On 2014-03-26 22:57 +0100, Viktor Malyarchuk wrote:
> On Sun, Mar 23, 2014 at 3:48 AM, Sven Joachim <svenjoac@gmx.de> wrote:
>
>> When the nouveau kernel module is loaded, any conflicting framebuffer
>> drivers are (supposed to be) removed. Check your dmesg if that is the
>> case for you.
> Conflicting framebuffer drivers are different. Here are relevant dmesg
> lines:
>
>
> a) CONFIG_X86_SYSFB=y (dmesg.3.13-1-amd64 and Xorg.0.log.3.13-1-amd64 in
> attachment)
> ---
> [ 10.591133] fb: conflicting fb hw usage nouveaufb vs simple - removing
> generic driver
> ...
> [ 10.983470] nouveau [ DRM] allocated 2560x1440 fb: 0x80000, bo
> ffff880265d15000
> [ 11.055551] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
> ---
>
> b) # CONFIG_X86_SYSFB is not set (dmesg.3.13.7+ and Xorg.0.log.3.13.7+ in
> attachment)
> ---
> [ 11.666121] fb: conflicting fb hw usage nouveaufb vs EFI VGA - removing
> generic driver
> ...
> [ 12.040732] nouveau [ DRM] allocated 2560x1440 fb: 0x80000, bo
> ffff880262dc8400
> [ 12.040790] fbcon: nouveaufb (fb0) is primary device
> [ 12.121273] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
> ---
That's how it is supposed to be in both cases, so we can rule that out.
Now why X fails in the first case but not in the second, I don't know.
I think you're best off reporting the bug upstream, please see
http://nouveau.freedesktop.org/wiki/Bugs/ for instructions.
> [ 10.800256] wl: module license 'MIXED/Proprietary' taints kernel.
You might want to disable the wl module temporarily, kernel developers
refuse to help when the kernel is tainted.
Cheers,
Sven