Dear Andreas,
I have tested 304.88 and am currently using 310.19-0, and everything
stays the same: I just got used to fiddle with the ViewPortIn and Panning
values to get the required resolution on the internal screen, and I had
to do some nitty gritty tricks to supersed the driver's now stri
On 2012-11-25 12:00, Roberto Di Cosmo wrote:
> After careful investigation, this issue comes from
> an upstream design decision in the 3xx driver series.
>
> In this new series of the NVidia driver, for reasons
> that completely escape my understanding, the user
> is directly exposed to the (power
On Sb, 24 nov 12, 12:01:03, Andreas Beckmann wrote:
> Control: tag -1 moreinfo
>
> On 2012-11-24 11:54, Roberto Di Cosmo wrote:
> > Package: nvidia-vdpau-driver:amd64
> > Version: 304.60-1
>
> > After upgrading to the 3xx version of the NVidia driver,
>
> Please try the most recent driver relea
After careful investigation, this issue comes from
an upstream design decision in the 3xx driver series.
In this new series of the NVidia driver, for reasons
that completely escape my understanding, the user
is directly exposed to the (powerful) details of
the inner working of the GPU pipeline, li
Control: tag -1 moreinfo
On 2012-11-24 11:54, Roberto Di Cosmo wrote:
> Package: nvidia-vdpau-driver:amd64
> Version: 304.60-1
> After upgrading to the 3xx version of the NVidia driver,
Please try the most recent driver releases:
304.64 in unstable
310.19 in experimental
Thanks
Andreas
--
Package: nvidia-vdpau-driver:amd64
Version: 304.60-1
Severity: important
After upgrading to the 3xx version of the NVidia driver,
I only get native resolution for the internal display
on my laptop, which was not the case before.
This is particularly annoying, as it is no longer
possible to use
6 matches
Mail list logo
