AMD64 + 2.6.7 initialisation issues

crazyfreekz · 05-31-04, 07:38 PM

Having problems getting this working...

I've recently switched to fedora core 2, x86-64 version.
I've recompiled a new kernel, specifically 2.6.7-rc1-mm1

I had tried the installer off the nvidia site, to no avail, then tried the 2.6 amd64 patched version that is linked to from minion.de.

It compiles fine, or seems to. The kernel module exists,a nd when doing an X -configure it gives the nvidia driver, and the long list of supported hardware. So I guess the module is fine.

However, when I start X, it says "no screens found."

When using the normal nv module, everything works fine and dandy.

I've tried with and without noapic and acpi=off, and as far as I know, the 4K stacks thingy isn't set up in the kernel - nothing in the .config anywhere has it.

Anybody got an ideas on what's next?

Cheers,

Nick.

Linegod · 05-31-04, 08:02 PM

You didn't specifically state it, so I'll ask: 'Is the nvidia module loaded?'

# lsmod|grep nv

If not:

# modprobe nvidia
$ startx

crazyfreekz · 05-31-04, 08:11 PM

Whoops. You'd think I'd get that right by now.

Still, didn't help. I get a black screen as if it's initialised the monitor, but nothing works, apart from me hitting reset.

So I guess it found the screen, but something else is screwed.

Attached is my xorg.conf and Xorg.0.log from when it crashes. (That's without the modprobe nvidia... which is probably kinda useless. The xorg.conf might be helpful though.)

crazyfreekz · 05-31-04, 08:38 PM

Here's the log when it dies at the black screen.

Setup:
Athlon64 3200+
1GB RAM
Gigabyte K8N Pro
GeForce2 MX400

taylor · 05-31-04, 09:08 PM

I'm using the stock FC2 kernel so the same rules may not apply but I had a similar problem when installing NVIDIA's drivers for x86_64. The problem turned out to be that the installer didn't add the nvidia alias line to /etc/modprobe.conf. Adding "alias char-major-195* nvidia" got X working fine with the nvidia driver. Don't know if it's your problem as well but it may be worth a look.

Linegod · 05-31-04, 09:15 PM

The only two things I can see out of the Xorg.0.log are that you might try setting your 'NvAGP' to '1' instead of '2' and if you are using an LCD with DVI, switch to the normal VGA cable until you get it working then switch to DVI.

crazyfreekz · 05-31-04, 09:21 PM

It seems to work fine on the stock FC2 kernel. Weird.
I'll try again with the same kernel arguments for the other kernel.

This is running with NvAGP 1.
Kinda slow though, glxgears is giving me 80-100 fps.

I'm not on an LCD. Plain old CRT for me

crazyfreekz · 05-31-04, 09:36 PM

Oh well, I decided to just stick with the stock kernel.

I put a new kernel on, mainly because I needed NTFS support. Now I don't need that, so I can just go back. (Yes yes, I know, I could've just compiled the module for the current kernel.)

Anybody know of any tweaks to get faster fps? I was getting 180 with the nv driver, and only 90 or so now.

EDIT:
390 frames in 5.0 seconds = 78.000 FPS
456 frames in 5.0 seconds = 91.200 FPS
283 frames in 5.0 seconds = 56.600 FPS
248 frames in 5.0 seconds = 49.600 FPS
451 frames in 5.0 seconds = 90.200 FPS
448 frames in 5.0 seconds = 89.600 FPS
X connection to :0.0 broken (explicit kill or server shutdown).

Leaves a lot to be desired :P

crazyfreekz · 05-31-04, 10:30 PM

Well, for some reason it's now going at ~800 fps. And I didn't really change anything.
Thanks for the help.

EDIT:
I figured out why it was so damn slow. Seti@HOME was taking up all the clock cycles, even when set to a nice of 19.

Silly, because glxgears runs at 0, which *should* mean it gets priority if needed.

Oh well, looks like I just turn off seti when I need 3D :P

