Red Hat Bugzilla – Bug 212172
FC6 boot fails on ASUS M2NPV-VM motherboard
Last modified: 2015-01-04 17:29:14 EST
Description of problem: FC-6-x86_64 DVD fails to boot on motherboard ASUS M2NPV-VM. It hangs at: io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Insert FC6 install DVD and boot 2. Press "enter" at install type prompt 3. It hangs Actual results: hangs Expected results: Install Fedora Core 6 Additional info: Problem looks to be the same as Bugs 205090 and 205650.
I encountered the same problem with motherboard ASUS A8M2N-LA. The system boots up with kernel parameter acpi=off. There is also a problem with usb devices. When the system is up I can't use my usb cordless Logitech mouse. I tried different kernel parameters without success, noapci nofb and pci=biosirq. Attached is the /var/log/messages and the last dmesg.
Created attachment 139393 [details] /var/log/messages
Created attachment 139394 [details] /var/log/dmesg
Here is the message that installation is working with new version (0504) of BIOS for Asus M2NPV-VM: http://forums.fedoraforum.org/showpost.php?p=657838&postcount=11. Am going to check it tomorrow.
I have flashed my M2NPV-VM with BIOS 0504. After this FC-6-x86_64 installation have started successfully without any additional parameters. I have only one doubt at present moment: I am afraid that the same bug may appear after next BIOS or Kernel update. Could somebody from Kernel team give any suggestions for future?
Lucky you... Sad that there is no new bios for the ASUS A8M2N-LA, because this is a mainboard produced for HP Pavillon t3551.de PC and I have the latest bios provided by HP :-(
Same thing on my HP Pavilion a1410n w/ A8N-LA motherboard :(
What's the last few lines that gets printed when you boot with initcall_debug (remove the 'quiet' from the boot command line)
Dave, who have to answer your question? I have FC6 working now, so I suppose that Michael or David have to answer on it. Is it right?
The last three lines are: io scheduler cfq registered (default) Calling initcall 0xffffffff80659588: blk_traceinit+0x0/0xc9() Calling initcall 0xffffffff80344873: pci_init+0x0/0x2b()
I noticed you may not have DMA on your DVD drive. You may have to add kernel arguement like noprobe NFORCE-MCP51: 0000:00:0d.0 (rev a1) UDMA133 controller ide0: BM-DMA at 0xf400-0xf407, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xf408-0xf40f, BIOS settings: hdc:DMA, hdd:DMA Probing IDE interface ide0... Probing IDE interface ide1... hdc: TSSTcorpCD/DVDW TS-H652L, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 Probing IDE interface ide0...
With my ASUS A8M2N-LA, I found that the root cause of the Probing idc0 freeze was related to this earlier error message, MP-BIOS bug: 8254 timer not connected to IO-APIC. This is with kernel 2-6.18, FC6. The workaround is using kernel parameter no_timer_check. Apparently, this is solved in 2-6.19, but I have not checked.
Thanks, this kernel option works fine for me :-)
Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.