Re: [PARPORT] FreeCom DriveIn


Steve Powers (sgp@pani.cx)
Sun, 18 Apr 1999 17:01:08 +0100


--------
Oops forgot,

The cable is a standard IEEE 1248 (approx 0.5 metre) parallel cable (supplied
with the unit) plugging directly in the parallel port on the PC.

Steve

---
OK, 

PC running Award BIOS v4.51PG

Parallel port set to EPP/SPP EPP1.9 in the BIOS

The motherboard is an ABIT (can't remember the number) with a P166MMX. Adaptec 2490 SCSI controller. SBPro using IRQ 5 DMA 1

Linux version 2.0.36 (hostname) (gcc version 2.7.2.1) with the paride code from2.0.37-pre-patch-10. I have just patched the /usr/src/linux/drivers/blocks/

paride files from the diffs in this patch. Are there any other files (except Documentation) it will be reliant on?

/proc/pci shows:

PCI devices found: Bus 0, device 17, function 0: SCSI storage controller: Adaptec AIC-7871 (rev 3). Medium devsel. Fast back-to-back capable. IRQ 10. Master Capable. Latency=32. Min Gnt=8.Max Lat=8. I/O at 0x6100. Non-prefetchable 32 bit memory at 0xe1804000. Bus 0, device 16, function 0: VGA compatible controller: Matrox Millennium II (rev 0). Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. Latency=32. Prefetchable 32 bit memory at 0xe0000000. Non-prefetchable 32 bit memory at 0xe1800000. Non-prefetchable 32 bit memory at 0xe1000000. Bus 0, device 7, function 1: IDE interface: Intel 82371SB PIIX3 IDE (rev 0). Medium devsel. Fast back-to-back capable. Master Capable. Latency=32.

I/O at 0xf000. Bus 0, device 7, function 0: ISA bridge: Intel 82371SB PIIX3 ISA (rev 1). Medium devsel. Fast back-to-back capable. Master Capable. No bursts. Bus 0, device 0, function 0: Host bridge: Intel 82439HX Triton II (rev 3). Medium devsel. Master Capable. Latency=32.

I have an Iomega Zip drive that works fine on the parallel port so know that's fine. I've now tries two different CDRom drives in the DriveIn both get the same results on paride, (both work fine in Win95). The primary drive I'm intending to use is a Mitsumi FX810s !BX01 as Win95 reports it. The drive works in Fast EEP Mode at address 378h IRQ 7 on Win95.

Steve

> > pcd0: friq: port 0x378, mode 0, test=(0,1,0) > > pcd0: friq: port 0x378, mode 1, test=(0,1,0) > > pcd0: friq: port 0x378, mode 2, test=(0,1,0) > > pcd0: friq: port 0x378, mode 3, test=(0,1,0) > > pcd0: friq: port 0x378, mode 4, test=(0,1,0) > > pcd0: friq 1.01, Freecom IQ ASIC-2 adapter at 0x378, mode 4 (EPP-32), delay 1 > > So this establishes that the adapter is the ASIC-2 - so that question is > resolved. > > > pcd0: Reset (1) signature = 1 1 1 14 eb > > pcd0: identify before command: alt=0x5a stat=0x58 err=0x100 loop=160001 phase=1 > > pcd0: Request sense before command: alt=0x5a stat=0x58 err=0x100 loop=160001 > > phase=1 > > pcd0: Reset (1) signature = 0 1 1 14 eb (incorrect) > > pcd: No CDrom drive found > > These data seem to suggest that either the drive is flaky (a not uncommon > problem) or you are getting random bit errors on the parallel cable. Power > is sometimes a factor - if the power supply is a little weak and the drive > is a pig ... > > Does the identical configuration work with DOS or Windows ? Tell us > about the computer, and the physical connections. Do you have an > alternate drive to test with ? > > > pcd0: friq: port 0x378, mode 0, test=(1,1,0) > > There might be something in that stray "1". > > The driver tests communication with the drive. Part of the testing is > to write values into the IDE registers and read them back using an > algorithm that can't be fooled by the intervening adapter. All 256 > 8-bit patterns are written (in a scrambled order). The first number of > the three is the number of errors encountered writing and reading the > registers in the "master" drive. It's quite unusual for a single > byte to fail like that. > > -------------------------------------------------------------------------- > Grant R. Guenther grant@torque.net > -------------------------------------------------------------------------- >

-- To unsubscribe, send mail to: linux-parport-request@torque.net -- -- with the single word "unsubscribe" in the body of the message. --



This archive was generated by hypermail 2.0b3 on Sun 18 Apr 1999 - 11:01:28 EDT