Under SlackWare12.2 (and earlier) I had my screen configured to be
1268x1024 pixels and was shown a part of it. This smaller screen
could be enlarged (or reduced) by pressing <ctr><alt>+(-).
I used the enlarging quite often, because I could not see the
screen very well when it was too small.
Can the same be done in the new version and, if yes, how?

On Mon, 05 Oct 2009 15:52:07 -0400, Johannes Beekhuizen
jbeekhui at (no spam) duinheks.nl> wrote:

Under SlackWare12.2 (and earlier) I had my screen configured to be
1268x1024 pixels and was shown a part of it. This smaller screen
could be enlarged (or reduced) by pressing <ctr><alt>+(-).
I used the enlarging quite often, because I could not see the
screen very well when it was too small.
Can the same be done in the new version and, if yes, how?

What I think you were doing was changing the screen resolution, which is
not something you'll normally want to do. Instead, you should use
something like KMag to magnify the screen sections that you want to read.

Under SlackWare12.2 (and earlier) I had my screen configured to be
1268x1024 pixels and was shown a part of it. This smaller screen
could be enlarged (or reduced) by pressing <ctr><alt>+(-).
I used the enlarging quite often, because I could not see the
screen very well when it was too small.
Can the same be done in the new version and, if yes, how?
Thanks for any help,

Have you tried using /xorgsetup/? It scans your hardware and builds you

On Tue, 06 Oct 2009 11:26:09 +1100, Grant
g_r_a_n_t_ at (no spam) bugsplatter.id.au> wrote:

What I think you were doing was changing the screen resolution, which is
not something you'll normally want to do. Instead, you should use
something like KMag to magnify the screen sections that you want to read.

OP needs to add some extra resolution settings to xorg.conf.

That was another one I stumbled on. For some reason I couldn't get a
desktop with the stock nvidia driver.

I had to add screen subsections from an old xorg.conf file and
download the Nvidia driver and launch the binary installer.

After that all was well, sorta anyway.

What I think you were doing was changing the screen resolution, which is
not something you'll normally want to do. Instead, you should use
something like KMag to magnify the screen sections that you want to read.

OP needs to add some extra resolution settings to xorg.conf.

Have you tried using /xorgsetup/? It scans your hardware and builds you
an //etc/xorg.conf/ that will probably provide the best resolution your
hardware is capable of -- and it makes a back up file of your existing
//etc/xorg.conf/ file. Once done, you can use one of the magnification
utilities (say, /kmag/) if necessary.

In Slackware 13.0, you really don't need an /xorg.conf/ as the system
dynamically determines the settings for your monitor (and keyboard and
mouse) with /udev/; you can have an /xorg.conf/ if you want, but you
start out without one.

Hope this helps some.

On Fri, 09 Oct 2009 08:35:18 +1100, Grant
g_r_a_n_t_ at (no spam) bugsplatter.id.au> wrote:

So why not use konsole terminal? Just check the P4 box (it's running
fluxbox at the moment) Ctrl-Alt-F2 happily switched to TTY. I'm also
running the VESA framebuffer set to 800x600. Maybe some hints in my
.config? See: http://bugsplatter.id.au/kernel/boxen/black/ I'm using
linux-2.6.31.3 there today (on slack-13).

I mentioned in another post the odd thing is this only happens when I
start KDE. If I use XFCE no problems.

Once I exit KDE the only way I can get my TTY text back is to reboot
???

Still wish they had the Wacom drivers already installed
in the kernal usb section.

So why not use konsole terminal? Just check the P4 box (it's running
fluxbox at the moment) Ctrl-Alt-F2 happily switched to TTY. I'm also
running the VESA framebuffer set to 800x600. Maybe some hints in my
.config? See: http://bugsplatter.id.au/kernel/boxen/black/ I'm using
linux-2.6.31.3 there today (on slack-13).

Once I exit KDE the only way I can get my TTY text back is to reboot
???

The distro kernel doesn't get it right for some hardware. I duplicated
another poster's issues here with slack-13's distro kernel. I've not
explored whether playing with the /etc/rc.d/rc.modules can fix things
here.

Have you tried the Generic Kernel? I assume also that Lilo is set to use
the standard console, and not the ones with fancy framebuffer
resolutions?
And what driver are you using for X?

This is something really odd. Just to see what would happen I tried
using my xorg.conf file from 12.2.

The first time I used it and did a CTL-ALT-F2 I got text! I logged out
of KDE dropped to tty1 and had text.

I logged back in and got the same problem every since.

I have a bad feeling this is going to take a lot of time to track down
and fix. I appreciate the suggestions but for now I'm going to place
that problem on the back burner until I get more time as I'm terribly
busy now and am planning on going on vacation to see my Mom.

I have a bad feeling this is going to take a lot of time to track down
and fix.

This problem reminds me a lot of a problem I had on OpenBSD with one of my
older Macbook Pros. For some reason, framebuffers and such in the X and
TTYs would conflict with each other. I had to disable something in X to
get it to work. It is possible the KDE is enabling something that causes
this problem. That was such a long time ago, though, that I would be
surprised if this were the exact same error.

On Sun, 11 Oct 2009 18:03:49 -0400, Aaron W. Hsu wrote:

On Sun, 11 Oct 2009 18:49:15 -0400, Ron Gibson
rsgibson at (no spam) tampabay.rr.com> wrote:

What I've know at
this point is I have text until I get that odd "screen flicker" and
then I lose TTY text.

Try disabling the compositing, the compiz special niceties, and the
speciale effects that KDE does. That might remedy the problem. The
Screen Flicker I usually see happens on the Splash screen when KDE
switches from normal X to a sort of composited system that uses more of
the graphics card for OpenGL or some such.

For Ron or anyone else wondering how to disable compositing, I had this
stanza in my xorg.conf from Slack 12.2, which worked great:

Section "Extensions"
Option "Composite" "Disable"
EndSection

I simply added that to the very end of the xorg.conf file. I don't seem
to need it with the new X in Slack 13.

Like I said I really have to rule out that it's only a KDE problem
because if it happens in XFCE then it must be an issue with X itself
or possibly the video driver.