I think I hosed my machine....
 

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?

Damn, I think I had this same problem when upgrading my desktop to -current. I forget how I solved it.

Is /etc/rc.d/rc.hald set executable?

At this point I'm not sure...I need to figure out how to boot to run level 1 to see if I can use the keyboard.

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:

1. slackpkg update
2. slackpkg install-new
3. slackpkg upgrade-all
4. slackpkg clean-system

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:

# = whatever number your Linux boot partition is.

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.

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.

I had that problem some time ago, just because I forgot the mandatory After that it worked like a charm (and still does).

Original thread was here: http://www.linuxquestions.org/questi...orking-943408/

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.

This worked, I can get into the system...Thanks for that

I installed GDM and its dependencies from slackbuilds.org.

I did run slackpkg install-new, and that seemingly went well...As stated above I did have a problem with slackpkg upgrade-all.

I'll give that thread a read over...

Thanks all...

The GPG key should be updated when you run slackpkg update. I don't see why it didn't.

Me either, I'll try again tonight and see if I get the error again...

When I do a clean install I run:

# slackpkg update gpg

then:

# slackpkg update

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...

let us know if you attempt it again and how it goes.

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...

I ran "slackpkg update gpg" again and got the same message again....WTF....

Here goes a reboot....hope it works....

Well, it's still the same as before....

Right now time is at a premium for me, I guess 13.37 will have to do...

That is odd. Perhaps you uncommented a -current mirror that has issues? Just grasping at straws as that should work.

Or. When you uncomment a mirror, you have to remove the # and a space. If you leave the space, it might **** things up. Only a guess.

Yes. You must remove the # in front of a mirror, save then exit, for slackpkg to work. You do not need to remove the space anymore. The space glitch did mess up past versions of Slackware.

Ah, thanks, hitest. Didn't know the space removal wasn't necessary now.

You're welcome, brianL. :)

The mirror that I uncommented is in the -current section, and I did save it. It's the Oregon State university ftp site.
I guess I could try a different mirror....

Nothing wrong with that mirror, that's the one I use. Odd indeed.

I can confirm this behavior. I have made some tests in Virtualbox, using my own mirror (which is not mirrored from Oregon State University):
a) Upgrade from fresh install:

1. Install Slackware64 13.37 in Virtualbox
2. Add my mirror in /ect/slackpkg/mirrors
3. slackpkg update, OK
4. slackpkg install-new, cancelled the test here because of gpg errors

b) Upgrade from an up-to-date OS

1. Install Slackware64 13.37 in Virtualbox
2. Add my 13.37 mirror in /ect/slackpkg/mirrors and upgraded the system the usual way (update, install-new, upgrade-all, clean-system), OK
3. Change the mirror to Slackware64 -current and repeat the process, cancelled after install-new because of gpg errors.

c) Upgrade with updating gpg first:

1. Install Slackware64 13.37 in Virtualbox
2. Add my 13.37 mirror in /ect/slackpkg/mirrors and upgraded the system the usual way (update, install-new, upgrade-all, clean-system), OK
3. Change the mirror to Slackware64 -current
4. updated the package database and gpg (slackpkg update followed by slackpkg update gpg)
5. Used the usual routine to upgrade the system (as above), cancelled at install-new because of gpg errors

Seems to me that upgrading from 13.37 to current is broken at this time.

Strange, I did on Wednesday, and it's worked for me.

As i can see you have the 32 bit version installed. May it be possible that this is a 64 bit only issue?

@ceh383: Which version have you used?

Mmm, could be.

At least I now know it's not just me...
I'm running 64bit here..

This is almost exactly what I did, the only differences are..
1) A)Upgrade from an up-to-date OS with added software (bumblebee, cairo dock, etc) B)Upgrade from fresh install completely updated C)Upgrade from fresh install D)Upgrade with updating gpg first
2) I was installing to a machine, not a virtual machine.
3) I used the Oregon State University mirror.

Thanks for taking the time to verify this issue....

Now that there has been a "Friday the 13th massive upgrade", can one assume this issue has been resolved?

I just tried it in the VM and the problem still exists.

Thanks for the info TobiSGD,

I guess I'll have to keep on waiting....LOL

Try updating with slackroll

http://rg3.github.com/slackroll/

Tried that but cancelled the test as soon as the install-new function reported that there are no new packages to install.

This issue has been solved with the update from July 15, hitest has already tested it and it works.
Have fun with -current.

Thank you all very much...
Now when I get internet service in the new house I'll try it again...