Re: NIC identification

2001-03-19 Thread Dave Sherohman
On Mon, Mar 19, 2001 at 11:43:47AM -0600, Keith G. Murphy wrote:
> I concur, and add that if it just *happens* to be an Optiplex GX1, it's
> probably a 3Com 3c905B-TX.  There is a Linux driver for that, 3c59x by
> name.

Optiplex GX100.  According to one of the Dell discussion forums, it's
a 3c920, which is supposed to be fully compatible with the 3c905c.
I'm guessing that either it's a bad NIC or (much more likely) the CD
I'm using is a bit too old, as the 3c59x driver refuses to load for me.

Time to make some floppies and see if the current driver likes it...

-- 
Linux will do for applications what the Internet did for networks. 
- IBM, "Peace, Love, and Linux"
Geek Code 3.1:  GCS d? s+: a- C++ UL++$ P++>+++ L+++> E- W--(++) N+ o+
!K w---$ O M- V? PS+ PE Y+ PGP t 5++ X+ R++ tv b+ DI D G e* h+ r y+



Re: NIC identification

2001-03-19 Thread Keith G. Murphy
"Brooks R. Robinson" wrote:
> 
> > the kernel with the correct modules for the card. You should be able to
> > get the info you need from Dell, especially since they are now
> > supporting Linux on many of their systems. They may have a driver/module
> 
> This seems to be your best idea.  Your box should have a number on it that
> you can plug into the web interface and it will tell you about your machine
> specifically.  Once you have an idea what the true hardware is, it'll be
> easier.
> 
I concur, and add that if it just *happens* to be an Optiplex GX1, it's
probably a 3Com 3c905B-TX.  There is a Linux driver for that, 3c59x by
name.



Re: NIC identification

2001-03-19 Thread Dave Sherohman
On Mon, Mar 19, 2001 at 10:06:28AM -0500, Hall Stevenson wrote:
> > /proc/bus/pci is there and contains two files (00 and 01), but
> > they're binary data.  The kernel is 2.2.12, which should support

> I'm not familiar with "devfs" at all, but are you using it, by chance ??

Nope.  It's a 2.2.12 kernel and devfs wasn't introduced until 2.4.  (And with
the problems I've seen other people here having with it, I'm not real
interested in trying devfs any time soon.)

> Also, I believe the "/proc" filesystem is a kernel option. You may not
> have it enabled.

/proc is there, it just doesn't include a pci (pseudo-)file/dir.

Looks like I'll have to wade through Dell's site to find the info.

-- 
Linux will do for applications what the Internet did for networks. 
- IBM, "Peace, Love, and Linux"
Geek Code 3.1:  GCS d? s+: a- C++ UL++$ P++>+++ L+++> E- W--(++) N+ o+
!K w---$ O M- V? PS+ PE Y+ PGP t 5++ X+ R++ tv b+ DI D G e* h+ r y+



Re: NIC identification

2001-03-19 Thread Hall Stevenson
> On Fri, Mar 16, 2001 at 12:52:54PM -0500, Hall Stevenson wrote:
> > The NIC is likely a PCI device even when it's integrated
> > into the MB. So, try "cat /proc/pci" and look for an "ethernet
> > controller" line. It will probably give you the chipset it uses
> > which is usually a pretty good starting point.
>
> I am really growing to hate this machine...
>
> hudson:~# cat /proc/pci
> cat: /proc/pci: No such file or directory
>
> /proc/bus/pci is there and contains two files (00 and 01), but
> they're binary data.  The kernel is 2.2.12, which should support
> /proc/pci, IIRC.  (Yeah, I know...  I really should be using a potato
> CD, but slink is all I had handy.)

I'm not familiar with "devfs" at all, but are you using it, by chance ??
Also, I believe the "/proc" filesystem is a kernel option. You may not
have it enabled.

Regards
Hall




RE: NIC identification

2001-03-19 Thread Brooks R. Robinson
> the kernel with the correct modules for the card. You should be able to
> get the info you need from Dell, especially since they are now
> supporting Linux on many of their systems. They may have a driver/module

This seems to be your best idea.  Your box should have a number on it that
you can plug into the web interface and it will tell you about your machine
specifically.  Once you have an idea what the true hardware is, it'll be
easier.

Brooks



Re: NIC identification

