Mailinglist Archive: opensuse (1696 mails)
| < Previous | Next > |
Re: [opensuse] Font size is too big
- From: Felix Miata <mrmazda@xxxxxxxxxxxxx>
- Date: Sun, 26 Jul 2009 16:48:06 -0400
- Message-id: <4A6CC106.2040707@xxxxxxxxxxxxx>
On 2009/07/26 20:23 (GMT+0100) Sean Rima composed:
DPI affects point sizes, but not px sizes. Most apps and desktop fonts are pt
sizes, heavily affected by DPI. Mozilla is an exception, with fonts not
affected by DPI. If you don't change the size back to 8 or more _before_
fixing the real problem, you may find if very difficult to set back.
Either boot into runlevel 3 directly, or after boot to X, instead of logging
in, switch to one of the virtual consoles, login as root, 'init 3', 'sax2',
and specify nv driver and a generic 1680x1050 22" display or some similar
Samsung LCD. Then 'init 5' and see if X got fixed. Normally VESA display
and/or gfxcard driver is for emergency use only on widescreen displays, and
won't be able to be configured for good results on a HDMI cable. You might
ultimately need the proprietary driver, but it's easier to try nv first if
right now you're stuck in VESA.
--
No Jesus - No peace , Know Jesus - Know Peace
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
but I have changed the font
size to 4, now that affects most things but Mozilla is still to big, and
the icons are blurry
DPI affects point sizes, but not px sizes. Most apps and desktop fonts are pt
sizes, heavily affected by DPI. Mozilla is an exception, with fonts not
affected by DPI. If you don't change the size back to 8 or more _before_
fixing the real problem, you may find if very difficult to set back.
thing I have noticed and I relaise that it maybe the problem is that in
the monitor section of xorg config, it says that I have using a VESA
monitor. Now there is no T220HD in the list but it seems to be stck on
that.
Either boot into runlevel 3 directly, or after boot to X, instead of logging
in, switch to one of the virtual consoles, login as root, 'init 3', 'sax2',
and specify nv driver and a generic 1680x1050 22" display or some similar
Samsung LCD. Then 'init 5' and see if X got fixed. Normally VESA display
and/or gfxcard driver is for emergency use only on widescreen displays, and
won't be able to be configured for good results on a HDMI cable. You might
ultimately need the proprietary driver, but it's easier to try nv first if
right now you're stuck in VESA.
--
No Jesus - No peace , Know Jesus - Know Peace
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
| < Previous | Next > |