Re: Bug#363426: building with new X breaks xlockmore

[bugs]

it works fine with -remote, otherwise it fails silently... could be more
verbose.
it used to work fine the before ! was the resource file
/etc/X11/app-defaults/XLock added meanwhile?

i guess you can close the bug ...

On Wednesday 19 April, 2006 � 09:31:07AM +0200, Michel Dänzer wrote:
> On Tue, 2006-04-18 at 20:36 -0400, Michael Stone wrote:
> > See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=363426
> > 
> > It's possible to duplicate easily by running from a forwarded X session 
> > to your local host.
> 
> Works fine here; please provide more information, in particular the
> symptoms of the failure you encounter.
> 
> 
> -- 
> Earthling Michel Dänzer  | Debian (powerpc), X and DRI developer
> Libre software enthusiast|   http://svcs.affero.net/rm.php?r=daenzer
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#318319: Also for Radeon 9200

[debian-bugs]

With a Radeon 9200 running 6.8.2.dfsg.1-4, I get a working X server
with the following quirks, which looks related to the original bug
reported:

- C-A-Fx doesn't work, it behaves like A-Fx is pressed.
- The 'windows' key is not recognised; xev reports NoSymbol for
  keycode 115.

Rutger.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#551803: [855GM] frequent GPU lockups, system still accessible via ssh

[debian-bugs]

This issue might have been fixed in 
http://bugs.freedesktop.org/show_bug.cgi?id=25475#c88




--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#166413: mga driver doesn't set gamma on second screen

[brett-debian-bugs]

Package: xserver-xfree86
Version: 4.2.1-3

I added a:
Gamma   1.8
to my XF86Config-4 file and upon restart it was obvious that my primary
monitor had it's gamma set to 1.8, but the secondary one was still set
to 1.0 even though the X log and xgamma claimed it was set at 1.8
Setting any gamma with xgamma on the second screen has no effect.  This
is on a matrox G450 dualhead with 2 identical ViewSonic P810 21" monitors.
-Brett Carter



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#166413: mga driver doesn't set gamma on second screen

[brett-debian-bugs]

On Sun, Oct 27, 2002 at 07:25:51PM -0500, [EMAIL PROTECTED] wrote:

I knew I forgot something.  My log and XF86Config are attached.

> 1) Please include the information described in XF86Config(7):
> 
>When   reporting   bugs   to   the   Debian   Bug  Tracking  System  in
>xserver-xfree86, be sure to include a copy  of  your  /etc/X11/XF86Con-
>fig-4  and  /var/log/XFree86.0.log  (or whichever log file the X server
>used - see XFree86(1x)) files in the bug report.   Many  problems  with
>the  X  server are the result of poor configuration.  Furthermore, this
>information aids the Debian Developers  in  determining  your  hardware
>scenario.
> 
> 2) It is possible that this is a hardware limitation.  Multiple-output
> video cards often don't support all features on secondary "heads".

I dual-boot to windows on this same box, I'll see if gamma on the second
monitor is supported there.  Also, I don't have Matrox's hal loaded, I
wonder if that would make a difference?

-Brett Carter