2001-03-19 Thread Dave Sherohman
On Fri, Mar 16, 2001 at 12:52:54PM -0500, Hall Stevenson wrote:
> The NIC is likely a PCI device even when it's integrated into the MB.
> So, try "cat /proc/pci" and look for an "ethernet controller" line. It
> will probably give you the chipset it uses which is usually a pretty
> good starting point.

I am really growing to hate this machine...

hudson:~# cat /proc/pci
cat: /proc/pci: No such file or directory

/proc/bus/pci is there and contains two files (00 and 01), but they're binary
data.  The kernel is 2.2.12, which should support /proc/pci, IIRC.  (Yeah, I
know...  I really should be using a potato CD, but slink is all I had handy.)

-- 
Linux will do for applications what the Internet did for networks. 
- IBM, "Peace, Love, and Linux"
Geek Code 3.1:  GCS d? s+: a- C++ UL++$ P++>+++ L+++> E- W--(++) N+ o+
!K w---$ O M- V? PS+ PE Y+ PGP t 5++ X+ R++ tv b+ DI D G e* h+ r y+



Re: NIC identification

2001-03-17 Thread b3
On Fri, Mar 16, 2001 at 12:52:54PM -0500, Hall Stevenson wrote:
> > I've got a Dell box I'm installing debian on with an intergrated
> > NIC on the motherboard.
> 
> The NIC is likely a PCI device even when it's integrated into the MB.
> So, try "cat /proc/pci" and look for an "ethernet controller" line. It
> will probably give you the chipset it uses which is usually a pretty
> good starting point.

(just to add a bit) If it doesn't tell you the exact chipset, it may
give you a vendor and model ID - there's a good chance you can figure
out the chipset from this.  Just do a search on Google for:

vendor  model  ethernet

This has helped me identify many a piece of otherwise unidentifiable
hardware =)

-b3



Re: NIC identification

2001-03-16 Thread Dave Sherohman
On Fri, Mar 16, 2001 at 09:15:52PM -0400, Roberto Rosario wrote:
> Try lspci it might give you some more info.

Tried it, but it's not there.  The current version available for download off
debian.org depends on a later version of libc than was installed off my CD
and I don't want to mess with sneakernetting enough stuff over to upgrade
that and everything that depends on it.

I will try the suggestion of catting /proc/pci on Monday, though.

-- 
Linux will do for applications what the Internet did for networks. 
- IBM, "Peace, Love, and Linux"
Geek Code 3.1:  GCS d? s+: a- C++ UL++$ P++>+++ L+++> E- W--(++) N+ o+
!K w---$ O M- V? PS+ PE Y+ PGP t 5++ X+ R++ tv b+ DI D G e* h+ r y+



Re: NIC identification

2001-03-16 Thread Roberto Rosario

Try lspci it might give you some more info.

Dave Sherohman wrote:

