From: Wolfgang Pfeiffer <roto@gmx.net>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linuxppc-dev@ozlabs.org, billfink@mindspring.com,
linux1394-devel@lists.sourceforge.net
Subject: Re: Broken Firewire 400/SCSI on ppc Powerbook5,8
Date: Wed, 23 Aug 2006 02:28:01 +0200 [thread overview]
Message-ID: <20060823002801.GA2709@localhost> (raw)
In-Reply-To: <44E6D634.3000207@s5r6.in-berlin.de>
Hi Stefan,
Hi All
On Sat, Aug 19, 2006 at 11:13:24AM +0200, Stefan Richter wrote:
[ ... ]
> The fact that Linux on the AlBook gets at least as far as "ieee1394:
> Error parsing configrom for node 0-00:1023" indicates that not all hope
> is lost. If you have got the time, compile the 1394 drivers for verbose
> logging and send the log. Don't crosspost the log if it gets too big.
Some tests on the Alubook:
I compiled a fresh git kernel now with verbose ieee logging turned on.
$ uname -r
2.6.18-rc4-ieeeverbose-gef7d1b24-dirty
$ zgrep 4_VERBOS /proc/config.gz
CONFIG_IEEE1394_VERBOSEDEBUG=y
Before starting the FW disk I removed all ieee drivers I thought could
be relevant, with this little script:
-------------------------
#!/bin/sh -x
/bin/sh -n /home/shorty/scripts/scsi.stop.sh; \
rmmod raw1394; \
rmmod eth1394;
rmmod ohci1394; \
rmmod sbp2; \
rmmod ieee1394
---------------------------------------
Then, with the FW disk connected to the alubook, but *not yet* powered
on by the latter via a switch at the enclosure which obviously, when
switched on, feeds the current to the firewire disk, thus switching it on:
-----------------------------------
#!/bin/sh -x
/bin/sh -n /home/shorty/scripts/scsi.start.sh ; \
modprobe ieee1394 disable_irm=0; \
sleep 2; \
modprobe ohci1394; \
sleep 2; \
modprobe sbp2; \
sleep 2; \
modprobe raw1394; \
sleep 2
chown root.shorty /dev/raw1394
sleep 4; \
ls /dev/sda
-------------------------------
Only after running the latter script, I switch on the FW disk. The log
for these moments covering about 60 seconds is here:
wolfgangpfeiffer.com/kern.log.when.fw.disk.is.switched.on.txt
Then, some time later on with no /dev/sda available, I run gscanbus,
forcing a bus reset. The log, again covering about 60 seconds is here:
wolfgangpfeiffer.com/kern.log.with.gscanbus.after.failed.fw.connection.txt
Again a bit later I click the 3 icons on the gscanbus window:
Clicking
"Unknown
Linux - ohci1394"
------------------------------------------------------
SelfID Info
-----------
Physical ID: 2
Link active: Yes
Gap Count: 63
PHY Speed: Unknown
PHY Delay: <=144ns
IRM Capable: Yes
Power Class: -1W
Port 0: Not connected
Port 1: Connected to child node
Port 2: Not connected
Init. reset: Yes
CSR ROM Info
------------
GUID: 0x001451FFFE3148BE
Node Capabilities: 0x000083C0
Vendor ID: 0x00001451
Unit Spec ID: 0x0000005E
Unit SW Version: 0x00000001
Model ID: 0x00000000
Nr. Textual Leafes: 1
Vendor: Unknown
Textual Leafes:
Linux - ohci1394
AV/C Subunits
-------------
N/A
-------------------------------------------------
Clicking
" <question mark>
S400 Unknown":
------------------------------------------
SelfID Info
-----------
Physical ID: 1
Link active: No
Gap Count: 63
PHY Speed: S400
PHY Delay: <=144ns
IRM Capable: No
Power Class: -1W
Port 0: Not connected
Port 1: Connected to parent node
Port 2: Connected to child node
Init. reset: No
CSR ROM Info
------------
GUID: 0x0000000000000000
Node Capabilities: 0x00000000
Vendor ID: 0x00000000
Unit Spec ID: 0x00000000
Unit SW Version: 0x00000000
Model ID: 0x00000000
Nr. Textual Leafes: 0
Vendor: (null)
Textual Leafes:
AV/C Subunits
-------------
N/A
-------------------------------------------------------------
Clicking a second
" <question mark>
S400 Unknown":
----------------------------------------------------
SelfID Info
-----------
Physical ID: 0
Link active: Yes
Gap Count: 63
PHY Speed: S400
PHY Delay: <=144ns
IRM Capable: No
Power Class: None
Port 0: Connected to parent node
Port 1: Not connected
Port 2: Not connected
Init. reset: No
CSR ROM Info
------------
GUID: 0x0000000000000000
Node Capabilities: 0x00000000
Vendor ID: 0x00000000
Unit Spec ID: 0x00000000
Unit SW Version: 0x00000000
Model ID: 0x00000000
Nr. Textual Leafes: 0
Vendor: (null)
Textual Leafes:
AV/C Subunits
-------------
N/A
---------------------------------------------------
Please, if you think it might help, let me know if want to change the
scripts to load the ieee drivers ... (Note the disable_irm=0 in one of
the scripts above .. )
Til then
Best Regards
Wolfgang
--
Wolfgang Pfeiffer: /ICQ: 286585973/ + + + /AIM: crashinglinux/
http://profiles.yahoo.com/wolfgangpfeiffer
Key ID: E3037113
http://keyserver.mine.nu/pks/lookup?search=0xE3037113&fingerprint=on
next prev parent reply other threads:[~2006-08-23 0:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-17 23:03 Broken Firewire 400/SCSI on ppc Powerbook5,8 Wolfgang Pfeiffer
2006-08-18 5:28 ` Bill Fink
2006-08-18 10:17 ` Wolfgang Pfeiffer
2006-08-19 9:32 ` Stefan Richter
2006-08-20 0:18 ` Bill Fink
2006-08-22 8:58 ` Stefan Richter
2006-08-18 23:49 ` Wolfgang Pfeiffer
2006-08-19 9:13 ` Stefan Richter
2006-08-20 1:31 ` Wolfgang Pfeiffer
2006-08-21 7:56 ` Stefan Richter
2006-08-21 0:29 ` Wolfgang Pfeiffer
2006-08-21 0:40 ` Wolfgang Pfeiffer
2006-08-23 0:28 ` Wolfgang Pfeiffer [this message]
2006-08-23 0:36 ` Wolfgang Pfeiffer
2006-08-23 1:50 ` [Correction #2] " Wolfgang Pfeiffer
2006-08-24 19:22 ` Wolfgang Pfeiffer
2006-08-24 19:43 ` Stefan Richter
2006-08-24 22:56 ` Wolfgang Pfeiffer
2006-09-02 19:18 ` Stefan Richter
2006-09-02 23:08 ` Wolfgang Pfeiffer
2006-09-02 23:28 ` Stefan Richter
2006-09-02 23:26 ` Wolfgang Pfeiffer
2006-09-04 16:58 ` Stefan Richter
2006-08-19 8:10 ` Stefan Richter
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=20060823002801.GA2709@localhost \
--to=roto@gmx.net \
--cc=billfink@mindspring.com \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=stefanr@s5r6.in-berlin.de \
/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).