Dell Precision 330 (Pentium 4, i850 chipset, 3c905c)

Dell Precision 330 (Pentium 4, i850 chipset, 3c905c)

[I Lee Hetherington]

Anybody get this working with 2.2.18 or 2.4.0-prerelease?  I can't seem
to get the on-board 3c905c to work.  I've seen it without an interrupt
assignment in /proc/interrupts.  With Red Hat's pump (DHCP), it sends
packets out but doesn't seem to see the response.

I can provide more details.

--Lee Hetherington


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Dell Precision 330 (Pentium 4, i850 chipset, 3c905c)

[Andrew Morton]

I Lee Hetherington wrote:
> 
> Anybody get this working with 2.2.18 or 2.4.0-prerelease?  I can't seem
> to get the on-board 3c905c to work.  I've seen it without an interrupt
> assignment in /proc/interrupts.  With Red Hat's pump (DHCP), it sends
> packets out but doesn't seem to see the response.
> 
> I can provide more details.

Please do.  The boot-time messages which come out of the driver
would be interesting.  It would help if you add `debug=7' to
the 3c59x modprobe command line also.

Thanks.

-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Dell Precision 330 (Pentium 4, i850 chipset, 3c905c)

[I Lee Hetherington]

[-- Attachment #1: Type: text/plain, Size: 462 bytes --]

Andrew Morton wrote:

> Please do.  The boot-time messages which come out of the driver
> would be interesting.  It would help if you add `debug=7' to
> the 3c59x modprobe command line also.

OK.  I've included dmesg output due to modprobe with debug=7 followed by ifup
(using pump -- problems persist with static IP as well), cat /proc/interrupts
showing no eth0, and ifconfig eth0.

Please let me know what else I can provide to help out.

--Lee Hetherington


