| 1 |
On Mon, Jan 3, 2011 at 5:22 PM, Nikos Chantziaras <realnc@×××××.de> wrote: |
| 2 |
> On 01/03/2011 10:23 PM, Paul Hartman wrote: |
| 3 |
>> |
| 4 |
>> On Mon, Jan 3, 2011 at 2:07 PM, Nikos Chantziaras<realnc@×××××.de> wrote: |
| 5 |
>>> |
| 6 |
>>> uvesafb will not give you extra resolutions. It will however allow you |
| 7 |
>>> to |
| 8 |
>>> use non-default refresh-rates which is sometimes useful with CRT |
| 9 |
>>> monitors. |
| 10 |
>>> |
| 11 |
>>> But it has a drawback too: it needs a userspace tool and resolution is |
| 12 |
>>> switched too late during the boot process, meaning until it loads you'll |
| 13 |
>>> be |
| 14 |
>>> seeing the kernel boot in 80x25 mode (which in turn means no boot |
| 15 |
>>> graphics/logo right from the start.) |
| 16 |
>> |
| 17 |
>> I use uvesafb and I can see Tux (eight of him) during my boot process |
| 18 |
>> before uvesafb kicks in. |
| 19 |
> |
| 20 |
> I mean more something like this when I say "boot logo": |
| 21 |
> |
| 22 |
> http://mjanusz.files.wordpress.com/2008/02/shot.png |
| 23 |
> |
| 24 |
> It's at least 10 years since I saw that default Tux boot thingy :-P But |
| 25 |
> anyway, if uvesafb hasn't kicked in yet, what on earth is drawing that Tux? |
| 26 |
|
| 27 |
Ah-ha, I think that's bootsplash (which I'm not using). I've only |
| 28 |
seen it on a Live CD. :) |
| 29 |
|
| 30 |
In my kernel config I have enabled VESA framebuffer as well as |
| 31 |
userspace framebuffer (uvesafb), and I enabled "Bootup Logo". So maybe |
| 32 |
what happens is that VESA framebuffer starts immediately into some |
| 33 |
default resolution, I see eight Tuxs (Tuxes?), then shortly thereafter |
| 34 |
the uvesafb kicks in and video mode changes to the one I specified. At |
| 35 |
least that's how it seems to happen. I reboot so rarely that I never |
| 36 |
gave it much thought. |
Archives
