[gentoo-user] SVGA mode & the console

[gentoo-user] SVGA mode & the console

[meino.cramer]

Hi,

there is a "small" linux distribution (GRML), which I use for rescue
and other purposes. I installed it on a USB-stick.

Furthermore installed in my PC there is a MSI GT430 (nvidia) graphics
card and I use the nvidia-driver in conjunction with xorg 1.9.2.

So far so nice...

The GRML uses the noveau driver as far as I know.

When I boot from my USB-stick I get a very nice high resolution
linux console. It uses vga=791 on the kernel commandline.

When I use the same option with my kernel (2.6.36.2 vanilla) it
ends in a console font/resolution which reminds me at the good
old times when 8bit homecomputers were the dream of many people
and PACMAN was top! ;)

I tried "vga=asK" and then "scan" but the highest resolution I was
offered were 80x60 and only VGA-modes, which again looks like the
"high resolution textmode" of my old ATARI 800...and not like that
nice looking console which I get with the same hardware and the GRML
distro.

I compared both the kernel config of the GRML distro and my
own but I didn't found nay suspicious (or overlooked something?).


Final question after all there words: How can I get such a high
resolution with this hardware and the nvidia-drivers???

Best regards and a happy new 2011!
mcc

Re: [gentoo-user] SVGA mode & the console

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2258 bytes --]

On Sunday 02 January 2011 11:28:09 meino.cramer@gmx.de wrote:
> Hi,
> 
> there is a "small" linux distribution (GRML), which I use for rescue
> and other purposes. I installed it on a USB-stick.
> 
> Furthermore installed in my PC there is a MSI GT430 (nvidia) graphics
> card and I use the nvidia-driver in conjunction with xorg 1.9.2.
> 
> So far so nice...
> 
> The GRML uses the noveau driver as far as I know.
> 
> When I boot from my USB-stick I get a very nice high resolution
> linux console. It uses vga=791 on the kernel commandline.
> 
> When I use the same option with my kernel (2.6.36.2 vanilla) it
> ends in a console font/resolution which reminds me at the good
> old times when 8bit homecomputers were the dream of many people
> and PACMAN was top! ;)
> 
> I tried "vga=asK" and then "scan" but the highest resolution I was
> offered were 80x60 and only VGA-modes, which again looks like the
> "high resolution textmode" of my old ATARI 800...and not like that
> nice looking console which I get with the same hardware and the GRML
> distro.
> 
> I compared both the kernel config of the GRML distro and my
> own but I didn't found nay suspicious (or overlooked something?).
> 
> 
> Final question after all there words: How can I get such a high
> resolution with this hardware and the nvidia-drivers???

I think that the "nice high resolution" you see with GRML is presented by the 
framebuffer.  You only get this once the kernel starts to load.  Until then 
you get a very basic VGA screen, which the GRML may not show at all (in other 
words the first visual impression of a LiveCD may be the framebuffer console).

With the latest versions CDs which use KMS (e.g. SystemrescueCD) the two 
stages VGA-->framebuffer are visible if I recall correctly.

With regards to your own kernel, are you using KMS?  If so, once the kernel 
starts loading the KMS will dictate what resolution you get.  If this is too 
small to read (I think it will render the highest resolution possible) or you 
want to set some custom resolution for whatever reason, then add nomodeset to 
the kernel line in your grub.conf and also restore the vga=XXX line you had 
there previously.

HTH.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[gentoo-user] Re: SVGA mode & the console

[Nikos Chantziaras]

On 01/02/2011 01:28 PM, meino.cramer@gmx.de wrote:
> Hi,
>
> there is a "small" linux distribution (GRML), which I use for rescue
> and other purposes. I installed it on a USB-stick.
>
> Furthermore installed in my PC there is a MSI GT430 (nvidia) graphics
> card and I use the nvidia-driver in conjunction with xorg 1.9.2.
>
> So far so nice...
>
> The GRML uses the noveau driver as far as I know.
>
> When I boot from my USB-stick I get a very nice high resolution
> linux console. It uses vga=791 on the kernel commandline.

Nouveau uses KMS, which means it automatically uses the monitor's native 
resolution and supports all resolutions the graphics card is capable of.

