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