Hyperion Entertainment Message Boards

musa wrote: Wed Jun 26, 2024 3:43 pm hi
I try to boot vmlinux-6.10_rc5 on a new fienix on sdb6 (Harddisk 2 )
Kernel panic

Could you please post a picture? The kernel has detected sdb1 and sdb2 in your last screenshot.

Hi
here is a screnshot . try to boot on sdb6 with 6.10:rc5

Thank you for the screenshot.

The kernel only see sdb1 and sdb2. I will test it on my X1000 at the weekend.

xeno74 wrote: Thu Jun 27, 2024 5:30 am Thank you very much for testing! Strange your test with vmlinux-6.10-10 is good and Musa reported a kernel panic.

I removed and reinstalled kernel to test again. I was able to boot. But after trying again I had a kernel panic. I had a USB stick in my keyboard so decided to pull it out so the sd assignment isn't messed up. Root is set to direct device.

I did some more investigating into the lighdm issue. I wonder if this has caused a dependence somehow? I noted that lighdm had an issue because plymouth quit service hadn't ended. But plymouth wasn't installed. Yet, when using kernel 6.9.0 it boots fine. Could these kernels be incompatible with Fienix? In the same kind of way the are incompatible with Xenial and break boot?

So I tried to install plymouth. It ended up in a dpkg error because it kept triggering mkinitramfs. I removed the linux image package that was somehow installed that was triggering it to fix it. Then wanted to reinstall lightdm. But I couldn't because it couldn't be downloaded. I don't know how but my Fienix repos are broken again. Well not broken really but incomplete. I don't have all sources to normally install software.

I have modified a little bit the kernel config. Could you please test the RC5 with the modifed kernel config?

Okay I have tested it. It doesn't panic. But it does stop. The cursor sits there looking at me. Might need to take screen shots myself soon. However, I noticed for whatever reason I put a "debug=" line in my bootargs. I booted it with a ramdisk.

musa wrote: Wed Jun 26, 2024 3:43 pm hi
I try to boot vmlinux-6.10_rc5 on a new fienix on sdb6 (Harddisk 2 )
Kernel panic

These issues look familiar. Though the kernel panics it hasn't crashed yet at that point so still technically works. I suggest you attempt to boot with a ramdisk and specify uuid to be unambiguous to the kernel.

I started using a ramdisk as I saw this issue of sda and sdc being mixed up on both my A1 and my X1000. Somehow it was more common on my system than on other peoples and in the past people would dispute my devices being reordered. But it can happen. Sometimes it seems to happen at random while other times a usb stick inserted can trigger it.

xeno74 wrote: Thu Jun 27, 2024 5:30 am The kernel only see sdb1 and sdb2. I will test it on my X1000 at the weekend.

These ata sata errors are very close to what I see. Almost exact. Reminded me how I should give layout of my drives:
HDD: 1TB, RDB, mixed, Amiga and Linux.
SSD: 500GB, RDB, Linux only.
BRD: Bluray reader
BRD: Bluray writer

Need to check what ports drives are in.

Maybe the SCSI fixes after the RC2 are responsible for the issue.

Link: SCSI fixes

git checkout 83a7eefedc9b56fe7bfeff13b6c7356688ffa670

git revert 8a92980606e3585d72d510a03b59906e96755b8a -m 1

hi
The last screenshot I uploaded was vmlinux-6.10_rc5 with fienix on sdb6.
I forgot to mention that the kernel was on a USB disk with 2 partitions. The kernel was located on partition1.
This screenshot is vmlinux-6.10_rc5 with fienix on sdb6. Here the kernel is located at cf0. There is no usb disk in the machine
Notice that only sda is found on the new screen.

xeno74 wrote: Thu Jun 27, 2024 9:39 am Maybe the SCSI fixes after the RC2 are responsible for the issue.

Link: SCSI fixes

git checkout 83a7eefedc9b56fe7bfeff13b6c7356688ffa670

git revert 8a92980606e3585d72d510a03b59906e96755b8a -m 1

I compiled the RC3 without the SCSI fixes.

Download: vmlinux-6.10-14

Please test.

Thanks

I retested vmlinux-6.10-10 again. Twice. Got a kernel panic.

I then tested vmlinux-6.10-14. Acted exactly the same. Has trouble with sata.

Also the 5.10.288 LTS kernel has issues. It cannot reset. When it resets machine it just sits there.