Am Montag, 9. August 2010 schrieb Tom H: > On Sun, Aug 8, 2010 at 5:14 PM, Frank Steinmetzger <Warp_7@gmx.de> wrote: > > On ye olde Gentoo I was a happy user of uvesafb at my laptop’s native > > resolution of 1400x1050. A while ago I installed Squeeze, and naturally, > > I would like it to also have a tiny console font. (The “Tiny Console > > Font” thread is what got me into investigating this issue again). :o) > > > > I’m attaching some relevant information. According to dmesg, uvesafb is > > loading, but fbset -i tells me that I’m running the normal VESA fb. I > > don’t mind really which one runs, as long as I can use my resolution. > > Setting the VESA mode via the kernel’s vga= parameter also wasn’t > > satisfactory. At my preferred mode 0x347 or 0x348, I got a 320x240 > > screen. The biggest mode I got running was with 1280 horizontal > > resolution. > If you are using grub2, try changing the values of > GRUB_GFXMODE > GRUB_GFXPAYLOAD_LINUX > in > /etc/default/grub > to your required resolution and run > update-grub Phew, I’ve been sitting at this for three hours now. And I finally have reached my goal. \o/ In essence: I’ve used Grub’s GFXMODE before, but it was too slow for my taste (2 seconds of black screen before the boot menu even appeared), so I went back to 640x480. For a test, I set it up again with GRUB_GFXMODE=1400x1050 GRUB_GFXPAYLOAD_LINUX=keep GRUB_TERMINAL_OUTPUT=gfxterm I now saw the boot messages at 1400x1050 right away. However, the colours were all wrong, everything was brighter and the hue was set off. I.e. white now was light green, red became purple and so on. fbset now said that the framebuffer was EFI VGA instead of VESA VGA. Then I found another line in dmesg, which I had overlooked before because the grep was too strict: uvesafb: scrolling: ypan using protected mode interface, yres_virtual=8192 Console: switching to colour frame buffer device 80x30 uvesafb: framebuffer at 0xc0000000, mapped to 0xf8000000, using 10240k, ... Note the “Console:” line which I was missing earlier. I researched that and found out about kernel mode setting. I guessed that this would cause the vesafb to load, thus blocking the framebuffer for uvesafb. So I added nomodeset to the kernel parameters. Unfortunately, this had no effect, it still switched text mode from 80x25 to 80x30. I can set the console resolution after login with a manual call to fbset. But not if I booted with a vga=x kernel parameter, fbset has no effect then. Next, I found a howto on uvesafb in the ubuntu forum. This said to append the uvesafb parameters also to the module entry in /etc/initramfs-tools/modules. I guess that was the small bit I was missing for a correct setup of uvesafb, because now it works, yay. All I’m missing now are the two penguin logos in the top-left corner. :-) -- Gruß | Greetings | Qapla' Programmers don’t die, they GOSUB without RETURN.
Attachment:
signature.asc
Description: This is a digitally signed message part.