On your PC, you're using the VESA fb driver, not Nouveau KMS.  That 
means you're limited to VESA resolutions for your consoles.  You can use 
the "vbetest" utility to detect which modes your card's VESA BIOS 
supports.  To use this tool, emerge the "sys-libs/lrmi" package.  Simply 
run the tool and it will print a list of modes you can use, and the 
resolutions those modes correspond to.

If your desired resolution is not in the list, then there's no way to 
use that resolution in a VESA fb; you will need to switch to Nouveau's 
KMS fb.

Re: [gentoo-user] SVGA mode & the console

[meino.cramer]

Mick <michaelkintzios@gmail.com> [11-01-02 14:08]:
> On Sunday 02 January 2011 11:28:09 meino.cramer@gmx.de wrote:
> > Hi,
> > 
> > there is a "small" linux distribution (GRML), which I use for rescue
> > and other purposes. I installed it on a USB-stick.
> > 
> > Furthermore installed in my PC there is a MSI GT430 (nvidia) graphics
> > card and I use the nvidia-driver in conjunction with xorg 1.9.2.
> > 
> > So far so nice...
> > 
> > The GRML uses the noveau driver as far as I know.
> > 
> > When I boot from my USB-stick I get a very nice high resolution
> > linux console. It uses vga=791 on the kernel commandline.
> > 
> > When I use the same option with my kernel (2.6.36.2 vanilla) it
> > ends in a console font/resolution which reminds me at the good
> > old times when 8bit homecomputers were the dream of many people
> > and PACMAN was top! ;)
> > 
> > I tried "vga=asK" and then "scan" but the highest resolution I was
> > offered were 80x60 and only VGA-modes, which again looks like the
> > "high resolution textmode" of my old ATARI 800...and not like that
> > nice looking console which I get with the same hardware and the GRML
> > distro.
> > 
> > I compared both the kernel config of the GRML distro and my
> > own but I didn't found nay suspicious (or overlooked something?).
> > 
> > 
> > Final question after all there words: How can I get such a high
> > resolution with this hardware and the nvidia-drivers???
> 
> I think that the "nice high resolution" you see with GRML is presented by the 
> framebuffer.  You only get this once the kernel starts to load.  Until then 
> you get a very basic VGA screen, which the GRML may not show at all (in other 
> words the first visual impression of a LiveCD may be the framebuffer console).
> 
> With the latest versions CDs which use KMS (e.g. SystemrescueCD) the two 
> stages VGA-->framebuffer are visible if I recall correctly.
> 
> With regards to your own kernel, are you using KMS?  If so, once the kernel 
> starts loading the KMS will dictate what resolution you get.  If this is too 
> small to read (I think it will render the highest resolution possible) or you 
> want to set some custom resolution for whatever reason, then add nomodeset to 
> the kernel line in your grub.conf and also restore the vga=XXX line you had 
> there previously.
> 
> HTH.
> -- 
> Regards,
> Mick



Hi Mick,

unfortunately the nvidia driver does not support KMS...see the Gentoo
docs.

Best regards,
mcc

Re: [gentoo-user] Re: SVGA mode & the console

[meino.cramer]

Nikos Chantziaras <realnc@arcor.de> [11-01-02 14:12]:
> On 01/02/2011 01:28 PM, meino.cramer@gmx.de wrote:
> >Hi,
> >
> >there is a "small" linux distribution (GRML), which I use for rescue
> >and other purposes. I installed it on a USB-stick.
> >
> >Furthermore installed in my PC there is a MSI GT430 (nvidia) graphics
> >card and I use the nvidia-driver in conjunction with xorg 1.9.2.
> >
> >So far so nice...
> >
> >The GRML uses the noveau driver as far as I know.
> >
> >When I boot from my USB-stick I get a very nice high resolution
> >linux console. It uses vga=791 on the kernel commandline.
> 
> Nouveau uses KMS, which means it automatically uses the monitor's 
> native resolution and supports all resolutions the graphics card is 
> capable of.
> 
> On your PC, you're using the VESA fb driver, not Nouveau KMS.  That 
> means you're limited to VESA resolutions for your consoles.  You can 
> use the "vbetest" utility to detect which modes your card's VESA BIOS 
> supports.  To use this tool, emerge the "sys-libs/lrmi" package.  
> Simply run the tool and it will print a list of modes you can use, and 
> the resolutions those modes correspond to.
> 
> If your desired resolution is not in the list, then there's no way to 
> use that resolution in a VESA fb; you will need to switch to Nouveau's 
> KMS fb.
> 
> 

