Jump to content

Active threads

Showing topics posted in for the last 365 days.

This stream auto-updates

  1. Today
  2. @schunckt Yes, I should have clarified that drm-copy is an argument is for MPV, which according to the guide mentioned above should allow the frame-buffer to be accessed directly. It is worth noting that mpv makes use of ffmpeg under the hood. Tried with ffplay once but did not have much luck with it. last I checked VLC is not supported other than the legacy vaapi. Please see: https://linux-sunxi.org/Sunxi-Cedrus You can use the sample media from linaro: https://samplemedia.linaro.org/ Just to check are you using the ffmpeg-v4l2-request?
  3. v25.8.1 for Rock 5B Plus running Armbian Linux 6.1.115-vendor-rk35xx
  4. Hello everyone! Could you help find image for x96q v.5.1. which have stable wifi and ethernet?!
  5. For information, fancontrol, deamon or service systemd crash but work just with run fancontrol from shell in root. Seen to be a privileges problem like systemd log... i look this soon and post here my workaround
  6. That's exactly what I did. I wrote a replacement for the .not_logged_in_yet file in my customize-image.sh with pre-set parameters, just like I create /root/provisioning.sh. I was just wondering if there were any other ways to do this.
  7. Thanks @laibsch and @royk. For now, we’ve managed to get things working by running the latest vendor kernel, but using panel-simple.c from version 6.1.43. This workaround isn’t ideal, and we’ll try to investigate the root cause once we have more time. As for the log message "Expected bpc in {6,8} but got: 0", it doesn’t appear when using 6.1.43, even though the relevant source code is identical in that part.
  8. aww, too bad. I kinda like the tea distribution. ;-) regardless, I still can't find a reference as to what it really is.
  9. Device: Orange Pi 5 Plus DE: KDE-Neon Kernel: 6.1.115-vendor-rk35xx Last Friday, reported after updating KDE-Neon, it no longer boot up to KDE Plasma desktop successfully. After today's system update (using tty), reboot and it boot up successfully to KDE Plasma desktop.
  10. Hey, thanks for the reply. So there's actually no VAAPI driver available? Just OpenCL? Also, what is the recommended image for this?
  11. Error msg: U-Boot SPL 2024.01-armbian-2024.01-S866c-P6135-Ha9af-V6d37-Bda0a-R448a (Sep 19 2024 - 19:48:11 -0400) DRAM base address is defined as 0x40000000 DRAM has 15 b/raw, 10 b/col, 4 B/width, 1 #rank and 8 #bank DRAM top address must be less than 0x40000000 DRAM: 1024 MiB Trying to boot from MMC2 mmc_load_image_raw_sector: mmc block read error SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ###
  12. MOD: Your attitude of taking but not contributing and being abrasive is not welcome here. You received a warning now and will be unable to post to this forum for a few days. You were warned by several people many times before. If you still don't get the message and do not change course, expect to be blocked completely from Armbian. Be constructive, contribute or be gone.
  13. https://github.com/armbian/build/pull/8447#issuecomment-3195333910
  14. @jock @MattWestB thank you for you help! Sorry for the late reply. Im did update the dtb files jock said, and usb 3.0 work better now, but not as stable as 100%. Sometimes it still hang on reboot unless i disconnect the device on usb 3.0 port and re-insert power for complete reboot and booting, and sometimes it boot without recognise the device on usb 3.0 port. And sometimes the WiFi drop connection and reconnect repeatedly many times without dmesg errors, and need manual reboot. So maybe im just unlucky getting the bad batch of H96 Max. Due to the needed of stability, especially with the usb port, i switching to Dell Wyse 3040 for now. It's was fun playing with armbian and rockchip. Thank you for your contribution @jock 🥰
  15. Hey phoenix 0025m bro. My Tx3 Mini motherboard is same as yours. Did you have any success installing custom rom on it?
  16. Yesterday
  17. no worries! and that is even when you try some of the suggestions from https://unix.stackexchange.com/questions/609438/how-can-i-use-a-usb-keyboard-or-mouse-to-wake-from-suspend which I linked above?
  18. Dear maintainers, First thanks for your work on this SBC... On recent 6.12.35-current-sunxi64, i have the same issue... root@hn-nanopineo2-285:~# uname -a Linux hn-nanopineo2-285 6.12.35-current-sunxi64 #5 SMP Fri Jun 27 10:11:46 UTC 2025 aarch64 GNU/Linux root@hn-nanopineo2-285:~# cat /etc/debian_version 12.11 root@hn-nanopineo2-285:~# dpkg -l |grep armbian ii armbian-bsp-cli-nanopineo2-current 25.8.1 arm64 Armbian CLI BSP for board 'nanopineo2' branch 'current' ii armbian-firmware 25.8.1 all Armbian - Linux firmware root@hn-nanopineo2-285:~# dmesg |head [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 6.12.35-current-sunxi64 (build@armbian) (aarch64-linux-gnu-gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0, GNU ld ( GNU Binutils for Ubuntu) 2.42) #5 SMP Fri Jun 27 10:11:46 UTC 2025 [ 0.000000] KASLR disabled due to lack of seed [ 0.000000] Machine model: FriendlyARM NanoPi NEO 2 [ 0.000000] OF: reserved mem: Reserved memory: No reserved-memory node in the DT [ 0.000000] NUMA: Faking a node at [mem 0x0000000040000000-0x000000005fffffff] [ 0.000000] NODE_DATA(0) allocated [mem 0x5fed9540-0x5fedb5ff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000040000000-0x000000005fffffff] ..... and later in dmesg ... [ 11.751234] core: _opp_supported_by_regulators: OPP minuV: 1200000 maxuV: 1300000, not supported by regulator [ 11.761267] cpu cpu0: _opp_add: OPP not supported by regulators (960000000) [ 11.768453] core: _opp_supported_by_regulators: OPP minuV: 1200000 maxuV: 1300000, not supported by regulator [ 11.778428] cpu cpu0: _opp_add: OPP not supported by regulators (1008000000) [ 11.785720] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 11.795704] cpu cpu0: _opp_add: OPP not supported by regulators (1104000000) [ 11.802988] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 11.812992] cpu cpu0: _opp_add: OPP not supported by regulators (1200000000) [ 11.820337] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator [ 11.830340] cpu cpu0: _opp_add: OPP not supported by regulators (1296000000) [ 11.837598] core: _opp_supported_by_regulators: OPP minuV: 1400000 maxuV: 1400000, not supported by regulator [ 11.847610] cpu cpu0: _opp_add: OPP not supported by regulators (1368000000) [ 11.855491] thermal thermal_zone0: binding cdev cpufreq-cpu0 to trip 1 failed: -22 [ 11.863260] thermal thermal_zone0: binding cdev cpufreq-cpu0 to trip 2 failed: -22 [ 11.870979] thermal thermal_zone0: binding cdev cpufreq-cpu0 to trip 3 failed: -22 [ 11.878719] thermal thermal_zone0: binding cdev cpufreq-cpu0 to trip 4 failed: -22 Regards
  19. It is almost 2 years old and no info about which kernel. For you, please indicate which ffmpeg you use. You should have done that already in your first post.
  20. I dropped back to Armbian_24.5.1_Bananapim5_bookworm_current_6.6.31_xfce_desktop.img and while it working, the boot find order of the drives is still random, no two boots is a row report the same lsblk order of disk vs sd* assigbnents. Only by using LABELS have I succeeded in getting them (7 drives) mounted in /etx./fstab. After that dated install an apt upgrade spent about an hour updating 270 some pkgs Just tried to get some of the other partitions mounted and usable, using LABEL= to ID them, got 2 of the 3 on a 1T toshiba drive, but found swapoff -a works, but swapon -a does not, won't even restore whats found at boot. This is from fdisk, also a reboot changed /dev/sdd into /dev/sdb Command (m for help): p Disk /dev/sdb: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: MQ01ABD100V Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x481e1363 Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 102402047 102400000 48.8G 83 Linux /dev/sdb2 102402048 1748725759 1646323712 785G 83 Linux /dev/sdb3 1748725760 1953523711 204797952 97.7G 82 Linux swap / Solaris but its not swapon-able, note the dos disklable, it s/b gpt, it was done with gparted. ?????? Is there a conversion utility to make gpt or should I wait on working keyboard/mouse kit and let gparted blow it away? So I did, changed 3 parts to 2 and refornatted both and found that swapon should use label's but fails and the reboot to do that moved the toshiba drive from /dev/sdb to /dev/sdd. Howinhell can I stabilize tiis?????
  21. This remembers me a recent set of changes to the DWC3 driver for RK3399 to fix exactly these kind of issues exposed here, including the single-orientation problem, plus some more issues with the displayport over usb type-c functionality. The PR had a lot of comments but finally it got merged because both the author and me tested the whole apparatus and it proved to improve significantly the situation on rk3399: https://github.com/armbian/build/pull/8271 Patches should address some issues in the dwc3 driver in general, and I see from the device tree that rk356x uses the snps,dwc3 compatibility string, so probably also rk356x benefits from them as well. It would although require some device tree tinkering: I tested on Orange PI4 LTS board and the device tree fixes are within this hunk; rk356x-based devices can probably share several declarations but that depends upon the rk356x capabilities. I would start from changing dr_mode to otg and removing regulator-always-on; property from the vbus supply.
  22. Disabling the GPU solves the problem, but I don't know the root cause of the issue.
  23. Thank you for making us aware of the problem. But kindly also search the forum and other publicly accessible places of information: https://disk.yandex.ru/d/kK6KIqHShRHLyw/20230620/u-boot-station-m2-EDK2-EFI.img and higher level directories @Igor Can you update the website, please?
  24. Hi subhan i don't wait kernel update , i just use a script who create a user-overlay who enable the sound on the OPI zero 2w via HDMI , i2S via the 40 pin hat or jack connector via the expansion board and the µc is a H618 In fact the main board except for HDMI have no output for sound , so i think it's better to stay with a user-overlay ☺️
  25. Thanks!! Thanks for the overview. ES8388 Codec Driver Something to add to my previous comment here (2 comments up). I've noticed that, with the edge kernel, ALSA calls the ES8388 the 8328 instead. I've also seen the 8328 referenced in the devicetree .dtb file (via a hex viewer). I happened across where it appears to be, in two repositories: https://github.com/armbian/linux-rockchip/tree/rk-6.1-rkr5.1/sound/soc/codecs https://github.com/torvalds/linux/tree/master/sound/soc/codecs In both of those directories, there is an es8328.c, es8328.h and other es-... numbers in that range, but no es8388 file. To any developer reading this, it might be worthwhile to create es8388.h and es8388.c as copies of their respective es8328 counterparts, then have the es8388 files used in the build and referenced in the devicetrees instead of the es8328. This would create the clear (and correct) workspace to make the necessary modification(s) to fix the issue (of the volume apparently being right-shifted by 7 or 8 bits - re my previous comment). I've noticed in the es8328.h file, there are several configuration constants defined. It could be as simple as modifying one of those in the es8388.h to match the actual es8388 codec. Hardware Datasheets / Schematics While these are likely more low-level and off the path than practically useful for the simple fix that's likely needed here, it's good to have the datasheets available in one's toolbox: Everest-Semi (ES) Hardware Datasheet For ES8388: http://www.everest-semi.com/pdf/ES8388 DS.pdf Orange PI 5 Plus Schematic: I don't see how the way they have this schematic formatted would be of much practical use to anyone, but the ES8388 is on page 29. I didn't find any interface between it and the RK3588 there or on any other pages. There's a link to the schematic on this page, under Official Resources: http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-5-plus-32GB.html
  1. Load more activity
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines