How can I manually enable LAN controller on A7V8X? TIA!

  • Thread starter Thread starter Andy Axnot
  • Start date Start date
A

Andy Axnot

Hi!

I have an Asus A7V8X mobo with an onboard Broadcom LAN controller which
connects to my DSL modem through a Linksys router. I dual boot Win98SE and
Mepis Linux (Debian based). I'm fairly new to Linux and have only a few
weeks experience with Mepis, but I like it quite a bit. It seems great at
finding and installing hardware.

The problem is that it, on booting, probes the hardware including the LAN
controller and resets it, which works fine. But when I log out to reboot to
Windows, it shuts everything down, including the LAN controller! To access
the internet in Windows I have to go to the Device Manager, disable the
controller and then enable it again. NOW the connect LEDs on the router
light and I can connect to the internet.

It works, but it's a PITA. There's a quick and easy utility in Linux to
enable or disable the controller, but I can't find anything similar in
Windows. Incidentally, it makes no difference whether I enable PnP OS in
the BIOS.

Is there some kind of utility that will allow me to start or stop the LAN
(ethernet) controller in Windows? TIA!

Andy
 
Is the LAN option enabled in BIOS as well?

Most mobos that have onboard LAN also
have the option of disabling and enabling it in
the BIOS.

Also does your mobo have firewire onboard?

As sometimes the firewire can bugger around with
the onboard LAN card.
 
Paul said:
Is the LAN option enabled in BIOS as well?

Most mobos that have onboard LAN also
have the option of disabling and enabling it in
the BIOS.

Also does your mobo have firewire onboard?

As sometimes the firewire can bugger around with
the onboard LAN card.
Click to expand...
The only option for the LAN is "Onboard LAN Boot Rom" which is enabled,
which gives a Broadcom message during booting, but does not change the
problem I described.

Please note that this is not a brand new mobo, it's been working fine for
about three months, and STILL works fine, but... Now I have to go through
a song-and-dance to activate the LAN in Windows after using Linux.

Board does have firewire, but that never affected anything before.

Andy
 
Andy said:
The only option for the LAN is "Onboard LAN Boot Rom" which is enabled,
which gives a Broadcom message during booting, but does not change the
problem I described.

Please note that this is not a brand new mobo, it's been working fine for
about three months, and STILL works fine, but... Now I have to go through
a song-and-dance to activate the LAN in Windows after using Linux.

Board does have firewire, but that never affected anything before.
Click to expand...

a while ago i runned winME and nt5.0 with a7v8x and if i restarted to
winME it refused to load but when i shutted down and then power on no
problems at all with winME. I think that your linux (like nt5.0)utilises
hardware different way than win98 (probably apic) and you need to do
clean boot (shut down and power on) to reset bios properly. you could
try 1013 bios because when i played with dual boot bios was older (over
a year ago). sorry my little poor english :)
 
a while ago i runned winME and nt5.0 with a7v8x and if i restarted to
winME it refused to load but when i shutted down and then power on no
problems at all with winME. I think that your linux (like nt5.0)utilises
hardware different way than win98 (probably apic) and you need to do
clean boot (shut down and power on) to reset bios properly. you could
try 1013 bios because when i played with dual boot bios was older (over
a year ago). sorry my little poor english :)
Click to expand...

Hulttio,

Thanks for your response! Unfortunately, the problem persists even after a
cold boot. I will look into the BIOS and APIC more, though.

Thanks again,
Andy
 
Andy said:
Unfortunately, the problem persists even after a
cold boot. I will look into the BIOS and APIC more, though.
Click to expand...
did you load 1013 or 1014.01 beta ? btw. do not put any pci-card to
pci-slot 4 because lan is there already, worth to try.
 
Hulttio,

Thanks for your response! Unfortunately, the problem persists even after a
cold boot. I will look into the BIOS and APIC more, though.

Thanks again,
Andy
Click to expand...



There has been an issue with some ASUS MBs and their MAC address.

This is usually written on a bar code beside one of the disk
connectors. Flashing can screw up the configuration. You can then
recover the situation by manually configuring Windows to use the MAC
address on the sticker.

I had to do this to get a board to work.

The details are over on:

http://www.amdmb.com/index.php

Search around in the ASUS area.

MK




_______________________________________________________________________
Michael Kenward Words for sale
 
Back
Top