Integrated Broadcom nic on Dell times out with dhcp

From: Kent West (westk_at_acu.edu)
Date: 11/18/03

  • Next message: Travis Crump: "Re: How do I use dpkg without superuser privileges?"
    Date: Mon, 17 Nov 2003 17:17:22 -0600
    To: debian users <debian-user@lists.debian.org>
    
    

    I have a new Dell Dimension 2400 with an integrated Broadcom BCM4401
    100Base-T nic.

    When I first installed Woody on it, with a 2.4.18-bf kernel, the nic was
    not recognized.

    When I upgraded the kernel to a stock 2.4.22-1-686 kernel, the nic
    worked. Later, for other reasons, I needed to compile my own kernel. I
    copied over the .config file and recompiled a new 2.4.22 kernel. The nic
    stopped getting a dhcp address, and if I put in a static address, the
    network was unreachable.

    So I changed back to the stock kernel, and the problem remained.

    After a while I discovered that if I power off the computer and unplug
    it from the AC mains for a few seconds, I can then restart the machine
    and get a DHCP address, but the network remains broken with errors such as:
     b44: eth0: Link is down
     b44: eth0: Link is up at 10 Mbps, half duplex.
     b44: eth0: Flow control is off for TX and off for RX.

    and then the network traffic just dies. A ping just sits there until I
    ctrl-c it, at which time I don't even get the normal x % packets lost
    type messages.

    If I reconfigure the nic for static and restart the network (but not the
    computer), the network remains dead. I can then reconfigure for dhcp,
    and restart the network, and never get a new dchp address. It's like the
    nic has gone off to spend the weekend in the Bahamas.

    If I reconfigure the nic for static and then restart the whole computer
    (with a power off), the network comes back up and I can use the machine,
    as long as I don't stop the network for any reason. If I do stop the
    network, the nic goes back on vacation until the next power cycling.

    It "feels" like the driver is failing to reset something in the nic, or
    the nic is failing to accept a reset command, but not being a
    programmer, that's just shooting from the hip.

    I installed the nictools-pci package, but don't find anything of use for
    the Broadcom. I also installed mii-diag, but it reports that everything
    is dandy:

    Using the default interface 'eth0'.
    Basic registers of MII PHY #1: 1000 782d 0040 6360 0de1 0021 0004 2001.
     Basic mode control register 0x1000: Auto-negotiation enabled.
     You have link beat, and everything is working OK.
     Your link partner is generating 10baseT link beat (no autonegotiation).
        End of basic transceiver information.

    Any clues would be appreciated.

    -- 
    Kent
    -- 
    Kent West (westk@acu.edu)
    -- 
    To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
    

  • Next message: Travis Crump: "Re: How do I use dpkg without superuser privileges?"

    Relevant Pages

    • Kernel upgrade 2.4.18-14 -> 2.4.23 (rh8)
      ... I just recompiled a new kernel, ... eth0: Broadcom BCM5701 Integrated Copper transceiver found ... eth1: Broadcom BCM5701 Integrated Copper transceiver found ... Dec 5 10:07:55 network: Setting network parameters: succeeded ...
      (RedHat)
    • Re: Problems w. Promise SATA300 TX2plus PDC40775
      ... I have a Debian Sarge system with 2.6.8-K7 linux kernel (original kernel from ... Raw IP | Low Level Network Programming ... # ACPI Support ...
      (Debian-User)
    • Presario oops on 2.6.0-test1
      ... the new kernel version. ... but I finally have my network set up at the new ... This laptop is a Compaq Presario model 12XL325 with a 650 MHz Pentium III. ... # ACPI Support ...
      (Linux-Kernel)
    • DHCP-Problem with new kernel
      ... I hope you can help me with a problem concerning a new kernel I built on ... the kernel that came with Debian. ... Configuring network interfaces... ... DHCPREQUEST on eth0 to 255.255.255.255 port 67 ...
      (comp.os.linux.setup)
    • frustrating problem with networking encountered while installing "Woody"
      ... I'm trying to dual boot an old Pentium box with Debian ... "Woody" and win98. ... time at "configuring network interfaces......" ... do a net install with dhcp using the bf2.4 kernel. ...
      (Debian-User)