Topic: lilo.conf boot problem

[Tony]

I am trying to add the append command to my lilo.conf file.
I can't get it to work. I have tried the following with my setting and the lilo.conf file will not update.

5. Make certain that you Add the "append" command to your
lilo.conf follow the examaple below:

image=/boot/vmlinuz-2.2.14-5.0
label=linux
read-only
root=/dev/hde9
append="ide2=0x9400, 0x9002 ide3=0x8800, 0x8402"

NOTE: Make certain always, whenever you modify your
lilo.conf file be sure to run /sbin/lilo as root to
reinstall lilo or you may not be able to reboot. To insure a
flawless install make certain that there is no resource
sharing from the start of the installation to insure a
flawless install.

[Chris O'Donovan]

I'm not sure what you mean when you say the "lilo.conf file will not update". Are you editing it as root?

If so, what does lilo say when you run it?

Chris

[Charlie Brady]

Tony wrote:
 
> image=/boot/vmlinuz-2.2.14-5.0
> label=linux
> read-only
> root=/dev/hde9
> append="ide2=0x9400, 0x9002 ide3=0x8800, 0x8402"

This is wrong. That line should be:

append="ide2=0x9400,0x9002 ide3=0x8800,0x8402"

i.e. with no spaces after the commas.

Charlie

P.S. You kernel version 2.2.14-5 is very old.

[aniston]

Hello Tony,

you can even check your lilo.conf syntax with

/sbin/lilo -t and it should tell you if everything is typed in correctly (syntax wise)

else it wil tell you the line number that the syntax is worng at.

** remember to run  /sbin/lilo if you do not get any errors.

finally it seems like you are trying to use the IDE onboard controllers either the Promise fast trak 100 or the Highpoint HPT 370 ... did you check and try the append manually durning the real boot process of esmith by hitting "ctrl-x" when you see the e-smith logo and then typing your kernel command like

esmith ide2=0x9400, 0x9002 ide3=0x8800, 0x8402

if the boot-up is succesful then only add the same line to your lilo.conf else check the /proc7pci for the correct numbers

eg: my gigabyte 1U rack takes ide2=0xdc00, 0xd802 ide3=0xd400, 0xd002 with its RAID disks on hde and hdg 8it was quite tricky getting them to sit in RAID 1 thru the linux s/w RAID)

By the way any ideas on how to enable the ft.o driver for the Promise fasttrak 100 driver module ? I am getting bad performance as of now as the driver module is not loaded, check this hdparm tests...

hdparm  -Tt /dev/hde

/dev/hde:
 Timing buffer-cache reads:   128 MB in  1.31 seconds = 97.71 MB/sec
 Timing buffered disk reads:  64 MB in  6.80 seconds =  9.41 MB/sec

doing hdparm -d /dev/hde also revealed thet the DMA option could not be set.

the Promise website has drivers for the following kernels only ...

Support List
       Red Hat 6.2           (2.2.14-5.0)
       Red Hat 6.2-OEM  (2.2.14-6.1.1)
       Red Hat 7.0           (2.2.16-22)
       Red Hat 7.1           (2.4.2-2)

doing an insmod after copying the RH 7.0 ft.o smp driver into /lib/modules/2.2.19-7.0.8smp/scsi (as I'm trying a dual CPU rack server) gives the obvious following error...

insmod ft.o
ft.o: unresolved symbol scsi_register_Rsmp666432ca
ft.o: unresolved symbol interruptible_sleep_on_Rsmp1ad2510f
ft.o: unresolved symbol __wake_up_Rsmp983d74e1

So to sum up all is there any way to recompile the driver for the current kernel 2.2.19-7.0.8smp in SME v5 ?

regards,
aniston.