PCLOS2010.07 Broadcom BCM4401 Adapterr Bug? and my Workaround

[BMaytum]

My Asus P4PE motherboard (circa 2002, Intel 845PE chipset) has an integrated Broadcom BCM4401 100BaseT ethernet LAN adapter/controller (eth0).  This PC is continually plugged into wall power, and the Broadcom adapter normally is powered on as evidenced by my router's port indicator.
PC has WindowsXP installed on SATA disk (partition sda1) and now PCLinuxOS 2010.07 installed on IDE disk (partitions sdb5-sdb8 for root, home, usr and swap respectively).

After booting PCLOS2010.07 from LiveCD -OR- from IDE disk via Grub boot floppy, shutting down PCLOS  (Start> Leave> Turn Off Computer) does shutdown and powers off the PC.
However, something in the shutdown process puts the Broadcom adapter in an unpowered state, as evidenced by my router's port indicator.  Subsequently booting PCLOS from LiveCD or IDE disk will re-power the Broadcom adapter during bootup, but again shutting down from PCLOS again puts Broadcom adapter in an unpowered state. The problem is that when I boot WindowsXP (from it's own NTLDR), WinXP reports "A network cable is unplugged" and I have NO ethernet connection, even though Windows Device Manager reports the Broadcom adapter is working normally (detected & drivers are loaded). The workaround I found is to unplug the PC from wall power (or toggle power supply switch off) for 10+ seconds, then back on, while the PC is shutdown - this will re-power the Broadcom adapter.

So is there a bug in PCLOS2010.07's shutdown process?
If so, is there some setting I can use to preclude PCLOS from putting the Broadcom adapter in an unpowered state during shutdown?

[wedgetail]

BMaytum
I don't know the answer to what you are asking but amongst the windows services is there not one that will restart the LAN card on windows boot?

Is there not something like msconfig you can run in the cmd line and check what you have set on startup. I am very rusty on Windows these days.

[jlf001]

BMaytum,

What kernel are you running?  You might try kernel 2.6.33.7-pclos5 and see if that helps.  I'm running a dual boot Dell laptop with a Broadcom BCM4401-B0 100Base-TX Ethernet controller and don't have that problem.

Jeff

[BMaytum]

@jif001:  I am now using kernel 2.6.33.7-pclos5 and am now booting from hard disk w/ GRUB as my boot manager.  Nevertheless, shutting down PCLOS2010.07 (w/ all cumulative updates to date) still puts my Asustek/Broadcom 440x 10/100 Integrated Controller in an unpowered state (router LED and the LAN port LED for this PC turns off).  Unless I remove 120VAC wall power for 10+ secs the plug wall power back in, Windows XP Pro (w/SP3) will NOT repower the controller.  Additional info: the hardware level driver for this controller is WHQL-certified "bcm4bsxp.sys" version 3.48.0.0 by Broadcom copyright 1998-2002.  If I remove wall power then reapply power (with the computer not running), then the router LED and the LAN port LED will turn on (illuminate).

@ wedgeling:  I perused the list of Windows services, don't see anything obvious that might control or force LAN adapter controller to power up as WinXP boots. Likewise nothing obvious in WinXP's TCP/IP configuration dialogs nor power-related adapter controller Properties in Device Manager. The Device Manager > Details tab for the adapter includes "Service: bcm4bxp", and the Event Log > System does record proper startup of bcm4bxp and tcpip services but ONLY if I remove&restore wall power after shutting down PCLOS and before booting WinXP;  if I don't remove&restore wall power between PCLOS shutdown and WinXP boot, the Event Log records NO event info (e.g. started, nor did not start/failed) pertaining to either bcm4bsxp nor tcpip serveices.   The adapter does NOT go to an unpowered state when I shutdown WinXP (as evidenced by router port LED & adapter port LED), thus I can thereafter boot WinXP again and again and again (or PCLOS) with NO adapter problems.

Thanks for suggestions thus far.  Has any Dev looked at shutcode code yet??
Any other ideas anyone?

[DeBaas]

In Winders, switch off the WiFi hardware in the hardware config screen, followed by activate/switch on.

my 2 pennies

[BMaytum]

@ DeBaas:

My Broadcom BCM4401 10/100baseT controller is for hard-wired ethernet LAN connection, it is NOT a WiFi adapter and there are no WiFi components in Windoze's Device Manager hardware profiles.  (Aside: I do own a LinkSys WRT54GS USB external wireless adapter, but I have never installed it's drivers under either Windoze XP Pro nor PCLOS2010).

