Red Hat Bugzilla – Bug 500544
855GM: F11 LiveCD Preview doesn't start; Computer freezes on start
Last modified: 2013-01-10 00:13:13 EST
Toshiba Portége M100
Pentium M 1300 MHz RAM 1 Gb
BIOS v. 1.50
VGA compatible controller:
Intel Corporation 82852/855GM Integrated Graphics Device
After CD start the cursor is blinking in the upper left corner for about 1 min and than turns the Display black. The background light is off. The Caps-Lock does switch on and off.
hardware report and lspci -nn output
Created attachment 343720 [details]
Created attachment 343721 [details]
lspci -nn output
I wasn't able to log in with ssh to the computer with F11 Preview Live to copy the logs.
I'm not sure if it is important, but i have tried other distributions with current xorg (Ubuntu 9.04 - v.1.6 and Mandriva 2009.1 v.1.6.1). I have got the following results. Ubuntu starts X and works with "UXA", Mandriva can't start X and freeze. I installed Mandriva and copied the logs. These logs are enclosed.
Created attachment 343922 [details]
Logs: mandriva 2009.1 free
What happens if you pass 'nomodeset' on the kernel command line?
If i pass 'nomodeset' on the kernel command line, the line and text "Fedora 10.9" are seen. After the stripe and text turn white nothing happens. The Caps-Lock lamp
turn on and off, but i wasn't able to log in with ssh to the computer.
Try to add 'nomodeset' and remove the 'quiet' and 'rhgb' keywords from the command line. That should tell us in more detail what goes wrong. Thanks!
Vladi: Are you able to reproduce this failure with more current Live media? You can find updated live media available at http://alt.fedoraproject.org/pub/alt/stage/f11-rc0.1/Fedora-11-i686-Live/
This issue was discussed during the May 22 F11 Blocker Review meeting. This issue will remain on F11Live blocker list until either:
1) Additional feedback from the reporter helps identify root cause
2) Positive feedback from other users with the same graphics setup
The bug will be reviewed again on May 25.
Feedback from Kamin Horvath in the other 855 bug (490366):
"I've never had an issue with X starting up for me. And I've been using Fedora
11 since beta."
(In reply to comment #7)
> Try to add 'nomodeset' and remove the 'quiet' and 'rhgb' keywords from the
> command line. That should tell us in more detail what goes wrong. Thanks!
1. I have managed to log in to gnome with the preview-CD, the only problem was the failure in 50-udev-default.rules (which, as I understand, has been corrected). Booting process lasted 10 minutes.
(In reply to comment #8)
> Vladi: Are you able to reproduce this failure with more current Live media?
> You can find updated live media available at
2. The situation which I described above repeats with the new updated live media: I get only black screen and the computer freezes.
3. If I insert 'nomodeset' into the command line and remove 'rhgb' and 'quiet' keywords I could log in to gnome. Booting process was without problems described in N.1. I have collected logs from /ect. They are enclosed.
--> logs: 03-f11-rc01-livecd-nomodeset.zip
4. I have installed live-CD on the hard disk. The installation had some problems (bugs: 500808, 499544) but was succsessful. After the installation there was 'nomodeset' in the command line. The booting from the hdd with 'nomodeset' runs well. I can log in to gnome.
--> logs: 04-f11-rc01-hdd-nomodeset.zip
5. If I remove only 'nomodeset' from the command line, booting fails. The computer freezes. I have collected logs and the are enclosed.
--> logs: 05-f11-rc01-hdd-modeset.zip
6. I have changed xorg.conf and inserted Option "AccelMethod" "UXA". I have tried to reboot with these changes and collect logs. Booting failed and the logs are enclosed.
--> logs: 06-f11-rc01-hdd-UXA.zip
Created attachment 345224 [details]
Created attachment 345225 [details]
Created attachment 345226 [details]
Created attachment 345227 [details]
logs: 06-f11-rc01-hdd-UXA + xorg.conf
I must correct myself: I collected logs not from '/etc' but from /var/log. Sorry and thanks.
Adam reports that this isn't happening on other 855 users he actively got testing for, so this is a limited case. As such it will not be an F11 blocker.
Re: comment #14, there's nothing obvious in those logs. To be honest, it looks like the logs from the hanging boot never made it to the disk.
Perhaps /var/log/messages might contain something useful in that case?
can you please test with this koji build? it fixed similar issues with 865, and kristian believes they may well be the same issue.
actually, scratch that, please test with:
that's the build that we intend to use for final. please see if it resolves this problem.
(In reply to comment #22,21)
I have installed new kernel-18.104.22.168-167.fc11.
I removed the 'quiet' and 'rhgb' keywords from the
command line and booted the computer. I saw boot messages, the last I saw were
i915 0000:00:02.0: VGA-1: no EDID data
i2c-adapter i2c-1: unable to read EDID block
The the screen turned black but the lamp HDD was for the next 10-15 seconds on.
Then the computer doesn't react.
Using the rescue CD I have collected logs which are attached as well as the photos that I've made while booting (--> F11-22.214.171.124-167-LVDS-1-logs+fotos.tar.bz2).
I have also tried to start the computer with an external display plugged to it. Kernel command line was the same, the result was also the same, only the booting process was a bit longer. I could see the messages of the starting services like cron and atd. These were the last services which started after that no changes are seen on the screen. The other special thing about this try was that the messages were not on the whole screen, but in the upper left corner, approximately 1/16th of the screen (see 004-f11-ext-vga.png).
I have collected the logs and enclose them as well as the pictures of the second attempt (-->F11-126.96.36.199-167-VGA-1-log+fotos.tar.bz2).
Created attachment 345819 [details]
Created attachment 345820 [details]
so it's *different*, but it still doesn't work?
and it still works with nomodeset?
(In reply to comment #26)
Yes, it still works with nomodeset.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.