Hi,
If the card has a FCC ID number (98 % do )you can search for it at.
http://www.fcc.gov/oet/fccid/
find out the manufactures name, and try their support web page (if exists).
You probably wont get a linux driver but you should be able to id the card.
or get jumper info or setup programs.
Have fun,
John Rogers
email [EMAIL PROTECTED]
> -----Original Message-----
> From: Ray Olszewski [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, 24 May 2000 2:33
> To: David Aikema; [EMAIL PROTECTED]
> Subject: Re: ethernet cards
>
>
> Identifying an "anonymous" NIC is a tough problem. Some NICs are well
> labelsd, so I'm inclined to think it isn't a 3Com or an HP,
> say. Others are
> rougher to classify.
>
> No sure procedure, but here are a few things to try;
>
> 1. Boot the system with a recent Red Hat install disk. RH has
> the best NIC
> autodetector I've found. (Even though I *never* install RH, I
> keep a RH
> install disk in my troubeshooting kit for this one reason.)
>
> 2. Put it in a regular Linux system, whatever distribution
> you are using,
> and work your way through the modules, modprobe'ing them one
> by one, until
> you get lucky. This will work if you have a card that uses a
> module that
> autoprobes for IRQ and IO port.
>
> 3. Take a chance (Advance to Boardwalk; pay the property
> owner twice the
> usual rent), and bet that an unknown isa-bus card is NE2000
> compatible. This
> one does require parameters, so you'll have to do a bunch,
> varying the irq=
> and io= lines over the likely range (mostly the irq= one; the
> odds are high
> that an NE2000 is set for io=0x300).
>
> 4. Same principle for unknown pci-bus cards, except try ne2k
> and tulip.
>
> This isn't great advice, I'll admit, but it's all I've got.
> If you could get
> the MAC address of the card, there's a database somewhere
> that associated
> the first 4 digits with a manfacturer ... but if you could
> read the MAC
> address, you could use the card.
>
> At 10:48 PM 5/23/00 -0400, David Aikema wrote:
> >Basically I've been having quite a time trying to get my
> network everywhere
> card to work under linux with absolutely no success. Others have also
> encountered this same problem judging by the data returned
> from searches on
> the internet.
> >
> >I am beginning to think that the only way to get beyond this
> problem is
> somply to replace the network card. I talked to my sysadmin
> at school and
> he offered me several spare cards that had accumulated over
> the years....
> currently I have 2 10baseT cards and two 10/100 cards.
> >
> >The only card that actually included a driver disk was one
> of the fast
> ethernet cards... upon which was the label 'Acer ALN-320'.
> Has anyone had
> any success in getting this card running under linux?
> >
> >Alternatively... how can I identify the other cards without
> any really
> clear, distinct labels? there's enough different numbers,
> etc. on those
> things that i am not sure which ones to look at.
>
> ------------------------------------"Never tell me the odds!"---
> Ray Olszewski -- Han Solo
> Palo Alto, CA [EMAIL PROTECTED]
> ----------------------------------------------------------------
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-newbie" in
> the body of a message to [EMAIL PROTECTED]
> Please read the FAQ at http://www.linux-learn.org/faqs
>
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
