Kernel-2.6.7-1.494 and Nvidia Drivers

[Brian R Smith]

> If you want to make other testers aware of your problems and
> compare notes with other testers use fedora-test-list

For testers of Fedora Core development releases...

That's what I've been using... is there another fedora-test-list I
should be aware of?

Quoting myself from the message you quoted:

>> I know that you guys do not tailor the kernel to run 
>> with the nvidia drivers, that its nvidia's responsibility 
>> to produce a driver that will run on their customers machine.

Never mind then.  I know you guys can't do anything about the nvidia
drivers because you don't have access to the source, as I stated in the
same post that you quoted.

That said, I only posted to assist users who may run into the same
problem, fully aware of how the linux development process goes as far as
proprietary drivers are concerned: avoid them like the plague and keep
them as far from the tree as possible.  If FC3 or kernel-2.6.8
w/PREEMPT_VOLUNTARY is released and this problem still exists for people
like me, then we will go to nvidia for a fix, because it is their
problem, not yours.

-brian

On Wed, 2004-07-28 at 11:55, Jeff Spaleta wrote:
> On Wed, 28 Jul 2004 10:19:25 -0400, Brian R Smith
> <brian at cypher.acomp.usf.edu> wrote:
> > I just figured there might be _someone_
> > on here that would benefit from my encounter.
> 
> I'm sure that some user out there will end up eventually googling and
> finding your report.
> So in the most general sense, you are probably right.. someone will
> end up finding your report not unuseful. But certaintly, a report like
> this is unuseful to developers since any problems that only happen
> when nvidia or other proprietary kernel module take an immense amount
> of effort to debug without access to the code. And even if the kernel
> developers could diagnose this problem after considerable effort, they
> can't necessarily fix the problem if its nvidia driver specific
> becuase they don't have access to nvidia's codebase.
> 
> Useful reports to developers, whether it be in this mailinglist or
> bugzilla or the irc chat, need to be situations that developers can
> attempt to reproduce AND diagnose via code review.  There must be a
> path towards achievable resolution for it to be worth their time, and
> to be useful to them.  So please be considerate the audience you are
> trying to reach and use the appropriate forum.  If you want to make
> other testers aware of your problems and compare notes with other
> testers use fedora-test-list.
> 
> -jef