Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Mon, 10 Jul 2000, Ron Peterson wrote: > Interesting thread. I just ran into the same problem. > > Every Linux installation I've done to date has autodetected the card(s) > I want to use. If not, recompiling the kernel to include the driver has > done the trick. Except on the machine I'm trying to set up right now... > > Here's my question: how do you know what IRQ and interupt to specify for > your card? The Net3-4 HOWTO tells me that my card's manufacturer The default was mentioned in the email I mentioned. The manufacturer's website might say in other cases. > probably sent me a DOS disk that lets me configure my card. I don't > have that. The card I have is a good old 3COM 509. 3COM's site has no > configuration utilities for the card that I could find either. That's almost always downloadable from the manufacturer. > I'm actually trying to put *two* 509's in this machine, if that makes > any difference (even just one card doesn't work right now, though). You will need to put two *sets* of lines in your conf.module file to specify which card is which, unless it's PCI, and then they will be assigned eth0 and eth1 automatically -- ------------------------------------------------------------------- DDDD David Kramer http://kramer.ne.mediaone.net DK KD DKK D Every non-key attribute depends on the key, the whole key, DK KD and nothing but the key, so help me Codd. DDDD (Sybase training class) - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |