From: Nuno Alexandre <kernel@imaginere.dk>
To: eddie tejeda <eddie@nailchipper.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: VIA and NVIDIA
Date: Wed, 14 Jan 2004 20:16:37 +0100 [thread overview]
Message-ID: <20040114201637.566a9330@Genbox> (raw)
In-Reply-To: <1074106424.6839.15.camel@applehead>
On Wed, 14 Jan 2004 13:53:45 -0500
eddie tejeda wrote:
> I have an NVidia Videocard with a VIA KT333 chipset motherboard..
>
> i am about to burst.. i am tried just about every bug-fix, workaround
> and hack, written everywhere in the internet.. to get the Nvidia driver
> to work on my machine. NV works fine.
>
> i've been trying this for 6months and finally caving and think that it
> has to be Linux's VIA support. which i've read there are some problems.
>
> I am willing to present all information needed.. but this is the post
> i've posted all over NVIDIA boards:
>
>
>
> ***********
>
>
> The screen used to go black, and flicker blue once, and stop responding.
> number lock works... i can SSH into machine to get logs.. if i try and
> kill X it crashes the machine hard... complete lock out...
>
> when i run ps aux i can see X is running 99% of CPU
>
> All the options enabled in XFConfig attached have been added and removed
> (when options are removed the flicker happens.. if not... I now get a
> screen with ASCII printed.. just junk.. no flicker.)
>
> I have:
> Athlon XP 2200
> Soyo Ultra Platinum, KT333
> PNY GeForce 3 Ti200
> Crucial 512 DDR-333
> ALL tested kernels (2.4.22+, 2.6.x)
> ALL distributions (Fedora, Redhat, Debian)
>
> I have tested with following kernel options on and off:
> ACPI/APM
> Fb-Nvidia/Riva
> Pre-empt
> AGPART
>
> i attached my XFConfig, XFree86.log and .config(2.6.0)
>
>
> ************
>
>
> i am almost certain it is linux.. because the cards work on windows
> machines perfect. and i have tried a few cards on this linux machine the
> same happens.
>
> also, most people who have the problems i described.... they get fixed
> with the OPTIONS that i have on my XF86Config. i have tested them all on
> and off.
>
>
> i would like to see linux do 3d.. one day. :o)...thanks in advance, i
> love the work you guys do and hope to contribute in the future..
>
Hi Eddie.
I have Asus A7V, KT 333
AMD 1800+
Gforce 2gts
768 DDR Kingston
settings on
pre-empt
AGPART
not using framebuffer.
As you see, very similar setup, apart from the riva fb.
But I have had a framebuffer working with help from some patches available on the gentoo forums, but they don't work on the latest
kernel build. So i dropped it.
I never had any problems with the nvidia drivers.
not on 2.4 or 2.6 always worked :)
I dont know how this can help you, but having 2 similar setups
maybe helps finding whats wrong on your setup that makes it not work.
Feel free to ask for anything that might help you.
--
Best regards - Nuno Alexandre - na:imaginere.dk
Gpg: EA74637D - http://www.fluxmod.dk
-----------------------------------------------/
next prev parent reply other threads:[~2004-01-14 19:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 18:53 VIA and NVIDIA eddie tejeda
2004-01-14 19:16 ` Nuno Alexandre [this message]
2004-01-14 22:28 ` eddie tejeda
2004-01-15 15:58 ` Charles Shannon Hendrix
2004-01-15 16:52 ` Valdis.Kletnieks
2004-01-15 17:08 ` eddie tejeda
2004-01-14 19:19 ` Max Valdez
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=20040114201637.566a9330@Genbox \
--to=kernel@imaginere.dk \
--cc=eddie@nailchipper.com \
--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.