Thanks for the info. I kept using -F which doesn't work. I press the
space bar so that I can scan for anything funky going on.
Patrick
On Thu, 2002-05-30 at 20:23, Bret Hughes wrote:
> On Thu, 2002-05-30 at 19:28, Patrick May wrote:
> > >From this information, you still need to load the aic7xxx
On Thu, 2002-05-30 at 19:28, Patrick May wrote:
> >From this information, you still need to load the aic7xxx module which
> is the driver for the 2930 (and many other Adaptec controllers.)
>
> As root do "modprobe aic7xxx' and it should detect and make the
> appropriate entries in /var/log/messag
On Thu, 2002-05-30 at 20:24, Ricardo J. Méndez Castro wrote:
>
> SG is NOT listed, but I had assumed (probably incorrectly) that it was
> compiled in scsi_mod. I'll re-check.
The SCSI generic module is separate and (assuming it is compiled as a
module) will show up by itself as can be seen her
> As root do "modprobe aic7xxx' and it should detect and make the
> appropriate entries in /var/log/messages (and dmesg I think will show
> it.)
That did the trick, thanks! It did involve several attempts where Linux got
hung up, I cursed profusely and had to hard-reset it, but it ended up bein
On Thu, 2002-05-30 at 20:28, Patrick May wrote:
... ...
> it.) For this I either run another xterm or log in as root on a virtual
> terminal and 'less /var/log/messages'. Press the space bar until you see
> END highlighted and then give it a capital "F". shift+f. This will put
> less into follow
>From this information, you still need to load the aic7xxx module which
is the driver for the 2930 (and many other Adaptec controllers.)
As root do "modprobe aic7xxx' and it should detect and make the
appropriate entries in /var/log/messages (and dmesg I think will show
it.) For this I either run
> The above information suggests that (a) your Adaptec SCSI adapter is not
> being detected, and (b) the sg module is not loaded. Your system should
> look like it has two SCSI adapters, one for the Promise controller and
> the other for the Adaptec. Depending on what order they are detected,
>
On Thu, 2002-05-30 at 15:58, Ricardo J. Méndez Castro wrote:
>
> > Also look in your boot logs to see what the SCSI driver is doing.
>
> [...]
>
> Looking at dmesg, the only SCSI device I found mentioned was the integrated
> Promise FastTrack lite controller. Here's the sub-section:
>
> Journa
> Also look in your boot logs to see what the SCSI driver is doing.
[...]
Looking at dmesg, the only SCSI device I found mentioned was the integrated
Promise FastTrack lite controller. Here's the sub-section:
Journalled Block Device driver loaded
SCSI subsystem driver Revision: 1.00
Promise Fa
On Thu, 2002-05-30 at 02:53, Ricardo J. Méndez Castro wrote:
> Hi Linus,
>
>
> > First, make sure you have sg (SCSI generic) support in your system. It
> > is almost always built as a module.
>
> sg is supported and loaded.
>
>
> > Also, make sure the scanner is being
> > detected by your SCS
Hi Linus,
> First, make sure you have sg (SCSI generic) support in your system. It
> is almost always built as a module.
sg is supported and loaded.
> Also, make sure the scanner is being
> detected by your SCSI adapter before Linux starts booting.
If you mean being detected by the adapter e
On Wed, 2002-05-29 at 12:55, Ricardo J. Méndez Castro wrote:
> Hi,
>
> I've got a problem with my SCSI scanner: it's apparently not being detected
> on
> boot. Here's my configuration:
>
> Red Hat Linux 7.2, kernel 2.4.7-10
> SCSI Card: Adaptec AHA-2930CU (Detected and running)
> Motherboard &
Hi,
I've got a problem with my SCSI scanner: it's apparently not being detected
on
boot. Here's my configuration:
Red Hat Linux 7.2, kernel 2.4.7-10
SCSI Card: Adaptec AHA-2930CU (Detected and running)
Motherboard & CPU: GA-7ZXR, Athlon 1.3 GHz
Scanner: Polaroid Sprintscan 35 Plus
I'm attempti
13 matches
Mail list logo
