Slack not starting!!!
 

So I wanted some challenge and I burned myself Slackware 8.1 with Nero, then I went to test machine (266mhz/64mhz Ram), threw cd in, installed (I did it lazy way: everything except KDE & Gnome.)

So I booted it as it told me to do with ctrl-alt-del, and waited... and waited... I waited unbelievable long time and finally it printed out LI. Can you believe it???? After one cd, 6 hours dl time, patient waiting and instruction reading while installing, that retarded program included nothing more than half of word LILO!!! :mad:

And I know that comp is bare.i, not some scsi.i, so I had right kernel selected!

WTF is wrong with these programs?

:) Hehe... I'm not laughing at you, I like your signature, it makes me laugh.

Anyways, did you create a boot disk, you know for when things like this happens so you can boot into Slack to fix it ?

If not, that is ok cause you should be able to boot with the cd you just made and installed with.

With the cd, just act like your going to boot with it but at the boot: prompt type this:

linux root=/dev/hdxx (Where the two xx's are where you have the root partition located.. like on your primary hard drive, if it was the first parititon, it would be /dev/hda1 and so on.. )

Then if you get booted up, give us a listing of fdisk -l and your /etc/lilo.conf to help you get your system working for ya.

Ok, here it is
 

Thank you very, very much. I managed to boot it now.

Here is all essential from fdisk -l:
hda1 has Bootable flag ON, it's type is Linux and code number 83. (Seems right for me...)
hda2has Bootable flag OFF, it's type is Linux swap and code number 82. (Seems right again)

Here is all essential from /etc/lilo.conf:
image = /boot/vmlinuz
root = /dev/hda1
label = Linux
read only

My suspects go with first line of lilo.conf... Whatta hell is vmlinuz?
Anyway it seems to make sense (at least for me, I've been using only mandy for ½ year)

BTW, I need some help now:
I opened lilo.conf with vim, and now I'm stuck. I managed to delete some characters from end of file (only comments, but still), and now I would like to undo/write them back and exit vim, but nothing seems to do the job :(

Slackware HC continues until I myself find solid prove of it's betterness!!! Battle!!! :D

In vi hit Esc, and type
:q! it will quit vi witout changes made to the file, also while editing the file press Esc and press u it will undo teh last change, press u one more time - one more change is undone, follow the pattern?
Now, vmlinuz - is the actual compiled kernel

And what does "the actual compiled kernel" means?
Do I need to recompile it or what? Doesn't the Slackware installation program compile it readily or do I have to do it manually or do I need to change place of image?

More complete answers please... :tisk:

BTW, my engineer steph-father claimed that I should install LILO to MBR, but as installation program told it's "propably unsafe", I didn't do it. But does he have the point? Should I reinstall?

By the "actual compiled kernel" I meant this is the core of your operating system - kernel, if you want more terse explanation you should contact a dictionary
As for LILO question it is OK to put it on MBR this is the most common option on a single boot PC (even on some dualboots)
You might need to recompile your kernel because by default it is stripped down, so some components may not work from the start (like sound cards, raid controllers, etc), I think you've been here long enough to know how to recompile the kernel, right?

You might want to make sure where the actual kernel resides. I know on my Slack systems, its just sitting on the / directory.. basically instead of /boot/vmlinuz mine points to /vmlinuz.

It would appear that tricky is running 8.0 or less, because each time I have installed 8.1 it puts all the boot info (the kernel etc) into /boot, that would include vmlinuz.

Eits0, don't get so irritated when nice people like Neo tell you a good answer.

vmlinuz would appear to be a renamed bzImage (or congruent) kernel file. You can do that, no problems. Just make sure your lilo reflects it.

Cool

Well The vmlinuz part should be right, because since Slack8.1 the Kernel image is placed in the /boot directory.

Also when you chose to install LILO, did you install it the MBR or the First section of your boot partition?

If you did it to the first section of the boot partition, then maybe it didn't get installed on the first 1024 blocks of the cyclender, and you will need to add this to the beginning of your lilo.conf:

lba32

then after you save, run this in the command prompt:

/sbin/lilo

Thanks for support Master :), I wasn't trying to irritate fellow LQers, but the whole thing is getting crippled on me, my fscking ISP is trying to cut the wire, then my Altec Lansing sub went smoking pot and now it is dead - drugs are bad (I don't do it :), sub did; all the other goop is gathering in a snowball, oh at least it is a weekend already.

Damn, hell came crashing into your front door eh? That always sucks, I would disconnect the phone, turn out the lights, warm up some milk (or hot cocoa) and snuggle up to a nice calm evening with LQ in front of me, or a good Spy film.

Hope tomorrow is much better for ya! You too Eits0, hopefully you can get Slack to work a little better for you as well.

;)

I got it!

I reinstalled as previously, but chaged fs to ext3, put LILO to MBR instead of First section of hda1 as before.

OK, I'am allmost ready to change my sig. X (whatsoever, especially GNOME) starts lot faster and works better too (3 hours experience now ;) ).
Als system starts up faster than Mandrakes did.

Now, I might exceed 1000th post limit quite soon, as my adventures continue!
Don't give me answers now, but this is what I would like to learn at this time with Slack:
1) How to install BlackBox
2) How to make it start to BlackBox immediately
3) How to make connection between windows machine and Slack
4) How to use wine to install and play games.

I've got short but cumbersome path to go for now... :)

Oh yeah, another Slack convert! You have felt the darkside (or darkstar, your choice), and now cannot resist!

Glad you got it fixed buddy, good job.

Cool

Cool . I had converted to Slackware too!!