7800gtx + P4 630 + Gentoo AMD64 = problem

[Curs0r]

Howdy folks, I got this monster MSI 7800gtx and a whole lotta trouble to go with it. In Gentoo AMD64(2005.1) I get a black screen and the system hard locks when i start X. This issue turned out to be identical in Fedora Core 4 (just for reference, I'm a Gentoo fan). In both cases I tried using the 7667 and the 7676 NVidia drivers with the same results for both. The card works fine, beautifully in fact with 32bit linux distros. Posting my xorg.conf file here won't be much help as the good people in the irc room #gentoo-amd64 (except for kumquat) went over it and no one could find a flaw in that. I think it's possible that the problem could be my motherboard (ECS 915P-A) as it has both AGP and PCI-E. If anyone else is having a similar issue or could offer any advice please post a reply. I know that I won't be happy if I retreat to 32bit.

[feliperal]

This seems to be a problem with most pci-express cards and amd64/em64t systems. I have tried to get X working on a 6800 ultra and now with the MSI 7800 GTX card. I was able to get the 6800 ultra running under the 6629 drivers. I'm not too sure if the 7800 GTX will even run with these drivers, but you can give it a try.

BTW, you can look at these threads, which talk about the problem:

[uri=http://forums.gentoo.org/viewtopic-t-33 ... t-325.html]Xorg Lockups part 2l[/uri] (Look at my post specifically about 64-bit BARs)
[uri=http://forums.gentoo.org/viewtopic-t-31 ... ight-.html]Xorg Nvidia 7167 x86_64 hardlocks when I startx[/uri]

This has been a known issue throught the 7xxx series of drivers and pci express nvidia cards. It is frustrating that Nvidia has not addressed or even came out with a fix for this problem, and pci express cards have been in the market for almost a year now.

[Curs0r]

Well, after an exhaustive search for someone else that has this same motherboard I finally found one. He doesn't have the same video card or even use linux but it turns out he has a similar audio issue to one I'm having in XP x64. Talking to many other people about their hardware I find that not many people have this same audio issue (stuttering and crackling when gaming). I think this and other issues are probably caused by this motherboard. I shall know in 2 or 3 days when my new MSI motherboard arrives. Little tip for the people out there: DO NOT be seduced by low priced equipment, you'll probably run into many mysterious issues and end up buying a more expensive board anyway.

[feliperal]

Well, after an exhaustive search for someone else that has this same motherboard I finally found one. He doesn't have the same video card or even use linux but it turns out he has a similar audio issue to one I'm having in XP x64. Talking to many other people about their hardware I find that not many people have this same audio issue (stuttering and crackling when gaming). I think this and other issues are probably caused by this motherboard. I shall know in 2 or 3 days when my new MSI motherboard arrives. Little tip for the people out there: DO NOT be seduced by low priced equipment, you'll probably run into many mysterious issues and end up buying a more expensive board anyway.

I'm not running a cheap motherboard. I have a Iwill dn800-sli with 2 x dual core Xeons, pci-express msi 7800 gtx, and 2 gb of ddr2-400 ram. It is a problem with hardware functioning outside of the 64-bit addressing space.

About 64-bit fucking windows. I tried to exchange my old copy of SP1, but the MS fucking site wouldn't allow to exchange my OEM copy. IT is a legitimate copy, and I have guarded the serials and windows ID vigilantly. I got a email from Microsoft support telling me to wait a few months to wait till they add my key to the database. Well, tried a few months later, and found that the prograam had ended. I deserve my free fucking upgrade. Well, fucking Microshit, I am not going to pay $150 for your fucking OS. I'm going to pirate what I truely deserve and which was promised to people with 64-bit processors and a legitimate copy of Windows.

Bill Gates can go take a fat dick up his ass!!!!

[Birtz]

feliperal, that was just hillarious, can't stop laughing (sorry)

[feliperal]

feliperal, that was just hillarious, can't stop laughing (sorry)

Well, the Microsludge Technology Advancement Program stated to qualify:

1) You must have purchased or built your x64-based PC between March 31, 2003 and June 30, 2005.
2) Have a legitimate copy of Windows XP.

I fufilled both of those stipulations. I feel ripped of and mislead. I am entitled to my free upgrade, and if I had big pockets, I'd sue Microsoft, or at least try to publicly humilate them. I will not pay for Windows XP 64-bit!

[nukem996]

While I didnt have this problem I had a problem were when I launched a game the computer what start to lock. I was lucky that Doom III I could still use the console to quit, once I did I found an error message telling me to add irqpoll to my boot options, after I did that it fixed the problem. For an SATA problem I had I also had to add noapic incase that helps.

[Curs0r]

Well, I got my new MSI motherboard and every single one of the issues I had before still exists. I have to guess at this point that the Intel CPU is to blame, it has to be since I've changed everything else already. This is very very frustrating.

[sarumont]

Well, I got my new MSI motherboard and every single one of the issues I had before still exists. I have to guess at this point that the Intel CPU is to blame, it has to be since I've changed everything else already. This is very very frustrating.

Not a good idea. I'm running on dual AMD 246s and an Asus K8N-D with an XFX GT6600 PCIe. Same issue. I thought it was just the 6600s...glad I didn't shell out some extra $$$ to fix it with a new card.

Threads for reference:

http://forums.gentoo.org/viewtopic-t-35 ... ight-.html
http://www.nvnews.net/vbulletin/showthr ... ge=1&pp=15

Guess nVidia's solution for us is to take our thumbs and shove them up our asses.

[feliperal]

Well, I got my new MSI motherboard and every single one of the issues I had before still exists. I have to guess at this point that the Intel CPU is to blame, it has to be since I've changed everything else already. This is very very frustrating.

Not a good idea. I'm running on dual AMD 246s and an Asus K8N-D with an XFX GT6600 PCIe. Same issue. I thought it was just the 6600s...glad I didn't shell out some extra $$$ to fix it with a new card.

Threads for reference:

http://forums.gentoo.org/viewtopic-t-35 ... ight-.html
http://www.nvnews.net/vbulletin/showthr ... ge=1&pp=15

Guess nVidia's solution for us is to take our thumbs and shove them up our asses.

The solution is to run your box in 32-bit mode. I suggest, getting a 32-bit copy of fedora core and using that for playing games.

[sarumont]

Well, I got my new MSI motherboard and every single one of the issues I had before still exists. I have to guess at this point that the Intel CPU is to blame, it has to be since I've changed everything else already. This is very very frustrating.

Not a good idea. I'm running on dual AMD 246s and an Asus K8N-D with an XFX GT6600 PCIe. Same issue. I thought it was just the 6600s...glad I didn't shell out some extra $$$ to fix it with a new card.

Threads for reference:

http://forums.gentoo.org/viewtopic-t-35 ... ight-.html
http://www.nvnews.net/vbulletin/showthr ... ge=1&pp=15

Guess nVidia's solution for us is to take our thumbs and shove them up our asses.

The solution is to run your box in 32-bit mode. I suggest, getting a 32-bit copy of fedora core and using that for playing games.

You misuse the word solution. That's not a solution; it's a workaround.

I realize that a 32-bit system would work. I was just throwing in information I had dug up to save Curs0r from spending needlessly.

[paulisdead]

Are you guys using any extra options to boot up your kernels with? I think i have had a similiar problem with the 6800 and 7800 series with newer drivers if I don't bootup my kernels with the "pci=biosirq" option on the kernel line in grub. I've been booting with that option now for so long, I almost can't remember exactly why.

Code: Select all

kernel /2.6.13-rc6 root=/dev/sda3 video=vesa:ywrap,mtrr vga=0x31A pci=biosirq pci=irqroute clock=pmtmr notsc

There's everything I bootup my kernel with if you're intrested, though the irqroute clock and pmtmr are what I used to fix a timer bug with the X2 CPUs. You can also try pci=noacpi.

If this fixes it, you guys are gonna kill me for keepin my mouth shut so long.

[feliperal]

Are you guys using any extra options to boot up your kernels with? I think i have had a similiar problem with the 6800 and 7800 series with newer drivers if I don't bootup my kernels with the "pci=biosirq" option on the kernel line in grub. I've been booting with that option now for so long, I almost can't remember exactly why.

Code: Select all

kernel /2.6.13-rc6 root=/dev/sda3 video=vesa:ywrap,mtrr vga=0x31A pci=biosirq pci=irqroute clock=pmtmr notsc

There's everything I bootup my kernel with if you're intrested, though the irqroute clock and pmtmr are what I used to fix a timer bug with the X2 CPUs. You can also try pci=noacpi.


If this fixes it, you guys are gonna kill me for keepin my mouth shut so long.

I tried feeding the pci=biosirq and pci=noacpi. Howerver it doesn't work on my setup:

Iwill dn800-sli
MSI 7800 GTX
2 x 3.6 Xeons
2.6.12-gentoo-r9
1.0-7676 Nvidia Driver

I think its a 64-bit problem and pci-express cards. I've had this since the 6800 ultra came out. I was only able to get the 6800 ultra card to work with the 1.0-6629 drivers. I've tried numerous boot options, kernels, xorg-cvs and regular xorg.; putting my thumb up my ass and hoping it would work.

If you go and check the forums at nvnews, alot of people are having these freeze ups and lockups, regardless of distribution.

I am very upset and frustrated with Nvidia.

[Adwin]

1: Check if you have got PCI-X enabled in the kernel.
2: Disable NvAGP in xorg.conf, instead, specify the pcibus address of the video card in the xorg.conf.
That should help.

[paulisdead]

pci-x is totally different than pci-e, but specifying the bus id might work.

Another thing to try would be to strip down your system as much as possible. Remove all addin cards except the video card, get rid of the mouse, optical drives, etc, and disable everything in the bios like parellel, floppy, serial ports, etc, just for the hell of it, since damn near everything else has been tried. A stripped down kernel to the bare minimum to run X with nvidia's drivers might not be a bad idea either. Bios updates to the mobo might not be a bad idea if that hasn't been done, just always reset the cmos on the board after you update it, surprising how many people don't do that.

[whig]

feliperal, that was just hillarious, can't stop laughing (sorry) :lol:

Well, the Microsludge Technology Advancement Program stated to qualify:

1) You must have purchased or built your x64-based PC between March 31, 2003 and June 30, 2005.
2) Have a legitimate copy of Windows XP.

