On Fri, 18 Jun 2010 00:25:24 -0400 (EDT), Sven Joachim wrote:
> On 2010-06-18 01:01 +0200, Stephen Powell wrote:
>>
>> The nouveau X driver now apparently works even if modeset=0 is specified
>> as a nouveau kernel module parameter.
>
> It does not, unless the module is loaded with modesetting enab
On 2010-06-18 01:01 +0200, Stephen Powell wrote:
> The nouveau X driver now apparently works even if modeset=0 is specified
> as a nouveau kernel module parameter.
It does not, unless the module is loaded with modesetting enabled
somehow. Maybe you got the vesa driver instead of nv.
> I also fo
On Thu, 17 Jun 2010 17:52:54 -0400 (EDT), Stephen Powell wrote:
>
> I experienced a similar problem on an older Nvidia card. If you want to
> get the old behavior back, create a file in /etc/modprobe.d with an extension
> of .conf. For example: /etc/modprobe.d/local.conf. Then turn off kernel
>
On Thu, Jun 17, 2010 at 14:11, Arthur Barlow wrote:
> I recently updated my kernel from 2.6.32-3 to 2.6.32-5, (Squeeze on an x86
> platform). I noticed on reboot that shortly after the kernel booted the
> screen switched to a frame buffer for the remaining loading messages. I
> have a desktop sy
On Thu, 17 Jun 2010 17:11:56 -0400 (EDT), Arthur Barlow wrote:
>
> I recently updated my kernel from 2.6.32-3 to 2.6.32-5, (Squeeze on an x86
> platform). I noticed on reboot that shortly after the kernel booted the
> screen switched to a frame buffer for the remaining loading messages. I
> have
I recently updated my kernel from 2.6.32-3 to 2.6.32-5, (Squeeze on an x86
platform). I noticed on reboot that shortly after the kernel booted the
screen switched to a frame buffer for the remaining loading messages. I
have a desktop system that runs GNOME and so gdm started as usual and I
logged
6 matches
Mail list logo
