Hi,
> > No, that looked like a very low-level chip design problem. As
> > far as I understand, the BIOS is not involved in this. Maybe a
> > workaround in the ohci1394 driver could do something about it,
> > maybe not.
>
> hmm, sounds really bad.
today i asked a collegue that has bought exactly the same
motherboard (Asus P4C800E-deluxe). He is using windows and
has no problems with the IEEE1394.
So i guess they wrote some workaround for that hardware.
> 2.4.26 fails with no message in /var/log/messages and a
> segmentation fault. I disabled "Excessive debug output" for
> this one as it floods the log files. I'll do it once more
> with that option enabled.
I just tried 2.4.26 with excessive debug output. "dvgrab"
still hangs and needs to be stopped with Ctrl-C and then
says "Segmentation fault".
In /var/log/messages i get the messages in the attached text
file. I attached it as text so the formatting is not changed.
Is there something that i possibly did wrong in kernel
configuration? I somehow have the strange feeling that
i messed something up. Would it make sense to change some
kernel settings?
Best regards,
Torsten.
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
mailing list Linux1394-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux1394-user
This archive was generated by hypermail 2.1.8 : Mon 02 May 2005 - 09:16:48 CEST