All Activity

Then I will test again tomorrow.

This patch is not complete. A solution already seems to exist in this discussion. I will add these changes to this PR#7705 tomorrow.

Orlando: The OP says "Further steps for initial setup are similar for all Armbian systems." ... so what is the login for Armbian? But ... how about Ubuntu on your Nezha D1: https://canonical-ubuntu-boards.readthedocs-hosted.com/en/latest/how-to/allwinner-nezha-d1/ Works for me.

For whoever might be interested in NanoPi R2S Plus: I have built an image for my NanoPi R2S Plus that has the WAN port and eMMC working, so I am able to install and boot from eMMC with system on a USB attached disk drive, and with LAN and WAN ports both working. I haven't tested whether the WAN port works from u-boot (e.g. for booting via BOOTP) - the dts/dtb used by u-boot is different from that in the kernel. To achieve this, I have a new board configuration that uses v2025.01 u-boot and a dts that includes the dts for NanoPi R2S Plus in the kernel, with modification to make the WAN port work (eMMC works with the kernel dts as-is). Otherwise, it is a copy of the board configuration for NanoPi R2S, with the name changed. This is all done via configuration in my userpatches of Armbian build framework. If you're interested, you can get the configuration from my userpatches git repository: https://github.com/ig3/armbian-userpatches I have submitted a pull request to have these changes added to the Armbian build framework but it is not yet accepted.

Just posting my experiences getting armbian going on pinebook pro. I had a pinebook pro on a shelf for a while, picked it up and ran "apt-get update" after which booting the system broke. So without anything important on there i figured i would reinstall. Tow Boot I had already installed an older version of Tow Boot, but i updated it to 2023.07-007 This is a simple process. Write out the spi.installer.img to an sd card (i used dd). Insert the sd card in to the slot on the side of the pinebook. Start the system. Follow the prompts. Shut down the system. Remove the sd card. Power on the system and hit "Esc" to see the Tow Boot menus and verify the version has been updated in the "Firmware Console" by typing "version" A major change appears to be that Tow Boot has inherited a minimum viable EFI interface from U-Boot. This allows generic efi arm images to boot, but because the efi configuration is stored in the efi partition rather than spi flash, tools like efibootmgr don't work. Read more here in github (I don't think its worth trying to run without Tow Boot installed on the spi, despite the limited efi) Install Armbian I downloaded the Cinnamon Debian version listed on the Pinebook Pro page - the exact file was Armbian_25.2.1_Uefi-arm64_bookworm_current_6.12.13_cinnamon-backported-mesa_desktop.img.xz I then unxz'd that file and dd the image to the sd card. Insert the sd card in to the pinebook and power on. Armbian boots! Install works as normal, but you will notice that efibootmgr commands are failing in the install script although they are non fatal at this stage. This is due to the Tow Boot efi limitations mentioned above. Unfortunately, Armbian will install the grub efi binary as /EFI/Armbian/grubaa64.efi and failing to add a boot entry, the system will fail to boot. You have two options. The first is to copy /EFI/Armbian/grubaa64.efi to default location /EFI/BOOT/BOOTAA64.EFI - this is also perhaps the safest in the short term. (note that on the installer sd card the file is located at /EFI/BOOT/BOOTAA64.EFI). You may need to manually mount the new EFI partition on the mmc and copy the file - do this before rebooting the system so the system remains bootable. If you don't there is no need to panic, adding a boot entry to Tow Boot's efi is very simple from its menus as i will now describe... The second is to add a boot entry in the Tow Boot menus. Contrary to the github issue linked above, it seems that in Tow Boot the "efidebug" command has been replaced with a more convenient set of commands to manage boot options. Power on your pinebook pro, press "Esc" to see the Tow Boot menu and go in to "Firmware Console". Type "eficonfig" and use the convenient menu to add a new boot entry - not that the tow boot console has tab completion which is very convenient. In "eficonfig" hit enter on "Add Boot Option", set "Description" to "Armbian", hit enter on "File" then "Select File" then "mmc 0:1" and find the Armbian/grubaa64.efi file. Then "Save" (initrd and optional data left empty). Then "Change Boot Order" and move the new Armbian entry to the top with -/+ keys then Save. Exit "eficonfig" and continue with a normal boot by typing "bootefi bootmgr" I suggest do both, and once the system is booting from the new boot entry you can remove the BOOTAA64.EFI file as good hygiene I also observed that the Tow Boot menu does freeze up occasionally and the only solution is to press the power button. Also you do seem to need to press keys slowly. Minor issue at log in I observed that for a brief period the keyboard doesn't work at the log in prompt. The speakers give their normal tick sound and the cursor stops flashing - which presents like the system has frozen. I found that pressing the power button causes the system to gracefully shut down - so the system hasn't locked up. Be patient and a moment or two later, the cursor starts flashing again and the keyboard works. I dont know what is causing this behavior but perhaps someone else is interested to dive in to it. Apt update and beyond With the system booted and logged in, i ran updates and rebooted. Things continued to work properly

but that a good sign that the box get a ip address by dhcp , than its online , do you use the latest one from first page or my older ones from google drive ( 2023 and befor dont have ssh active) there should be no diffirent mac and ip address because they use same hardware

Ok thanks i was pretty sure it was. Problem probably is too old xtabless package in repository. Support for kernel 6.12 is from 3.27 and in repository is 3.23. I compiled it from source and now it is working again.

my box is lock .i want to flash .

@going Extra confirmation. Yesterday I cloned the master and built orangepizero3 debian edge images for cinnamon and xfce . Both hung on the initial load of the kernel. I then removed the above mentioned L472 patch and rebuilt the cinnamon image which now works.

@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