[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#335229: udev: problems with firewire CDR hotplug



robertojimenoca@terra.es wrote:
> robertojimenoca@terra.es wrote:
> > robertojimenoca@terra.es wrote:
> > > > > On Oct 22, "ROBERTOJIMENOCA@terra.es" <ROBERTOJIMENOCA@terra.es> wrote:
> > > > > > I'm having problems hotplugging my firewire CDR.
> > > > > > I'm using linux-image-2.6.13-1-686_2.6.13-1 but it fails with any new
> > > > > > kernel version.
> > > > > > The error log is:
> > > > > > ieee1394: Error parsing configrom for node 0-00:1023
> > > > > > ieee1394: Node changed: 0-00:1023 -> 0-01:1023
> > > > > > ieee1394: Node added: ID:BUS[0-00:1023]  GUID[0010100305000000]
> > > > > I 
can't see how this would be related to udev.
> > > > > 
> > > > > > I had no problems with previous udev and hotplug packages and
> > > > > > linux-image-2.6.12-1-686.
> > > > 
> > > > Notice that the firewire support is utterly broken in pre 2.6.14-rc4 kernels,
> > > > and that many changes got into 2.6.14-rc4 which helped a lot.
> > > 
> > > I got it working with previous kernels. I think with 2.6.11 and 2.6.12
> > > but I can't anymore.
> > > 
> > > > Please try the 2.6.14-rc4 packages currently in experimental and confirm that
> > > > it fixes this problem or not.
> > 
> > I just tried a 
custom compiled 2.6.14-rc5 kernel without luck (just the
> > same problem)
> > 
> > I'll try the older udev + hotplug.
> 
> I tried the older udev + hotplug with the same unsuccessful results.
> 
> If someone got it working with current Debian unstable please let me know.

I just found a workaround.
If I do:
rmmod sbp2
modprobe sbp2
the drive is recognized and the device node created.
So this is probably a problem in sbp2.
Sorry for filling it directly in udev.



Prueba el Nuevo Correo Terra; Seguro, Rápido, Fiable.




Reply to: