I don't have test machines with Firewire, so unfortunately I can't test
it. Can someone else try this with Firewire?
I tested that it is not working with USB mass storage. I think USB
problem is more serious, as it is much more common.
--
usb-mass storage disk isn't recognized the right way
http
This bug refers to two problems. One in firewire and the other in usb.
Can you test that it does or doesn't work with firewire?
--
usb-mass storage disk isn't recognized the right way
https://launchpad.net/bugs/36619
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu
Thanks for releasing a fix for this serious problem. Unfortunately, the
fix does not seem to work for me.
I made a standard system upgrade. After that, I have 'uname -srv' "Linux
2.6.15-27-k7 #1 SMP PREEMPT Sat Sep 16 02:35:20 UTC 2006", 'grep DESC
/etc/lsb-release' 'DISTRIB_DESCRIPTION="Ubuntu 6.
Fixes related to this went into dapper-security. Please test it.
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Unconfirmed => Fix Released
--
usb-mass storage disk isn't recognized the right way
https://launchpad.net/bugs/36619
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
The regression I referred to in comment 4 went into Ubuntu Dapper too, as part
of a bugfix for other devices. Ubuntu Edgy has the regression fixed:
http://www.kernel.org/git/?p=linux/kernel/git/bcollins/ubuntu-2.6.git;a=commitdiff;h=a54c9d30dbb06391ec4422aaf0e1dc2c8c53bd3e
--
usb-mass storage di
The PL3507 is widely known for a weak FireWire implementation and
sometimes extremely bad firmware. USB is supposed to work better on this
though.
As far as sbp2 is concerned, failures to connect are perhaps fixed
upstream. There was a regression in sbp2 concerning some PL3507 in Linux
2.6.16...2.
