Bug 530692
| Summary: | No Virtual Consoles after Installation | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Qian Cai <qcai> | ||||||||||
| Component: | xorg-x11-drv-vesa | Assignee: | Adam Jackson <ajax> | ||||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | high | Docs Contact: | |||||||||||
| Priority: | high | ||||||||||||
| Version: | 12 | CC: | awilliam, lxu, mcepl, notting, plautrba, xgl-maint | ||||||||||
| Target Milestone: | --- | Keywords: | Triaged | ||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | All | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2010-04-24 00:46:11 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Qian Cai
2009-10-24 09:13:56 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. Same for xorg-x11-drv-ati-6.13.0-0.7.20091006git457646d73.fc12.x86_64 It is basically black screens when switching VCs. Created attachment 365960 [details]
dmesg
Created attachment 365961 [details]
messages
Created attachment 365962 [details]
dmesg with drm.debug=1
Created attachment 365963 [details]
Xorg.0.log
Remove it from the blocker list, since this was using the VESA driver from the installation using the basic video driver. 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.] 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 Same problem here. xorg-x11-drv-vesa-2.2.1-1.fc12.x86_64 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 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. 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. 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) 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 Adam, I am fine to close this bug given that Lijian indicated that KMS with the native driver was working correctly in F13. Thanks. 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 |