MLUG: [UUG/MLUG] Interrupt Conflicts
[UUG/MLUG] Interrupt Conflicts
Email address obfuscation in effect -- please click here to turn it off.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
As a followup to my own question, here is an extract from the output of
DMESG:
________________________________________________________
aha152x: processing commandline: ok
aha152x: BIOS test: passed, detected 1 controller(s)
aha152x0: vital data: PORTBASE=0x340, IRQ=3, SCSI ID=7, reconnect=enabled,
parity=enabled, synchronous=disabled, delay=100, extended
translation=disabled
aha152x: trying software interrupt, ok.
scsi0 : Adaptec 152x SCSI driver; $Revision: 1.7 $
scsi : 1 host.
.
.
.
3c574_cs.c v1.08 9/24/98 Donald Becker/David Hinds,
EMAIL:PROTECTED
eth0: 3Com 3c574 at I/O 0x300, IRQ 3, MAC Address 00:00:86:1D:29:55.
eth0:  No acceleration memory window.
  64K FIFO split 1:1 Rx:Tx, autoselect MII interface.
  MII transceiver at index 32, status 7809.
tty01 at 0x02f8 (irq = 3) is a 16550A
eth0: MII #0 status 7809, link partner capability 0000, setting half-duplex.
______________________________________________________________
Notice that they are both using IRQ3.

One of the RedHat FAQ pages has:
Q. How can I boot without typing in "ahaxxxx=nn,nn,nn" every time? 
Where a disk device cannot be autodetected it is necessary to supply the
kernel with a command device parameter string, such as: 
	        aha152x=0x340,11,3,1
This parameter string can be supplied in several ways using LILO: 
*	By entering it on the command line every time the system is booted
via LILO. This is boring, though. 
*	By using the LILO ``lock'' keyword to make it store the command line
as the default command line, so that LILO will use the same options every
time it boots. 
*	By using the append= statement in the LILO config file. Note that
the parameter string must be enclosed in quotes. 
For example, a sample command line using the above parameter string would
be: 
	        zImage  aha152x=0x340,11,3,1 root=/dev/sda1 lock
This would pass the device parameter string through, and also ask the kernel
to set the root device to /dev/sda1 and save the whole command line and
reuse it for all future boots. 
A sample APPEND statement is: 
	        APPEND = "aha152x=0x340,11,3,1"
Note that the parameter string must NOT be enclosed in quotes on the command
line, but it MUST be enclosed in quotes in the APPEND statement. 
Note also that for the parameter string to be acted on, the kernel must
contain the driver for that disk type. If it does not, then there is nothing
listening for the parameter string, and you will have to rebuild the kernel
to include the required driver. For details on rebuilding the kernel, cd to
/usr/src/linux and read the README, and read the Linux FAQ and Installation
HOWTO. Alternatively you could obtain a generic kernel for the disk type and
install that. 
Readers are strongly urged to read the LILO documentation before
experimenting with LILO installation. Incautious use of the BOOT statement
can damage partitions. 
______________________________________________________________________

Being new to Linux, I can probably enter the string on the command line.
I do not know anything about the "lock" keyword.
I do not know what LILO config file to put the "append=" statement into.
Finally, I do not know what they mean by:
	        zImage  aha152x=0x340,11,3,1 root=/dev/sda1 lock

Any help would be appreciated.