Topic: promise ultra 100 controller

[Bob]

Hi,

I have installed the mentioned controllercard, and with the help of what is in this and other fora, I am now able to mount my 40 GB disk which is connected to the card. The problem is that I can only get it to work when I manually add commands to lilo when it boots (boot: esmith ide2=.... etc.).
If I change lilo.conf the way it is supposed to be done (append="ide3=... etc), then it will not work.
Also, when I look at the boot messages I can see the 40 GB disk is detected when it is done manually, but not when I try it changing lilo.conf...

[Eric Martin]

Is this your primary HDD that the OS resides on?  If it isn't, add the entry to the /etc/fstab with an entry like this:

"/dev/hdb1 /home/e-smith/files/newdrive ext2 defaults 1 2"

If it's your primary drive...ummm...I'm not sure...

[Bob]

Thanks Eric,

No it is not my primary drive. It's a drive that only contains user data.
I also had put a correct line in fstab, but if the controller does not get recognized in the first place, so the system will not boot up completely, and gives me a shell to fix the 'error'.
Anyhow, the problem lies in lilo I think, because when I boot and type in the correct i/o addresses manually, the controller and the connected drive is recognized. I can then mount the drive manually and use it as an ibay. The thing that doesn't work is changing lilo.conf to get it all going automatically every time I start the system.

[Bob]

Solved!

I am not completely sure what solved it, but I noticed from dmesg that I had made a typing error in the io-address in lilo.conf. Also, and I think this is more important, I put in an extra space in the added line in lilo.conf :
before it was:

append="ide2=0xc400....etc..."

and must be:

append=" ide2=0xc400....etc..."

so, there must be a space after the first "

The reason why I think that this was the error and not the typing mistake I made is that I tried changing lilo.conf several times earlier today, and it is unlikely that I made typing errors every time.....

Now it's time to play with hdparm to see how it's performing...