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

Re: display limited to 1/4 of monitor after upgrade to sid, 2.6.32, grub 2

On 2010-06-04 15:22 +0200, Kent West wrote:

> On 06/03/2010 04:10 PM, Sven Joachim wrote:
>> On 2010-06-03 22:49 +0200, Kent West wrote:
>>> When I boot 2.6.32 using grub2, my display is only in the top left
>>> quadrant of my monitor, leaving a huge unusable border around the
>>> right and bottom of my viewable area, and leaving my viewable area too
>>> small to be very usable. It's like the resolution is locked at
>>> something small, like 320x180, and pushed into the upper left corner
>>> of the monitor. (xdpyinfo within X reports:
>>> screen #0:
>>>    dimensions:    720x576 pixels (191x152 millimeters)
>>>    resolution:    96x96 dots per inch
>>>    depths (7):    24, 1, 4, 8, 15, 16, 32
>>> (but this problem does not only affect X, which I'm starting manually
>>> with "startx"; it begins in the console mode just after the grub menu
>>> and about 20-30 seconds of black screen, with a text image finally
>>> appearing mid-boot.
>> This happens when udev starts and loads the nouveau module, switching to
>> graphics mode.  Text mode appears to be b0rked with your card/monitor.
>>> [    6.338804] [drm] nouveau 0000:04:06.0: allocated 1280x1024 fb: 0x49000, bo efa1a000
>> This looks normal, I get something similar.
>>> [    6.486533] Console: switching to colour frame buffer device 90x36
>> But this is bad, it should have been 160x64.  The 90x36 match the
>> xdpyinfo output, though.
> What do these numbers (90x36 & 160x64) mean, and how do you see those
> in the snippet of xdpyinfo's output that I included above?

They mean columns * rows, and the default font has a size of 8x16, so
90*8 = 720 and 36*16 = 576 (see the dimensions line in xdpyinfo).

> And, is there anyway I can tell udev to override that setting so that
> I could maybe have a usable display?

Not that I know of.  The "video=…" parameter does not work for you, and
I don't know any other.

You should report a bug at https://bugs.freedesktop.org/.  Choose
product xorg and component Driver/nouveau.


Reply to: