Pavel Machek wrote :
> Hi!
>
> > > I use XFree86 4.0.1 with nvidia-drivers 0.96.
> >
> > Take it up with nvidia. Obfuscated effectively binary only code isnt anyone
> > elses problem
It is not only "effectively binary" but "actually binary".
There are no sources, only a few line of C "glue"
Hi!
> > I use XFree86 4.0.1 with nvidia-drivers 0.96.
>
> Take it up with nvidia. Obfuscated effectively binary only code isnt anyone
> elses problem
Is it legal, BTW? Obfuscated drivers should _not_ be linked into
kernel, because they are not "form preferable for editing".
The source code f
I'm having no problems with 2.4.2-ac6, using XFree86 4.0.2 and the
included nv (nvidia) driver. Works great with my geForce2 GTS,
without any binary only drivers. 4.0.2 seemed to have improved
support for nvidia chips.
If it's any help, I'm also using the rivafb for console (although not
for X)
> I use XFree86 4.0.1 with nvidia-drivers 0.96.
Take it up with nvidia. Obfuscated effectively binary only code isnt anyone
elses problem
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.ke
"Manfred H. Winter" wrote:
> I'm going back to vanilla 2.4.2 for now. Is there another way to get
> loop to work?
Working fine here:
2.4.2 + Axboe's loop patch + Morton's low latency patch
jjs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message t
Hi!
Yesterday I've upgraded my 2.4.2 kernel to ac5, because loop-device
seems not to work in plain 2.4.2. But now my X-server crashes.
When I start with startx, X comes up, gnome starts, sawfish starts. Then
the system freezes. Even SysRQ-keys don't work.
I use XFree86 4.0.1 with nvidia-drivers
6 matches
Mail list logo
