Re: [gentoo-user] Weird framebuffer problem when booting

[Alan McKinnon]

On 28/04/2013 19:15, Tanstaafl wrote:
> In my defense though, the example immediately following that comment did
> NOT have the '0x' preceding the value, and it was the example I was
> going by...

I remember that from a LONG time ago too.
You are not the only one who got caught out...



>
> On 2013-04-28 1:13 PM, Tanstaafl <tanstaafl@×××××××××××.org> wrote:
>> On 2013-04-28 12:51 PM, Alan McKinnon <alan.mckinnon@×××××.com> wrote:
>>> IIRC (this goes back a long while), the vesafb and vga= options are
>>> completely unrelated and refer to *different* framebuffer systems. So
>>> vesafb ignores vga= and defaults to ... default :-)
>>
>> Not according to the gentoo wiki:
>>
>> http://en.gentoo-wiki.com/wiki/Framebuffer#vesafb_2
>>
>>> Put the vesafb: option on the kernel command line instead.
>>
>> I am putting it on the kernel command line:
>>
>> title Gentoo Linux 3.7.10-r1-curr
>> root (hd0,0)
>> kernel /boot/kernel-3.7.10-gentoo-r1-curr root=/dev/sda3
>> video=vesafb:mtrr:y,ywrap vga=ask
>>
>> But, after re-reading that page above for the 10th time, I finally
>> noticed this comment:
>>
>>> Setting vga=ask is a good idea if you are unsure what to use, as the
>>> kernel will stop and ask you for the desired resolution and color
>>> depth. The displayed mode numbers are in HEX format - use the
>>> preceding 0x when updating your grub.conf with the new video mode.
>>
>> I was just adding the number '341'... after adding vga=0x341, it works
>> just fine.
>>
>> Wasted a few hours on that one. Gotta start paying more attention to
>> detail...
>>
>
>


-- 
Alan McKinnon
alan.mckinnon@×××××.com