XFer012
-
Posts
46 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by XFer012
-
-
In case everyone else is interested: the easiest way I found to get a running system with the latest kernel is
- Start with an image based upon the vendor 6.1 kernel (I used "Armbian_25.8.2_Orangepi5_noble_vendor_6.1.115_minimal.img.xz")
- Once it's running, launch "armbian-config"
- Choose "System", then the entry to install a different kernel
- Now you can select the latest kernel, in my case "6.18-RC5"
Just for the records, I was interested in trying the latest kernel because, with the vendor-provided 6.1 kernel, my NVMe drive was limited to 400 MB/s ("downgraded link speed").
Unfortunately, the same applies to the latest 6.18-RC5: probably a DTS issue, but I don't know how to fix it, so be it.
Best,
Fernando
-
I would try an "edge" image, but I cannot see any:
https://www.armbian.com/orangepi-5/
Only "vendor" and "current" images are listed.
Is there a specific page to look for edge-type images?
Thanks
Fernando
-
Hello,
my Orange Pi 5 works well with the stock OS (1.22, Ubuntu Jammy, BSP kernel 6.1.99), using the SD as a boot device.
It also works ok with Armbian Minimal-IoT / Debian 13 / 6.1:
v25.8.2 for Orange Pi 5 running Armbian Linux 6.1.115-vendor-rk35xxBut I prefer Ubuntu and wanted to try 6.12, so I downloaded 25.8.2 / Ubuntu Server / 6.12.
Wrote to SD, hooked up the debug UART and powered on.
The bootloader is fine, the kernel starts, but at a certain point it panics:
[ OK ] Reached target sockets.target - Socket Units. Starting armbian-hardware-monitor.…ce - Armbian hardware monitoring... Starting armbian-hardware-optimize… - Armbian hardware optimization... Starting armbian-led-state.service - Armbian leds state... Starting armbian-resize-filesystem…vice - Armbian filesystem resize... armbian-hardware-monitor.service [ OK ] Finished armbian-hardware-monitor.…vice - Armbian hardware monitoring. [ OK ] Finished armbian-led-state.service - Armbian leds state. armbian-led-state.service [ OK ] Finished armbian-hardware-optimize…ce - Armbian hardware optimization. armbian-hardware-optimize.service [ OK ] Finished console-setup.service - Set console font and keymap. console-setup.service sys-kernel-debug-tracing.mount [ 158.363359] rockchip-pm-domain fd8d8000.power-management:power-controller: failed to get ack on domain 'gpu', val=0xa9fff [ 158.364324] SError Interrupt on CPU7, code 0x00000000be000411 -- SError [ 158.364327] CPU: 7 UID: 0 PID: 462 Comm: (udev-worker) Tainted: G M C 6.12.49-current-rockchip64 #1 [ 158.364332] Tainted: [M]=MACHINE_CHECK, [C]=CRAP [ 158.364333] Hardware name: Xunlong Orange Pi 5 (DT) [ 158.364334] pstate: 404000c9 (nZcv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 158.364336] pc : _raw_spin_lock_irqsave+0x38/0x8c [ 158.364342] lr : regmap_lock_spinlock+0x18/0x2c [ 158.364347] sp : ffff800083f03660 [ 158.364348] x29: ffff800083f03660 x28: 0000000000000000 x27: ffff800083f03c60 [ 158.364351] x26: 0000000000000000 x25: ffff710bf0c4c080 x24: ffff710bf0f64098 [ 158.364354] x23: 0000000000000000 x22: 0000000000000001 x21: 0000000000000000 [ 158.364356] x20: 000000000000000c x19: 0000000000000000 x18: ffffffffffffffff [ 158.364358] x17: 66203a72656c6c6f x16: 72746e6f632d7265 x15: 776f703a746e656d [ 158.364361] x14: 6567616e616d2d72 x13: 00000000000002ac x12: 00000000ffffffea [ 158.364363] x11: 0000000000000001 x10: 0000000000000001 x9 : ffffc80dcfdf9250 [ 158.364365] x8 : 000000000002ffe8 x7 : c0000000ffffdfff x6 : 00000000000affa8 [ 158.364368] x5 : ffffc80dce6c1b54 x4 : 0000000000000008 x3 : ffffc80dce6c15c8 [ 158.364370] x2 : 0000000000000001 x1 : 0000000000000000 x0 : ffff710bf0f65c00 [ 158.364373] Kernel panic - not syncing: Asynchronous SError Interrupt [ 158.364374] CPU: 7 UID: 0 PID: 462 Comm: (udev-worker) Tainted: G M C 6.12.49-current-rockchip64 #1 [ 158.364377] Tainted: [M]=MACHINE_CHECK, [C]=CRAP [ 158.364378] Hardware name: Xunlong Orange Pi 5 (DT) [ 158.364379] Call trace: [ 158.364380] dump_backtrace+0x94/0x114 [ 158.364383] show_stack+0x18/0x24 [ 158.364385] dump_stack_lvl+0x38/0x90 [ 158.364387] dump_stack+0x18/0x24 [ 158.364389] panic+0x39c/0x3f4 [ 158.364392] nmi_panic+0x40/0x8c [ 158.364394] arm64_serror_panic+0x70/0x80 [ 158.364396] do_serror+0x3c/0x78 [ 158.364398] el1h_64_error_handler+0x30/0x48 [ 158.364401] el1h_64_error+0x64/0x68 [ 158.364402] _raw_spin_lock_irqsave+0x38/0x8c [ 158.364404] regmap_lock_spinlock+0x18/0x2c [ 158.364407] regmap_write+0x3c/0x78 [ 158.364409] rockchip_pd_power+0xf8/0x5e8 [ 158.364414] rockchip_pd_power_on+0x14/0x20 [ 158.364417] _genpd_power_on+0x94/0x188 [ 158.364418] genpd_power_on.part.0+0xa4/0x1ac [ 158.364421] __genpd_dev_pm_attach+0x144/0x2dc [ 158.364423] genpd_dev_pm_attach+0x60/0x70 [ 158.364425] dev_pm_domain_attach+0x20/0x34 [ 158.364429] platform_probe+0x50/0xdc [ 158.364431] really_probe+0xc0/0x38c [ 158.364434] __driver_probe_device+0x7c/0x15c [ 158.364437] driver_probe_device+0x40/0x114 [ 158.364440] __driver_attach+0xf4/0x1fc [ 158.364443] bus_for_each_dev+0x74/0xd4 [ 158.364445] driver_attach+0x24/0x30 [ 158.364448] bus_add_driver+0x110/0x234 [ 158.364451] driver_register+0x60/0x128 [ 158.364453] __platform_driver_register+0x24/0x30 [ 158.364455] panthor_init+0x64/0x1000 [panthor] [ 158.364467] do_one_initcall+0x44/0x2a8 [ 158.364470] do_init_module+0x58/0x20c [ 158.364472] load_module+0x1e4c/0x1f3c [ 158.364474] init_module_from_file+0x84/0xc4 [ 158.364476] __arm64_sys_finit_module+0x1f4/0x2f0 [ 158.364478] invoke_syscall+0x48/0x110 [ 158.364481] el0_svc_common.constprop.0+0xc8/0xe8 [ 158.364484] do_el0_svc+0x20/0x2c [ 158.364487] el0_svc+0x30/0xfc [ 158.364488] el0t_64_sync_handler+0x13c/0x158 [ 158.364491] el0t_64_sync+0x190/0x194 [ 158.364492] SMP: stopping secondary CPUs [ 158.364557] Kernel Offset: 0x480d4dc00000 from 0xffff800080000000 [ 158.364558] PHYS_OFFSET: 0xffff8ef600000000 [ 158.364559] CPU features: 0x1c,00000017,00280928,4200720b [ 158.364561] Memory Limit: none [ 158.393407] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]---Power brick is a solid 5V/4A and as I said works OK with the stock OS (7zip benchmark and all) and Armbian Minimal
Any suggestion?
Thanks a lot
Fernando
-
Ok, setting 1.8/2.4 is still OK and completes the test, but real clockspeed is 2276 MHz. That's OK since my A76 pvtm-volt-sel is 5 not 7 (max silicon quality).
Geekbench scores are satisfying https://browser.geekbench.com/v5/cpu/21182824
Issue closed I'd say.
-
Switched to 150balbes' "Lunar" image (kernel 6.2.0 rc1) and now I can successfully complete Geekbench 5.5.1 @ 1.8 A55 / 2.2 A76
Scores are better as well: https://browser.geekbench.com/v5/cpu/21182173 , expecially considering 2.2 GHz (true speed = 2.246 GHz according to "mhz")
-
Many people run GB without issues @2.4, was wondering where to look for, since mine cannot run over 2.0 which is quite a difference.
-
Hello,
I am running Armbian 23.05 "minimal" (with the provided kernel 5.10.110) on my OrangePI 5 4GB. Upgraded all packets to latest.
When trying to run GeekBench 5.5.1 ARM Preview, it reboots when approaching the end of multicore tests, with "performance" governor and default speed range (0.4 - 2.4 GHz for A76).
Same goes if I drop the max clock speed to 2.2 for A76.
After dropping to 2.0 GHz max, it runs fine; but this hurts performances quite a bit.
I tried various power sources, including a bench PSU which can reliably supply up to 30A (but I only see a few spikes over 2A).
The board has a large heatsink installed with thin 3M thermal pad; temperatures stay under 54 C under full load.
I suspected a bad silicon, but it does not look bad, should ad least reach 2.2 GHz:
root@orangepi5:~# dmesg | grep pvtm [ 6.624098] rockchip-pvtm fda40000.pvtm: pvtm@0 probed [ 6.624154] rockchip-pvtm fda50000.pvtm: pvtm@1 probed [ 6.624207] rockchip-pvtm fda60000.pvtm: pvtm@2 probed [ 6.624270] rockchip-pvtm fdaf0000.pvtm: pvtm@3 probed [ 6.624321] rockchip-pvtm fdb30000.pvtm: pvtm@4 probed [ 7.352652] cpu cpu0: pvtm=1487 [ 7.352872] cpu cpu0: pvtm-volt-sel=4 [ 7.362528] cpu cpu4: pvtm=1723 [ 7.366667] cpu cpu4: pvtm-volt-sel=5 [ 7.376888] cpu cpu6: pvtm=1731 [ 7.381119] cpu cpu6: pvtm-volt-sel=5 [ 7.561843] mali fb000000.gpu: pvtm=881 [ 7.563822] mali fb000000.gpu: pvtm-volt-sel=3 [ 7.612340] RKNPU fdab0000.npu: pvtm=896 [ 7.617305] RKNPU fdab0000.npu: pvtm-volt-sel=4Any suggestion?
Thanks!
-
Necroposting, I know, but just in case someone else googles up this thread as I did.
The MPI3508 3.5" screen is cheap and sold a ton apparently.
So the problem is, the display is actually 480x320 but identifies itself as 1024x768 (!), which is not correct as size and not even as aspect ratio (4:3 vs. actual 3:2)
Trying to force 480x320 in armbianEnv.txt does not work, the display shows nothing; probably there are no proper timings in the kernel/DTB/whatever for such low an HDMI resolution.
So the trick is using 720x480, which is 1.5x the actual resolution. The aspect ratio is correct, the timings are there, and after all it's even quite readable.
So in /boot/armbianEnv.txt add:
extraargs=video=HDMI-A-1:720x480@60
disp_mode=720x480and then recompile boot.scr:
mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr
Display should run fine.
fbset reports:
mode "720x480"
geometry 720 480 720 480 32
timings 0 0 0 0 0 0 0
accel true
rgba 8/16,8/8,8/0,0/0
endmodewhich may be added to /etc/fb.modes
Hope this helps, despite not being optimal.
-
On 8/29/2021 at 3:55 PM, kprasadvnsi said:
Armbian desktop running on Orange Pi Zero2 with kernel 5.13
Nice!!
Is it stock Armbian, or did you have to patch something/rebuild kernel/rebuild uboot / etc?
-
I would test it gladly.
Is it OK to install it on an Armbian Unstable? It's what I have now.
If you advice against it, no problem, will reinstall.
-
You may try with the latest Unstable kernel (based upon 5.11.x), but I don't think WiFi works even with that one.
-
On 4/30/2021 at 1:54 PM, lampra said:
If @hexdump could provide headers for his kernel, then we could have the edge image with his kernel and support for usb, reboot and onewire until proper support is enabled.
I think hexdump added some DTS patches to:
https://github.com/jernejsk/linux-1/tree/h616-hdmi
Me, I was unable to "integrate" that kernel into mainline. But I'm a newbie.
-
I think he was referring to Armbian, which does not reboot even with genuine Sandisk cards.
I seem to remember that at a certain point, amid various kernel reconfig/rebuilds, I had it rebooting properly by disabling "Enable suspend to disk" and disabling "Enable hibernate" in kernel Power Management section. But I'm not 100% sure.
-
Confirmed.
At some point, rebuilding the latest mainline kernel from the Unstable branch, I managed to have the board rebooting properly; but it was in the middle of many tests and never managed to succeed again.
-
Indeed.
For example, my Rock64 and my Neo3 are stable at 1.3 GHz with -25mV and -50mV respectively vs. default OPP values. Silicon lottery.
It's still strange that H6 DTS lacks a proper OPP. Maybe with Unstable kernel, based upon 5.11 mainline? Some patches for H6 were included in 5.11 and accompaining DTS.
-
-
Maybe my problem is a bit different then.
My Rock64 (with both Armbian Stable and Unstable) does not reboot after "sudo poweroff": it performs the shutdown sequence, but does not really "power off". It is halted, does not respond to login or ping, but the peripherals are still powered and the board still draws the typical idle current (about 220 mA); the heatsink stays warm too.
-
This sounds like good news!!
Maybe poor little H616 is going to get some love by mainline kernel? Fingers crossed!!
Arm updates in Linux 5.12
Removal of several obsolete 32-bit Arm platforms – efm32, picoxcell, prima2, tango, u300, zx, and c6x, as well as associated device drivers.
Allwinner
Allwinner H616 and H616-R – Initial support including pin controllers, clocks
Allwinner/sunxi power management
Various DTS changes
...
-
@firewire10000
Hi, I can confirm this behaviour, both with the Stable image (kernel 5.10.21) and with the latest Unstable from yesterday (kernel 5.11.15).
Unfortunately I don't know how to fix it.
I tried rebuliding the kernel from the latest "Edge", with CPU Power Management enabled, but nothing changed.
The Rock64 is not supported by Armbian, so if powerdown is important to you, I would advice sticking with Ayufan images.
-
Ok, so let's see the steps I followed.
1. Installed Armbian Unstable for OrangePi Zero2:
2. Forced ethernet at 100 mbit/s, otherwise it did not work: added in /etc/rc.local
ethtool -s eth0 speed 100 duplex full autoneg off
3. Downloaded hexdump's precompiled kernel (derived from jernej's 5.11.0rc1 kernel):
4. Extracted the various parts and fixed the symlinks:
Image -> Image-5.11.0-rc1-stb-616+
uInitrd -> uInitrd-5.11.0-rc1-stb-616+
dtb -> dtb-5.11.0-rc1-stb-616+
5. Inside dtb-5.11.0-rc1-stb-616+, created a new folder "allwinner" and moved the 3 .dtb there; otherwise, initramfs would not find them
6. Rebooted. Voilà, we now have a working mainline-ish kernel (patched 5.11.0rc1) with USB support!
[ 57.289791] usb 2-1: new high-speed USB device number 2 using ehci-platform [ 57.454110] usb-storage 2-1:1.0: USB Mass Storage device detected [ 57.454976] scsi host0: usb-storage 2-1:1.0 [ 59.122397] scsi 0:0:0:0: Direct-Access Lexar USB Flash Drive 1100 PQ: 0 ANSI: 6 [ 59.124408] sd 0:0:0:0: [sda] 125038592 512-byte logical blocks: (64.0 GB/59.6 GiB) [ 59.125522] sd 0:0:0:0: [sda] Write Protect is off [ 59.125549] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00 [ 59.126563] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 59.163290] sda: sda1 sda2 [ 59.168389] sd 0:0:0:0: [sda] Attached SCSI removable disk -
Partial success.
I was able to boot @hexdump 's precompiled kernel (using Armbian "unstable" image).
This kernel indeed has USB working!
I am not able to rebuild this kernel by myself, but at least we have a mainline-ish kernel with working USB!More details later, have to go now.
-
Not the same results.. maybe different revisions?
and my OrangePiZero2 never got past 61 degrees, and that's without an heatsink.
I added a tiny heatsink, and it stayed below 52 degrees even after repeating 7zr benchmarks
-
13 minutes ago, NicoD said:
@XFer012Do you need HDMI? Otherwise the RockPiS is way more power efficient. Runs at 0.1A idle
I have the RockPiS, too; quite nice, but very difficult to find here (Italy) and it's quite slower. Power efficiency is not much higher, by the way.
In absolute terms, using "7zr b" as benchmark, RockPi-S gives 2327, OrangePiZero2 3739 (1.6x)
Using "7zr b" MIPS / MHz as an IPC figure, the RockPi-S gives 1.78, while the OPIzero2 gives 2.54.
Using "7zr b" MIPS / W as an efficiency figure, RockPi-S gives 1450, OPIZero2 1246
Also, microSD speed is almost 2x on the OPI02.
A very nice board (at 20 Eur!), if only we could iron out USB support.
-
The board is very good. IMHO, one of the best out there! And I have so many SBCs... maybe 10 or more.
Let me summarize:
Small and cheap
Draws little power, thanks to the 28nm SOC
Does not run hot, at all, not even with the (quite bad) Orange kernel (which loads one core at 100% all the time), not even at 1.5 GHz
Has onboard audio
MicroSD is quite fast, among the fastest actually
I see it as the best SBC for battery-powered projects, or whenever heat dissipation is an issue
Orange PI 5 Armbian 25.8.2 Ubuntu Server 24.04/6.12 does not boot (kernel panic)
in Orange Pi 5
Posted
I expect 2x the figure:
dmesg | grep PCIe pci 0004:41:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x1 link at 0004:40:00.0 (capable of 15.752 Gb/s with 8.0 GT/s PCIe x2 link)lspci -vv | grep LnkSta LnkSta: Speed 5GT/s (downgraded), Width x1 (downgraded)