| 1 |
On Fri, Jan 16, 2009 at 12:33 PM, <reader@×××××××.com> wrote: |
| 2 |
> Paul Hartman <paul.hartman+gentoo@×××××.com> writes: |
| 3 |
> |
| 4 |
>> I'm ashamed to admit I made the most basic mistake. I compiled uvesafb |
| 5 |
>> as a module. Oops! Compiled it as "Y" instead of "M" and now I have a |
| 6 |
>> pair of Tux sitting atop my kernel boot screen and no more 80x25 |
| 7 |
>> horror. :) |
| 8 |
> |
| 9 |
> Is there some difference in uvesafb and vesafb? I've always just ignored |
| 10 |
> the uvesafb choice and used plain vesafb. |
| 11 |
> |
| 12 |
> I just assumed from the name of it and the menuconfig help on it that |
| 13 |
> it was something only usable in `userspace'. I took that to mean |
| 14 |
> after bootup.. something you'd do from the command line. |
| 15 |
> |
| 16 |
> Anyone here that can explain what the difference is. |
| 17 |
|
| 18 |
According to the website: |
| 19 |
|
| 20 |
uvesafb is a generic framebuffer driver for Linux systems and the |
| 21 |
direct successor of vesafb-tng. Its main features are: |
| 22 |
|
| 23 |
* works on non-x86 systems, |
| 24 |
* the Video BIOS code is run in userspace by a helper application, |
| 25 |
* can be compiled as a module, |
| 26 |
* adjustable refresh rates with VBE 3.0-compliant graphic cards. |
| 27 |
|
| 28 |
It also enumerates all of the supported modes when you cat |
| 29 |
/sys/class/graphics/fb0/modes which is handy... no need for vga=0x382 |
| 30 |
or whatever. They are nice human-readable modes lik 1024x768-60 or |
| 31 |
whatever. |
| 32 |
|
| 33 |
You can also disable the framebuffer entirely or change modes from the |
| 34 |
commandline once the system is up and running (maybe vesafb lets you |
| 35 |
do that too, I'm not sure). |
| 36 |
|
| 37 |
Now I just need to find a good consolefont that doesn't look |
| 38 |
"squished" in 16:9 aspect ratio. Right now I'm using ter-112n (from |
| 39 |
terminus-fonts) and it's pretty good but still a little too wide for |
| 40 |
my taste. |
| 41 |
|
| 42 |
Paul |
Archives