| 1 |
Nikos Chantziaras <realnc@×××××.de> writes: |
| 2 |
|
| 3 |
> reader@×××××××.com wrote: |
| 4 |
>> Paul Hartman <paul.hartman+gentoo@×××××.com> writes: |
| 5 |
>> |
| 6 |
>>> I'm ashamed to admit I made the most basic mistake. I compiled uvesafb |
| 7 |
>>> as a module. Oops! Compiled it as "Y" instead of "M" and now I have a |
| 8 |
>>> pair of Tux sitting atop my kernel boot screen and no more 80x25 |
| 9 |
>>> horror. :) |
| 10 |
>> |
| 11 |
>> Is there some difference in uvesafb and vesafb? I've always just ignored |
| 12 |
>> the uvesafb choice and used plain vesafb. |
| 13 |
>> |
| 14 |
>> I just assumed from the name of it and the menuconfig help on it that |
| 15 |
>> it was something only usable in `userspace'. I took that to mean |
| 16 |
>> after bootup.. something you'd do from the command line. |
| 17 |
>> |
| 18 |
>> Anyone here that can explain what the difference is. |
| 19 |
> |
| 20 |
> uvesafb also works on non-x86 system. It has one drawback though: it |
| 21 |
> doesn't switch to graphical mode right from the start like vesafb |
| 22 |
> does. Instead, you get the initial kernel messages in text mode and |
| 23 |
> need to wait for graphics to kick-in. With vesafb, you're in graphics |
| 24 |
> mode right from the start. That pretty much makes uvesafb a poor |
| 25 |
> choice for bootsplash configurations. |
| 26 |
|
| 27 |
If you select both will that lead to problems? |
| 28 |
Could you invoke uvesafb from console session one you've booted? |
Archives