I bought an Nvidia MX 4000 (10de:0185 (rev c1)), and am having problems with it.
If I remove xorg.conf and let the nvidia installer build a new one, I can run startx and X srarts up. I get a blue screen and the mouse works, but the keyboard does not. I can log in over SSH, and find that the system locks up for several seconds at a time, until the system locks up completely. At that point, a reset is necessary.
I see the same results with the livna RPM and the native installer from Nvidia.
I see the following in /var/log/messages:
-------------------------------------------------- Jun 13 15:38:33 charlesc kernel: NVRM: loading NVIDIA Linux x86 Kernel Module 1.0-8762 Mon May 15 13:06:38 PDT 2006 Jun 13 15:38:33 charlesc kernel: agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0. Jun 13 15:38:33 charlesc kernel: agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode Jun 13 15:38:33 charlesc kernel: agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode Jun 13 15:38:36 charlesc gconfd (ccurley-4027): starting (version 2.14.0), pid 4027 user 'ccurley' Jun 13 15:38:36 charlesc gconfd (ccurley-4027): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0 Jun 13 15:38:36 charlesc gconfd (ccurley-4027): Resolved address "xml:readwrite:/home/ccurley/.gconf" to a writable configuration source at position 1 Jun 13 15:38:36 charlesc gconfd (ccurley-4027): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2 Jun 13 15:38:39 charlesc gconfd (ccurley-4027): Resolved address "xml:readwrite:/home/ccurley/.gconf" to a writable configuration source at position 0 Jun 13 15:39:03 charlesc kernel: NVRM: Xid (0001:00): 8, Channel 0000001e Jun 13 15:39:47 charlesc last message repeated 3 times Jun 13 15:41:02 charlesc last message repeated 5 times Jun 13 15:42:17 charlesc last message repeated 5 times Jun 13 16:02:41 charlesc syslogd 1.4.1: restart. --------------------------------------------------
I see no errors or warnings in /var/log/Xorg.0.log
Ideas?
On 6/13/06, Charles Curley charlescurley@charlescurley.com wrote:
I bought an Nvidia MX 4000 (10de:0185 (rev c1)), and am having problems with it.
If I remove xorg.conf and let the nvidia installer build a new one, I can run startx and X srarts up. I get a blue screen and the mouse works, but the keyboard does not. I can log in over SSH, and find that the system locks up for several seconds at a time, until the system locks up completely. At that point, a reset is necessary.
I see the same results with the livna RPM and the native installer from Nvidia.
I see the following in /var/log/messages:
Jun 13 15:38:33 charlesc kernel: NVRM: loading NVIDIA Linux x86 Kernel Module 1.0-8762 Mon May 15 13:06:38 PDT 2006 Jun 13 15:38:33 charlesc kernel: agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0. Jun 13 15:38:33 charlesc kernel: agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode Jun 13 15:38:33 charlesc kernel: agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode Jun 13 15:38:36 charlesc gconfd (ccurley-4027): starting (version 2.14.0), pid 4027 user 'ccurley' Jun 13 15:38:36 charlesc gconfd (ccurley-4027): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0 Jun 13 15:38:36 charlesc gconfd (ccurley-4027): Resolved address "xml:readwrite:/home/ccurley/.gconf" to a writable configuration source at position 1 Jun 13 15:38:36 charlesc gconfd (ccurley-4027): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2 Jun 13 15:38:39 charlesc gconfd (ccurley-4027): Resolved address "xml:readwrite:/home/ccurley/.gconf" to a writable configuration source at position 0 Jun 13 15:39:03 charlesc kernel: NVRM: Xid (0001:00): 8, Channel 0000001e Jun 13 15:39:47 charlesc last message repeated 3 times Jun 13 15:41:02 charlesc last message repeated 5 times Jun 13 15:42:17 charlesc last message repeated 5 times Jun 13 16:02:41 charlesc syslogd 1.4.1: restart.
I see no errors or warnings in /var/log/Xorg.0.log
try booting with noapic and/or acpi=off verify you're using the latest BIOS set NvAGP=0 in xorg.conf
On Tue, Jun 13, 2006 at 03:50:48PM -0700, Lonni J Friedman wrote:
On 6/13/06, Charles Curley charlescurley@charlescurley.com wrote:
I bought an Nvidia MX 4000 (10de:0185 (rev c1)), and am having problems with it.
If I remove xorg.conf and let the nvidia installer build a new one, I
try booting with noapic and/or acpi=off
Tried it; no go.
verify you're using the latest BIOS
I've just upgraded to the latest non-beta BIOS. The MB is an ASUS A7V8X-X, and the latest BIOS is 1013, dated 9 September 2004.
set NvAGP=0 in xorg.conf
There was no xorg.conf. I had manually removed it. I just re-installed and made sure to rebuild xorg.conf. So I got an XF86Config instead of an xorg.conf. NBD.
Anyway, I added that line and NoLogo "0" to the device section. I get:
(==) Using config file: "/etc/X11/XF86Config" Parse error on line 57 of section Device in file /etc/X11/XF86Config "NvAGP" is not a valid keyword in this section. (EE) Problem parsing the config file (EE) Error parsing the config file
According to the README file, it is valid in both the device and screen sections, which I tried.
Charles Curley wrote:
On Tue, Jun 13, 2006 at 03:50:48PM -0700, Lonni J Friedman wrote:
On 6/13/06, Charles Curley charlescurley@charlescurley.com wrote:
I bought an Nvidia MX 4000 (10de:0185 (rev c1)), and am having problems with it.
If I remove xorg.conf and let the nvidia installer build a new one, I
try booting with noapic and/or acpi=off
Tried it; no go.
verify you're using the latest BIOS
I've just upgraded to the latest non-beta BIOS. The MB is an ASUS A7V8X-X, and the latest BIOS is 1013, dated 9 September 2004.
set NvAGP=0 in xorg.conf
There was no xorg.conf. I had manually removed it. I just re-installed and made sure to rebuild xorg.conf. So I got an XF86Config instead of an xorg.conf. NBD.
Anyway, I added that line and NoLogo "0" to the device section. I get:
(==) Using config file: "/etc/X11/XF86Config" Parse error on line 57 of section Device in file /etc/X11/XF86Config "NvAGP" is not a valid keyword in this section. (EE) Problem parsing the config file (EE) Error parsing the config file
According to the README file, it is valid in both the device and screen sections, which I tried.
Option "NvAgp" "0"
Belongs in Section "Screen". Is that where you have it?
On 6/13/06, Ed Greshko Ed.Greshko@greshko.com wrote:
Charles Curley wrote:
On Tue, Jun 13, 2006 at 03:50:48PM -0700, Lonni J Friedman wrote:
On 6/13/06, Charles Curley charlescurley@charlescurley.com wrote:
I bought an Nvidia MX 4000 (10de:0185 (rev c1)), and am having problems with it.
If I remove xorg.conf and let the nvidia installer build a new one, I
try booting with noapic and/or acpi=off
Tried it; no go.
verify you're using the latest BIOS
I've just upgraded to the latest non-beta BIOS. The MB is an ASUS A7V8X-X, and the latest BIOS is 1013, dated 9 September 2004.
set NvAGP=0 in xorg.conf
There was no xorg.conf. I had manually removed it. I just re-installed and made sure to rebuild xorg.conf. So I got an XF86Config instead of an xorg.conf. NBD.
Anyway, I added that line and NoLogo "0" to the device section. I get:
(==) Using config file: "/etc/X11/XF86Config" Parse error on line 57 of section Device in file /etc/X11/XF86Config "NvAGP" is not a valid keyword in this section. (EE) Problem parsing the config file (EE) Error parsing the config file
According to the README file, it is valid in both the device and screen sections, which I tried.
Option "NvAgp" "0"
Belongs in Section "Screen". Is that where you have it?
Actually, it will work in either the Screen section or Device section. Charles' problem was that he specified it as keyword instead of as an option.
Lonni J Friedman wrote:
Belongs in Section "Screen". Is that where you have it?
Actually, it will work in either the Screen section or Device section. Charles' problem was that he specified it as keyword instead of as an option.
Ah-Ha...so "keyword" was the "keyword". :-)
Thanks for the info on the "device section" ....
Ed Greshko wrote:
Lonni J Friedman wrote:
Belongs in Section "Screen". Is that where you have it?
Actually, it will work in either the Screen section or Device section. Charles' problem was that he specified it as keyword instead of as an option.
Ah-Ha...so "keyword" was the "keyword". :-)
I meant "keyword" was the "key word". Can't even get puns wright this morning.
On Wed, Jun 14, 2006 at 10:26:43AM +0800, Ed Greshko wrote:
Ed Greshko wrote:
Lonni J Friedman wrote:
Belongs in Section "Screen". Is that where you have it?
Actually, it will work in either the Screen section or Device section. Charles' problem was that he specified it as keyword instead of as an option.
Ah-Ha...so "keyword" was the "keyword". :-)
I meant "keyword" was the "key word". Can't even get puns wright this morning.
Right. I guess you're just not a punwright this morning.
On Tue, Jun 13, 2006 at 07:21:24PM -0700, Lonni J Friedman wrote:
On 6/13/06, Ed Greshko Ed.Greshko@greshko.com wrote:
Charles Curley wrote:
On Tue, Jun 13, 2006 at 03:50:48PM -0700, Lonni J Friedman wrote:
On 6/13/06, Charles Curley charlescurley@charlescurley.com wrote:
I bought an Nvidia MX 4000 (10de:0185 (rev c1)), and am having problems with it.
If I remove xorg.conf and let the nvidia installer build a new one, I
try booting with noapic and/or acpi=off
Tried it; no go.
verify you're using the latest BIOS
I've just upgraded to the latest non-beta BIOS. The MB is an ASUS A7V8X-X, and the latest BIOS is 1013, dated 9 September 2004.
set NvAGP=0 in xorg.conf
There was no xorg.conf. I had manually removed it. I just re-installed and made sure to rebuild xorg.conf. So I got an XF86Config instead of an xorg.conf. NBD.
Anyway, I added that line and NoLogo "0" to the device section. I get:
(==) Using config file: "/etc/X11/XF86Config" Parse error on line 57 of section Device in file /etc/X11/XF86Config "NvAGP" is not a valid keyword in this section. (EE) Problem parsing the config file (EE) Error parsing the config file
According to the README file, it is valid in both the device and screen sections, which I tried.
Option "NvAgp" "0"
Belongs in Section "Screen". Is that where you have it?
Actually, it will work in either the Screen section or Device section. Charles' problem was that he specified it as keyword instead of as an option.
Huh? Would you please try that in English?
That, plus looking at the config file, gave me a clue, and I tried an experiment. I had:
Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" NvAGP 0 NoLogo 0 DefaultDepth 24 SubSection "Display" Depth 24 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection
And that didn't work. I changed it to:
Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" Option "NvAGP" "0" Option "NoLogo" "0" DefaultDepth 24 SubSection "Display" Depth 24 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection
And that worked. Thank you.
It would be nice of Nvidia to document it or at least provide some examples. I had no reason to believe that the text in the README was to be taken literally; I assumed that "option foo bar" was a heading, not literal text. Grrrr.
Oh, since I got the logo on start, I assume that option should be "1", not "0". I'll try that next.
On 6/13/06, Charles Curley charlescurley@charlescurley.com wrote:
Huh? Would you please try that in English?
That, plus looking at the config file, gave me a clue, and I tried an experiment. I had:
Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" NvAGP 0 NoLogo 0 DefaultDepth 24 SubSection "Display" Depth 24 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection
And that didn't work. I changed it to:
Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" Option "NvAGP" "0" Option "NoLogo" "0" DefaultDepth 24 SubSection "Display" Depth 24 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection
And that worked. Thank you.
It would be nice of Nvidia to document it or at least provide some examples. I had no reason to believe that the text in the README was
In the NVIDIA driver README, I see:
Option "NvAGP" "integer"
I'm not sure how much more explicit it could be.
On Tue, Jun 13, 2006 at 09:31:26PM -0700, Lonni J Friedman wrote:
On 6/13/06, Charles Curley charlescurley@charlescurley.com wrote:
Huh? Would you please try that in English?
That, plus looking at the config file, gave me a clue, and I tried an experiment. I had:
Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" NvAGP 0 NoLogo 0 DefaultDepth 24 SubSection "Display" Depth 24 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection
And that didn't work. I changed it to:
Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" Option "NvAGP" "0" Option "NoLogo" "0" DefaultDepth 24 SubSection "Display" Depth 24 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection
And that worked. Thank you.
It would be nice of Nvidia to document it or at least provide some examples. I had no reason to believe that the text in the README was
In the NVIDIA driver README, I see:
Option "NvAGP" "integer"
I'm not sure how much more explicit it could be.
An example from a working file. A clear statement, like "Use the following form: 'Option "NvAGP" "0"'." A clear statement like "Use exactly this form, substituting an appropriate integer."
This is not the place to teach technical writing; it suffices to say that just because it is clear to you does not mean it is clear to anyone else.
Charles Curley wrote:
An example from a working file. A clear statement, like "Use the following form: 'Option "NvAGP" "0"'." A clear statement like "Use exactly this form, substituting an appropriate integer."
Yes, an example file from the Nvidia folks would have gone a long way. They probably assume (there's that dangerous word) that people doing this have experience in this area.
You may want to send a suggestion to that effect to them.
But, you know, don't be surprised if they don't act. They may be concerned that some people will take the examples, copy and paste them into their xorg.conf and expect them to work....causing other types of grief for them.
You know what they say...Damned if you do...Damned if you don't.
This is not the place to teach technical writing; it suffices to say that just because it is clear to you does not mean it is clear to anyone else.
Yep. That's why when someone tells me that I say.... Yes, I didn't know that...now I do. If I'm in a sarcastic mood I add..."Guess you've never found yourself in that situation, huh?"
On 6/14/06, Ed Greshko Ed.Greshko@greshko.com wrote:
Charles Curley wrote:
An example from a working file. A clear statement, like "Use the following form: 'Option "NvAGP" "0"'." A clear statement like "Use exactly this form, substituting an appropriate integer."
Yes, an example file from the Nvidia folks would have gone a long way. They probably assume (there's that dangerous word) that people doing this have experience in this area.
You may want to send a suggestion to that effect to them.
Well for those who are perplexed by manually configuring an xorg.conf, there's also the nvidia-xconfig utility which could have been used:
nvidia-xconfig --nvagp=0
Lonni J Friedman wrote:
On 6/14/06, Ed Greshko Ed.Greshko@greshko.com wrote:
Charles Curley wrote:
An example from a working file. A clear statement, like "Use the following form: 'Option "NvAGP" "0"'." A clear statement like "Use exactly this form, substituting an appropriate integer."
Yes, an example file from the Nvidia folks would have gone a long way. They probably assume (there's that dangerous word) that people doing this have experience in this area.
You may want to send a suggestion to that effect to them.
Well for those who are perplexed by manually configuring an xorg.conf, there's also the nvidia-xconfig utility which could have been used:
nvidia-xconfig --nvagp=0
Right.... Or even "man xorg.conf" and/or man nvidia-xconfig to learn the syntax/options of nvidia-xconfig.
I guess I wouldn't have used "perplexed"...."inexperienced" or "novice" seems more appropriate.
-
Charles Curley -
Ed Greshko -
Lonni J Friedman