usb-ide bridge - Hardware

This is a discussion on usb-ide bridge - Hardware ; Hello, I'd like to use a USB-IDE bridge under Linux (slackware 10.2, kernel 2.6.13). Here is the information regarding the hardware : lsusb -vvv Bus 005 Device 001: ID 0000:0000 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 9 ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: usb-ide bridge

  1. usb-ide bridge

    Hello,

    I'd like to use a USB-IDE bridge under Linux (slackware 10.2, kernel
    2.6.13).

    Here is the information regarding the hardware :


    lsusb -vvv

    Bus 005 Device 001: ID 0000:0000
    Device Descriptor:
    bLength 18
    bDescriptorType 1
    bcdUSB 1.10
    bDeviceClass 9 Hub
    bDeviceSubClass 0 Unused
    bDeviceProtocol 0
    bMaxPacketSize0 8
    idVendor 0x0000
    idProduct 0x0000
    bcdDevice 2.06
    iManufacturer 3 Linux 2.6.13 uhci_hcd
    iProduct 2
    iSerial 1 0000:00:1d.3
    bNumConfigurations 1
    Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 25
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xc0
    Self Powered
    MaxPower 0mA
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 1
    bInterfaceClass 9 Hub
    bInterfaceSubClass 0 Unused
    bInterfaceProtocol 0
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x81 EP 1 IN
    bmAttributes 3
    Transfer Type Interrupt
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0002 bytes 2 twice
    bInterval 255

    Bus 004 Device 001: ID 0000:0000
    Device Descriptor:
    bLength 18
    bDescriptorType 1
    bcdUSB 1.10
    bDeviceClass 9 Hub
    bDeviceSubClass 0 Unused
    bDeviceProtocol 0
    bMaxPacketSize0 8
    idVendor 0x0000
    idProduct 0x0000
    bcdDevice 2.06
    iManufacturer 3 Linux 2.6.13 uhci_hcd
    iProduct 2 Intel Corporation 82801EB/ER (ICH5/ICH5R)
    USB UHCI #3
    iSerial 1 0000:00:1d.2
    bNumConfigurations 1
    Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 25
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xc0
    Self Powered
    MaxPower 0mA
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 1
    bInterfaceClass 9 Hub
    bInterfaceSubClass 0 Unused
    bInterfaceProtocol 0
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x81 EP 1 IN
    bmAttributes 3
    Transfer Type Interrupt
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0002 bytes 2 twice
    bInterval 255

    Bus 003 Device 001: ID 0000:0000
    Device Descriptor:
    bLength 18
    bDescriptorType 1
    bcdUSB 1.10
    bDeviceClass 9 Hub
    bDeviceSubClass 0 Unused
    bDeviceProtocol 0
    bMaxPacketSize0 8
    idVendor 0x0000
    idProduct 0x0000
    bcdDevice 2.06
    iManufacturer 3 Linux 2.6.13 uhci_hcd
    iProduct 2
    iSerial 1 0000:00:1d.1
    bNumConfigurations 1
    Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 25
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xc0
    Self Powered
    MaxPower 0mA
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 1
    bInterfaceClass 9 Hub
    bInterfaceSubClass 0 Unused
    bInterfaceProtocol 0
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x81 EP 1 IN
    bmAttributes 3
    Transfer Type Interrupt
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0002 bytes 2 twice
    bInterval 255

    Bus 002 Device 001: ID 0000:0000
    Device Descriptor:
    bLength 18
    bDescriptorType 1
    bcdUSB 1.10
    bDeviceClass 9 Hub
    bDeviceSubClass 0 Unused
    bDeviceProtocol 0
    bMaxPacketSize0 8
    idVendor 0x0000
    idProduct 0x0000
    bcdDevice 2.06
    iManufacturer 3 Linux 2.6.13 uhci_hcd
    iProduct 2
    iSerial 1 0000:00:1d.0
    bNumConfigurations 1
    Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 25
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xc0
    Self Powered
    MaxPower 0mA
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 1
    bInterfaceClass 9 Hub
    bInterfaceSubClass 0 Unused
    bInterfaceProtocol 0
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x81 EP 1 IN
    bmAttributes 3
    Transfer Type Interrupt
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0002 bytes 2 twice
    bInterval 255

    Bus 001 Device 004: ID 152d:2338
    Device Descriptor:
    bLength 18
    bDescriptorType 1
    bcdUSB 2.00
    bDeviceClass 0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 64
    idVendor 0x152d
    idProduct 0x2338
    bcdDevice 1.00
    iManufacturer 1 JMicron
    iProduct 2 *USB to ATA/ATAPI Bridge*
    iSerial 5 152D203380B6
    bNumConfigurations 1
    Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 32
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 4 USB Mass Storage
    bmAttributes 0xc0
    Self Powered
    MaxPower 2mA
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 2
    bInterfaceClass 8 Mass Storage
    bInterfaceSubClass 6 SCSI
    bInterfaceProtocol 80 Bulk (Zip)
    iInterface 6 MSC Bulk-Only Transfer
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x81 EP 1 IN
    bmAttributes 2
    Transfer Type Bulk
    Synch Type wMaxPacketSize 0x0200 bytes 512 once
    bInterval 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x02 EP 2 OUT
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0200 bytes 512 once
    bInterval 0

    Bus 001 Device 001: ID 0000:0000
    Device Descriptor:
    bLength 18
    bDescriptorType 1
    bcdUSB 2.00
    bDeviceClass 9 Hub
    bDeviceSubClass 0 Unused
    bDeviceProtocol 1 Single TT
    bMaxPacketSize0 8
    idVendor 0x0000
    idProduct 0x0000
    bcdDevice 2.06
    iManufacturer 3 Linux 2.6.13 ehci_hcd
    iProduct 2 Intel Corporation 82801EB/ER (ICH5/ICH5R)
    USB2 EHCI Controller
    iSerial 1 0000:00:1d.7
    bNumConfigurations 1
    Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 25
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xe0
    Self Powered
    Remote Wakeup
    MaxPower 0mA
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 1
    bInterfaceClass 9 Hub
    bInterfaceSubClass 0 Unused
    bInterfaceProtocol 0
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x81 EP 1 IN
    bmAttributes 3
    Transfer Type Interrupt
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0002 bytes 2 twice
    bInterval 12
    None
    Usage Type Data







    When I plug the USB cable, le "usb-storage" module is loaded by the kernel :


    usb 1-3: new high speed USB device using ehci_hcd and address 4
    scsi2 : SCSI emulation for USB Mass Storage devices
    usb-storage: device found at 4
    usb-storage: waiting for device to settle before scanning
    Vendor: Model: Rev:
    Type: Direct-Access ANSI SCSI revision: 02
    Attached scsi disk sda at scsi2, channel 0, id 0, lun 0
    usb-storage: device scan complete




    But, I don't know how to access to the datas on the disk :

    # dd if=/dev/sda
    0+0 records in
    0+0 records out

    # fdisk /dev/sda

    Unable to read /dev/sda

    Any idea about this issue ?


    Regards.





  2. Re: usb-ide bridge

    f. lecaille wrote:

    > usb 1-3: new high speed USB device using ehci_hcd and address 4
    > scsi2 : SCSI emulation for USB Mass Storage devices
    > usb-storage: device found at 4
    > usb-storage: waiting for device to settle before scanning
    > Vendor: Model: Rev:
    > Type: Direct-Access ANSI SCSI revision: 02
    > Attached scsi disk sda at scsi2, channel 0, id 0, lun 0
    > usb-storage: device scan complete
    >
    > Any idea about this issue ?


    It only finds the bridge, not the actual disk. Try it on another computer.
    Try eith another drive. Check the connectors etc. If the disk is found it
    should look similar to this:

    usb-storage: device found at 6
    usb-storage: waiting for device to settle before scanning
    scsi 10:0:0:0: Direct-Access Maxtor 6 Y080P0 0811 PQ: 0 ANSI:
    0
    sd 10:0:0:0: [sdc] 160086528 512-byte hardware sectors (81964 MB)
    sd 10:0:0:0: [sdc] Test WP failed, assume Write Enabled
    sd 10:0:0:0: [sdc] Assuming drive cache: write through
    sd 10:0:0:0: [sdc] 160086528 512-byte hardware sectors (81964 MB)
    sd 10:0:0:0: [sdc] Test WP failed, assume Write Enabled
    sd 10:0:0:0: [sdc] Assuming drive cache: write through
    sdc: sdc1
    sd 10:0:0:0: [sdc] Attached SCSI disk
    sd 10:0:0:0: Attached scsi generic sg2 type 0
    usb-storage: device scan complete


    --
    Lasse Jensen [fafler at g mail dot com]
    Linux, the choice of a GNU generation.

  3. Re: usb-ide bridge

    Lasse Jensen wrote:
    > f. lecaille wrote:
    >
    >
    >>usb 1-3: new high speed USB device using ehci_hcd and address 4
    >>scsi2 : SCSI emulation for USB Mass Storage devices
    >>usb-storage: device found at 4
    >>usb-storage: waiting for device to settle before scanning
    >> Vendor: Model: Rev:
    >> Type: Direct-Access ANSI SCSI revision: 02
    >>Attached scsi disk sda at scsi2, channel 0, id 0, lun 0
    >>usb-storage: device scan complete
    >>
    >>Any idea about this issue ?

    >
    >
    > It only finds the bridge, not the actual disk. Try it on another computer.
    > Try eith another drive. Check the connectors etc. If the disk is found it
    > should look similar to this:
    >
    > usb-storage: device found at 6
    > usb-storage: waiting for device to settle before scanning
    > scsi 10:0:0:0: Direct-Access Maxtor 6 Y080P0 0811 PQ: 0 ANSI:
    > 0
    > sd 10:0:0:0: [sdc] 160086528 512-byte hardware sectors (81964 MB)
    > sd 10:0:0:0: [sdc] Test WP failed, assume Write Enabled
    > sd 10:0:0:0: [sdc] Assuming drive cache: write through
    > sd 10:0:0:0: [sdc] 160086528 512-byte hardware sectors (81964 MB)
    > sd 10:0:0:0: [sdc] Test WP failed, assume Write Enabled
    > sd 10:0:0:0: [sdc] Assuming drive cache: write through
    > sdc: sdc1
    > sd 10:0:0:0: [sdc] Attached SCSI disk
    > sd 10:0:0:0: Attached scsi generic sg2 type 0
    > usb-storage: device scan complete
    >
    >

    Thx !


    I ran a second test with another IDE disk than the firt one... without
    any problem... so the USB-ide bridge is ok.

    I didn't tell you that during my firt test I connected a DOM (Disk On
    Module) to the IDE connector on the USB-ide bridge...

    But I forgot I had to cross the connexion using a 40-pin IDE cable, so
    that the pin 1 on the USB-ide side may be connected to the pin 1 on the
    DOM side... and so on...

    So, now when I connect my DOM to the USB-ide bridge, it seems to be
    detected... but not very well :



    # dmesg

    usb 1-3: USB disconnect, address 7
    usb 1-3: new high speed USB device using ehci_hcd and address 8
    scsi6 : SCSI emulation for USB Mass Storage devices
    usb-storage: device found at 8
    usb-storage: waiting for device to settle before scanning
    Vendor: Q) )D! Model: )0 0 2"9" Rev: *0 f
    Type: Direct-Access ANSI SCSI revision: 02
    SCSI device sda: 537077760 512-byte hdwr sectors (274984 MB)
    sda: assuming drive cache: write through
    SCSI device sda: 537077760 512-byte hdwr sectors (274984 MB)
    sda: assuming drive cache: write through
    sda: unknown partition table
    Attached scsi disk sda at scsi6, channel 0, id 0, lun 0
    usb-storage: device scan complete




    Note that my DOM has a 128 Mbytes capacity storage !!!








  4. Re: usb-ide bridge

    tartinator wrote:
    > Lasse Jensen wrote:
    >
    >> f. lecaille wrote:
    >>
    >>
    >>> usb 1-3: new high speed USB device using ehci_hcd and address 4
    >>> scsi2 : SCSI emulation for USB Mass Storage devices
    >>> usb-storage: device found at 4
    >>> usb-storage: waiting for device to settle before scanning
    >>> Vendor: Model: Rev:
    >>> Type: Direct-Access ANSI SCSI revision: 02
    >>> Attached scsi disk sda at scsi2, channel 0, id 0, lun 0
    >>> usb-storage: device scan complete
    >>>
    >>> Any idea about this issue ?

    >>
    >>
    >>
    >> It only finds the bridge, not the actual disk. Try it on another
    >> computer.
    >> Try eith another drive. Check the connectors etc. If the disk is found it
    >> should look similar to this:
    >>
    >> usb-storage: device found at 6
    >> usb-storage: waiting for device to settle before scanning
    >> scsi 10:0:0:0: Direct-Access Maxtor 6 Y080P0 0811 PQ: 0
    >> ANSI:
    >> 0
    >> sd 10:0:0:0: [sdc] 160086528 512-byte hardware sectors (81964 MB)
    >> sd 10:0:0:0: [sdc] Test WP failed, assume Write Enabled
    >> sd 10:0:0:0: [sdc] Assuming drive cache: write through
    >> sd 10:0:0:0: [sdc] 160086528 512-byte hardware sectors (81964 MB)
    >> sd 10:0:0:0: [sdc] Test WP failed, assume Write Enabled
    >> sd 10:0:0:0: [sdc] Assuming drive cache: write through
    >> sdc: sdc1
    >> sd 10:0:0:0: [sdc] Attached SCSI disk
    >> sd 10:0:0:0: Attached scsi generic sg2 type 0
    >> usb-storage: device scan complete
    >>
    >>

    > Thx !
    >
    >
    > I ran a second test with another IDE disk than the firt one... without
    > any problem... so the USB-ide bridge is ok.
    >
    > I didn't tell you that during my firt test I connected a DOM (Disk On
    > Module) to the IDE connector on the USB-ide bridge...
    >
    > But I forgot I had to cross the connexion using a 40-pin IDE cable, so
    > that the pin 1 on the USB-ide side may be connected to the pin 1 on the
    > DOM side... and so on...
    >
    > So, now when I connect my DOM to the USB-ide bridge, it seems to be
    > detected... but not very well :
    >
    >
    >
    > # dmesg
    >
    > usb 1-3: USB disconnect, address 7
    > usb 1-3: new high speed USB device using ehci_hcd and address 8
    > scsi6 : SCSI emulation for USB Mass Storage devices
    > usb-storage: device found at 8
    > usb-storage: waiting for device to settle before scanning
    > Vendor: Q) )D! Model: )0 0 2"9" Rev: *0 f
    > Type: Direct-Access ANSI SCSI revision: 02
    > SCSI device sda: 537077760 512-byte hdwr sectors (274984 MB)
    > sda: assuming drive cache: write through
    > SCSI device sda: 537077760 512-byte hdwr sectors (274984 MB)
    > sda: assuming drive cache: write through
    > sda: unknown partition table
    > Attached scsi disk sda at scsi6, channel 0, id 0, lun 0
    > usb-storage: device scan complete
    >
    >
    >
    >
    > Note that my DOM has a 128 Mbytes capacity storage !!!
    >



    Hello Lasse,

    I can't answer your last questions because I downloaded your last
    message at home... and I'm right now at work...

    The problem is that on a DOM, the connector is a female connector, as
    the connector on a 40 wire ribbon cable or on the USB-bridge.

    So I cannot connect directly the DOM to the USB-ide bridge.

    I used a 40 wire ribbon cable between the DOM and the USB-ide bridge.

    Here is the complete chain I've tested :



    M M M F F M M F
    A A A E E A A E
    L(USB-ide) <->L L <-> M (ribbon) M <-> L L <-> M (DOM)
    E E E A A E E A
    L L L
    E E E


    Note that I used MALE-MALE (40 pin) connectors between the USB-ide
    bridge and theribbon cable and between this ribbon cable and the DOM.





  5. Re: usb-ide bridge

    Previously tartinator wrote:
    > Lasse Jensen wrote:
    >> f. lecaille wrote:
    >>
    >>
    >>>usb 1-3: new high speed USB device using ehci_hcd and address 4
    >>>scsi2 : SCSI emulation for USB Mass Storage devices
    >>>usb-storage: device found at 4
    >>>usb-storage: waiting for device to settle before scanning
    >>> Vendor: Model: Rev:
    >>> Type: Direct-Access ANSI SCSI revision: 02
    >>>Attached scsi disk sda at scsi2, channel 0, id 0, lun 0
    >>>usb-storage: device scan complete
    >>>
    >>>Any idea about this issue ?

    >>
    >>
    >> It only finds the bridge, not the actual disk. Try it on another computer.
    >> Try eith another drive. Check the connectors etc. If the disk is found it
    >> should look similar to this:
    >>
    >> usb-storage: device found at 6
    >> usb-storage: waiting for device to settle before scanning
    >> scsi 10:0:0:0: Direct-Access Maxtor 6 Y080P0 0811 PQ: 0 ANSI:
    >> 0
    >> sd 10:0:0:0: [sdc] 160086528 512-byte hardware sectors (81964 MB)
    >> sd 10:0:0:0: [sdc] Test WP failed, assume Write Enabled
    >> sd 10:0:0:0: [sdc] Assuming drive cache: write through
    >> sd 10:0:0:0: [sdc] 160086528 512-byte hardware sectors (81964 MB)
    >> sd 10:0:0:0: [sdc] Test WP failed, assume Write Enabled
    >> sd 10:0:0:0: [sdc] Assuming drive cache: write through
    >> sdc: sdc1
    >> sd 10:0:0:0: [sdc] Attached SCSI disk
    >> sd 10:0:0:0: Attached scsi generic sg2 type 0
    >> usb-storage: device scan complete
    >>
    >>

    > Thx !



    > I ran a second test with another IDE disk than the firt one... without
    > any problem... so the USB-ide bridge is ok.


    > I didn't tell you that during my firt test I connected a DOM (Disk On
    > Module) to the IDE connector on the USB-ide bridge...


    > But I forgot I had to cross the connexion using a 40-pin IDE cable, so
    > that the pin 1 on the USB-ide side may be connected to the pin 1 on the
    > DOM side... and so on...


    > So, now when I connect my DOM to the USB-ide bridge, it seems to be
    > detected... but not very well :




    > # dmesg


    > usb 1-3: USB disconnect, address 7
    > usb 1-3: new high speed USB device using ehci_hcd and address 8
    > scsi6 : SCSI emulation for USB Mass Storage devices
    > usb-storage: device found at 8
    > usb-storage: waiting for device to settle before scanning
    > Vendor: Q) )D! Model: )0 0 2"9" Rev: *0 f
    > Type: Direct-Access ANSI SCSI revision: 02
    > SCSI device sda: 537077760 512-byte hdwr sectors (274984 MB)
    > sda: assuming drive cache: write through
    > SCSI device sda: 537077760 512-byte hdwr sectors (274984 MB)
    > sda: assuming drive cache: write through
    > sda: unknown partition table
    > Attached scsi disk sda at scsi6, channel 0, id 0, lun 0
    > usb-storage: device scan complete



    > Note that my DOM has a 128 Mbytes capacity storage !!!


    Looks to me that the bridge manufacturer really screwed this up.
    Not too surprising, they probably did not read the standard, but
    just tested disks from the major manufacturers. Pretty stupid,
    but also pretty common.

    Arno






  6. Re: usb-ide bridge

    Arno Wagner wrote:
    > Previously tartinator wrote:
    >
    >>Lasse Jensen wrote:
    >>
    >>>f. lecaille wrote:
    >>>
    >>>
    >>>
    >>>>usb 1-3: new high speed USB device using ehci_hcd and address 4
    >>>>scsi2 : SCSI emulation for USB Mass Storage devices
    >>>>usb-storage: device found at 4
    >>>>usb-storage: waiting for device to settle before scanning
    >>>> Vendor: Model: Rev:
    >>>> Type: Direct-Access ANSI SCSI revision: 02
    >>>>Attached scsi disk sda at scsi2, channel 0, id 0, lun 0
    >>>>usb-storage: device scan complete
    >>>>
    >>>>Any idea about this issue ?
    >>>
    >>>
    >>>It only finds the bridge, not the actual disk. Try it on another computer.
    >>>Try eith another drive. Check the connectors etc. If the disk is found it
    >>>should look similar to this:
    >>>
    >>>usb-storage: device found at 6
    >>>usb-storage: waiting for device to settle before scanning
    >>>scsi 10:0:0:0: Direct-Access Maxtor 6 Y080P0 0811 PQ: 0 ANSI:
    >>>0
    >>>sd 10:0:0:0: [sdc] 160086528 512-byte hardware sectors (81964 MB)
    >>>sd 10:0:0:0: [sdc] Test WP failed, assume Write Enabled
    >>>sd 10:0:0:0: [sdc] Assuming drive cache: write through
    >>>sd 10:0:0:0: [sdc] 160086528 512-byte hardware sectors (81964 MB)
    >>>sd 10:0:0:0: [sdc] Test WP failed, assume Write Enabled
    >>>sd 10:0:0:0: [sdc] Assuming drive cache: write through
    >>> sdc: sdc1
    >>>sd 10:0:0:0: [sdc] Attached SCSI disk
    >>>sd 10:0:0:0: Attached scsi generic sg2 type 0
    >>>usb-storage: device scan complete
    >>>
    >>>

    >>
    >>Thx !

    >
    >
    >
    >>I ran a second test with another IDE disk than the firt one... without
    >>any problem... so the USB-ide bridge is ok.

    >
    >
    >>I didn't tell you that during my firt test I connected a DOM (Disk On
    >>Module) to the IDE connector on the USB-ide bridge...

    >
    >
    >>But I forgot I had to cross the connexion using a 40-pin IDE cable, so
    >>that the pin 1 on the USB-ide side may be connected to the pin 1 on the
    >>DOM side... and so on...

    >
    >
    >>So, now when I connect my DOM to the USB-ide bridge, it seems to be
    >>detected... but not very well :

    >
    >
    >
    >
    >># dmesg

    >
    >
    >>usb 1-3: USB disconnect, address 7
    >>usb 1-3: new high speed USB device using ehci_hcd and address 8
    >>scsi6 : SCSI emulation for USB Mass Storage devices
    >>usb-storage: device found at 8
    >>usb-storage: waiting for device to settle before scanning
    >> Vendor: Q) )D! Model: )0 0 2"9" Rev: *0 f
    >> Type: Direct-Access ANSI SCSI revision: 02
    >>SCSI device sda: 537077760 512-byte hdwr sectors (274984 MB)
    >>sda: assuming drive cache: write through
    >>SCSI device sda: 537077760 512-byte hdwr sectors (274984 MB)
    >>sda: assuming drive cache: write through
    >> sda: unknown partition table
    >>Attached scsi disk sda at scsi6, channel 0, id 0, lun 0
    >>usb-storage: device scan complete

    >
    >
    >
    >>Note that my DOM has a 128 Mbytes capacity storage !!!

    >
    >
    > Looks to me that the bridge manufacturer really screwed this up.
    > Not too surprising, they probably did not read the standard, but
    > just tested disks from the major manufacturers. Pretty stupid,
    > but also pretty common.


    Not so sure...
    Because I have tested this type of connexion :

    IDE-connector(on a mother board) <-> ribbon ide cable <-> ribbon ide
    cable <-> DOM ...


    and the BIOS utility displays the same strange vendor (as the USB-ide
    bridge does it !!!) : Q) )D!


    ..........

    So the question is : may I use a ribbon cable between a DOM and a
    USB-ied bridge ???




+ Reply to Thread