* Gaudenz Steinlin (gaudenz@soziologie.ch) wrote: > Am Don, den 22.01.2004 schrieb Stephen Frost um 03:35: > > * Gaudenz Steinlin (gaudenz@soziologie.ch) wrote: > > > This looks like discover is hanging when detecting the hardware not when > > > loading modules. > > > > Yup, looks like that's it somehow, if not earlier... > > > > > The "all" does not mean all modules but all types of devices. You can > > > modify /etc/discover.conf to see which type of device causes it to hang. > > > > Looks like any of them cause it. I tried a number of combinations and > > basically, inside the /target chroot, discover --module blah hangs. > > discover --module all on the main system works just fine. I tried > > copying the modules from /lib/modules into the chroot, but that didn't > > change anything. > Hm, running "discover --module all" on the installed system works fine, > but you experience a hang during the discover startup script? If this is > the case, then there might be two independent problems. > For the /target chroot I suspect the problem might be that there is no > /proc. Please try to mount a proc filesystem at /target/proc. But then I > don't understand why only you have this problem and it does not occur on > every machine. Err, sorry, maybe I wasn't clear, I havn't actually tried running discover --module all on the *installed* and booted system (yet, I can do that tonight). I suspect it will actually have problems. Running discover --module all works fine from the install CD when *not* in the /target chroot from same. I think discover --module all actually does hang on the booted system since the startup scripts hang at some point and I have to ctrl-c them to get the system to finish booting. I can try it manually tonight, as mentioned, though. I'll try mounting /proc at /target/proc and see what happens. I really hope that helps. :) Stephen
Attachment:
signature.asc
Description: Digital signature