Hi Nikos,

unfortunately lrmi fails to compile.

Best regards,
mcc

[gentoo-user] Re: SVGA mode & the console

[Nikos Chantziaras]

On 01/02/2011 03:57 PM, meino.cramer@gmx.de wrote:
> Nikos Chantziaras<realnc@arcor.de>  [11-01-02 14:12]:
>> On 01/02/2011 01:28 PM, meino.cramer@gmx.de wrote:
>>> Hi,
>>>
>>> there is a "small" linux distribution (GRML), which I use for rescue
>>> and other purposes. I installed it on a USB-stick.
>>>
>>> Furthermore installed in my PC there is a MSI GT430 (nvidia) graphics
>>> card and I use the nvidia-driver in conjunction with xorg 1.9.2.
>>>
>>> So far so nice...
>>>
>>> The GRML uses the noveau driver as far as I know.
>>>
>>> When I boot from my USB-stick I get a very nice high resolution
>>> linux console. It uses vga=791 on the kernel commandline.
>>
>> Nouveau uses KMS, which means it automatically uses the monitor's
>> native resolution and supports all resolutions the graphics card is
>> capable of.
>>
>> On your PC, you're using the VESA fb driver, not Nouveau KMS.  That
>> means you're limited to VESA resolutions for your consoles.  You can
>> use the "vbetest" utility to detect which modes your card's VESA BIOS
>> supports.  To use this tool, emerge the "sys-libs/lrmi" package.
>> Simply run the tool and it will print a list of modes you can use, and
>> the resolutions those modes correspond to.
>>
>> If your desired resolution is not in the list, then there's no way to
>> use that resolution in a VESA fb; you will need to switch to Nouveau's
>> KMS fb.
>>
>>
>
> Hi Nikos,
>
> unfortunately lrmi fails to compile.

You can boot an older Live CD (something like Ubuntu 9.x) that has this 
tool.  Run the tool there and save the output for future reference.

[gentoo-user] Re: SVGA mode & the console

[Nikos Chantziaras]

On 01/02/2011 03:57 PM, meino.cramer@gmx.de wrote:
> unfortunately lrmi fails to compile.

In addition to what I wrote in my other reply, make sure you use a 32bit 
Live CD.  vbetest does not work with 64-bit kernels.

Btw, if you're on a 32-bit Gentoo, you can compile lrmi on it.  Steps:

Download 
http://sourceforge.net/projects/lrmi/files/lrmi/0.10/lrmi-0.10.tar.gz/download

Unpack it and apply the patch from Gentoo with:

   cd lrmi-0.10
   patch -p1 < 
/usr/portage/sys-libs/lrmi/files/lrmi-0.10-kernel-2.6.26.patch

Simply run make.  Now you can run it with: ./vbetest

You don't need to install anything.  When you're done, simply delete the 
lrmi-0.10 directory.

Re: [gentoo-user] Re: SVGA mode & the console

[meino.cramer]

Nikos Chantziaras <realnc@arcor.de> [11-01-02 16:12]:
> On 01/02/2011 03:57 PM, meino.cramer@gmx.de wrote:
> >unfortunately lrmi fails to compile.
> 
> In addition to what I wrote in my other reply, make sure you use a 
> 32bit Live CD.  vbetest does not work with 64-bit kernels.
> 
> Btw, if you're on a 32-bit Gentoo, you can compile lrmi on it.  Steps:
> 
> Download 
> http://sourceforge.net/projects/lrmi/files/lrmi/0.10/lrmi-0.10.tar.gz/download
> 
> Unpack it and apply the patch from Gentoo with:
> 
>   cd lrmi-0.10
>   patch -p1 < 
> /usr/portage/sys-libs/lrmi/files/lrmi-0.10-kernel-2.6.26.patch
> 
> Simply run make.  Now you can run it with: ./vbetest
> 
> You don't need to install anything.  When you're done, simply delete 
> the lrmi-0.10 directory.
> 
> 

