[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: nouveau



On Wed, 2010-03-31 at 10:36 +0200, Cyril Brulebois wrote: 
> 
> Will Set <debiandunes@yahoo.com> (31/03/2010):
> > xserver-xorg-video-nouveau_0.0.15+git20100219+9b4118d-1_i386.deb
> > 
> > dmesg | grep -E "onsole|fb|agp|drm"
> > [    0.000000] Console: colour dummy device 80x25
> > [    0.000000] console [tty0] enabled
> > [    0.535761] vesafb: framebuffer at 0xf0000000, mapped to 0xf7c80000, using 6144k, total 32704k
> > [    0.535769] vesafb: mode is 1024x768x32, linelength=4096, pages=0
> > [    0.535774] vesafb: protected mode interface info at c000:0944
> > [    0.535779] vesafb: pmi: set display start = c00c097d, set palette = c00c09f3
> > [    0.535783] vesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da 
> > [    0.535810] vesafb: scrolling: redraw
> > [    0.535815] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
> 
> it'd be nice if you could try and get rid of this vesafb thingy, I
> assume you're loading this from the kernel commandline? See below, it
> looks like it's conflicting with nouveau at some point.
> 
> It'd also be nice to know which kernel version you're running. IOW,
> please paste full dmesg.
> 
> > [  457.021371] fb: conflicting fb hw usage nouveaufb vs VESA VGA - removing generic driver
> 
> ^^^^ that probably doesn't help.

Should be fine, it's the KMS handover mechanism in action.


> > [  457.316471] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
> 
> That could be a consequence.

I don't think so, could be the X driver is doing something wrong.


If there's a problem, I missed its description in Will's post.


-- 
Earthling Michel Dänzer           |                http://www.vmware.com
Libre software enthusiast         |          Debian, X and DRI developer


Reply to: