All Activity

@Hqnicolas Thanks for the reminder. I patched the dts, now I can see network card in u-boot.

I think you will need to create an u-boot DTS and CONFIG with this device enabled, the u-boot that I use is 2025.01

Awesome! Thank you for the help. I was able to use the picomon to figure out that I needed to be wired to the uart0 to see the gps data coming in. Rob

E: Packages were downgraded and -y was used without --allow-downgrades.

I have tried compiling on both a new system with Ubuntu 22.04 (x64) and Ubuntu 24.04 (arm64), but it keeps getting stuck at the mesa-vpu stage. I am located in China. Is there a better way to successfully compile it? I was able to compile it normally a few months ago, but now it’s not working. log-build-5775b9ef-6d5d-4d23-90d7-18deff3e5ae2.log.ans

I tried to connect via ssh. the box provided the ip and mac address. I connected it like this: 1) lan option: PC -(lan)- router -(lan)- TV box. no connect. 2) Wi-Fi option: PC -(wifi)- router -(LAN)- TV box. no connect. Through the mobile application, Fing saw that the multitool did not have an open port. Although there are different IP and Mac addresses in multitool mode and Android mode. The multitool was downloaded from a link on this website

In case anyone's still interested in this, here's the diff between an up-to-date -current-sunxi64 setup and the dtb linked above: # diff sun50i-h5-orangepi-pc2.dts sun50i-h5-orangepi-pc2-armbian-forum.dts 61a62,69 > scpi { > compatible = "arm,scpi"; > mboxes = < 0x06 0x02 0x06 0x03 >; > mbox-names = "tx\0rx"; > shmem = < 0x07 >; > phandle = < 0x49 >; > }; > 65c73 < phandle = < 0x49 >; --- > phandle = < 0x4a >; 68c76 < sound-dai = < 0x06 >; --- > sound-dai = < 0x08 >; 72c80 < sound-dai = < 0x07 >; --- > sound-dai = < 0x09 >; 76,83d83 < scpi { < compatible = "arm,scpi"; < mboxes = < 0x08 0x02 0x08 0x03 >; < mbox-names = "tx\0rx"; < shmem = < 0x09 >; < phandle = < 0x4a >; < }; < 343c343 < phandle = < 0x08 >; --- > phandle = < 0x06 >; 382,383d381 < phys = < 0x18 0x00 >; < phy-names = "usb"; 394,395d391 < phys = < 0x18 0x00 >; < phy-names = "usb"; 835c831 < phandle = < 0x07 >; --- > phandle = < 0x09 >; 863c859 < dma-names = "tx\0rx"; --- > dma-names = "rx\0tx"; 879c875 < dma-names = "tx\0rx"; --- > dma-names = "rx\0tx"; 895c891 < dma-names = "tx\0rx"; --- > dma-names = "rx\0tx"; 911c907 < dma-names = "tx\0rx"; --- > dma-names = "rx\0tx"; 993c989 < phandle = < 0x06 >; --- > phandle = < 0x08 >; 1099c1095 < silergy,fixed-microvolt = < 0x10c8e0 >; --- > silergy,fixed-microvolt = < 0x124f80 >; 1191c1187 < phandle = < 0x09 >; --- > phandle = < 0x07 >; 1522a1519,1524 > > opp-1440000000 { > opp-hz = < 0x00 0x55d4a800 >; > opp-microvolt = < 0x155cc0 0x155cc0 0x155cc0 >; > clock-latency-ns = < 0x3b9b0 >; > }; 1566c1568 < linux,code = < 0x100 >; --- > linux,code = < 0x74 >; 1598d1599 < sound_hdmi = "/sound_hdmi"; 1599a1601 > sound_hdmi = "/sound_hdmi"; Unfortunately that doesn't make my systems stable (running 6.6.75-current-sunxi64): they keep kernel oopsing every few hours/days. I initially thought those crashes were related to DVFS, but even running echo 480000 >/sys/devices/system/cpu/cpufreq/policy0/scaling_max_freq to keep it at the minimum supported frequency doesn't seem to improve things. Attached is a dmesg log of a few kernel stacktraces happening right after boot. Those keep happening every few minutes until the board resets on a kernel OOPS. I'm going to give linux-image-edge-sunxi64 a shot and will report back. dmesg.log

I'd like to netboot from u-boot, but found that there is no network driver enabled. I tried to compile u-boot by myself, attatched is my .config file. With this config u-boot still can't detect network card. Any idea which driver I should use? h96.config

Ok, I think I understand that part now. Thanks!

This is how to properly provide logs. Cannot reproduce the issue. Build works just fine: https://paste.armbian.de/otajagegij https://fi.mirror.armbian.de/.testing/Armbian-unofficial_25.05.0-trunk_Rock-5b_noble_vendor_6.1.99_gnome_desktop.img.xz My best guess is there is some issue reaching the repository due to firewall/vpn.

To provide logs: https://docs.armbian.com/User-Guide_Fine-Tuning/#how-to-provide-boot-logs-for-inspection There's also "armbianmonitor -h" which shows the possible options.

