Summary: | Black screen on Iiyama Vision Master 450 | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Jeremy Henty <onepoint> | ||||||||||||
Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||||||||||
Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||||
Severity: | normal | ||||||||||||||
Priority: | medium | ||||||||||||||
Version: | unspecified | ||||||||||||||
Hardware: | Other | ||||||||||||||
OS: | All | ||||||||||||||
Whiteboard: | |||||||||||||||
i915 platform: | i915 features: | ||||||||||||||
Attachments: |
|
Description
Jeremy Henty
2009-04-21 05:09:36 UTC
Created attachment 24994 [details]
Default xorg.conf that displays the bug
This is a copy of the default xorg.conf created by "Xorg -configure".
It reproduces the bug as described.
Created attachment 24995 [details]
Server log from a buggy X session.
This the server log using the previous xorg.conf and running "X -config <conf>".
The screen goes blank. I recovered with Alt-SysRq-r , Ctrl-Alt-F1 , Ctrl-C .
Created attachment 24996 [details]
Server log from buggy session.
Oops, I resubmitted the xorg.conf last time. *This* is the server log.
Created attachment 24997 [details]
Fixed xorg.conf .
This is a new xorg.conf, same as the old one except for adding Modes lines as described in the bug description.
With this configuration the server displays the background and cursor as you would expect.
Created attachment 24998 [details]
Server log of fixed session
This is the log of a successful session using the fixed xorg.conf submitted above.
The session was started and stopped exactly as before, only the config file is different.
The diff of the logs is very small.
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases. |
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.