I know there were some other links to similar issues,
https://www.linuxquestions.org/quest...urrent-947120/
https://www.linuxquestions.org/quest...orking-943408/

I checked those and both were caused by not running which I did do.

My most recent update/install-new/upgrade-all upgraded my desktop to 5.4.1. I was looking forward to using it, however when I booted my computer I saw several error messages of the form:
I had never seen these messages before so I attempted to redo the updates, thinking maybe something didn't install right. Unfortunately when I attempted to run the slackpkg commands I found that my network wasn't working.

Running ifconfig showed only lo, and not eth0. My desktop does not have a wireless adapter, so I didn't expect to see it. I also went to /etc/rc.d/ and checked that rc.inet1 was set to executable. I finally ran netconfig to see if NetworkManager could auto fix it.

I found the second issue when I attempted to startx to check if NetworkManager was working. My cursor was in the middle of the screen and my keyboard and mouse were non-responsive. I couldn't get back to TTY without a hard reboot. I attempted using X with multiple installed Desktop Environments and Window Managers to see if it was just one.

I'm posting this from my laptop since my desktop is mostly unusable. I'm a college student with somewhat limited time, is this something that can be fixed or would my time be better used if I just backup my files and reinstall?

Edit: I did run lilo to update the bootloader

here's what I see

maybe something didn't work when you did your most recent update/install-new/upgrade-all?

Most likely the OP do not ran yet LILO to update the bootloader, and probably he uses the huge kernel, then he still uses the previous installed kernel with no modules.

1 members found this post helpful.

I did run /sbin/lilo. Although I am running the generic huge kernel. I will edit my post to reflect that!

or elilo and didn't copy new kernel to the efi partition

Running ls on reveals that the folder is empty.

I didn't use elilo, I stuck with regular Lilo.

I have been having similar issues after updates with slackpkg, after updates I have needed to run slackpkg install kernel.

Then, you failed the upgrade or you are a victim of some bug on slackpkg.

So, did you use Slackware i586 or x96_64? For the later, you need this package downloaded with another computer:

https://mirrors.slackware.com/slackw...1-x86_64-1.txz

Then, in your computer, to upgrade it manually:
Further, you may want to consider other packages with upgrading issues.

And for the future, I recommend you to make a Slackware system on a small USB hard drive, because it is very useful on debugging a failed installation.

That's what I do, with a spare 80GB hard drive from an old laptop, mounted in a cheap USB enclosure and where I have a full installation of slackware-current and a mirror of slackware-current, of course.

It is very handy, but there's a little trick: to use in fstab, lilo.conf and initrd generation instead of absolute devices like /dev/sdd2 instead their UUIDs. This way, the partitions setup from the USB hard drive survive to the movement on whatever computer.

1 members found this post helpful.

Thank you, I'm gonna reinstall. I have everything set up so it shouldn't take me too long to reinstall, I guess this is a learning experience.

Had the same problem. Ran lilo (and lilo -v) before the reboot but 1)had not create a new initrd 2)had left the (previous) generic as default option in lilo. To solve this, i "chrooted", comment in lilo.conf the line that sets the default option run lilo and lilo -v and reboot.
(afterwards i create the new initrd etc etc)