I have tried cycling Disable/Enable the integrated Broadcom adapter in Windoze Device Manager, but that does not force the adapter to power up from the unpowered state caused by shutting down PCLOS. Does anyone know if Windoze has a command-line (via "ipconfig" or other CL) equivalent to linux "ip link set eth0 down"/ "ip link set eth0 up"?
When booted into PCLOS I see:

Code: [Select]

[root@localhost ~]# ip link show eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:e0:18:af:8d:4b brd ff:ff:ff:ff:ff:ff

I'm still wondering if any PCLOS2010 Devs have reviewed the adapter / ethernet shutdown process to see if there is some code that unnecessarily leaves eth0 in an unpowered state?

[jlf001]

BMaytum,

In Windows, open the device manager and look at the Broadcom controller's power management settings.  If allow the computer to turn off this device to save power is checked, uncheck it.  Reboot and see it that works.

Jeff

[nerdful1]

Interesting...

I thought some of my wifi and/or wired ethernet problems might be due to Windows switching off a device, then Linux finding it DOA on the motherboard.

This is the opposite problem.

It does pay to keep this in your bag of t-shooting tricks, one os affecting another through a reboot and even power off.

[BMaytum]

@ jlf001:

Good tip, but I already disabled that  "power saving feature"  (pffft) in Windoze with no effect.  PCLOS2010.07 still puts Broadcom wired LAN adapter in unpowered state during shutdown.

[wedgetail]

BMaytum
In root konsole, please do the following command line as shown in the example, your result will be different, but Ethernet is a good filter to start with

Code: [Select]

[root@localhost gert]$ lspci |grep Ethernet
02:00.0 Ethernet controller: Atheros Communications AR8121/AR8113/AR8114 Gigabit or Fast Ethernet (rev b0)

Post your result in code tags exactly as shown above to improve readability ( I have noticed you have described your card, still want to see above)

Then when You look at your line for the Ethernet card, take note of the first 7 characters, in my case 02:00.0 yours will be different.

Then following command may give you a very long list, use your 7 characters to quickly locate the section for your card and post the result in code tags.

Code: [Select]

[root@localhost gert]$ lspci -vnn

The result will look something like:

Code: [Select]

02:00.0 Ethernet controller [0200]: Atheros Communications AR8121/AR8113/AR8114 Gigabit or Fast Ethernet [1969:1026] (rev b0)
        Subsystem: ASUSTeK Computer Inc. P5KPL-CM Motherboard [1043:8304]
        Flags: bus master, fast devsel, latency 0, IRQ 29
        Memory at fe9c0000 (64-bit, non-prefetchable) [size=256K]
        I/O ports at ec00 [size=128]
        Capabilities: [40] Power Management version 2
        Capabilities: [48] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [58] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [180] Device Serial Number ff-cc-dd-d7-00-26-18-ff
        Kernel driver in use: ATL1E
        Kernel modules: atl1e

Don't post all the other sections, only the relevant section for the Network card.  

[BMaytum]

# wedgeling:

OK here's my results:

Code: [Select]

[root@localhost ~]# lspci |grep Ethernet
02:05.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01)

[root@localhost ~]# lspci -vnn
02:05.0 Ethernet controller [0200]: Broadcom Corporation BCM4401 100Base-T [14e4:4401] (rev 01)
        Subsystem: ASUSTeK Computer Inc. A7V8X motherboard [1043:80a8]
        Flags: bus master, fast devsel, latency 32, IRQ 20
        Memory at db000000 (32-bit, non-prefetchable) [size=8K]
        Capabilities: [40] Power Management version 2
        Kernel driver in use: b44
        Kernel modules: b44

Odd that this says A7V8X motherboard given that mine is an ASUSTeK P4PE mobo that uses Intel i845PE mobo chipset for my Intel Pentium4 CPU, vastly different than an AMD-based chipset for Athlon CPU; likewise

Code: [Select]

02:04.0 RAID bus controller [0104]: Promise Technology, Inc. PDC20376 (FastTrak 376) [105a:3376] (rev 02)
        Subsystem: ASUSTeK Computer Inc. A7V8X motherboard [1043:809e]yet correctly shows:

Code: [Select]

00:00.0 Host bridge [0600]: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface [8086:2560] (rev 02)
        Subsystem: ASUSTeK Computer Inc. Device [1043:80b2]
