Re: More info on i386 install fails to load modules
At 22:19 +0100 2/16/00, Geert Stappers wrote:
Yes, it is a reply on my own mail.
>>> When using the resue.bin & root from a debian ftp mirror
>>> in the directory
>>> dists/potato/main/disks-i386/2.2.6-2000-02-07/disks-1.44
>>>
>>> I not able to load modules for a network card ( for network install )
>
>Symptoms are like bug #57700 ( they are Carbon Copied )
><57700symptom>
>However, when I selected "Configure
>Device Driver Modules" from the menu of choices, the system would return
>immediately, saying that was all done.
></57700symptom>
>
>>> on tty3 there is message like
>>> modconf: can't open for write /lib/modules/2.2.14/mod.conf
>>> (or something like that ( It was late last night ))
>>
>>Please try this again and see if you can send us the exact message. I can't
>>be sure what the problem is until I know what the error message is :-)
>>
>
>I did the test once again.
>
>When selecting "Configure Device Driver Modules" on tty3 appears
>
><tty3msg>
>Feb 16 20:01:55 (none) user.info dbootstrap[27]: depmod: Can't open
>/lib/modules/2.2.14/modules.dep for writing
></tty3msg>
>
>/lib/modules is a symbolic link to /target/lib/modules,
>but below /target there is NO directory lib
>( /target, which becomes "/", has a lost+found, root, etc & tmp dir. )
>
>And I found more info:
>On the menu console ( tty1 ) there is briefly the message
><tty1msg>
>/target/usr/sbin/modconf: not found
></tty1msg>
>
>( I was very hard to see the tty1message,
> even at 8MHz still needed about 6 times,
> using a monochrome monitor ( phosphorus ) made it easier 8^)
>
>The directory /target/usr/sbin was empty.
>Even didn't exist.
>
In an other attempt I noticed that there is
"Installation Kernel and Modules"
Selecting it, it asked for the drivers disks...
So the problem I reported was as user error.
Sorry
Groet Geert St
--------------
End of Message
Reply to: