I got a bit further.
I mounted / on my disk as a partition while running from the sdcard, and rc.4 has that message about starting the Session Manager. Lightdm & xdm are present, so that should start.
I set up for runlevel 3, tried things and found the error. / on the disk is not mounting rw, but ro.
I can't see any errors, Now I had previously run
Code:
grep -inre 'mmcblk0' /etc/*
on this disk, and the only hit was from /etc/mtab
. So I opened /etc/mtab in nano.
Code:
bash-5.1$ cat /mnt/tmp/etc/mtab
/dev/mmcblk0p2 / ext4 rw,noatime,nodiratime,data=writeback,errors=remount-ro 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /dev/shm tmpfs rw 0 0
shm /dev/shm tmpfs rw 0 0
bash-5.1$
Don't ask me why or how, but /etc/mtab must not get wiped on a Slackware shutdown. All my pc backups have things in /etc/mtab. So I ran my grep in /boot, and it's bad.
Code:
bash-5.1$ cd /mnt/tmp/boot
bash-5.1$ grep -r mmcblk0 *
grep: boot.scr: binary file matches
config:CONFIG_CMDLINE="console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait"
config-5.15.5:CONFIG_CMDLINE="console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait"
grep: Image: binary file matches
rebuild-initrd.sh:if [[ ! -z $(mount | grep -P "(mmcblk0|sd).1.*boot.*fat") ]]; then
grep: start4cd.elf: binary file matches
grep: start4db.elf: binary file matches
grep: start4.elf: binary file matches
grep: start4x.elf: binary file matches
grep: start_cd.elf: binary file matches
grep: start_db.elf: binary file matches
grep: start.elf: binary file matches
grep: start_x.elf: binary file matches
grep: vmlinuz-5.15.5: binary file matches
It was also in boot.cmd, some u-boot file, but I edited it out. I'm worried about it being in the kernel, though.
As a last resort, I checked /dev, which is empty. So I tried
Code:
ln -sf sda2 mmcblk0p2
making a symlink from mmcblk0p2 to point at sda2 - just in case. When you at the bottom, the only way is up
I'll have to wait to try it.
