New kernels

[musa]

Hi
Have test vmlinux -6.10_rc1 with Fienix, Debian 32 and Debian 64.
Fenix and Debian 32 get this error : Failed to start lightdm.service - Light Display manager
failed to start Plymouth-quit.service - terminate plymouth boot screen
Debian 64 stop with this error failed to start colord.service - manage, Install and generate colord profiles.

There is no boot error with the normal kernel.

have a nice day.

[xeno74]

Hi
Have test vmlinux -6.10_rc1 with Fienix, Debian 32 and Debian 64.
Fenix and Debian 32 get this error : Failed to start lightdm.service - Light Display manager
failed to start Plymouth-quit.service - terminate plymouth boot screen
Debian 64 stop with this error failed to start colord.service - manage, Install and generate colord profiles.

There is no boot error with the normal kernel.

have a nice day.

Thank you for the test. It seems, that the root file system was mounted read-only.

Can you boot with the boot argument “3” additionally and post some more error messages?

setenv bootargs "root=/dev/<partition or disk> 3"

# multi-user.target: analogous to runlevel 3
# graphical.target: analogous to runlevel 5

For example:

Code: Select all

setenv bootargs "root=/dev/sdb4 3"

[musa]

Hi
Have tried several times with both runlevel 3 and 5.
The best result gave me a login screen with no graphical login. Trying to log in and start lightdm as root. Gets a black screen with a blinking cursor. Sometimes I can see lightdm trying to start several times.
Have a nice day

[xeno74]

Hi
Have tried several times with both runlevel 3 and 5.
The best result gave me a login screen with no graphical login. Trying to log in and start lightdm as root. Gets a black screen with a blinking cursor. Sometimes I can see lightdm trying to start several times.
Have a nice day

Thank you. Could you please take a picture from the start of your X1000? (Kernel error messages)

If you get a login. Please post the output of journalctl.

Or journalctl > boot.log and upload it to pastebin.com.

If it doesn’t work then boot the alpha3 and post the output of journalctl -k -b -1. (Gives logs from previous boot)

Or journalctl -k -b -1 > boot.log and upload it to pastebin.com.

[musa]

Hi
I can log into debian 64, but am not aware of how I can transfer the contents of the loaded file to a file on my usb disk.

[xeno74]

Hi
I can log into debian 64, but am not aware of how I can transfer the contents of the loaded file to a file on my usb disk.

After you have booted the RC1 with the boot argument “3”, you can boot the alpha3 with X11 and post the output of journalctl -k -b -1. (Gives logs from previous boot)

Or journalctl -k -b -1 > boot.log and upload it to pastebin.com.

[xeno74]

Xorg doesn't start anymore with the RC1 of kernel 6.10 in a virtual QEMU ppce500 machine.

[xeno74]

I think, it is: + CONFIG_ARCH_HAS_KERNEL_FPU_SUPPORT=y.

[xeno74]

I have reported it to the kernel developers: Xorg doesn't start and some other issues with the RC1 of kernel 6.10

[xeno74]

FYI: powerpc: implement ARCH_HAS_KERNEL_FPU_SUPPORT

Code: Select all

git revert 01db473e1aa32d651477be80f79b309313636203

Output:

Code: Select all

[master d6ea96a49698] Revert "powerpc: implement ARCH_HAS_KERNEL_FPU_SUPPORT"
 3 files changed, 1 insertion(+), 33 deletions(-)
 delete mode 100644 arch/powerpc/include/asm/fpu.h

Edit: I tested it but without any success.

The merge: Merge tag 'mm-nonmm-stable-2024-05-22-17-30'

Code: Select all

git revert  c760b3725e52403dc1b28644fb09c47a83cacea6 -m 1

It doesn't solve the issue.

@Musa
You don't need to test the RC1 again. There is an issue.