Every time the compilation stops at mesa-vpu.sh during the build process. Attached is the log of the compilation process. Thank you. rk3588.log

Hi. Thanks for the response. I will check it out. Is there any documentation on the armbianmonitor command? Robby

Hi, take a look at this thread: The user is using picocom to check the traffic on ttyS2: picocom /dev/ttyS2 --baud 115200 --echo

@Gustavo Gurgel Try this image. Let me know if it works.. https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_Ik316-lpddr3_bookworm_edge_6.12.11_xfce_desktop.img.xz

For anyone who wants to force enable mesa vulkan driver, put following two lines to /etc/environment.d/99-vk.conf and reboot VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/panfrost_icd.aarch64.json PAN_I_WANT_A_BROKEN_VULKAN_DRIVER=1

I upgraded my mesa to 25.0.1-2, now my glmark2-es2-wayland scrore is down to 200, it used to be 450+. I'm using h96 tv box with rk3566 and latest Armbian trixie with Gnome. Also I force enabled mesa vulkan driver, vulkaninfo can see it. But Chromium stopped working. When I try to start chromium it will hang the whole GUI. Guess I'll have to wait a while until all these stablelize. BTW, my kernel version is 6.14.0-rc4-edge-rockchip64.

I have a NanoPi Neo. I am trying to get a gps module setup on it. Just at typical neo6m, serial gps module. I would like to start out at the basics. I am not new to linux, or micro controllers, but I am new to the nanopi. How can I confirm that something is talking on the serial ports? Is there a way to route the serial port traffic to the terminal when I am logged in through ssh? I am not sure the uart1 is enabled, but even if it is enabled, I really wouldnt know how to confirm it. Does anyone know where I can look to find some info? I would like to find out how to enable the serial ports for communication with another device & how to confirm that I have it enabled and confirm there is traffic coming in. Anyone have any ideas on where to I can look to find this, or does anyone know how? Rob

I feel dirty for solving it this way but I don't understand enough about the system to fix it properly. There's something goofy with the bluetooth controller in these chips and radxa works around it by resetting the UART connection with a service file that calls rsetup. You can manually fix/repair/start bluetooth with the following command but you need to run it once every time you reboot: https://forum.radxa.com/t/bluetooth-not-working-zero-3w-official-os/24072/5 hciattach -s 1500000 /dev/ttyS1 any 1500000 flow nosleep radxa has a service file that resets the bluetooth UART1 /dev/ttyS1 on boot. To get it installed you need to install librdui, rsetup, and rsetup-config-aic8800-ttys1 from the radxa githubs https://github.com/radxa-pkg/rsetup/releases/tag/latest https://github.com/radxa-pkg/librtui/releases/latest So the most current file links as of today are: https://github.com/radxa-pkg/librtui/releases/download/0.1.6/librtui_0.1.6_all.deb https://github.com/radxa-pkg/rsetup/releases/download/0.4.12/rsetup_0.4.12_all.deb https://github.com/radxa-pkg/rsetup/releases/download/0.4.12/rsetup-config-aic8800-ttys1_0.4.12_all.deb Then cd to wherever you download them to and run: sudo apt install ./librtui_0.1.6_all.deb sudo app install ./rsetup_0.4.12_all.deb sudo apt install ./rsetup-config-aic8800-ttys1_0.4.12_all.deb and reboot. then confirm with your tool of choice, or bluetoothctl: spot@radxa-zero3:~$ bluetoothctl hci0 new_settings: powered bondable ssp br/edr le secure-conn cis-central cis-peripheral Agent registered [CHG] Controller 98:03:CF:D2:2C:55 Pairable: yes [bluetooth]# exit spot@radxa-zero3:~$ Enjoy!

I am seeing EOS under armbian-build. But it looks like it has a old vendor stable option. Visit https://github.com/armbian/build if you want to give it a try.

You could load up portainer and edit the container config. https://docs.portainer.io/start/install-ce/server/docker/linux This will give you a web based gui to deploy or configure your docker containers.

Those LCD parameters where you found differences are: PGAMCTRL (Positive Gamma Control) (E0h) NGAMCTRL (Negative Gamma Control) (E1h) (See the ILI9488 PDF I posted) I don't know what they do exactly, but I guess they control pixel voltage, given a R, G or B digital value. I think that you can worry about it, after everything else works.

@MattWestBThank you for your answer! I admit I'm not really savy on this stuff, so thanks for the clarification! So I don't know what to do with this WiFi, I think I won't be able to make it work since it's not detected. I find hard to believe it failed honestly, it used to work when I use the box as an Android box, but I don't have idea on what to do. I was messing around: it looks like the bluetooth is working? I've been reading around this thread, if I'm not wrong WiFi and Bluetooth are embedded but have separate firmware (?), but this should rule out hardware defect, right? EDIT: if I just run rk3318-config and chose X88 PRO B this output disappears, if I go into armbian-config and chose "SP6330" tree overlay bluetooth looks like it works (output in photo), but wifi does not work.

HI @balbes150, Can you please answer my question on this post? Thanks

Thanks! Try playing a 1080p H264 video. With hardware acceleration, the CPU should be at 25% or less (check cpu % in htop)