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