Salix Forums

Running Salix64 14.0 with xfce.
I did few package upgrades (can't find the log) via gslapt (using the GUI) and after rebooting at the logon screen mouse and keyboard no longer work, and the screen resolution has lowered, althoug you can still see the login fields! weired.
Using SysRescCD choosing "Boot to an existing linux distribution..." I managed to boot it and get the login screen where everything is as it's supposed to be
however after login there is no sound and also problem with playing some video files on internet. I would assume these would get fixed if I manage to do a proper/normal login (not using SysResCD).
Can someone please guide me to fix this?

What updates? You don't provide enough information for anyone to understand what happened. Basically, what you describe should be impossible.

Post the output of and the contents of your /etc/slapt-get/slapt-getrc.

khash777 wrote:Running Salix64 14.0 with xfce.
I did few package upgrades (can't find the log) via gslapt (using the GUI) and after rebooting at the logon screen mouse and keyboard no longer work, and the screen resolution has lowered, although you can still see the login fields! weired.

This looks to me like the kernel was updated but "lilo -v" wasn't done before reboot.

gapan: sorry for not providing enough info, I basically didn't know how to get that info

The list of updated pkgs after running that command was:
slapt-get-0.10.2p-x86_64-1gv
sourcery-0.9.2-noarch-1gv
midori-0.5.2-x86_64-1gv
libgcrypt-1.5.3-x86_64-1_slack14.0
geany-1.23.1-x86_64-1gv
xorg-server-1.12.4-x86_64-1_slack14.0
xorg-server-xvfb-1.12.4-x86_64-1_slack14.0
xorg-server-xnest-1.12.4-x86_64-1_slack14.0
xorg-server-xephyr-1.12.4-x86_64-1_slack14.0
kernel-modules-3.2.45-x86_64-3

and the /etc/slapt-get/slapt-getrc is:

WORKINGDIR=/var/slapt-get
EXCLUDE=^aaa_elflibs,^aaa_base,^devs,^glibc.*,^udev,^rootuser-settings,^zzz-settings.*,-i?86-
SOURCE=http://salix.enialis.net/x86_64/slackwa ... /:OFFICIAL
SOURCE=http://salix.enialis.net/x86_64/slackwa ... /:OFFICIAL
SOURCE=http://salix.enialis.net/x86_64/14.0/:PREFERRED
SOURCE=http://www.slackware.com/~alien/slackbuilds/:OFFICIAL

laprjns: what would that command do?

Appreciate all your help

lilo -v needs to be run after a kernel upgrade, so that the bootloader points at the new kernel.

Your /etc/slapt-get/slapt-getrc, among other things, excludes certain packages from being automatically upgraded, including kernel packages; but you have somehow lost the kernel from the list. Mine reads:
You need to add
back into your list to stop anything like this happening again (not anything else from my list, which is just for comparison). It looks like you have upgraded the kernel-modules, but not anything else ... though that seems puzzling.
Notice the format: items are separated by commas, with no spaces between. "^kernel-.*" means "anything with kernel- at the beginning of its name"

Please post which version of Salix you are using, and the output of these commands:

Ah I see, I removed the "^kernel-.*," filter flag to be able to upgrade it, I had few random kernel crashes (before doing
this upgrade) with "kernel panic" messages in the black screen so thought I could solve it that way.
I'm using Salix64 Xfce 14.0.

ls -l /boot:

mar 15 20:23 README.initrd -> /usr/doc/mkinitrd-1.4.7/README.initrd
mar 15 20:25 System.map -> System.map-huge-3.2.29
sep 17 2012 System.map-huge-3.2.29
mar 15 20:42 boot.0800
mar 15 20:42 boot_message.txt
jun 15 23:18 config
sep 17 2012 config-huge-3.2.29
aug 17 15:47 map
aug 9 2012 salix.bmp
mar 15 20:25 vmlinuz -> vmlinuz-huge-3.2.29
sep 17 2012 vmlinuz-huge-3.2.29

ls -lt /var/log/packages | grep kernel:

aug 13 16:11 kernel-modules-3.2.45-x86_64-3
mar 15 20:25 kernel-huge-3.2.29-x86_64-1
mar 15 20:23 kernel-headers-3.2.29-x86-1
mar 15 20:23 kernel-firmware-20120804git-noarch-1

uname -r:

2.6.35-std200-amd64

You ned to reinstall the correct kernel'modules package, perhaps by downloading it from the repos. And then look into the problem that originally led you to edit the blacklist line.

My battery's about to run out so I hope someone else will step in with the link you need.

In general, to install something blacklisted, just request it explicitly and the blacklist is overruled. But have a look in the wiki for guidance on kernel upgrades, not that that is necesarily the solution in the present case.

You ned to reinstall the correct kernel'modules package, perhaps by downloading it from the repos. And then look into the problem that originally led you to edit the blacklist line.

My battery's about to run out so I hope someone else will step in with the link you need.

In general, to install something blacklisted, just request it explicitly and the blacklist is overruled. But have a look in the wiki for guidance on kernel upgrades, not that that is necesarily the solution in the present case.

mimosa:
You were right, I solved this by updating the kernel-huge and kernel-headers to the same version as the kernel-modules, i.e. "3.2.45-x86_64-3". The opposite of your suggestion somehow but thought this would be the easier way

Thank you all for your help.

That makes sense, in that it presumably does what you were hoping to do originally to address the problem you had.

I'm glad everything's working properly now