Description of problem: (don't know which component affected, sorry, maybe kernel) I see a circle when system boots, and when almost the entire circle is filled with white system freeze and CD disk spin down and stops. In Ubuntu I and others found the __same bug__ we can workaround it by adding "nolapic" option, but this is not a solution. In Ubuntu bug you can find full system information. If you need some additional, let me know. Version-Release number of selected component (if applicable): 12 beta LiveCD How reproducible: always Steps to Reproduce: 1. HP Compaq 615 notebook, disk with Fedora 12 beta LiveCD 2. start the second on the first =) Actual results: booting freeze Expected results: full system booting Additional info:
I see that this laptop has Radeon HD 3200 a.k.a. RS780. This could easily be KMS related. Can you retry with adding radeon.modeset=0 as a boot parameter?
Ok, I'll try it after work today.
Didn't work.
Press <Esc> when you see the circle and watch the messages while it's booting. You should at least be able to see where it stops.
(In reply to comment #4) > Press <Esc> when you see the circle and watch the messages while it's booting. > You should at least be able to see where it stops. It stops when udev starts and screen fade to black. Also I defined "radeon.modeset=0" and it said that it doesn't know this parameter.
hm, I've installed Fedora 11 (2.6.29 kernel) on my laptop and update it's kernel to 2.6.30.8 and all system too. Now it doesn't boot =) I'll re check it today.
hmm, I found a bug, which affects the Fedora 12 and my RS780
It is a good solution to switch off KMS for rs780 if possible and switch it on again when the problem will be fixed. (http://bugs.freedesktop.org/show_bug.cgi?id=24218)
System freezes (monitor become black) after udev starts (no "OK" status present in loading udev). It happening with and without "nomodeset" and radeon.modeset=0. I've deleted "quiet" option from kernel line, and left "rhgb".
I've tested with desktop-i386-20091107.20.iso nightly build with no success.
Updating summary per comments.
eem I've started this image with additional params "debug udevdebug nomodeset" and using webcam from another PC I got these lines before screen turns black: ... ... udevd-work[474]: M ATTRS match 'idVendor' '056a'(plain) udevd-work[469]: forward to rule:8172 udevd-work[474]:got 'idVendor' ((null)) from cache
Also, no luck with "selinux=0" boot parameter.
hm, interesting kernel bug report
Any chance it would be fixed before Fedora 12 release?
No, as final package set is already chosen. Likely will be fixed when Fedora picks up upstream fix.
So, I could not install the final release. Very sad.
Could it be an udev bug or not?
Try to boot disabling ACPI. It worked for me. acpi=off
Need Real Name, acpi=off is NOT a solution.
tested lxde-i386-20091126.17 (kernel 2.6.32, udev 147) with the same result. "Could not setup common clock" and then ... Starting udev: and then screen fade to black and CD spins down. I think it stops at lines like in Comment #12
I found that someone localised the problem. Yes it is not distribution specific. Here is the link http://bbs.archlinux.org/viewtopic.php?id=82052 quote some useful lines: "The only way to boot is to append acpi=off paramter. ______Problem is caused by pcmcia and pcmcia_core acpi modules(strange indeed that they are loaded,becouse my laptop has a express not pcmcia slot neutral)______ Boot with acpi=off and add these modules in rc.conf with ! to disable them from loading with system,boot again normally and everything will work fine now with acpi enabled I also notice that people with similar hardware like my netbook(AMD chipset)have same problems" I think now the fix will be trivial. Please squash this bug.
This regression starts with 2.6.30 kernel, with 2.6.29 al was fine.
It's indeed kernel bug, not acpid. acpid is a userspace daemon and has very little to do with problematic kernel modules here. Does 2.6.32-rc8 vanilla work better?
Don't know. Can't check. The only thing I definitely know is that Ubuntu 9.10, Fedora 11 (with .30 kernel), Fedora 12, Mandriva 2010 does not work. Ubuntu 9.04 (.28) and Fedora 11 with .29 works just fine. I'm on Ubuntu 9.04 now and all that I can check is ~kernel-ppa/mainline .32-rc8 kernel and any fedora rawhide(13) isos.
Created attachment 374629 [details] dmesg dmesg
Created attachment 374630 [details] messages messages
Created attachment 374631 [details] udev log udev log
These log files are from 2.6.32-020632rc8_2.6.32-020632rc8 kernel which I could boot on Ununtu 9.04! Don't know how "vanilla" it is but... I hope that this information help you in any way. It you need some other __please let me know__.
Created attachment 374636 [details] dmesg upload again with Content Type: text/plain
oops, sorry, these logs frm 2.6.28. 2.6.32-020632rc8_2.6.32-020632rc8 DOES NOT BOOT! :-(
hi all,i'm a debian user but i landed here to share bugs with you,i got a compaq 615 and i'm experiencing all the above listed problems,i recompiled a vanilla kernel without all the pcmcia modules,because they are not real dependencies of b43,now i can load the kernel(i recompiled it with the initrd)but nearly after "Version 2.86 loading..."it fails,there are trouble with b43/ssb and the acpi,in fact if i do a ssb.blacklist=1 it boot well but with no wireless :( .I am recompiling right now a new kernel without the initrd to prevent the ssb/b43 modules to be loaded in the first steps of booting,they should be loaded in a higher runlevel to avoid troubles.
Small copy/paste from : http://bugzilla.kernel.org/show_bug.cgi?id=14716 "@8disk, all those people which have trouble with the HP Compaq 615 and the developers of hp_wmi, the HP laptop WMI hotkeys driver. Excluding ssb from the initrd seems to be a neccessary prerequisite to let the HP Compaq 615 boot with the linux kernel 2.6.3[23]. But one should not forget to exclude hp_wmi (the HP laptop WMI hotkeys driver), too. The latter one puts the HP Compaq 615 into big trouble with all recent 2.6.33 kernels, Everybody can easily reproduce this by modprobing the hp_wmi driver after a (hopefully) successfull boot." "great,now i'm able to boot,i just blacklisted ssb only,not b43 and/or wmi as you have said above"
change external bugs in list.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.