New build - Bad motherboard?

nullzilla

Reputable
Oct 13, 2014
2
0
4,510
I just put together my first build - Gigabyte 970a-ud3p Motherboard and an AMD 6350 processor. I have 8GB of Ram in an Antec case with a Corsair 500W power supply. I've loaded Ubuntu 14.04 onto a 256GB SSD as my primary boot device and I also have a WD 1TB drive in it. Due to budget constraints I'm using an old graphics card and monitor salvaged from an old Dell system.

My problem is that I am having major problems getting off the ground with this build. There are 8 USB2.0 ports and none of them work. The only way I can use my keyboard or mouse is to plug them into a USB3 port. Additionally, I cannot get a wired connection to my modem to connect at all. I've tried two different cables and different ports on the back of the modem. The motherboard doesn't have built-in wireless, and I don't yet have an adapter for this computer, so I'm unable to connect at all to the Internet.

The other thing to know here is that I'm a total noob with Ubuntu and Linux in general. I really don't want to use Windows on this build, but I've run out of troubleshooting knowledge with this OS.

My gut is that the motherboard is bad, but I'm hoping to get some expertise and advice on how to confirm that or fix my problems.

Thanks!
 

nullzilla

Reputable
Oct 13, 2014
2
0
4,510
Thanks for convincing me that it was not a bad motherboard. After losing my mind chasing in circles looking for chipset drivers (gigabyte doesn't provide them for linux and recommends that you get them from the chipset mfr., AMD doesn't give a rat's ass about supporting anything but their graphics chipsets), I found a thread on Ubuntu Forums ( here) that gives the answer.



The BIOS default for the IOMMU is Disabled. Change it to Enabled, and everything works as it should!

A quick digest of the cause from the UF thread:

1: Turns out that there is some sort of bug in the nic itself so that the 64 bit Linux OS identifies the built-in as eth1 instead of eth0 and the interfaces file is built by default for eth0.

2: Because of the glitch, the OS is trying to use USB2.0 slots as eth0 in some cases.

Again, thanks for pushing me to keep looking!
 

TRENDING THREADS