nVidia Troubles
 

Hi all. I just got an nVidia MX 4000, tried installing the latest drivers from nvidia, updated the Xorg.conf, but it crashes with sig 11 on `startx'. Useful files (/etc/X11/xorg.conf, /var/log/Xorg.0.log) are uploaded here.

Thanks in advance for the help.
-Wes

Everything looks good, except for one thing.
You might try commenting out this line in the Device section:
I have an MX 4000 as well. I was looking in my Xorg.0.log and came across this line:
That is the only thing I see that could be a problem. It is probably not a good thing to ignore the EDID. I think you can damage the hardware that way.

I have tried without that line, and am still having troubles. If it helps, it's in a Dell Dimension 3000 with a Dell E193FP. (dunno if either of those could be the cause)

I have disabled the GLX driver and flux is loading now so it's got to be the GLX driver. Anyone have any ideas why??

Also having problems but of a different sort - driver loads ok but on killing x or switching to console i geta black screen full of green pixel blocks

Cant think why the GLX messes it up tho - from the readme:

Remove the following lines:

Load "dri"
Load "GLCore"

In the "Module" section of the file, add the line (if it does not already
exist):

Load "glx"

ftp://download.nvidia.com/XFree86/Li...667/README.txt

Does the glx affect gaming? (I would have thought thats its an OpenGL driver or module)

I fathom that glx affects gaming, and notably, I'm having the same problem on exiting X (even with glx disabled).

I cannot accurately state whether or not glx is gaming related, I just disabled glx as that's where signal 11 was happening. Out of curiousity, however, I am interested in seeing your /var/log/Xorg.0.log and /etc/X11/xorg.conf or whatever yours is, as I would like to try and compare and hopefully locate the problem (however, I know little).

-Wes

.::Edit::. I figured it worth noting that I also had this problem, initially, when loading X. When I looked at the logs when I had the problem loading, I noticed that it was throwing signal 11, and returning to console mode. When you get those green boxes, if you're confortable typing blindly, you can do a and enter your password, and your system will reboot safely and your display will come up properly again.

Ok, I've been pulling my hair out, so if anyone reads this, please help.

I found this.

Does anyone know where a similar option would be in slackware-current?

-Wes

They are talking about recompiling the kernel with no vesa support. If you have never done that before I would read thru the sticky at top of forum. It's not that hard but you will need to know the specifics of your hardware to start with. Try to set up your boot loader so you can boot back with our old kernel if things don't work out

Dive, I hope you get this, since the PM system is disabled for me.

I was screwing around lately, and have discovered how to stop the issue with the black screen filled with green blocks. I'm betting you're using a frame buffer console? That seems to be the problem on my system, and I hope it helps you out.


-Wes

I recompiled my kernel without GLX and it fixed this problem for me.

Thanks for the tip, man. Greatly appreciated. I'll start a modified kernel compiling now ;)

-Wes

Hope it helps.
Let me know if it works for you as well. I'm new to messing around with the kernel, and although I believe that disabling GLX was the only change I made that would affect the graphics, it would be good to confirm that it wasn't possibly something I tweaked somewhere else.

I have had brief contact with nVidia while submitting the bug report to them. I will forward this thread link to them, in hopes that they can better locate the issue. On a side note, can I get a copy of your .config for your kernel (if you're running kernel version 2.4.31) to try and compare it to the default slackware kernel options? (Should be located at /usr/src/linux-2.4.31/.config)

Anyways, hope it works :X

Thanks for your assistance thus far and have a GREAT day :)
-WEs

.::Edit::. Hmm...I don't see GLX in the kernel. Can you point out where it's at for me? :\

i never saw a "glx" option in the kernel config.
maybe you've got framebuffer support compiled in.
( only use " vesa " )

you don't need ' Load "glx" ' in your xorg.conf file.
maybe check that ( and "# comment " that)
same for "dri"

if still no luck, then check the file /var/log/Xorg.0.log
for warnings and errors.

egag

No, there wasn't, but I am finally getting around to compiling the kernel without vesa framebuffer support, hoping that'll solve the glx problem. And dri is commented out anyways, by default, and by the nvidia install directions. :)

I do need to load glx in the xorg file, AFAIK, as I wish to play games ;P

Xorg.0.log was posted up here, at the very beginning of the thread ;p (link). Seg 11 in glx. I'm able to load into X with it disabled, but I would love to play games ;p

Thanks again egag :)

-Wes

Did you check AGP settings ?
Have tried Option "NvAGP" "1" in xorg.conf ?
What does lsmod show about agp modules ?
Also, AGP motherboard chip could be found with
/sbin/lspci | grep -i agp

Sorry, I don't know if I mentioned this earlier, but my graphics card is PCI. I've got an onboard one that doesn't support games, so I had to go out and get one, and there is no AGP slot on my MB.

Recompiling the kernel without VESA Framebuffer support did not solve the problem, and I'm still slightly unsure what riemann_noodles might have changed to make it work. :\

Thanks for your continuing time

-Wes

Hi. Sorry it has taken me so long to respond. i did fix the pixel problem on my first recompile, but I also lost network connection. i tried to recompile again aand I totally blew the system. I've spent the last few days trying to get it back to where I was. I believe egag is right that there was no GLX option, but there was an option that affected whether or not it was used. Sorry I don't have any info right now- I'm totally new to this and I only halfway knew what I was doing n the first recompile. But I know that it can be fixed :) - I just wish I knew what I did. I will let you know as I retrace my steps what works and what doesn't.

I checked dell dimension 3000 and it has integrated intel extreme graphics video. In order to use other cards you'll have to disble the integrated video. This model has pci slots only, so you'll have to check to see if your card is compatible for this dell model.

riemann_noodles, your continual assistance is greatly appreciated, and I would love to know how it goes for you. As for your network going down, I had the same problem, and having to go back to work on a project and being 3 weeks behind -current, I just upgraded again to slackware-current and did a few changes so the new config files would work ;) (I think there was an inittab update or something like that in there).
Out of curiousity, does your MB have integrated video also?

north49er: As far as I know, the intel i820 (or i810--unsure) seems to be automatically disabling itself when it notices the nVidia card in a PCI slot. Are you suggesting that there is a bios setting I need to change? If so, then I shall look into it.

Have a GREAT day
-Wes

ncf: Yes, i've got integrated nForce2. I have fixed my network problem with a 2.6.12 kernel compile, which has an experimental reverse engineered forcedeth driver option- I disabled everything but that and just forgot about trying to install the drivers from nvidia.com since it's working now.

I have also fixed the green pixel problem again! though I'm still not exactly sure of the source. I'm learning how this all works as I go along.

When recompiling 2.6.12 under Device Drivers > Graphics Support I have included only:
Support for Frame Buffer Devices and selected only Vesa VGA Graphics Support.

This works, but the console is low-res, which is worth the trade off for now, as I don't have to reboot every time I exit X.


Before, when I was getting the green pixels, I had these included under Support for Frame Buffer Devices:

Enable Video Mode Handling Helpers
Enable Tile Blitting Support

under Console display driver support I had included:

Video mode selection support
Framebuffer Console support
Select compiled-in fonts
VGA 8x8 font
VGA 8x16 font

and everything included under Logo Configuration (although I dont believe this part matters)

Tomorrow I may try to reinclude some of these options and see which one causes the problem- but for now my eyes are about to bleed :p

Here is my present working .config:

Hope this helps!