From: Timothy Miller <miller@techsource.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Balaji Calidas <balaji@techsource.com>
Subject: 2.4.24 problems [WAS: Re: IDE DMA problem [WAS: Re: Getting lousy NFS + tar-pipe throughput on 2.4.20]]
Date: Mon, 16 Feb 2004 12:09:35 -0500 [thread overview]
Message-ID: <4030F94F.1000900@techsource.com> (raw)
In-Reply-To: <200402140154.54307.bzolnier@elka.pw.edu.pl>
Bartlomiej Zolnierkiewicz wrote:
> On Saturday 14 of February 2004 01:16, Timothy Miller wrote:
>
> Does 2.4.20 not work well with the KT600
>>chipset?
>
>
> It doesn't, upgrade to 2.4.24.
Ok, so we tried that. That caused all sorts of havoc, most of which we
might be able to figure out. It seems that RedHat's utilities and stuff
don't get along well with 2.4.24 if all you do is just boot the new
kernel. Seems a bunch of other stuff needs to be upgraded.
Also, 'root=LABEL=/' doesn't work anymore in grub.conf, and there seems
to be no way to enable it. Is this a RedHat only thing?
In any event, when we managed to get it to boot, it absolutely did NOT
fix the DMA problem with the KT600. Trying to enable it with hdparm
still says "Operation not permitted". We spend a LOT of time trying to
make sure we got the kernel configured right with all of the right
options, etc., but we're still without IDE DMA.
Any further suggestions?
Thanks.
next prev parent reply other threads:[~2004-02-16 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 23:48 Getting lousy NFS + tar-pipe throughput on 2.4.20 Timothy Miller
2004-02-14 0:16 ` IDE DMA problem [WAS: Re: Getting lousy NFS + tar-pipe throughput on 2.4.20] Timothy Miller
2004-02-14 0:54 ` Bartlomiej Zolnierkiewicz
2004-02-16 17:09 ` Timothy Miller [this message]
2004-02-16 17:20 ` 2.4.24 problems [WAS: Re: IDE DMA problem [WAS: Re: Getting lousy NFS + tar-pipe throughput on 2.4.20]] Bartlomiej Zolnierkiewicz
2004-02-16 19:10 ` Jeff Garzik
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=4030F94F.1000900@techsource.com \
--to=miller@techsource.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=balaji@techsource.com \
--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