I am facing issues with 6.6 kernel (build from the same repo; branch 6.6-main) where the kernel is logging to serial line, systemd gets starting but the console is lost after some time and there is no login console being shown. It seems like it incorrectly initialize the ttyS console.
Any guess from where to start? I plan to investigate the problem via ssh because the network seem to be running but I am wondering of some of you was already facing the problem like this .
Looks good so far…disp lines are for drm (hdmi out). TtyS0 is recognized and i guess it is a problem with systemd. Maybe the service file for the ttyS0 is wrong,but wonder why this is kernel depended
11004000.serial: ttyS0 at MMIO 0x11004000 (irq = 204, base_baud = 1625000) is a ST16650V2
Sorry, it get me some time until I get back to this. I have seen some queued jobs with systemctl list-jobs like graphical.target etc. So I have enabled just systemctl set-default multi-user.target because the default one was graphical target. Commenting out the wifi.sh solved the issue because the rc-local service was running but it was’t ending.
systemctl list-jobs --after
JOB UNIT TYPE STATE
1 multi-user.target start waiting
└─ waiting for job 114 (systemd-update-utmp-runlevel.service/start) - -
114 systemd-update-utmp-runlevel.service start waiting
104 getty.target start waiting
└─ waiting for job 1 (multi-user.target/start) - -
105 [email protected] start waiting
└─ waiting for job 104 (getty.target/start) - -
113 rc-local.service start running
└─ waiting for job 1 (multi-user.target/start) - -
└─ waiting for job 105 ([email protected]/start) - -
└─ waiting for job 110 ([email protected]/start) - -
110 [email protected] start waiting
└─ waiting for job 104 (getty.target/start) - -
6 jobs listed.
I am not sure if it was my fault during the kernel compilation but systemd was complaining about missing autofs4 module and I have find out that the autofs support wasn’t enabled in my kernel compilation. So recompiling with this option also made systemd happy about this.
Thank you for your patience, I wasn’t aware that there is wifi being enabled in /etc/rc.local file :). I have created a sytemd service with timeout so when the WIFI is not available than it doesn’t stuck in the rc-local.service. I am starting with this but it might require some tuning and it might be good to split the device init and add the dependency on the wifi init service.