XFree86 Version 4.2.1 (Debian 4.2.1-3 20021016191246 [EMAIL PROTECTED]) / X Window 
System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 3 September 2002
If the server is older than 6-12 months, or if your card is
newer than the above date, look for a newer version before
reporting problems.  (See http://www.XFree86.Org/)
Build Operating System: Linux 2.4.18 i686 [ELF] 
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Fri Oct 25 17:41:50 2002
(==) Using config file: "/etc/X11/XF86Config-4"
(==) ServerLayout "Default Layout"
(**) |-->Screen "DefaultScreen[0]" (0)
(**) |   |-->Monitor "ViewSonic"
(**) |   |-->Device "Matrox G450[0]"
(**) |-->Screen "DefaultScreen[1]" (1)
(**) |   |-->Monitor "ViewSonic"
(**) |   |-->Device "Matrox G450[1]"
(**) |-->Input Device "Generic Keyboard"
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "pc101"
(**) XKB: model: "pc101"
(**) Option "XkbLayout" "us"
(**) XKB: layout: "us"
(==) Keyboard: CustomKeycode disabled
(**) |-->Input Device "Configured Mouse"
(WW) The directory "/usr/lib/X11/fonts/cyrillic" does not exist.
Entry deleted from font path.
(**) FontPath set to 
"unix/:7100,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi"
(==) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(==) ModulePath set to "/usr/X11R6/lib/modules"
(--) using VT number 7

(II) Open APM successful
(II) Module ABI versions:
XFree86 ANSI C Emulation: 0.1
XFree86 Video Driver: 0.5
XFree86 XInput driver : 0.3
XFree86 Server Extension : 0.1
XFree86 Font Renderer : 0.3
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor="The XFree86 Project"
compiled for 4.2.1, module version = 1.0.0
Module class: XFree86 Font Renderer
ABI class: XFree86 Font Renderer, version 0.3
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor="The XFree86 Project"
compiled for 4.2.1, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.5
(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x80010040, mode1Res1 = 0x8000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 1106,0305 card 147b,a401 rev 03 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 1106,8305 card , rev 00 class 06,04,00 hdr 01
(II) PCI: 00:07:0: chip 1106,0686 card 1106, rev 40 class 06,01,00 hdr 80
(II) PCI: 00:07:1: chip 1106,0571 card , rev 06 class 01,01,8a hdr 00
(II) PCI: 00:07:2: chip 1106,3038 card 0925,1234 rev 16 class 0c,03,00 hdr 00
(II) PCI: 00:07:3: chip 1106,3038 card 0925,1234 rev 16 class 0c,03,00 hdr 00
(II) PCI: 00:07:4: chip 1106,3057 card , rev 40 class 06,00,00 hdr 00
(II) PCI: 00:0f:0: chip 11ad,0002 card 2646,f002 rev 20 class 02,00,00 hdr 00
(II) PCI: 00:11:0: chip 9005,0010 card 9005,a180 rev 00 class 01,00,00 hdr 00
(II) PCI: 01:00:0: chip 102b,0525 card 102b,0641 rev 82 class 03,00,00 hdr 00
(II) PCI: End of PCI scan
(II) LoadModule: "sc

Bug#166413: mga driver doesn't set gamma on second screen

[brett-debian-bugs]

On Mon, Oct 28, 2002 at 02:53:35PM -0500, [EMAIL PROTECTED] wrote:
> Okay, I'm getting frustrated with you Matrox guys.

Hopefully this message will clear the air.



> Brett Carter says:
> "After a quick reboot to windows, looks like the results are the same
> there - you can't set the gamma on the second head."

To clarify:  Both in windows 98SE and X setting the gamma only sets it
on the primary display.  It looks to me like the hardware is crippled.
I'll send a message to matrox tech support and see if they indeed can
confirm this.

> Given all this contradiction, I'm making the following decree:
> 
> * Brett Carter is the bug submitter.  He is willing and able to see if
>   he can reproduce this on his specific hardware.  Maybe he is using a
>   Matrox card that can't set gamma on the secondary head.  If so, this
>   is not a bug.  Brett, can you confirm this?

Yes, I :cannot: set the gamma on the secondary head either in windows or
X.  I even flashed my card to the latest bios and driver under windows
just to make sure.  Go ahead and close this report as "not a bug".

> * If someone has a Matrox card that *can* set the gamma on the second
>   head, file a separate report.
>
> Brett has a Matrox MGA G400 AGP rev 130.  That is the only model of card
> that matters for this report.

Umm, actually I've got a matrox G450 - their similar, but slightly
different.  Looks like linux's pci database needs to be updated, and
lspci on my box returns:
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 82)

But I know for a fact I've got a g450 (at least that's what the box
says, and what windows reports).  I'm running 2.4.18 so maybe this is
reported correctly in a newer kernel.  AFIK the g400 isn't even a
dual-head card.  

So to sum things up:
1. On a matrox G450, it looks like you can't set gamma on the secondary
head due to a hardware limitation.
2. This bug can be closed as "not a bug"
3. It looks like there still might be an issue with the g400, which to
my knowledge isn't a dual head card.
-Brett Carter



msg04450/pgp0.pgp
Description: PGP signature

Bug#166413: mga driver doesn't set gamma on second screen

[brett-debian-bugs]

Package: xserver-xfree86
Version: 4.2.1-3

I added a:
Gamma   1.8
to my XF86Config-4 file and upon restart it was obvious that my primary
monitor had it's gamma set to 1.8, but the secondary one was still set
to 1.0 even though the X log and xgamma claimed it was set at 1.8
Setting any gamma with xgamma on the second screen has no effect.  This
is on a matrox G450 dualhead with 2 identical ViewSonic P810 21" monitors.
-Brett Carter

Bug#166413: mga driver doesn't set gamma on second screen

[brett-debian-bugs]

On Sun, Oct 27, 2002 at 07:25:51PM -0500, [EMAIL PROTECTED] wrote:

I knew I forgot something.  My log and XF86Config are attached.