00:01.0 PCI bridge [0604]: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE Host-to-AGP Bridge [8086:2561] (rev 02) (prog-if 00 [Normal decode])
00:1d.0 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 02) (prog-if 00 [UHCI])
        Subsystem: ASUSTeK Computer Inc. P4B533 [1043:8089]
00:1f.0 ISA bridge [0601]: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge [8086:24c0] (rev 02)
00:1f.1 IDE interface [0101]: Intel Corporation 82801DB (ICH4) IDE Controller [8086:24cb] (rev 02) (prog-if 8a [Master SecP PriP])
        Subsystem: ASUSTeK Computer Inc. P4B533 [1043:8089]
00:1f.3 SMBus [0c05]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller [8086:24c3] (rev 02)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8089]
00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24c5] (rev 02)
        Subsystem: ASUSTeK Computer Inc. P4B533 [1043:80b0]

... and other Intel chips.

That oddity aside, can you offer ideas on the PCLOS2010.07 shutdown -> Broadcom power-off?

[wedgetail]

BMaytum
Sorry I did not mean to leave you high and dry. Very unexpected interruption to my days is occurring.

The result of you effort did not help me. I had hoped some more information in the lspci would have revealed a clue.

I don't know if the 'oddity'  means anything, the Asus A7V8X Motherboard so I am not quite sure what you mean. Did you mean that the A7V8X was not ASUS?

I googled: Asus P4PE motherboard  Broadcom BCM4401 problem power off quite interesting results

From that I found one in particular:

http://www.linuxquestions.org/questions/linux-hardware-18/i-cant-detect-my-ethernet-card-33441/

Have not had time to read it properly, but this chap found the driver came on the disk that came with the motherboard? Question would your CD hold some README related to your problem?

...  Additional info: the hardware level driver for this controller is WHQL-certified "bcm4bsxp.sys" version 3.48.0.0 by Broadcom copyright 1998-2002. ...

I don't follow what you mean by this comment?  Do you mean this is the driver used in XP?

[BMaytum]

@ wedgetail:
No apology for delay needed, hope life smooooooothes out for you soon.
By 'oddity' I was referring to fact that lspci tagged the Broadcom BDM4401 controller as an A7V8X motherboard device - maybe Asus A7V8X mobo was released before my Asus P4PE mobo so the device driver was labelled as A7V8X? At any rate, that's just an 'oddity' that has no consequence as far as the controller behavior.

Thanks for the Googled thread, I read most of it but since the discussion there is predominantly about problems people were having back in 2002 trying to successfully build a Broadcom linux driver (e.g., run 'make' & 'install' & 'insmod' & so on), that thread doesn't help me in any obvious way - my PCLOS2010.07 *does* always load & properly use a (kernel-level) driver for the Broadcom controller -> No Problem.

The Problem is that when PCLOS2010.07 shuts down, the Broadcom controller seems to be powered OFF (LEDs tuurn off during shutdown process) in such a way that UNLESS I REMOVE WALL POWER, Windows bootup will NOT re-power the controller.  Nor will any of the controller-related nor ethernet-related  enable/disable tricks in Windows cause the controller to pwer up/restart.  So maybe there's something invoked during PCLOS shutdown scripts that puts the chip into total hibernation Windows-wise, contrasted to PCLOS being able to re-power the controller from an unpowered state upon PCLOS bootup (WITHOUT me having to remove & re-connect wall power beforehand)

Yes Asus' Download search tool (for mobo+socket478+P4PE+Linux) *does* have a 15MB file containing Broadcom's Linux (v1.0.1) tarball & drivers for various circa-2002 Windows operating systems, along with some release notes and (Windows or DOS only) Broadcom test & diagnosis tools. But since PCLOS2010 (& earlier PCLOS versions) has no problem detecting the chip & loading a driver for it, I currently don't plan to compile a driver from that tarball to then install in place of PCLOS2010.07's kernel-level driver.  I just need a solution to the PCLOS shutdown -> unpowered/hibernated controller problem.

Regarding the Quoted 'additional info', I was simply stating the version of the WindowsXP driver for my Broadcom controller ("WHQL' means Microsoft has tested the driver and awarded it "Windows Hardware Qualified List" status, like betty Crocker-approved recipes I guess....). I stated my WindowsXP driver version just in case a fellow PCLOS forum reader might put me onto a newer/better version.