From: Anders Peter Fugmann <afu@fugmann.dhs.org>
To: John Jasen <jjasen@realityfailure.org>, linux-kernel@vger.kernel.org
Subject: Re: SiS630 chipsets && linux 2.4.x kernel == snails pace?
Date: Sun, 18 Nov 2001 19:01:54 +0100 [thread overview]
Message-ID: <3BF7F792.8010403@fugmann.dhs.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0111180957020.10229-100000@geisha.realityfailure.org>
Hi again.
One thing i cannot see is "unmaskirq" setting.
So I would really like to see the output of a plain
hdparm /dev/hda.
As far as I can see the 2.4.X kernel gives much better throughput,
but 4-5 hours for compiling the kernel is way too long on a 700Mhz
celeron. Please try to do a
$ make dep clean && time make bzImage -j 3
on both 2.2.19 and 2.4.X kernel and send the time information.
The line
"PCI: No IRQ known for interrupt pin A of device 00:00.1. Please try
using pci=biosirq." in the dmesg output is strange. Have you tried to do
what is says?
I've only seen it on my server, where I have disabled my onboard
controller, which means that the BIOS does not allocate an interrupt pin
for it. Have you looked in the BIOS, to see if the controller is enabled
correctly?
Regards
Anders Fugmann
next prev parent reply other threads:[~2001-11-18 18:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-18 15:02 SiS630 chipsets && linux 2.4.x kernel == snails pace? John Jasen
2001-11-18 18:01 ` Anders Peter Fugmann [this message]
2001-11-18 18:37 ` John Jasen
2001-11-18 18:52 ` John Jasen
2001-11-19 1:07 ` John Jasen
2001-11-19 2:12 ` Anders Peter Fugmann
2001-11-19 2:53 ` John Jasen
2001-11-19 4:55 ` John Jasen
2001-11-19 17:48 ` John Jasen
2001-11-21 16:51 ` John Jasen
2001-11-22 1:36 ` D. Hugh Redelmeier
-- strict thread matches above, loose matches on Subject: below --
2001-11-19 3:04 Nate Eldredge
2001-11-19 3:05 ` Nate Eldredge
[not found] <Pine.SGI.4.31L.02.0111181459340.12354143-100000@irix2.gl.umbc.edu>
2001-11-18 21:41 ` Anders Peter Fugmann
2001-11-18 21:55 ` John Jasen
2001-11-19 0:44 ` Stuart Young
2001-11-19 1:19 ` John Jasen
2001-11-17 22:22 John Jasen
2001-11-18 2:01 ` John Jasen
2001-11-18 4:09 ` Anders Peter Fugmann
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=3BF7F792.8010403@fugmann.dhs.org \
--to=afu@fugmann.dhs.org \
--cc=jjasen@realityfailure.org \
--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