> On Fri, Mar 16, 2001 at 01:59:04PM -0600, John Foster wrote:
> > Look for Realtek, 3com, intel, i.e.
> > something with a ethernet card name and model number. Once you have
> > identified the chipset you can recompile the kernel and modules for your
> > specefic hardware setup.
>
> I'm guessing it's a 3com NIC (Why?  There's a largish chip labeled "3com
> 40-0579-006" near the rj45.), but none of the 3com drivers on the install
> disc recognize it.
>
> > What are you installing from? Since I see no indication of dialup
> > connections to the internet via modem, I hope it is via cdrom not
> > flopppy disks.
>
> Oh, it's off CD.  No need to worry about that...  I've done debian installs
> via modem before and they don't rate highly on the list of things I'd want to
> do again.
>
> --
> Linux will do for applications what the Internet did for networks.
> - IBM, "Peace, Love, and Linux"
> Geek Code 3.1:  GCS d? s+: a- C++ UL++$ P++>+++ L+++> E- W--(++) N+ o+
> !K w---$ O M- V? PS+ PE Y+ PGP t 5++ X+ R++ tv b+ DI D G e* h+ r y+
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: NIC identification

2001-03-16 Thread Hall Stevenson
> I've got a Dell box I'm installing debian on with an intergrated
> NIC on the motherboard.

The NIC is likely a PCI device even when it's integrated into the MB.
So, try "cat /proc/pci" and look for an "ethernet controller" line. It
will probably give you the chipset it uses which is usually a pretty
good starting point.

Hall



Re: NIC identification

2001-03-16 Thread Dave Sherohman
On Fri, Mar 16, 2001 at 01:59:04PM -0600, John Foster wrote:
> Look for Realtek, 3com, intel, i.e.
> something with a ethernet card name and model number. Once you have
> identified the chipset you can recompile the kernel and modules for your
> specefic hardware setup.

I'm guessing it's a 3com NIC (Why?  There's a largish chip labeled "3com
40-0579-006" near the rj45.), but none of the 3com drivers on the install
disc recognize it.

> What are you installing from? Since I see no indication of dialup
> connections to the internet via modem, I hope it is via cdrom not
> flopppy disks.

Oh, it's off CD.  No need to worry about that...  I've done debian installs
via modem before and they don't rate highly on the list of things I'd want to
do again.

-- 
Linux will do for applications what the Internet did for networks. 
- IBM, "Peace, Love, and Linux"
Geek Code 3.1:  GCS d? s+: a- C++ UL++$ P++>+++ L+++> E- W--(++) N+ o+
!K w---$ O M- V? PS+ PE Y+ PGP t 5++ X+ R++ tv b+ DI D G e* h+ r y+



Re: NIC identification

2001-03-16 Thread John Foster
Dave Sherohman wrote:
As I suspected the kernel is not trying to load a kernel module for the
NIC, everything else looks OK. My suggestion is to contact Dell and
query them about the onboard NIC chip set. They may have the specs
listed on their website. It is likely that the board is made to their
specs (saves them big bucks) and the NIC may only be identifiable by the
chip set name and model. Alternatively if you have windows also
installed check in the start; control panel; settings; systems; menu and
look at the network card setting there...that should show the card/chip
set and model number as a driver. Look for Realtek, 3com, intel, i.e.
something with a ethernet card name and model number. Once you have
identified the chipset you can recompile the kernel and modules for your
specefic hardware setup. Try to find out also about any other onboard
components such as video chipset, sound chipset and hard drive
controller chipsets. These are all very likely built in and the
performance may be improved significantly when you recompile a new
kernel.
What are you installing from? Since I see no indication of dialup
connections to the internet via modem, I hope it is via cdrom not
flopppy disks. You will need to have several applications installed in
order to recompile the kernel.
-- 
We specialize in multi-processor computing systems!
John Foster
AdVance-Computing Systems



Re: NIC identification

2001-03-16 Thread Dave Sherohman
On Fri, Mar 16, 2001 at 11:10:33AM -0600, John Foster wrote:
> Dave Sherohman wrote:
> > ide0 at 0x1f0-0x1f7 on irq 14
> 
> This is your hard drive :-)

*sigh*  Uh-huh.  I knew that...  Of course ide0 != eth0.  Guess I was just a
little too desperate for info on eth0 and turned temporarily dyslexic or
something.

> send us the output from "dmesg"

Linux version 2.2.12 ([EMAIL PROTECTED]) (gcc version 2.7.2.3) #2 Thu Aug 26
11:46:26 PDT 1999
Detected 462825985 Hz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 462.03 BogoMIPS
Memory: 126376k/129664k available (1244k kernel code, 416k reserved, 1528k
data, 100k init)
CPU: Intel Celeron (Mendocino) stepping 05
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
Checking for popad bug... OK.
POSIX conformance testing by UNIFIX
PCI: PCI BIOS revision 2.10 entry at 0xfc0ce
PCI: Using configuration type 1
PCI: Probing PCI hardware
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
Starting kswapd v 1.5 
Detected PS/2 Mouse Port.
RAM disk driver initialized:  16 RAM disks of 4096K size
loop: registered device at major 7
PCI_IDE: unknown IDE controller on PCI bus 00 device f9, VID=8086, DID=2411
PCI_IDE: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio
hda: WDC WD43AA, ATA DISK drive
hdb: CD-ROM Drive/F5E, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: WDC WD43AA, 4112MB w/2048kB Cache, CHS=524/255/63
hdb: ATAPI 56X CD-ROM drive, 128kB Cache
Uniform CDROM driver Revision: 2.55
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8
NCR53c406a: no available ports found
Failed initialization of WD-7000 SCSI card!
megaraid: v1.04 (August 16, 1999)
scsi : 0 hosts.
scsi : detected total.
Partition check:
 hda: hda1 hda2
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 100k freed
Adding Swap: 265064k swap-space (priority -1)
Serial driver version 4.27 with no serial options enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A

> for the onboard NIC that you will require. Such is the hardship of
> integrated systems.

Indeed.  I bought one a couple years back and never intend to repeat the
mistake.  (I knew it was a bad idea at the time, but the price was so
good...)  This one was inherited when I started a new job.

-- 
Linux will do for applications what the Internet did for networks. 
- IBM, "Peace, Love, and Linux"
Geek Code 3.1:  GCS d? s+: a- C++ UL++$ P++>+++ L+++> E- W--(++) N+ o+
!K w---$ O M- V? PS+ PE Y+ PGP t 5++ X+ R++ tv b+ DI D G e* h+ r y+



Re: NIC identification

2001-03-16 Thread John Foster
Dave Sherohman wrote:
> 
> I've got a Dell box I'm installing debian on with an intergrated NIC on the
> motherboard.  When I booted the install CD, the system startup messages
> included
> 
> ide0 at 0x1f0-0x1f7 on irq 14

This is your hard drive :-)
> 
> so I figured, "Great!  It's been autodetected, so I don't have to worry about
> what it actually is!"
> 
> I was wrong.  When it booted off the hard drive, the same message was
> displayed in the startup sequence, but eth0 isn't there:
-

