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,

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

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 k

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 st

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 p

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 poi

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"

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 snea

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

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 pr

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 NI

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

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

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

RE: NIC identification

2001-01-17 Thread John Galt
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 wil

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 PC

RE: NIC identification

2001-01-17 Thread robin . c . smith
: 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

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:y

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 ty

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 pr

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

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 >

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

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