LinuxQuestions.org
Page 1 of 2 1 2
Show 50 post(s) from this thread on one page

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Slackware (current) does not work properly after update (https://www.linuxquestions.org/questions/slackware-14/slackware-current-does-not-work-properly-after-update-4175707234/)

paulomatheus 01-31-2022 01:28 PM
Slackware (current) does not work properly after update
 
Hi.
I use Slackware current with KDE Plasma as graphic interface, and I did an update. After that, Slackware stopped work properly. At the initial screen (terminal, before use starx command) the keyboard of the notebook works normal, but the USB keyboard don't. After I enter the graphical interface (using startx command) the KDE Plasma loads and show the desktop, but the keyboard (now, the notebook keyboard) and the mouse do not work.
The O.S. seems to continue working, because after a time the screen locks automatically.
I've tried to upgrade again the Slackware at the terminal, but a error appears. That's when I saw that the network card was not being recognized.
I used the ifconfig -a but it did not show my network card, only shows lo result.
The commands that I used to upgrade the Slackware before the errors was:
Code:
slackpkg update
slackpkg install-new
slackpkg upgrade-all

LuckyCyborg 01-31-2022 01:32 PM
Quote:
Originally Posted by paulomatheus (Post 6323840)
Hi.
I use Slackware current with KDE Plasma as graphic interface, and I did an update. After that, Slackware stopped work properly. At the initial screen (terminal, before use starx command) the keyboard of the notebook works normal, but the USB keyboard don't. After I enter the graphical interface (using startx command) the KDE Plasma loads and show the desktop, but the keyboard (now, the notebook keyboard) and the mouse do not work.
The O.S. seems to continue working, because after a time the screen locks automatically.
I've tried to upgrade again the Slackware at the terminal, but a error appears. That's when I saw that the network card was not being recognized.
I used the ifconfig -a but it did not show my network card, only shows lo result.
The commands that I used to upgrade the Slackware before the errors was:
Code:
slackpkg update
slackpkg install-new
slackpkg upgrade-all
Looks like you forgot to update your bootloader(s) for the latest installed kernel, so you use an older kernel without its associated modules.

paulomatheus 01-31-2022 01:32 PM
Quote:
Originally Posted by LuckyCyborg (Post 6323843)
Looks like you forgot to update your bootloader(s) for the latest installed kernel, so you use an older kernel without its associated modules.
How can I fix it?

LuckyCyborg 01-31-2022 01:34 PM
Quote:
Originally Posted by paulomatheus (Post 6323845)
How can I fix it?
Depends on how you have configured the bootloader and what bootloader you use.

Anyway, you are still lucky that you can boot the system, and you can inspect it.

paulomatheus 01-31-2022 01:40 PM
Quote:
Originally Posted by LuckyCyborg (Post 6323846)
Depends on how you have configured the bootloader and what bootloader you use.

Anyway, you are still lucky that you can boot the system, and you can inspect it.
I'm using LILO and I used the automatic configuration for it in the the Slackware installer

LuckyCyborg 01-31-2022 01:42 PM
Show your /etc/lilo.conf

And, did you observed a kernel update when you did the last update?

As principle, after a kernel update you should run "lilo" to update your bootloader. BUT, usually you should also update your initrd, too.

paulomatheus 01-31-2022 01:46 PM
Quote:
Originally Posted by LuckyCyborg (Post 6323849)
Show your /etc/lilo.conf

And, did you observed a kernel update when you did the last update?

As principle, after a kernel update you should run "lilo" to update your bootloader. BUT, usually you should also update your initrd, too.
Yes, there was a kernel update

paulomatheus 01-31-2022 01:51 PM
Quote:
Originally Posted by LuckyCyborg (Post 6323849)
Show your /etc/lilo.conf

And, did you observed a kernel update when you did the last update?

As principle, after a kernel update you should run "lilo" to update your bootloader. BUT, usually you should also update your initrd, too.
To update my initrd do I need to know the kernel version and edit the file?

LuckyCyborg 01-31-2022 01:56 PM
Quote:
Originally Posted by paulomatheus (Post 6323854)
To update my initrd do I need to know the kernel version and edit the file?
The current kernel version is simple to find, looking in the /boot directory - I suspect that you have 5.15.18 and to generate a new initrd you can use "/usr/sbin/geninitrd"

BTW, what architecture you use? i586 or x86_64?

giomat 01-31-2022 01:58 PM
It happened some times to me and what I do in these cases is a chroot using the installation media (USB drive in my case).

You can follow this great guide here
https://docs.slackware.com/howtos:sl...oot_from_media.

Once you are inside the chroot, just run /shin/lilo and it should be good to go after a reboot, provided that you didn't switch to the generic kernel after the installation.

EDIT: sorry after a better read i see that you are indeed running a generic kernel, better follow the luckycyborg advice

LuckyCyborg 01-31-2022 02:01 PM
Quote:
Originally Posted by giomat (Post 6323857)
It happened some times to me and what I do in these cases is a chroot using the installation media (USB drive in my case).

You can follow this great guide here
https://docs.slackware.com/howtos:sl...oot_from_media.

Once you are inside the chroot, just run /shin/lilo and it should be good to go after a reboot, provided that you didn't switch to the generic kernel after the installation.

EDIT: sorry after a better read i see that you are indeed running a generic kernel, better follow the luckycyborg advice
The OP still can boot and enter in the system, I do not think that s/he needs to chroot.

paulomatheus 01-31-2022 02:02 PM
Quote:
Originally Posted by LuckyCyborg (Post 6323856)
The current kernel version is simple to find, looking in the /boot directory - I suspect that you have 5.15.18 and to generate a new initrd you can use "/usr/sbin/geninitrd"

BTW, what architecture you use? i586 or x86_64?
I'm using x86_64
And the Kernel's version: that's exactly what you said
5.15.18

LuckyCyborg 01-31-2022 02:03 PM
Quote:
Originally Posted by paulomatheus (Post 6323860)
I'm using x86_64
Again, please show your /etc/lilo.conf file content.

paulomatheus 01-31-2022 02:18 PM
1 Attachment(s)
Quote:
Originally Posted by LuckyCyborg (Post 6323861)
Again, please show your /etc/lilo.conf file content.
I took photos because I couldn't copy them, here are the photos from my Lilo.conf file in PDF

LuckyCyborg 01-31-2022 02:31 PM
Quote:
Originally Posted by paulomatheus (Post 6323863)
I took photos because I couldn't copy them, here are the photos from my Lilo.conf file in PDF
So, you do not use initrd. It's enough to execute "lilo" as root, and to reboot.


All times are GMT -5. The time now is 10:37 AM.
Page 1 of 2 1 2
Show 50 post(s) from this thread on one page