Bug 688686 - [PALM] F15 Alpha install: default boot option results in unusable display
Summary: [PALM] F15 Alpha install: default boot option results in unusable display
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 15
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Jérôme Glisse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-17 17:56 UTC by ben
Modified: 2018-04-11 12:04 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-29 18:49:43 UTC
Type: ---


Attachments (Terms of Use)
xorg.conf (67 bytes, text/plain)
2011-03-17 23:11 UTC, ben
no flags Details
xorg log (83.16 KB, text/plain)
2011-03-17 23:12 UTC, ben
no flags Details
dmesg (70.41 KB, text/plain)
2011-03-17 23:12 UTC, ben
no flags Details
messages (4.65 MB, text/plain)
2011-03-17 23:13 UTC, ben
no flags Details

Description ben 2011-03-17 17:56:01 UTC
Description of problem:
When booting up the install image and selecting the default option in the grub menu, I get a flickering gray screen which flashes pink occasionally. Choosing the basic video option gets me to the installer. 
I'm using the install iso located here: http://download.fedoraproject.org/pub/fedora/linux/releases/test/15-Alpha/Fedora/x86_64/iso/Fedora-15-Alpha-x86_64-DVD.iso
Computer is a Thinkpad x120e with AMD e-350 APU. I'm booting in 'legacy' mode as opposed to UEFI mode, because UEFI mode fails.

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


How reproducible:
Every time.

Steps to Reproduce:
1. Boot install image
2. Select default grub option
3.
  
Actual results:
Unusable display

Expected results:
Usable display, access to anaconda

Additional info:
See bug #683693 for details on my problems with UEFI boot on this hardware.

Comment 1 ben 2011-03-17 19:36:22 UTC
On a related note, after the install is completed, I can successfully switch to the ati driver and run glxgears, but I cannot run gnome-shell. I get the error:
"failed to create drawable

(gnome-shell:1815): Clutter-CRITICAL **: Unable to initialize Clutter: Unable to select the newly created GLX context
Window manager error: Unable to initialize Clutter."

I'm not sure if this is the same problem or a different problem.

Comment 2 Matěj Cepl 2011-03-17 22:43:31 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.

Comment 3 ben 2011-03-17 23:11:37 UTC
Created attachment 486116 [details]
xorg.conf

Comment 4 ben 2011-03-17 23:12:06 UTC
Created attachment 486117 [details]
xorg log

Comment 5 ben 2011-03-17 23:12:45 UTC
Created attachment 486118 [details]
dmesg

Comment 6 ben 2011-03-17 23:13:37 UTC
Created attachment 486119 [details]
messages

Comment 7 ben 2011-03-17 23:31:40 UTC
Note: xorg.conf was initially set to use the vesa driver.

Comment 8 Dave Airlie 2011-03-19 08:12:29 UTC
try removing the nomodeset from the kernel command line.

Comment 9 ben 2011-03-19 16:49:01 UTC
(In reply to comment #8)
> try removing the nomodeset from the kernel command line.

Removing the nomodeset option fixes the post-install issue of not being able to start gnome-shell. :)

Comment 10 Jérôme Glisse 2011-03-29 18:49:43 UTC
ok closing we don't support ums


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