make dep
make bzlilo
make modules
make modules_install
mk_initrd
depmod -a
You do need to install the newer ver of modutiles of course
Regards,
Jon
Jon R. Doyle
Sendmail Inc.
6425 Christie Ave
Emeryville, Ca. 94608
(o_
(o_ (o_ //\
(/)_ (\)_ V_/_
On Fri, 31 Jan 2003, Geyer, Thomas L. wrote:
> Mark,
>
> No I did not...
>
> Thomas L. Geyer
> Email:[EMAIL PROTECTED]
> Phone:(330) 471-2073
> Fax:(330) 471-4034
>
>
> -----Original Message-----
> From: Post, Mark K [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 30, 2003 3:01 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Network Problems with new kernel....
>
>
> Tom,
>
> Did you upgrade your modutils package also?
>
> Mark Post
>
> -----Original Message-----
> From: Geyer, Thomas L. [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 30, 2003 2:54 PM
> To: [EMAIL PROTECTED]
> Subject: Network Problems with new kernel....
>
>
> 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
> Setting up network device eth0:
> modprobe: modprobe: Can't locate module eth0
> SIOCSIFADDR: No such device
> modprobe: modprobe: Can't locate module eth0
> eth0: unknown interface: No such device
> modprobe: modprobe: Can't locate module eth0
> SIOCSIFBRDADDR: No such device
> modprobe: modprobe: Can't locate module eth0
> eth0: unknown interface: No such device
> modprobe: modprobe: Can't locate module eth0
> SIOCSIFNETMASK: No such device
> modprobe: modprobe: Can't locate module eth0
> SIOCSIFMTU: No such device
> modprobe: modprobe: Can't locate module eth0
> eth0: unknown interface: No such device
> 7 [80C [10D [1;31mfailed [m" 8
> Waiting 15s for qeth network device eth0................. 7
> [m" [m"Setting up routing (using /etc/route.conf)
> [1mError while excuting:
> /sbin/route add default gw 147.185.179.65 [m
> SIOCADDRT: Network is unreachable
> Setting up routing 7 [80C [10D [1;31mfailed [m" 8
> [m" [m"Starting RPC portmap daemon [80C [10D [1;32mdone [m"
> [m"Starting SSH daemon 7 [80C [10D [1;32mdone [m" 8
> [m"Starting syslog services [80C [10D [1;32mdone [m"
> [m" [m"Starting lpdIPv6 v0.8 for NET4.0
> IPv6 over IPv4 tunneling driver
> Jan 30 13:49:12 ctnhtx01 sshd[215]: error: Bind to port 22 on 0.0.0.0
> failed: Ad
> 7 [80C [10D [1;32mdone [m" 8
> [m" [m"Starting service at daemon: [80C [10D [1;32mdone [m"
> [m" [m"Initializing SMTP port. (sendmail) [80C [10D [1;32mdone [m"
> [m" [m" [m" [m" [m"
> Starting CRON daemon 7 [80C [10D [1;32mdone [m" 8
> [m" [m"Starting kernel based NFS serversvc: unknown version (3)
> [80C [10D [1;32mdone [m"
> [m"Starting Name Service Cache Daemon 7 [80C [10D [1;32mdone [m" 8
> [m"Starting inetd 7 [80C [10D [1;32mdone [m" 8
> [m" [m"Master Resource Control: runlevel 3 has been [80C [10D [1mreached
> [m"
>
> 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.
>
> I have compared the locations of qdio.o and qeth.o in the
> /lib/modules/2.4.19 tree with their locations in another Linux virtual
> machine which is running the 2.4.17 kernel. I move qdio.o and qeth.o to the
> same locations and I got the same errors.
>
> This error only occurs with the new kernel. If I boot with the old kernel
> the nework starts right up.
>
> Is there something I did wrong in the configuration of the new kernel? Where
> should qdio.o and qeth.o be in the /lib/modules/2.4.19 directory tree? What
> did I do wrong?
>
> Any help or insight will be greatly appreciated. Thanks in advance.
>
>
> Thomas L. Geyer
> Email:[EMAIL PROTECTED]
> Phone:(330) 471-2073
> Fax:(330) 471-4034
>
>
>
> **********************************************************************
> This message and any attachments are intended for the
> individual or entity named above. If you are not the intended
> recipient, please do not forward, copy, print, use or disclose this
> communication to others; also please notify the sender by
> replying to this message, and then delete it from your system.
>
> The Timken Company
> **********************************************************************
>
