kjhdfgkio

I'm not sure since I can't scroll up and I haven't been able to catch it as it is happening with a camera as I haven't found a specific trigger, but I've attached a picture of the not-very-useful end of it. I'm running the Plex server inside a docker container and it seems to be associated with Plex rescanning the media collection on a 2 hour timer, but I can't trigger it on manual rescans. There are no Plex clients trying to get media from this as I've just set it up on my desk to test the board out to see if it can replace my current Plex server.

I moved the eMMC install back to the legacy kernel. Any tips for collecting kernel panic dumps or auto-rebooting after a kernel panic? I set "kernel.panic=5" in /etc/sysctl.conf, but it seems to only reboot for about 1 in 5 kernel panics. For the other ones, everything has scrolled so far up that I can't get the details and the normal up arrows, or ctl+page up, keyboard sequences aren't scrolling. All the methods I know for getting kernel panic dumps require building the kernel on my own... I also tried installing the system watchdog service (apt install watchdog), but the /dev/watchdog device that exists in the Firefly linux image seems to be missing in this Armbian image. There are more details at https://wiki.t-firefly.com/en/ROC-RK3588S-PC/usage_watchdog.html

"Armbian_23.02.0-trunk_Station-m3_jammy_legacy_5.10.110.img.xz" from the 20230302 folder on a USB flash drive has a "not syncing" kernel panic during boot. The normal shift+pageup doesn't seem to work for scrolling back up to get stack info. "Armbian_23.02.0-trunk_Station-m3_jammy_legacy_5.10.110.img.xz" from the 20230302 folder on an SD card has the same "not syncing" kernel panic during boot. I tried the "Armbian_23.02.3_Station-m3_jammy_legacy_5.10.110.img.xz" image again from USB and got video this time (no changes, just worked this time?). It also landed at a "not syncing" kernel panic. When the stock bootloader was on the device I was able to boot the "Armbian_23.02.3_Station-m3_jammy_legacy_5.10.110.img.xz" image from SD and flash the device (eMMC bootloader/eMMC system), but after flashing the "Armbian_23.02.3_Station-m3_lunar_current_6.2.0.img.xz" image (eMMC bootloader, SSD system) the jammy images seem to panic during boot.

"Armbian_23.02.3_Station-m3_lunar_current_6.2.0.img.xz" Whatever Android came on the eMMC for the device that Firefly shipped to me last week. I didn't actually look at the Android build, I just immediately used RKDevTool to flash "ROC-RK3588S-PC_Ubuntu20.04-Gnome-r240_v1.0.6f_230404" to it. I've tried both a Dell U4021QW and a Phillips 272P7VUBNB/27. Both are just a direct HDMI cable from the RK's HDMI output port to the HDMI1 port on the monitor. I also tried a few different HDMI cables, some active, some passive. Again, works fine on USB boot from the "Armbian_23.02.3_Station-m3_lunar_current_6.2.0.img.xz" image, but not the "Armbian_23.02.3_Station-m3_jammy_legacy_5.10.110.img.xz" image. Understood. Any pointers to ways I can collect more information or kernel dumps to help the team troubleshoot these issues?

On the "Armbian_23.02.3_Station-m3_lunar_current_6.2.0.img.xz" image, I'm seeing a Kernel panic that seems somewhat random while reading/writing to the NVMe. Here are two examples of it (OCR'd from a photo of the panic ... pretty sure I double checked every character in it). station-m3 login: [ 659.401029] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b [ 659.401730] CPU: 5 PID: 1 Comm: systemd Tainted: G W 6.2.0-rc1-station-m3 #23.02.3 [ 659.402523] Hardware name: Firefly ROC-RK3588S-PC NVMe (DT) [ 659.403017] Call trace: [ 659.403236] dump_backtrace+0xdc/0x130 [ 659.403577] show_stack+0x18/0x30 [ 659.403874] dump_stack_lvl+0x64/0x80 [ 659.404204] dump_stack+0x18/0x34 [ 659.404502] panic+0x180/0x330 [ 659.404776] make_task_dead+0x0/0x16c [ 659.405104] do_group_exit+0x34/0x90 [ 659.405423] get_signal+0x830/0x894 [ 659.405734] do_notify_resume+0x2d0/0x1310 [ 659.406101] el0_svc+0xa4/0xb4 [ 659.406375] el0t_64_sync_handler+0xf4/0x120 [ 659.406754] elot_64_sync+0x1a0/0x1a4 [ 659.407081] SMP: stopping secondary CPUs [ 659.407496] Kernel Offset: disabled [ 659.407806] CPU features: 0x60000,000e0148,cc00720b [ 659.408239] Memory Limit: none [ 659.414666]---[ end Kernel panic- not syncing: Attempted to kill init! exitcode=0x0000000b ]--- station-m3 login: [ 1298.038509] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b [ 1298.039211] CPU: 7 PID: 1 Comm: systemd Tainted: G W 6.2.0-rc1-station-m3 #23.02.3 [ 1298.040004] Hardware name: Firefly ROC-RK3588S-PC NVMe (DT) [ 1298.040498] Call trace: [ 1298.040718] dump_backtrace+0xdc/0x130 [ 1298.041060] show_stack+0x18/0x30 [ 1298.041358] dump_stack_lvl+0x64/0x80 [ 1298.041688] dump_stack+0x18/0x34 [ 1298.041986] panic+0x180/0x330 [ 1298.042260] make_task_dead+0x0/0x16c [ 1298.042587] do_group_exit+0x34/0x90 [ 1298.042906] get_signal+0x830/0x894 [ 1298.043217] do_notify_resume+0x2d0/0x1310 [ 1298.043583] el0_undef+0xf0/0xf4 [ 1298.043871] el0t_64_sync_handler+0xa0/0x120 [ 1298.044251] el0t_64_sync+0x1a0/0x1a4 [ 1298.044578] SMP: stopping secondary CPUs [ 1298.044930] Kernel Offset: disabled [ 1298.045239) CPU features: 0x60000,000e0148, cc00720b [ 1298.045671] Memory Limit: none [ 1298.052109] ---[ end Kernel panic- not syncing: Attempted to kill init! exitcode=0x0000000b ]--- I had another one that was a paging issue during a find_inode_fast call, but it seems to have been fixed by changing mergerfs to have "cache.files=off" rather than "cache.files=full" or "partial", so I'm assuming mergerfs just isn't fully 6.2.0 compatible yet.

ROC-RK3588-PC running Firefly provided "ROC-RK3588S-PC_Ubuntu20.04-Gnome-r240_v1.0.6f_230404" image (which had been written over USB using RKDevTool 2.96 from a Windows 11 machine) Used Raspberry Pi Imager to write the provided image to an SDHC card on a Windows 11 machine Inserted SDHC card into the SBC's card slot Powered on the SBC It booted to Armbian Ran "lsblk", noticed there was no NVMe Edited "/boot/extlinux/extlinux.conf" to set the fdt file to "/boot/dtb/rockchip/rk3588s-roc-pc-nvme.dtb" (just added "-nvme" before ".dtb") Ran "reboot" Booted from Armbian again Ran "lsblk", was happy to see the "nvme0n1" drive - but noticed no partitions Ran "fdisk /dev/nvme0n1" - typed "n" for a new partition, took defaults, typed "w" to write and quit Typed 'armbian-install' Selected "Boot from eMMC - system on SATA, USB or NCMe" - answered "Y" to both prompts warning it would overwrite "mmcblk0p1" and "nvme0n1p1" Rebooted at the end Ran "mount" and was happy to see "/dev/nvme0n1p1 on /" and "/dev/mmcblk0p1 on /boot" Removed the SDHC card, tried power cycling a few more times, all seemed good The "Armbian_23.02.3_Station-m3_jammy_legacy_5.10.110.img.xz" image on a USB flash drive seems to boot, as it gets to a point where the fan slows down and the post-boot blue LED just above the SD slot lights up, but there is no network or HDMI, so I can't do anything with it. The "Armbian_23.02.3_Station-m3_lunar_current_6.2.0.img.xz" image on a USB flash drive booted, and took me to the initial "Create root password" prompt. HDMI and networking worked great. Thanks for the pointer here. USB flash drives are substantially faster than the SDHC cards, so this is a much better way to go. Works great, thank you! Got it, thanks!

It was a me issue... updating /boot/extlinux/extlinux.conf to point to "rk3588s-roc-pc-nvme.dtb" instead of "rk3588s-roc-pc.dtb" got the NVMe going. For the Armbian_23.02.3_Station-m3_lunar_current_6.2.0.img.xz image, the blue post-boot LED never comes on and the fan is always full speed. I saw the prior note about replacing the "/usr/bin/firefly-fan-control" file, but it looks like the image is completely missing the firefly-fan-control file to start with. Running firefly-fan-control is verbose mode gets: set_PWM: 59000 pwm: 50 pwm: 50 no such file /tmp/fan_temperature no such file /tmp/fan_temperature no such file /tmp/fan_temperature set_PWM: 59000 pwm: 50 SetValue: 53000.000000 ActualValue: 50000.000000 PID->Ek: 3000.000000 PID->LocSum: 3000.000000 PIDLoc: -4584.000000 pwm:50.000198 count is 0 fan_switch is 1 PID_fan_func exit set_PWM: 59000 pwm: 50 SetValue: 53000.000000 ActualValue: 50000.000000 PID->Ek: 3000.000000 PID->LocSum: 3000.000000 PIDLoc: -7584.000000 pwm:50.000198 So, it seems the -current build is missing some stuff for fan control. The other issue I have is that now that I've installed armbian on the eMMC, I can't seem to get this ROC-RK3588-PC to boot from the SDCard again. During boot I only get the Armbian logo image, and no amount of hitting space-bar gets me into to the uboot cli.

This is fantastic! It's the first Armbian I was able to get to boot on the ROC-RK3588S-PC board, which seems to be nearly identical to the board inside the M3. The only issue I have is that it doesn't seem to recognize the NVMe drive, or perhaps I'm just doing something wrong. Any tips for troubleshooting the NVMe? I'm using this image from the "20230330-legacy" folder: Armbian_23.02.3_Station-m3_jammy_legacy_5.10.110.img armbianmonitor logs at: https://paste.armbian.com/uyiwocajac I also tried this image from the "20230330-current" folder: Armbian_23.02.3_Station-m3_lunar_current_6.2.0.img.xz Which booted fine, but seems to have no fancontrol, and also no NVMe. Logs for Lunar are at https://paste.armbian.com/catoxosije The NVMe drive I'm using is the SABRENT 2TB Rocket NVMe PCIe M.2 2242 (SB-1342-2TB): https://www.amazon.com/dp/B07XVRTG1H