Hyperion Entertainment Message Boards

musa wrote: Sat May 31, 2025 11:23 am Hello
I have tested vmlinux-6.16_alpha3.
I have formatted a usb disk and then copied vmlinux-6.16_alpha2 and vmlinux-6.16_alpha3 to the disk.
Then checked the file system on the disk for errors ( result : no errors) .
I have then tested several systems e.g. Ubuntu 18 .mintppc 64 ,mintppc 32 , Debian 64 , Debian 32 , Chimera 32 . Alpha2 boot on all system , Alpha3 got kernel panic on all system. (cant mount root system)
Sorry but I skip Alpha3 and hope it goes better with alpha4.
Have a nice day

OK, good to know. Thank you for testing. Could you please test the following package?

linux-image-6.16.0-alpha3-2-X1000.tar.gz

Unbelievable. By the time I had the final 6.15 installed a 6.16 alpha was already out and then suddenly it was three alphas!

Well 6.15 full is working well on my Xenial. I tested 6.16 a1 on Debian and it works well for an alpha. I then intended to test 6.16 a2 on my MATE install but it broke.

Unfortunately, the ramdisk I had built from Debian is oversized and bloated out, so it just dropped back to CFE. It was 13GB which is way too big as well as being way big. This is most disappointing, especially since having updated my manager recently, which should make it easy to generate a ramdisk. I already put in safeguards to prevent bloating years ago but Debian has put in firmware and all this other junk that is simply not needed and messed it all up! I've found mkinitramfs is too limiting in this regard. You can add hooks with your own custom configuration but I know no way of telling it to use just a basic layout or filter out the hooks. You can only add hooks that need to hack around and remove stuff. Not the best design.

Please test
linux-image-6.16.0-alpha3-2-X1000.tar.gz


Thanks

Hi
Test vmlinux-6.16_alpha3-2
First try with vmlinux-6.16_alpha2 = ok
Next try withvmlinux-6.16_alpha3-2 = Kernel panic.

Here the output in 2 foto

foto:1


Foto 2:

Musa,

interesting! Thanks for posting the pictures.

There are hardware errors with the SATA (SSD etc) drives ata1, ata2, ata3, and ata4. (failed to IDENTIFY and I/O error)

Sorry, I can’t fix them because I can’t bisect currently.

Hypex, could you please help me to fix this issue?

Cheers,
Christian

xeno74 wrote: Sun Jun 01, 2025 12:09 pm
Hypex, could you please help me to fix this issue?

Cheers,
Christian

Sure, I'll do some more testing. Somehow, my Debian is the only install that boots without ramdisk, so just as well I installed it. My "Fast Fienix" was like that but it's broken so disabled it in my menu.

I'll test with and without ramdisk.

Now, as to the issues on screen, this is exactly what happens to me when I start having SATA drive errors. In particular, my Linux SSD drive, which suddenly developed these problems out of the blue. Unless it really is a kernel ATA code fault, I'd suggest to musa to check the cables and to even re jig the SATA cables, pulling them out and plugging back in.

Hypex,

do you have the same issues with the alpha3?

Thanks,
Christian

Unfortunately, I have not found a commit that has anything to do with our ATA problems in the alpha 3 period.

xeno74 wrote: Sun Jun 01, 2025 4:29 pm Hypex,

do you have the same issues with the alpha3?

Okay so I've just tested the alpha 2, 3, and 3 patched. On Zesty remix. All up to and including 3 boot fine on my Zesty system. Which is using a ramdisk. Apparently I had just installed alpha 3 last after remaking ramdisk. I booted from a stripped vmlinux. Using my boot loader. I didn't see any SATA issues or any other major issues in the log for once.

Hypex wrote: Sun Jun 01, 2025 6:48 pm I didn't see any SATA issues or any other major issues in the log for once.

Code: Select all

amigaone@ubuntu:~$ uname -a
Linux ubuntu 6.16.0-a3-powerpc64-smp #1 SMP Sat May 31 16:31:03 CEST 2025 ppc64 ppc64 ppc64 GNU/Linux

I am irritated. I haven’t found any sata changes for the alpha3 and it works on your X1000.
Why does Musa's X1000 have problems with the alpha3 and not with the alpha2?

Thank you for testing the alpha3.