Can't log into system, several (keyboard doesn't even work, mounting, modules) after current update (jun 11)
by Nang Dabbit from LinuxQuestions.org on (#5K0N4)
I don't even know where to begin, so I'll just list the issues I was able to glean, myself.
(Can't really scroll the tty without a working keyboard after all)
Edit:I am booting using 'legacy bios' not UEFI.
/dev/shm and /dev/pts don't have mount points.
uuids for my harddrives are not recognized
(despite being correct, checked it with a liveslack stick)
alsa seems to have troubles
keyboard doesn't work, if I unplug it and put it back in, all the mode lights stay on (numlock, caps, scroll)
'failed to find sysfs'
kmod tripping over some holders it can't find for the realtek r8168 module (which is one of my biggest problems in general, it seems it only works with the realtek drivers I have to compile myself)
when I use direct device pathes like /dev/sda1 they get recognized but things still work
grub-makecfg goes nuts with device nodes it can't find
(and a recent change also disabled the os prober, hot diggity damn bad timing I am SO GLAD I found a backup in vims backup dir no less)
(...and I wish I kept a backup of my system, too! ...frack!)
Anyway, there's a bunch of stuff wrong, I think the last update before this one I did was around march?
I'd have to check the /var/log/removed_packages I guess
What I have tried so far (other than using direct device paths):
I edited inittab to run a script that ran slackpkg update, but slackpkg plus seems to have some issue with GPGs or something and other problems
(used a different kernel that loads my internet but keyboard is still off)
grabbed Alien Bobs current ISO to do a slackpkg reinstall slackware64 in case I messed up the update process, but that didn't help either
I install-new'd and clean-system'd
(blacklisting my custom packages to get rid of any 'removed' packages, but there were none)
danced around with module blacklisting for the ethernet card and alsa-loopback, didn't work.
Using a slackware USB stick of forgotten make date (kernel is 4.4.14, or something, don't quote me on it)
to chroot in sundry ways but since I'm clueless I couldn't think of anything beyond editing fstab/inittab and the like turning things off an on.
(no internet on that one either and IF I can build the module for the card there, I don't know how...)
'slackpkg new-config' checks, but nothing out of the ordinary
single user mode (init 1)
...if only the keyboard would work at least...
it *seems* that the system kind of works through the script I put in instead of the 'login' prompt in the first tty but without a keyboard or an X session for that matter, not easy.
Got any ideas?
(Can't really scroll the tty without a working keyboard after all)
Edit:I am booting using 'legacy bios' not UEFI.
/dev/shm and /dev/pts don't have mount points.
uuids for my harddrives are not recognized
(despite being correct, checked it with a liveslack stick)
alsa seems to have troubles
keyboard doesn't work, if I unplug it and put it back in, all the mode lights stay on (numlock, caps, scroll)
'failed to find sysfs'
kmod tripping over some holders it can't find for the realtek r8168 module (which is one of my biggest problems in general, it seems it only works with the realtek drivers I have to compile myself)
when I use direct device pathes like /dev/sda1 they get recognized but things still work
grub-makecfg goes nuts with device nodes it can't find
(and a recent change also disabled the os prober, hot diggity damn bad timing I am SO GLAD I found a backup in vims backup dir no less)
(...and I wish I kept a backup of my system, too! ...frack!)
Anyway, there's a bunch of stuff wrong, I think the last update before this one I did was around march?
I'd have to check the /var/log/removed_packages I guess
What I have tried so far (other than using direct device paths):
I edited inittab to run a script that ran slackpkg update, but slackpkg plus seems to have some issue with GPGs or something and other problems
(used a different kernel that loads my internet but keyboard is still off)
grabbed Alien Bobs current ISO to do a slackpkg reinstall slackware64 in case I messed up the update process, but that didn't help either
I install-new'd and clean-system'd
(blacklisting my custom packages to get rid of any 'removed' packages, but there were none)
danced around with module blacklisting for the ethernet card and alsa-loopback, didn't work.
Using a slackware USB stick of forgotten make date (kernel is 4.4.14, or something, don't quote me on it)
to chroot in sundry ways but since I'm clueless I couldn't think of anything beyond editing fstab/inittab and the like turning things off an on.
(no internet on that one either and IF I can build the module for the card there, I don't know how...)
'slackpkg new-config' checks, but nothing out of the ordinary
single user mode (init 1)
...if only the keyboard would work at least...
it *seems* that the system kind of works through the script I put in instead of the 'login' prompt in the first tty but without a keyboard or an X session for that matter, not easy.
Got any ideas?