Which is the default console font?
Just post the setfont line from /etc/rc.d/rc.font and I will be happy again.

Using Slackware 9.1
--
copyright is copywrong
copyleft is copyright

On Thu, 19 Feb 2004 23:33:38 GMT,
haggeluring <hagman@comhem.se> wrote:
> Which is the default console font?
> Just post the setfont line from /etc/rc.d/rc.font and I will be happy again.

The default font, AFAIK is not listed in /usr/share/kbd/consolefonts/
but is "builtin". The only way I know for the default font to be enabled
is to disable rc.font and reboot.


--
Mark Hill <usenet@mark.ukfsn.org> (devnull address not read)
GPG KeyID: 4A3B58AC

On 20 Feb 2004 00:13:52 GMT, Mark Hill
<devnull@mark.ukfsn.org> appears to have said:

> On Thu, 19 Feb 2004 23:33:38 GMT,
> haggeluring <hagman@comhem.se> wrote:
>> Which is the default console font?
>> Just post the setfont line from /etc/rc.d/rc.font and I will be happy again.
>
> The default font, AFAIK is not listed in /usr/share/kbd/consolefonts/
> but is "builtin". The only way I know for the default font to be enabled
> is to disable rc.font and reboot.

Yep... it took me a long time to discover that the "default" font
is actually just whatever font is built in to the video card.

If you have svgalib installed you can save/restore the vga font with
restorefont {-w|-r} filename. (Could be hazardous to your console's
health, though.)

ciao,
Jonathan

--
Don't just hit reply. Email address is broken. Thank
your friendly neighborhood spammer. Email replies to:
user: jnthn1 domain: earthlink<dot>net

On 20 Feb 2004 15:43:25 GMT,
Jonathan A. <me@privacy.net> wrote:
> On 20 Feb 2004 00:13:52 GMT, Mark Hill
><devnull@mark.ukfsn.org> appears to have said:
>
>> The default font, AFAIK is not listed in /usr/share/kbd/consolefonts/
>> but is "builtin". The only way I know for the default font to be enabled
>> is to disable rc.font and reboot.
>
> Yep... it took me a long time to discover that the "default" font
> is actually just whatever font is built in to the video card.

Is that the case for framebuffer-enabled consoles also? I suspect the
default font used there is the one(s) you can select during the kernel
compilation process [1], but I haven't investigated it enough to be
sure.

[1] E.g: (from .config)
CONFIG_FBCON_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y


--
Mark Hill <usenet@mark.ukfsn.org> (devnull address not read)
GPG KeyID: 4A3B58AC

On 22 Feb 2004 00:30:36 GMT, Mark Hill
<devnull@mark.ukfsn.org> appears to have said:

> On 20 Feb 2004 15:43:25 GMT,
> Jonathan A. <me@privacy.net> wrote:
>>
>> Yep... it took me a long time to discover that the "default" font
>> is actually just whatever font is built in to the video card.
>
> Is that the case for framebuffer-enabled consoles also?

I don't know... I never thought of it, to tell the truth. I always
found FB to be painfully slow. Every time I've tried it, I turned
tail and ran back to the VGA console in short order.

> I suspect the default font used there is the one(s) you can select
> during the kernel compilation process [1], but I haven't investigated
> it enough to be sure.

Dunno... Configure.help from 2.4.24 says:

CONFIG_FBCON_FONTS
Say Y here if you would like to use fonts other than the default
your frame buffer console usually use.

So that leaves it pretty unclear, IMO. Depends on just where FB gets
"the default your frame buffer console usually use." I was curious
enough to take a quick google, but didn't turn up much.

It would be interesting to know, though. <shrug>

ciao,
Jonathan

--
Don't just hit reply. Email address is broken. Thank
your friendly neighborhood spammer. Email replies to:
user: jnthn1 domain: earthlink<dot>net

On Sat, 22 Feb 2004, Jonathan A. wrote:
> On 22 Feb 2004 00:30:36 GMT, Mark Hill <devnull@mark.ukfsn.org>
>> On 20 Feb 2004 15:43:25 GMT, Jonathan A. <me@privacy.net> wrote:
>>> Yep... it took me a long time to discover that the "default" font
>>> is actually just whatever font is built in to the video card.
>> Is that the case for framebuffer-enabled consoles also?
>
> I don't know... I never thought of it, to tell the truth. I always
> found FB to be painfully slow. Every time I've tried it, I turned
> tail and ran back to the VGA console in short order.
[...]

