Not sure about Redhat 6.0 mind you, don't you have to mount these
devices?
~P~
Richard Spencer wrote:
>
> Gurus:
>
> I am trying to get my system to recognize my SCSI Zip and Syquest paride
> SparQ. First, regarding the Zip, I've read /var/log/messages and it seems to
> find my Adaptec controller. But I wonder--while looking at these error
> messages--why it cannot find the Zip drive. I do have a disk inside when
> I boot the system. AFAIK, SCSI is enabled. I don't know what modules this
> needs, however. I plan to run make xconfig, look at help blurbs until I find
> the SCSI parport module I need, and exit without saving changes. Can anyone
> tell me an easier way to establish this? You'll see my system info. and error
> messages below.
>
> The same would apply to my paride SparQ; power is on, cable connected to
> parport, and disk inserted prior to booting the system. I've established this
> puppy needs the following modules: paride, paride_pd and paride_epat. I guess
> I'll have to figure out IRQs and I/O addresses etc. Can anyone tell me if I can
> read the contents of some file to determine IRQs already taken? Also, where
> can I look to see if these modules are being loaded?--if I hadn't read
> /var/log/messages, I wouldn't have known that Linux recognized my SCSI
> adapter. I would have tried to re-configure/rebuild the kernel.
>
> Notwithstanding the risk of RTFM comments, If anyone can explain this insmod
> and how it might help me, I'd appreciate it. BTW, I DO plan to rtfm asap. But
> it seems that if I know what module I need (for one of the two drives, for
> instance) I can insert it at will. This sounds good, no?
>
> Oh, did I mention I've been windoze-free for 3 days, and I've never felt better?
>
> I'm running RH 6.0 on a Dell Latitude Pentium 133 laptop--why? because I don't
> have a desktop system ;-)
>
> part of /var/log/messages:
> scsi : 0 hosts
> scsi : detected total
> <snip>
> localhost kernel : aha152x : processing command line : ok
> localhost kernel : aha152x : BIOS test : passed, detected 1 controller(s)
> localhost kernel : aha152x0 : vital data : PORTBASE 0x340, IRQ=3, SCSI ID=7
> reconnect=enabled, parity=enabled, synchronous=disabled, delay=100, extended
> translation=disabled
> localhost kernel : aha152x : trying software interrupt, ok.
> localhost pcmcia : modules
> localhost kernel : scsi0 : Adaptec 152x SCSI driver; $Revision: 1.7$
> localhost kernel : scsi : 1 host
> localhost pcmcia : cardmgr.
> localhost cardmgr. [289] : starting, version is 3.0.9
> localhost cardmgr. [289] : watching 2 sockets
> localhost cardmgr. [289] : initializing socket 1
> localhost cardmgr. [289] : socket 1 : Adaptec APA-1460 SlimSCSI
> localhost cardmgr. [289] : executing : insmod
> /lib/modules/2.2.5-15/pcmcia/aha152x_cs.o
> localhost rc : Starting pcmcia suceeded
> <snip>
> localhost kernel : scsi : aborting command due to timeout: pid 0, scsi 0
> channel 0, id 0, lun 0, Test Unit Ready 00 00 00 00 00
> <snip>
> localhost kernel : aha152x_cs : no SCSI devices found
> localhost kernel : scsi : 0 hosts
> localhost cardmgr[289] : get dev info on socket 1failed : no such device
> <snip>
>
> And then the following error message from above repeats, with minor changes to
> (if memory serves me correctly) pid and id--even as I attempt to log in
> (runlevel 3)
> localhost kernel : scsi : aborting command due to timeout: pid 0,
> scsi 0 channel 0, id 0, lun 0, Test Unit Ready 00 00 00 00 00
>
> --
> ~~~~~~~~~~~~~~~
> Richard Spencer
