Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with AMD processors => Topic started by: vbgunz on January 13, 2011, 06:23:56 pm
-
Sorry about this being long and winded but it's detailed. I just RMA'd a board with Newegg and am very close to RMA'ing its replacement. I love Newegg and this is the first (about to be second RMA) I've ever had to do with them in years I've been a loyal customer. I believe I triggered a hardware defect. I'll explain.
I dual boot. I have Windows 7 and Kubuntu 10.10 *both* 64bit and updated. After the motherboard installation and first boot, Kubuntu ran like a champ. Upon bootup to Windows 7, I had to install everything under the sun (CD). After all was said and done, both OS ran happily. My usual use at dual booting is hibernate Kubuntu and boot into Windows. Shutdown Windows and resume Kubuntu. I have always done this. This has always worked.
One day, out of nowhere, the networking just stopped working. I swapped cables. I thought it fried. Kubuntu wouldn't connect. So, I boot into Windows. Windows wouldn't connect. I boot into the BIOS and the Smart LAN function couldn't connect. Every other device in the house was connected but my gigabyte motherboard refused to connect. I was convinced the ethernet port blew out. So, I remove all the cables and open the case. I insert a wireless card and BOOM the ethernet (not just the wireless) was working again.
I google for details and come up with nothing. Then after a while, I get hit by no networking again. I figure maybe if I remove the wireless card, it'll magically heal up? I removed the card and boot up. Nothing. I tried Kubuntu, Windows and the Smart LAN function. No ethernet. I re-insert the wireless. No matter how hard I try, nothing works. I call gigabyte and they can't help. They told me to RMA the board so I call up Newegg. They handled it like a boss. Had a new board out the door for me before I could hang up. I'm happy and a bit sour (this is my first gigabyte product ever).
So, I remove all cables to the case and put it back under the desk. Plug all the cables back in and boot up. BOOM. The ethernet works. At this point I'm thinking about calling up Newegg and canceling the RMA. I don't do it though. And lucky. I get bit by this several times again and again before the replacement arrives. So what's the solution? Physically going under my desk and cutting off all power to the PSU. Ridiculous. I tried shutting down the PC normally and no matter how long I leave it off, this doesn't work. I have to remove all power flowing to the PSU for at least a minute. Really?
I called gigabyte and asked if they knew anything about this issue. Sort of futile. I visit the official Gigabyte site and join up with the gigabyte club. Sort of futile. I end up googling for a place where I can maybe get some official input about this problem and I end up here. So basically, the networking capability of the board turns absolutely off no matter what OS I'm in. Nothing but shutting down all power fixes it. Does anybody know what in the world is happening with this board? Surely I can't be the only one?
-
Hi there,
The latest Microsoft update driver breaks the Ethernet driver roll back your driver all should be well.
This quote was taken from a thread reporting a similar issue. Check here: http://forum.giga-byte.co.uk/index.php/topic,4038.0.html If you read through this thread you'll see that I had a similar issue.
-
Note that Gigabyte has released a new Ethernet driver on 21 Dec 2010. Are you using the latest driver? (Will not help the Kubuntu OS but maybe the Ethernet gets clobbered in Windows before you get back to Kubuntu).
-
I went here and got this http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false (http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false). This might have solved something. I have never had an experience where hardware state carried over from OS to OS. Even the failsafe and optimized defaults in the bios couldn't fix it. Only pulling the power. Is Gigabyte working on this? I believe a firmware update is needed for this. This is sort of why I came here. Is this a known issue and is it being worked on?
-
Actually I was thinking about:
http://www.gigabyte.com/products/product-page.aspx?pid=3516&dl=1#dl
But you may have the same thing.
After i bought my board I looked closer at the comments on the product at NEWEGG (where i bought mine). There were a lot of complaints about the LAN.
So when I brought my board up I specifically looked at the Gigabyte web site and downloaded the latest drivers for everything. Seemed to work for me.
I figure Gigabyte knows about this issue and is activelly trying to fix it (BUT I have no real knowledge of that - only they read the product reviews also - so they SHOULD know).
-
The thing that bothers me; the thing nobody seems to address is the severity of this. I could absolutely and totally understand how one messed up driver can mess up one OS but in 15 years, I've never come across a fault in any one driver that had the ability to completely disable one piece of hardware. I was on the phone with gigabyte support for 20 minutes and they had no clue what the issue was. I'm just here hoping someone can officially address this behavior. I don't at all feel comfortable about it as it strikes at random times.
-
I have considered that this problem is largely caused by some kind of BIOS bug.I have seen similar behavior when network of my ISP for some reason began to fail- LAN completely froze and only thing that helped me to reconnect again was full cmos reset ... PCI NIC always "refreshed" itself,onboard not...
-
I have GA-890GPA-UD3H revision 2.1. This is my first gigabyte product ever. I'm not gonna be a child about this and cry and whine about it; go give it 1 star/egg and recommend people stay away or worse. To be honest, I think this board is a champion. When the ethernet is working, everything seems flawless. Everything works for me, everything is stable, I did a memtest with the first board (no errors) and the installation was very easy.
I'm sort of happy with the board and I want to keep it (has all the connections I need) and provides a great upgrade path but this one issue with the networking is like a splinter in my mind. I just want to feel comfortable and am hoping for a "We know about this issue, here's a geeky explanation, we're working on it". That would make me feel a ton better.
-
It seems that Gigabyte has a big problem to admit their own mistakes, I have noticed that too. Again and again just expressing regret that the user is disappointed with their products ... and the problem remains unresolved or is resolved partially,it's as if they didn´t know what´s wrong...or did not care what they produce... :(
-
It seems that Gigabyte has a big problem to admit their own mistakes, I have noticed that too. Again and again just expressing regret that the user is disappointed with their products ... and the problem remains unresolved or is resolved partially,it's as if they didn´t know what´s wrong...or did not care what they produce... :(
or more to the point they like any big company don't want to admit liability and have to spend money putting things right. Much cheaper just to say "sorry".
-
At this point, I'll take "I'm sorry" Vs nothing. I dont' want to hate my first gigabyte product. I was just hoping for some stellar support.
-
if the ETHERNET stop working, and you get "not connected to LAN" or how is it exactly that is not working?
If you reboot the Modem or Router or whatever you're using, doesn't even connect then?
I had a big problem with my board that is a GA-890FXA-UD5; I was losing connectivity every hour but the problem was with my router, so I replace my router and everything is been working very good ever since
-
if the ETHERNET stop working, and you get "not connected to LAN" or how is it exactly that is not working?
If you reboot the Modem or Router or whatever you're using, doesn't even connect then?
I had a big problem with my board that is a GA-890FXA-UD5; I was losing connectivity every hour but the problem was with my router, so I replace my router and everything is been working very good ever since
Christoph, I have the same motherboard and use Ubuntu 10.04 32bit along with Windows7 "seperate hard drives" and run the OS's seperate of each other. After running Ubuntu I have to disconnect the power to the PSU or Win7 only recognizes the connection as 10megs/min instead of 1000megs/min. It seems this is a hardware problem as vbgunz has stated with this Lan Card.
Tim
-
then why I am not having that problem?
I think I'm using the latest driver for my Ethernet port from the Realtek as I downloaded an update few months ago
-
I think I know where's the problem, don't know quite well if really has anything to do or whatever, you can call me crazy but
I noticed that W7 makes up to 300 connections thru LAN just to surf the NET, against WXP that's make around 40 to surf the net, then If your router (what happened to me) doesn't support multi-connections like for P2P software the router drops connection to the device (this is why even Ubuntu was not able to connect to LAN, cuz the router drops conecction by MAC address), this was back then known as a "protection" against hackers
now that I upgraded my router I can even download stuff with my 3 computers at the same time without a problem
don't know really but this was clear for me...
the 2WIRE router has this "protection" and if you start downloading stuff, the router itself would kick you out the conecction and give you an message about having too many connections at the same time and that you could've been hacked, and actually you can "disable" this "protection" from the router's firewall.
-
I experienced this: onboard LAN stopped working. I tried my other PC - network worked flawlessly, so I thought the onboard LAN is bad. I put a PCI NIC from this PC into my "main" PC, it worked about 2 days ... and stopped working. I switched back to the onboard LAN ... it worked. Two days later, stopped again! WTF???! After a few days I found out that someone trying to hack the network and router is blocking my MAC addresses! :o
-
I experienced this: onboard LAN stopped working. I tried my other PC - network worked flawlessly, so I thought the onboard LAN is bad. I put a PCI NIC from this PC into my "main" PC, it worked about 2 days ... and stopped working. I switched back to the onboard LAN ... it worked. Two days later, stopped again! WTF???! After a few days I found out that someone trying to hack the network and router is blocking my MAC addresses! :o
did you actually found out that you were hacked?
like I said, some modems have this "feature" and IT takes it AS HACK ATTACK
-
I'm 99.99% sure. When problems started, Windows reported that my internal IP (provided by my ISP and manually saved, no DHCP) is currently associated with the device with MAC address I had NEVER seen before and in any case it came from the "outside"..
-
After getting the latest LAN driver from here http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false (http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false) about 3 days ago, the issue hasn't popped up since. As for my MAC address getting blocked at the router, this just wasn't the case. I do have MAC filtering on the router and I do use it for all my devices *but* I never set up the wireless MAC filter. The wireless never connected before this issue and no matter how badly I tried to set it up, it wouldn't work. Nothing networking worked until I removed power from the PSU.
Another thing was, no matter how long I left the PC in the off state, turning it back on when it had the problem kept the problem going. Just removing power for a minute from the PSU, everything came back up normal. I just never had a problem ever with this router in the 5 years I've had it. It's seen plenty of motherboards and connects over 20 live devices in the house. More to the point is I've eliminated the router from the problem.
I've had many driver issues in my life. Never once did I have a driver issue that affected every OS and SmartLAN? Gigabyte technical support couldn't help and recommended I RMA the board. I found out how to solve the problem completely by accident. I haven't had this problem since the Windows 7 driver update *but* it is constantly in the back of my mind.
-
hmmm
that's why some ISP supports just one device connected to the router (internet), and that is why many (almost every one) aftermarket router support the cloning of your computer MAC address to the router MAC address, so this way the modem thinks that the router connected to IT, is actually your computer
Well I can't say that you guys are the first users with this problem as I seen it before, but I can say that I didn't have this problem even when using the same driver...
really don't know what to think and please is not like I'm trying to be a troll about this
-
Hi,
This whole scenario sounds familiar to me so let me throw this into the mix..Several months ago on my wife's computer running WinXP and an older Asus board she complained she could not always get on the Internet..I had previously tried to update AVG but it failed..I then thought of a malware problem so I scanned it with Kespersky cd rescue disk..It called out that it found a trojan..It offered to delete it so foolishly I did.
Soon after the computer complained of an ethernet problem..I had just made an image using terabyte so I thought ok why not ..
I reinstalled an image I made just days previous when there was no problems and much to my surprise the same problem..It indicated a defective ethernet card..As a last ditch effort I substituted the cable and still no go..I rebooted the cable modem and the Router and Volia!!
The internet came back and is still working today and has not missed a beat..Was it the cable or the router reboot??? I still do not know ..
I suspect that somehow the handshake between the router and the ethernet card was corrupted somehow but that is just a guess..
The only thing I know is that a software problem can cripple hardware...I have no idea how it affects the firmware of the interface card..
jolphil ???
-
I never ever try the cable first. Too much work. I did though switch the cable and whenever theres a networking problem I shutoff the modem and the router first. Then I turn on the modem first and wait for it to get situated. Once that's done, I plug in the router. Then boot up. Still no net connection. In case, people with this problem keep missing the solution that's works for me, "It's to *unplug* (not just power down), your rig; killing power at the mains for at least a minute".
-
what I noticed with my old router is that IF I boot up my modem first and then the router, this one wouldn't get the WAN IP
but if I boot up the router first and then the modem would get to work right away, so it my be different with every user, depending on the routers model/brand