Geyer, Thomas L. writes:
> I am running SLES7 under zVM 4.3 using a Guest Lan. The current kernel is
> 2.4.7. I have built kermel 2.4.19, when I reboot with the new kernel I see
> the folloowing errors:
>
> Initializing random number generator 7 [80C [10D [1;32mdone
> [m"
> [m"
> modprobe: modprobe: Can't locate module eth0
modprobe looks for a module or alias called "eth0", looks up its
module dependencies and then tries to load it/them. Check whether
you have a line
alias eth0 qeth
in /etc/modules.conf or else modprobe won't even look for qeth.
Since you later say it works for an earlier kernel, I guess this isn't
then problem.
[...]
> When I logon onto the virtual machine through the TN3270, I see (using the
> lsmod command) that the qdio.o and qeth.o modules have not been loaded. I
> then use the insmod command to load qdio.o and qeth.o followed by ifconfig
> and route command to get the Linux virtual machine on the network.
If you are using insmod on qdio then qeth then you are resolving the
module dependencies yourself. I suspect if you tried "modprobe qeth"
(without loading qdio) then you might run into the same problem. The
table of module dependencies is per-kernel-version-tree. You'll need
to run a
depmod -a
to rebuild the dependencies for a new kernel. You may need to fiddle
with explicit options to depmod to ensure you build the dependencies
for the right kernel and put them in the right place. Look at the man
page for depmod for details. Often, distributions will run an
automatic depmod sometime during boot. This normally removes the need
to do a manual depmod but equally makes it easy to forget when one
*does* need to do one.
--Malcolm
--
Malcolm Beattie <[EMAIL PROTECTED]>
Linux Technical Consultant
IBM EMEA Enterprise Server Group...
...from home, speaking only for myself
