NVIDIA driver causes kernel freeze

Steve Morris samorris at netspace.net.au
Thu Aug 26 01:36:27 UTC 2010

On 25/08/10 15:49, Ric Moore wrote:
> On Wed, 2010-08-25 at 15:36 +1000, Steve Morris wrote:
>> On 25/08/10 15:13, Ric Moore wrote:
>>> On Wed, 2010-08-25 at 10:44 +1000, Steve Morris wrote:
>>>> On 25/08/10 05:53, Thomas Olsen wrote: 
>>>>> On Tue, Aug 24, 2010 at 7:03 PM, Ric Moore <wayward4now at gmail.com>
>>>>> wrote:
>>>>>         On Tue, 2010-08-24 at 15:11 +0200, Thomas Olsen wrote:
>>>>>         > Actually I have no problems booting up with the nouveau
>>>>>         driver now
>>>>>         > except that it's so damn slow.
>>>>>         > After reading my mail again I can see that I wasn't being
>>>>>         quite clear.
>>>>>         > I'd like to see if the binary driver is faster but as it
>>>>>         freezes the
>>>>>         > kernel I wanted to ask if this was a known bug and if
>>>>>         there's a way to
>>>>>         > get around it.
>>>>>         I have several nvidia video cards on machines that are older
>>>>>         than yours.
>>>>>         Nary a hiccup in the barrel. It did take several tries with
>>>>>         the
>>>>>         "hardware drivers" app to finally get it to work though.
>>>>>         Nouveau is a
>>>>>         ways off to become a replacement for the stock nvidia
>>>>>         driver. I don't
>>>>>         have the xserver-xorg-video-nouveau package installed. I
>>>>>         think I ran
>>>>>         into a conflict with it early in my fresh install of Lucid.
>>>>>         Ric
>>>>> Well maybe I should try to purge xserver-xorg-video-nouveau and
>>>>> before I install the binary because kern.log looked like parts of
>>>>> nouveau was being loaded. Hmm. I'll give it a try tomorrow. Thanks.
>>>>> BTW: In xorg.conf do you user Driver "nvidia" or "nv"?
>>>> In xorg.conf to use the proprietary nvidia driver you  need     Driver
>>>> "nvidia", the "nv" driver is non-accelerated precursor to "nouveau".
>>>> The slowness you are experiencing is due to the nouveau driver not
>>>> using hardware acceleration which is also required for some
>>>> games/software. I am using the proprietary driver without any problems
>>>> but I had to start with an xorg.conf from another distribution as by
>>>> default Ubuntu does not use xorg.conf and installing the proprietary
>>>> driver in my case did not create one. I also found that using
>>>> nvidia-xconfig to create an xorg.conf did not work either.
>>>> I have attached the xorg.conf I am using under ubuntu for reference. 
>>> I had to use the "Nvidia Xserver settings" app that gets installed along
>>> with nvidia (look in systems in your applications launcher) to set my
>>> monitor (by autodetect) and write a new xorg.conf file. Once I did that,
>>> I'm back in business. 
>> For me that didn't work because it did not put the necessary modeset
>> statements into xorg.conf to enable proper resolution/refresh rates for
>> my monitor, so I had to start with an xorg.conf that I knew did work
>> correctly.
> I have a "plug n play" monitor that identifies itself and is detected by
> the nvidia setup thingie. Before I ran it, I had a sparse bare little
> xorg.conf file. After I ran it, it's now populated with the entries I
> used to have to make by hand. YMMV, Ric
My monitor is detected automatically and correctly by ubuntu, but the
monitor is internally optimised for 1280x1024 @ 60 Hz, but with the
xorg.conf the nvidia utility creates the drivers want to run the monitor
at 1280x1024 @ 50Hz which pushes the display off the left hand edge of
the monitor. Consequently I have to put the modeset statements in by
hand to get things to run properly.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: samorris.vcf
Type: text/x-vcard
Size: 126 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/kubuntu-users/attachments/20100826/4dd7241b/attachment.vcf>

More information about the kubuntu-users mailing list