From: DervishD <raul@pleyades.net>
To: Eugene <spamacct11@yahoo.com>, linux-kernel@vger.kernel.org
Cc: "ynezz @ hysteria. sk" <ynezz@hysteria.sk>
Subject: Re: best AMD motherboard for Linux
Date: Sun, 28 Dec 2003 18:48:28 +0100 [thread overview]
Message-ID: <20031228174828.GF3386@DervishD> (raw)
In-Reply-To: <20031228172008.GA9089@c0re.hysteria.sk> <3FEF0AFD.4040109@yahoo.com>
Hi Eugene :)
* Eugene <spamacct11@yahoo.com> dixit:
> Asus A7N8X-X
Look for the chipset. I think all KT chipsets are supported.
IMHO your worst problem will be the video card :(( If you can
live with binary-only drivers, you can use nVidia, things like that.
I don't know new video cards that provide open source drivers, or
which ones are natively supported by the stock kernels, sorry :(
> Gigabyte GA-7VT600-P-L
This should be supported. KT400 is supported (AFAIK), so KT600
may work.
> planning to get GeForce FX graphics card, if it makes a difference.
Ask here before if you are planning to change your video card.
>So which board is more compatibile?
I would make my bet for the Gigabyte one...
* ynezz@hysteria.sk <ynezz@hysteria.sk> dixit:
> WTF! I'm going mad YOU ignorant. Why the hell do you ask
> for such thing on LKML ? God bless mailing-lists...
Oh, ye olde kernel hacker... who hasn't write a line of code in
the kernel... Have you tried to be polite and stop making noise in
the list? Eugene is not an ignorant, since he has asked. You, on the
other hand, don't even have a name. Since you are very clever, you
won't mind if I write in spanish, gilipollas tonto del culo, es gente
como tú la que hace que las listas sean lugares insoportables, los
gaznápiros mendrugos que se creen algo porque se saben de memoria las
últimas notícias de los lugares para enterados. Bravo por tamaña
expresión de estulticia. Ahora a ver si encuentras quien te traduzca
esto, and sorry to the list for the flame bit, but I can't stand such
gilipollas.
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/
next prev parent reply other threads:[~2003-12-28 17:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-28 16:55 best AMD motherboard for Linux Eugene
2003-12-28 17:20 ` ynezz
2003-12-29 20:32 ` Shawn
2003-12-28 17:48 ` DervishD [this message]
2003-12-28 21:10 ` Patrick Plattes
2003-12-29 20:28 ` Shawn
2003-12-29 16:56 ` Tomas Szepe
2003-12-30 18:32 ` Derek Foreman
2003-12-30 18:35 ` Joel Jaeggli
2003-12-30 19:42 ` Tomas Szepe
2003-12-31 0:46 ` Derek Foreman
2003-12-31 9:39 ` Tomas Szepe
2004-01-01 6:15 ` Derek Foreman
2004-01-01 17:04 ` Lionel Bouton
2004-01-01 19:37 ` Diego Calleja
2004-01-01 21:43 ` Martin Schlemmer
2004-01-01 21:44 ` Derek Foreman
2004-01-02 0:15 ` Lionel Bouton
[not found] <17MTX-4tr-5@gated-at.bofh.it>
[not found] ` <17Mr0-3MN-9@gated-at.bofh.it>
[not found] ` <17NmT-53G-1@gated-at.bofh.it>
[not found] ` <1894e-34n-11@gated-at.bofh.it>
[not found] ` <18wWI-5xF-5@gated-at.bofh.it>
[not found] ` <18y2M-7Zy-15@gated-at.bofh.it>
[not found] ` <18CSr-880-1@gated-at.bofh.it>
[not found] ` <18L9o-5xr-5@gated-at.bofh.it>
[not found] ` <194lF-8q6-3@gated-at.bofh.it>
[not found] ` <19euJ-59K-7@gated-at.bofh.it>
[not found] ` <19gZu-8vz-1@gated-at.bofh.it>
2004-01-02 6:51 ` Yaroslav Klyukin
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=20031228174828.GF3386@DervishD \
--to=raul@pleyades.net \
--cc=linux-kernel@vger.kernel.org \
--cc=spamacct11@yahoo.com \
--cc=ynezz@hysteria.sk \
/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