Thanks to all.
I changed mu kernel version from 2.0.30 to 2.0.36 and now it is working .It is picking the right card as the new ver. contains ne2k-pci driver.
Abhijeet
[EMAIL PROTECTED] wrote:
Is it possible for you to set a fixed IRQ within the eprom on the chip The setup utility that comes with the ethernet card typically allows you to set the IRQ manually but in PCI cards the port is set to a value determines by the card After the setup program prompts you to save changes to the eprom on the NIC Try this .. and tell us what happened [EMAIL PROTECTED] on 01/14/99 06:26:27 PM To: [EMAIL PROTECTED] cc: [EMAIL PROTECTED] (bcc: Sandesh Rao/Systems/NSEIL) Subject: Re: NE1000 :Tx RDC hello tried this by changing in bios setup for IRQ10 to ISA/Legacy but after reboot the card is showing another IRQ in /proc/pci file .Then I changed all the IRQ to ISA Legacy ,now it piked up IRQ 255. But at the same time it is loading the eth0. The file dmesg is showing-- loading device 'eth0'... ne.c:v1.10 9/23/94 Donald Becker ([EMAIL PROTECTED]) NE*000 ethercard probe at 0x6100: 00 80 48 eb 74 90 eth0: NE1000 found at 0x6100, using IRQ 10. eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x17, t=500. eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x17, t=500. eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x17, t=500. eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x17, t=6000. eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x17, t=1464. eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x17, t=123. eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=104. eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x17, t=101. eth0: timeout waiting for Tx RDC. AND /proc/pci file shows PCI devices found: Bus 0, device 10, function 0: Ethernet controller: Unknown vendor Unknown device (rev 10). Vendor id=11f6. Device id=1401. Medium devsel. Fast back-to-back capable. IRQ 255. I/O at 0x6100. Henrik Olsen wrote: > On Thu, 14 Jan 1999, Y2K wrote: > > > Hi all > > During boot time system is showing following lines > > eth0:NE1000 found at 0x6100,using IRQ10 > > eth0:timeout waiting for Tx RDC > > > > and after this the m/c is not in network.Cable is not faulty. > > Can any one tell me what is Tx RDC error. > > I remember that one from last time I had to beat a pc into submission > before it worked, though I can't remember at which stage it came. > > It was either the missed interrupt due to int 10 being reserved for the > pci bus, or the timeouts because the card was set to autodetect the > connector and stupidly picked the BNC instead of RJ-45 connector, since I > can't remember which was the cause I'll give both as possibilities. > > Make sure int 10 is marked as ISA/LEGACY, non pci/pnp in your bios setup > and make sure the card uses the right connector. > > HTH > -- > Henrik Olsen, Dawn Solutions I/S > URL=http://www.iaeste.dk/~henrik/ > Plug'n'play works wonders in the environment it was designed for > ie. any periferal can be set to anything. > This is NOT a description of any existing hardware. > Draw your own conclusions from this. Henrik Olsen > > - > To unsubscribe from this list: send the line "unsubscribe linux-net" in > the body of a message to [EMAIL PROTECTED] (UUEncoded file named: att1.htm follows) (Its format is: Internet HTML )hello
tried this by changing in bios setup for IRQ10 to ISA/Legacy but after reboot
the card is showing another IRQ in /proc/pci file .Then I changed all the IRQ to ISA Legacy ,now it piked up IRQ 255. But at the same time it is loading the eth0.The file dmesg is showing--
loading device 'eth0'...
ne.c:v1.10 9/23/94 Donald Becker ([EMAIL PROTECTED])
NE*000 ethercard probe at 0x6100: 00 80 48 eb 74 90
eth0: NE1000 found at 0x6100, using IRQ 10.
eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x17, t=500.
eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x17, t=500.
eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x17, t=500.
eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x17, t=6000.
eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x17, t=1464.
eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x17, t=123.
eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=104.
eth0: Tx timed out, lost interrupt? TSR=0x3, ISR=0x17, t=101.
eth0: timeout waiting for Tx RDC.AND /proc/pci file shows
PCI devices found:
Bus 0, device 10, function 0:
Ethernet controller: Unknown vendor Unknown device (rev 10).
Vendor id=11f6. Device id=1401.
Medium devsel. Fast back-to-back capable. IRQ 255.
I/O at 0x6100.
Henrik Olsen wrote:
On Thu, 14 Jan 1999, Y2K wrote:> Hi all
> During boot time system is showing following lines
> eth0:NE1000 found at 0x6100,using IRQ10
> eth0:timeout waiting for Tx RDC
>
> and after this the m/c is not in network.Cable is not faulty.
> Can any one tell me what is Tx RDC error.I remember that one from last time I had to beat a pc into submission
before it worked, though I can't remember at which stage it came.It was either the missed interrupt due to int 10 being reserved for the
pci bus, or the timeouts because the card was set to autodetect the
connector and stupidly picked the BNC instead of RJ-45 connector, since I
can't remember which was the cause I'll give both as possibilities.Make sure int 10 is marked as ISA/LEGACY, non pci/pnp in your bios setup
and make sure the card uses the right connector.HTH
--
Henrik Olsen, Dawn Solutions I/S
URL=http://www.iaeste.dk/~henrik/
Plug'n'play works wonders in the environment it was designed for
ie. any periferal can be set to anything.
This is NOT a description of any existing hardware.
Draw your own conclusions from this. Henrik Olsen-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]- To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to [EMAIL PROTECTED]
