Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
no it was the liveslack install and that was the only way I could get Slackware to boot the first time after installing.
I think it was trying to load the wrong driver on the first boot after installing
Last edited by colorpurple21859; 09-30-2017 at 12:05 PM.
I've been reading about installing on one computer, then putting the hard drive into another. Does this work if the processors are totally different? My old desktop, relegated to 2nd place, has an AMD Athlon 64 X2 5200+, and has run every release of Slackware64 perfectly. The present one has a Xeon E5-1650. Can't make my mind up if it's worth the effort.
I've been reading about installing on one computer, then putting the hard drive into another. Does this work if the processors are totally different? My old desktop, relegated to 2nd place, has an AMD Athlon 64 X2 5200+, and has run every release of Slackware64 perfectly. The present one has a Xeon E5-1650. Can't make my mind up if it's worth the effort.
It should work fine... Linux doesn't care about what machine it was installed on. It will load whatever drivers it determines it needs when it boots up. But, if you have multiple drives installed, it could mess with the naming of those drives (/dev/sda is now /dev/sdc, or something similar) and cause things to not boot.
I've gone off that idea. I opened up the old desktop, and remembered the wrestling match I had a few years ago, fitting a new PSU & graphics card, getting the leads packed in, etc. It was like major surgery. That's one good thing about this Dell, all the bits & pieces inside are easy to get at, remove, and replace.
I still think the answer lies in a Ubuntu/Dell patched kernel. I've had a look at the Mint kernel source, but nothing's jumping out at me.
Whoopeee! Praise "Bob"!
Unplugged everything.
Took out RAID controller (don't use it, and it was increasing boot-time 100%).
Plugged everything in, switched on, Mint booted OK.
Stuck Slackware64 14.2 DVD in, rebooted: NO error message. Install went OK.
Rebooted with fingers crossed, and no problems.
So the RAID controller (PERC H310) was the cause of the trouble.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
