(IIRC, the atapi_enabled thing will be on by default in a upcoming kernel version.) So hw-detect has all sorts of code to give the user control over what modules are loaded and with what parameters, and to pass those along to the installed system even, but this is all sidestepped by udev which just does whatever it feels like during boot. I don't know how we can possibly fix this. Somehow delay udev from running until hw-detect? (While still getting any necessary serial, mouse, keyboad, etc devices working?) Come up with some kind of udev rules hack to allow kernel parameters to be passed to modprobe? -- see shy jo
Attachment:
signature.asc
Description: Digital signature