[-- Attachment #2: dmesg --]
[-- Type: text/plain, Size: 6678 bytes --]

3c59x.c 15Sep00 Donald Becker and others http://www.scyld.com/network/vortex.html
eth0: 3Com 3c905C Tornado at 0xe880,  00:b0:d0:14:d2:b4, IRQ 11
  Internal config register is 1800000, transceivers 0xa.
  8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface.
  MII transceiver found at address 1, status   24.
  MII transceiver found at address 2, status   24.
  Enabling bus-master transmits and whole-frame receives.
eth0: Initial media type Autonegotiate.
eth0: MII #1 status 0024, link partner capability 41e1, setting full-duplex.
eth0: vortex_open() InternalConfig 01800000.
eth0: vortex_open() irq 11 media status 8080.
eth0:  Filling in the Rx ring.
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: Trying to send a boomerang packet, Tx index 0.
eth0: interrupt, status f201, latency 3, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status f201.
eth0: exiting interrupt, status f000.
eth0: Media selection timer tick happened, Autonegotiate.
eth0: MII transceiver has status 0020.
eth0: Media selection timer finished, Autonegotiate.
eth0: Trying to send a boomerang packet, Tx index 1.
eth0: interrupt, status e201, latency 3, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status e201.
eth0: exiting interrupt, status e000.
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: Trying to send a boomerang packet, Tx index 2.
eth0: interrupt, status e201, latency 3, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status e201.
eth0: exiting interrupt, status e000.
eth0: Trying to send a boomerang packet, Tx index 3.
eth0: interrupt, status e201, latency 3, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status e201.
eth0: exiting interrupt, status e000.
eth0: Trying to send a boomerang packet, Tx index 4.
eth0: interrupt, status e201, latency 3, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status e201.
eth0: exiting interrupt, status e000.
eth0: Trying to send a boomerang packet, Tx index 5.
eth0: interrupt, status e201, latency 3, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status e201.
eth0: exiting interrupt, status e000.
eth0: Trying to send a boomerang packet, Tx index 6.
eth0: interrupt, status e201, latency 3, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status e201.
eth0: exiting interrupt, status e000.
eth0: Trying to send a boomerang packet, Tx index 7.
eth0: interrupt, status e201, latency 3, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status e201.
eth0: exiting interrupt, status e000.
eth0: Trying to send a boomerang packet, Tx index 8.
eth0: interrupt, status e201, latency 3, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status e201.
eth0: exiting interrupt, status e000.
eth0: Trying to send a boomerang packet, Tx index 9.
eth0: interrupt, status e201, latency 3, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status e201.
eth0: exiting interrupt, status e000.
eth0: Trying to send a boomerang packet, Tx index 10.
eth0: interrupt, status e201, latency 2, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status e201.
eth0: exiting interrupt, status e000.
eth0: vortex_close() status e000, Tx status 00.
eth0: vortex close stats: rx_nocopy 0 rx_copy 0 tx_queued 11 Rx pre-checksummed 0.
eth0: Initial media type Autonegotiate.
eth0: MII #1 status 0020, link partner capability 41e1, setting full-duplex.
eth0: vortex_open() InternalConfig 01800000.
eth0: vortex_open() irq 11 media status 8080.
eth0:  Filling in the Rx ring.
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: Trying to send a boomerang packet, Tx index 0.
eth0: interrupt, status f201, latency 3, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status f201.
eth0: exiting interrupt, status f000.
eth0: Media selection timer tick happened, Autonegotiate.
eth0: MII transceiver has status 0020.
eth0: Media selection timer finished, Autonegotiate.
eth0: Trying to send a boomerang packet, Tx index 1.
eth0: interrupt, status e201, latency 3, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status e201.
eth0: exiting interrupt, status e000.
eth0: no boomerang interrupt pending
eth0: no boomerang interrupt pending
eth0: Trying to send a boomerang packet, Tx index 2.
eth0: interrupt, status e201, latency 2, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status e201.
eth0: exiting interrupt, status e000.
eth0: Trying to send a boomerang packet, Tx index 3.
eth0: interrupt, status e201, latency 3, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status e201.
eth0: exiting interrupt, status e000.
eth0: Trying to send a boomerang packet, Tx index 4.
eth0: interrupt, status e201, latency 3, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status e201.
eth0: exiting interrupt, status e000.
eth0: Trying to send a boomerang packet, Tx index 5.
eth0: interrupt, status e201, latency 3, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status e201.
eth0: exiting interrupt, status e000.
eth0: Trying to send a boomerang packet, Tx index 6.
eth0: interrupt, status e201, latency 3, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status e201.
eth0: exiting interrupt, status e000.
eth0: Trying to send a boomerang packet, Tx index 7.
eth0: interrupt, status e201, latency 2, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status e201.
eth0: exiting interrupt, status e000.
eth0: Trying to send a boomerang packet, Tx index 8.
eth0: interrupt, status e201, latency 3, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status e201.
eth0: exiting interrupt, status e000.
eth0: Trying to send a boomerang packet, Tx index 9.
eth0: interrupt, status e201, latency 3, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status e201.
eth0: exiting interrupt, status e000.
eth0: Trying to send a boomerang packet, Tx index 10.
eth0: interrupt, status e201, latency 3, cur_rx 0, dirty_rx 0
eth0: In interrupt loop, status e201.
eth0: exiting interrupt, status e000.
eth0: vortex_close() status e000, Tx status 00.
eth0: vortex close stats: rx_nocopy 0 rx_copy 0 tx_queued 22 Rx pre-checksummed 0.

[-- Attachment #3: interrupts --]
[-- Type: text/plain, Size: 358 bytes --]

           CPU0       
  0:      20048          XT-PIC  timer
  1:        314          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  8:          1          XT-PIC  rtc
 11:       1660          XT-PIC  aic7xxx
 12:          0          XT-PIC  PS/2 Mouse
 13:          1          XT-PIC  fpu
 15:          7          XT-PIC  ide1
NMI:          0

[-- Attachment #4: ifconfig --]
[-- Type: text/plain, Size: 307 bytes --]

eth0      Link encap:Ethernet  HWaddr 00:B0:D0:14:D2:B4  
          BROADCAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:1 frame:0
          TX packets:23 errors:0 dropped:0 overruns:0 carrier:1
          collisions:0 txqueuelen:100 
          Interrupt:11 Base address:0xe880 

Re: Dell Precision 330 (Pentium 4, i850 chipset, 3c905c)

[Andrew Morton]

I Lee Hetherington wrote:
> 
> Andrew Morton wrote:
> 
> > Please do.  The boot-time messages which come out of the driver
> > would be interesting.  It would help if you add `debug=7' to
> > the 3c59x modprobe command line also.
> 
> OK.  I've included dmesg output due to modprobe with debug=7 followed by ifup
> (using pump -- problems persist with static IP as well), cat /proc/interrupts
> showing no eth0, and ifconfig eth0.

OK, that's wierd.  Why on earth isn't it showing up in 
/proc/interrupts?  It's certainly generating Tx interrupts,
and the ISR is being called.

Is this a new NIC?  3Com have just started shipping a
new flavour of the 905c, the 3c905CX.  With this device
the RxReset command takes tens of milliseconds to complete,
not tens of microseconds like all the others.  This
breaks the driver.  You end up being able to transmit but
not receive.

And the old media interface selection algorithms don't work
right with the 3c905CX either.   We only got this sorted
a few days ago and we missed the 2.4.0 boat :(

Could you please test this 2.2 driver?

	http://www.uow.edu.au/~andrewm/linux/3c59x.c-2.2.19-pre2-2.gz

Thanks.

-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Dell Precision 330 (Pentium 4, i850 chipset, 3c905c)

[I Lee Hetherington]

Andrew Morton wrote:

> Could you please test this 2.2 driver?
>
>         http://www.uow.edu.au/~andrewm/linux/3c59x.c-2.2.19-pre2-2.gz

Bingo!  This driver works fine.  Thanks.

(Why do hardware people keep tweaking things for seemingly unnecessary reasons?)

--Lee Hetherington


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Dell Precision 330 (Pentium 4, i850 chipset, 3c905c)

[Andrew Morton]

I Lee Hetherington wrote:
> 
> Andrew Morton wrote:
> 
> > Could you please test this 2.2 driver?
> >
> >         http://www.uow.edu.au/~andrewm/linux/3c59x.c-2.2.19-pre2-2.gz
> 
> Bingo!  This driver works fine.  Thanks.

And /proc/interrupts?

> (Why do hardware people keep tweaking things for seemingly unnecessary reasons?)

They hate software people.

-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Dell Precision 330 (Pentium 4, i850 chipset, 3c905c)

[I Lee Hetherington]

/proc/interrupts shows eth0 (sharing aic7xxx) now.  The NIC is fully
functional now.

I was actually trying your 3c59x.c-2.2.19pre2.gz, and not the -2
version.  Trying that now.

--Lee

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Dell Precision 330 (Pentium 4, i850 chipset, 3c905c)

[I Lee Hetherington]

Sorry to follow up, but I forgot to note that it is trying to share IRQ
11 for aic7xx and eth0.  However, even if I move the Adaptec card to
another slot, where it gets IRQ 10, still no joy for eth0 on IRQ 11.

--Lee Hetherington


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Dell Precision 330 (Pentium 4, i850 chipset, 3c905c)

[Manfred]

> Anybody get this working with 2.2.18 or 2.4.0-prerelease?
> I can't seem to get the on-board 3c905c to work.

Everything except the NIC works?

> I've seen it without an interrupt assignment in
> /proc/interrupts. With Red Hat's pump (DHCP), it sends 
> packets out but doesn't seem to see the response. 

What do you mean with "without an interrupt assignment"?
Is there no line for ethx in /proc/interrupt, or the number of
interrupts remains 0?

what does `lspic -vxx` say about the interrupt number?

Is there a BIOS setting similar to "Pnp aware OS"? For the 2.2 kernel
that must be "No", 2.2 might run with "Yes", but I'm not sure if the
850i board is supported.

--
	Manfred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Dell Precision 330 (Pentium 4, i850 chipset, 3c905c)

[I Lee Hetherington]

Manfred wrote:

> Everything except the NIC works?

Yes.

> What do you mean with "without an interrupt assignment"?
> Is there no line for ethx in /proc/interrupt, or the number of
> interrupts remains 0?

There is no entry for eth0 anywhere in /proc/interrupts.  That seems
strange.

> what does `lspic -vxx` say about the interrupt number?

lspci -v says IRQ 11, which is what the BIOS says.  This is also what
I see in dmesg when eth0 is found.

> Is there a BIOS setting similar to "Pnp aware OS"? For the 2.2 kernel
> that must be "No", 2.2 might run with "Yes", but I'm not sure if the
> 850i board is supported.

I'll look into this.

Thanks.

--Lee Hetherington


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Dell Precision 330 (Pentium 4, i850 chipset, 3c905c)

[Jon Burgess]

What is the output of 'lspci -v'? If it says that the chip revision is '78' then
this is one of the new 3C905CX (note the CX) NIC's or ASIC on the motherboard.
I've seen a problem with the 3c59x.c driver and this chip, it can send packets
but not receive any. The 3Com 3c90x-1.0.0i.tgz driver at
http://support.3com.com/infodeli/tools/nic/linux.htm should work with this chip.

There has been some discussion of this NIC on the vortex mailing list at
http://www.scyld.com/network/vortex.html , with a patched driver to make for
this chip available for testing at Andrew's web site
http://www.uow.edu.au/~andrewm/linux/#3c59x-bc (see the '2.2.19pre2 driver for
testing').

     Jon


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Dell Precision 330 (Pentium 4, i850 chipset, 3c905c)

[I Lee Hetherington]

Yes, it is rev 78, but I have at least 20 of these working on other
machines (Precision 620) for a long time now.  The difference in this
machine is the i850 chipset vs. the i810 in the 620.

This seems to be a problem of 3c59x making a successful call of
request_irq(), but nothing shows up in /proc/interrupts.  It sounds like
something is getting dropped on the floor somewhere else.

I will try the patched driver on Andrew's web site.

--Lee Hetherington


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/