> 1) Please include the information described in XF86Config(7):
> 
>When   reporting   bugs   to   the   Debian   Bug  Tracking  System  in
>xserver-xfree86, be sure to include a copy  of  your  /etc/X11/XF86Con-
>fig-4  and  /var/log/XFree86.0.log  (or whichever log file the X server
>used - see XFree86(1x)) files in the bug report.   Many  problems  with
>the  X  server are the result of poor configuration.  Furthermore, this
>information aids the Debian Developers  in  determining  your  hardware
>scenario.
> 
> 2) It is possible that this is a hardware limitation.  Multiple-output
> video cards often don't support all features on secondary "heads".

I dual-boot to windows on this same box, I'll see if gamma on the second
monitor is supported there.  Also, I don't have Matrox's hal loaded, I
wonder if that would make a difference?

-Brett Carter




XFree86 Version 4.2.1 (Debian 4.2.1-3 20021016191246 [EMAIL PROTECTED]) / X 
Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 3 September 2002
If the server is older than 6-12 months, or if your card is
newer than the above date, look for a newer version before
reporting problems.  (See http://www.XFree86.Org/)
Build Operating System: Linux 2.4.18 i686 [ELF] 
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Fri Oct 25 17:41:50 2002
(==) Using config file: "/etc/X11/XF86Config-4"
(==) ServerLayout "Default Layout"
(**) |-->Screen "DefaultScreen[0]" (0)
(**) |   |-->Monitor "ViewSonic"
(**) |   |-->Device "Matrox G450[0]"
(**) |-->Screen "DefaultScreen[1]" (1)
(**) |   |-->Monitor "ViewSonic"
(**) |   |-->Device "Matrox G450[1]"
(**) |-->Input Device "Generic Keyboard"
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "pc101"
(**) XKB: model: "pc101"
(**) Option "XkbLayout" "us"
(**) XKB: layout: "us"
(==) Keyboard: CustomKeycode disabled
(**) |-->Input Device "Configured Mouse"
(WW) The directory "/usr/lib/X11/fonts/cyrillic" does not exist.
Entry deleted from font path.
(**) FontPath set to 
"unix/:7100,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi"
(==) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(==) ModulePath set to "/usr/X11R6/lib/modules"
(--) using VT number 7

(II) Open APM successful
(II) Module ABI versions:
XFree86 ANSI C Emulation: 0.1
XFree86 Video Driver: 0.5
XFree86 XInput driver : 0.3
XFree86 Server Extension : 0.1
XFree86 Font Renderer : 0.3
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor="The XFree86 Project"
compiled for 4.2.1, module version = 1.0.0
Module class: XFree86 Font Renderer
ABI class: XFree86 Font Renderer, version 0.3
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor="The XFree86 Project"
compiled for 4.2.1, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.5
(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x80010040, mode1Res1 = 0x8000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 1106,0305 card 147b,a401 rev 03 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 1106,8305 card , rev 00 class 06,04,00 hdr 01
(II) PCI: 00:07:0: chip 1106,0686 card 1106, rev 40 class 06,01,00 hdr 80
(II) PCI: 00:07:1: chip 1106,0571 card , rev 06 class 01,01,8a hdr 00
(II) PCI: 00:07:2: chip 1106,3038 card 0925,1234 rev 16 class 0c,03,00 hdr 00
(II) PCI: 00:07:3: chip 1106,3038 card 0925,1234 rev 16 class 0c,03,00 hdr 00
(II) PCI: 00:07:4: chip 1106,3057 card , rev 40 class 06,00,00 hdr 00
(II) PCI: 00:0f:0: chip 11ad,0002 card 2646,f002 rev 20 class 02,00,00 hdr 00
(II) PCI: 00:11:0: chip 9005,0010 card 9005,a180 rev 00 class 01,00,00 hdr 00
(II) PCI: 01:00:0: chip 102b,0525 card 102b,0641 rev 82 class 03,00,00 hdr 00
(II) PCI: End of PCI scan
(II) LoadModule: "sc

Bug#166413: mga driver doesn't set gamma on second screen

[brett-debian-bugs]

On Mon, Oct 28, 2002 at 02:53:35PM -0500, [EMAIL PROTECTED] wrote:
> Okay, I'm getting frustrated with you Matrox guys.

Hopefully this message will clear the air.



> Brett Carter says:
> "After a quick reboot to windows, looks like the results are the same
> there - you can't set the gamma on the second head."

To clarify:  Both in windows 98SE and X setting the gamma only sets it
on the primary display.  It looks to me like the hardware is crippled.
I'll send a message to matrox tech support and see if they indeed can
confirm this.

> Given all this contradiction, I'm making the following decree:
> 
> * Brett Carter is the bug submitter.  He is willing and able to see if
>   he can reproduce this on his specific hardware.  Maybe he is using a
>   Matrox card that can't set gamma on the secondary head.  If so, this
>   is not a bug.  Brett, can you confirm this?

Yes, I :cannot: set the gamma on the secondary head either in windows or
X.  I even flashed my card to the latest bios and driver under windows
just to make sure.  Go ahead and close this report as "not a bug".

> * If someone has a Matrox card that *can* set the gamma on the second
>   head, file a separate report.
>
> Brett has a Matrox MGA G400 AGP rev 130.  That is the only model of card
> that matters for this report.

Umm, actually I've got a matrox G450 - their similar, but slightly
different.  Looks like linux's pci database needs to be updated, and
lspci on my box returns:
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 82)

But I know for a fact I've got a g450 (at least that's what the box
says, and what windows reports).  I'm running 2.4.18 so maybe this is
reported correctly in a newer kernel.  AFIK the g400 isn't even a
dual-head card.  

