On 2010-07-12 19:33:15 +0100, Julien Cristau wrote:
> We don't have nvidia hardware, so maybe our perception is flawed. If
> people think we should keep that driver, please explain why. If the
> reason is "nouveau doesn't work for me", we'll ignore your reply unless
> it comes with a bugs.freedes
On Tue, 13 Jul 2010 04:31:56 -0400 (EDT), Cyril Brulebois wrote:
>
> Care to share a reference to the bug you reported?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589452
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debi
On Tue, 13 Jul 2010 11:36:10 -0400 (EDT), Cyril Brulebois wrote:
> Cyril Brulebois wrote:
>> ... I didn't ask for an UMS-related bug reference.
For some reason I was under the impression that KMS drivers were
limited to modes which can be set by the video BIOS. I stand corrected.
A bug report wil
On Dienstag, 13. Juli 2010, Julien Cristau wrote:
> > I would say that you should ask for adoption or help maintaining the
> > package.
> What is this supposed to mean?
he missed all the X strike force requests for help, I'd say.
signature.asc
Description: This is a digitally signed message part
On Tue, Jul 13, 2010 at 19:41:13 +0200, Salvo Tomaselli wrote:
> On Monday 12 July 2010 20:33:15 Julien Cristau wrote:
> > We don't have nvidia hardware, so maybe our perception is flawed.
> I would say that you should ask for adoption or help maintaining the package.
>
What is this supposed to
On Monday 12 July 2010 20:33:15 Julien Cristau wrote:
> We don't have nvidia hardware, so maybe our perception is flawed.
I would say that you should ask for adoption or help maintaining the package.
Bye
--
Salvo Tomaselli
signature.asc
Description: This is a digitally signed message part.
> On 2010-07-13 04:31 +0200, Stephen Powell wrote:
> > I designed a custom video mode for 1024x768 @ 100 Hz Interlaced
> > that is even better. (100 Hz is the maximum vertical refresh rate
> > of the monitor). This mode is still within the video bandwidth of
> > the monitor (maximum supported pi
Stephen Powell (13/07/2010):
> Cyril Brulebois wrote:
> > Care to share a reference to the bug you reported?
> As Sven Joachim has pointed out, this would be an exercise in
> futility. Upstream deliberately removed support for UMS a while
> ago.
Guess what, I *know*. And I didn't ask for an UMS-
On 2010-07-13 04:31 +0200, Stephen Powell wrote:
> Second, I can't seem to get an 80-column virtual console with KMS.
> Yes, I can change the font size, but the traditional 80-column display
> doesn't seem to present itself. Maybe I just haven't tried hard enough.
It's not possible with a horizo
Le 13/07/2010 17:11, Stephen Powell a écrit :
> As of xserver-xorg-video-intel 2:2.9.1-4, which is current in Squeeze,
> and for the i915G chipset, I can still pass
>
>modeset=0
>
> to the i915 module and the X driver will still work. Are you saying that
> this is going to be taken away from m
Cyril Brulebois wrote:
> Care to share a reference to the bug you reported?
Ben Hutchings wrote:
> I assume you've filed a bug requesting support for custom modes, as
> requested by the X maintainers?
As Sven Joachim has pointed out, this would be an exercise in futility.
Upstream deliberately rem
On Mon, 2010-07-12 at 22:31 -0400, Stephen Powell wrote:
[...]
> But I can't get the nouveau driver
> to use my custom 100 Hz Interlaced mode, or even the VESA standard 87 Hz
> Interlaced mode. It insists on running the monitor at 60 Hz
> non-interlaced. And my eyes just won't take that for very
Stephen Powell (12/07/2010):
> But I can't get the nouveau driver to use my custom 100 Hz
> Interlaced mode, or even the VESA standard 87 Hz Interlaced mode.
> It insists on running the monitor at 60 Hz non-interlaced. And my
> eyes just won't take that for very long. At 100 Hz interlaced, I
> c
On Mon, 12 Jul 2010 15:24:56 -0400 (EDT), Sven Joachim wrote:
> On 2010-07-12 21:09 +0200, Stephen Powell wrote:
>> If nouveau set KMS by default, as the intel driver does, but did not
>> *require* KMS, I would agree. But the last time I checked, using the nouveau
>> driver *forces* KMS. I don't
On Mon, Jul 12, 2010 at 08:05:25PM +, Sven Joachim wrote:
> On 2010-07-12 21:09 +0200, Stephen Powell wrote:
>
> > If nouveau set KMS by default, as the intel driver does, but did not
> > *require* KMS, I would agree. But the last time I checked, using the
> > nouveau
> > driver *forces* KMS
On 2010-07-12 21:09 +0200, Stephen Powell wrote:
> If nouveau set KMS by default, as the intel driver does, but did not
> *require* KMS, I would agree. But the last time I checked, using the nouveau
> driver *forces* KMS. I don't like that. I still use, and prefer, hardware
> text mode virtual
On Mon, 12 Jul 2010 14:33:15 -0400 (EDT), Julien Cristau wrote:
>
> We're considering the removal of xserver-xorg-video-nv (the "free" X
> driver for nvidia hardware) from sid and squeeze.
I'm replying to both debian-x and debian-devel, but I am only
subscribed to debian-devel. If you post only
Hi,
We're considering the removal of xserver-xorg-video-nv (the "free" X
driver for nvidia hardware) from sid and squeeze.
Some reasons are:
- the source is obfuscated [0]
- nvidia stopped maintaining it [1]
- nouveau seems to be mostly ready to replace it, although it has some
pains, including
18 matches
Mail list logo
