I had no loopback network device enabled in /etc/network/interfaces (found and corrected courtesy of an old email in this list by Karen M. Self: much obliged Karen) and IRQ10 was configured for pci/pnp in my pre-boot hardware set up (now changed to isa/eisa); The latest state is that now at least the enables look okay, but I get "Adapter Failure indication"...the fun continues. Regards, Dave. -----Original Message----- From: Andrew Sackville-West <[EMAIL PROTECTED]> To: Dave Whelan <[EMAIL PROTECTED]> Cc: debian-user@lists.debian.org <debian-user@lists.debian.org> Date: December 21, 2005 3:34 PM Subject: Re: NIC PnP
> > >Dave Whelan wrote: >> Thanks Andrew. I should have written "...but cannot access the nic". I do have >> the driver installed, but the syslog files don't show the NIC. > >I know, but sometimes its the really simple things... actual >conversation follows > >wife "I can't get the car door open" >me "did you unlock it?" >wife "oh..." > >and she's no dummy... > >anyway, so the module is loaded, but doesn't show in the syslog? When >does it load? automatically on boot, or do you have to modprobe it? are >there any useful parameters in modinfo? your question about the >"enables" may be pertinent, can you set that through modprobe parameters? > >just thinking aloud > >A > >> Regards >> Dave. >> -----Original Message----- >> From: Andrew Sackville-West <[EMAIL PROTECTED]> >> To: Dave Whelan <[EMAIL PROTECTED]> >> Cc: debian-user@lists.debian.org <debian-user@lists.debian.org> >> Date: December 20, 2005 4:24 PM >> Subject: Re: NIC PnP >> >> >> >>> >>>Dave Whelan wrote: >>> >>>>I have the driver but cannot access the driver. The setup utility for the NIC >>>>gives me: >>>> >>>>3c5x9setup.c:v1.00 6/19/2000 Donald Becker ([EMAIL PROTECTED]) >>>>http://www.scyld.com/diag/index.html >>>>No interrupt sources are pending. >>>>3c5x9 found at 0x300. >>>>Indication enable is 0000, interrupt enable is 0000. >>>>EEPROM contents: >>>> Model number 3c509 version 5, base I/O 0x300, IRQ 10, 10baseT port. >>>> 3Com Node Address 00:50:DA:7E:30:2A (used as a unique ID only). >>>> OEM Station address 00:50:DA:7E:30:2A (used as the ethernet address). >>>> Manufacture date (MM/DD/YY) 11/11/99, division 6, product WK. >>>> Options: half duplex, enable linkbeat. >>>> The computed checksum matches the stored checksum of 7e03. >>>> >>>>The enables don't look right, could that be my problem? >>>>Regards, >>>>Dave. >>> >>>I'm sorry, but I have to state the obvious, just in case its something >>>really simple... >>> >>>modprobe 3c509 >>> >>>and maybe check the logs after that. >>> >>>A >>> >>> >>>>-----Original Message----- >>>>From: Ralph Katz <[EMAIL PROTECTED]> >>>>To: debian-user@lists.debian.org <debian-user@lists.debian.org> >>>>Date: December 19, 2005 11:57 AM >>>>Subject: Re: NIC PnP >>>> >>>> >>>> >>>> >>>>>On 12/18/2005 08:00 PM, Dave Whelan wrote: >>>>> >>>>> >>>>>>I can't get my 3c509 working for aliant dsl, does anyone know how I can >> >> check >> >>>>>>whether PnP is enabled on this NIC? >>>>>>Regards, >>>>>>Dave Whelan. >>>>> >>>>>Dave, >>>>> >>>>>I have that card working fine on a sarge box with kernel 2.4.27. From >>>>>the syslog: >>>>> >>>>> >>>>> >>>>>>Dec 19 10:05:57 localhost kernel: isapnp: Scanning for PnP cards... >>>>>>Dec 19 10:05:57 localhost kernel: isapnp: Card '3Com 3C509B EtherLink III' >>>>>>Dec 19 10:05:57 localhost kernel: isapnp: 1 Plug & Play card detected total >>>>>>Dec 19 10:05:57 localhost kernel: eth0: 3c5x9 at 0x220, 10baseT port, >> >> address >> >>>>0 >>>> >>>> >>>>>>0 10 4b 15 c4 ed, IRQ 5. >>>>>>Dec 19 10:05:57 localhost kernel: 3c509.c:1.19 16Oct2002 [EMAIL PROTECTED] >>>>>>Dec 19 10:05:57 localhost kernel: http://www.scyld.com/network/3c509.html >>>>> >>>>>You should already have the driver: >>>>> >>>>>$ locate 3c509 >>>>>/lib/modules/2.4.27-2-586tsc/kernel/drivers/net/3c509.o >>>>> >>>>>I do have 3c509 listed in /etc/modules. >>>>> >>>>>Regards, >>>>>Ralph >>>>> >>>>> >>>>>-- >>>>>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] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
