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.
I've been trying to get a slack 10.2 install going on a clean system. Mainly wanna use it to learn more than the basic linux stuff and use it as a test for apache http. Every time I get it installed and try to boot it either hangs or I get a kernel panic error. LILO won't install either and I've tried it both without LILO and tried using a boot disk. I'm wondering if my partition scheme is causing the problem. System specs are very basic: Athlon XP 2600+, 512MB ram, radeon 9600, 160GB HD. Here's the partition scheme I've been using:
/boot - 100MB (bootable)
/ - 500MB
/swap - 1GB
/var - 10GB
/home - 10GB
/usr - rest of unused space (approx 140GB)
Can anyone tell me what the basic partition scheme I should use is to just get Slackware running? Also, are there certan partitons that need to be logical or extended? Thanks
It shouldn't matter the partition scheme or if the partitions are primary or logical.
Is your harddisk sata or ata? Can you give more details on which kernel you select and what errors you're getting? Also, in the lilo configuration, choose Expert mode and install to MBR, that works better than on superblock.
My HD is ATA; it's just a plain old Western Digital drive. I'm using the default kernel, but I've also tried the base kernel too. I've also gone through the expert install for LILO and it won't install to either the superblock or the MBA. Not sure what else to try.
Ok, so, could you sucesfully install Slackware?
If you did, you could boot into it by booting with CD 1, and at LILO's boot: prompt, typing: bare.i root=/dev/hdXX
Change hdXX to your root partition and if you need, change bare.i for other kernel you may want.
If you can boot into it succesfully, try running the lilo configuration script from there by typing: /sbin/liloconfig and again, try Expert mode -> Install to MBR
I've gotten through the entire installation & configuration except for LILO. Every time I try to install LILO, whether it be to the superblock or MBA, it fails. Also tried going without LILO completely. If I try to boot after install it either hangs on a blank screen or I get a kernel panic error. I also tried using the floppy boot disk it asks to create and I still get a kernel panic. I know I tried one of the bare kernels when going through the config, but not sure if it was the bare.i specifically. I've gotten both Fedora & Mandrake to successfully intall on this box so I'm not sure what I'm doing wrong with slack.
assuming you are installing a very basic install, my / has 1.2 gig in it, but i installed everything
shouldnt the / partition be bootable and not the /boot partition? i may be wrong but i remember seeing another distro that installed a /boot partition by default but the / partition was what was marked bootable
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.