send us the output from "dmesg"

 
> hudson:~# ifconfig eth0 up
> eth0: unknown interface: Operation not supported by device
> 
> Where would I start looking to determine what the appropriate module/settings
> for this card would be?
---
you must select the card when you install Debian originally or recompile
the kernel with the correct modules for the card. You should be able to
get the info you need from Dell, especially since they are now
supporting Linux on many of their systems. They may have a driver/module
for the onboard NIC that you will require. Such is the hardship of
integrated systems.
-- 
We specialize in multi-processor computing systems!
John Foster
AdVance-Computing Systems



RE: NIC identification

2001-01-17 Thread John Galt

Assuming, of course, that he got the card up, which leads us back to his
original problem

On Wed, 17 Jan 2001, Joris Lambrecht wrote:

>eh, won't it show when typing ifconfig with one or more options ?
>
>-Original Message-
>From: Casey Webster [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, January 17, 2001 2:26 PM
>To: John Griffiths
>Cc: debian-user@lists.debian.org
>Subject: Re: NIC identification
>
>
>often they will pe printed onto th card, or printed onto a sticker that is
>placed on the card or one of the chips on the card, it will be a in the
>form: 00:01:02:70:5E:B1 or possbile without the colons, but it will
>contain that many digits.  The first 6 numbers (00:01:02) identify the
>vendor, and i this case thats 3com (3c905-c-txm)
>
>-Casey
>
>On Wed, 17 Jan 2001, John Griffiths wrote:
>
>> At 11:38 PM 1/16/2001 -0600, Casey Webster wrote:
>> >if its netware approved you might try the ne2k driver, that thing works
>> >for a lot of cards with that sticker, also if you can figure out the
>> >card's MAC address (in the form of xx:xx:xx:yy:yy:yy and often on the
>card
>> >somewhere) then search google for a MAC address to vendor converter and
>> >pop on the xx:xx:xx from the mac addr and it will give you the vendor of
>> >the card and then you can check thier website for the model number and
>try
>> >and figure out what driver to use
>> >
>> >-Casey
>> well the things we learn..
>> 
>> any ideas what the MAC might look like? where it may be?
>> 
>> 
>> -- 
>> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
>> with a subject of "unsubscribe". Trouble? Contact
>[EMAIL PROTECTED]
>> 
>
>
>

-- 
Pardon me, but you have obviously mistaken me for someone who gives a
damn.
email [EMAIL PROTECTED]



Re: NIC identification

2001-01-17 Thread John Galt

>From the thinnet connector on it, I'd try ne2k-pci.  Hell, what do you
have to lose?  The netware sitcker also implies ne2k: IIRC the netware
sticker meant ne2000 compliance...

modprobe ne2k-pci

On Wed, 17 Jan 2001, John Griffiths wrote:

>OK i've got a NIC that i need to get working.
>
>its PCI appears to support Co-ax as well as cat-45
>
>it has a netware approved sticker on it
>
>it has 3 components on it made by Delta
>
>the most comprehensible component proclaims itself to be 
>
>Delta LANF7236 9701F
>
>has anyone got any ideas what driver i should use?
>
>it has worked with slackware (which does auto-detect) but the HD it was 
>working with has gone to heaven.
>
>thanks for any help that can be proferred
>
>John
>
>
>

