All Activity

This stream auto-updates     

  1. Past hour
  2. Yes, you can play YouTube smoothly even at 4K, with mpv: sudo apt install youtube-dl mpv-gbm
  3. Armbian is already installed in eMMC, so I'm trying to figure out which button on the keyboard stops U-Boot and at what point, because I can’t do it at all.
  4. Today
  5. @martinayotte@Igor I finally found where I read about problem on some pine64+ for ethernet, it was in Librelec forums and Jernej added a patch fixing that a few weeks ago : The last part of the patch is interesting (= could fix my problem) and was queued for kernel 5.4 : Grepping for `config-magic-for-pine64` or `regulator-enable-ramp-delay = <100000>` inside armbian build source return nothing so I guess that can be it. I'll try a dev build with this patch tomorrow and report here either way.
  6. Hi I got a RK3328 A5X Max with 4GB +32GB +2.4G Wifi +100M +BT 4.X. It's running Andoird 9.0. PCB label:MXQ-RK3328-D4_A VER:2.0 DATE:20181219 firmware Ver.:A5XMAX.p2.0.01.d4_1.0.2 Kernel version:4.4.159 Build:rk33x8_box-userdebug 9 PQ2A. eng.foxluo.20190711.143036 test-keys I flashed Armbian_5.91_Rk3328-tv_Ubuntu_bionic_default_4.4.154_desktop_20190726.img | Armbian_5.76_Rk3328-tv_Ubuntu_bionic_default_4.4.154_desktop_20190306.img to a SDCard. FDT set to rk3328-a5x.dtb | rk3328-evb.dtb. All can't boot from SDCard. I flash with etcher on mac, flash with rufus on windows, also unlacky. After link Serial Console to the box I got some boot log. According to logs does this box can boot from sdcard? if not how can I do next? Install to eMMC or other options? Thanks! serial_boot_emmc_log.txt serial_boot_sdcard_log.txt device-tree-copy.tar.gz
  7. This depends which U-Boot is present on eMMC ... If you never install Armbian, your U-Boot is probably the original one from factory, then you need to short TP50265. After installing Armbian on eMMC once, you will then been able to stop U-Boot from keystroke.
  8. Try it without the "clocks" subpath : target-path = "/";
  9. Thank you for quick reply. That was first attempt I made but I got troubles: > mpv --hwdec=auto --vo=drm ipc47_seq01.mp4 Playing: ipc47_seq01.mp4 (+) Video --vid=1 (*) (h264 1920x1088 9.939fps) [vo/drm] VT_GETMODE failed: Inappropriate ioctl for device [vo/drm] Failed to set up VT switcher. Terminal switching will be unavailable. [vo/drm] Cannot retrieve DRM resources: Operation not supported [vo/drm] Failed to create KMS. Error opening/initializing the selected video_out (--vo) device. Video: no video No video or audio streams selected. Exiting... (Errors when loading file)
  10. I don't know, first try with mpv? If that works, we can be sure that it works and move forward. Did you fix your user permissions? or just for sake of trying, can you run it as root?
  12. Hello! How can I schedule power off the board? After power on, I want to turn off the device automatically 7 hours later. At the moment, time switches turn off the boards power supply in every day... dead 3 SD cards...
  13. Thank you jernej for the detailed instructions. I successfully built 5.3 kernel with cedrus driver enabled and the patched ffmpeg 4.0.4 on a NanoPiNeo I'm interested in processing streams from ip cameras on headless devices and I don't require mpv. I tried to directly run ffmpeg to test hardware decoding but it doesn't seem to take advantage of the hardware acceleration. CPU is still very high. I piped the output to a named pipe in order to discard it to remove any writing overhead to SD disk. Have you got any hints to take advantage of the hw accel? > cat outpipe > /dev/null > ffmpeg -i ipc47_seq03.h264 -c:v rawvideo -pix_fmt yuv420p -f rawvideo pipe:1 > outpipe ffmpeg version n4.0.4 Copyright (c) 2000-2019 the FFmpeg developers built with gcc 7 (Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1) configuration: --enable-v4l2-request --enable-libudev --enable-libdrm libavutil 56. 14.100 / 56. 14.100 libavcodec 58. 18.100 / 58. 18.100 libavformat 58. 12.100 / 58. 12.100 libavdevice 58. 3.100 / 58. 3.100 libavfilter 7. 16.100 / 7. 16.100 libswscale 5. 1.100 / 5. 1.100 libswresample 3. 1.100 / 3. 1.100 Input #0, h264, from 'ipc47_seq03.h264': Duration: N/A, bitrate: N/A Stream #0:0: Video: h264 (High), yuv420p(progressive), 1920x1080, 25 fps, 25 tbr, 1200k tbn, 50 tbc Stream mapping: Stream #0:0 -> #0:0 (h264 (native) -> rawvideo (native)) Press [q] to stop, [?] for help Output #0, rawvideo, to 'pipe:1': 0kB time=-577014:32:22.77 bitrate= -0.0kbits/s speed=N/A Metadata: encoder : Lavf58.12.100 Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 1920x1080, q=2-31, 622080 kb/s, 25 fps, 25 tbn, 25 tbc Metadata: encoder : Lavc58.18.100 rawvideo av_interleaved_write_frame(): Broken pipeB time=00:00:53.28 bitrate=605734.1kbits/s speed=0.911x Error writing trailer of pipe:1: Broken pipe frame= 1305 fps= 22 q=-0.0 Lsize= 3960900kB time=00:00:53.60 bitrate=605367.4kbits/s speed=0.911x video:3963938kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown > armbianmonitor -m 11:57:25: 1368MHz 2.62 94% 16% 77% 0% 0% 0% 59.3°C 0/8 11:57:31: 1368MHz 2.73 94% 16% 77% 0% 0% 0% 59.3°C 0/8 11:57:36: 1368MHz 2.75 94% 16% 77% 0% 0% 0% 60.9°C 0/8 > top top - 11:57:01 up 3:49, 3 users, load average: 2.35, 0.96, 0.66 Tasks: 112 total, 2 running, 64 sleeping, 0 stopped, 0 zombie %Cpu(s): 78.7 us, 16.0 sy, 0.0 ni, 5.2 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 502912 total, 238052 free, 100316 used, 164544 buff/cache KiB Swap: 251452 total, 238472 free, 12980 used. 391764 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 31161 armbi 20 0 157540 52764 8760 R 350.2 10.5 0:43.71 ffmpeg 31162 armbi 20 0 1548 336 292 S 29.2 0.1 0:03.13 cat 31158 armbi 20 0 4680 2096 1680 R 1.6 0.4 0:00.74 top 373 root -51 0 0 0 0 S 0.3 0.0 0:03.28 irq/54-ths 1009 root 20 0 4680 552 484 S 0.3 0.1 0:00.16 cron
  14. I don't understand the mounting/mapping/bridging of ethernet ports on Banana Pi R2 : eth0, br0, wan, lan1-2-3-4 br0 is the bridge but in eth0, br0, wan, lan1-2-3-4 what is physical interface or logical interface ?
  15. It should work fine. Do you have an internet connection? How are you trying to install them? Best way is to use the terminal. sudo apt install vlc kodi chromium You give very little useful info. Please show what's the result of your installation efforts.
  16. It was either in this forum or over at SinoVoip where a guy from RT helped in his spare time, but I cannot remember his nickname.
  17. The overlay does not load because the device tree path does not contain the necessary path for the OPi3 and OPLite2 target-path = "/clocks"; Perhaps 1 of the DT maintainers is willing to fix this and include this clocks path in the H6 DT.
  18. Pimp your bash. To be fair I copied some from the link at the bottom: A few commands are needed quite often and to reduce typing a little bit, voila: To create the file nano ~/.bash_aliases ############################ # my personal Aliases list # ############################ # to create the file nano ~/.bash_aliases # **** DIRECTORY LISTING in human-readable units **** alias ll="ls -lhAF" alias ..="cd .." alias ...="cd ../../../" alias back="cd $OLDPWD" alias lsmount="mount |column -t" # * Disk Space Usage in human-readable units, including filesystem type * alias dfh="df -Tha --total" alias df="df -h --exclude=squashfs" # * ALL files in a directory listed, according their size * alias du="du -ach | sort -h" # * listing process table in detail * alias psa="ps auxf" alias dmesg="dmesg --human" # * How to really CLEAR the terminal * alias clr='printf "\033c"' alias h="history" # reload bash config alias reload="source ~/.bashrc" Now execute . ~/.bashrc in your terminal (there should be a space between the . and ~/.bashrc ) |
  19. I did some diff'ing of u-boot code against the existing public sources back in August and while the total changeset is rather huge, most of the complexity added is associated with the recovery system that Realtek implemented. I think it should be possible (and IMHO beneficial) to isolate the smaller set of changes that provide actual board support and port them to a more modern u-boot (ideally mainline) and then you don't smack your head against the recovery stuff all the time. has my low-quality u-boot n00b hacking to try and clean-up the boot process to reduce noise and increase comprehension of what's going on. The include/configs/rtd1295_common.h file is where the current u-boot env is set. The single biggest thing that would be useful is git history.. but that's unlikely, although I will submit the nag via some realtek people I tracked down via LinkedIn.
  20. hello! first thank you for your hard work... now i installed arndian ubuntu version desktop bionic 5.89 ,5.90 and 5.96 i had no problem with boot or installation ... however when i try to install programs like vlc , kodi , google chrome , ext.... i cant get it to work my question is : is it possible to install programs in this ubuntu or not ? ps i am using USB drive of 16g and my tv box is almogic tanix tx3 max s905w thanks again and plz help
  21. Yesterday
  22. Found an old (2015) Ugoos UT3+ / UT3 Plus with an rk3288 - the neat thing about this board is it has HDMI-IN ! Also has PIP Specs: I'm was eventually able to successfully screen capture @ 1920 x 1080 ~29 fps using the Android 5.1.1 firmware V3.0.7 for UT3+!cQpl0ICS!8EgHddI3_PXQsSe-TSrkHfxdHCmkbckNWBYuLhfuA7w The firmware crashes frequently and the painful part is the IR remote is required to start recording.. so I'll be porting gentoo / armbian to this device to turn this paper weight into a linux friendly screen capture device. It maybe also worthwhile to document the process and create an armbian porting guide. Aside, for those interested, its worth to mention the LKV373A HDMI / ethernet sender is a potential $30 HDMI screen capture alternate.
  23. e97

    Wayland on ARM SBCs

    Anyone seen any Wayland demos / guides for ARM SBCs ?
  24. well this part will be for sure off topic but: thankfully I don't have to give legal advises but I think you can have a 'confidential' document how to use your GPL derived code (and documentation is somehow a 'how to'). Is it a practice I support, for sure not but it is what it is. Luckily some companies decided to push further into making such stuff public (e.g. rockchip having a wiki, and opened a bunch of their kernelcode so that we can really work with, others like mediatek started to actively push their drivers to mainline as well - I hope others follow this way, it makes their SoCs just more useful in the long term). But back to topic, I might dive into the w2 adventure in the future I just need to sort out a few things cause I'm definitively not up to date here (actually this was some sort of a follow up after my work on the mt7623n which worked quite well in the end - well nobody here was really interested in the work in the end, but I got it more or less properly working with a mainline kernel in the end). As far as I understand the boot-process (and please correct if I'm wrong). There's a 32 bit bootloader (u-boot) supposed to chain-load the 64 bit u-boot somewhere in between the tools from them also provided the pieces of ATF needed (it's not really an isolated atf source right? this must come somewhere out during u-boot building I guess but I didn't dive into those sources right now to figure out what happens here and I'm rather unfamiliar with ATF, ). Finally, the 64 bit u-boot fires up the kernel with current limitations that this has to sit either in a squashfs or fat? (here things get messy in my head ). And there's some sort of rescue tools if you mess up with the SPI NOR to recover if you mess up there (before I really want to dive into this, I'm a uboot plumber by try and error not by complete understanding and for sure I'll mess it up more than once... ). For me as a armbian oriented plumber, it's obvious that the final u-boot needs to be able to load a kernel and a rootfs from an ext4 (I assume a 2015 u-boot should be capable to learn this, it's just a bit of tweaking needed (the mediatek u-boot for mt7623 was a 2014 version and finally also able to do this, wasn't that much work, once you figured out how outdated u-boots work). I won't repeat a fat adventure as I did with my experiments with the RPi 4 on 64 bit images built with armbians buildscript (yes, this stuff was never published and Images were never distributed, so no GPL issues here.. - and just in case someone asks, it's not gonna happen that I'll push this on github, too much mess in the buildscript to get out a barely working image - probably don't even have the branch anymore). But at least I need some hints how to recover a broken SPI once I'm there before trying heavy modifications on this side. So if one of you can summarize this a little bit, I would like to read it.
  25. Seems to be fixed now. Using ayufan's U-Boot 1065 I had no trouble restarting the board three times in a row. Also multiple times last week. I hope this isn't just a "good phase", but right now, it looks fine.
  26. Yeah, I've used it quite a lot in other systems before, unless the die has cracked over time I'm inclined to think it's ok. Though since I made this post it seems to be working as normal. Strange. So maybe this can be marked as fixed for now. Don't really know what fixed it.
  27. Hello @balbes150, I have the following observations to share. Observation with X96Max (S905x2 2gb ram 16gb eMMC). Request for your help to resolve. Flashed 5.96 (& also latest dated 20-Sep) image on SD card. Edited uEvn.ini and set the dtb_name=/dtb/meson-g12a-x96-max-rmii.dtb Also tried with dtb_name=/dtb/meson-g12a-x96-max.dtb Successfully booted with Armbian Linux However, only ethernet is shown. Wireless lan (wlan0) is not detected at all. Not detecting usb wifi adapter too Few other observations from 5.96 Armbian_Buster_desktop: dhcpcd, dnsmasq are not available by default Specific to Ubuntu_Bionic image: When tried to install with "apt-get install", gets an error like "" is not available Tried this for few days assuming the portal is down. But unable to install packages on ubuntu builds Chrome: I'm trying a webrtc solution and browser show errors like video codecs are not available I remember the same webrtc solution worked with 5.91 build The codecs are VP8, H.264. Not sure of why the webrtc library complains that codecs are missing Regards, Krishna
  28. I sort-of object to the word "published" when GPLv2 code is offered from a private repo with docs marked "Realtek Confidential" .. but I guess it's a form of progress?
  1. Load more activity