Bug 9760
Summary: | Firewire Card Not Detected by JuJu Stack. | ||
---|---|---|---|
Product: | Drivers | Reporter: | Joshua Schmidlkofer (joshland) |
Component: | IEEE1394 | Assignee: | Stefan Richter (stefanr) |
Status: | CLOSED CODE_FIX | ||
Severity: | normal | CC: | jarod |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.24-rc7 | Subsystem: | |
Regression: | --- | Bisected commit-id: |
Description
Joshua Schmidlkofer
2008-01-15 19:18:08 UTC
After the two "giving up" messages, do /dev/fw0 and /sys/bus/firewire/devices/fw0/ still exist? I am waiting for the next Maintenance Window to get this info. Is there anything else I can do at the same time? If access to the hardware is limited, then this is troublesome. It's already difficult to go after this without me having direct access to affected hardware to directly experiment with it to get to an idea about it. However, if we are lucky then this is the same problem as Jarod is currently working on. https://bugzilla.redhat.com/show_bug.cgi?id=429598 So maybe we get a patch for your testing pleasure some time soon. Since you run Gentoo and 2.6.24-rc and have both FireWire stacks installed --- and if you don't need FireWire 24/7 --- you could hopefully switch between the working old drivers and patched new drivers when we get a patch out before a maintenance window at your site, right? Yep, this looks like the same thing I'm debugging right now. Hoping to have the fix isolated by the end of the day... :) We have a patch series now which fixes similar or same issues on Jarod's test setup. I will prepare a combo patch for you to test later today. Please try patch v610 or later from http://me.in-berlin.de/~s5r6/linux1394/updates/. The patch for 2.6.24 is also applicable to late 2.6.24-rc*s. If you have the firewire-* drivers configured as modules, you only need to "make modules; sudo make modules_install" after patching and to reload the firewire modules. I.e. no reboot necessary. The mentioned patches have been committed to Linus' tree. Please reopen the bug if the problem persists with either Linus' latest or with a kernel patched with my updates. |