From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/312.5.1 (KHTML, like Gecko) Safari/312.3.1
Description of problem:
the system fails to recognise a firewire drive attached
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.plug in drive
Actual Results: drive not recognised
Expected Results: drive recognised
Created attachment 122216 [details]
output of dmesg attached
output of uname -a:
Darwin nindalf 7.9.0 Darwin Kernel Version 7.9.0: Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu
-517.12.7.obj~1/RELEASE_PPC Power Macintosh powerpc
sorry, correct info:
Linux memiki 2.6.14-1.1644_FC4 #1 Sun Nov 27 03:27:21 EST 2005 ppc ppc ppc GNU/Linux
Based on this:
scsi: Device offlined - not ready after error recovery: host 2 channel 0 id 0 lun 0
and a similar bug I've seen for RHEL bug #175188 I'd wager it's this fix:
A few things - you're not on the latest FC 4 update kernel
2.6.14-1.1653_FC4 which looks as if it has this fix in already, you can try yum
update kernel to get the latest update.
If the latest update does not resolve - can you try attaching the
device/powering on the device after doing:
echo 12295 > /sys/module/scsi_mod/scsi_logging_level
and attach the resulting log.
Created attachment 122217 [details]
new dmesg output
I've upgraded to kernel 2.6.14-1.1653_FC4 but still no luck
This is a mass-update to all currently open kernel bugs.
A new kernel update has been released (Version: 2.6.15-1.1830_FC4)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO_REPORTER state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
Closing per previous comment.