I cannot use the various quot;command-bashquot;, (tty1-tty6)

amy

Sorry if my title is not self-explainable.

I cannot see the tty 2. (The Framebuffer console mode)

I just press Ctrl+Alt+F2 and it does not appear.
Only appears a screen with quot;scratchesquot; (a broken image).

After that, if I press Ctrl+Alt+F7 it gets back to my usual workspace.

And when I shutdown, or hibernate, the screen becomes the wallpaper but with quot;bugsquot; (the same broken image)

When I had Edgy-Eft, it worked perfectly.

I am working on a Feisty Fawn, generic kernel (vmlinuz-2.6.20-16-generic).
I am using beryl, nvidia graphics driver
My username is quot;quakequot;:

quake@quake:~$ glxheads
glxheads: exercise multiple GLX connections (any key = exit)
Usage: glxheads xdisplayname ...
Example: glxheads :0 mars:0 venus:1
Name: :0 Display:     0x805e380 Window:      0x4000002 Context:     0x8079050 GL_VERSION:  2.1.0 NVIDIA 97.55 GL_VENDOR:   NVIDIA Corporation GL_RENDERER: GeForce Go 6800/PCI/SSE2

I am running with the resolution: 1440x900 (widescreen) 60Hz

What do I need to do to make the terminals work?

I would apreciate some help.
Thanks.

Hi Qu4k3r,

I share your problem, although I've got an ATI Radeon Mobility X700 card.
Hopefully some friendly soul here will come to our aid.

Here's what I had to do to get it to work.
Try forcing 1024x768 resolution on the TTY:

Code:
gksudo gedit /boot/grub/menu.lst
Add quot;vga=791quot; to the defoptions line as such:

Code:
# defoptions=quiet splash vga=791
Also add it to the kernel line, then reboot:

Code:
kernel  /boot/vmlinuz-2.6.some_long_name ro quiet splash vga=791
Undo these steps if it doesn't work.

This is my menu.lst file (I removed commented text and other options like default, colors, splashimage) :

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
defoptions=quiet nosplash vga=791

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
##      altoptions=(recovery) single
# altoptions=(recovery mode) single

title Linux - Feisty Fawn
root(hd0,1)
kernel/boot/vmlinuz-2.6.20-16-generic root=UUID=49e9547a-7ace-4207-8656-34229051bd8e ro quiet nosplash vga=791
initrd/boot/initrd.ing-2.6.20-16-generic
quiet
savedefault

I think that is not the resolution.
Thank you anyway, testube_babies.EDIT:

I am using AIGLX drivers.

Unfortunately, the advice didn't help me either.

I'm using the open source quot;radeonquot; driver with AIGLX. If I change to tty[1-6], the screen only show a broken image as described in the first post. The image is still broken when I return to the x-session, but I can get it back if I close and reopen the laptop lid.

I don't experience the same problem when I use the 'fglrx' driver without any extras, so maybe the   problem has to do with AIGLX.  But if it stands between the virtual consoles and beryl, I choose the latter.

I've searched around for help but all I can find are advices like testube_babies'. Perhaps the problem will vanish when Gutsy arrives.

@Qu4k3R:

I think you should have left the defoptions line commented.
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

It won't make testube_babies' advice work, but you should perhaps put the # back.

I had already commented the option. Thank you.

I am looking for even more info about this error.
I see only people who adds quot;vga=791quot; to menu.lst and then

sudo update-grub

I have tried it. It does not work either.PS:

I'll try this:
from : localhost/en.wikipedia.org/wiki/VESA_BI...o_mode_numbers

I'll try to change from 791 to another corresponding to VESA framebuffer :s
Let's see if I got those terminals working. (I'll post something)EDIT:
Does not work


Originally Posted by mali2297Unfortunately, the advice didn't help me either.

I'm using the open source quot;radeonquot; driver with AIGLX. If I change to tty[1-6], the screen only show a broken image as described in the first post. The image is still broken when I return to the x-session, but I can get it back if I close and reopen the laptop lid.

I don't experience the same problem when I use the 'fglrx' driver without any extras, so maybe the   problem has to do with AIGLX.  But if it stands between the virtual consoles and beryl, I choose the latter.

I've searched around for help but all I can find are advices like testube_babies'. Perhaps the problem will vanish when Gutsy arrives.

When you start your computer, even before login in (I mean, before the session starts up) I cannot use the command lines, and I think that beryl hasn't started up yet.

A funny thing:
I installed warsow

I was changing the graphics and the game has frozen up. The screen appeared with only one colour: white.
After this, (the screen does not change) I could change from tty7 to anothers and login to killall warsow
funny.

I changed the opengl mode and the screen depth (16 bits).
The bug seems to be not in beryl..

I don't quite understand,  did you manage to permanently get tty[1-6] available? If so, what exactly did you do?

Since we use different graphics cards and drivers but have AIGLX in common, that made me suspect that the bug somehow is connected to AIGLX.  As I mentioned earlier, if I install the 'fglrx' driver (which is not compatible with AIGLX) and restart X, then I can use tty[1-6].

There is also the possibility that, although the symptom is the same, the cause to our problem is not.

I was trying to say that beryl was not the source of the bug.
Before I start the session, beryl hasn't started yet. But I cannot access those terminals.

I don't understand why I could access those terminals after the Warsaw quot;leakquot;.

But after I restart the computer, I could not access the terminals again.
So it was only quot;accidentalquot; but it worked just perfectly.
I have the bug again. (I don't want to use warsaw to get my terminals avaiable everytime I need them )

BTW:
What are the quot;majorquot; differences between AIGLX and FGLRX drivers?