Problems with FireWire and Kernel 2.6.14

[Les Mikesell]

On Wed, 2005-11-30 at 10:19, Claude Jones wrote:
> On Tuesday 29 November 2005 09:11 pm, D. D. Brierton wrote:
> > On Tue, 2005-11-29 at 18:20 +0000, D. D. Brierton wrote:
> > > Good to know it's not just me. I've just searched bugzilla and I can't
> > > see this reported with regard to these latest kernels. Does anyone know
> > > if this is in bugzilla? If not I'll report it.
> >
> > Reported:
> >
> > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=174537
> >
> 
> I saw this flash by, yesterday, while going through a ton of mail, and dealing 
> with other issues, and was surprised. I just read the bug report's 
> declaration that "FireWire does not appear to be working in the 2.6.14 FC4 
> kernels". I had the opposite experience, so this seems to be something that 
> has to be parsed a bit more. I installed a new firewire card just yesterday, 
> because I'd had problems with an older D-Link multi-USB/Firewire card, which 
> had also given problems on Windows systems. I installed a Trendnet TFU-H33PI 
> which is a 3 firewire and 3 USB PCI card. I started up the computer and 
> connected an external Maxtor 250 GB via the firewire port (it can talk USB or 
> Firewire), and the dialog window popped up immediately asking what I'd like 
> to do. I clicked on "Open" and the drive was mounted and a Konqueror window 
> opened and showed me the contents of the drive. Next, I connected my DV 
> camera, a Sony VX1000, and the camera was recognized, and when I opened Kino, 
> I was able to successfully capture. 
> This is on the latest kernel...2.6.14.1644 

The generic firewire level is fine - it is the disk handling that is
broken.  It still gets to the point of making the disk device
appear in /proc/scsi/scsi with the correct name, but the /dev/sdx
devices aren't created and no partitions are recognized.

-- 
  Les Mikesell
    lesmikesell at gmail.com