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.
I have a little curiosity here.
Slackware 13, using the CD image disc 1 (the one I believe is the install cd) doesn't seem to be able to boot on any system, on any cd or dvd drive, without giving a Kernel Panic.
Wolvix, based on Slackware 12.2, on the other hand, works fine, which is what interests me - what changed between 12.2 and 13 that caused it to cease to boot?
I'm certain the image is fine. I've had issued with high burn rates before, and use lower ones to avoid repeats anyway. I don't think it's the media either, since I re-downloaded and burnt a second one, which also suffers from the same problem.
I'm certain the image is fine. I've had issued with high burn rates before, and use lower ones to avoid repeats anyway. I don't think it's the media either, since I re-downloaded and burnt a second one, which also suffers from the same problem.
Okay. Can you boot CD #1 on a different machine? This will completely rule out the CD image corruption issue. Did you check the md5 sum on the image?
Once you've ruled out bad media, image corruption then you can move onto other possibilities.
No.
Well, technically, it does boot as such, but it doesn't get to a point where the user can interact before giving the now-familiar Kernel Panic, which seems to happen everywhere.
And yes, I did, I always check. It still matches.
No.
Well, technically, it does boot as such, but it doesn't get to a point where the user can interact before giving the now-familiar Kernel Panic, which seems to happen everywhere.
And yes, I did, I always check. It still matches.
If you have access to a different machine try booting CD #1 on that unit. If it boots up fine, then perhaps you have a hardware issue with your PC. If it fails to boot then the CD may be bad.
Good luck with this!
I do have several machines, and I'm fairly certain I pointed out it doesn't seem to boot on any system.
Which I'll admit seems to suggest the media, but with two separate copies of the CD1 image both doing exactly the same, it looks like I'm going to have to grab yet another one.
Maybe this time the DVD will be a better idea.
I do have several machines, and I'm fairly certain I pointed out it doesn't seem to boot on any system.
Which I'll admit seems to suggest the media, but with two separate copies of the CD1 image both doing exactly the same, it looks like I'm going to have to grab yet another one.
Maybe this time the DVD will be a better idea.
If it does not boot on *any* system you've got a bad CD. Yeah. Get another CD image or try the DVD.
I generally find using the USB net-installer to be more reliable, as my CD/DVD writers are notorious for pumping out faulty discs. Just make sure you have a good network connection!
I find network installs aren't ideal on the current home network - while it's reliable, there are often other users using the bandwidth as well, which means either they experience slow speeds and come complaining at their network admin (me) or I have to put up with low speeds, which is irritating when I'm trying to make the system just get on with it and work.
USB also would be nice - if the BIOSes available here supported it. Only one does support it to my knowledge, and I've only ever managed to get it work once.
I'm happy to report the DVD has left me with a working KDE desktop of Slackware 13, and now it's just a case of learning.
And I'm already starting to see why people say if you use Slackware, you'll learn Linux.
Now I just have to figure a few last things out. A graphic login, even if not a necessity, would be useful.
I also know GNOME seems to be conspicuously missing, to my knowledge removed, but I have an affinity for certain GNOME apps which I haven't managed to get out of me yet. It'd be nice to have them until I can get fully over to KDE.
The proprietary nVidia drivers also currently escape me. I'm too used to grabbing the nVidia 173 packages from whichever distro's repository, or using alien to steal Ubuntu's driver management. I had planned to do that again, but alien's missing, and rpm2tgz doesn't seem to want to install.
I think that's all. I'm getting there, and learning. I'm just still too used to other distros.
I'm happy to report the DVD has left me with a working KDE desktop of Slackware 13, and now it's just a case of learning.
And I'm already starting to see why people say if you use Slackware, you'll learn Linux.
Now I just have to figure a few last things out. A graphic login, even if not a necessity, would be useful.
I also know GNOME seems to be conspicuously missing, to my knowledge removed, but I have an affinity for certain GNOME apps which I haven't managed to get out of me yet. It'd be nice to have them until I can get fully over to KDE.
The proprietary nVidia drivers also currently escape me. I'm too used to grabbing the nVidia 173 packages from whichever distro's repository, or using alien to steal Ubuntu's driver management. I had planned to do that again, but alien's missing, and rpm2tgz doesn't seem to want to install.
I think that's all. I'm getting there, and learning. I'm just still too used to other distros.
Congratulations!!
To get a graphical log-in just fire-up a text editor such as nano and edit:
# nano /etc/inittab
change this:
Code:
id:3:initdefault:
to:
Code:
id:4:initdefault:
Save and exit.
That will give you a graphical log-in manager at run level 4.
I'm curious about your hardware, what are the specs?
If you did verify both the download image & burnt image then I suspect hardware. If older hardware you may be running up against the '4kvs8k' block issue with the CDROM.
The above link and others can be found at 'Slackware-Links'. More than just SlackwareŽ links!
I never had any problems with NVIDIA*.run installers from nvidia website. Just make sure you have kernel-source package installed, exit X and 'sh NVIDIA*.run' should get you going. Another, slackware package management controlled way, is to install using slackbuilds.org buildscripts.
hitest, thanks. I was trying to find KDM to do the same thing. Didn't realize it wasn't needed.
onebuck - this is a rather custom rig, and it's also rather old. About the only thing I can really say for certain is that I know the graphics card is a GeForce FX 5200, which is the one that needs the 173 version of the drivers. And on that...
veeall, I just found that myself. I'm googling my way through each problem and missing thing, and only just run across those.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.