From: Matt <matt@bodgit-n-scarper.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: aacraid success with 2.4.17-pre8. Intentional?
Date: Tue, 11 Dec 2001 22:41:04 +0000 [thread overview]
Message-ID: <20011211224104.B256@butterlicious.bodgit-n-scarper.com> (raw)
In-Reply-To: <20011211150717.A20308@mould.bodgit-n-scarper.com> <E16DvOC-0006wF-00@the-village.bc.nu>
In-Reply-To: <E16DvOC-0006wF-00@the-village.bc.nu>
On Tue, Dec 11, 2001 at 10:28:40PM +0000, Alan Cox wrote:
> > I've just tried the latest 2.4.17-pre8 kernel, and it works, in that
> > it gets passed the fsck'ing. I couldn't see anything in the changelog that
> > screamed "Fix fsck hang with aacraid", so I was wondering if my working
> > setup is intentional or not? I haven't followed the development of this
> > driver too closely, I just had the card and downloaded the latest "stable"
> > release and went from there...
>
> The later fixes I applied (and Matt Domsch's fixes too) don't really do
> anything that would explain this.
That was what I was afraid of. :-)
The only other kernel that I have tried was 2.4.7, from a Slackware 8.0
bootdisk, found at http://www.alphacent.com/opensource, which I needed to use
to be able to install the system. I then used this kernel as a temporary
measure for booting, no problems with it either, but I guess a lot has
changed since then...
Is there anything I can do to help? I can provide the kernel config if that
would be useful, (I can't get at it until tomorrow morning), which is the same
one I used on all three kernel builds. The box isn't in production use,
(funny, that), so I can run some tests if needs be.
Cheers
Matt
--
"Phase plasma rifle in a forty-watt range?"
"Only what you see on the shelves, buddy"
next prev parent reply other threads:[~2001-12-11 22:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 15:07 Matt
2001-12-11 22:28 ` Alan Cox
2001-12-11 22:41 ` Matt [this message]
2001-12-11 23:02 ` Alan Cox
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=20011211224104.B256@butterlicious.bodgit-n-scarper.com \
--to=matt@bodgit-n-scarper.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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®