New kernels

[Skateman]

Kernel 6.18 RC3 up and running on my Mirari PPC system



Big picture https://www.skateman.nl/wp-content/uplo ... -33-47.png

Thank for showing off the Mirari with MintPPC at Amiga 40 !! I had a great time

[xeno74]

Kernel 6.18 RC3 up and running on my Mirari PPC system

Thanks a lot for testing!

Thank for showing off the Mirari with MintPPC at Amiga 40 !! I had a great time

I had a great time too. Thank you for your support and for your help.

[xeno74]

Hi All,

Here is the RC4 of kernel 6.18 for X1000 and e5500 machines (X5000/20, X5000/40, Mirari, and QEMU VMs).

Download and further information: github.com



Please test the kernels.

Thanks,
Christian

[xeno74]

I don't actually need initial ramdisks, but I have sometimes created ramdisks for others.

You can use the following commands to create a new ramdisk and boot from it:

Code: Select all

dracut initrd-6.12.img 6.12.48-powerpc64-smp

Code: Select all

mkimage -T ramdisk -C gzip -n 'Kernel 6.12 uInitrd' -d initrd-6.12.img uInitrd-6.12

-- Testing --

Code: Select all

# tune2fs -L MintPPC <Volume or partition>

Code: Select all

# reboot

Code: Select all

X5000> setenv bootargs root=LABEL=MintPPC

Code: Select all

X5000> load sata 1:1 1000000 uImage-6.12

Code: Select all

X5000> load sata 1:1 1c00000 cyrus-p5040.dtb

Code: Select all

X5000> load sata 1:1 2000000 uInitrd-6.12

Code: Select all

X5000> bootm 1000000 2000000 1c00000

I created a new uInitrd on MintPPC32 today.

Download: github.com

I was already able to check the contents of the uInitrd.-6.12 you made earlier with Void:

Code: Select all

dd if=uInitrd of=initrd skip=64 bs=1
zcat initrd | cpio -id

/media/NTFS/rd/usr/bin/e2fsck' -V
e2fsck 1.46.5 (30-Dec-2021)
Using EXT2FS Library version 1.46.2, 28-Feb-2021

So the e2fsck was indeed outdated and caused the boot problems! As void cannot be anymore updated, it is better to create the uInitrds with Mint.

Thanks a lot to Roland for reporting the issue with the old version of e2fsck in the old uInitrd.

I was able to boot MintPPC32 with a LABEL today.

[Roland]

I created a new uInitrd on MintPPC32 today

Download: github.com

Thanks, but it has the same issue as those I already tried to create on MintPPC. Desktop cannot be loaded (MintPPC25, up-to-date), and booting halts to the 'Debian login' prompt (disk is in read-only state). This issue is not anymore related to the e2fsck.

But yesterday I was able to create a working uInitrd (6.12.48) using Adelie! I used the same commands as you, and It seems to work with all distros.

[xeno74]

Thanks, but it has the same issue as those I already tried to create on MintPPC.

Strange. I successfully tested it with MintPPC32 (latest version) on my X5000/40 today.

BTW, I need the following commands for unpacking the new uInitrd-6.18.

1. Code: Select all

   dd if=uInitrd-6.18 of=initrd skip=64 bs=1

2. Code: Select all

   zstd -d initrd -o initrd_cpio

3. Code: Select all

   cpio -id < initrd _cpio

[Skateman]

Kernel 6.18 RC4 up and running on my Mirari Linux machine.



Big picture https://www.skateman.nl/wp-content/uplo ... 3-10-1.png

[xeno74]

Kernel 6.18 RC4 up and running on my Mirari Linux machine.

Nice screenshot. Thanks a lot for testing.

[Roland]

@Christian

I started suddenly to get to my personal email several messages concerning Linux kernel development (titled like "[PPC] Boot problems after the pci-v6.18-changes"). I have not myself subscibed any mailing list, though. Have you possibly put my name on your messsages as an additional recipient? You are the only person I recognized from the senders/recipients in those messages.

If that has happened, could you please take care that my address will be immediately removed? Thank you!

[xeno74]

@Christian

I started suddenly to get to my personal email several messages concerning Linux kernel development (titled like "[PPC] Boot problems after the pci-v6.18-changes"). I have not myself subscibed any mailing list, though. Have you possibly put my name on your messsages as an additional recipient?

No, I haven't. I don't know your email address. I think you have reported an issue in the past and a developer has added you to this thread.