From: "John Stoffel" <stoffel@lucent.com>
To: caleb_gibbs@sbcglobal.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Firewire hard drives
Date: Thu, 5 Aug 2004 16:18:55 -0400 [thread overview]
Message-ID: <16658.38447.591862.21787@gargle.gargle.HOWL> (raw)
In-Reply-To: <200408051612.36445.caleb_gibbs@sbcglobal.net>
Caleb> Has anyone had any luck getting there external firewire hard
Caleb> drive to mount? my laptop is running suse9.0 and detects the
Caleb> firewire hub and works great with my usb devices but when I
Caleb> plug in the firewire hdd it boots the device but I can`t mount
Caleb> it.
I've been having problems too with these devices. I've been trying
with a dual interface USB2.0/Firewire box with a Prolific Technology
chipset. This is with 2.6.[678]-* kernels of various types. I can do
a mkfs under either USB2 or Firewire connections (both ports are on
the same Adaptec PCI card) but the firewire sides bombs out much
quicker.
I've just found some issues with Device Mapper and MD that I wonder
might be causing some issues here, but if I use the USB side, I get
full system lockups at points which are not fun, while on the Firewire
side I get tons of errors and the device (drive and case) just lock up
completely. Takes a power cycles and a couple of un-plugs to get it
working again under Firewire.
I've filed a bug report with the linux-ieee1394 folks, but I haven't
had a chance to look into it yet to provide more info if they've
requested it.
Sorry, not much else to report here, but I'd certainly like to help out.
John
next prev parent reply other threads:[~2004-08-05 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 21:12 Caleb Gibbs
2004-08-05 20:18 ` John Stoffel [this message]
2004-08-05 20:36 ` Måns Rullgård
2004-08-06 13:22 ` John Stoffel
2004-08-05 20:41 ` Erik Steffl
2004-08-06 2:38 ` Raf D'Halleweyn (list)
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=16658.38447.591862.21787@gargle.gargle.HOWL \
--to=stoffel@lucent.com \
--cc=caleb_gibbs@sbcglobal.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®