On 9/3/06, Khoa Ton <khoa@xxxxxxxxxxxxxxx> wrote:
Hi all, My ASUS M2NPV-VM motherboard with AMD Athlon X2 3800+ would not boot kernel 2.6.17-1.2471, whereas it booted 2.6.15-1.2054 fine. Brand new install from FC5 downloaded media for x86_64. Did a "yum update" to get the new kernel and the hang occurred. I just filed Bugzilla report against FC5 kernel: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=205090 Any information gathering method or workaround would be appreciated. Khoa Ton -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Hi Khoa Ton! Step one, hit escape during the boot process to get rid of the splash screen and see what is happening when the hang occurs. Write down what is on the screen when the hang occurs. Step two, when the hang occurs - wait for five minutes - then hit ctl+c. This may well "pop" you through the script which is having a problem and continue the boot. Step three, if through the boot (if not - get here with a live CD such as Puppy or KNOPPIX, or by booting rescue) migrate to /var/log and copy; bootstrap.log; daemon.log; dmesg; kern.log; messages; syslog; udev; Xorg.0.log, to a directory you have created in a flash drive (hopefully) or a floppy, or a CD if you have enough to write (the live CDs will probably do this fine) or at least to your Desktop directory on your hard drive. These logs (dmesg, messages, and syslog especially) contain valuable information, most likely, about what happened that caused the hang. Step four, get a cup of coffee or other favorite beverage and sit down and look through the logs. Think about where it crashed, and google the important things you now know. Hopefully you come up with a fix or two to try. If so or if not please type back to us at this point. Step five, if no solution yet get yourself a LCKD kit ( http://lkcd.sourceforge.net/ ), use it, and update your bug report with all the new information. Good hunting! Tod
