From: "Rogério Brito" <rbrito@ime.usp.br>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Ben Collins <bcollins@debian.org>,
linux-scsi@vger.kernel.org,
linux1394-devel@lists.sourceforge.net,
James.Bottomley@SteelEye.com
Subject: Re: changes to ieee1394/sbp2 outside of linux1394.org
Date: Fri, 15 Jul 2005 23:10:18 -0300 [thread overview]
Message-ID: <20050716021018.GA1555@ime.usp.br> (raw)
In-Reply-To: <42D82E49.7090907@s5r6.in-berlin.de>
Hi, Stefan.
On Jul 15 2005, Stefan Richter wrote:
> Rogério, try "modprobe ieee1394 disable_irm=1" again, of course before
> ohci1394 is loaded. Make sure that sd_mod was loaded.
Ok, I tried this. Here is the relevant part of the dmesg (the whole log is
uploaded to http://www.ime.usp.br/~rbrito/bug/):
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
SCSI subsystem initialized
ieee1394: Initialized config rom entry `ip1394'
ieee1394: IRM functionality disabled
sbp2: $Rev: 1311 $ Ben Collins <bcollins@debian.org>
ohci1394: $Rev: 1313 $ Ben Collins <bcollins@debian.org>
PCI: Found IRQ 5 for device 0000:00:0a.0
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[5] MMIO=[db800000-db8007ff] Max Packet=[2048]
ieee1394: Host added: ID:BUS[0-00:1023] GUID[0011066645555ead]
ieee1394: Node added: ID:BUS[0-01:1023] GUID[0050c501e00010e8]
scsi0 : SCSI emulation for IEEE-1394 SBP-2 Devices
ieee1394: sbp2: Logged into SBP-2 device
ieee1394: Node 0-01:1023: Max speed [S400] - Max payload [2048]
Vendor: ST316002 Model: 1A Rev: 3.06
Type: Unknown ANSI SCSI revision: 06
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
SCSI device sda: drive cache: write back
sda: [mac] sda1 sda2 sda3 sda4
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This time, I removed everything like udev and hotplug, doing things by
hand. I loaded the ohci1394 module after I loaded the sbp2 module.
The drive works this way, but the mouse (ps2) doesn't work. I don't know if
this is related to the fact that I am not using the hotplug scripts (OTOH,
I do see that the kernel has identified the mouse in the dmesg log).
> If this does not help, enable scsi_print_command(...) and
> scsi_print_sense(...)
> in sbp2scsi_complete_command(), i.e. #define CONFIG_IEEE1394_SBP2_DEBUG 1
> or 2 near the beginning of sbp2.c. I assume there won't be too much
> resulting SCSI traffic logged, so you could post it directly here to the
> lists.
I will try this right now with the hotplug/udev scripts back (with the
patch you mentioned) and without disable_irm.
Thanks, Rogério.
--
Rogério Brito : rbrito@ime.usp.br : http://www.ime.usp.br/~rbrito
Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat: http://freshmeat.net/projects/algorithms/
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-07-16 2:10 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-09 12:37 changes to ieee1394/sbp2 outside of linux1394.org Stefan Richter
2005-07-09 15:18 ` James Bottomley
2005-07-09 16:27 ` Ben Collins
2005-07-09 16:35 ` James Bottomley
2005-07-09 16:56 ` Stefan Richter
2005-07-09 17:24 ` James Bottomley
2005-07-15 0:53 ` Rogério Brito
2005-07-15 1:43 ` Ben Collins
2005-07-15 6:36 ` Stefan Richter
2005-07-15 15:30 ` Rogério Brito
2005-07-15 15:15 ` Rogério Brito
2005-07-15 15:53 ` Rogério Brito
2005-07-15 17:28 ` Ben Collins
2005-07-15 18:50 ` Rogério Brito
2005-07-15 20:57 ` Ben Collins
2005-07-15 21:44 ` Stefan Richter
2005-07-16 2:10 ` Rogério Brito [this message]
2005-07-16 1:42 ` Rogério Brito
2005-07-16 15:56 ` Ben Collins
2005-07-16 16:42 ` Rogério Brito
2005-07-16 18:10 ` Stefan Richter
2005-07-16 19:34 ` Rogério Brito
2005-07-17 16:57 ` Ben Collins
2005-07-17 19:18 ` Rogério Brito
2005-07-17 19:46 ` Stefan Richter
2005-07-18 0:14 ` Rogério Brito
2005-07-17 23:27 ` Stefan Richter
2005-07-18 4:50 ` Philipp Slusallek
2005-07-18 7:13 ` Stefan Richter
2005-07-18 8:18 ` Rogério Brito
2005-07-20 0:20 ` Rogério Brito
2005-07-09 17:49 ` Ben Collins
2005-07-09 18:41 ` James Bottomley
2005-07-09 19:22 ` Ben Collins
2005-07-09 16:37 ` Arjan van de Ven
2005-07-09 17:53 ` Ben Collins
2005-07-09 17:00 ` Stefan Richter
2005-07-09 17:51 ` Ben Collins
2005-07-09 17:57 ` Arjan van de Ven
2005-07-09 18:12 ` Ben Collins
2005-07-09 18:38 ` James Bottomley
2005-07-09 23:06 ` Ben Collins
2005-07-10 3:34 ` Jeff Garzik
2005-07-10 4:36 ` Ben Collins
2005-07-10 15:25 ` James Bottomley
2005-07-10 15:58 ` Ben Collins
2005-07-10 17:05 ` James Bottomley
2005-07-10 17:33 ` Ben Collins
2005-07-10 17:34 ` Stefan Richter
2005-07-10 18:14 ` James Bottomley
2005-07-10 20:13 ` Stefan Richter
2005-07-10 20:27 ` Ben Collins
2005-07-10 21:24 ` Stefan Richter
2005-07-10 22:06 ` Stefan Richter
2005-07-10 22:16 ` (summary) " Stefan Richter
2005-07-10 22:32 ` Stefan Richter
2005-07-11 13:57 ` James Bottomley
2005-07-13 19:56 ` Stefan Richter
2005-07-13 20:12 ` James Bottomley
2005-07-13 21:09 ` Stefan Richter
2005-07-13 22:39 ` Stefan Richter
2005-07-10 19:26 ` Stefan Richter
2005-07-10 4:21 ` James Bottomley
2005-07-09 23:31 ` Ben Collins
2005-07-10 3:29 ` Jeff Garzik
2005-07-10 4:38 ` Ben Collins
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=20050716021018.GA1555@ime.usp.br \
--to=rbrito@ime.usp.br \
--cc=James.Bottomley@SteelEye.com \
--cc=bcollins@debian.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--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