Hi folks,

I must apologize for that question, but I cannot find the slightest information in any of the widely spread documentation of the first Slackware Disk -- and, of course, not in the slackbook:

Prob: LILO does not find any kernel image, since TAB does not show ANYTHING except but the last entry of mine.

What I did before: I made the installation with hugesmp.s with option hda=noprobe. Everything works fine; but: there is not the SLIGHTEST hint what to do at the LILO-Prompt. It is not possible to load the installed system.

It seems to me as if LILO does not recognize the devices as SCSI, but again as IDE.

I would appreciate any idea of you. Thanks a lot.
Heiko

Try booting the system from the installation CD/DVD (it tells you how to boot your system using the kernel from the CD/DVD 'in a pinch'). You may have to pass the hda=noprobe option again. Then, edit /etc/lilo.conf to boot your system properly (the kernel images should use /dev/sd* instead of /dev/hd*) and run `/sbin/lilo` as root. You may need to permanently append hda=noprobe, but I'm not sure since I've never had this problem with my SATA drive. In my /etc/lilo.conf I have the following line (you may not if you chose to use UTF-8...)
If you already have that line, change it to
If not, add
above the "prompt" line (before all of the vga stuff).

I'm not sure if that will help or not -- if not, you'll have to wait for others. That *may* prevent an IDE CD/DVD drive from working -- but I'm not sure. If it does, you'd have to do something else (like use an initrd to load the correct hard drive controller driver before the IDE driver?), but since I'm not knowledgeable enough to suggest something definite (and since I don't have a box with that problem to test on) you'll have to wait for others to help.

Heiko, I'm a little confused, as usual. During the installation you should have entered the location of the kernel /dev/hda2 or /dev/sda2. This information isn't entered automatically although it does display a possible location, if you don't manually type it in that field during installation lilo.conf "root =" will be blank. It also asks for a name for the partition... I usually just type "Slack" or "Linux". Having done all that when I boot my computer my choice is "Slack" or "Linux" and it is displayed in Lilo.


image = /boot/vmlinuz
root = /dev/hda2
label = linux

You can check this by booting installation disk 1 and logging in as root. Create a directory:

mkdir hdrive

mount /dev/hda2 /hdrive

cat /hdrive/etc/lilo.conf

In your case since you are scsi and after reading your previous post it is probably /dev/sda2.

> You may have to pass the hda=noprobe option again.
Yes, I did it nearly eight times today including installation ;-(

> Then, edit /etc/lilo.conf
That file does not exist in this directory. I expected it, but it is not.

> /sbin/lilo
This command is not at this place either. I use Slackware 12.1. I do not know what the problem could be.

Thanks a lot for the very good advices in the rest of your mail. I will give it another very last try after dinner. If not, I will stay with SuSE.

IMHO such an extremely user unfriendly installation routine has nothing to do with learning, but with good design. The instructions are VERY good. But since append="hda=noprobe" is declared as false and until the wrong LILO is still installed and you CANNOT correct it, I do not know what these unnecessary difficulties are aimed to.

I understand more and more why Linus T. uses openSuSE. ;-)
Although the whole idea of Slackware ist sympathetic.

Cheers
Heiko

You're not listening. You can boot up your physical installed system using just the kernel on the CD. DO NOT just press enter at the boot: prompt. You must enter the line displayed on the screen to boot your system 'in a pinch'. At the boot: prompt of the install CD/DVD, enter the following:
where /dev/sda1 points to the root partition of your Slackware installation (change it if /dev/sda1 is not correct -- it could be /dev/sda2, /dev/hda1, etc. It should probably be /dev/sd* since it is an SATA drive.) You will probably also have to pass the hda=noprobe option here. I'm not entirely sure of the syntax, but it should probably be something like
If there is no /etc/lilo.conf or no /sbin/lilo, then either you haven't actually installed Slackware or you're not using your actual Slackware install and are instead still just using the LiveCD (ie you booted incorrectly).
I don't mean to sound rude, but this is your problem and not the installer's. Slackware does things differently. You are *required* to read CHANGES_AND_HINTS.TXT before installing unless you like having problems. It tells you exactly how to fix your problem. I personally have never had any trouble with Slackware's installer and wouldn't call it user-unfriendly. It involves a nice, step-by-step process in which you have total control. By making the installer a simple script, you could edit it yourself if you want to change either the installer or certain options. This is what Slackware is good at -- allowing you to do whatever you want with your system. If you like OpenSuSE, that's fine. But Slackware and OpenSuSE have completely different philosophies. You need to be willing to read to install Slackware and hopefully have at least some form of problem-solving skills.

I would be more than willing to continue to help you, but you must at least be willing, and you should also search the web, these forums, and the official Slackware documentation located on the root directory of the install CD/DVD if you expect to solve your problems.

Heiko Schroeder,

You don't need to come to the Slackware forum complaining because
you don't like the way Slackware is configured. Lots of guys use it
with zero problems. Reading is a must. If you prefer point-and-click,
and SuSE works that way, use it ... or use Windows. But don't come
here and troll, okay? This is not the first thread where you asked for help with
Slack while complaining about it.

Read the Slackware-HOWTO and other docs.

Hi,

I would like to add to this thread that the OP could do a search on Google/Linux or LQ Slackware forum. He would find loads of information similar to his problems.

I would suggest that the OP read the documentation that PV has provided; Announce 12.1, Slackware-Howto, CHANGES_AND_HINTS.TXT, UPGRADE.TXT. Plus the other text files relevant to your needs.