Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: srushik on August 27, 2008, 09:17:04 PM
-
Running the current release of SME 7
During boot up, I receive these messages.
Welcome to SME Server
Press'I' to enter interactive startup
Setting clock (UTC): <time details> [ OK ]
Starting udev: [ OK ]
Initializing hardware... Storage Network Audio
The cursor hangs on this line and never progresses any farther. This is running on a Dell Dimension 2400 workstation.
What is the OS trying to do at this point. What could be causing it to hang?
-
Running the current release of SME 7
During boot up, I receive these messages.
Welcome to SME Server
Press'I' to enter interactive startup
Setting clock (UTC): <time details> [ OK ]
Starting udev: [ OK ]
Initializing hardware... Storage Network Audio
The cursor hangs on this line and never progresses any farther. This is running on a Dell Dimension 2400 workstation.
What is the OS trying to do at this point. What is could be causing it to hang?
I think your best bet for this is to try the bugtracker so the core devs can try and help you diagnose this.
-
Bugzilla does not consider it a bug, and closed it.
Does anyone know what is it trying to do at this point in the boot? Is there anyway to get around it?
-
Bugzilla does not consider it a bug, and closed it.
No, that is not correct. It is a bug, in either your hardware or the linux kernel. Unfortunately, the SME server development team is unable to fix either problem.
Does anyone know what is it trying to do at this point in the boot?
It's loading the kernel modules which have been identified as matching your various hardware. At the point you show, it is loading "other" drivers (the network and audio drivers have already been loaded). Here's the code which is running (from /etc/rc.sysinit):
echo -n $" network"
# Sound
for module in `/sbin/modprobe -c | awk '/^alias[[:space:]]+snd-card-[[:digit:]]+[[:sp
ace:]]/ { print $3 }'` $audio; do
load_module $module
done
echo -n $" audio"
# Everything else (duck and cover)
for module in $other ; do
load_module $module
done
echo -n $" done"
success
echo
Judging by the comment there, trouble sometimes happens at that point.
Is there anyway to get around it?
Gavin gave you one suggestion in the bug tracker. Google might suggest some others to you.
Booting with the "noapic" command argument sometimes helps with buggy drivers. Disabling or removing unneeded hardware can also help.
-
Thank you for getting me pointed in the right direction.
In the BIOS, I disabled "Legacy USB Support"
That solved this issue. It totally boots normally now.
-
Disabling USB in Bios works also for me. Thanks
-
Hey guys just a heads up and thank you for the solution- been trying to resolve this for a while- disabled legacy USB and booted fine.