On Tue, Mar 25, 2008 at 4:42 PM, Sergey Kobzar <tod.zullu@gmail.com> wrote:

uvesafb works nice.
Can anyone help me with the following?
Do any of you know how to make uvesafb (that replaces the old vesafb-tng) set to a pre-defined resolution?

What I mean is that with vesafb-tng I used to set like: "1440x900@60"
as fb settings and then, during boot, while kernel was loading, when it
passed through that "instruction", it would start using the console
with those fb settings and the penguins on the top. Then the penguins
disappear and I had a great text console @ 1440x900.

I remeber putting the exact string 1440x900@60 when building my kernel on the vesafb page. Now with uvesafb I don't get that option and my text console has a horrible resolution. A simple "lspci" will generate text long enough for a line to break.

Anyone?
Regards,

Saffi

--
Ricardo Saffi Marques
Laboratório de Administração e Segurança de Sistemas (LAS/IC)
Universidade Estadual de Campinas (UNICAMP)
Cell: +55 (19) 8128-0435

Skype: ricardo_saffi_marques
Website: http://www.rsaffi.com

Hi.

Try to determine possible resolutions by typing "hwinfo --framebuffer". Use the
hex code 0x... and put it as kernel parameter in your grub.conf.


For 1400x1050 with kernel 2.6.24-r3 I am using the following lines:

title Gentoo GNU/Linux (gentoo-sources-2.6.24-r3)
root (hd0,1)
kernel /gentoo-sources-2.6.24-r3 root=/dev/sda5 vga=0x344


Regards,

acm.

2008/3/25, Alexander Meinke <ameinke@online.de>:

Are you guys using* uvesafb in the latest gentoo sources kernel? because i dont have the option to choose this one..i am using vesa

Ale wrote:

2008/3/25, Alexander Meinke <ameinke@online.de <mailto:ameinke@online.de>>:
*
*

Are you guys using uvesafb in the latest gentoo sources kernel? because
i dont have the option to choose this one..i am using vesa


Yes I am using gentoo-sources. I think since kernel 2.6.23 (or maybe 2.6.24)
there is only uvesafb - nothing else to choose. uvesafb replaced vesafb-tng.



Greets,

acm.

On Tue, Mar 25, 2008 at 5:37 PM, Alexander Meinke <ameinke@online.de> wrote:

Try to determine possible resolutions by typing "hwinfo --framebuffer". Use the

hex code 0x... and put it as kernel parameter in your grub.conf.
Okay, *that* I didn't know. :-)
I do know 1440x900 is a supported resolution on my machines since it's the native resolution of their screen's.

*For 1400x1050 with kernel 2.6.24-r3 I am using the following lines:

title Gentoo GNU/Linux (gentoo-sources-2.6.24-r3)

root (hd0,1)

kernel /gentoo-sources-2.6.24-r3 root=/dev/sda5 vga=0x344
So after the change from the vesafb-tng to the actual uvesafb on the kernel, it actually IS necessary to use the "vga=something" trick on the boot line, then?

I'll do it and tell the results.

Thanks a lot, Alexander!

Best regards,

Saffi
--
Ricardo Saffi Marques
Laboratório de Administração e Segurança de Sistemas (LAS/IC)
Universidade Estadual de Campinas (UNICAMP)

Cell: +55 (19) 8128-0435
Skype: ricardo_saffi_marques
Website: http://www.rsaffi.com

Ricardo Saffi Marques wrote:
On Tue, Mar 25, 2008 at 5:37 PM, Alexander Meinke <ameinke@online.de
<mailto:ameinke@online.de>> wrote:


Try to determine possible resolutions by typing "hwinfo
--framebuffer". Use the
hex code 0x... and put it as kernel parameter in your grub.conf.


Okay, *that* I didn't know. :-)
I do know 1440x900 is a supported resolution on my machines since it's
the native resolution of their screen's.



For 1400x1050 with kernel 2.6.24-r3 I am using the following lines:
title Gentoo GNU/Linux (gentoo-sources-2.6.24-r3)
root (hd0,1)
kernel /gentoo-sources-2.6.24-r3 root=/dev/sda5 vga=0x344


So after the change from the vesafb-tng to the actual uvesafb on the
kernel, it actually IS necessary to use the "vga=something" trick on the
boot line, then?

I'll do it and tell the results.

Thanks a lot, Alexander!

Best regards,

Saffi

--
Ricardo Saffi Marques
Laboratório de Administração e Segurança de Sistemas (LAS/IC)
Universidade Estadual de Campinas (UNICAMP)
Cell: +55 (19) 8128-0435
Skype: ricardo_saffi_marques
Website: http://www.rsaffi.


i always thought vga= was only used by the old vesafb driver
i use video=uvesafb:1024x768-32
i cant get any wide screen modes to work at all, anybody else know how??
--
gentoo-user@lists.gentoo.org mailing list

On Tue, Mar 25, 2008 at 7:53 PM, Ian Lee <ian@leehouse.eclipse.co.uk> wrote:

i always thought vga= was only used by the old vesafb driver

i use video=uvesafb:1024x768-32

i cant get any wide screen modes to work at all, anybody else know how??
Nice, new thoughts being added to the discussion. That's good!! Let's keep the brainstorm. :-)
Any ideas?


--
Ricardo Saffi Marques
Laboratório de Administração e Segurança de Sistemas (LAS/IC)
Universidade Estadual de Campinas (UNICAMP)
Cell: +55 (19) 8128-0435
Skype: ricardo_saffi_marques
Website: http://www.rsaffi.com

On Wed, Mar 26, 2008 at 3:55 AM, Ricardo Saffi Marques
<saffi@las.ic.unicamp.br> wrote:
> On Tue, Mar 25, 2008 at 4:42 PM, Sergey Kobzar <tod.zullu@gmail.com> wrote:
>
> > uvesafb works nice.
>
> Can anyone help me with the following?
> Do any of you know how to make uvesafb (that replaces the old vesafb-tng)
> set to a pre-defined resolution?
May be you want this guide http://dev.gentoo.org/~spock/projects/uvesafb/



--
wcw
--
gentoo-user@lists.gentoo.org mailing list

Ian Lee wrote:

i always thought vga= was only used by the old vesafb driver
i use video=uvesafb:1024x768-32
i cant get any wide screen modes to work at all, anybody else know how??


Did you tried to find out what resolutions are supported by your graphic card
(e.g. hwinfo --framebuffer)? I only know this tool to get the necessary hex code.

So I don't really know if the vga= option works with uvesafb too.
I have to correct my statement that I am using uvesafb. It seems that I am using
vesafb. This is because I don't want either any additional userspace application
(v86d) nor bootsplash etc.



acm.

On Tuesday 25 March 2008 20:42:47 Ale wrote:

> Are you guys using uvesafb in the latest gentoo sources kernel? because
> i dont have the option to choose this one..i am using vesa

You have to select Connector - unified userspace <-> kernelspace linker in
the Device Drivers page. Then you will have uvesafb available for
selection.

It seems that you also need v86d installed, and start with an initramfs with
that in it, though I haven't yet finished working this out for myself.

--
Rgds
Peter
--
gentoo-user@lists.gentoo.org mailing list