Good day,

I'm having a problem with my tty1 through tty6. When I start up my computer, which is running slackware64 14.0, I see the boot message and am brought to the first login terminal. I login and run startx as normal and am brought to my favorite eyecandy. The problem arises when I go to use a tty terminal again (any of tty1 through tty6). The boot message is written over the console buffer, and pressing and holding enter causes the screen to flicker between the proper tty buffer and the imposing one.

It is a rather fresh install having just organized, and revamped, my system. I installed a video card driver (fglrx - for ATI card) and some packages from slackbuilds, but nothing I didn't have before. I used the same data to install slackware64 on a laptop computer making sure the error wasn't due to bad data.

Note that it is only after I run startx and use ctrl-alt-f1 to return to tty1 that I find this problem.

Can anyone help me return my system to its proper order? Much thanks in advance for all help!

Update: so far I think it is a frame buffer issue with switching to the driver in my xorg.conf after startx (fglrx).

When you run 'startx' you are still logged in in tty1, so what you see is not bootmessages but messages from your X-session. This is not so good for security reasons. If someone is near your computer when you don't see it, they can press ctrl+c in tty1 and cancel your x-session, and still be logged in as you.

What you can do is either start X automatically when you login in tty1 (the other ttys won't be affected), by adding this to your ~/.bash_profile:
That will start your X-session in tty1.

If you dont want to start X automatically you can create an alias for it. You can get some more ideas here.

1 members found this post helpful.

Hi Lennie,

I tried your suggestion and also the ones in your link and I still have the same problem. All the tty's get covered in junk script when startx is run no matter how I do it. Could this be to do with the graphics card driver? Maybe it's starting with VESA and switching to fglrx after startx leaving some sort of buffer from VESA still being used on the same display?

A shot in the dark (I agree that it's probably a framebuffer issue, but that kind of fix is beyond my scope...), if you login and startx via a tty other than tty1, do you get the same issue?

On a somewhat-related note, if you're interested in starting an x session automatically from runlevel 3, see this thread:

http://www.linuxquestions.org/questi...ut-gui-374338/

cheers,

Running startx on any of the tty's results in the same thing. I agree it is likely a frame buffer issue that is beyond me at the moment. Do we know how the system switches from the driver used to start up the machine to the one used in xorg.conf?