Processing commands for [EMAIL PROTECTED]:
> retitle 198447 Matrox Dual-Head: Second Monitor DDC Queries Going To First
> Monitor Instead
Bug#198447: G450 Dual-Head: Second Monitor I2C Detection Happening Incorrectly
Changed Bug title.
> tags 198447 upstream
Bug#198447: Matrox Dual-Hea
Processing commands for [EMAIL PROTECTED]:
> retitle 198447 Matrox Dual-Head: Second Monitor DDC Queries Going To First Monitor
> Instead
Bug#198447: G450 Dual-Head: Second Monitor I2C Detection Happening Incorrectly
Changed Bug title.
> tags 198447 upstream
Bug#198447: Matrox Dual-Hea
On Thu, Jun 26, 2003 at 01:01:36AM -0500, Jason Bucata wrote:
> On Tue, Jun 24, 2003 at 09:51:13PM -0700, Marc Wilson wrote:
> > I got around this by explicitly disabling I2C on both heads. I knew
> > perfectly well what the specifications of my monitors were... I didn't
> > need X to figure it ou
retitle 198447 Matrox Dual-Head: Second Monitor DDC Queries Going To First Monitor
Instead
tags 198447 upstream
thanks
On Thu, Jun 26, 2003 at 08:28:42PM -0700, Marc Wilson wrote:
> On Thu, Jun 26, 2003 at 01:01:36AM -0500, Jason Bucata wrote:
> > On Tue, Jun 24, 2003 at 09:51:13PM -0700, Marc Wi
retitle 198447 Matrox Dual-Head: Second Monitor DDC Queries Going To First
Monitor Instead
tags 198447 upstream
thanks
On Thu, Jun 26, 2003 at 08:28:42PM -0700, Marc Wilson wrote:
> On Thu, Jun 26, 2003 at 01:01:36AM -0500, Jason Bucata wrote:
> > On Tue, Jun 24, 2003 at 09:51:13PM -0700, Marc Wi
On Thu, Jun 26, 2003 at 01:01:36AM -0500, Jason Bucata wrote:
> On Tue, Jun 24, 2003 at 09:51:13PM -0700, Marc Wilson wrote:
> > I got around this by explicitly disabling I2C on both heads. I knew
> > perfectly well what the specifications of my monitors were... I didn't
> > need X to figure it ou
On Tue, Jun 24, 2003 at 09:51:13PM -0700, Marc Wilson wrote:
> On Sun, Jun 22, 2003 at 06:02:22PM -0500, Jason Bucata wrote:
> > The explicit frequency settings in the configuration file appear to be
> > ignored.
>
> I got around this by explicitly disabling I2C on both heads. I knew
> perfectly
On Tue, Jun 24, 2003 at 09:51:13PM -0700, Marc Wilson wrote:
> On Sun, Jun 22, 2003 at 06:02:22PM -0500, Jason Bucata wrote:
> > The explicit frequency settings in the configuration file appear to be
> > ignored.
>
> I got around this by explicitly disabling I2C on both heads. I knew
> perfectly
On Sun, Jun 22, 2003 at 06:02:22PM -0500, Jason Bucata wrote:
> I have two different monitors that I'm trying to use in a dual-head
> configuration, if only just to experiment with it. The I2C monitor info
> detection isn't working on the second head. In the logs, I see it
> detecting the first m
On Sun, Jun 22, 2003 at 06:02:22PM -0500, Jason Bucata wrote:
> I have two different monitors that I'm trying to use in a dual-head
> configuration, if only just to experiment with it. The I2C monitor info
> detection isn't working on the second head. In the logs, I see it
> detecting the first m
Package: xserver-xfree86
Version: 4.1.0-16
Severity: normal
Kernel version: 2.4.21-rc6-ac1
Libc version: 2.2.5-11.5
I have two different monitors that I'm trying to use in a dual-head
configuration, if only just to experiment with it. The I2C monitor info
detection isn't working on the second he
Package: xserver-xfree86
Version: 4.1.0-16
Severity: normal
Kernel version: 2.4.21-rc6-ac1
Libc version: 2.2.5-11.5
I have two different monitors that I'm trying to use in a dual-head
configuration, if only just to experiment with it. The I2C monitor info
detection isn't working on the second he
12 matches
Mail list logo