** Changed in: linux (Ubuntu Lucid)
Status: Confirmed = Triaged
--
Some firewire disks not working under 10.04
https://bugs.launchpad.net/bugs/548513
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Tags added: lucid
** Tags removed: kernel-series-unknown
--
Some firewire disks not working under 10.04
https://bugs.launchpad.net/bugs/548513
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I too was experiencing this problem on Ubuntu 10.4 with my Western
Digital 500GB My Book external hard drive connected via firewire.
I can confirm that after manually patching the file my external drive is
recognized by Ubuntu. (Note: installing Jerone's patch via command line
would not work for
I had reported back in Bug #543488 that with Lucid, it was not possible
to mount some firewire hard disks either with the old or new stack. I
had made the test with Lucid Beta 1.
Today, I'm updating the status with Lucid Beta 2:
It is working out-of-the-box (without patch or other configuration),
Another test with Lucid Beta 2...
I have migrated to the new firewire kernel stack and I have applied the above
mentionned patch. In this case, I can use the firewire HDD.
So here is the whole summary:
1. with Lucid Beta 2, firewire HDD is using the old kernel stack and is
working
I've found, what I think, is a good solution to the problem for now.
The hdparm udev rule that is launching hdparm. What hdparm is tyring to
do is enable ATA passthrough for drives that claim to support it (most
newer drives do). The problem is there doesn't seem to be proper kernel
support or
Here is a patch for the hdparm package.
** Attachment added: hdparm_debian_udev_fix
http://launchpadlibrarian.net/43361088/hdparm_debian_udev_fix
--
Some firewire disks not working under 10.04
https://bugs.launchpad.net/bugs/548513
You received this bug notification because you are a member
Yes, this is probably an appropriate workaround (assuming it works, but
it does look plausible) - but hdparm is (potentially) doing other things
as well as enabling ATA passthrough, so I'd like to allow the active
upstream discussion of this problem to proceed a bit longer before we
slam a
** Tags added: patch
--
Some firewire disks not working under 10.04
https://bugs.launchpad.net/bugs/548513
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
Confirming the workaround by Jerone to work, thanks!
--
Some firewire disks not working under 10.04
https://bugs.launchpad.net/bugs/548513
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Just to let everyone know. The comment I made about a 2nd issue with
udev was invalid. Had something in my other install.
Though on my new install apport is giving a false error about the
kernel. Though no errors reported in dmesg and the firewire drive is
working fine (with the workaround fix).
The issue here is the hdparm command is launched by udev. It then attempts to
try to activate ata pass through. This then causes the drive to fail.
bug 515023
But disabling hdparm from being lauched by udev gets around the issue.
Then the drive works fine.
I tested the latest hdparm (9.28) and
Renaming the file mentioned in #15 works for me as well,
05:00.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
--
Some firewire disks not working under 10.04
https://bugs.launchpad.net/bugs/548513
You received this bug notification because you are a member of Ubuntu
sudo mv /lib/udev/rules.d/85-hdparm.rules
/lib/udev/rules.d/85-hdparm.disabled fixes this issue for me. I am using
the new firewire subsystem.
jer...@hephaestus:~$ lsmod | grep firewire
firewire_sbp2 15009 2
firewire_ohci 25343 0
firewire_core 51537 2 firewire_sbp2,firewire_ohci
crc_itu_t 1715 1
Please see bug 515023
--
Some firewire disks not working under 10.04
https://bugs.launchpad.net/bugs/548513
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
@Jeremy
Ok looks to be an issue with hdparm in user space. Can you
test on a clean install of Lucid with the kernel currently shipping.
** Also affects: hdparm (Ubuntu)
Importance: Undecided
Status: New
--
Some firewire disks not working under 10.04
*** This bug is a duplicate of bug 543488 ***
https://bugs.launchpad.net/bugs/543488
** This bug has been marked a duplicate of bug 543488
Lucid Beta 1 cannot use firewire hard disk
--
Some firewire disks not working under 10.04
https://bugs.launchpad.net/bugs/548513
You received this
** This bug is no longer a duplicate of bug 543488
Lucid Beta 1 cannot use firewire hard disk
--
Some firewire disks not working under 10.04
https://bugs.launchpad.net/bugs/548513
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
@Manoj
I have a theory after some other partically related issues with a
USB 3.0 drive found in a disscussion on the udev mailing list. Can you remove
/lib/udev/85-hdparm.rules reboot and see it works.
It may be hdparm at fault?
--
Some firewire disks not working
** Changed in: oem-priority
Status: New = In Progress
--
Some firewire disks not working under 10.04
https://bugs.launchpad.net/bugs/548513
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Looks like we are using the older firewire stack, I the older stack is
reported not to work as well with the newer kernel (2.6.32).
https://ieee1394.wiki.kernel.org/index.php/Release_Notes#Linux_2.6.32
((scroll up for 2.6.33 notes).
I tried blacklising the old stack and using the new stack but I
@jerone can you please try the kernel in
http://people.ubuntu.com/~manjo/lp548513-lucid/ and report back here?
** Changed in: linux (Ubuntu Lucid)
Status: Confirmed = Incomplete
--
Some firewire disks not working under 10.04
https://bugs.launchpad.net/bugs/548513
You received this bug
@Manoj
Tried it out. Did not work. I've attached the dmesg.
Still same issue can see the device .. but when something
tries to access it it can't.
Manoj also if you need a machine or device call me or email
me. Can meet up and can let you borrow a device to
@Jeremy
The drive requires an external power source, so tried that case.
Also played around with powering it up and down.
@Brian
Actually are you able to mount and write to the disk? I saw this
too with one system .. but when trying to access the disk
I've seen this issue with a Ricoh e832 firewire card. Same behavior
(can see the disk in /proc/partitions though gparted cant see it and it
can't be mounted). Attaching dmesg
** Attachment added: dmesg.txt
http://launchpadlibrarian.net/42089732/dmesg.txt
--
Some firewire disks not working
@Jerone
Unfortunately, I think the firewire disk we have here is the same one you have,
so I'd expect the results to be similar
--
Some firewire disks not working under 10.04
https://bugs.launchpad.net/bugs/548513
You received this bug notification because you are a member of Ubuntu
Bugs, which
@Jerone - I was able to write to the disk.
--
Some firewire disks not working under 10.04
https://bugs.launchpad.net/bugs/548513
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
27 matches
Mail list logo
