From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Andreas Messer <andreas.messer@stud-mail.uni-wuerzburg.de>
Cc: linux1394-devel@lists.sourceforge.net,
Manuel Lauss <mano@roarinelk.homelinux.net>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] firewire: mass-storage i/o-problems
Date: Mon, 23 Jul 2007 13:30:58 +0200 [thread overview]
Message-ID: <46A49172.2060200@s5r6.in-berlin.de> (raw)
In-Reply-To: <200707231007.50565.andreas.messer@stud-mail.uni-wuerzburg.de>
Andreas Messer wrote:
> On Monday, 23. Juli 2007 01:34 Stefan Richter wrote:
>> Are you sure the FireWire controller is from VIA? Check with lscpi.
>> The NVidia nForce2 chipset has an own FireWire controller, and that one
>> is only "supported" by a gross hack in ohci1394 and at the moment
>> unsupported in firewire-ohci.
...
> The first System, where harddisc don't work at all with the new stack:
> Nvidia NForce2 Ultra Chipset; 1GB RAM; XP-M 2600; FW-Controller is
> PCI addon card; lspci says Via
OK, if it's an add-on card, then you surely got the right information
from lspci. I tested 3 different VIA controllers, they all worked for me.
> Vanilla Kernel 2.6.22, apic, Preempt, Dynamic Tics. hmm something else
> interesting?
I haven't tested dyntics yet, should do so eventually.
--
Stefan Richter
-=====-=-=== -=== =-===
http://arcgraph.de/sr/
prev parent reply other threads:[~2007-07-23 11:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 21:32 Andreas Messer
2007-07-22 23:34 ` Stefan Richter
2007-07-23 6:37 ` Manuel Lauss
2007-07-23 7:40 ` Stefan Richter
2007-07-23 8:45 ` Manuel Lauss
2007-07-23 11:34 ` Stefan Richter
2007-07-23 18:33 ` Manuel Lauss
2007-07-23 18:44 ` Manuel Lauss
2007-07-24 19:56 ` Stefan Richter
2007-07-25 5:12 ` Manuel Lauss
2007-07-25 16:27 ` Stefan Richter
2007-07-23 8:07 ` Andreas Messer
2007-07-23 9:58 ` Andreas Micklei
2007-07-23 11:30 ` Stefan Richter [this message]
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=46A49172.2060200@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=andreas.messer@stud-mail.uni-wuerzburg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=mano@roarinelk.homelinux.net \
/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®