Hi Nikos,

unfortunately I am on a AMD64 Gentoo.

I will whether GRML has this tool...

Re: [gentoo-user] SVGA mode & the console

[Paul Hartman]

On Sun, Jan 2, 2011 at 5:28 AM,  <meino.cramer@gmx.de> wrote:
> Final question after all there words: How can I get such a high
> resolution with this hardware and the nvidia-drivers???

http://dev.gentoo.org/~spock/projects/uvesafb/

Works for me on ~amd64 gentoo with nvidia-drivers :)

Re: [gentoo-user] SVGA mode & the console

[meino.cramer]

Paul Hartman <paul.hartman+gentoo@gmail.com> [11-01-03 17:27]:
> On Sun, Jan 2, 2011 at 5:28 AM,  <meino.cramer@gmx.de> wrote:
> > Final question after all there words: How can I get such a high
> > resolution with this hardware and the nvidia-drivers???
> 
> http://dev.gentoo.org/~spock/projects/uvesafb/
> 
> Works for me on ~amd64 gentoo with nvidia-drivers :)
> 

Hi,

that sounds really promising! :)

I tried to compile the stuff...but...

When starting to emerge v86d (was it that name...cant remember
exactly) also linux-2.6.26 starts to download and klibc.*

I checked, for what klibc is good for and in this case it is
used for calling the userland tool via from initram, which I
do not plan...

Ok, I thought, than "low level".

I compiled v86d by hand using "./configure --default" for the
default configuration.

