Re: Corrupted module?
When I do that, it enters the directory, finds nothing (target module)
and then leaves the directory. Am I doing something wrong?
Thanks,
Cameron Matheson
Ron Rademaker wrote:
>
> Try recompiling the module...
>
> Go to your kernel-source do and do: make modules && make modules_install
>
> If it really is the module, that should solve it...
>
> Ron
>
> On Tue, 15 Feb 2000, Cameron Matheson wrote:
>
> > Hey,
> >
> > When my power went out, I think a module in my kernel was corrupted
> > (cause my computer turned off). It's the SBPCD module (a module for the
> > external Creative CD-ROM drive). This is the output:
> >
> > Module inserted $Id: cdrom.c,v 0.8 1996/08/10 10:52:11 david Exp $
> > sbpcd-0 [01]: sbpcd.c v4.6 Eberhard Moenkeberg <emoenke@gwdg.de>
> > sbpcd-0 [02]: Scanning 0x230 (SoundBlaster)...
> > sbpcd-0 [03]: Scanning 0x230 (SoundBlaster)...
> > sbpcd-0 [04]: Scanning 0x300 (LaserMate)...
> > sbpcd-0 [05]: Scanning 0x250 (SoundBlaster)...
> > sbpcd-0 [06]: Scanning 0x2C0 (Teac16bit)...
> > sbpcd-0 [07]: Scanning 0x260 (SoundBlaster)...
> > sbpcd-0 [08]: Scanning 0x320 (LaserMate)...
> > sbpcd-0 [09]: Scanning 0x338 (LaserMate)...
> > sbpcd-0 [10]: Scanning 0x340 (LaserMate)...
> > ...
> > sbpcd-0 [29]: No drive found.
> >
> > The drive is on 0x230 (which it scanned twice). The CD-ROM drive is
> > connected properly (it reads it when it scans 0x230), so I think it must
> > be the module. Does anyone know how I could fix this?
> >
> > Thanks,
> > Cameron Matheson
> >
> >
> > --
> > Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
> >
Reply to: