Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi,
I'm in the process of upgrading from RH7.3 to RH9
Everything seemed to be going fine, until it was time to boot from the HD.
It hangs at
Initializing USB controller (usb-unci):
I've searched for causes and it may be I need to check the /etc/modprobe.conf, or other files. But how do I bypass the check so it will boot?
When hung, if I hit Ctrl-C, it goes into
INIT: Entering runlevel:5
then reports
Checking for new hardware/etc/rc5.d/S05kudzo: line 46: /usr/sbin/kudzu: No such file or directory [FAILED]
Updating /etc/fstab execvp: No such file or directory [FAILED]
then hangs again on
Bringing up loopback interface:
There might have been errors earlier (before the INIT: version 2.84 booting etc but it's scrolled off the screen). So, same question, how can I see the boot log if I can't boot?
Also, I do have a boot disktette (created from the RH9 upgrade CD procedures). When I boot from it, it gets so far and then
boot:
Loading
Boot failed: please change disks and press a key to continue.
Maybe you could try the kernel parameter "nousb"? If you need to change configuration files, you could try a live-cd like knoppix to get a working environment.
Hope that helps.
Sounds like something is pretty badly b0rked if it's hanging on bringing up the loopback interface. Try booting into single user mode (append the word single to the kernel command line, just as you did with nousb) and trying to see what has gone wrong. Hopefully dmesg and/or the system logs should give you some ideas.
well, looking at dmesg
it appears the first sign of trouble comes much earlier, in PCI checks as follows (pardon the typos, I'm transcribing)
(booting with "nousb noprobe text single")
PCI: PCI BIOS revision 2.10 entry at 0xfdb81, last bus=2
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Cannot allocate resource region 0 of device 00:12.0
PCI: Cannot allocate resource region 1 of device 00:12.0
PCI: Cannot allocate resource region 0 of device 00:12.1
PCI: Cannot allocate resource region 1 of device 00:12.1
Limiting direct PCI/PCI transfers.
then later after the file systems are mounted
PCI: Enabling device 00:12.1 (0000 -> 0003)
PCI: No IRQ known for interrupt pin B of deviced 00:12.1. Please try using pci=biosirq.
Unable to handle kernel NULL pointer dereference at virtual address 00000000
printing eio:
c01d3dbe
*pde = 00000000
Oops: 0002
and then a bunch of values that includes a dump of registers and a stack and call trace on a pci_driver... ?
I don't even know if this is related to the other issues
perhaps I should just backup and install a clean install of RH9 (this was an upgrade from 7.3)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.