Strange issues with K8N-Neo4H / Linux

VirtualLarry

No Lifer
Aug 25, 2001
56,571
10,206
126
I have an older PC cobbled together out of parts.

A (mostly-new) K8N Neo4H, which is an NF4 board with an A64 4000+ CPU (S939). Two mis-matched 1GB DDR DIMMs, a 128MB PCI-E video card, a 200GB SATA HDD (WD), and a SATA DVD-RW drive. Using my Logitech wireless KB + MS dongle in a front USB2.0 port.

In a cheap generic case with a PSU, that may have been pulled from a different case + PSU combo.

Anyways, I hooked it up, it was running some older version of Ubuntu, it prompted for updates after booting, and I upgraded to 12.04.5. That took about two hours, and seemed to complete successfully.

Then I booted that version, and it prompted to update to 14.04. So, a few hours later, and I was on that version too.

I rebooted, and that's when the trouble started.

I clicked on the top Unity search widget, and it popped up, but then the desktop wouldn't respond to mouse clicks. So I hit RESET, and tried it again.

I was able to launch Firefox, but then it was going really slow, and launching the search widget caused the desktop to hang again.

So I thought maybe the HDD was on it's way out. I hit RESET and then powered-off. I then removed the HDD, and connected a 60GB Corsair Force LS SSD, that had an older build of Win10 64-bit.

I tried booting Win10 64-bit, but it gave me an error, most likely because, although I had a 64-bit capable CPU, it didn't support the features that Win10's kernel needs.

So I put in my Linux Mint 17.1 MATE DVD, powered off, powered on, and got a BIOS error that the keyboard wasn't connected.

I tried unplugging the dongle, and plugged it back in the same port, the other front port, and even a rear port. (Note that there was no problem with the dongle, as it later worked fine with my H81 board's front USB2.0 port.)

So, best I can figure, either my K8N's USB2.0 controller is screwed up, or the cheap crappy PSU is going out on me.

I do have a spare PSU to throw in, but I haven't bothered yet.
 

daveybrat

Elite Member
Super Moderator
Jan 31, 2000
5,804
1,015
126
Sounds like a power supply or motherboard problem, easy enough to solve. Just try a spare power supply and if that doesn't resolve it......you know what it is :)