But this time it fails to compile with:

   make[1]: Leaving directory `/home/mccramer/data/downloads/v86d-0.1.9/libs/x86emu'
   cc -march=native -O2 -pipe -msse3 -I/lib/modules/2.6.36.2/source/include -Ilibs/x86emu -c -o v86_x86emu.o v86_x86emu.c
   In file included from /usr/include/asm/types.h:4,
                    from /lib/modules/2.6.36.2/source/include/linux/types.h:4,
                    from /lib/modules/2.6.36.2/source/include/linux/connector.h:25,
                    from v86.h:7,
                    from v86_x86emu.c:4:
   /lib/modules/2.6.36.2/source/include/asm-generic/int-ll64.h:11:29: error: asm/bitsperlong.h: No such file or directory
   In file included from /lib/modules/2.6.36.2/source/include/linux/connector.h:25,
                    from v86.h:7,
                    from v86_x86emu.c:4:
   /lib/modules/2.6.36.2/source/include/linux/types.h:13:2: warning: #warning "Attempt to use kernel headers from user space, see http://kernelnewbies.org/KernelHeaders"
   make: *** [v86_x86emu.o] Error 1


I dont know, what the problem is...I am using linux-2.6.36.2 vanilla
and compile this kernel with uvesafb support in beforehand.
Nonetheless there seems something to be missed in the kernel
sources...

My goal is to have a better resolution on the console as this
8bit homecomputer like crap. It doesnot matter that much, whether
switching to the higher resolution happens when the first boot scripts
are read from /etc ...

May I ask you for a little more informations how to proceed here?
How did you achieve a working uvesafb? Do you use the gentoo sources
or the vanilla kernel?

Best regards and thank you very much in advance for your help!
mcc

Re: [gentoo-user] SVGA mode & the console

[meino.cramer]

Paul Hartman <paul.hartman+gentoo@gmail.com> [11-01-03 17:27]:
> On Sun, Jan 2, 2011 at 5:28 AM,  <meino.cramer@gmx.de> wrote:
> > Final question after all there words: How can I get such a high
> > resolution with this hardware and the nvidia-drivers???
> 
> http://dev.gentoo.org/~spock/projects/uvesafb/
> 
> Works for me on ~amd64 gentoo with nvidia-drivers :)
> 

Ok, forget the previous mail... ;)

I give up not to use initramfs and did it as described
in above webpage.

Unfortunately I get an even more blocky design (4bit pocket
calculator design, so to say... ;-/ )

Will try more...we will see.

If you have some more hints for....I would be happier ;)))

Best regards
mcc

Re: [gentoo-user] SVGA mode & the console

[Paul Hartman]

On Mon, Jan 3, 2011 at 11:55 AM,  <meino.cramer@gmx.de> wrote:
> Paul Hartman <paul.hartman+gentoo@gmail.com> [11-01-03 17:27]:
>> On Sun, Jan 2, 2011 at 5:28 AM,  <meino.cramer@gmx.de> wrote:
>> > Final question after all there words: How can I get such a high
>> > resolution with this hardware and the nvidia-drivers???
>>
>> http://dev.gentoo.org/~spock/projects/uvesafb/
>>
>> Works for me on ~amd64 gentoo with nvidia-drivers :)
>>
>
> Hi,
>
> that sounds really promising! :)
>
> I tried to compile the stuff...but...
>
> When starting to emerge v86d (was it that name...cant remember
> exactly) also linux-2.6.26 starts to download and klibc.*
>
> I checked, for what klibc is good for and in this case it is
> used for calling the userland tool via from initram, which I
> do not plan...
>
> Ok, I thought, than "low level".
>
> I compiled v86d by hand using "./configure --default" for the
> default configuration.
>
> But this time it fails to compile with:
>
>   make[1]: Leaving directory `/home/mccramer/data/downloads/v86d-0.1.9/libs/x86emu'
>   cc -march=native -O2 -pipe -msse3 -I/lib/modules/2.6.36.2/source/include -Ilibs/x86emu -c -o v86_x86emu.o v86_x86emu.c
>   In file included from /usr/include/asm/types.h:4,
>                    from /lib/modules/2.6.36.2/source/include/linux/types.h:4,
>                    from /lib/modules/2.6.36.2/source/include/linux/connector.h:25,
>                    from v86.h:7,
>                    from v86_x86emu.c:4:
>   /lib/modules/2.6.36.2/source/include/asm-generic/int-ll64.h:11:29: error: asm/bitsperlong.h: No such file or directory
>   In file included from /lib/modules/2.6.36.2/source/include/linux/connector.h:25,
>                    from v86.h:7,
>                    from v86_x86emu.c:4:
>   /lib/modules/2.6.36.2/source/include/linux/types.h:13:2: warning: #warning "Attempt to use kernel headers from user space, see http://kernelnewbies.org/KernelHeaders"
>   make: *** [v86_x86emu.o] Error 1
>
>
> I dont know, what the problem is...I am using linux-2.6.36.2 vanilla
> and compile this kernel with uvesafb support in beforehand.
> Nonetheless there seems something to be missed in the kernel
> sources...
>
> My goal is to have a better resolution on the console as this
> 8bit homecomputer like crap. It doesnot matter that much, whether
> switching to the higher resolution happens when the first boot scripts
> are read from /etc ...
>
> May I ask you for a little more informations how to proceed here?
> How did you achieve a working uvesafb? Do you use the gentoo sources
> or the vanilla kernel?

Hi,

I use vanilla-sources and do not use initrd. Don't be confused about
initramfs, it does not require you to use initrd. Basically just
follow the directions on that webpage and it should work. Here I'll
explain in different words in case it helps. :)

1. configure your kernel like it says on that page (CONFIG_CONNECTOR=y
and CONFIG_FB_UVESA=y)
2. make the kernel
3. emerge klibc (if it's already installed, emerge it again so it
builds against this newly-configured kernel)
4. emerge v86d
5. configure your kernel again, enable "Initial RAM filesystem and RAM
disk (initramfs/initrd) support"
6. In "Initramfs source file(s)" type /usr/share/v86d/initramfs
7. Make and install the new kernel :)
8. Reboot and type "cat /sys/class/graphics/fb0/modes" to see a list
of compatible modes on your card.
9. Edit your kernel commandline in grub configuration file to add the
uvesafb command. For example mine is
video=uvesafb:1280x720p-59,mtrr:2,ywrap (you can replace 1280x720p-59
with the mode that your card supports from the previous step)
9. Reboot again and hopefully enjoy new high-resolution framebuffer :)

Another way to make it look better is to use different console fonts.
I'm using ter-112n from package media-fonts/terminus-font. You can set
this in /etc/conf.d/consolefont (be sure consolefont is set as a boot
service from rc-update).

If you have a message in dmesg about mtrr type mismatch, you may need
to change from mtrr:2 to another number. Please read the uvesafb
documentation from linux kernel for more info:
/usr/src/linux/Documentation/fb/uvesafb.txt

Good luck :) If you have any problems let me know and I can send you
my kernel .config in case you want to compare settings.

[gentoo-user] Re: SVGA mode & the console

[Nikos Chantziaras]

On 01/03/2011 08:09 PM, meino.cramer@gmx.de wrote:
> Paul Hartman<paul.hartman+gentoo@gmail.com>  [11-01-03 17:27]:
>> On Sun, Jan 2, 2011 at 5:28 AM,<meino.cramer@gmx.de>  wrote:
>>> Final question after all there words: How can I get such a high
>>> resolution with this hardware and the nvidia-drivers???
>>
>> http://dev.gentoo.org/~spock/projects/uvesafb/
>>
>> Works for me on ~amd64 gentoo with nvidia-drivers :)
>>
>
> Ok, forget the previous mail... ;)
>
> I give up not to use initramfs and did it as described
> in above webpage.
>
> Unfortunately I get an even more blocky design (4bit pocket
> calculator design, so to say... ;-/ )
>
> Will try more...we will see.
>
> If you have some more hints for....I would be happier ;)))

uvesafb will not give you extra resolutions.  It will however allow you 
to use non-default refresh-rates which is sometimes useful with CRT 
monitors.

But it has a drawback too: it needs a userspace tool and resolution is 
switched too late during the boot process, meaning until it loads you'll 
be seeing the kernel boot in 80x25 mode (which in turn means no boot 
graphics/logo right from the start.)

Re: [gentoo-user] Re: SVGA mode & the console

[Paul Hartman]

On Mon, Jan 3, 2011 at 2:07 PM, Nikos Chantziaras <realnc@arcor.de> wrote:
> uvesafb will not give you extra resolutions.  It will however allow you to
> use non-default refresh-rates which is sometimes useful with CRT monitors.
>
> But it has a drawback too: it needs a userspace tool and resolution is
> switched too late during the boot process, meaning until it loads you'll be
> seeing the kernel boot in 80x25 mode (which in turn means no boot
> graphics/logo right from the start.)

I use uvesafb and I can see Tux (eight of him) during my boot process
before uvesafb kicks in.

[gentoo-user] Re: SVGA mode & the console

[Nikos Chantziaras]

On 01/03/2011 10:23 PM, Paul Hartman wrote:
> On Mon, Jan 3, 2011 at 2:07 PM, Nikos Chantziaras<realnc@arcor.de>  wrote:
>> uvesafb will not give you extra resolutions.  It will however allow you to
>> use non-default refresh-rates which is sometimes useful with CRT monitors.
>>
>> But it has a drawback too: it needs a userspace tool and resolution is
>> switched too late during the boot process, meaning until it loads you'll be
>> seeing the kernel boot in 80x25 mode (which in turn means no boot
>> graphics/logo right from the start.)
>
> I use uvesafb and I can see Tux (eight of him) during my boot process
> before uvesafb kicks in.

I mean more something like this when I say "boot logo":

http://mjanusz.files.wordpress.com/2008/02/shot.png

It's at least 10 years since I saw that default Tux boot thingy :-P  But 
anyway, if uvesafb hasn't kicked in yet, what on earth is drawing that Tux?

Re: [gentoo-user] SVGA mode & the console

[meino.cramer]

Paul Hartman <paul.hartman+gentoo@gmail.com> [11-01-03 17:27]:
> On Sun, Jan 2, 2011 at 5:28 AM,  <meino.cramer@gmx.de> wrote:
> > Final question after all there words: How can I get such a high
> > resolution with this hardware and the nvidia-drivers???
> 
> http://dev.gentoo.org/~spock/projects/uvesafb/
> 
> Works for me on ~amd64 gentoo with nvidia-drivers :)
> 

Hi all,

thank you very much for all the input !

And....(TADA!).....it works now! :)

Very last question:
Is there any way to test what font looks best without haveing
to boot each time ?


