Page 6 of 9
Re: Kernel 5.14
Posted: Mon Aug 02, 2021 3:39 pm
by Skateman
Kernel 5.14 RC3 and latest Interweb browser up and running fine on my AmigaOne X5000
Big picture
http://www.skateman.nl/wp-content/uploa ... 152032.png
Re: Kernel 5.14
Posted: Mon Aug 02, 2021 8:15 pm
by xeno74
Skateman wrote: Mon Aug 02, 2021 3:39 pm
Kernel 5.14 RC3 and latest Interweb browser up and running fine on my AmigaOne X5000
Hi Skateman,
Thanks a lot for testing the RC3 and for testing the new InterWeb browser.
Cheers,
Christian
Re: Kernel 5.14
Posted: Thu Aug 05, 2021 5:14 pm
by xeno74
Hi All,
I released the
RC4 of kernel
5.14 for the X1000 and X5000 today.
New:
Download:
linux-image-5.14-rc4-X1000_X5000.tar.gz
Please test the kernels.
Thanks,
Christian
Re: Kernel 5.14
Posted: Thu Aug 05, 2021 10:29 pm
by kilaueabart
Not much of a test, but I can report that RC4 boots to Fienix
rc4.png
Re: Kernel 5.14
Posted: Fri Aug 06, 2021 7:53 am
by xeno74
kilaueabart wrote: Thu Aug 05, 2021 10:29 pm
Not much of a test, but I can report that RC4 boots to Fienix
Thanks for testing!
Re: Kernel 5.14
Posted: Sun Aug 08, 2021 9:14 am
by acefnq
I finally have my Linux systems up and running again on various partitions. In the past I tested new kernel versions by simply replacing the new version number in the bootargs and off course placing the .dtb, kernel and modules in the correct places. When doing this in the past I used a uRamdisk image which let do this no problems. Now if I use a uRamdisk or uInitrd images I seem to be locked to the kernel version on my system (at this time 5.7). If I try to boot pointing to a new kernel the boot simply fails. I have tried to read up on initrd and get the concept but I don't understand how you can make a new initrd image of the new kernel is not already loaded on the system?
How is everyone else booting their systems with Christian's new kernel images?
ace
Re: Kernel 5.14
Posted: Sun Aug 08, 2021 10:31 am
by Roland
acefnq wrote: Sun Aug 08, 2021 9:14 am
How is everyone else booting their systems with Christian's new kernel images?
I run it with these commands (uInitrd-5.10 is new enough to work also with uImage-5.14; I have not installed the kernel modules):
setenv bootargs root=LABEL=FIENIX
load mmc 0:1 1000000 uImage-5.14;load mmc 0:1 1c00000 cyrus_5020.dtb;load mmc 0:1 2000000 uInitrd-5.10
bootm 1000000 2000000 1c00000
Re: Kernel 5.14
Posted: Sun Aug 08, 2021 12:02 pm
by acefnq
Thanks Roland. My args are almost identical but I will try with an uinitrd-5.10 image.
cheers
ace
Re: Kernel 5.14
Posted: Sun Aug 08, 2021 12:42 pm
by acefnq
Roland
Using a backup of Uinitrd-5.10 failed to boot. I got a message similar to the one below:
mount: mounting /dev/disk/by-uuid/***************************** on /root
failed: Invalid argument
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /proc on /root/proc failed: No such file or directory
Target file system doesn't have /sbin/init
No init found. Try passing init= bootarg
Busybox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu7) built-in shell (ash)
Enter 'help' for a list of built-in commands
(initramfs) _
Any ideas? I can boot with uInitrd-5.10 and kernel image 5.7. I'll look around for another download of uInitrd-5.10 in case mine is corrupt. I basically get the same message trying to boot Fienix or MintPPC32.
ace
Re: Kernel 5.14
Posted: Sun Aug 08, 2021 2:14 pm
by xeno74
acefnq wrote: Sun Aug 08, 2021 12:42 pm
Roland
Using a backup of Uinitrd-5.10 failed to boot. I got a message similar to the one below:
mount: mounting /dev/disk/by-uuid/***************************** on /root
failed: Invalid argument
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /proc on /root/proc failed: No such file or directory
Target file system doesn't have /sbin/init
No init found. Try passing init= bootarg
Busybox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu7) built-in shell (ash)
Enter 'help' for a list of built-in commands
(initramfs) _
Any ideas? I can boot with uInitrd-5.10 and kernel image 5.7. I'll look around for another download of uInitrd-5.10 in case mine is corrupt. I basically get the same message trying to boot Fienix or MintPPC32.
ace
Could you please boot without an initial ramdisk?
