All of lore.kernel.org
 help / color / mirror / Atom feed
From: FonkiE <fonkie@fsmat.at>
To: Ben Collins <bcollins@debian.org>
Cc: FonkiE <fonkie@fsmat.at>,
	linux1394-user@lists.sourceforge.net,
	linux1394-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: problems with sbp2 and sd_mod (ipod firewire harddisk)
Date: Thu, 25 Apr 2002 17:41:24 +0200	[thread overview]
Message-ID: <20020425174124.A4588@elch.elche> (raw)
In-Reply-To: <3CC81A29.3050204@fsmat.at> <20020425152328.GD508@blimpo.internal.net>

hi!
 
> > i have an ipod too. yesterday everything worked fine. today i updated
> > from firmware 1.02 to 1.1. now the system crashed with 'modprobe sbp2'.
> 
> See our website for obtaining the latest source. There are a lot of
> changes to ohci1394 and sbp2 that have so far fixed every known issue
> with sbp2 devices.

thanks that worked:

Apr 25 17:37:52 elch kernel: ohci1394: $Rev: 460 $ Ben Collins <bcollins@debian.org>
Apr 25 17:37:52 elch kernel: PCI: Found IRQ 11 for device 00:0d.0
Apr 25 17:37:52 elch kernel: ohci1394_0: OHCI-1394 1.0 (PCI): IRQ=[11]  MMIO=[efffe000-effff000]  Max Packet=[2048]
Apr 25 17:37:53 elch kernel: ieee1394: Device added: Node[00:1023]  GUID[000a27000201e05c]  [Apple Computer, Inc.]
Apr 25 17:37:53 elch kernel: ieee1394: Host added: Node[01:1023]  GUID[009096000000036a]  [Linux OHCI-1394]
Apr 25 17:37:53 elch /sbin/hotplug: no runnable /etc/hotplug/ieee1394.agent is installed
Apr 25 17:38:23 elch kernel: ieee1394: sbp2: Logged into SBP-2 device
Apr 25 17:38:23 elch kernel: ieee1394: sbp2: Node[00:1023]: Max speed [S400] - Max payload [2048]
Apr 25 17:38:23 elch kernel: scsi3 : IEEE-1394 SBP-2 protocol driver (host: ohci1394)
Apr 25 17:38:23 elch kernel: $Revision: 1.0 $ James Goodwin <jamesg@filanet.com>
Apr 25 17:38:23 elch kernel: SBP-2 module load options:
Apr 25 17:38:23 elch kernel: - Max speed supported: S400
Apr 25 17:38:23 elch kernel: - Max sectors per I/O supported: 255
Apr 25 17:38:23 elch kernel: - Max outstanding commands supported: 8
Apr 25 17:38:23 elch kernel: - Max outstanding commands per lun supported: 1
Apr 25 17:38:23 elch kernel: - Serialized I/O (debug): no
Apr 25 17:38:23 elch kernel: - Exclusive login: yes
Apr 25 17:38:23 elch kernel:   Vendor: Apple     Model: iPod              Rev: 1.10
Apr 25 17:38:23 elch kernel:   Type:   Direct-Access                      ANSI SCSI revision: 02
Apr 25 17:38:23 elch kernel: Attached scsi removable disk sda at scsi3, channel 0, id 0, lun 0
Apr 25 17:38:23 elch kernel: SCSI device sda: 9780750 512-byte hdwr sectors (5008 MB)
Apr 25 17:38:23 elch kernel: sda: test WP failed, assume Write Enabled
Apr 25 17:38:24 elch kernel:  sda: [mac] sda1 sda2 sda3

when is this scheduled for the main kernel? is it already in a pre-patch?

CU,
	FonkiE
--
fonkie@fsmat.at                         pgp public key on request        CU

  reply	other threads:[~2002-04-25 15:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-25 15:00 problems with sbp2 and sd_mod (ipod firewire harddisk) FonkiE
2002-04-25 15:23 ` Ben Collins
2002-04-25 15:41   ` FonkiE [this message]
2002-04-25 15:57     ` Ben Collins
2002-04-25 19:15       ` J.A. Magallon

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=20020425174124.A4588@elch.elche \
    --to=fonkie@fsmat.at \
    --cc=bcollins@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=linux1394-user@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.