From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: daRonin <daronin@digimerc.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: firewire in 2.4.21-ben2
Date: 15 Jul 2003 11:30:52 +0200 [thread overview]
Message-ID: <1058261452.628.36.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.56.0307141313050.1861@daronin.digimerc.com>
On Mon, 2003-07-14 at 21:19, daRonin wrote:
> Hi,
>
> I just upgraded to 2.4.21-ben2 kernel. And I can't mount my firewire
> HDDs any longer.
>
> These are the commands I am executing:
>
> modprobe -k ieee1394
> modprobe -k ohci1394
> modprobe -k sbp2
> modprobe -k raw1394
> modprobe -k sd_mod
> mount /dev/sda2 /mnt/fire
>
> Judging by the logs everything seems to go fine up to inserting sd_mod.
> sbp2 module seems to see the device and such.
>
> But after inserting sd_mod absolutely nothing happens. I tried rmmod'ing
> the modules and inserting them again, tried to switch the order around,
> etc. No luck...
>
> After I reboot back in 2.4.20-ben10 everything works fine...
That's a change in the firewire layer, you have to trigger a scsi probe
yourself now. Either using the rescan-scsi-bus.sh script, or the scsiadd
command for example
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-15 9:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 19:19 firewire in 2.4.21-ben2 daRonin
2003-07-15 9:30 ` Benjamin Herrenschmidt [this message]
2003-07-17 10:11 ` Calum Selkirk
2003-07-26 14:39 ` Calum Selkirk
2003-07-27 16:06 ` Benjamin Herrenschmidt
2003-07-27 20:56 ` Calum Selkirk
-- strict thread matches above, loose matches on Subject: below --
2003-07-15 4:40 Bill Fink
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=1058261452.628.36.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=daronin@digimerc.com \
--cc=linuxppc-dev@lists.linuxppc.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).