Re: CF-Firewire adapter
On 12/31/2003 09:07 PM, peasthope@shaw.ca wrote:
> A photo of a CF-Firewire adapter here.
> http:/carnot.yi.org/UnityDigitalCF.Firewire.jpg
> I removed the cover in case anyone is interested. The two largest chips
> are marked LSI SYM13FW501 and Winbond W27E010P-70.
>
> When the firewire plug is connected, dmesg gives the following.
> fdisk -l yields nothing about the device.
>
> Is anything short of work on the driver likely to make this adapter operate?
>
> Thanks, ... Peter E.
>
> =======================
> [ 2127.727949] firewire_core: skipped bus generations, destroying all nodes
> [ 2128.224257] firewire_core: rediscovered device fw1
> [ 2128.224299] firewire_core: phy config: card 2, new root=ffc1, gap_count=5
> [ 2131.234125] firewire_core: giving up on config rom for node id ffc0
> [ 2171.962587] firewire_core: skipped bus generations, destroying all nodes
> [ 2172.461296] firewire_core: rediscovered device fw1
> [ 2172.461335] firewire_core: phy config: card 2, new root=ffc1, gap_count=5
> [ 2175.524876] scsi5 : SBP-2 IEEE-1394
> [ 2175.524994] firewire_sbp2: Workarounds for fw2.0: 0x1 (firmware_revision 0xa0b832, model_id 0x000000)
> [ 2175.525004] firewire_core: created device fw2: GUID 00a0b80000005000, S400, 1 config ROM retries
> [ 2176.372964] firewire_sbp2: fw2.0: logged in to LUN 0000 (0 retries)
> [ 2176.377064] scsi 5:0:0:0: Direct-Access LSILogic SYM13FW500-Disk 1.00 PQ: 0 ANSI: 0
> [ 2176.378556] sd 5:0:0:0: Attached scsi generic sg3 type 0
> [ 2176.381845] sd 5:0:0:0: [sdb] 1000944 512-byte logical blocks: (512 MB/488 MiB)
> [ 2176.384615] sd 5:0:0:0: [sdb] Write Protect is off
> [ 2176.384622] sd 5:0:0:0: [sdb] Mode Sense: 10 00 00 00
> [ 2176.386164] sd 5:0:0:0: [sdb] Cache data unavailable
> [ 2176.386171] sd 5:0:0:0: [sdb] Assuming drive cache: write through
> [ 2176.393377] sd 5:0:0:0: [sdb] Cache data unavailable
> [ 2176.393383] sd 5:0:0:0: [sdb] Assuming drive cache: write through
> [ 2207.072560] firewire_sbp2: fw2.0: sbp2_scsi_abort
> [ 2217.073225] firewire_sbp2: fw2.0: sbp2_scsi_abort
> [ 2217.073435] sd 5:0:0:0: Device offlined - not ready after error recovery
> [ 2217.073453] sd 5:0:0:0: [sdb] Unhandled error code
> [ 2217.073457] sd 5:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK
> [ 2217.073463] sd 5:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
> [ 2217.073475] end_request: I/O error, dev sdb, sector 0
> [ 2217.073484] Buffer I/O error on device sdb, logical block 0
> [ 2217.073552] sd 5:0:0:0: rejecting I/O to offline device
> [ 2217.073599] sd 5:0:0:0: rejecting I/O to offline device
> [ 2217.073619] sd 5:0:0:0: rejecting I/O to offline device
> [ 2217.073637] sd 5:0:0:0: rejecting I/O to offline device
> [ 2217.073646] ldm_validate_partition_table(): Disk read failed.
> [ 2217.073660] sd 5:0:0:0: rejecting I/O to offline device
> [ 2217.073677] sd 5:0:0:0: rejecting I/O to offline device
> [ 2217.073695] sd 5:0:0:0: rejecting I/O to offline device
> [ 2217.073712] sd 5:0:0:0: rejecting I/O to offline device
> [ 2217.073721] Dev sdb: unable to read RDB block 0
> [ 2217.073735] sd 5:0:0:0: rejecting I/O to offline device
> [ 2217.073752] sd 5:0:0:0: rejecting I/O to offline device
> [ 2217.073780] sd 5:0:0:0: rejecting I/O to offline device
> [ 2217.073792] sd 5:0:0:0: rejecting I/O to offline device
> [ 2217.073809] sd 5:0:0:0: rejecting I/O to offline device
> [ 2217.073817] sdb: unable to read partition table
> [ 2217.073977] sd 5:0:0:0: [sdb] Attached SCSI removable disk
> =======================
>
>
>
Did you really post this over nine years ago? It's dated
12/31/2001 09:07 PM. Someone must have solved this by now!
--doug
--
Blessed are the peacemakers..for they shall be shot at from both sides.
--A.M.Greeley
Reply to: