Bug 5611 - I can't switch between X (xdm/kdm) and text console
Summary: I can't switch between X (xdm/kdm) and text console
Alias: None
Product: xorg
Classification: Unclassified
Component: App/xdm (show other bugs)
Version: 6.8.2
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact:
Depends on:
Reported: 2006-01-16 08:49 UTC by arek
Modified: 2007-02-22 14:27 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

xorg.conf (2.81 KB, text/plain)
2006-06-07 15:41 UTC, Roy Dragseth
no flags Details
the log (28.53 KB, text/plain)
2006-06-07 15:42 UTC, Roy Dragseth
no flags Details
a small prog to reset radeon videocards (821 bytes, text/plain)
2006-06-07 15:43 UTC, Roy Dragseth
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description arek 2006-01-16 08:49:28 UTC
I can't switch between X (7 ->) and text console (1-6) by using shortcut
Alt+Ctrl+Fnr (Alt+Ctrl+F1 for example) when xdm/kdm (login screen) is on the
Xconsole (7).
(I can't swich from kdm to text conslole and from text console to kdm.)
When another X environment works on Xconsole (kde for example) I can use this
shortcut for switching betwen X and text console.

Where is the problem, is it xorg or xdm/kdm problem?

I use kdm 3.4.3
Comment 1 Erik Andren 2006-04-20 05:29:19 UTC
Any improvements using a current version of xorg? Also please post your
xorg.conf and your xorg.log
Comment 2 Roy Dragseth 2006-06-07 15:39:35 UTC
Hi, I'm piggybacking on this one as I see similar behaviour.  I did submit 
this to the Fedora bugzilla, and they asked me to take my problem here 

Here is the text I submitted to the Fedora bugzilla, and some additional 
experiments I've done later.

Description of problem:
I have a 3 year old Sony Picturebook with a videocard detected as 

(--) RADEON(0): Chipset: "ATI Radeon Mobility M6 LY (AGP)" (ChipID = 0x4c59)

Up until FC3 everything was working fine, but with FC4 and upwards X freezes 
when switching to and from the text console, usually the first switch is OK, 
but a second one locks up the system.  (Yes, I should have reported this 
earlier, but until FC5 I found a workaround by using old xorg-x11 rpms)

I get nothing in the logs indicating any errors, the screen just goes dark and 
never recovers.

Version-Release number of selected component (if applicable):


The last working version I used was  in this rpm.


How reproducible:

Install basic FC5 with X11.

Steps to Reproduce:
1. boot to runlevel 3
2. run X as root
3. Ctrl-Alt-F1, Alt-F7, Ctrl-Alt-F1, Alt-F7.
Actual results:
Screen goes dark and system freezes.

Expected results:
X should come back again.

Additional info:

I just found that the vesa driver does not exhibit this problem, I just wanted 
to report it as I've seen others complaining about this when trying to work 
around a bug in FC5 when installing on Crusoe cpus (bug  186378).


After these tests I've discovered that one can make the text console 
functional again by running the program boot-radeon (see attached, not written 
by me) from another network login.  The graphical display comes back too but 
looks distorted, the mouse-cursor 'x' has changed to something like a big 
white vertical bar.

Also, I cannot run two X servers after one another: If booting up with the 
redhat graphical boot (rhgb), then the screen goes dark when it tries to fire 
up the login screen (kdm).

I've tried to turn off all hw-accelerations, but that doesn't help.

Attached you'll find xorg.conf and Xorg.0.log from these experiments.

As stated above, the last version not exhibiting this behavior was in the rpm 

Best regards,

Comment 3 Roy Dragseth 2006-06-07 15:41:50 UTC
Created attachment 5845 [details]
Comment 4 Roy Dragseth 2006-06-07 15:42:34 UTC
Created attachment 5846 [details]
the log
Comment 5 Roy Dragseth 2006-06-07 15:43:35 UTC
Created attachment 5847 [details]
a small prog to reset radeon videocards
Comment 6 Timo Jyrinki 2007-02-22 14:27:46 UTC
Marking broken (status null/blank) bugs in xorg with no activity in a long time as fixed. Please reopen if you think it's necessary, but first do a search if a similar bug report is already filed and in a NEW/ASSIGNED state. These bugs do not currently show in most search results as they do not have any status.

Sorry for this janitorial spam, you know where to send hate mails to when your inbox gets full of bugs you're subscribed to.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.