Werner

[182764.941115] Bad mode in undefined instruction handler detected [182764.952552] Internal error: Oops - bad mode: 0 [#1] SMP THUMB2 [182764.963861] Modules linked in: rfkill input_leds snd_soc_hdmi_codec sun4i_gpadc_iio industrialio sun8i_thermal sun8i_ce sunxi_cedrus(C) crypto_engine sun8i_di evdev uio_pdrv_genirq uio cpufreq_dt zram ip_tables x_tables autofs4 lima gpu_sched dw_hdmi_i2s_audio dw_hdmi_cec sunxi phy_generic gpio_keys display_connector [182765.004106] CPU: 2 PID: 1 Comm: systemd Tainted: G C 5.7.10-sunxi #trunk [182765.018311] Hardware name: Allwinner sun8i Family [182765.028826] PC is at 0xffff10ca [182765.037366] LR is at 0xb6e87be6 [182765.045482] pc : [<ffff10ca>] lr : [<b6e87be6>] psr: 800701b7 [182765.056862] sp : d70dffb0 ip : b6f67ba0 fp : 00008000 [182765.067193] r10: 00000068 r9 : 00000001 r8 : 00000008 [182765.077505] r7 : 01b72dd0 r6 : b6f6776c r5 : b6f677a0 r4 : 01b72dd0 [182765.089159] r3 : b6f67808 r2 : 01ae9248 r1 : 00000071 r0 : c0ff880c [182765.100871] Flags: Nzcv IRQs off FIQs on Mode ABT_32 ISA Thumb Segment none [182765.113591] Control: 50c5387d Table: 568d406a DAC: 00000000 [182765.124711] Process systemd (pid: 1, stack limit = 0x33bc84e2) [182765.135980] Stack: (0xd70dffb0 to 0xd70e0000) [182765.145799] ffa0: c0ff880c 00000071 01ae9248 b6f67808 [182765.159593] ffc0: 01b72dd0 b6f677a0 b6f6776c 01b72dd0 00000008 00000001 00000068 00008000 [182765.173468] ffe0: b6f67ba0 d70dffb0 b6e87be6 ffff10ca 800701b7 ffffffff 00000000 00000000 [182765.187425] Code: f850 e02e 4668 efca (f8f0) efee [182765.198035] ---[ end trace 2a7b257dd76743ba ]--- [182765.208522] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b [182766.252010] SMP: failed to stop secondary CPUs [182766.262576] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]--- I think I stop tinkering with this one. He's dead, Jim.

The OPi4 is built around the RK3399 SoC which is known to perform best on kernel 4.4.x in desktop applications. So if you plan to build a desktop around that board you should stick with the legacy branch.

I've create an issue on jira regarding the zram thingy. Whoever wants to take a shot at it... https://armbian.atlassian.net/browse/AR-382

Maybe I have overlooked those. Can you provide those in high resolution (>4k) and with transparent background?

reserved

You asked for it, here it is: The official Armbian SWAG store http://swag.armbian.com (small selection, there is more!) Earlier you could write Armbian to an SD card only, now you can even wear it. Awesome, right? Comes even with a free hug if I catch somebody wearing it (and the pandemic is over) . The best part: a small cut of every sale goes straight to Armbian and will be invested into infrastrucuture, testing equipment and of course new boards (if a parsimonious vendor does not want to provide free samples to the lap ). You can grab your favorite merchandise and support the project at the same time! Note: The US and EU product variety are slightly different since even though the look the same both companies are independent. Special thanks goes to our awesome community which provided many of the used designs. We could not have done it without you! If you do have any question please raise them below. Thanks for stopping by and happy shopping! PS: If you are curious how the stuff looks in reality I recommend to check out @armbian on Twitter (and follow ): https://twitter.com/armbian

Wrong board. Panfrost is not for Mali400 GPU.

Does not work very well atm. Just tried with Bullseye on an OrangePi One. Chromium does not render any website at all (error code 256) and Firefox crashes when calling about:support....

If you have an NVMe installed anyways you should put the swap there since it is way faster than an eMMC. Or investigate if there is a memory leak.

Was broken in 5.7 too but has been fixed. Was due to missing dts entries. If it is broken in 5.8 again it is most likely for the same reason.

So.... ¯\_(ツ)_/¯

Hm seems an issue with sunxi. Working normally on sunxi64. Sources are the same...

Well nightlies can be broken at any time...tried to switch back to stable?

armbianmonitor -u

https://docs.armbian.com/#what-is-supported

This may fix it: https://github.com/armbian/build/pull/2108

Interesting. This needs to be investigated. https://armbian.atlassian.net/browse/AR-340

Once again in this particular case defining a specific branch won't work since sunxi relying on 3rd party sources. In your particular case here: https://github.com/megous/linux/tree/orange-pi-5.4 You can find these also when you start digging through the configs for your boards and their matching board families. Back to the sources: Megi does not add tags and also maintains a kernel version only to a certain level and mostly works on the newest available sources. It is up to us as we use these sources to keep them halfway up to date if possible and we do that using our patches. The location you can find in my previous post. There is no general way to get specific kernel versions for every single board. The wide variety of boards makes that impossible.

The only thing that catched my attention by digging through the logs is that at the first boot wifi was there as wlan0. Also firmware was loaded: [ 7.465721] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4356/2 wl0: May 14 2014 19:51:52 version 7.35.17 (r477908) FWID 01-2ed3ee81 That particular line is missing in all the other boot logs where wlan0 is missing too. So maybe the firmware is missing. Check if the armbian-firmware-full (was it I think) package is installed and maybe do a reinstall.

Do you have an armbianmonitor -u output for us? Did you modify the device tree?

I don't know. Maybe, maybe not. I neither have this board nor access to a similar one to test atm. Dealing with SBCs often is try'n'error. That is the usual business....

As far from what I see it is not software rendered. That would be LLVM. What you can try is to install mesa from scratch or use oibaf ppa (I had more success on H6 with 1st method though) to get more up to date mesa binaries and/or install a more recent kernel. You can compile a 5.7 kernel package for sunxi64 using the build script: github.com/armbian/build/ or check nightly builds for trunk kernel packages.

Should be possible. I want to mention two things here: First: https://docs.armbian.com/Developer-Guide_User-Configurations/#user-provided-image-customization-script This allows do add customizations to an image right before it is being packed into an img file. And 2nd have a look at:

Enjoy yourself

That could be an issue. This kind of upgrade is neither tested nor supported. If you have a chance try with a fresh image. And always handy to have: armbianmonitor -u