public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: wrlk@riede.org
Cc: linux-scsi@vger.kernel.org
Subject: Re: aic7xxx 6.2.24 bug report
Date: Sun, 29 Dec 2002 13:30:07 +1100	[thread overview]
Message-ID: <3E0E5E2F.9030403@torque.net> (raw)
In-Reply-To: 20021229015759.GI9319@linnie.riede.org

Willem Riede wrote:
> On 2002.12.28 19:35 Justin T. Gibbs wrote:
> 
>>>I'm particularly surprised by the line
>>>
>>>Parameter aic7xxx length must be 1-1 characters
>>>
>>>which hints that the options are not correctly coded?
>>
>>This is due to the shell magic used during initrds.  Did you
>>try quoting this options?
>>
>>options aic7xxx 'aic7xxx=verbose.debug:0x63'
>>
> 
> I have now, without change. I had earlier quoted just "aic7xxx=verbose.debug:0x63"
> and tried only aic7xxx=verbose to avoid special characters, all with the same
> effect.
> 
> One thought just occured to me, the modutils have been in flux, I'll see if
> there is a newer version than I'm using now.

This seems to be the latest module-init-tools:
http://www.[COUNTRY].kernel.org/pub/linux/kernel/people/rusty/modules/module-init-tools-0.9.6.tar.gz

Announced in lkml:
http://marc.theaimsgroup.com/?l=linux-kernel&m=104089668930417&w=2

BTW Module parameters seem to start working again in lk 2.5.52
(with module-init-tools-0.9.3).

Doug Gilbert



  reply	other threads:[~2002-12-29  2:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-28 20:45 aic7xxx 6.2.24 bug report Willem Riede
2002-12-28 20:48 ` Justin T. Gibbs
2002-12-28 22:26   ` Willem Riede
2002-12-28 22:28     ` Justin T. Gibbs
     [not found]       ` <20021228232624.GG9319@linnie.riede.org>
     [not found]         ` <910548112.1041122117@aslan.scsiguy.com>
2002-12-29  1:57           ` Willem Riede
2002-12-29  2:30             ` Douglas Gilbert [this message]
2002-12-29 14:17               ` Willem Riede
2002-12-29 19:07                 ` Doug Ledford

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=3E0E5E2F.9030403@torque.net \
    --to=dougg@torque.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=wrlk@riede.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