So to sum things up:
1. On a matrox G450, it looks like you can't set gamma on the secondary
head due to a hardware limitation.
2. This bug can be closed as "not a bug"
3. It looks like there still might be an issue with the g400, which to
my knowledge isn't a dual head card.
-Brett Carter


pgpB7nOVlPnCf.pgp
Description: PGP signature

Bug#360879: xserver-xorg: Xorg's radeon driver does not seem to supportDVI on docking station

[Eric Lavarde - Debian Bugs]

Hi,

the problem is definitely still there with etch (version 6.6.3-2).
My system is productive (laptop at work) so I'm not too keen to install
experimental on it. But if there would be a backported version, I'd be
happy to try.

Eric

Brice Goglin said:
> Hi,
>
> About a year ago, you reported a bug to the Debian BTS regarding Xorg's
> radeon driver having problem with the DVI output of your docking
> station. Did you reproduce this problem recently? With Xorg/Etch? With
> latest ATI driver 6.6.192 is currently in experimental?
>
> Thanks,
> Brice
>
>
>


-- 

Bug#360879: [Bug 3621] radeon output handling re-work

[Eric Lavarde - Debian Bugs]

Hi,

from the upstream bug, which has been recently closed, the issue is fixed
in SVN, and fix should be released with version 6.7.

Thanks, Eric

