[ale] SCSI module not loading on Debian Sarge

[Jim Seymour]

Just did a uname -a and found out it is still using the original kernel.  
The links from /initrd.img and /vmlinuz both point to the new versions 
in /boot.  Lilo.conf confirms that it should be using these links to 
boot.  Okay now I am really lost.  At least this explains why it can't 
find the new module for the scsi controller.

Jim Seymour

On Sun, Dec 21, 2003 at 12:07:32AM -0800, Jim Popovitch wrote:
> Check to make sure the driver is valid and loads manually by using insmod.  You
> might see some dependency errors.  If so, you may need one or more other
> support modules.
> 
> -Jim P.
> 
> --- Jim Seymour <bluejay at speedfactory.net> wrote:
> > Thanks Jim,
> > 
> > Just tried it both ways. Once with it in as an alias (just like it was 
> > under Red Hat) and once added to the modules file.  Neither worked.  
> > However with it listed in the modules file I did get a boot message 
> > about the modprobe not finding the module. This kernel was built with 
> > make-kpkg following the Debian Reference. What's next?????
> > 
> > Jim Seymour
> > 
> > On Sat, Dec 20, 2003 at 10:31:39PM -0800, Jim Popovitch wrote:
> > > One more thing, run 'update-modules' after making your changes.
> > > 
> > > -Jim P.
> > > 
> > > --- Jim Popovitch <jimpop at yahoo.com> wrote:
> > > > 
> > > > If you need to alias the driver, then add an entry to
> > /etc/modutils/aliases. 
> > > > Otherwise, just put dc395 (or whatever the driver is called) into
> > > > /etc/modules
> > > > 
> > > > hth,
> > > > 
> > > > -Jim P.
> > > > 
> > > > --- Jim Seymour <bluejay at speedfactory.net> wrote:
> > > > > Hi All,
> > > > > 
> > > > > 	Just finished compiling a kernel Debian's way patching in a 
> > > > > Tekram driver for a dc395.  Everything went fine (I guess) until I 
> > > > > rebooted.  The Tekram driver is for a scanner.  I can find the module 
> > > > > under /lib/modules/2.4.22-486/kernel/drivers/scsi.  However I am used
> > to 
> > > > > Red Hat's way of building/installing of kernels and modules.  Debian 
> > > > > uses this modconf thingy.  Modconf doesn't think the module is 
> > > > > installed.  Can someone get me through this or am I looking at trying
> > to 
> > > > > recompile the kernel?
> > > > > 
> > 
> > _______________________________________________
> > Ale mailing list
> > Ale at ale.org
> > http://www.ale.org/mailman/listinfo/ale
> 
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
>