Results 1 to 5 of 5
Hello,
While booting my fedora15, it gets stuck for about 5-6 minutes. Previously there was no problem. I don't know what made this problem. After going through the boot process, ...
- 06-06-2011 #1Just Joined!
- Join Date
- Mar 2010
- Posts
- 15
pauses during boot, fedora15
Hello,
While booting my fedora15, it gets stuck for about 5-6 minutes. Previously there was no problem. I don't know what made this problem. After going through the boot process, error occurred during network process. Using following command I got the result.
Also right after the long pause following messages are printedCode:# systemctl status network.service network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network) Active: failed since Sun, 05 Jun 2011 21:13:55 +0545; 11h ago Process: 845 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/network.service
I noted it down as soon as I saw the message after that long pause.Code:261.742053 usb4-1: device not accepting address 4 error -7 261.794087 hub4-0.1.0: unable to enumerate usb device on ports
Hope this provided information could getting through the problem. If more information is needed, I'm happy to provide
Regards
- 06-06-2011 #2Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 8,974
Have you tried disconnecting any USB devices before you boot? I know that I have a similar problem with RHEL if my Android cell phone is connected to the system when I boot.
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!
- 06-06-2011 #3Just Joined!
- Join Date
- Mar 2010
- Posts
- 15
I have no USB devices connected.
- 06-07-2011 #4
- 06-07-2011 #5Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 8,974
Thinking some more...
My laptop's bluetooth wireless is USB connected, even though it is internal to the system. It may be that there is either a problem with your USB controller, or an internal device that is connected to it.Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!


Reply With Quote
