Re: Panel Segmentation Fault

[rkelsoe ev1 net]

Steven Bradley wrote:
> 
> Well this produced more problems:
> 
> Kernel panic: No init found.  Try passing init= option to kernel.
> 
> and it hangs.  With old kernel, still boots/runs correctly.  This is with
> a fresh install.  The initrd image appears to be ok.  It could be the fact
> I am using both the 2840VLB and 2940W controllers (narrow VLB EISA SCSI
> and wide EISA SCSI) and perhaps the SCSI driver needs an update.  I loaded
> the SCSI driver and SMC EISA Ultra drivers individually during the install.
> 
> If I need new driver(s) for SCSI and or the two SMC cards, where would I
> find compatible drivers to go with this kernel?
> 
> Any clues?  I appreciate your help.  Steven
> 
> Previously, on Sun Dec 30 13:58:43 2001, rkelsoe ev1 net said:
> 
> > Steven Bradley wrote:
> > >
> > > Dear Randy,
> > >
> > > Thank you for this useful gem.  Please excuse my ignorance, but for myself
> > > (and others on the list), can you please describe how to upgrade the kernel
> > > to 2.4.9-13 (I'm not a computer novice, I simply have never done a kernel
> > > update before).  I will really appreciate getting this to run.  Thank you.
> > >
> > > Steven
> > >
> > > Previously, on Sun Dec 30 13:05:37 2001, rkelsoe ev1 net said:
> > >
> > > > Steven Bradley wrote:
> > > > >
> > > > > I am hoping someone can help me with this problem.
> > > > >
> > > > > I have installed at least three times, RH 7.2 and each time when I go to
> > > > > start X (startx), it comes back with a Fatal Error while loading the panel
> > > > > at the bottom of the screen.  It is due to a segmentation fault.  It will
> > > > > happen every time I install and try to start X.  It will also do it every
> > > > > time I try to start X and not just after an install as well.
> > > > >
> > > > > Bottom line -- I can not get X to run on RH 7.2 without the Panel crashing
> > > > > every time.  I use KNOME obviously.
> > > > >
> > > > > I tried RH 7.1 and it does not have this problem.  It works perfectly.
> > > > >
> > > > > But there are some nice features in 7.2 and I am creating a new server
> > > > > (EISA, SCSI, AMI BIOS/Motherboard) and would like the latest on it.
> > > > >
> > > > > I have searched all over the net and found a few references to other people
> > > > > with this problem, but no solutions.  I have checked on redhat.com and it
> > > > > appears to them the problem is non-existant by the lack of any reference to
> > > > > it at all.
> > > > >
> > > > > I can make it fail so well, if someone does have a fix, it will be easy to
> > > > > test it out.
> > > > >
> > > > > If anyone can help, I will appreciate it.  If not, I will have to make a
> > > > > decision at some point to use 7.1 as it does at least function without
> > > > > crashing every time.  Hopefully someone may know the answer to this, or
> > > > > perhaps it will be "wait for 7.3".
> > > > >
> > > > > Steven
> > > > > --
> > > > > Steven Bradley            121 Cambridge Drive, Longwood, FL  32779-5707  USA
> > > > > steven sgb dyndns org                 Home: (407) 862-7226 or (407) 869-4598
> > > > >
> > > >
> > > > I saw this same problem and upgrading to the 2.4.9-13 kernel resolved
> > > > the problem.
> > > >
> >
> > If you are registered with the RedHat Network, you can use up2date to
> > update the kernel.
> >
> > Or, you can go to:
> >
> >   ftp://ftp.redhat.com/pub/redhat/linux/updates/7.2/en/os/
> >
> > and you will see several directories for the different processors. Pick
> > the directory for the processor you are using, and download that kernel
> >
> > (eg. kernel-2.4.9-13.i386.rpm)
> >
> > If you want to customize your kernel, you will need to go back to the
> > i386 directory and get the kernel-source, kernel-headers, and kernel-doc
> > rpm's as well.
> >
> > As root, you can do a
> >
> >       rpm -ivh kernel-2.4.9-13.iXXX.rpm      (XXX=your processor number)
> >
> > Which will install your new kernel, keeping your old kernel, in case of
> > emergency. If you are using lilo (and not grub) the rpm should update
> > your /etc/lilo.conf to add a new entry for the new kernel. You can then
> > run lilo -v, and if every thing looks fine, reboot and try the new
> > kernel. If you have problems, you should still be able to reboot your
> > old kernel. Once you are happy with your new kernel, you can edit your
> > /etc/lilo.conf and make the new kernel the default boot kernel and rerun
> > lilo.
> >
> > If you installed the kernel source, headers, and doc rpm's you can
> > upgrade these with rpm.
> >
> >   rpm -Uvh kernel-source*.rpm kernel-headers*.rpm kernel-doc*.rpm
> >
> > If theses packages were not installed, just use:
> >
> >   rpm -ivh kernel-source*.rpm kernel-headers*.rpm kernel-doc*.rpm
> >
> >
> > RK
> >
> > --

Check your /etc/lilo.conf file and see if it has a line under the label
for the 2.4.9-13 kernel. It should look something like this:

	initrd=/boot/initrd-2.4.9-13

and you should have that initrd-2.4.9-13 in the /boot directory. Once
you get the lilo.conf file straightened out, don't forget to run lilo
again.

As far as the drivers, you might try an 'lsmod' with the old kernel. I
suspect they get loaded as modules and should be fine for the new
kernel.

RK

-- 
Randy Kelsoe
Dae Richt, Fear Nacht