[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#96237: boot-floopies problem

Doug Regehr <dhjregeh@uwaterloo.ca> writes:

> Immediately before the main menu appears, I see a whole bunch of
> messages that look like this:
> "modprob:  modprob:  Can't open dependencies file
> target/lib/modules/2.2.19pre17..."

Does the directory exist? 

AFter you install the kernel and modules, then /lib/modules/`uname -r`
becomes a symlink to /target/lib/modules/`uname -r`.  You can check in
tty2 if that got fudged.

Be sure your kernel and drivers disk are matching -- e.g., not from
different sets.

If you didn't mess up somehow, and the symlink is broken, then we have
a problem.  Try again from scratch, and see if it happens again.  If
so, give me 'ls -l' output in /lib/modules and /target/lib/modules, as
well as 'uname -r' output please.

> I'm trying to install over a network.  At the "Select Installation
> Medium" screen, my network card does not appear in the list.

Sure... you don't have a network yet.

> Recognizing that I probably need to set up PCMCIA first, I select
> "Configure PCMCIA support" from the main menu.

As documented, yes, no bug here...

> After answering all the
> questions, I receive the following error message:
> "An error encountered while trying to load and configure the PCMCIA
> modules"

> Very informative.

Look in your system logs, tty3, or /var/log/message.

Please RTFM before complaining about not being informative.  

> At this point I am thoroughly confused. 


> I select "Configure Device Driver Modules" from the main menu.
> After answering "yes" to the question, I receive the following error
> message:
> "Problem: No modules were found in /target/lib/modules/2.2.19pre17 that
> could be configured.  Please install the modules first."

See the problem above.

> I have some vague notion that the modprob errors I got at the beginning
> are somehow related to the absence of device driver modules on the root
> disk I downloaded.

Well, a possible symptom of the bad /lib/modules symlinks...

> I tried downloading the root disk again, but the same thing happened.
> I have read the installation manual, but I couldn't find the answer to
> my problem.

I'm sorry, but your bug report gives me the impression you have *not*
read the install manual, esp. the section on troubleshooing and where
to look for logs.

.....Adam Di Carlo....adam@onshore.com.....<URL:http://www.onshored.com/>

Reply to: