>> In addition, on the computer with the Matrox-adapter running
>> something as simple as 'dmesg -T' is really really slow. It literally
>> takes several seconds while the text scrolls on the screen.
>> The thing is, I do not really care about fancy framebuffer resolution
and
>> graphics on the
On 2017-12-28 16:53 +, Brian wrote:
> On Thu 28 Dec 2017 at 17:12:47 +0100, henrik i wrote:
>
>> A small update. I did some more testing on the system with Intel 3600
>> graphics, and at least one working solution was to blacklist the module:
>>
>> In /etc/modprobe.d/whatever.conf
>>
On Thu 28 Dec 2017 at 17:12:47 +0100, henrik i wrote:
> A small update. I did some more testing on the system with Intel 3600
> graphics, and at least one working solution was to blacklist the module:
>
> In /etc/modprobe.d/whatever.conf
> blacklist gma500_gfx
>
> This enabled me to use the
ed to troubleshoot from the console. When I do this, I just connect
> a plain VGA cable to my 1920x1200 Dell monitor. Just upgraded to Stretch
> with kernel 4.9 and noticed that no matter what I do, the console
> resolution is 1920x1200. In addition, on the computer with the
> Matrox-adapt
Hi,
I got two computers that usually run headless, but from time to time I
might need to troubleshoot from the console. When I do this, I just connect
a plain VGA cable to my 1920x1200 Dell monitor. Just upgraded to Stretch
with kernel 4.9 and noticed that no matter what I do, the console
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Oct 06, 2017 at 05:45:07PM +0530, Mayuresh Kathe wrote:
> On 2017-10-06 05:30 PM, Darac Marjal wrote:
> >On Fri, Oct 06, 2017 at 03:00:50PM +0530, Mayuresh Kathe wrote:
> >>i tried my level best to do it, but have failed.
> >>i used
Mayuresh Kathe composed on 2017-10-06 15:00 (UTC+0530):
> i tried my level best to do it, but have failed.
> i used 'dpkg-reconfigure console-setup' and followed the
> appropriate steps, but yet my console's screen resolution
> is way to high. not that it's a big problem, just an
> irritant, the
On 2017-10-06 05:30 PM, Darac Marjal wrote:
On Fri, Oct 06, 2017 at 03:00:50PM +0530, Mayuresh Kathe wrote:
i tried my level best to do it, but have failed.
i used 'dpkg-reconfigure console-setup' and followed the
appropriate steps, but yet my console's screen resolution
is way to high. not
On Fri, Oct 06, 2017 at 03:00:50PM +0530, Mayuresh Kathe wrote:
i tried my level best to do it, but have failed.
i used 'dpkg-reconfigure console-setup' and followed the
appropriate steps, but yet my console's screen resolution
is way to high. not that it's a big problem, just an
irritant, the
i tried my level best to do it, but have failed.
i used 'dpkg-reconfigure console-setup' and followed the
appropriate steps, but yet my console's screen resolution
is way to high. not that it's a big problem, just an
irritant, the text is usually too tiring to read.
can i be helped?
thanks,
On Mon 14 Nov 2011 at 21:48:05 -0500, Dan B. wrote:
When I boot with my monitor connected (through a KVM), I end up with
high-resolution virtual consoles (67 rows by 240 columns).
However, when I boot with the KVM switched away, then since the
kernel/etc. can't auto-detect my monitor, I get
Brian wrote:
On Mon 14 Nov 2011 at 21:48:05 -0500, Dan B. wrote:
When I boot with my monitor connected (through a KVM), I end up with
high-resolution virtual consoles (67 rows by 240 columns).
However, when I boot with the KVM switched away, then since the
kernel/etc. can't auto-detect my
On Tue 15 Nov 2011 at 11:03:33 -0500, Dan B. wrote:
What tools (commands) are there in console-data or console-tools or
whatever for getting (and changing) the console video settings?
dpkg-reconfigure console-setup
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a
What command shows the virtual console video mode (specifically,
the information needed to set it to that mode if it's in a different
mode)?
When I boot with my monitor connected (through a KVM), I end up with
high-resolution virtual consoles (67 rows by 240 columns).
However, when I boot with
On Lu, 14 nov 11, 21:48:05, Dan B. wrote:
What command shows the virtual console video mode (specifically,
the information needed to set it to that mode if it's in a different
mode)?
When I boot with my monitor connected (through a KVM), I end up with
high-resolution virtual consoles (67
On 18/02/11 20:11, Sven Joachim wrote:
On 2011-02-18 20:22 +0100, Dom wrote:
On 18/02/11 18:24, Camaleón wrote:
To make this a bit more clear, nvidia card owners can run either:
a) KMS+nouveau
b) nvidia propietary driver
c) vesa/fb
d) nv (obsolete but still available, AFAICT)
d) is the
On Vi, 18 feb 11, 19:22:07, Dom wrote:
d) is the only option that worked for one of my machines. It used to
run the nvidia driver, but stopped working when I upgraded it to
squeeze and it tried to use the nouveau driver.
Removing all traces of the nvidia driver and just using nouveau
On Fri, 18 Feb 2011 13:49:33 -0500, Paul Cartwright wrote:
To make this a bit more clear, nvidia card owners can run either:
a) KMS+nouveau
so, what is this, why would I want it?
It's another driver available for your card. It is open source and it
uses reverse engineering techniques
On Fri, 18 Feb 2011 19:56:50 +0100, Pier Paolo wrote:
2011/2/18 Camaleón
What is what you tried hard, exactly?
from rescue mode chrooting to recompile kernel after a not even
system-base-install alternate cd netinstall. Booting from hard disk
resulted in complete unusable system with vt
2011/2/19 Camaleón noela...@gmail.com
On Fri, 18 Feb 2011 19:56:50 +0100, Pier Paolo wrote:
2011/2/18 Camaleón
What is what you tried hard, exactly?
from rescue mode chrooting to recompile kernel after a not even
system-base-install alternate cd netinstall. Booting from hard disk
On Sat, 19 Feb 2011 14:55:55 +0100, Pier Paolo wrote:
2011/2/19 Camaleón
I asked what you tried hard for the easy way, what steps did you
follow and what errors did you get.
Can't recall exactly... some procedure from the wiki; i think i
blacklisted nouveau, and tried to install
2011/2/19 Camaleón noela...@gmail.com
On Sat, 19 Feb 2011 14:55:55 +0100, Pier Paolo wrote:
2011/2/19 Camaleón
I asked what you tried hard for the easy way, what steps did you
follow and what errors did you get.
Can't recall exactly... some procedure from the wiki; i think i
On Sat, 19 Feb 2011 15:17:15 +0100, Pier Paolo wrote:
2011/2/19 Camaleón
Can't recall exactly... some procedure from the wiki; i think i
blacklisted nouveau, and tried to install kernel-nvidia something,
but substantially that won't prevent nouveau from loading and messing
up console.
On Thu, 17 Feb 2011 20:07:51 -0500, Chris Brennan wrote:
I am not new to the linux way of things but I am new to the debain way
of things and I have some questions that need to be answered. To start,
I need to ket rid of nouveau as it's screwing with uvesafb (produces an
'Error -22').
2011/2/18 Camaleón noela...@gmail.com
On Thu, 17 Feb 2011 20:07:51 -0500, Chris Brennan wrote:
I am not new to the linux way of things but I am new to the debain way
of things and I have some questions that need to be answered. To start,
I need to ket rid of nouveau as it's screwing with
El 2011-02-18 a las 10:33 -0500, Chris Brennan escribió:
On Fri, Feb 18, 2011 at 7:41 AM, Camaleón wrote:
By installing nvidia driver, nuvó should not be loaded.
the non-free nvidia driver script/installer dies, complaining that nouveau
is present and needs to be removed first, this is
Camaleón wrote:
El 2011-02-18 a las 10:33 -0500, Chris Brennan escribió:
On Fri, Feb 18, 2011 at 7:41 AM, Camaleón wrote:
By installing nvidia driver, nuvó should not be loaded.
the non-free nvidia driver script/installer dies, complaining that nouveau
is present and needs to be removed
On Fri, 18 Feb 2011 17:40:40 +0100, Pier Paolo wrote:
2011/2/18 Camaleón
By installing nvidia driver, nuvó should not be loaded.
Also, by disabling KMS (nouveau.modeset=0) nuvó should not load.
At least in Debian Lenny and Fedora 12 it was not so simple as said in
debian wiki or by you;
On 02/18/2011 07:41 AM, Camaleón wrote:
By installing nvidia driver, nuvó should not be loaded.
Also, by disabling KMS (nouveau.modeset=0) nuvó should not load.
Greetings,
wow, I just looked at my new Squeeze xorg.conf device section. What is
the nouveau, and should we be using/not using
On Fri, 18 Feb 2011 13:05:16 -0500, Paul Cartwright wrote:
On 02/18/2011 07:41 AM, Camaleón wrote:
By installing nvidia driver, nuvó should not be loaded.
Also, by disabling KMS (nouveau.modeset=0) nuvó should not load.
wow, I just looked at my new Squeeze xorg.conf device section.
Drivernvidia
^^
You are not using nuvó at all but the nvidia driver:-)
right, I knew that.
To make this a bit more clear, nvidia card owners can run either:
a) KMS+nouveau
so, what is this, why would I want it?
b) nvidia propietary driver
2011/2/18 Camaleón noela...@gmail.com
On Fri, 18 Feb 2011 17:40:40 +0100, Pier Paolo wrote:
2011/2/18 Camaleón
By installing nvidia driver, nuvó should not be loaded.
Also, by disabling KMS (nouveau.modeset=0) nuvó should not load.
At least in Debian Lenny and Fedora 12 it was not
console resolution as well as not displaying things in X
correctly (unreadable in fact, but I am able to drop back to console and
cleanly terminate X w/ '/etc/init.d/kdm stop'.
First of all, please reply to the list for the benefit of others following
the thread and so that the list archives can
On 18/02/11 18:24, Camaleón wrote:
On Fri, 18 Feb 2011 13:05:16 -0500, Paul Cartwright wrote:
On 02/18/2011 07:41 AM, Camaleón wrote:
By installing nvidia driver, nuvó should not be loaded.
Also, by disabling KMS (nouveau.modeset=0) nuvó should not load.
wow, I just looked at my new
On 2011-02-18 20:22 +0100, Dom wrote:
On 18/02/11 18:24, Camaleón wrote:
To make this a bit more clear, nvidia card owners can run either:
a) KMS+nouveau
b) nvidia propietary driver
c) vesa/fb
d) nv (obsolete but still available, AFAICT)
d) is the only option that worked for one of my
On Fri, 18 Feb 2011 13:49:33 -0500 (EST), Paul Cartwright wrote:
Camaleón wrote:
You are not using nuvó at all but the nvidia driver:-)
right, I knew that.
To make this a bit more clear, nvidia card owners can run either:
a) KMS+nouveau
...
so, what is this, why would I want
I am not new to the linux way of things but I am new to the debain
way of things and I have some questions that need to be answered. To
start, I need to ket rid of nouveau as it's screwing with uvesafb
(produces an 'Error -22'). I added it to
/etc/modprobe.d/blacklist.conf but it's still being
On Thu, 17 Feb 2011 20:07:51 -0500 (EST), Chris Brennan wrote:
I am not new to the linux way of things but I am new to the debain
way of things and I have some questions that need to be answered. To
start, I need to ket rid of nouveau as it's screwing with uvesafb
(produces an 'Error -22').
I am not new to the linux way of things but I am new to the debain
way of things and I have some questions that need to be answered. To
start, I need to ket rid of nouveau as it's screwing with uvesafb
(produces an 'Error -22'). I added it to
/etc/modprobe.d/blacklist.conf but it's still
On Wed, Jan 27, 2010 at 09:17:51PM +0200, Andrei Popescu wrote:
On Sun,24.Jan.10, 14:22:22, Nima Azarbayjany wrote:
I was able to achieve the desired resolution of 1280x800 (equivalent
to, I think, 0x361) by manually editing grub.cfg but the grub menu
does not show correctly. It only fills
On Tue, Feb 02, 2010 at 01:50:23AM +1300, Chris Bannister wrote:
Looks like a bug in /usr/share/doc/grub2-splashimages/README where it
says to run update-grub, that should be update-grub2.
Arrrgh ... I see that:
fischer:~# less /usr/sbin/update-grub2
#!/bin/sh -e
exec update-grub
Sorry about
On Fri,22.Jan.10, 15:38:55, Nima Azarbayjany wrote:
Hi,
I have recently installed Squeeze on my laptop and most things seem
to work fine right now.
I used to add vga=xxx to the kernel parameters line to adjust the
console resolution but this is now deprecated as a message printed
On Sun,24.Jan.10, 14:22:22, Nima Azarbayjany wrote:
I was able to achieve the desired resolution of 1280x800 (equivalent
to, I think, 0x361) by manually editing grub.cfg but the grub menu
does not show correctly. It only fills the left top quarter of the
screen and parts of it cannot be seen.
of using the nvidia
framebuffer and the nvidia binary driver ?
[..]
--
You will be the victim of a bizarre joke.
:-)
I the above question the bizarre joke, or was this meant as a reply to a
different post?
Sorry didn't see this reply. The thread was about frame buffer and
console
s. keeling wrote:
Jeffrey Cao jcao.li...@gmail.com:
On 2010-01-22, Nima Azarbayjany i.adore.deb...@gmail.com wrote:
I have recently installed Squeeze on my laptop and most things
seem to work fine right now.
I used to add vga=xxx to the kernel parameters line to adjust the
console
Okay... I finally got it to work. I set two different resolutions, that
is, I did not use gfxpayload=keep.
Thanks all.
Nima
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
tv.deb...@googlemail.com tv.deb...@googlemail.com:
s. keeling wrote:
Isn't it strange that we now need to `update-grub`, when having to run
lilo was such a hardship before?
Grumble, mumble, wtf doesn't OpenBSD ever show up in the grub* boot
menu, grumble, mumble, ... Grr.
Hi
On Mon, Jan 25, 2010 at 10:26:45PM EST, s. keeling wrote:
[..]
My complaint is neither grub-legacy nor grub2 ever pick up my OBSD
install, yet /etc/grub.d/40_custom is there and describes it, and
/boot/grub/menu.lst is there to upgrade from.
Just be aware that auto-detecting kernels is not
My complaint is neither grub-legacy nor grub2 ever pick up my OBSD
install, yet /etc/grub.d/40_custom is there and describes it, and
/boot/grub/menu.lst is there to upgrade from.
From
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/432254
I finally got the boot into FreeBSD to work.
I was able to achieve the desired resolution of 1280x800 (equivalent to,
I think, 0x361) by manually editing grub.cfg but the grub menu does not
show correctly. It only fills the left top quarter of the screen and
parts of it cannot be seen. The rest was fine (the boot up of linux I
mean)
On Sun, Jan 24, 2010 at 05:52:22AM EST, Nima Azarbayjany wrote:
I was able to achieve the desired resolution of 1280x800 (equivalent
to, I think, 0x361) by manually editing grub.cfg but the grub menu
does not show correctly. It only fills the left top quarter of the
screen and parts of it
Jeffrey Cao jcao.li...@gmail.com:
On 2010-01-22, Nima Azarbayjany i.adore.deb...@gmail.com wrote:
I have recently installed Squeeze on my laptop and most things
seem to work fine right now.
I used to add vga=xxx to the kernel parameters line to adjust the
console resolution
On Sat, Jan 23, 2010 at 01:15:39AM EST, Chris Jones wrote:
[..]
I the above question the bizarre joke, or was this meant as a reply to a
different post?
s/I the above/Is the above/
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Nima Azarbayjany wrote:
set gfxpayload=keep will tell Grub2 to hand off the graphics settings
to the kernel, which if configured properly will carry them forward.
There are some other settings to tweak as well, insmod vbe and whatnot
in the appropriate file, but that's about the gist of it.
On 2010-01-22 at 18:11:38 -0500, Chris Jones wrote:
PIII 650MHz - 386M of RAM - ATI Rage Mobility (Mach64).
That is *lightning fast* compared to my slowest machine,
a PII 266 MHz with a very slow hard drive. And the saddest
thing is, until about three years ago, it was my fastest machine!
The
It's weird but it's not working for me. Somehow update-grub (as well as
update-grub2, in case they are different) ignore all modifications to
/etc/default/grub. I'm giving up. Should I report a bug?
Hi, I use a slightly different way, I put:
GRUB_GFXMODE=1440x900 640x480
in
It's weird but it's not working for me. Somehow update-grub (as well as
update-grub2, in case they are different) ignore all modifications to
/etc/default/grub. I'm giving up. Should I report a bug?
Are you making all the changes that have been suggested?
In short:
In
/etc/default/grub
tv.debian wrote:
Hi, I use a slightly different way, I put:
GRUB_GFXMODE=1440x900 640x480
in /etc/defaults/grub (native resolution first, fall-back one isn't
necessary, it's the default).
Then in /etc/grub.d/00_header I add gfxpayload=keep to this section
(around line 80):
[...]
if
Hi,
I have recently installed Squeeze on my laptop and most things seem to
work fine right now.
I used to add vga=xxx to the kernel parameters line to adjust the
console resolution but this is now deprecated as a message printed at
the startup says. What should be passed to the kernel
On 2010-01-22, Nima Azarbayjany i.adore.deb...@gmail.com wrote:
Hi,
I have recently installed Squeeze on my laptop and most things seem to
work fine right now.
I used to add vga=xxx to the kernel parameters line to adjust the
console resolution but this is now deprecated as a message
Hi,
On Fri, Jan 22, 2010 at 1:08 PM, Nima Azarbayjany
i.adore.deb...@gmail.comwrote:
Hi,
I have recently installed Squeeze on my laptop and most things seem to work
fine right now.
I used to add vga=xxx to the kernel parameters line to adjust the console
resolution but this is now
Nima Azarbayjany wrote at 2010-01-22 06:08 -0600:
I have recently installed Squeeze on my laptop and most things seem
to work fine right now.
I used to add vga=xxx to the kernel parameters line to adjust the
console resolution but this is now deprecated as a message printed
at the startup
the
console resolution but this is now deprecated as a message printed at
the startup says. What should be passed to the kernel instead of, for
example, vga=0x361? Let me add that I have upgraded the kernel to
2.6.32 from sid.
For the new grub, edit the file /etc/default/grub, add
On 2010-01-22 at 09:00:54 -0500, Javier Barroso wrote:
Seem like gfxpayload is the substitute, but now I can't find where is the
doc (it doesn't appear in kernel-parameters.txt).
The vga kernel option is a strange option. It's really more of
a bootloader option than a kernel option. The
On Fri, Jan 22, 2010 at 10:03 AM, Stephen Powell zlinux...@wowway.comwrote:
On 2010-01-22 at 09:00:54 -0500, Javier Barroso wrote:
Seem like gfxpayload is the substitute, but now I can't find where is the
doc (it doesn't appear in kernel-parameters.txt).
I'm really going out on a limb when
On 2010-01-22 at 12:08:56 -0500, Arthur Machlas wrote:
set gfxpayload=keep will tell Grub2 to hand off the graphics settings to the
kernel, which if configured properly will carry them forward. There are some
other settings to tweak as well, insmod vbe and whatnot in the appropriate
file, but
On Fri, 2010-01-22 at 13:08 -0500, Stephen Powell wrote:
snip
Jeffrey Cao wrote in another post that grub2 can support the traditional
vga kernel option by means of editing /etc/default/grub and adding the
line
GRUB_CMDLINE_LINUX=vga=xxx
and then running update-grub to update
set gfxpayload=keep will tell Grub2 to hand off the graphics settings
to the kernel, which if configured properly will carry them forward.
There are some other settings to tweak as well, insmod vbe and whatnot
in the appropriate file, but that's about the gist of it. The nice
thing is it
On Fri, Jan 22, 2010 at 01:08:23PM EST, Stephen Powell wrote:
[..]
So then this is designed to work with framebuffer graphics mode
virtual consoles, right? That wouldn't help me. I prefer the
traditional hardware text mode virtual consoles.
Just curious, but what's wrong with using a
On 2010-01-22 at 15:50:02 -0500, Chris Jones wrote:
On Fri, Jan 22, 2010 at 01:08:23PM EST, Stephen Powell wrote:
So then this is designed to work with framebuffer graphics mode
virtual consoles, right? That wouldn't help me. I prefer the
traditional hardware text mode virtual consoles.
On Fri, Jan 22, 2010 at 04:47:29PM EST, Stephen Powell wrote:
I prefer a hardware text mode virtual console for a number of
reasons, but one of them is that it performs better, particularly
on the ancient under-powered hardware that I tend to use!
PIII 650MHz - 386M of RAM - ATI Rage Mobility
On Fri, Jan 22, 2010 at 06:11:38PM -0500, Chris Jones wrote:
On Fri, Jan 22, 2010 at 04:47:29PM EST, Stephen Powell wrote:
[snip]
I don't know if my video card takes care of that, but I find that moving
the cursor, scrolling, etc. is noticeably faster on a framebuffer
console than on the
On Fri, Jan 22, 2010 at 09:39:50PM EST, Alex Samad wrote:
On Fri, Jan 22, 2010 at 06:11:38PM -0500, Chris Jones wrote:
[..]
I don't know if my video card takes care of that, but I find that
moving the cursor, scrolling, etc. is noticeably faster on a
framebuffer console than on the vga
well, since i've completely failed to get x working beyond a messed up
640x480 res that flickers and uses really wacky colors on this
machine... is there a way to change the console resolution to somthing a
little higher?
or someone who has a thinpad 365XD w/ an active matrix screen could
On Sat, Jan 20, 2001 at 12:55:30AM -0800, forrest wrote:
well, since i've completely failed to get x working beyond a messed up
640x480 res that flickers and uses really wacky colors on this
machine... is there a way to change the console resolution to somthing a
little higher?
or someone
On Sat, Jan 20, 2001 at 12:55:30AM -0800, forrest wrote:
:well, since i've completely failed to get x working beyond a messed up
:640x480 res that flickers and uses really wacky colors on this
:machine... is there a way to change the console resolution to somthing a
:little higher?
:
:or someone
on Sat, Jan 20, 2001 at 12:55:30AM -0800, forrest ([EMAIL PROTECTED]) wrote:
well, since i've completely failed to get x working beyond a messed up
640x480 res that flickers and uses really wacky colors on this
machine... is there a way to change the console resolution to somthing a
little
On Fri, 27 Feb 1998, Benoit Goudreault-Emond wrote:
[snip]
Hmm, I used to have that running with my tseng et4000, but when I went to
my new s3 virge, It died completely... anyway, 80x34 is fine... 80x25 is
just too large... I hate DOS so much... :)
Died how? Don't forget that you
[snip]
Hmm, I used to have that running with my tseng et4000, but when I went to
my new s3 virge, It died completely... anyway, 80x34 is fine... 80x25 is
just too large... I hate DOS so much... :)
Died how? Don't forget that you absolutely HAVE to load fonts if you use
any S3 based card in
On Thu, 26 Feb 1998, Benoit Goudreault-Emond wrote:
[A heck of a lot clipped]
I hope that will be of some use to you.
Apparently not... I am beginning to think I need to raise some money for a
new monitor.. :( limits: 30-50 horiz 50-75 Vert
Oh well...
Well, you can change
On Sun, 22 Feb 1998, Benoit Goudreault-Emond wrote:
As a matter of interest, who is using SVGATextMode with an S3 ViRGE and a
1024x768 capable monitor? if I try to go above 80x30, the characters on
the left hand side of the screen get all screwy, and sometimes the left of
the screen is
[A heck of a lot clipped]
I hope that will be of some use to you.
Apparently not... I am beginning to think I need to raise some money for a
new monitor.. :( limits: 30-50 horiz 50-75 Vert
Oh well...
Well, you can change the first number on the modeline, I beleive it's
the dot clock.
On Sat, 21 Feb 1998, Bill Leach wrote:
William R. Ward wrote:
[snip]
I've never seen much point in svgatextmode, personally - you can get
80x50 from LILO, isn't that enough?
The 80x50 LILO can give me, also gives me 8x8 pixel characters. Using
SVGATextMode I have 116x51 using 16x9 pixel
On Mon, 23 Feb 1998, Remco Blaakmeer wrote:
On Sat, 21 Feb 1998, Bill Leach wrote:
William R. Ward wrote:
[snip]
I've never seen much point in svgatextmode, personally - you can get
80x50 from LILO, isn't that enough?
The 80x50 LILO can give me, also gives me 8x8 pixel characters.
As a matter of interest, who is using SVGATextMode with an S3 ViRGE and a
1024x768 capable monitor? if I try to go above 80x30, the characters on
the left hand side of the screen get all screwy, and sometimes the left of
the screen is cut off at the 10thish column and is repeated from there...
The 80x50 LILO can give me, also gives me 8x8 pixel characters.
Using SVGATextMode I have 116x51 using 16x9 pixel characters.
Readable characters are enough reason for me.
I don't even remember what I am using in lilo but I am quite happy with
it (bully for me).
But if you haven't
William R. Ward wrote:
[snip]
I've never seen much point in svgatextmode, personally - you can get
80x50 from LILO, isn't that enough?
I'm all for giving everyone as many options as practical but
SVGATextMode is one that I plan on leaving off of my system.
Quite fortunately, for me, after
87 matches
Mail list logo
