hi
vmlinux-6.10-4 from cf0: boot fienix fine but stop with this
failed to start lightdm.service - Lightdm Display manager
I can log in but not start lightdm
New kernels
Re: New kernels
This is a "git bisect good". The lightdm issue is from the bug ioctls (Xorg is affected).musa wrote: Fri Jun 21, 2024 9:55 pm hi
vmlinux-6.10-4 from cf0: boot fienix fine but stop with this
failed to start lightdm.service - Lightdm Display manager
I can log in but not start lightdm
Here is the next test kernel vmlinux-6.10-5.
Re: New kernels
Hi
vmlinux-6.10-5 boot on Fienix and get fail on start lightdm.
Can log in from promt but can not start X
vmlinux-6.10-5 boot on Fienix and get fail on start lightdm.
Can log in from promt but can not start X
AmigaX1000
Re: New kernels
Thank you for testing!musa wrote: Sat Jun 22, 2024 4:23 pm Hi
vmlinux-6.10-5 boot on Fienix and get fail on start lightdm.
Can log in from promt but can not start X

This is a "git bisect good" because your X1000 boots.
Here is the next test kernel: vmlinux-6.10-6
Re: New kernels
Thanks a lot for testing. It has been noted as "git bisect bad".
Here is the next test kernel: vmlinux-6.10-7
Re: New kernels
Hi
vmlinux.6.10-7 start but get failed to start lightdm.service error
can log in from promt
vmlinux.6.10-7 start but get failed to start lightdm.service error
can log in from promt
AmigaX1000
Re: New kernels
OK, login works so "git bisect good".musa wrote: Sun Jun 23, 2024 7:00 pm Hi
vmlinux.6.10-7 start but get failed to start lightdm.service error
can log in from promt
Next kernel for testing: vmlinux-6.10-8
Re: New kernels
My experience echoes recent findings. So for me the RC3 and RC4 of 6.10 resulted in kernel panic. Except when booted with ramdisk which resulted in a drop to initramfs with a dead keyboard.
With 6.10-5 and 6.10-6 it boots like reported and ends in lighdm error.
However it does something funky with my SATA controller. I rebooted into Xenial with kernel 5.10.218 and it stalled on SATA query. It eventually boots but but shouldn't get stuck on SATA. But the worst was when I rebooted and amigaboot couldn't load due to insufficient memory. This is CFE code for faulty SATA connection. I ran menu and it was able to load after. Funny quirk.
So that is from the 6.10-6 kernel. I'm not sure what it means by ata2. I don't see it mapping ata2 to sd something. All my sata ports have drives.
Also kernel 5.10.218 complains about no depmod file in modules.
With 6.10-5 and 6.10-6 it boots like reported and ends in lighdm error.
However it does something funky with my SATA controller. I rebooted into Xenial with kernel 5.10.218 and it stalled on SATA query. It eventually boots but but shouldn't get stuck on SATA. But the worst was when I rebooted and amigaboot couldn't load due to insufficient memory. This is CFE code for faulty SATA connection. I ran menu and it was able to load after. Funny quirk.
Code: Select all
Jun 24 03:10:52 fienix kernel: scsi 6:0:0:0: Direct-Access SanDisk Cruzer Glide 1.27 PQ: 0 ANSI: 6
Jun 24 03:10:52 fienix kernel: sd 6:0:0:0: Attached scsi generic sg1 type 0
Jun 24 03:10:52 fienix kernel: sd 6:0:0:0: [sda] 30529536 512-byte logical blocks: (15.6 GB/14.6 GiB)
Jun 24 03:10:52 fienix kernel: sd 6:0:0:0: [sda] Write Protect is off
Jun 24 03:10:52 fienix kernel: sd 6:0:0:0: [sda] Mode Sense: 43 00 00 00
Jun 24 03:10:52 fienix kernel: sd 6:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Jun 24 03:10:52 fienix kernel: sda: sda1
Jun 24 03:10:52 fienix kernel: sd 6:0:0:0: [sda] Attached SCSI removable disk
Jun 24 03:10:52 fienix kernel: ata2: link is slow to respond, please be patient (ready=0)
Jun 24 03:10:52 fienix kernel: ata2: link is slow to respond, please be patient (ready=0)
Jun 24 03:10:52 fienix kernel: ata2: link is slow to respond, please be patient (ready=0)
Jun 24 03:10:52 fienix kernel: ata2: limiting SATA link speed to <unknown>
Jun 24 03:10:52 fienix kernel: ata2: hardreset failed
Jun 24 03:10:52 fienix kernel: ata2: reset failed, giving up
Jun 24 03:10:52 fienix kernel: scsi 2:0:0:0: Direct-Access ATA SAMSUNG HD103SJ 00E5 PQ: 0 ANSI: 5
Jun 24 03:10:52 fienix kernel: sd 2:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Jun 24 03:10:52 fienix kernel: sd 2:0:0:0: Attached scsi generic sg2 type 0
Jun 24 03:10:52 fienix kernel: sd 2:0:0:0: [sdb] Write Protect is off
Jun 24 03:10:52 fienix kernel: scsi 3:0:0:0: Direct-Access ATA WDC WDS480G2G0A- 0000 PQ: 0 ANSI: 5
Jun 24 03:10:52 fienix kernel: sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Jun 24 03:10:52 fienix kernel: sd 3:0:0:0: [sdc] 937721856 512-byte logical blocks: (480 GB/447 GiB)
Jun 24 03:10:52 fienix kernel: sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jun 24 03:10:52 fienix kernel: sd 3:0:0:0: Attached scsi generic sg3 type 0
Jun 24 03:10:52 fienix kernel: sd 2:0:0:0: [sdb] Preferred minimum I/O size 512 bytes
Jun 24 03:10:52 fienix kernel: sd 3:0:0:0: [sdc] Write Protect is off
Jun 24 03:10:52 fienix kernel: sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Also kernel 5.10.218 complains about no depmod file in modules.
Re: New kernels
Thank you for testing. We do a bisecting. I hope, we can find the issue.Hypex wrote: Sun Jun 23, 2024 8:15 pm My experience echoes recent findings. So for me the RC3 and RC4 of 6.10 resulted in kernel panic. Except when booted with ramdisk which resulted in a drop to initramfs with a dead keyboard.
With 6.10-5 and 6.10-6 it boots like reported and ends in lighdm error.
Next kernel for testing: vmlinux-6.10-8
You can also test the vmlinux-6.10-8.
