On 07/05/10 15:46, Jake Moe wrote: > I've recently installed a new system, and can't seem to get UVESAFB > working properly. I've set up everything in the kernel, and modified > GRUB's menu.lst to use the framebuffer. However, even though there > doesn't seem to be any errors, I can't seem to get anything other than > "default" resolution with far too large fonts. > > I've compared dmesg info, GRUB configs and kernel configs between this > laptop, and another laptop that has UVESAFB running fine, and am at a > loss to find what's wrong. > > The laptop in question is a HP EliteBook 8440p with an nVidia graphics chip. > > Relevant info that I can think of: > > > -----***** lspci *****----- > <snip> > > > -----***** dmesg | grep uvesafb *****----- > Kernel command line: root=/dev/sda4 video=uvesafb:mtrr:3,ywrap,1600x900 > uvesafb: NVIDIA Corporation, NVIDIA Quadro NVS 170M > uvesafb: protected mode interface info at c000:c2d0 > uvesafb: pmi: set display start = c00cc333, set palette = c00cc38e > uvesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc > 3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da > uvesafb: VBIOS/hardware doesn't support DDC transfers > uvesafb: no monitor limits have been set, default refresh rate will be used > uvesafb: scrolling: ywrap using protected mode interface, yres_virtual=7200 > uvesafb: framebuffer at 0xd1000000, mapped to 0xf8080000, using 11250k, > total 14336k > > > -----***** /sys/devices/platform/uvesafb.0/graphics/fb0/modes *****----- > U:1600x900p-59 > <snip> > U:1600x900p-59 > <snip> > > I've also attached my kernel .config file for reference. If you need > anything further, please let me know. I'm sure I've overlooked > something obvious here; usually getting the framebuffer set up isn't > this hard; but for some reason, I can't figure this one out. While this > isn't a big deal, since usually the first thing I do after login is > "startx", it's an annoyance that I'd like cleared up; it *should* work, > dammit! :-P > > Jake Moe > This may be a bit of a long shot, but: according to the modes file you included, your monitor only actually supports 1600x900 at 59 Hz. Since you aren't specifying a refresh, uvesafb says in dmesg that it is using a default refresh. My guess is that means "60", rather than some smart value. Does anything different happen if you specify the full mode, e.g. 1600x900...@59?
I'm afraid if that doesn't help I'm not likely to be much good myself. But I thought seeing that 59 there was odd, and figure it might be worth a look. -Andy
