Very Computer

by **A J Kenned** » Sat, 28 Apr 2001 14:13:51

Hi,

I have recently upgraded my kernel from 2.2.12-20 to 2.2.19 & overall it is finding the new one ok. My machine is a Redhat 6.1 machine

Apr 25 01:17:31 echelon kernel: klogd 1.3-3, log source = /proc/kmsg started.
Apr 25 01:17:31 echelon kernel: Inspecting /boot/System.map-2.2.19
Apr 25 01:17:31 echelon kernel: Loaded 7545 symbols from /boot/System.map-2.2.19.
Apr 25 01:17:31 echelon kernel: Symbols match kernel version 2.2.19.
Apr 25 01:17:31 echelon kernel: Loaded 17 symbols from 2 modules.

Seems to be having problems with some modules as shown below though
Also i seem to has lost my internal connection to the gateway machine from my LAN. (Fails to bring up eth0) & so no ipmasquading ??
Any ideas what the ^[[60G means when starting sshd ??

Apr 25 22:56:20 echelon rc.sysinit: Setting up ISA PNP devices succeeded
Apr 25 22:56:20 echelon rc.sysinit: Remounting root filesystem in read-write mode succeeded
Apr 25 22:56:21 echelon rc.sysinit: Finding module dependencies succeeded
Apr 25 22:56:21 echelon modprobe: modprobe: Can't locate module sb
Apr 25 22:56:21 echelon rc.sysinit: Loading sound module (sb) failed
Apr 25 22:56:21 echelon modprobe: modprobe: Can't locate module opl3
Apr 25 22:56:21 echelon rc.sysinit: Loading midi module (opl3) failed
Apr 25 22:56:34 echelon sysctl: net.ipv4.ip_forward = 0
Apr 25 22:56:34 echelon sysctl: net.ipv4.conf.all.rp_filter = 1
Apr 25 22:56:34 echelon sysctl: net.ipv4.ip_always_defrag = 0
Apr 25 22:56:34 echelon sysctl: net.ipv4.ip_forward = 1
Apr 25 22:56:34 echelon sysctl: error: 'kernel.sysrq' is an unknown key
Apr 25 22:56:34 echelon network: Setting network parameters succeeded
Apr 25 22:56:34 echelon network: Bringing up interface lo succeeded
Apr 25 22:56:34 echelon ifup: Delaying eth0 initialization.
Apr 25 22:56:34 echelon network: Bringing up interface eth0 failed
Apr 25 22:56:34 echelon portmap: /etc/rc.d/rc3.d/S11portmap: /etc/rc.d/rc3.d/S11portmap: cannot execute binary file
Apr 25 22:56:34 echelon rc: Starting portmap failed
Apr 25 22:56:43 echelon sshd: Starting sshd:
Apr 25 22:56:43 echelon sshd: sshd startup succeeded
Apr 25 22:56:43 echelon sshd: ^[[60G
Apr 25 22:56:43 echelon sshd:
Apr 26 11:36:52 echelon modprobe: modprobe: Can't locate module char-major-108
Apr 26 11:50:24 echelon modprobe: modprobe: Can't locate module sound-slot-0
Apr 26 11:50:24 echelon modprobe: modprobe: Can't locate module sound-service-0-3
Apr 26 13:43:04 echelon snort[10643]: pcap_loop: read: Network is down
Apr 26 13:43:05 echelon pppd[12370]: Can't execute /etc/ppp/ip-down: Exec format error

Once you upgrade a new kernel can you simply do another make menuconfig to go through your options again.?

One of the bad things that happened when i was doing this upgrade was put the tarred file in my /usr/src/ directory . This is what a help page told me to do. Problem was though that when i untarred the kernel it overwrote my linux folder that was already in there. %^%$##.

What do you think ?? What do you suggest
Regards...

Andrew

by **Dean Thompso** » Sat, 28 Apr 2001 21:58:47

Hi Andrew,

Quote:> I have recently upgraded my kernel from 2.2.12-20 to 2.2.19 & overall it
> is finding the new one ok. My machine is a Redhat 6.1 machine

[...]

Quote:> Seems to be having problems with some modules as shown below though
> Also i seem to has lost my internal connection to the gateway machine from
> my LAN. (Fails to bring up eth0) & so no ipmasquading ??
> Any ideas what the ^[[60G means when starting sshd ??

> Apr 25 22:56:20 echelon rc.sysinit: Setting up ISA PNP devices succeeded
> Apr 25 22:56:20 echelon rc.sysinit: Remounting root filesystem in
> read-write mode succeeded
> Apr 25 22:56:21 echelon rc.sysinit: Finding module dependencies succeeded
> Apr 25 22:56:21 echelon modprobe: modprobe: Can't locate module sb
> Apr 25 22:56:21 echelon rc.sysinit: Loading sound module (sb) failed
> Apr 25 22:56:21 echelon modprobe: modprobe: Can't locate module opl3
> Apr 25 22:56:21 echelon rc.sysinit: Loading midi module (opl3) failed

The errors mentioned above seem to indiciate that when you were doing the
compile of the system that you didn't seelct that you wanted your SoundBlaster
and OPL3 devices to be compiled in as modules. Hence the modules haven't been
created or haven't been installed correctly.

I presume that during the kernel compile, you actually did the make modules
and the make modules_install to ensure that the modules were placed on the
system.

Quote:> Apr 25 22:56:34 echelon sysctl: net.ipv4.ip_forward = 0
> Apr 25 22:56:34 echelon sysctl: net.ipv4.conf.all.rp_filter = 1
> Apr 25 22:56:34 echelon sysctl: net.ipv4.ip_always_defrag = 0
> Apr 25 22:56:34 echelon sysctl: net.ipv4.ip_forward = 1
> Apr 25 22:56:34 echelon sysctl: error: 'kernel.sysrq' is an unknown key

The kernel wasn't compiled with the sysrq functionality within it. You can
either remove this statement from the /etc/sysctl.conf file or compile it in
next time you do a compile of the system.

Quote:> Apr 25 22:56:34 echelon network: Setting network parameters succeeded
> Apr 25 22:56:34 echelon network: Bringing up interface lo succeeded
> Apr 25 22:56:34 echelon ifup: Delaying eth0 initialization.
> Apr 25 22:56:34 echelon network: Bringing up interface eth0 failed

I suspect that this might again be a problem with not specifying the network
device which you have installed in your system. If you did select it as a
module, then the system hasn't installed the modules correctly. You will need
to recompile your kernel with the network device support or make and install
your modules.

Quote:> Apr 25 22:56:34 echelon portmap: /etc/rc.d/rc3.d/S11portmap:
> /etc/rc.d/rc3.d/S11portmap: cannot execute binary file

Very wierd error. Check to make sure that the symbolic link
/etc/rc.d/rc3.d/S11portmap is actually pointing to a startup script for the
RPC portmapper. You may need to re-install the package to fix the fault.

Quote:> Apr 25 22:56:34 echelon rc: Starting portmap failed
> Apr 25 22:56:43 echelon sshd: Starting sshd:
> Apr 25 22:56:43 echelon sshd: sshd startup succeeded
> Apr 25 22:56:43 echelon sshd: ^[[60G
> Apr 25 22:56:43 echelon sshd:

Not exactally sure about the sshd start up sequence. If the daemon loads
successfully, I would learn to live with it, although it is very wierd.

Quote:> Apr 26 11:36:52 echelon modprobe: modprobe: Can't locate module
> char-major-108
> Apr 26 11:50:24 echelon modprobe: modprobe: Can't locate module sound-slot-0
> Apr 26 11:50:24 echelon modprobe: modprobe: Can't locate module
> sound-service-0-3
> Apr 26 13:43:04 echelon snort[10643]: pcap_loop: read: Network is down
> Apr 26 13:43:05 echelon pppd[12370]: Can't execute /etc/ppp/ip-down: Exec
> format error

Check to make sure that the ppp interface is supported within the system and
also check the file /etc/ppp/ip-down, although the system should be starting
up your PPP connection during the boot and not shutting it down.

Quote:
> Once you upgrade a new kernel can you simply do another make menuconfig to
> go through your options again.?

Yes, that is correct. If you do a "make menuconfig" you will be presented
with the options that you selected last time. From there, you can reconfigure
your kernel and modules.

Quote:> What do you think ?? What do you suggest

Take a look at the inline comments, but I would rebuild the kernel and check
to make sure that your modules were compiled and installed.

See ya

Dean Thompson

Very Computer

kernel & network problems

kernel & network problems

kernel & network problems