one nice thing about framebuffer is the ability to change the number
of rows and columns displayed. myself just started using this, but
it seems to be worth suffering slowness. i have some log following
at 85x128, most consoles at 34x80, some coding at 48x128.



--
William Hunt, Portland Oregon USA

On Sat, 21 Feb 2004 21:39:52 -0800,
William Hunt <wjh@huntbros.net> wrote:
>
> one nice thing about framebuffer is the ability to change the number
> of rows and columns displayed.

Sounds good. Will have to play around with that.

One of my biggest likes about the framebuffer is the ability to display
graphics. There's an excellent tool caled fbi, which is an image viewer
for the fb. Also, there's "links -g -driver fb", which can save firing up
an X-based browser for certain web sites.


--
Mark Hill <usenet@mark.ukfsn.org> (devnull address not read)
GPG KeyID: 4A3B58AC

On 22 Feb 2004 02:49:50 GMT,
Jonathan A. <me@privacy.net> wrote:
> On 22 Feb 2004 00:30:36 GMT, Mark Hill
><devnull@mark.ukfsn.org> appears to have said:

> I don't know... I never thought of it, to tell the truth. I always
> found FB to be painfully slow.

There are FB modules for specific cards. Perhaps they'd fare
better than the default VESA?

>> I suspect the default font used there is the one(s) you can select
>> during the kernel compilation process
>
> CONFIG_FBCON_FONTS
> Say Y here if you would like to use fonts other than the default
> your frame buffer console usually use.
>
> So that leaves it pretty unclear, IMO.

I'd agree. :\

A quick look in the kernel docs didn't bring any further clarification.
Perhaps only the source has the answer.


--
Mark Hill <usenet@mark.ukfsn.org> (devnull address not read)
GPG KeyID: 4A3B58AC

On 24 Feb 2004 03:07:49 GMT, Mark Hill
<devnull@mark.ukfsn.org> appears to have said:

> On 22 Feb 2004 02:49:50 GMT,
> Jonathan A. <me@privacy.net> wrote:
>
>> I don't know... I never thought of it, to tell the truth. I always
>> found FB to be painfully slow.
>
> There are FB modules for specific cards. Perhaps they'd fare
> better than the default VESA?

Probably, but I've heard nothing but horror stories about my setup.
(Nvidia card w/evil binary-only NV driver + rivafb = nightmare, for
all I've heard.) Besides... I actually *like* the VGA console.

>> CONFIG_FBCON_FONTS
>> Say Y here if you would like to use fonts other than the default
>> your frame buffer console usually use.
>>
>> So that leaves it pretty unclear, IMO.
>
> I'd agree. :\
>
> A quick look in the kernel docs didn't bring any further clarification.
> Perhaps only the source has the answer.

I don't know if svgalib tools work under framebuffer but, if they do,
and you really want to know, you could boot to FB with the "default"
font and do "restorefont -w FB-Fontdata" then boot to raw VGA mode
at the same resolution and "restorefont -w VGA-Fontdata." If FB is
using your video card's built-in font, the files should be identical,
I would think.

FWIW,
Jonathan

--
Don't just hit reply. Email address is broken. Thank
your friendly neighborhood spammer. Email replies to:
user: jnthn1 domain: earthlink<dot>net

On 24 Feb 2004 13:27:35 GMT,
Jonathan A. <me@privacy.net> wrote:
> On 24 Feb 2004 03:07:49 GMT, Mark Hill
><devnull@mark.ukfsn.org> appears to have said:
>
>> There are FB modules for specific cards. Perhaps they'd fare
>> better than the default VESA?
>
> Probably, but I've heard nothing but horror stories about my setup.
> (Nvidia card w/evil binary-only NV driver + rivafb = nightmare, for
> all I've heard.)

I have a similar setup, (NV driver / TNT 2 M64), and find VESA works
fine. (I haven't given rivafb a fair go yet.)

> Besides... I actually *like* the VGA console.

Fair enough then.

> you could boot to FB with the "default"
> font and do "restorefont -w FB-Fontdata" then boot to raw VGA mode
> at the same resolution and "restorefont -w VGA-Fontdata." If FB is
> using your video card's built-in font, the files should be identical,
> I would think.

Thanks. I'll have to give that a try.

--
Mark Hill <usenet@mark.ukfsn.org> (devnull address not read)
GPG KeyID: 4A3B58AC