From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: pf-kernel@mirkwood.net (PinkFreud), linux-kernel@vger.kernel.org
Subject: Re: Are we going too fast?
Date: Mon, 13 Aug 2001 14:55:18 +0100 [thread overview]
Message-ID: <5.1.0.14.2.20010813143232.00a38140@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <E15WHVE-0007N6-00@the-village.bc.nu>
In-Reply-To: <Pine.LNX.4.20.0108130303120.1037-100000@eriador.mirkwood.net>
At 14:11 13/08/01, Alan Cox wrote:
> > Should development continue on the latest and supposedly greatest
> > drivers? Or should the existing bugs be fixed first? I've got at least
> > three up there that need taking care of, and I'm sure others on this list
> > have found more. 3 seperate crashes on 3 seperate installs on 3 seperate
> > boxes - that's 100% failure rate. If I get 100% failure on my installs,
> > what are others seeing?
>
>Near enough 0%. But then I try and avoid buying broken chipsets.
0% here. Admittedly I have only one VIA box and only as of this weekend but
it works great with all kernels tried. [Epox 8KTA3 mobo, KT133A chipset
running 266MHz FSB and 1.33GHz Athlon Thunderbird, PC133 CL2 RAM from
Micron, active PFC power supply, BIOS setup to the fastest settings it
allows me to set it to while stayin in spec (i.e. no o/c of CPU or
busses!), IBM Ericson ATA100 41GiB HD attached to the VIA controller].
Tried kernels are 2.4.4-4GB (from SuSE 7.1 binary install Pentium
optimizations I believe), 2.4.8 and 2.4.8-ac1 (the latter two both compiled
with Athlon optimizations) and the system is absolutely fine. bonnie
scores >30MiB/s (in mostly 34-39 MiB/s) on intelligent read/write tests
with DMA enabled and a working set 2x size of RAM (i.e. 512MiB test size on
256MiB RAM). Even when using fsync after every operation i/o speed is
almost unaffected (it drops a bit but only by about 1-2MiB/s).
Copying 15 GiB of data from one partition to the other on the same disk
worked fine. Compiling kernels works fine (Admittedly it only takes just
over 3 minutes to compile the kernel with make -j 2 bzImage, so it's not
too much of a stress test).
Oh and the VIA AC97 audio codec seems to work beautifully, too. As does X
(both 3.3.x and 4.0.3) is fine, too. (I use an ancient ET6000 PCI gfx card.)
So, basically no problems here. I was quite worried about buying a VIA
chipset but now it seems like a great buy. (-:
The only thing that's slightly annoying is that during boot three of the
PCI resources from the VIA chipset are reported as "unknown, treating
transparently" (or some simillar msg), don't have box handy to say what
they were exactly... if anyone is intersted in exact messages I can provide
dmesg + lspci -vvv output once I get home tonight.
> > I like Linux. I'd like to stick with it. But if it's going to
> > continually crash, I'm going to jump ship - and I'll start recommending to
>
>If you want maximum stability you want to be running 2.2 or even 2.0. Newer
>less tested code is always less table. 2.4 wont be as stable as 2.2 for a
>year yet.
Or alternatively buy quality components that other people have tested under
Linux with kernel 2.4...
Anton
--
"Nothing succeeds like success." - Alexandre Dumas
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Linux NTFS Maintainer / WWW: http://linux-ntfs.sf.net/
ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/
next prev parent reply other threads:[~2001-08-13 13:55 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 7:43 PinkFreud
2001-08-13 8:52 ` Brian
2001-08-13 8:55 ` Francois Romieu
2001-08-14 4:21 ` Pete Toscano
2001-08-14 12:48 ` Alan Cox
2001-08-14 13:03 ` usb-uhci + SMP -> bad Andre Pang
2001-08-14 16:01 ` Russell Cattelan
2001-08-14 22:30 ` Are we going too fast? Paul G. Allen
2001-08-13 10:03 ` Gérard Roudier
2001-08-13 10:29 ` Justin Guyett
2001-08-13 12:56 ` Andrzej Krzysztofowicz
2001-08-13 16:54 ` Gérard Roudier
2001-08-13 10:09 ` Chris Wilson
2001-08-13 11:09 ` szonyi calin
2001-08-13 13:11 ` Alan Cox
2001-08-14 18:51 ` Anders Larsen
2001-08-14 20:29 ` Anders Larsen
2001-08-13 13:46 ` hugang
2001-08-13 13:55 ` Anton Altaparmakov [this message]
2001-08-13 17:16 ` Stephen Satchell
2001-08-13 21:01 ` A warning (was: Re: Are we going too fast?) Nico Schottelius
2001-08-13 17:53 Are we going too fast? PinkFreud
2001-08-13 20:27 ` Gérard Roudier
2001-08-13 18:46 Per Jessen
2001-08-14 13:58 ` Andrew Scott
2001-08-14 19:54 ` David Ford
2001-08-13 18:53 Petr Vandrovec
[not found] <fa.l9dq0tv.7gqnhh@ifi.uio.no>
[not found] ` <fa.g70as7v.1722ipv@ifi.uio.no>
2001-08-13 19:14 ` John Weber
2001-08-13 21:07 PinkFreud
2001-08-13 21:20 ` Alan Cox
2001-08-13 21:41 ` Rog�rio Brito
2001-08-14 0:56 ` Ben Ford
2001-08-14 7:34 ` Peter Wächtler
2001-08-14 2:24 ` David Ford
2001-08-14 4:19 ` Nicholas Knight
2001-08-14 12:49 ` Alan Cox
2001-08-14 22:27 ` Paul G. Allen
2001-08-13 21:36 PinkFreud
2001-08-14 7:57 ` Helge Hafting
2001-08-13 21:44 PinkFreud
2001-08-14 0:04 ` PinkFreud
2001-08-14 7:24 ` Francois Romieu
2001-08-15 23:24 ` Dr. Kelsey Hudson
2001-08-14 16:25 PinkFreud
2001-08-14 16:32 PinkFreud
2001-08-14 19:47 Per Jessen
2001-08-14 20:07 Per Jessen
2001-08-14 20:20 Per Jessen
[not found] <no.id>
2001-08-13 20:24 ` Alan Cox
2001-08-13 21:06 ` Anthony Barbachan
2001-08-14 20:47 ` Alan Cox
2001-08-15 0:07 ` PinkFreud
2001-08-15 20:13 Roy Murphy
2001-08-16 21:42 PinkFreud
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=5.1.0.14.2.20010813143232.00a38140@pop.cus.cam.ac.uk \
--to=aia21@cam.ac.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pf-kernel@mirkwood.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 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®