Need some guidence with Slackware

[geekzaus]

I have installed slack and everything went smooth on the installation (or so I thought). Anyhoo, when my system boots it goes through the normal boot process until it activates the boot loader. GRUB apears on the screen and then nothing......happens. The system just sits there and I need some ideas or some guidence on how to fix this.

I have been using Mandrake 8.1 but I beleive it would be better for me to run and learn Slackware. Well, at any rate thanks in advance for the help.
:)

[ 07 December 2001: Message edited by: geekzaus ]

[ 07 December 2001: Message edited by: geekzaus ]

[scott_R]

If you have the space, it would be best for you to continue to use your old system, then "upgrade" to another once you become familiar with the new distro, especially with slackware, debian, and other "hard to install" distros. Just create a separate partition, then modify lilo/grub to boot into both.

While I understand your intention to run slackware, you should understand the downsides. While repudately secure, it takes a lot of work to acheive that security. While extremely stable in a knowledgable user's hands, that also takes a lot of time and effort. In other words, slackware is great for learning linux, running a solid system, etc., but you should already know linux inside and out before you install it as your main system.

Assuming from your post that you aren't, I'd recommend reloading your mandrake distro, using that as your main system, and playing with slackware as necessary. That way, when you have a problem (and with slackware being so hands-on, you will at some point), you'll have a back up linux distro. (This is also useful even if you have windows on the same system, as windows is about useless when it comes to fixing a broken linux system, unlike the reverse situation.)

[scanez]

What do you mean nothing happens? Does the GRUB boot screen come up? What happens if you press enter or another key? Does the whole system just freeze? You should be able to press enter if the GRUB boot screen comes up to boot into your default OS, in lilo pressing the tab key will give you a list of choices to boot but I'm not sure if GRUB does that too.

Little more info please :)
SC

[ 07 December 2001: Message edited by: scanez ]

[geekzaus]

sanez, When GRUB appears it seems that the system doesn't lock up. I can hit Enter and it returns a line but nada. So, At that piont I'm scratching my head thinking, hmmmmm?? What's going on. Oh, I must mention that on install I selected LILO as my boot loader and selected it to be put in my MBR. So, That also confuses me.

Scott_R, I really appriciate the guidence. It really makes a lot of since. I don't know how to explain my reasons for wanting to run Slack. #1 I am running Linux on my P2Celeron 500 that is basicly my Linux box. I have tried many different distros just to see what they are like and to find one that challenges me into learning more. #2 My other machine is a AMD 1.4ghz that runs WIN200 (I know, I know) but my wife is a student and is not into the Linux thing.
So, my Linux box is my "toy" and boy I love playing with Linux. 3# So, with that said, Slack is challenging and I like that. Otherwise I would just use windows, which Mandrake reminds me of. So, I am just being adventurous(sp?) And Slack will make me come head to head with the inter-workings of Linux and make me really learn a lot. And that's cool with me.

Have any of you guys ever gotten a new toy and just thought it was so cool, but you ended taking it apart to see how it works?

That's how I am and sometimes it's a curse because I never want to quit!

So, Right now I want to get me Slack to boot so I can begin to use and learn it.

Thanks for the replies guys, I really do appriciate them a great deal!!!!!!!!!!! :)

[jbstew32]

:cool: Slackware :cool:

[Carnel]

Geekzaus, did you create a bootdisk at install time? Please say you did!!! Heh, no matter how confident you get with Linux, always create a boot disk. I have to admit, with Slackware it's either learn, or give up. I've heard it best decribed as something like this:

"Windows has a learning curve of a flat plain, with foothills in the distance. Slackware has a learning curve of a brick wall". Not sure who exactly said it. But credit goes out to them anyways.

In anycase, I do have to agree that Slackware as a first distro can be very... challenging. VERY. Especially if you don't have any previous *nix experience.. anywho. My suggestion in this case, if you don't have a boot disk created, would be to do a reinstall (this time making certain to create a boot disk). Because if you can't get past grub (of which I have no experience with, I use lilo personally), then you're not really losing anything anyways. I am going with the assumtion that you used a CD to install with.

[geekzaus]

Carnel, Yes, I did create the boot disk. that's another thing that confuses me. When I boot with the disk it goes to GRUB again like it isn't even there. Oh, I don't know if I stated before that I selected LILO as my boot-loader and put it in my MBR. So, I can't figure out why I'm getting this msg.

I think scott_R is right, I'll just go back to Mandrake. I mean, there's no need to rush things. I'm probably not ready for Slack yet. :rolleyes:

[bdl]

Something's not right. I noticed that no one even bothered to mention that Slackware doesn't even use GRUB. But Mandrake does. It makes me think that there is some remnant of your old install left over that is still controlling the boot process. It would seem that GRUB is vying for control of the MBR.

Can you describe the change over from MDK to Slackware? Did you install over Mandrake or into a seperate partition? It may be you'll have to run the Slack installation again, this time using a command to 'wipe' the contents of your MBR and also create a bootdisk. If you can provide some more insight as to how you went about the installation, how your drive is partitioned, etc, I'm sure it will be usefull.

[geekzaus]

bdl, When mdk was installed I also used LILO, and the only thing on the hd at that time was mdk. I believe it had the hd partitioned as follows:

hda1/ linux native
hda6/ linux native
hda2/ linux swap

So, when I installed Slack I went through and formated all the drives starting of coarse with the swap and then to the hda1 and hda6. So, that's a good piont about mdk still fighting for the MBR. Because I never told slake to wipe the MBR I just told it to use LILO there. So, Do you think I should totaly reformat the hd and start over installing slack on a fresh drive? And if I do that will Slack set up the hda options I will need during installation? i.e. hda1, 6, 2 etc.

[bdl]

Originally posted by geekzaus:
<STRONG>bdl, When mdk was installed I also used LILO, and the only thing on the hd at that time was mdk. I believe it had the hd partitioned as follows:

hda1/ linux native
hda6/ linux native
hda2/ linux swap

So, when I installed Slack I went through and formated all the drives starting of coarse with the swap and then to the hda1 and hda6. So, that's a good piont about mdk still fighting for the MBR. Because I never told slake to wipe the MBR I just told it to use LILO there. So, Do you think I should totaly reformat the hd and start over installing slack on a fresh drive? And if I do that will Slack set up the hda options I will need during installation? i.e. hda1, 6, 2 etc.</STRONG>


Since you've only got one linux installation going, it makes it quite a bit easier. What I'd do is stick the bootdisk in (or bootable CDROM, whichever) and start the installation process over. In this case, the first thing you're going to do after you get the slackware root prompt is issue the command:

dd if=/dev/zero of=/dev/hda bs=1b count=1

This will wipe the MBR and partition table with zeros, you'll then need to partition the drive as you see fit. If you want, partition it the same way. Some people like to reboot after they've partitioned a drive, you may do that if you like. Then just start the installation and this time, make sure you create a bootdisk. You can install LILO to the MBR at this time (some will disagree with this, but if it's the only OS on the drive, big deal) and then you should be set. Reboot and try the install out. Luck!

[geekzaus]

bdl, sounds like a plan! I really appriciate the help, You Rock!!

I'll let you know how it goes.