SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
After debating weather to leave well enough alone, or up grade to -current, curiosity got the best of me...
I decided to upgrade my laptop to -current.
Now when I boot-up my keyboard and mouse (touch pad) don't work at all. I have no input what so ever.
The computer is a Dell XPS 17 (L702X) It was set to boot to runlevel 4 using GDM with xfce as the WM.
Will it be possible to revert to 13.37 or, will I need to reinstall?
If it is possible to revert back to 13.37, what is the best approach?
Whenever you upgrade from a preset release to -Current you should revert to the basic runlevel 3 just to be safe because often you may have to rerun several configuration scripts again to reset the system like xorgsetup, alsaconf, netconfig, etc.
Perform the upgrade commands in this order (reconfirmed from AlienBOB) after switching your FTP/HTTP mirror over to a Current mirror:
At present you MAY be able to boot the system using the rescue command from the install disk and get some functionality before reattempting to see what is wrong:
You can try forcing runlevel 3 at boot-time by passing 3 as a parameter at the lilo boot screen (assuming you use lilo). For example, if the menu entry is called Linux, you would type "Linux 3" (without quotes) and press enter (I think you have to press Tab to get to the prompt but I cannot remember). If it still doesn't work then you can try booting into single user mode by passing 1 instead of 3. And of course if that still doesn't work then you can always use ReaperX7's above-mentioned trick when booting using the install CD/DVD.
It was set to boot to runlevel 4 using GDM with xfce as the WM.
I'm guessing you installed GDM from a third party as that is not part of a standard Slackware install. Are you running GSB or just GDM from a repository? Just curious. I'm not sure if that has anything to do with your upgrade getting hosed.
Whenever you upgrade from a preset release to -Current you should revert to the basic runlevel 3 just to be safe because often you may have to rerun several configuration scripts again to reset the system like xorgsetup, alsaconf, netconfig, etc.
Perform the upgrade commands in this order (reconfirmed from AlienBOB) after switching your FTP/HTTP mirror over to a Current mirror:
At present you MAY be able to boot the system using the rescue command from the install disk and get some functionality before reattempting to see what is wrong:
Code:
huge.s root=/dev/sda# noinitrd=ro
# = whatever number your Linux boot partition is.
Live and learn, next time I attempt an upgrade I will switch to runlevel 3 before hand.
I did run the upgrade commands in that order, however when it came to slackpkg upgrade-all I got an error saying I needed to update the gpg key.
I ran slackpkg update-gpg, it failed...I don't remember the exact message.
Quote:
Originally Posted by T3slider
You can try forcing runlevel 3 at boot-time by passing 3 as a parameter at the lilo boot screen (assuming you use lilo). For example, if the menu entry is called Linux, you would type "Linux 3" (without quotes) and press enter (I think you have to press Tab to get to the prompt but I cannot remember).
This worked, I can get into the system...Thanks for that
Quote:
Originally Posted by hitest
Are you running GSB or just GDM from a repository?
I installed GDM and its dependencies from slackbuilds.org.
Quote:
Originally Posted by TobiSGD
I had that problem some time ago, just because I forgot the mandatory
Code:
slackpkg install-new
After that it worked like a charm (and still does).
Well, I will note that for future use....
Given the time I've spent trying to get this back up and getting nowhere, I decided to reinstall...It just takes less time...
Ok, I reinstalled 13.37, ran slackpkg update gpg, then updated using slackpkg in the order given above.
when I got to slackpkg upgrade-all I got this...
Code:
bash-4.1# slackpkg upgrade-all
You need the GPG key of Slackware Linux Project <security@slackware.com>.
To download and install that key, run:
# slackpkg update gpg
You can disable GPG checking too, but it is not a good idea.
To disable GPG, edit slackpkg.conf and change the value of the CHECKGPG
variable to off - you can see an example in the original slackpkg.conf.new
file distributed with slackpkg.
I ran "slackpkg update gpg" again and got the same message again....WTF....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.