|" It is an Asus motherboard, in a mini 'designer' case so (1)|
Asus don't list it any longer ..."
Gigabyte has (and some other mboard makers have ) definitely lost the info and support for some of their older mboard models, but I've been able to find drivers listings for all the Asus retail mboards that I can recall.
Asus (and Gigabyte, etc.) makes many OEM only mboard models - they're supplied only to brand name system builders, and there is no support for the model on the Asus web sites. They're very similar, but not identical, to Asus retail models.
If you supply the model and Rev. or Ver. printed on the mboard surface, we may be able to dig up info and the drivers listed for it.
They also make / have made a small number of Asus systems. A mboard that's in a Asus system may not be in their mboards listings.
If you find the model on the Broadcom chip, you can find the correct drivers if you make sure they're for the right model, but randomly searching for Broadcom drivers without that is likely to find ones for the wrong chip.
Generally, network adapter drivers are quite stable, and it's not surprising that no newer drivers would be available. Whatever drivers worked fine before should work fine now.
Sometimes you see indications of what the problem is in System Information, sometimes you don't.
(shortcut - Start - Run - type: msinfo32 , click OK or press Enter)
On the left side, open up Hardware Resources - IRQs
When the device is built into the mboard, it's usually okay for more than one of certain devices to use the same IRQ, but it's preferable for the built in network adapter to be the only one that uses a specific IRQ.
When you have a network card in the PCI slot, you will probably see that the two different network adapters are assigned an IRQ, probably two different ones.
When you don't have a network card in the PCI slot, when the Broadcom adapter is showing code 10 in Device Manager, there is probably no IRQ listed for the Broadcom adapter.
Also, when the Broadcom adapter is showing code 10 in Device Manager, if you open up Components - Problem Devices, you may see that there is something listed about the Broadcom adapter.
Built in USB 1.x controllers that older mboards have use one IRQ. Built in USB 2.0 controllers that newer mboards have use two IRQs, one for USB 1.1 support, the other for USB 2.0 support. There is usually more than one USB controller related listing than uses the same IRQ, that's fine, but you can have problems in some situations if the IRQs the USB controller related devices use are shared with other devices.
On a desktop system, you're more likely to have that problem when a card is installed in a mboard slot other than the dedicated one for a video card (the AGP or PCI-E X 16 slot on newer mboards).
Things you could try.
When the Broadcom adapter has the code 10 error in Device Manager, look at it's Properties
- if it says it's disabled, try enabling it.
- if it says there is some other problem, RIGHT click on the Broadcom adapter's name, choose Un-install, click on OK, reboot.
That MIGHT re-install the drivers automatically and it might then work fine. If not, try re-installing the drivers for it, taking into account what I told you you need to do above (un-install any listing for it in Add Remove programs, reboot if that apllies, un-install it in Device Manager if it's still listed there, reboot, install the drivers after the desktop has loaded.)
Go into the bios Setup and find the setting for "PNP aware operating system (OS)" or similar - whatever that is set to, try setting it to the other choice, Save bios settings. Sometimes changing that shifts IRQ assingments in Windows and solves an IRQ conflict problem.
These also might shift IRQ assignments and solve an IRQ conflict problem...
If you're not using a PS/2 mouse, go into the bios Setup and disable the PS/2 mouse support - doing that usually frees up IRQ 12, which a few devices including network adapters and USB controllers can use.
Go into the bios using a PS/2 keyboard. Disable all the USB controllers, if you can (you may only be able to disable the USB 2.0 controllers , not all of them, which is less likely to help.)
Boot the computer into Windows a least once.
If you were using a USB mouse and have no mouse in that situation,
- if you need to Logon while booting, use the Tab key to toggle which choice is active, Enter to choose it, type the password if you need to
- after Windows has loaded, press Alt-Ctrl-Del, then Alt-U, then R to Restart the computer.
Go back into the bios Setup and enable the USB controllers.
Sometimes doing that shifts which IRQ(s) the USB controllers use(s). E.g they can often use IRQ 12 .