New kernels

[xeno74]

hej
5.18.alfa2 working with debian 64

I test again tomorrow

Great! Many thanks for testing!

[musa]

Hi Christian
I have testet kernel 5.18.alfa2

Ubuntu 16.04 No boot sdc1
Fienix 5 Boot sdc2
Remix 17 no boot sdc3
Debian 64 Boot sdc4
Mint 32 boot sdc5
Fedora no boot sdc6
Void no boot sdc7

Its the new generation there boot
I will try to find the last LTS kernel there boots all my Linux
Have a nice day
Peter

[xeno74]

Hi All,

Here is the third alpha of kernel 5.18 with the first PowerPC updates 5.18-1 for testing.

Download: linux-image-5.18-alpha3-X1000_X5000.tar.gz



Please test the kernels.

Thanks,
Christian

[musa]

Hi
I have tested 5.18.a3 with remix 17 which booted
Debian 64 bit which also booted
Ubuntu 16.04 which did not boot
last I tried Void which booted and then froze (do not think it was because of the kernel)
A good day to all
Peter
Here is Remix 17

[xeno74]

Hi
I have tested 5.18.a3 with remix 17 which booted
Debian 64 bit which also booted
Ubuntu 16.04 which did not boot
last I tried Void which booted and then froze (do not think it was because of the kernel)
A good day to all
Peter
Here is Remix 17

Hi Peter,

Thanks a lot for testing the alpha3!

Hi Christian.
I got Kernel panic on 5.18-alfa1 with Debian 64 bit. and Mint 32 bit
Have a nice day

Your boot results are very strange. First, Debian PPC64 doesn’t boot and then it boots.

Cheers,
Christian

[musa]

Your boot results are very strange. First, Debian PPC64 doesn’t boot and then it boots.

Cheers,
Christian

Hi Christian
yes Debian did not boot with alfa 1 but its boot with alfa 2 and 3
i have tried several times with the same result so it is not periodic. It is also strange that alpha 1 and 2 can't boot
remix but alpha 3 can boot remix
Sometimes I've noticed that things change if I switch to another usb disk, maybe I should try
Have a nice day
Peter

[xeno74]

Peter,

What do you think about booting with a label?

Depending on the number of USB drives available on your X1000 the block device name may change. It is better to use labels.

For example adding the label void to the partition /dev/sdc6::

Code: Select all

tune2fs -L void /dev/sdc6

Booting with a label:

1. Code: Select all

   CFE> setenv bootargs "root=LABEL=void rootdelay=5"

2. Code: Select all

   CFE> ramdisk -z -addr=0x24000000 -fatfs cf0:initrd-5.10.img

3. Code: Select all

   CFE> boot -elf -noints -fatfs -z cf0:zImage-5.18

Cheers,
Christian

[musa]

Hi Christian.
My experience with zimage is that it is a very slow boot compared to kernel boot.

I only use usbdisk as boot when I test a new kernel and there I only need to write 2 short lines.
Why is there a ramdisk involved in booting a partition?
If it means anything for a better test I might be persuaded but it does not give me any benefits I thought
Peter

[xeno74]

Hi Christian.
My experience with zimage is that it is a very slow boot compared to kernel boot.

I only use usbdisk as boot when I test a new kernel and there I only need to write 2 short lines.
Why is there a ramdisk involved in booting a partition?
If it means anything for a better test I might be persuaded but it does not give me any benefits I thought
Peter

Yes, you’re right. vmlinux loads faster than zImage from USB sticks but zImage loads faster from the internal CF card.
You need the ramdisk for booting with a label.

[musa]

ok i want to look at it.
where do i get the ram disks.
I suppose there is a difference from Void to Debian 64.
Thank you for your help