From: Florian Idelberger <florian.idelberger@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: firewire controller
Date: Fri, 28 Jan 2005 22:26:59 +0000 [thread overview]
Message-ID: <acc911d905012814263fbc0340@mail.gmail.com> (raw)
Somehow recently the kernel (2.6.10) gives all kinds of errors,
although my firewire controller normally works on linux. I also wrote
about this to fedora and submitted a bug, because fc3 is the
distribution it occured. As the kernel messages are about the
controller not getting recognized properly and writing here, and no
real idea what else to do, here is the output:
Jan 28 22:48:57 localhost kernel: ohci1394: fw-host0: Set PHY Reg
timeout [0xffffffff/0x00004000/100]
Jan 28 22:48:57 localhost kernel: ohci1394: fw-host0: Set PHY Reg
timeout [0xffffffff/0x00004000/100]
Jan 28 22:48:58 localhost hald[3990]: Timed out waiting for hotplug
event 819. Rebasing to 820
Jan 28 22:49:03 localhost kernel: PCI: Via IRQ fixup
Jan 28 22:49:03 localhost kernel: PCI: Enabling device 0000:06:00.0
(0080 -> 0083)
Jan 28 22:49:03 localhost kernel: ACPI: PCI interrupt 0000:06:00.0[A]
-> GSI 11 (level, low) -> IRQ 11
Jan 28 22:49:04 localhost wait_for_sysfs[17698]: error: unknown bus,
please report to <linux-hotplug-devel@lists.sourceforge.net>
'ieee1394'
Jan 28 22:49:04 localhost wait_for_sysfs[17698]: either wait_for_sysfs
(udev 039) needs an update to handle the device
'/devices/pci0000:00/0000:00:11.1/0000:06:00.0/fw-host0' properly
(unknown bus) or the sysfs-support of your device's driver needs to be
fixed, please report to <linux-hotplug-devel@lists.sourceforge.net>
Jan 28 22:49:04 localhost kernel: ohci1394: fw-host0: OHCI-1394 1.1
(PCI): IRQ=[11] MMIO=[11000000-110007ff] Max Packet=[65536]
Jan 28 22:49:04 localhost ieee1394.agent[17707]: ... no drivers for
IEEE1394 product 0x/0x/0x
Jan 28 22:49:04 localhost kernel: ieee1394: Error parsing configrom
for node 0-00:1023
Jan 28 22:49:04 localhost wait_for_sysfs[17736]: error: unknown bus,
please report to <linux-hotplug-devel@lists.sourceforge.net>
'ieee1394'
Jan 28 22:49:04 localhost wait_for_sysfs[17736]: either wait_for_sysfs
(udev 039) needs an update to handle the device
'/devices/pci0000:00/0000:00:11.1/0000:06:00.0/fw-host0/01ac9120000002e7'
properly (unknown bus) or the sysfs-support of your device's driver
needs to be fixed, please report to
<linux-hotplug-devel@lists.sourceforge.net>
Jan 28 22:49:05 localhost kernel: ieee1394: Error parsing configrom
for node 0-01:1023
Jan 28 22:49:05 localhost wait_for_sysfs[17765]: error: unknown bus,
please report to <linux-hotplug-devel@lists.sourceforge.net>
'ieee1394'
Jan 28 22:49:05 localhost wait_for_sysfs[17765]: either wait_for_sysfs
(udev 039) needs an update to handle the device
'/devices/pci0000:00/0000:00:11.1/0000:06:00.0/fw-host0/400401012800c037'
properly (unknown bus) or the sysfs-support of your device's driver
needs to be fixed, please report to
<linux-hotplug-devel@lists.sourceforge.net>
Jan 28 22:49:05 localhost ieee1394.agent[17776]: ... no drivers for
IEEE1394 product 0x/0x/0x
Jan 28 22:49:05 localhost ieee1394.agent[17750]: ... no drivers for
IEEE1394 product 0x/0x/0x
Jan 28 22:49:06 localhost wait_for_sysfs[17793]: error: unknown bus,
please report to <linux-hotplug-devel@lists.sourceforge.net>
'ieee1394'
Jan 28 22:49:06 localhost wait_for_sysfs[17793]: either wait_for_sysfs
(udev 039) needs an update to handle the device
'/devices/pci0000:00/0000:00:11.1/0000:06:00.0/fw-host0/400401012800c037/400401012800c037-0'
properly (unknown bus) or the sysfs-support of your device's driver
needs to be fixed, please report to
<linux-hotplug-devel@lists.sourceforge.net>
Jan 28 22:49:06 localhost ieee1394.agent[17796]: ... no drivers for
IEEE1394 product 0x/0x/0x
That's what I get after reinserting my firewire pcmcia card at
runtime, and plugging a firewire drive in. Funny thing, sometimes it
works, (although I don't know, wheter with or without the message from
the kernel) and my ipod even works more often (not always).
Would be cool if anybody'd be able t help me.
Florian
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2005-01-28 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 22:26 Florian Idelberger [this message]
2005-01-29 1:18 ` firewire controller Kay Sievers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=acc911d905012814263fbc0340@mail.gmail.com \
--to=florian.idelberger@gmail.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).