[E3-hacking] Why won't my E3 boot?
dg at cowlark.com
Mon Sep 4 15:31:52 BST 2006
Jon Masters wrote:
> Well, if they're in the standard initcall table then the driver init
> functions are called in the order the drivers were built into the kernel
> - directory order during compile and subsequent built-in.o processing.
Any USB devices will only have their drivers inited after the USB bus
has been enumerated, which happens in the background. This means that
block devices frequently only show up *after* the kernel tries to mount
them, which is a pain. There is a kernel option to deal with this ---
rootdelay --- which causes the kernel to pause for the specified number
of seconds before mounting. You could try fiddling with that...
+- David Given --McQ-+ "You cannot truly appreciate _Atlas Shrugged_
| dg at cowlark.com | until you have read it in the original Klingon."
| (dg at tao-group.com) | --- Sea Wasp on r.a.sf.w
+- www.cowlark.com --+
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 254 bytes
Desc: OpenPGP digital signature
Url : http://www.earth.li/pipermail/e3-hacking/attachments/20060904/b0a3684f/signature.pgp
More information about the e3-hacking