Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I recently got my Athlon64 system put together, fully loaded, did everything myself (quite proud). nforce4 chipset w/PCI-express, 2gb of DDR-3200, Athlon64 3200, huge Antec case, and an NVIDIA 6600 with 256mb GDDR. Naturally, the nice keyboard and mouse (both Logitech, wired, and wireless, respectively)
Now, the first time I booted and installed FC3, it was great, but no h-w acceleration. I went to nvidia's site, got the newest driver, and went about installing them the EXACT way they said.
I didn't konw of a test I should try, so I just typed "glxgears" and the screen blinked to diagonally-tiled noise. The machine locked, NO response, moving the mouse didn't change diddly about the noisy tiled screen. Only thing I could do was reboot.
This only happens when an OpenGL-overlay program comes up, such as glxgears, tuxracer, xscreensaver with any of the gl-based screensavers, maya... The list goes on.
Has anyone seen this? Does anyone have a fix? If not, I'm just using my RMA and sending the stupid card back, because my ATI cards have *always* been under the "Just Works" tm. I'll give any info I need to fix this, it's very urgent.
Also, forgot to mention: I'm running the 32-bit version of FC3 till I can get the dvd-iso of the x86_64 version, so the display drivers I have on there now are the IA32 release.
Would that cause the problem I'm getting? 32-bit OS on a 64-bit system, using 32-bit drivers instead of 64? Seems like it shouldn't make a difference, but I'm just wondering...
I ordered an ABit motherboard (Fatal1ty AN8), and it has the same problem as above.
I ordered an ATI Radeon X700 Pro. First few dozen times I turned on the computer, it wouldn't get a display at all. I pulled half the RAM, and it powered on just fine. I went to lunch, came back, and the display was gone. Doesn't power on again. Nice...
I figured that changing out the main pieces would help, but... The same thing happens with any 64-bit motherboard. Video cards do not work properly. I was told that it's probably too small a power-supply (i have a 400w, i picked up a 600w at Fry's), but after testing it, it did the same thing. Could this be a RAM problem? Doesn't seem logical, but that's the only thing left, other than the CPU...
Has ANYONE had this problem? What is wrong with this stupid godforsaken thing?
Last edited by JamieMcLaughlin; 05-02-2005 at 02:13 PM.
When I use GLX, my screen gets blurred and vertical stripes stripes appear. After a few seconds I get a hard lockup.
This is what I tried:
- I had a dual-boot with Windows, which could perfectly use my card, so it's not a hardware-issue.
- removing everything out of my pc except the videocard. Nothing.
- putting a big fan on my videocard.
- I switched to Debian-based Ubuntu today because I read there were alot of 3D-problems with FC3 (Fedora tends to be a distribution for the buisinessman who has Redhat at work, which doesn't play games). But no luck at all.
Sometimes I get some luck with glx for about 30 seconds and after that I get a lockup.
My next step would be upgrading to an AMD64 with a new videocard, but after reading your post I think I will switch to Apple
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.