Bugzilla – Bug 144618
Unable to go to [CTRL][ALT][F1]
Last modified: 2006-02-07 01:36:43 UTC
After installing it is almost impossible to go to textmode with [CTRL][ALT][Fx]. Only fater going through [CTRL][ALT][F10] it is possible to go to F1. When I go back to F7, I first have to go to F10, before can go back to F1
Component: Basesystem?
works for me. hmm, which windowmanager are you using? update or fresh installation? special hardware? please check with xev if an event is generated for F1.
Created attachment 64589 [details] xev output Standard new installation with KDE No special hardware PS2 keyboard Happy Hacker. Attached the output of xev. All I did after lauchning was [CTRL][ALT][F1]. During the installation when YaST is still running, it is possible to go to [CTRL][ALT][F1] (or any other F1)
I have done a new installation with Gnome this time and got the same problem. After running `sax2 -b /usr/share/sax/profile/Matrox_Dualhead the problem seemed to be solved. Is there any sests or files I can add (even after a new installation) to see where the problem comes from in the first place?
Let's ask Marcus.
sorry I cannot reproduce this. - You are using a dualhead Matrox card which one G200 G450 G550... ? - During boot are there both display active displaying the same console information (cloned) ? - After the X-Server has been started using the command X what exactly happens if you switch to the console using Ctrl-Alt-F1 ? - If you exit the X-Server with Ctrl-Alt-BackSpace are both console screens valid and usable again ?
- I use Dualhead G550 connected with VGA to two AL2021 20" 1600x1200 ACER LCD screens. - I do not configure anything at startup as I can not launch sax with -b ... No configuration else then what Sax has done is been done. At that moment I have not even logged in yet. So only the main display is active. So to sum it up. I do a default installation, I get the reboot, then entering the password and so on. So I click on OK till I get the login screen for either KDE or Gnome, depending on what I have selected. Instead of loging in, I do a CTRL-ALT-F1 and nothing happens. My screen goes blank and then tells me there is no input. I can only do a CTRL-ALT-F7, run sax2 -b ... there and then it will work. As this seems to be a local problem, I will give feedback after trying with 10.1 Beta2 to see if the problem went away or is still there. The workaround at this moment is to configure inside the GUI first. If the problem persists within Beta2, I will also try and see what a basic installation (No GUI) gives as result.
Thanks for the explanation according to this I'm pretty sure you ran into the mga driver bug which destroys the text console. The only solution for this is to boot the system without framebuffer. At the boot prompt type vga=normal you will now have a 80x25 text console like in the good old days :-) Starting the X-Server shouldn't destroy that console and you should be able to switch back and forth with Ctrl-Alt-Fx
vga=normal at the bootprompt gave me the same problem. No text consoles.
Marcus: As you took care of this, I assign this bug to you ;)
yes I can reproduce this problem. I made a beta2 10.1 test installation with a G550 card and if you try to switch back to the console the card lost its VGA signal no matter whether framebuffer is active or not. I assume this is a mga driver problem
Marcus, does ' Option "nohal" ' help? I've updated the HAL library after SUSE 10.0.
yes this fixed the problem :-) The current workflow will not set Option "NoHal" no matter what kind of Matrox card is used. In other words we are using the hal lib whenever the driver activates it.
Ok. I'll attach a driver built with the old HALlib for testing.
*** Bug 144246 has been marked as a duplicate of this bug. ***
Created attachment 65878 [details] New mga driver built with old HALlib (4.1 instead of 4.2)
Thanks will test is now
rpm -Uhv /suse/ms/Documents/xorg-x11-driver-video-6.9.0-10.i586.rpm sax2 -r -a X -> Ctrl-Alt-F1 works again. It seems the old lib is better than the new one ? :-)
Yes, new xorg-x11-driver-video package submitted. Fixed for Beta4.
*** Bug 148125 has been marked as a duplicate of this bug. ***
Just as a cross-update from the duplicate bug 144246: I tried the 'Option "NoHal"' hint and it works fine on my G450. Will also retest as soon as Beta4 comes out.