From: Roberto Sanchez <rcsanchez97@yahoo.es>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4 vs 2.6
Date: Sun, 14 Dec 2003 11:01:27 -0500 [thread overview]
Message-ID: <3FDC8957.4000602@yahoo.es> (raw)
In-Reply-To: <3FDC0BAC.8020909@mscc.huji.ac.il>
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]
Voicu Liviu wrote:
> My specs:
> Cpu:Athlon XP 2500+ BARTON {10x190}
> Mobo:EPOX 8RDA3 + NFORCE 2
> Ram:Corsair TWINX 512 3200LL{dual channel/11-3-2-2.0}
> Fan:Cooler Master +7
> Video:Hercules 3D Prophet 9600 PRO Radeon 128MB
>
> My Hercules 3D Prophet 9600 PRO Radeon simply freezes my comp. with
> ati-drivers from ati.com so I need to press reset!(so I only can run
> console)
> My sound (nvidia on board) works very shitty and I have no control on
> it (level sound I mean).
> I was running 2.4.23 vanilla + lvm1 so I moved to 2.6 vanilla+lvm2 and
> now I can not move back
>
> These are my biggest problems with 2.6.
Have you treid the in kernel DRI drivers? They work with my Radeon
9000 on an nForce2.
Also, why can't you go back to 2.4.23?
-Roberto
[-- Attachment #2: Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2003-12-14 16:01 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 6:20 XFS for 2.4 Nathan Scott
2003-12-01 9:24 ` Jens Axboe
2003-12-01 9:44 ` Stefan Smietanowski
2003-12-01 9:45 ` Jens Axboe
2003-12-01 14:06 ` Marcelo Tosatti
2003-12-01 22:10 ` Nathan Scott
2003-12-01 22:20 ` Larry McVoy
2003-12-02 0:23 ` Nathan Scott
2003-12-02 11:22 ` Marcelo Tosatti
2003-12-02 18:05 ` Austin Gonyou
2003-12-02 19:55 ` Stephan von Krawczynski
2003-12-02 20:05 ` Marcelo Tosatti
2003-12-02 20:16 ` Lawrence Walton
2003-12-03 19:01 ` bill davidsen
2003-12-03 20:45 ` Willy Tarreau
2003-12-03 21:17 ` bill davidsen
2003-12-03 21:48 ` Joel Becker
2003-12-03 22:17 ` bill davidsen
2003-12-03 22:08 ` Ed Sweetman
2003-12-04 5:21 ` Willy Tarreau
2003-12-04 0:34 ` Clemens Schwaighofer
2003-12-04 5:33 ` Willy Tarreau
2003-12-04 10:13 ` Clemens Schwaighofer
2003-12-02 11:18 ` Marcelo Tosatti
2003-12-02 11:48 ` Marcelo Tosatti
2003-12-02 15:34 ` Russell Cattelan
2003-12-02 15:50 ` Marcelo Tosatti
2003-12-02 16:10 ` Darrell Michaud
2003-12-02 16:21 ` Austin Gonyou
2003-12-02 16:28 ` Jeff Garzik
2003-12-02 16:57 ` venom
2003-12-02 17:41 ` Stefan Smietanowski
2003-12-02 18:01 ` Russell Cattelan
2003-12-02 16:13 ` Jeremy Jackson
2003-12-02 0:51 ` Clemens Schwaighofer
2003-12-02 1:26 ` Marcos D. Marado Torres
2003-12-14 1:08 ` 2.4 vs 2.6 Jan Rychter
2003-12-14 1:01 ` Roberto Sanchez
2003-12-14 11:23 ` Måns Rullgård
2003-12-14 18:09 ` Daniel Gryniewicz
2003-12-14 1:53 ` Daniel Gryniewicz
2003-12-14 2:01 ` coderman
2003-12-14 20:23 ` tabris
2003-12-14 7:05 ` Voicu Liviu
2003-12-14 16:01 ` Roberto Sanchez [this message]
2003-12-14 17:32 ` Voicu Liviu
2003-12-15 7:23 ` Harry McGregor
2003-12-15 7:51 ` Voicu Liviu
2003-12-14 11:24 ` Frederik Deweerdt
2003-12-01 21:00 ` XFS for 2.4 Dan Yocum
2003-12-01 21:50 ` Bryan Whitehead
2003-12-01 22:01 ` Jeffrey E. Hundstad
2003-12-01 22:13 ` Gerardo Exequiel Pozzi
2003-12-02 2:54 ` Joshua Schmidlkofer
2003-12-02 11:02 ` Maciej Soltysiak
[not found] <fa.iaibikf.1l5injd@ifi.uio.no>
[not found] ` <fa.m5245vp.h0ukb5@ifi.uio.no>
2003-12-15 10:56 ` 2.4 vs 2.6 Anssi Saari
2003-12-15 17:25 ` David Ford
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=3FDC8957.4000602@yahoo.es \
--to=rcsanchez97@yahoo.es \
--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;
as well as URLs for NNTP newsgroup(s).