[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: Enigma stuck at 2.4.9?
- From: Steven Bradley <steven sgb dyndns org>
- To: enigma-list redhat com
- Subject: Re: Enigma stuck at 2.4.9?
- Date: Mon, 31 Dec 2001 17:20:13 -0500 (EST)
Previously, on Mon Dec 31 14:07:31 2001, Chris Kloiber said:
>
> On Mon, 2001-12-31 at 09:35, Aaron Konstam wrote:
> > On Mon, Dec 31, 2001 at 08:41:23AM -0500, Steven Bradley wrote:
> > > I've got a problem that needs me to install the 2.4.9-13 kernel. The
> > > problem is the "chicken and the egg" syndrome. Specifically, it appears
> > > my existing SCSI driver (for 2740W) is not compatible with the new kernel.
> > >
> > > I do not know how to link the SCSI driver for 2.4.9-13 into the initrd
> > > file to allow it to access SCSI during boot, I believe the driver is the
> > > aic7xxx driver. The problem is I am booted under the earlier file, the
> > > version it uses when initrd is made, it does so under the existing
> > > environment (ie old driver) and I get all kinds of errors when I reboot
> > > and try to use the new kernel.
> > >
> > When you run mkinitrd to produce the initrd file for the kernel just use
> > the --with=aic7xxx option.
>
> Actually, it would be better to make sure your modules.conf is in order,
> (alias scsi_hostadapter aic7xxx) then just use the command:
>
> # mkinitrd /boot/initrd-2.4.9-13 2.4.9-13
>
> Edit your {grub,lilo}.conf to match, and rerun lilo if used.
Ok, I've done yet one more fresh install, one more rpm -ihv to install the
2.4.9-13 kernel, verified the modules.conf would load the correct drivers,
and then did:
mkinitrd -f -v /boot/initrd-2.4.9-13.img 2.4.9-13
I am using grub, it is set to use the correct file. The system hangs
right after the attempt to scan the SCSI drives for ID (which has error
dump data, it never sees the SCSI drives). None of this ever ends up
in the log files as it never can address the SCSI drives where the
/var/log/messages are located. I really have no idea what to do next.
The -f was to replace the rpm installed file created when the kernel
2.4.9-13 rpm is installed and -v was for seeing the most I can - it looked
ok. Now I wonder if there could be a problem with the driver in this
version of the kernel. I am using adaptec controllers, two of them,
2840VLB is for narrow SCSI (CDROM and Tape) and 2740W is Wide SCSI for
two 4G 15150W and one 9G Wide Barracuda (I forget the model). It works
fine if I select the older kernel.
Help please!
Steven
--
Steven Bradley 121 Cambridge Drive, Longwood, FL 32779-5707 USA
steven sgb dyndns org Home: (407) 862-7226 or (407) 869-4598
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]