From: Filip djMedrzec Zyzniewski <lkml@filip.eu.org>
To: linux-kernel@vger.kernel.org
Subject: Hardware recommentations.
Date: Sun, 2 Feb 2003 19:46:37 +0100 [thread overview]
Message-ID: <20030202184637.GA3777@ekatalog.com.pl> (raw)
Hello.
I am sick of my hardware and I'd like to change it.
Not to make bad buys, I decided to ask you for advice :).
What I need:
STABLE x86 architecture, capable of decoding DVD realtime in
software and run some 3D games like RtCW. It doesn't have to
be extremely powerful, but has to run smoothly. Without
IDE transfer locking all other stuff (via kt133a/686)
What I have now:
CPU: duron 700 spitfire
mainboard: sono vk2208a (via kt133a / vc82C686B)
RAM: 384MB PC133 SDRAM
sound: SB Live!
NIC: rtl8139C
GPU: radeon 7500 64MB DDR
HDD: ST340810A 40GB/5400rpm
CDRW: Teac CD-W58E
problems:
heavy IDE transfers cause horrible system slowdowns (UDMA100 mode)
using DRI causes hard freezes (AGP x1 mode)
processes influence other ones more than on 440lx / p2 266 machine (cache?)
tried on kernels 2.4.17 to 2.2.40. DRI from CVS.
What I'd like to keep: sound, nic, gpu, hdd and cdrw.
What CPU/mobo/ram would you suggest?
Considering 2.5 kernels too (to have nice sys with 2.6.x).
I have a limited budget...
tia and bye,
Filip Zyzniewski
reply other threads:[~2003-02-02 18:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030202184637.GA3777@ekatalog.com.pl \
--to=lkml@filip.eu.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