-- 
Pardon me, but you have obviously mistaken me for someone who gives a
damn.
email [EMAIL PROTECTED]



RE: NIC identification

2001-01-17 Thread robin . c . smith
If you want to find the vendor of any piece of eletrical equipment and you
can find the FCC code on it then go to http://www.fcc.gov/oet/fccid/ and
type that number in.

Works every time

Robin

-Original Message-
From: Sebastiaan [mailto:[EMAIL PROTECTED]
Sent: 17 January 2001 16:17
To: John Griffiths
Cc: Casey Webster; debian-user@lists.debian.org
Subject: Re: NIC identification


On Wed, 17 Jan 2001, John Griffiths wrote:

> At 11:38 PM 1/16/2001 -0600, Casey Webster wrote:
> >if its netware approved you might try the ne2k driver, that thing works
> >for a lot of cards with that sticker, also if you can figure out the
> >card's MAC address (in the form of xx:xx:xx:yy:yy:yy and often on the
card
> >somewhere) then search google for a MAC address to vendor converter and
> >pop on the xx:xx:xx from the mac addr and it will give you the vendor of
> >the card and then you can check thier website for the model number and
try
> >and figure out what driver to use
> >
> >-Casey
> well the things we learn..
> 
> any ideas what the MAC might look like? where it may be?
It looks like a serie of hexadecimal numbers (xx and yy are he in the
example above). It can be found in the card's eeprom(not bootprom), but to
get there you should know the cardtype, and that is the problem (I
beliove)


Greetz,
Sebastiaan
 > 

> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
> 
> 



Re: NIC identification

2001-01-17 Thread Sebastiaan


On Wed, 17 Jan 2001, John Griffiths wrote:

> At 11:38 PM 1/16/2001 -0600, Casey Webster wrote:
> >if its netware approved you might try the ne2k driver, that thing works
> >for a lot of cards with that sticker, also if you can figure out the
> >card's MAC address (in the form of xx:xx:xx:yy:yy:yy and often on the card
> >somewhere) then search google for a MAC address to vendor converter and
> >pop on the xx:xx:xx from the mac addr and it will give you the vendor of
> >the card and then you can check thier website for the model number and try
> >and figure out what driver to use
> >
> >-Casey
> well the things we learn..
> 
> any ideas what the MAC might look like? where it may be?
It looks like a serie of hexadecimal numbers (xx and yy are he in the
example above). It can be found in the card's eeprom(not bootprom), but to
get there you should know the cardtype, and that is the problem (I
beliove)


Greetz,
Sebastiaan
 > 

> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 
> 



Re: NIC identification

2001-01-17 Thread Hall Stevenson
>> somewhere) then search google for a MAC address
>> to vendor converter and pop on the xx:xx:xx from
>> the mac addr and it will give you the vendor of
>>the card and then you can check thier website
>> for the model number and
>> try and figure out what driver to use

> eh, won't it show when typing ifconfig with one or
> more options ?

Not 'til it's loaded and recognized... the problem originally started
because the person doesn't know what card/chipset it is and can't get it
loaded. I copied the relevant parts of an early reply above.

Regards
Hall



RE: NIC identification

2001-01-17 Thread Joris Lambrecht
eh, won't it show when typing ifconfig with one or more options ?

-Original Message-
From: Casey Webster [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 17, 2001 2:26 PM
To: John Griffiths
Cc: debian-user@lists.debian.org
Subject: Re: NIC identification


often they will pe printed onto th card, or printed onto a sticker that is
placed on the card or one of the chips on the card, it will be a in the
form: 00:01:02:70:5E:B1 or possbile without the colons, but it will
contain that many digits.  The first 6 numbers (00:01:02) identify the
vendor, and i this case thats 3com (3c905-c-txm)

-Casey

On Wed, 17 Jan 2001, John Griffiths wrote:

> At 11:38 PM 1/16/2001 -0600, Casey Webster wrote:
> >if its netware approved you might try the ne2k driver, that thing works
> >for a lot of cards with that sticker, also if you can figure out the
> >card's MAC address (in the form of xx:xx:xx:yy:yy:yy and often on the
card
> >somewhere) then search google for a MAC address to vendor converter and
> >pop on the xx:xx:xx from the mac addr and it will give you the vendor of
> >the card and then you can check thier website for the model number and
try
> >and figure out what driver to use
> >
> >-Casey
> well the things we learn..
> 
> any ideas what the MAC might look like? where it may be?
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]