[EMAIL PROTECTED] said:
> http://bugs.freedesktop.org/show_bug.cgi?id=3621
>
> --- Comment #107 from [EMAIL PROTECTED]  2007-07-27 05:47 PST ---
> (In reply to comment #106)
>> Sorry if I can read this information from somewhere else, but in which
>> version
>> can we expect this patch to be released?
>
> The soon to be released 6.7 will have these changes and then the randr
> branch
> breaks it down even nicer.
>
>
> --
> Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
> --- You are receiving this mail because: ---
> You are on the CC list for the bug, or are watching someone who is.
>
>


-- 
Eric de France, d'Allemagne et de Navarre

Bug#360879: xserver-xorg: Xorg's radeon driver does not seemto support DVI on docking station

[Eric Lavarde - Debian Bugs]

Hi,

> On Tue, 2006-04-11 at 10:06 +0200, Eric Lavarde - Debian Bugs wrote:
>>
>> > On Wed, 2006-04-05 at 10:22 +0200, Eric Lavarde wrote:
>> >>
>> >> Before upgrading to etch/xorg from sarge/xfree86, I was able to have
>> one
>> >> configuration (attached as xorg.conf.200602171936) and the xserver
>> would
>> >> do the right thing:
>> >> - laptop standalone: 1024x768 on the internal display.
>> >> - laptop in docking station: 1280x1024 on external screen.
>> >> (I'm *not* trying to have something fancy like dual screen!)
>> >
>> > Both config and log file included by the reportbug script show a dual
>> > screen configuration though.
>> Might be, I'm not saying I'm fully understanding how all the parameters
>> work together (I'm grateful for a link to synthetic documentation of
>> those).
>
> Well, the "Layout" section references several screens. :)
>
>
>> > Please attach log files obtained when starting with
>> > xorg.conf.200602171936, both when docked and not.
>> Here it is! File names should be obvious.
>
> Thanks. Apparently, the driver only detects the internal display in both
> cases. You're saying neither case works with this config file? Does it
> make a difference if it's already docked on bootup? Or if you use Option
> "MonitorLayout" "TMDS" when docked?
No, it works undocked. When docked, the external screen doesn't show any
picture, but X seems happy with it (not me!), so that I assume it shows
something on the internal (closed) LCD.
But I can try the option.

>
>
>> >>  Option  "MonitorLayout" "TMDS,LVDS"
>> >
>> > This combination can't work currently because the driver doesn't
>> support
>> > external TMDS chips yet (the Radeon chip only has one TMDS unit
>> > integrated, which is used for the internal display).
>> Well, it's not explained in radeon(1).
>
> You may want to look at
> https://bugs.freedesktop.org/show_bug.cgi?id=3621 . Unfortunately, it
> looks like LVDS+TMDS is still not working with the superpatch referenced
> there.
Eerg, you mean patching, recompiling, etc... ? Hmpf, need to think about
it, especially where you complain in there about regression issues :->
(it's my work laptop, so I'm not too keen to test too much on it)

>
> Speaking of upstream bugzilla, you may want to report this problem there
> as well, assuming it hasn't yet.
Sounds like the bug you pointed me to is the potential solution to the
issue, no? (I'm referring to: "- LVDS + internal TMDS.  if you have a
laptop or docking station with LVDS and a DVI port, ...")

I'll have anyway a deeper look at the entry.

Thanks, Eric

-- 

Bug#360879: xserver-xorg: Xorg's radeon driver does not seemto support DVI on docking station

[Eric Lavarde - Debian Bugs]

Hi,

>> > Thanks. Apparently, the driver only detects the internal display in
>> both
>> > cases. You're saying neither case works with this config file? Does it
>> > make a difference if it's already docked on bootup? Or if you use
>> Option
>> > "MonitorLayout" "TMDS" when docked?
>> No, it works undocked. When docked, the external screen doesn't show any
>> picture, but X seems happy with it (not me!), so that I assume it shows
>> something on the internal (closed) LCD.
>> But I can try the option.
>
> Please do, and/or boot the machine docked.
Yes, the above option added to my original xfree86.conf does make it work
docked, but (of course) then it doesn't work undocked (xorg seems to try
to drive the internal LCD with 1280x1024). It works undocked with LVDS
instead, or without the option.

>> > Speaking of upstream bugzilla, you may want to report this problem
>> there
>> > as well, assuming it hasn't yet.
>> Sounds like the bug you pointed me to is the potential solution to the
>> issue, no? (I'm referring to: "- LVDS + internal TMDS.  if you have a
>> laptop or docking station with LVDS and a DVI port, ...")
>
> Yes, once that works, at least Option "MonitorLayout" "LVDS,TMDS" should
> work. Autodetection of the docking station may be a different story
> though.
Yes, it looks like the remaining issue for me: the xserver doesn't
automatically switch between TMDS and LVDS. Any further hint, or is my
last chance to place a bug in bugzilla?

Thanks for your help anyway,
Eric

-- 

Bug#360879: xserver-xorg: Xorg's radeon driver does not seemto support DVI on docking station

[Eric Lavarde - Debian Bugs]

Hi,

> On Mon, 2006-04-17 at 21:29 +0200, Eric Lavarde - Debian Bugs wrote:
>> Or if you use
>> >> Option
>> >> > "MonitorLayout" "TMDS" when docked?
[...]
>> Yes, the above option added to my original xfree86.conf does make it
>> work
>> docked, but (of course) then it doesn't work undocked (xorg seems to try
>> to drive the internal LCD with 1280x1024). It works undocked with LVDS
>> instead, or without the option.
>
> Out of curiosity, does it have any impact on the autodetection or
> otherwise if you boot the machine while it's docked?
I am booting while already docked! Being able to dock/undock on the fly is
my next dream! Who do I need to kill to get this one?

>> > Autodetection of the docking station may be a different story
>> > though.
>> Yes, it looks like the remaining issue for me: the xserver doesn't
>> automatically switch between TMDS and LVDS.
>
> Well, once LVDS and TMDS are supported together, this shouldn't matter
> so much, as you can force them both on.
Right, in clone mode, it wouldn't matter much.

So, anyway, what do we do with this bug? Close it or is there still some
potential action able to help me?

Eric

-- 

Bug#360879: xserver-xorg: Xorg's radeon driver does not seemto support DVI on docking station

[Eric Lavarde - Debian Bugs]

Hello,

it's been a while since we last discussed about this bug.
In the mean time the upstream bug 
 seems to have made 
some good progress.


Would it be too shameless to ask if it would be possible to get this 
patch into Debian's xserver-xorg-video-ati package? e.g. in experimental?!


Thanks, Eric


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]