Internet problem with new motherboard.

w_Alpha

Reputable
Jan 21, 2016
5
0
4,510
Hi.
I have problems probably with my motherboard.
I brought it to get a bit more RAM in my MB.
But it's not story about it.

MB - GA-M57SLI-S4
Internet doesen't work on it. It looks like it haven't right drivers but I had tryed bunch of them. Even on ubuntu internet doesn't work it says connected but nothing. Maybe something in BIOS? Reinstalling windows with some kind of universal drivers doesen't work.

Maybe network card can help?

Please help. ;)
Sorry for my bad English.
 
Solution
Sorry it took so long to get back. Not on all of the time. I think the issue is that this is a driver or hard ware problem with the onboard nic. There are lots of trouble shooting test you can do but they are network trouble shooting. You would have gotten better answers in the Networking Forum than here but here are some things you can do.

1) get another NIC like you said you are doing.

2) Test the network cable you are using. You can do this by plugging both ends of the cable into your Home Portal and it should cause what is called a broadcast storm lighting up the activity lights on both connections. If it does not then your cable may have become damaged.

3) Test you NIC. You can do this my pinging the loopback. Go to the command...

JimF_35

Distinguished
Are you saying your network connection quit working after you got a RAM update but it worked before?

There is a way to turn off the onboard network card through the BIOS, so yea you can check that.

http://download.gigabyte.asia/FileList/Manual/motherboard_manual_ga-m57sli-s4_2.0_e.pdf

Look at page 41.

Last question, are you only running Linux on this computer or Windows. If it is Ubuntu then you will need to find the appropriate driver. Not sure which Kernel version you are running but try this...

http://www.marvell.com/support/downloads/search.do#

 

w_Alpha

Reputable
Jan 21, 2016
5
0
4,510
Nope I had different motherboard before all worked well.

Orginaly I'm on windows 7, I was using Ubuntu live (non-install) version.

Actualy BIOS - Auto detctecting LAN (page 42 or 43) says that I have problems with cables, but on old motherboard all worked as charm.
 

JimF_35

Distinguished
Sorry it took so long to get back. Not on all of the time. I think the issue is that this is a driver or hard ware problem with the onboard nic. There are lots of trouble shooting test you can do but they are network trouble shooting. You would have gotten better answers in the Networking Forum than here but here are some things you can do.

1) get another NIC like you said you are doing.

2) Test the network cable you are using. You can do this by plugging both ends of the cable into your Home Portal and it should cause what is called a broadcast storm lighting up the activity lights on both connections. If it does not then your cable may have become damaged.

3) Test you NIC. You can do this my pinging the loopback. Go to the command prompt and type the following command PING 127.0.0.1 and note if there is any packets that are lost.

4) Check you DHCP is assigning your NIC a proper IP. You do this by going to the command prompt and typing IPCONFIG. Look at the IPv4 address and it should start with 192.168.x.x if it starts with a 169.254.x.x then your NIC is either not communicating with the DHCP services in your router or the services in your router are down.

5) Try a firmware update. That is they provide a Firmware update for that NIC. It does not area so...

http://www.marvell.com/support/downloads/search.do#

You could try contacting Gigabyte to see if there is one and if there is a tool for flashing your NIC. (It could be a part for the BIOS flash which I believe you have already done)

Last) Take this evidence and send it to Gygabyte as a reason you want an RMA. The above steps will show them that the problem is not in your equipment but in theirs.

I know this is not helping and I should have posted this last night but it is more for others having the same problem. I believe these steps are listed on the Networking form under a troubleshooting guide.
 
Solution