Re: NIC identification

2001-01-17 Thread Casey Webster
often they will pe printed onto th card, or printed onto a sticker that is
placed on the card or one of the chips on the card, it will be a in the
form: 00:01:02:70:5E:B1 or possbile without the colons, but it will
contain that many digits.  The first 6 numbers (00:01:02) identify the
vendor, and i this case thats 3com (3c905-c-txm)

-Casey

On Wed, 17 Jan 2001, John Griffiths wrote:

> At 11:38 PM 1/16/2001 -0600, Casey Webster wrote:
> >if its netware approved you might try the ne2k driver, that thing works
> >for a lot of cards with that sticker, also if you can figure out the
> >card's MAC address (in the form of xx:xx:xx:yy:yy:yy and often on the card
> >somewhere) then search google for a MAC address to vendor converter and
> >pop on the xx:xx:xx from the mac addr and it will give you the vendor of
> >the card and then you can check thier website for the model number and try
> >and figure out what driver to use
> >
> >-Casey
> well the things we learn..
> 
> any ideas what the MAC might look like? where it may be?
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 



Re: NIC identification

2001-01-17 Thread Phil Brutsche
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

A long time ago, in a galaxy far, far way, someone said...

> OK i've got a NIC that i need to get working.
>
> its PCI appears to support Co-ax as well as cat-45
>
> it has a netware approved sticker on it
>
> it has 3 components on it made by Delta
>
> the most comprehensible component proclaims itself to be
>
> Delta LANF7236 9701F
>
> has anyone got any ideas what driver i should use?
>
> it has worked with slackware (which does auto-detect) but the HD it was 
> working with has gone to heaven.
>
> thanks for any help that can be proferred

If it's a PCI nic just pop it into a computer with a PCI bus and see what
you get.  On Linux you should find this ethernet card listed under
/proc/pci someplace.

You can also try to do "modprobe ne2k-pci" as root - it sounds awfully
similar to a NE2000 PCI card I have here someplace.

- -- 
- --
Phil Brutsche   [EMAIL PROTECTED]

GPG fingerprint: 9BF9 D84C 37D0 4FA7 1F2D  7E5E FD94 D264 50DE 1CFC
GPG key id: 50DE1CFC
GPG public key: http://tux.creighton.edu/~pbrutsch/gpg-public-key.asc
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE6ZT9b/ZTSZFDeHPwRAjnnAKDb7KxH51ZEKviopEYjQh/fz+RQTwCg0SBW
u1q/+zKhCWvv1Re7/cz78Nc=
=XLXn
-END PGP SIGNATURE-



Re: NIC identification

2001-01-16 Thread John Griffiths
At 11:38 PM 1/16/2001 -0600, Casey Webster wrote:
>if its netware approved you might try the ne2k driver, that thing works
>for a lot of cards with that sticker, also if you can figure out the
>card's MAC address (in the form of xx:xx:xx:yy:yy:yy and often on the card
>somewhere) then search google for a MAC address to vendor converter and
>pop on the xx:xx:xx from the mac addr and it will give you the vendor of
>the card and then you can check thier website for the model number and try
>and figure out what driver to use
>
>-Casey
well the things we learn..

any ideas what the MAC might look like? where it may be?



Re: NIC identification

2001-01-16 Thread Casey Webster
if its netware approved you might try the ne2k driver, that thing works
for a lot of cards with that sticker, also if you can figure out the
card's MAC address (in the form of xx:xx:xx:yy:yy:yy and often on the card
somewhere) then search google for a MAC address to vendor converter and
pop on the xx:xx:xx from the mac addr and it will give you the vendor of
the card and then you can check thier website for the model number and try
and figure out what driver to use

-Casey

On Wed, 17 Jan 2001, John Griffiths wrote:

> OK i've got a NIC that i need to get working.
> 
> its PCI appears to support Co-ax as well as cat-45
> 
> it has a netware approved sticker on it
> 
> it has 3 components on it made by Delta
> 
> the most comprehensible component proclaims itself to be 
> 
> Delta LANF7236 9701F
> 
> has anyone got any ideas what driver i should use?
> 
> it has worked with slackware (which does auto-detect) but the HD it was 
> working with has gone to heaven.
> 
> thanks for any help that can be proferred
> 
> John
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>