Best regards,
mcc

Re: [gentoo-user] SVGA mode & the console

[Hung Dang]

Hi,

You can try to modify the default font in /etc/conf.d/consolefont and
restart /etc/init.d/consolefont to see if the new font look OK for you
or not. The terminus-font looks OK for me.

Hope  this help
Hung

On 01/03/11 20:04, meino.cramer@gmx.de wrote:
> Paul Hartman <paul.hartman+gentoo@gmail.com> [11-01-03 17:27]:
>> On Sun, Jan 2, 2011 at 5:28 AM,  <meino.cramer@gmx.de> wrote:
>>> Final question after all there words: How can I get such a high
>>> resolution with this hardware and the nvidia-drivers???
>> http://dev.gentoo.org/~spock/projects/uvesafb/
>>
>> Works for me on ~amd64 gentoo with nvidia-drivers :)
>>
> Hi all,
>
> thank you very much for all the input !
>
> And....(TADA!).....it works now! :)
>
> Very last question:
> Is there any way to test what font looks best without haveing
> to boot each time ?
>
>
> Best regards,
> mcc
>
>
>
>

Re: [gentoo-user] Re: SVGA mode & the console

[Paul Hartman]

On Mon, Jan 3, 2011 at 5:22 PM, Nikos Chantziaras <realnc@arcor.de> wrote:
> On 01/03/2011 10:23 PM, Paul Hartman wrote:
>>
>> On Mon, Jan 3, 2011 at 2:07 PM, Nikos Chantziaras<realnc@arcor.de>  wrote:
>>>
>>> uvesafb will not give you extra resolutions.  It will however allow you
>>> to
>>> use non-default refresh-rates which is sometimes useful with CRT
>>> monitors.
>>>
>>> But it has a drawback too: it needs a userspace tool and resolution is
>>> switched too late during the boot process, meaning until it loads you'll
>>> be
>>> seeing the kernel boot in 80x25 mode (which in turn means no boot
>>> graphics/logo right from the start.)
>>
>> I use uvesafb and I can see Tux (eight of him) during my boot process
>> before uvesafb kicks in.
>
> I mean more something like this when I say "boot logo":
>
> http://mjanusz.files.wordpress.com/2008/02/shot.png
>
> It's at least 10 years since I saw that default Tux boot thingy :-P  But
> anyway, if uvesafb hasn't kicked in yet, what on earth is drawing that Tux?

Ah-ha, I think that's bootsplash (which I'm not using).  I've only
seen it on a Live CD. :)

In my kernel config I have enabled VESA framebuffer as well as
userspace framebuffer (uvesafb), and I enabled "Bootup Logo". So maybe
what happens is that VESA framebuffer starts immediately into some
default resolution, I see eight Tuxs (Tuxes?), then shortly thereafter
the uvesafb kicks in and video mode changes to the one I specified. At
least that's how it seems to happen. I reboot so rarely that I never
gave it much thought.

Re: [gentoo-user] SVGA mode & the console

[Paul Hartman]

On Mon, Jan 3, 2011 at 9:04 PM,  <meino.cramer@gmx.de> wrote:
> Very last question:
> Is there any way to test what font looks best without haveing
> to boot each time ?

setfont

Re: [gentoo-user] SVGA mode & the console

[meino.cramer]

Paul Hartman <paul.hartman+gentoo@gmail.com> [11-01-04 17:28]:
> On Mon, Jan 3, 2011 at 9:04 PM,  <meino.cramer@gmx.de> wrote:
> > Very last question:
> > Is there any way to test what font looks best without haveing
> > to boot each time ?
> 
> setfont
> 

Hi all,

thank you very much for your help again!
Now I have a beautiful console!
Long lives Linux! ;)

Best regards,
mcc

Re: [gentoo-user] Re: SVGA mode & the console

[Alan McKinnon]

Apparently, though unproven, at 18:03 on Tuesday 04 January 2011, Paul Hartman 
did opine thusly:

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


It's the VESA framebuffer that does it, nothing to do with bootsplash.

Look at the help text for CONFIG_FB_VESA in menuconfig.


-- 
alan dot mckinnon at gmail dot com