I fufilled both of those stipulations. I feel ripped of and mislead. I am entitled to my free upgrade, and if I had big pockets, I'd sue Microsoft, or at least try to publicly humilate them. I will not pay for Windows XP 64-bit!

MS stuffed up. They should have released Win 64 Pro that installs and boots only if it finds a valid, activated copy of Win 32 Pro on a partition on your hdd. A 64 bit driver/app not work? Reboot into 32 for it while you wait for a patch.

[sarumont]

I'm actually starting to think that this is a kernel problem, not an nVidia driver issue. Check this out from dmesg:

Code: Select all

PCI: Cannot allocate resource region 0 of device 0000:02:00.0
PCI: Cannot allocate resource region 3 of device 0000:04:00.0

and 0000:04:00.0 is my GT6600. Now when I check out /sys:

Code: Select all

Thu Sep 08 -- 10:39:32
~
sarumont@illusion $ cat /sys/bus/pci/devices/0000\:04\:00.0/resource
0x00000000f8000000 0x00000000fbffffff 0x0000000000000200
0x00000000c8000000 0x00000000cfffffff 0x000000000000120c
0x0000000000000000 0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000 0x0000000000000000
0x00000000d0000000 0x00000000d001ffff 0x0000000000007202

If my assumptions are correct, the resource "file" lists the registers allocated for this PCI device. That being the case, there are some addresses in there in excess of the 4GB mark, whereas I only have 2GB of RAM. I can't be 100% on this, but I do feel that the first part from dmesg is pertinent to the issue.

[neuron]

I will not pay for Windows XP 64-bit!

64bit windows is such a lie anyway, it's not 64bit, yeah, the kernel is 64bit, but most of the applications still run in their 32bit emulation layer.

[hooflungpoo]

I will not pay for Windows XP 64-bit!

64bit windows is such a lie anyway, it's not 64bit, yeah, the kernel is 64bit, but most of the applications still run in their 32bit emulation layer.

And how is this different than what we have in Linux x86-64? They have a their 32bit schema and we have ours to make our 32bit stuff work in a 64bit environmet. I dislike MS$ just like the next guy but for real reasons: Legally Stealing VMS and MTFS, Dropping OS/2 when they found the NT ( ie stolen VMS OS ) could give them sole domination and their clever, albeit illegal trade practices. If any OS for x64 is pure of 32bit application compatability layers then let that OS cast the first stone.

[neuron]

64bit linux is true 64bit, the entire thing kernel and applications are compiled in 64bit and runs in true 64bit mode.

windows however runs 32bit applications in their WOW layer, because they couldn't be arsed with dealing with 32bit plugins for example.

This is why flash for example runs fine in internet explorer on 64bit windows, because it isn't in any way 64bit.

[sarumont]

Looks like this patch is supposed to fix it:

http://www.nvnews.net/vbulletin/showthread.php?t=56150

Using that, my box just restarts itself rather than Black Screening. I'm going to play with it a bit more, and I'll report back if I figure anything out.

[Curs0r]

That patch fixed it for me in FC4 but I do not know how to apply it in gentoo.

[sarumont]

You do exactly as he says. You'll have to emerge --unmerge nvidia-kernel nvidia-glx then do what the guide tells you. The OpenGL 32-bit compatibility doesn't install on my box, so I tell it to skip that.

[sarumont]

OK...working now. Here's sorta what I did:

Code: Select all

emerge =xorg-x11-6.8.99.15-r2 (not sure if this is required)
emerge nvidia-kernel
emerge -C nvidia-kernel
sh /path/to/NVIDIA-Linux-x86_64-1.0-7676-pkg2.run --extract-only
cd NVIDIA-Linux-x86_64-1.0-7676-pkg2
patch -p0 < /path/to/NVIDIA_kernel-1.0-7676-1359015.diff.txt
make install
modprobe nvidia
emerge -O --oneshot nvidia-glx
eselect opengl set nvidia
xinit

Now you may have to create the device nodes:

Code: Select all

mknod /dev/nvidiactl c 195 255
for nn in 0 1 2 3 4 5 6 7 ; do
        mknod /dev/nvidia$nn c 195 $nn
done

chown root:video /dev/nvidia*
chmod 0660 /dev/nvidia*

But now I'm working with 3d accelleration *and* TwinView...no longer crippled by one monitor.

Edit: Added the --oneshot flag to the glx emerge to keep portage from trying to update this in the future.

[sarumont]

Oh yeah...you'll have to add to your /etc/portage/package.mask:

Code: Select all

media-video/nvidia-kernel
media-video/nvidia-glx

so that an emerge -auDv world doesn't try to overwrite what we did with the drivers.