Mailinglist Archive: opensuse (3337 mails)

< Previous Next >
external firewire hdd on suse 10.1?
  • From: Mathias Homann <admin@xxxxxxxxxx>
  • Date: Sun, 23 Apr 2006 13:24:18 +0200
  • Message-id: <200604231324.20761.admin@xxxxxxxxxx>
Hi,


i have an external harddisk which has usb 2.0, and firewire. right
now, i'm running 9.2 with all updates applied.
When i try to connect the disk via firewire, it does not work (the
disk itself is seen, but not the partition on it), and "fdisk -l"
hangs after printing the partition table of my internal ide disk.
Here's what /var/log/messages says about it:

Apr 23 10:24:07 gildor kernel: ieee1394: Current remote IRM is not
1394a-2000 compliant, resetting...
Apr 23 10:24:08 gildor kernel: ieee1394: Error parsing configrom for
node 0-00:1023
Apr 23 10:24:08 gildor kernel: ieee1394: Node changed: 0-00:1023 ->
0-01:1023
Apr 23 10:24:20 gildor kernel: ieee1394: Node added: ID:BUS[0-00:1023]
GUID[0050770e00071002]
Apr 23 10:24:20 gildor kernel: ieee1394: unsolicited response packet
received - no tlabel match
Apr 23 10:24:25 gildor /sbin/hotplug[5809]: ... no drivers for
IEEE1394 product 0x/0x/0x
Apr 23 10:24:25 gildor /sbin/hotplug[5811]: ... no drivers for
IEEE1394 product 0x/0x/0x
Apr 23 10:24:25 gildor kernel: sbp2: $Rev: 1219 $ Ben Collins
<bcollins@xxxxxxxxxx>
Apr 23 10:24:25 gildor kernel: scsi0 : SCSI emulation for IEEE-1394
SBP-2 Devices
Apr 23 10:24:26 gildor kernel: ieee1394: sbp2: Logged into SBP-2
device
Apr 23 10:24:26 gildor kernel: ieee1394: Node 0-00:1023: Max speed
[S400] - Max payload [2048]
Apr 23 10:24:26 gildor kernel: Vendor: IC35L090 Model: AVV207-0
Rev:
Apr 23 10:24:26 gildor kernel: Type: Direct-Access
ANSI SCSI revision: 06
Apr 23 10:24:26 gildor kernel: SCSI device sda: 160836480 512-byte
hdwr sectors (82348 MB)
Apr 23 10:24:26 gildor kernel: sda: asking for cache data failed
Apr 23 10:24:26 gildor kernel: sda: assuming drive cache: write
through
Apr 23 10:24:36 gildor /etc/dev.d/block/50-hwscan.dev[5986]: new block
device /block/sda
Apr 23 10:24:36 gildor /etc/dev.d/block/51-subfs.dev[5996]: mount
block device /block/sda
Apr 23 10:24:56 gildor kernel: ieee1394: sbp2: aborting sbp2 command
Apr 23 10:24:56 gildor kernel: Test Unit Ready 00 00 00 00 00
Apr 23 10:25:26 gildor kernel: ieee1394: sbp2: aborting sbp2 command
Apr 23 10:25:26 gildor kernel: Test Unit Ready 00 00 00 00 00
Apr 23 10:25:26 gildor kernel: ieee1394: sbp2: reset requested
Apr 23 10:25:26 gildor kernel: ieee1394: sbp2: Generating sbp2 fetch
agent reset
Apr 23 10:25:28 gildor kernel: ieee1394: Node changed: 0-01:1023 ->
0-00:1023
Apr 23 10:25:28 gildor kernel: ieee1394: Node suspended:
ID:BUS[0-00:1023] GUID[0050770e00071002]
Apr 23 10:25:50 gildor init: Switching to runlevel: 0
Apr 23 10:25:56 gildor kernel: bootsplash: status on console 0 changed
to on
Apr 23 10:25:56 gildor kernel: ieee1394: sbp2: aborting sbp2 command
Apr 23 10:25:56 gildor kernel: Test Unit Ready 00 00 00 00 00
Apr 23 10:25:56 gildor kernel: ieee1394: sbp2: hpsb_node_write failed.
Apr 23 10:25:56 gildor kernel:
Apr 23 10:25:56 gildor kernel: ieee1394: sbp2: reset requested
Apr 23 10:25:56 gildor kernel: ieee1394: sbp2: Generating sbp2 fetch
agent reset
Apr 23 10:25:56 gildor kernel: ieee1394: sbp2: hpsb_node_write failed.
Apr 23 10:25:56 gildor kernel:


now my question: will it work on suse 10.1?

the chipset in the external case is a prolific chip, as identified
like this by lsusb when connected to usb:

gildor:/var/log # lsusb
Bus 004 Device 003: ID 067b:3507 Prolific Technology, Inc.


bye,
MH

--
gpg key fingerprint: 5F64 4C92 9B77 DE37 D184 C5F9 B013 44E7 27BD
763C

< Previous Next >
Follow Ups