05-31-04, 07:38 PM	#1
crazyfreekz Registered User Join Date: May 2004 Posts: 6	AMD64 + 2.6.7 initialisation issues Having problems getting this working... I've recently switched to fedora core 2, x86-64 version. I've recompiled a new kernel, specifically 2.6.7-rc1-mm1 I had tried the installer off the nvidia site, to no avail, then tried the 2.6 amd64 patched version that is linked to from minion.de. It compiles fine, or seems to. The kernel module exists,a nd when doing an X -configure it gives the nvidia driver, and the long list of supported hardware. So I guess the module is fine. However, when I start X, it says "no screens found." When using the normal nv module, everything works fine and dandy. I've tried with and without noapic and acpi=off, and as far as I know, the 4K stacks thingy isn't set up in the kernel - nothing in the .config anywhere has it. Anybody got an ideas on what's next? Cheers, Nick.

05-31-04, 08:02 PM	#2
Linegod Registered User Join Date: Nov 2003 Posts: 10	Re: AMD64 + 2.6.7 initialisation issues You didn't specifically state it, so I'll ask: 'Is the nvidia module loaded?' # lsmod\|grep nv If not: # modprobe nvidia $ startx __________________ -- Live fast, die young You're sucking up my bandwidth

05-31-04, 09:08 PM	#5
taylor Registered User Join Date: Mar 2004 Posts: 1	Re: AMD64 + 2.6.7 initialisation issues I'm using the stock FC2 kernel so the same rules may not apply but I had a similar problem when installing NVIDIA's drivers for x86_64. The problem turned out to be that the installer didn't add the nvidia alias line to /etc/modprobe.conf. Adding "alias char-major-195* nvidia" got X working fine with the nvidia driver. Don't know if it's your problem as well but it may be worth a look.

05-31-04, 09:15 PM	#6
Linegod Registered User Join Date: Nov 2003 Posts: 10	Re: AMD64 + 2.6.7 initialisation issues The only two things I can see out of the Xorg.0.log are that you might try setting your 'NvAGP' to '1' instead of '2' and if you are using an LCD with DVI, switch to the normal VGA cable until you get it working then switch to DVI. __________________ -- Live fast, die young You're sucking up my bandwidth

05-31-04, 09:21 PM	#7
crazyfreekz Registered User Join Date: May 2004 Posts: 6	Re: AMD64 + 2.6.7 initialisation issues It seems to work fine on the stock FC2 kernel. Weird. I'll try again with the same kernel arguments for the other kernel. This is running with NvAGP 1. Kinda slow though, glxgears is giving me 80-100 fps. I'm not on an LCD. Plain old CRT for me

05-31-04, 09:36 PM	#8
crazyfreekz Registered User Join Date: May 2004 Posts: 6	Re: AMD64 + 2.6.7 initialisation issues Oh well, I decided to just stick with the stock kernel. I put a new kernel on, mainly because I needed NTFS support. Now I don't need that, so I can just go back. (Yes yes, I know, I could've just compiled the module for the current kernel.) Anybody know of any tweaks to get faster fps? I was getting 180 with the nv driver, and only 90 or so now. EDIT: 390 frames in 5.0 seconds = 78.000 FPS 456 frames in 5.0 seconds = 91.200 FPS 283 frames in 5.0 seconds = 56.600 FPS 248 frames in 5.0 seconds = 49.600 FPS 451 frames in 5.0 seconds = 90.200 FPS 448 frames in 5.0 seconds = 89.600 FPS X connection to :0.0 broken (explicit kill or server shutdown). Leaves a lot to be desired :P

05-31-04, 10:30 PM	#9
crazyfreekz Registered User Join Date: May 2004 Posts: 6	Re: AMD64 + 2.6.7 initialisation issues Well, for some reason it's now going at ~800 fps. And I didn't really change anything. Thanks for the help. EDIT: I figured out why it was so damn slow. Seti@HOME was taking up all the clock cycles, even when set to a nice of 19. Silly, because glxgears runs at 0, which should mean it gets priority if needed. Oh well, looks like I just turn off seti when I need 3D :P