Bug 11638 - firewire_ohci: probe of 0000:01:0a.0 failed with error -5
Summary: firewire_ohci: probe of 0000:01:0a.0 failed with error -5
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: Drivers
Classification: Unclassified
Component: IEEE1394 (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_ieee1394
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-24 05:03 UTC by sangu
Modified: 2010-01-06 21:53 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.27-0.347.rc7.git1.fc10.i686
Subsystem:
Regression: No
Bisected commit-id:


Attachments
lspci -vvv (26.88 KB, text/plain)
2008-09-24 05:04 UTC, sangu
Details
dmesg (52.61 KB, text/plain)
2008-09-24 05:06 UTC, sangu
Details

Description sangu 2008-09-24 05:03:11 UTC
kernel version:
Distribution: Fedora
Hardware Environment:
CPU : AMD Phenom X4 9850BE
MB : ASUS m3n78 pro
MB Chipset : nForce 730a
FireWire (IEEE 1394): Agere Systems FW323 (rev 70)

Problem Description:
$ dmesg 
[...]
ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
firewire_ohci 0000:01:0a.0: PCI INT A -> Link[APC4] -> GSI 19 (level, low) -> IR
Q 19
gameport: EMU10K1 is pci0000:01:09.1/gameport0, io 0xc800, speed 562kHz
firewire_ohci: failed to set phy reg bits.
firewire_ohci 0000:01:0a.0: PCI INT A disabled
firewire_ohci: probe of 0000:01:0a.0 failed with error -5
[...]

device name doesn't  be creatived  in /dev/
Comment 1 sangu 2008-09-24 05:04:45 UTC
Created attachment 18002 [details]
lspci -vvv
Comment 2 sangu 2008-09-24 05:06:15 UTC
Created attachment 18003 [details]
dmesg
Comment 3 Stefan Richter 2008-09-24 05:55:26 UTC
Could you try with the older alternative ohci1394 driver?  For example, boot from a live CD of another Linux distro if you don't know how to install the ohci1394 driver on Fedora.  Also, do you have the means to test the FireWire port with a different OS?
Comment 4 Stefan Richter 2010-01-06 21:53:15 UTC
Feel free to reopen if you were able to gather more information (e.g. from a test with the old drivers or with a newer Fedora kernel).

Note You need to log in before you can comment on or make changes to this bug.