Re: Can't get if_txp(4) to attach to a 3CR990B-TXM NIC

On Tuesday 12 June 2007 09:15 pm, Pyun YongHyeon wrote:
On Tue, Jun 12, 2007 at 10:20:11AM -0700, Freddie Cash wrote:
> On Friday 08 June 2007 09:59 pm, Pyun YongHyeon wrote:
> > On Fri, Jun 08, 2007 at 09:13:37AM -0700, Freddie Cash wrote:
> > > Good morning,
> > >
> > > I'm having a bit of an issue getting a 3CR990B-TXM NIC detected
> > > and usable. Just wondering if anyone knows of any issues with
> > > this NIC chipset and/or with the motherboard chipset.
> > >
> > > The motherboard is a Biostar GeForce 6100 AM2 using an nVidia
> > > nForce 410 chipset and nVidia GeForce 6100 vide chipset.
> > >
> > > I've tried FreeBSD 6.1, 6.2, 6-STABLE (from Wed), and 7-CURRENT
> > > (from Thu) on this system. Everything installs nicely,
> > > everything on the board is detected correctly and usable. It's
> > > just the PCI NIC that doesn't work.
> > >
> > > If I compile a custom kernel without any network drivers in it,
> > > and then kldload if_txp, the following appears (same message on
> > > all 4 versions):
> > >
> > > txp0: <3Com 3cR990B-TXM Etherlink with 3XP Processor> port
> > > 0xbc00-0xbc7f mem 0xfdcff000-0xfdcff07f irq 16 at device 8.0 on
> > > pci3 txp0: not waiting for boot
> > > device_attach: txp0 attach returned -1
> >
> > Would you try attached path?
> > It wouldn't fix your issue but it will handle failure of
> > contigmalloc as expected.
>
> Patch applies cleanly, module compiles cleanly, and module is
> kldloaded cleanly. But same error message as before, and no txp0
> device is created.
>
> Tested on 7-CURRENT from last week.

Thanks for testing!

It seems that the message will show up in case of firmware loading/ring
initialization failure. Try attached patch which will show failing
function name.

Patch uplied cleanly, module compiled clealy, and module was kldloaded
cleanly.

Error message is now:
txp0: <3Com 3cR990B-TXM Etherlink with 3XP Processor> port 0xbc00-0xbc7f
mem 0xfdcff000-0xfdcff07f irq 18 at device 6.0 on pci3
txp0: txp_download_fw: not waiting for boot
device_attach: txp0 attach returned -1

The IRQ and device numbers changed as it's in a different PCI slot than
before.

Looks like your guess was right, there's something not working right in
the firmware download.

Because I don't have 3CR990 hardware it's very hard to fix it. I'm
unsure remote debugging would help here.
Btw, it seems the hardware looks very good(except for extra copying on
strict alignment architecture) and it even supports TSO!

We normally use 3C905-series and 3C980-series NICs. Our local PC vendor
sent us these instead when we ordered low-profile NICs to put into our
new firewall boxes (while we wait for the back-order on Intel gigabit
dual-port, low-profile, PCIe NICs to be filled).

I was going to try upgrading the firmware on the NICs, as there's an
update available on the 3Com website, but the installer requires a
Windows box (tried via a DOS boot disk and get the "Can't be run in DOS
mode" error), which we don't have available at the moment.

--
Freddie Cash, LPIC-2 CCNT CCLP Network Support Technician
School District 73 (250) 377-HELP [377-4357]
fjwcash+freebsd@xxxxxxxxx
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Cant get if_txp(4) to attach to a 3CR990B-TXM NIC
    ... > Patch applies cleanly, module compiles cleanly, and module is ... But same error message as before, ... Try attached patch which will show failing ... We normally use 3C905-series and 3C980-series NICs. ...
    (freebsd-stable)
  • Re: Cant get if_txp(4) to attach to a 3CR990B-TXM NIC
    ... >>> Patch applies cleanly, module compiles cleanly, and module is ... Try attached patch which will show failing ... > the firmware download. ... > dual-port, low-profile, PCIe NICs to be filled). ...
    (freebsd-stable)
  • Re: Cant get if_txp(4) to attach to a 3CR990B-TXM NIC
    ... >>> Patch applies cleanly, module compiles cleanly, and module is ... But same error message as before, ... Try attached patch which will ... > in the firmware download. ...
    (freebsd-stable)
  • Re: eth0 - eth1 confusion vs. local network
    ... I went Googling and found the udev ... NICs have "Kernel driver in use". ... Changing kernels likely broke your firmware blobs. ...
    (Debian-User)
  • Re: Cant get PC to talk to router
    ... Thanks Trooper but as I said, when I tried ipconfig /release and ipconfig ... You should have an active connection led on the NIC when the cable is ... NICs ... and ipconfig /renew but got the following error message: ...
    (microsoft.public.windowsxp.help_and_support)