Bug 710289 - After updating no screen available
Summary: After updating no screen available
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-02 22:09 UTC by antonio montagnani
Modified: 2018-04-11 08:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-21 12:02:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description antonio montagnani 2011-06-02 22:09:13 UTC
Description of problem:
If I upgrade xorg-x11-server to latest update I get a blank screen at login

Version-Release number of selected component (if applicable):
 xorg-x11-server-Xorg-1.10.2-1.fc15.i686

How reproducible:
alwaay

Steps to Reproduce:
1.Just boot
2.
3.
  
Actual results:
No login screen

Expected results:
a standard screen

Additional info:

using an intel card
If I use nomodeset as boot option I can login, even if graphic is ugly

Comment 1 antonio montagnani 2011-06-03 06:49:47 UTC
using i915 as driver

Comment 2 antonio montagnani 2011-06-06 07:01:30 UTC
I made an update on another laptop using same i915 driver, but different chipset and everything went fine.

But this computer is using Intel GL960 chipset, while the problematic one is using GM965

Comment 3 Matěj Cepl 2011-06-06 15:35:21 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.


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