http://cesdis.gsfc.nasa.gov/linux/misc/multicard.html

[Hunkeler, Chris]

Sorry folks.  The original post was in Rich Text and html format.  Here
it is in plain text.  Does anyone know the email address for the
maintainer of the Ethernet HowTo?  gpg109@csc.anu.edu.au doesn't work.

> -----Original Message-----
> From:	Chris Hunkeler [SMTP:hunkeler@netscape.net]
> Sent:	Sunday, April 25, 1999 11:11 AM
> To:	becker@cesdis.gsfc.nasa.gov
> Cc:	gpg109@csc.anu.edu.au; steve@moonglade.com;
> linux-tulip@beowulf.gsfc.nasa.gov
> Subject:	http://cesdis.gsfc.nasa.gov/linux/misc/multicard.html
> 
> I would like to suggest the following addition to the HOWTO. 
> In the section titled "Passing parameters using your boot loader",
> after: 
> IRQ 
>      This entry specifies the IRQ value to be set (on boards with
> software-settable IRQs) or used (on boards with jumpered IRQs). A
> value of '0' means to read the IRQ line from the board (if possible)
> or use autoIRQ if the board doesn't provide a way to read the IRQ. 
> please add: 
> See Resolving Linux PCI Interrupt Conflicts 
> http://cesdis.gsfc.nasa.gov/linux/misc/irq-conflict.html  if your
> board reports IRQ0 or IRQ255. 
>   
> I'm copying this to the tulip mailing list since you can be trying to
> pass parameters until you are blue in the face to get a board to
> recognize the IRQ and it won't happen with a PCI board unless you
> change some settings in the BIOS first.  Most of the documentation
> seems to be on ISA cards but many people are getting PCI cards to try
> set up DSL.  The ISPs don't provide any support and if you dont
> realize what's going on you can go in circles (like Linux idiot newbie
> me did for about 24 hours).  It seems so obvious once you figure it
> out. 
> I'm copying a portion of a message I sent to the maintainer of the
> Ethernet HowTo: 
> I would like to suggest the following addition to the HOWTO. 
> In Section 3.7 
> http://metalab.unc.edu/LDP/HOWTO/Ethernet-HOWTO-3.html#ss3.7  
> Please add under the section titled SIOCSFFLAGS:  Try again: 
> SIOCADDRT:  Network is down. 
> SIOCSIFFLAGS:  Resource temporarily unavailable. 
> I get 'SIOCSIFFLAGS:  Resource temporarily unavailable' when I run
> 'ifconfig ethN'. 
> The IRQ has not been correctly configured for your board.  The driver
> has detected the board but can not access the network until an IRQ is
> available.  Use dmesg|tail to see the startup debug messages.  If your
> board reports IRQ0 or IRQ255, see Section 10.1
> http://metalab.unc.edu/LDP/HOWTO/Ethernet-HOWTO-10.html#ss10.1  for
> ISA cards and Resolving Linux PCI Interrupt Conflicts 
> http://cesdis.gsfc.nasa.gov/linux/misc/irq-conflict.html  for PCI
> cards. 
>   
>