rajeevramdas@xxxxxxxxxxxx wrote:
> I just installed ubuntu 6 on my dell latitude d600 laptop.
> Kernel is now 2.6.15-25-386.
>
> I have an external hard disk (Firewire, enclosure uses the oxford
> chipset) that used to work with ubuntu 5 (Breezy), now when i plug
> that in (Using a pcmcia firewire card), it gives the following
> messages and does not recognize the drive.
What kernel version did Ubuntu 5 come with?
> i think that have the latest libraw1394, for ubuntu.
> sudo dpkg -s libraw1394-5 | grep Version
> Version: 0.10.1-1.1ubuntu1
Libraw1394 is not involved in access to FireWire disks.
...
> [17179589.056000] ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[11]
> MMIO=[f6000000-f60007ff] Max Packet=[1024]
OK.
...
> [17179590.080000] ieee1394: The root node is not cycle master capable;
> selecting a new root node and resetting...
Should be no problem. However you could try if it's becoming better if
you switch the "select a new root" routine off:
- disconnect the harddisk
- unload all FireWire drivers:
"lsmod | grep 1394" shows which are present,
unload depending modules first: "modprobe -r sbp2 raw1394 eth1394"
unload the base driver last: "modprobe -r ieee1394"
- reload the base driver with a special option:
"modprobe ieee1394 disable_irm=1"
then load the host adapter driver: "modprobe ohci1394"
- plug the disk in.
> [17179590.200000] sbp2: $Rev: 1306 $ Ben Collins <bcollins@xxxxxxxxxx>
> [17179590.200000] ieee1394: sbp2: Driver forced to serialize I/O
> (serialize_io=1)
> [17179590.200000] ieee1394: sbp2: Try serialize_io=0 for better performance
> [17179590.380000] ieee1394: Node added: ID:BUS[0-00:1023]
> GUID[0050770e00071002]
> [17179590.380000] ieee1394: Host added: ID:BUS[0-01:1023]
> GUID[0011060000009467]
> [17179590.380000] scsi0 : SCSI emulation for IEEE-1394 SBP-2 Devices
> [17179591.592000] ieee1394: sbp2: Logged into SBP-2 device
> [17179591.592000] ieee1394: Node 0-00:1023: Max speed [S400] - Max payload
> [1024]
OK.
> [17179597.092000] ieee1394: sbp2: aborting sbp2 command
> [17179597.092000] 0:0:0:0:
> [17179597.092000] command: Inquiry: 12 00 00 00 24 00
> [17179607.092000] ieee1394: sbp2: aborting sbp2 command
> [17179607.092000] 0:0:0:0:
> [17179607.092000] command: Test Unit Ready: 00 00 00 00 00 00
> [17179607.092000] ieee1394: sbp2: reset requested
> [17179607.092000] ieee1394: sbp2: Generating sbp2 fetch agent reset
...
> [17179657.100000] 0:0:0:0: scsi: Device offlined - not ready after error
> recovery
> [17179657.100000] ieee1394: sbp2: scsi_add_device failed (-19)
Actually the disk was recognized by sbp2 but it could not be made
available as a SCSI device because the very first SCSI command which was
sent was not completed.
> [17179657.100000] scsi1 : SCSI emulation for IEEE-1394 SBP-2 Devices
> [17179678.908000] ieee1394: sbp2: Error logging into SBP-2 device - login
> timed-out
> [17179678.908000] sbp2: probe of 0050770e00071002-0 failed with error -16
This is a very strong hint for a faulty device firmware or otherwise bad
hardware. Right after sbp2 failed to start up the unit, the ieee1394
base driver loads sbp2 again for the same unit. However now the unit
refuses to talk with sbp2 right from the beginning. I could imagine two
reasons why ieee1394 immediately loaded sbp2 again for the same unit:
- The disk's firmware reset the bus after it already made itself
visible as an SBP-2 device. Such behaviour would not be compliant to
SBP-2. Or
- the bus has an electrical instability which was seen by the
controller as a bus reset.
You said the enclosure was based on an Oxford chip. Did you look inside
it or did you trust some product specification?
The device's GUID of 0050770e00071002 comes from Prolific Technology
Inc., therefore and because of the behaviour I suspect it is actually
based on a Prolific chip.
If it is Prolific based, please check if you could update the firmware
of the disk. You need an uploader and the firmware binary from
http://www.prolific.com.tw/. The uploader runs only under Windows. Very
old revisions of the chip cannot be updated at all. Some revisions need
to be updated in two steps as detailed at Prolific's website.
BTW, I have a Prolific based DVD-RW which _sometimes_ features a similar
behaviour. I.e. the first contact fails (but I believe with different
error messages) and a second attempt is made by Linux immediately (like
with your disk). I did not take the time yet to look into it further or
to check whether my DVD-RW's bridge has old firmware. The bad behaviour
does not occur always. When it does, switching the enclosure off and on
again may help, sometimes only after a few attempts.
--
Stefan Richter
-=====-=-==- -=== --=-=
http://arcgraph.de/sr/
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
|
