Bug 530692 - No Virtual Consoles after Installation
Summary: No Virtual Consoles after Installation
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-vesa
Version: 12
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-24 09:13 UTC by Qian Cai
Modified: 2018-04-11 08:27 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-04-24 00:46:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg (34.76 KB, text/plain)
2009-10-24 17:15 UTC, Qian Cai
no flags Details
messages (478.09 KB, text/plain)
2009-10-24 17:16 UTC, Qian Cai
no flags Details
dmesg with drm.debug=1 (37.47 KB, text/plain)
2009-10-24 17:25 UTC, Qian Cai
no flags Details
Xorg.0.log (49.72 KB, text/plain)
2009-10-24 17:26 UTC, Qian Cai
no flags Details

Description Qian Cai 2009-10-24 09:13:56 UTC
Description of problem:
After installed F12 Beta i386, there is no VC login prompt anymore after VC switch in runlevel 5.

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

How reproducible:


Steps to Reproduce:
1. install F12 Beta i386.
2. the system boots into runlevel 5.
3. once enter the X, switch VCs.
  
Actual results:
No login prompt in VCs.

Expected results:
Have login prompt in VCs

Additional info:
It was working in Alpha.

Comment 1 Qian Cai 2009-10-24 17:02:01 UTC
This looks like a kernel or/and X driver problem since it only happen with KMS enabled for Radeon XPRESS 200M graphic card. The software versions are,

kernel-2.6.31.5-96.fc12.x86_64
xorg-x11-drv-ati-6.13.0-0.4.20090908git651fe5a47.fc12.x86_64

The hardware is the same as in bug 521512.

Comment 2 Qian Cai 2009-10-24 17:06:48 UTC
Same for xorg-x11-drv-ati-6.13.0-0.7.20091006git457646d73.fc12.x86_64

Comment 3 Qian Cai 2009-10-24 17:13:58 UTC
It is basically black screens when switching VCs.

Comment 4 Qian Cai 2009-10-24 17:15:57 UTC
Created attachment 365960 [details]
dmesg

Comment 5 Qian Cai 2009-10-24 17:16:24 UTC
Created attachment 365961 [details]
messages

Comment 6 Qian Cai 2009-10-24 17:25:19 UTC
Created attachment 365962 [details]
dmesg with drm.debug=1

Comment 7 Qian Cai 2009-10-24 17:26:43 UTC
Created attachment 365963 [details]
Xorg.0.log

Comment 8 Qian Cai 2009-10-24 18:01:40 UTC
Remove it from the blocker list, since this was using the VESA driver from the installation using the basic video driver.

Comment 9 Matěj Cepl 2009-11-05 17:18:59 UTC
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages (at least F12Beta, but even better if the very latest versions).

Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]

Comment 10 Bug Zapper 2009-11-16 14:10:25 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 11 Qian Cai 2009-11-19 13:12:41 UTC
Same problem here.
xorg-x11-drv-vesa-2.2.1-1.fc12.x86_64

Comment 12 Adam Williamson 2010-04-16 21:13:47 UTC
Cai, can you clarify exactly what the situation is for F13, since you've marked this as an F13 blocker? are you still seeing the bug with a recent F13 build (Beta, nightly, or Test Day build)? What is the bug exactly? thanks.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 13 Adam Jackson 2010-04-20 15:11:47 UTC
Removing from F13Blocker as the report seems to be about F12.  Please re-add this bug to F13Blocker if you can reproduce it there too.

Comment 14 Lijian Xu 2010-04-21 05:37:51 UTC
Hi, I'm now testing this issue instead of Cai, and I found the problem has been resolved in F13. The login prompt is well displayed now, thanks.

Comment 15 Lijian Xu 2010-04-21 06:29:26 UTC
Sorry for a WRONG test above with ati driver.

The situation is all the same as Cai on an up-to-date F13 with vesa driver, and only occurs with KMS enabled.

Versions of components:
kernel-2.6.33.2-41.fc13(x86_64)
xorg-x11-server-Xorg-1.8.0-6.fc13(x86_64)
xorg-x11-drv-vesa-2.2.1-2.fc13(x86_64)

Comment 16 Adam Williamson 2010-04-21 16:43:09 UTC
Having KMS enabled for a native driver but using VESA is known to be a problematic configuration. If you use the VESA driver you should also specify 'nomodeset'. Again, the question is why not use the native driver with KMS enabled?



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 17 Qian Cai 2010-04-22 08:13:28 UTC
Adam, I am fine to close this bug given that Lijian indicated that KMS with the native driver was working correctly in F13. Thanks.

Comment 18 Adam Williamson 2010-04-24 00:46:11 UTC
okay. just to reiterate to make sure it's clear, if there is any existing problem with using the native driver with KMS on this machine, that's what we'd like to focus on. thanks!



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers


Note You need to log in before you can comment on or make changes to this bug.