Re: Problems with Firewire and -mm kernels

[Rogério Brito]

On Jun 28 2005, Stefan Richter wrote:
> But again, I don't see how -mm and the stock kernel should differ to that
> respect.

Well, I can only say that this problem is 100% reproducible with my
enclosure.

Perhaps more data is needed here? The 2.6.12 kernel is able to see the
drive without any problems while the -mm kernels aren't. I can provide
anything that you guys want.

Right now, I am using a stock/vanilla kernel, for using the drive.

> You could load ieee1394 with a new parameter that supresses the "Root 
> node is not cycle master capable..." routine:
> # modprobe ieee1394 disable_irm=1
> before ohci1394 and the other 1394 related drivers are loaded.

Ok, I'll disable hotplug, udev etc and try to boot into single user mode
for that as soon as I wake up (I'm going to bed right now---had a lot of
work done for a day).

> > ieee1394: Node changed: 0-01:1023 -> 0-00:1023
> > ieee1394: Node suspended: ID:BUS[0-00:1023]  GUID[0050c501e00010e8]
> 
> What caused these two messages? Did you disconnect the drive at this
> point?

Yes, I did. In both cases, just to see if any messages issued to dmesg were
different when unplugging the drive.

If you have other ideas or if any extra information is necessary, please,
let me know and I'll do my best to provide what you need.


Thank you all for the interest, Rogério.

-- 
Rogério Brito : rbrito@xxxxxxxxxx : http://www.ime.usp.br/~rbrito
Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat:  http://freshmeat.net/projects/algorithms/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/