From: Wolfgang Pfeiffer <roto@gmx.net>
To: linux1394-devel@lists.sourceforge.net
Cc: linuxppc-dev@ozlabs.org, Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: Broken Firewire 400/SCSI on ppc Powerbook5,8
Date: Sat, 19 Aug 2006 01:49:30 +0200 [thread overview]
Message-ID: <20060818234930.GB2662@localhost> (raw)
In-Reply-To: <20060817230347.GC3440@localhost>
On Fri, Aug 18, 2006 at 01:03:47AM +0200, Wolfgang Pfeiffer wrote:
> Hi All
>
> Short version first:
>
> The SCSI/FW routines seem to work like a charm with a LSILogic Model/
> SYM13FW500-Disk on my old Macintosh titanium-IV laptop, with exactly
> the same relatively fresh git-kernel that does not work on the
> PowerBook5,8. That is I compiled the kernel on the Apple Powerbook5,8
> and installed it on both machines.
>
[ ... ]
In the meantime I suspect a hardware problem.
Here's why:
I connected the FW disk I was reporting about in previous postings to
both an older Apple titanium Powerbook and to the newer Apple alubook
5,8.
In both instances I rebooted the machines with the accompanying
different Apple OS X install CD's. Both CD's have a so-called "Disk
Utility" tool with them, a tool that generally detects and repairs
disks. The tool clearly detected the FW disk attached to my old
titanium. And the same tool didn't detect the same FW disk on the
newer alubook 5,8 ... :)
In both instances I connected the FW disk to the FW 400 connector of
the machines.
So unless there are differing FW 400 versions available on both
machines I'd suspect a hardware prob with the 5,8.
[Note: Do there actually exist different Firewire 400 versions?]
I'll make this issue clear next week with a trip to the shop where I
bought the alubook.
And I'll be back as soon as I know more ...
Thanks. And sorry the idea with the check via OSX didn't come to my
mind earlier ...
Until then, and a nice week-end to everyone
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-18 23:49 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 [this message]
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
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=20060818234930.GB2662@localhost \
--to=roto@gmx.net \
--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).