Hi On 11/01/07, dann frazier <[EMAIL PROTECTED]> wrote:
hey James, Can you provide a log of the errors you get when loading raw1394? I'm unable to reproduce with 2.6.18-8. gscanbus works fine for me; granted, I don't actually have any devices on my bus (I don't own any).
Everything worked fine with 2.6.18-8 today. I tried repeatedly on December 18th to no avail. Something else must have changed since then to fix things up...? Anyway, I guess I can only agree with "can't reproduce". Sorry I can't dig out the errors I was consistently getting. Here is the "all working fine log" anyway: dmesg log as I insert cardbus 1394 card (all okay): pccard: CardBus card inserted into slot 1 ieee1394: Initialized config rom entry `ip1394' PCI: Enabling device 0000:07:00.0 (0000 -> 0002) ACPI: PCI Interrupt 0000:07:00.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11 PCI: Setting latency timer of device 0000:07:00.0 to 64 ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[11] MMIO=[c4004000-c40047ff] Max Packet=[2048] IR/IT contexts=[4/8] ieee1394: Host added: ID:BUS[0-00:1023] GUID[0000000000010001] eth1394: eth1: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0) dmesg log as I modprobe raw1394 (hmmm, seems fine this time!): ieee1394: raw1394: /dev/raw1394 device initialized dmesg log as I plug in a JVC camcorder (all okay): ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting... ieee1394: Node added: ID:BUS[0-00:1023] GUID[00808803094801ab] ieee1394: Node changed: 0-00:1023 -> 0-01:1023 gscanbus runs fine and detects the JVC device. modprobe video1394 works without error and the camera is fully useable. Cheers James -- James McCaw [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
