Can't Use the Generic nv Driver with Current?

Woodsman · 08-16-2009, 03:48 PM

Does the generic nv video driver included with Current/13.0 support the NVidia MCP78S chip set? This chip set is on my M3N78-EM motherboard. The chip set provides the GeForce 8300 video controller.

The generic nv driver works with my M2NPV-VM motherboard, which uses the MCP51 chip set (GeForce 6150 video controller). The man page does not specifically list the MCP51 chip set, although there is a C51 listed. Possibly a typo? Regardless, the nv man page does not list the MCP78S chip set or 8300 specifically.

When using no xorg.conf in a stock 13.0/Current install I cannot start X. With an xorg.conf I can start X in the stock 13.0/current but only with the vesa driver.

I compiled and installed the latest (185.18.31) proprietary drivers, which then requires an xorg.conf, but I like having the generic nv driver as a backup and troubleshooting tool.

windtalker10 · 08-16-2009, 04:22 PM

I can't find nvidia listed in current anywhere myself but Googling tells me the NVidia MCP78S is a GeForce 8200 instead of 8300.
I also wasn't aware it was possible to have two Nvidia drivers installed at the same time.
They have always conflicted for me in the past.

Woodsman · 08-16-2009, 05:08 PM

Quote:

but Googling tells me the NVidia MCP78S is a GeForce 8200 instead of 8300.

True but the video controller is 8300. At least that is what lspci reports.

Quote:

I also wasn't aware it was possible to have two Nvidia drivers installed at the same time.

I don't run both at the same time. I create two xorg.conf files and use the xorg-switch script from slackbuilds to quickly toggle between the two.

ppr:kut · 08-17-2009, 03:43 AM

I had the same issue with my QuadroFX 770M. The id wasn't supported by nv, but a recent update fixed that. Looking at nv-driver.c reveals it supports the 8300 GS, but not a 8200 yet.

Woodsman · 08-17-2009, 10:54 AM

Quote:

Looking at nv-driver.c reveals it supports the 8300 GS, but not a 8200 yet.

So the short answer is "no."

Well that sucks.

cwwilson721 · 08-17-2009, 01:26 PM

Yea, you're kind of stuck in the void, there...

The open driver doesn't really support it...And the closed Nvidia is...Well, closed.

Personally, I'd take the closed one until the nv driver gets more mature/more supported cards/chips. Then use nv.

My 2cents...

Woodsman · 08-17-2009, 02:28 PM

Quote:

Personally, I'd take the closed one until the nv driver gets more mature/more supported cards/chips. Then use nv.

Yes, I am using the proprietary package.

I like have a backup choice for troubleshooting. The generic vesa driver seems to support only 1280x1024 and my monitor is 1680x1050 --- quite a discrepancy. I would not mind as much if the vesa driver supported the full resolution. Perhaps this is a PEBKAC issue, but I haven't yet figured out how to force the vesa driver to full resolution. Thus, seems I'm stuck with a distorted screen or only using the proprietary drivers.