Bug#483314: xserver-xorg-video-intel: [945GM] Wrong resolution used for external monitor
On Wed, May 28, 2008 at 12:25:26 +0200, Sander Marechal wrote: I have a Dell D520 laptop with an Intel 945GM chipset. The internal 15 screen has a resolution of 1400x1050. When I hook up an external monitor (A bog standard Dell 17 TFT, model no. 1704FPTt) then the intel driver correctly detects that it has a maximum resolution of 1280x1024 (according to Xorg.0.log, see attachment) but X still seems to start a 1400x1050 display. I'm not sure what the problem is here. The internal panel and the external monitor are both enabled, according to the log the panel uses 1400x1050 and the external monitor 1280x1024. What behaviour did you expect instead? You can disable the internal screen with xrandr --output LVDS --off, but by default all connected outputs are enabled. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483314: xserver-xorg-video-intel: [945GM] Wrong resolution used for external monitor
On Wed, May 28, 2008 at 16:22:40 +0200, Sander Marechal wrote: Julien Cristau writes: On Wed, May 28, 2008 at 12:25:26 +0200, Sander Marechal wrote: I have a Dell D520 laptop with an Intel 945GM chipset. The internal 15 screen has a resolution of 1400x1050. When I hook up an external monitor (A bog standard Dell 17 TFT, model no. 1704FPTt) then the intel driver correctly detects that it has a maximum resolution of 1280x1024 (according to Xorg.0.log, see attachment) but X still seems to start a 1400x1050 display. I'm not sure what the problem is here. The internal panel and the external monitor are both enabled, according to the log the panel uses 1400x1050 and the external monitor 1280x1024. What behaviour did you expect instead? You can disable the internal screen with xrandr --output LVDS --off, but by default all connected outputs are enabled. The problem is that the external monitor also seems to be running 1400x1050, but I only see the top-left 1280x1024 part of it. I can move Then that monitor is running at 1280x1024 :) my mouse in the parts between 1280 and 1400 horizontal, and between the 1024 and 1050 vertical. The mouse cursor disappears, but it's definitely there, because it takes time to scroll back. When I maximize an application, it becomes 1400 pixels wide and 1050 pixels (minus the height of the gnome-panel) high. That means I don't see the minimize/maximize/close buttons. They're off-screen. When iceweasel is maximized, I don't see the statusbar at the bottom. It falls behind the gnome-panel. Your desktop is 1400x1050, because that's the dimension of the biggest connected output. Note that my laptop lid is closed. You can tell X (through xrandr) to turn off the LVDS before closing the lid, manually or using a script. Then the desktop will be resized to the dimension of the other output. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483314: xserver-xorg-video-intel: [945GM] Wrong resolution used for external monitor
Julien Cristau writes: On Wed, May 28, 2008 at 12:25:26 +0200, Sander Marechal wrote: I have a Dell D520 laptop with an Intel 945GM chipset. The internal 15 screen has a resolution of 1400x1050. When I hook up an external monitor (A bog standard Dell 17 TFT, model no. 1704FPTt) then the intel driver correctly detects that it has a maximum resolution of 1280x1024 (according to Xorg.0.log, see attachment) but X still seems to start a 1400x1050 display. I'm not sure what the problem is here. The internal panel and the external monitor are both enabled, according to the log the panel uses 1400x1050 and the external monitor 1280x1024. What behaviour did you expect instead? You can disable the internal screen with xrandr --output LVDS --off, but by default all connected outputs are enabled. The problem is that the external monitor also seems to be running 1400x1050, but I only see the top-left 1280x1024 part of it. I can move my mouse in the parts between 1280 and 1400 horizontal, and between the 1024 and 1050 vertical. The mouse cursor disappears, but it's definitely there, because it takes time to scroll back. When I maximize an application, it becomes 1400 pixels wide and 1050 pixels (minus the height of the gnome-panel) high. That means I don't see the minimize/maximize/close buttons. They're off-screen. When iceweasel is maximized, I don't see the statusbar at the bottom. It falls behind the gnome-panel. Note that my laptop lid is closed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483314: xserver-xorg-video-intel: [945GM] Wrong resolution used for external monitor
Julien Cristau writes: Your desktop is 1400x1050, because that's the dimension of the biggest connected output. I just opened my lid and indeed, my laptop screen is on and shows the desktop. So this is expected then. Note that my laptop lid is closed. You can tell X (through xrandr) to turn off the LVDS before closing the lid, manually or using a script. Then the desktop will be resized to the dimension of the other output. I think the bug may be the switching between internal and external monitor then. Under Etch, when I started my laptop with the lid closed, the desktop would be 1280x1024. When I openend my lid, the internal display would be off. I was able to switch between internal monitor and external monitor with the function keys (on my Dell, it's Fn+F8 and reads CRT/LCD). It seems that when I boot the laptop with the lid closed under Lenny, the internal monitor is still working. And my Fn+F8 key doesn't work anymore to switch between the displays. Is this also a bug in Xorg somewhere? Any idea where I should reassign this to? Thanks in advance, -- Sander Marechal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483314: xserver-xorg-video-intel: [945GM] Wrong resolution used for external monitor
On Wed, May 28, 2008 at 23:40:11 +0200, Sander Marechal wrote: That appears to me as quite a regression for laptop users. Especially today on newer laptops with all the non-standard widescreen display sizes. I consider it quite an improvement as a laptop user, so clearly this is not as clear cut as you say. Can't the keyboard part of X.org intercept the keys for switching between monitors (Fn+F8) and execute the correct xrandr commands to toggle the display on and off? *If* this key combination sends something via the keyboard device, then it would be possible to have the desktop environment see it and act appropriately. This is not always the case (varies between laptops), sometimes the firmware acts on it directly and changes things behind the driver's back. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483314: xserver-xorg-video-intel: [945GM] Wrong resolution used for external monitor
Julien Cristau wrote: On Wed, May 28, 2008 at 23:40:11 +0200, Sander Marechal wrote: That appears to me as quite a regression for laptop users. Especially today on newer laptops with all the non-standard widescreen display sizes. I consider it quite an improvement as a laptop user, so clearly this is not as clear cut as you say. Perhaps not, but hooking a regular 4:3 monitor to a laptop with a closed lid, then booting is a fairly common use case I think. It describes a large class of user who take a laptop to work, put it in a docking station and boot. I haven't seen many offices with 24 widescreen LCD's for everone :-) Can't the keyboard part of X.org intercept the keys for switching between monitors (Fn+F8) and execute the correct xrandr commands to toggle the display on and off? *If* this key combination sends something via the keyboard device, then it would be possible to have the desktop environment see it and act appropriately. This is not always the case (varies between laptops), sometimes the firmware acts on it directly and changes things behind the driver's back. I think that for my Dell D520 the combo is sent. Fn+F8 used to work under Etch but now it does nothing. If it was purely hardware and firmware then Lenny shouldn't be able to prevent the key combo from working, right? Any way I can check/log this? -- Sander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
