All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lionel Bouton <Lionel.Bouton@inet6.fr>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: best AMD motherboard for Linux
Date: Fri, 02 Jan 2004 01:15:37 +0100	[thread overview]
Message-ID: <3FF4B829.8060406@inet6.fr> (raw)
In-Reply-To: <Pine.LNX.4.58.0401011516110.437@uberdeity>

Derek Foreman wrote the following on 01/01/2004 10:44 PM :

> [...]
>
>There are features available in both the ati and nvidia closed source
>drivers that are not available in DRI.  If I want "full use" of my
>hardware, then DRI is does not "work best" for me.
>
>  
>

We could argue endlessly on that subject. Let's agree that what 
*practically* works best for one doesn't automatically for another. My 
"best" in "they can't work best" conclusion referred to the utopic 
bug-free, adaptable to whatever changes in new kernels happen during the 
21st century driver.

>
>What would probably happen, as has happened with the aureal vortex, is
>that someone would maintain the open source wrapper.
>

You can't bet on it. You don't know which assumptions the binary code 
part makes on kernel structures' layouts.

> Is nvidia aware of this issue?


Yes they are, a bug report was already filed to them when I searched 
before posting mine. For the text mode, according to the nvidia people 
answering on their support forums this seems to come from the various 
ways hardware are initialised depending on the actual VGA BIOS. For the 
software suspend problem that bites me now this is probably the lack of 
ACPI support in their driver they are already well aware of but as 
swsusp is a patch to the 2.4 (and now 2.6), I don't think they'll take a 
bug report seriously anyway.

>Better would be to return the laptop and follow Joel Jaeggli's advice
>from earlier in this same thread, but unfortunately that's probably not an
>option.
>
>  
>

This laptop was the best hardware I could buy for the money and my 
needs. In fact my problems with the nvidia driver weren't even supposed 
to exist as I first planned to go the XFree86 nv driver way (without 3D 
support as I don't need it). Unfortunately, the LCD panel isn't setup 
properly by the OSS driver version distributed with RH9. I didn't have 
time to try XFree86 CVS so proprietary I went...

>The closed source modules "work best" for me, as some of the code I play
>with uses vertex buffer objects.
>
>I realize that tomorrow nvidia could drop linux support, next week someone
>could discover that echo HI\ MOM > /dev/nvidiactl gives them a root shell.
>
>But for my situation, these things are an acceptable trade for the added
>toys.
>
>  
>
As I said I agree that "work best for me" is obviously a variable...

My e-mail was only meant to bring some facts to the discussion 
describing the problems with proprietary drivers not a "burn all unholy 
hardware without proper OSS driver" flamewar starter.
In the hope that will help cool things down a little, best regards and 
happy new year,

-- 
Lionel Bouton - inet6
---------------------------------------------------------------------
   o              Siege social: 51, rue de Verdun - 92158 Suresnes
  /      _ __ _   Acces Bureaux: 33 rue Benoit Malon - 92150 Suresnes
 / /\  /_  / /_   France
 \/  \/_  / /_/   Tel. +33 (0) 1 41 44 85 36
  Inetsys S.A.    Fax  +33 (0) 1 46 97 20 10
 


  reply	other threads:[~2004-01-02  0:15 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
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 [this message]
     [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=3FF4B829.8060406@inet6.fr \
    --to=lionel.bouton@inet6.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.