Again, thanks Stefan for the suggestions. I followed up on this and tried getting the Tandberg VXA-2 tape drive and PacketLoader tape library to mount with the new drivers.
Booted off a jaunty alpha 3 live cd, which gives kernel 2.6.28-4-generic. Then, with the tape drive not plugged in, did modprobe -r ohci1394 modprobe firewire-ohci modprobe firewire-sdp2 so far, this gives the following in the kern.log: Feb 4 00:07:14 ubuntu kernel: [ 152.065612] ieee1394: Node removed: ID:BUS[0-00:1023] GUID[0030934100002325] Feb 4 00:07:28 ubuntu kernel: [ 166.296014] firewire_ohci: Added fw-ohci device 0000:03:01.0, OHCI version 1.10 Feb 4 00:07:29 ubuntu kernel: [ 166.796127] firewire_core: created device fw0: GUID 0030934100002325, S800 I then plug in the tape drive and the following shows up: firewire_core: phy config: card 0, new root=ffc1, gap_count=5 scsi3 : SBP-2 IEEE-1394 firewire_sbp2: Workarounds for fw1.0: 0x2 (firmware_revision 0x000201, model_id 0x000000) scsi4 : SBP-2 IEEE-1394 firewire_sbp2: Workarounds for fw1.1: 0x2 (firmware_revision 0x000201, model_id 0x000000) firewire_core: created device fw1: GUID 0010100319003177, S800 firewire_sbp2: fw1.0: logged in to LUN 0000 (0 retries) scsi 3:0:0:0: Sequential-Access EXABYTE VXA-2a 2152 PQ: 0 ANSI: 2 scsi 3:0:0:0: Attached scsi generic sg2 type 1 firewire_sbp2: fw1.1: logged in to LUN 0001 (0 retries) firewire_sbp2: released fw1.0, target 3:0:0 firewire_sbp2: released fw1.1, target 4:0:0 st: Version 20080504, fixed bufsize 32768, s/g segs 256 Driver 'st' needs updating - please use bus_type methods osst :I: Tape driver with OnStream support version 0.99.4 osst :I: $Id: osst.c,v 1.73 2005/01/01 21:13:34 wriede Exp $ Driver 'osst' needs updating - please use bus_type methods firewire_core: giving up on config rom for node id ffc1 firewire_core: phy config: card 0, new root=ffc1, gap_count=5 firewire_core: giving up on config rom for node id ffc0 scsi5 : SBP-2 IEEE-1394 firewire_sbp2: Workarounds for fw1.0: 0x2 (firmware_revision 0x000201, model_id 0x000000) scsi6 : SBP-2 IEEE-1394 firewire_sbp2: Workarounds for fw1.1: 0x2 (firmware_revision 0x000201, model_id 0x000000) firewire_core: created device fw1: GUID 0010100319003177, S800 firewire_core: phy config: card 0, new root=ffc0, gap_count=5 firewire_sbp2: released fw1.0, target 5:0:0 firewire_sbp2: released fw1.1, target 6:0:0 firewire_core: phy config: card 0, new root=ffc1, gap_count=5 firewire_core: giving up on config rom for node id ffc0 Looks like it initially figured out it was a VXA-2 and created the sg device, but then it was released and something went on with the tape driver. This seems to loop forever, creating two more devices, then giving up on them, over and over again. Is there something else I need to do about the tape driver? Other ideas for testing on jaunty? -- External ieee1394 drive not recognized 2.6.27-5 https://bugs.launchpad.net/bugs/279342 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
