xorg uses laptop video BIOS 'Panel Size' for external monitors, so apps end up confined to small space in top left of screen

[Mike MacCana]

Binary package hint: xserver-xorg-core

Removing the xorg.conf and allowing X to determine video settings from the monitor, the following happens (I'll attach a picture shortly):

* xorg correctly uses the external monitor to display GDM
* The monitor runs at the correct resolution (eg, 1600 x 1200), with GDM background colors and wallpapers occupying the whole screen (eg, 1600 x 1200)
* Applications, for example, GDM, or the gnome panel, are confined to a 1024 x 768 area in the top left corner of the screen
* After logging on, non-maximized applications that are placed inside the 1024 x 768 area will maximise to 1024 x 768.
* After logging on, non-maximized applications that are placed inside the 1024 x 768 area will maximise to 1600 x 1200

This has been tested on two separate Hardy laptops, with different hardware and monitors.

The issue seems to be X treating the PanelSize from the video BIOS as an indication of the size of the external monitor, rather than the just the inbuilt one.

Eg, from Xorg.0.log

(II) RADEON(0): Panel ID string: 1024x768
(II) RADEON(0): Panel Size from BIOS: 1024x768
(II) RADEON(0): Added native panel mode: 1024x768
(II) RADEON(0): Added native panel mode: 1024x768

If using an xorg.conf, this can be overridden by modifying xorg.conf and specifying a Panel Size in the Device section:

Section "Device"
        Option "PanelSize" "1600x1200"
EndSection

However it would be better if Panel Size simply was not used for external screens.

[Bryce Harrington (bryce)]

I wonder if this could be another instance of the s-video requiring a monitor quirk.

Can you please attach the output of `xrandr` and `lspci -vvnn`?

[Mike MacCana (lovekudu)]

It happens with two separate machines
One ATI, with a Lenovo Monitor
One Intel, with a ViewSonic Monitor

So I don't think it's a hardware quirk, but that's up to you to judge.

When not using an xorg.conf (and exhibiting the problem above):

Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 1600 x 1200
VGA-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis)
400mm x 300mm
   1600x1200 60.0*+ 59.9
   1280x1024 76.0 75.0 69.8 59.9
   1152x864 75.0
   1024x768 84.9 75.1 70.1 60.0
   832x624 74.6
   800x600 72.2 75.0 60.3 56.2
   640x480 84.6 75.0 72.8 65.4 60.0
   720x400 70.1
DVI-0 disconnected (normal left inverted right x axis y axis)
LVDS connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x
0mm
   1024x768 60.0*+ 60.0
   800x600 60.3
   640x480 59.9
S-video disconnected (normal left inverted right x axis y axis)

When configures with specific Panelsize:

$ xrandr
Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 1600 x 1200
VGA-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis)
400mm x 300mm
   1600x1200 60.0*+ 59.9
   1600x1200@60 60.0
   1280x1024 75.0 69.8 59.9
   1152x864 75.0
   1024x768 84.9 75.1 70.1 60.0
   832x624 74.6
   800x600 72.2 75.0 60.3 56.2
   640x480 84.6 75.0 72.8 65.4 60.0
   720x400 70.1
DVI-0 disconnected (normal left inverted right x axis y axis)
LVDS connected 1600x1200+0+0 (normal left inverted right x axis y axis) 0mm
x 0mm
   1600x1200 27.3*+
   1280x800 60.0
   1280x768 60.0
   1024x768 60.0
   800x600 60.3
   640x480 59.9
S-video disconnected (normal left inverted right x axis y axis)

PCI device:

01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon
Mobility M7 LW [Radeon Mobility 7500] [1002:4c57] (prog-if 00 [VGA
controller])
    Subsystem: IBM Unknown device [1014:0530]
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping+ SERR+ FastB2B+
    Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
    Latency: 66 (2000ns min), Cache Line Size: 32 bytes
    Interrupt: pin A routed to IRQ 11
    Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
    Region 1: I/O ports at 3000 [size=256]
    Region 2: Memory at c0100000 (32-bit, non-prefetchable) [size=64K]
    [virtual] Expansion ROM at c0120000 [disabled] [size=128K]
    Capabilities: [58] AGP version 2.0
        Status: RQ=48 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit-
FW- AGP3- Rate=x1,x2,x4
        Command: RQ=32 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x4
    Capabilities: [50] Power Management version 2
        Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
        Status: D0 PME-Enable- DSel=0 DScale=0 PME-

On Tue, Mar 11, 2008 at 12:45 PM, Bryce Harrington <
<email address hidden>> wrote:

> I wonder if this could be another instance of the s-video requiring a
> monitor qui...

[Mike MacCana (lovekudu)]

Earlier I stated 'This has been tested on two separate Hardy laptops, with different hardware and monitors.'

That's incorrect - I've just re-tested on the second system (HP laptop with Viewsonic external monitor) and the problem doesn't occur - in fact the tool works splendidly, and I can finally get external monitor working and disable the distracting internal one - thanks Bryce!

The IBM laptop with the ATI video card and Lenovo monitor (whose lspci and xrandr output is above) still has the problem.

[John Gill (swfiua)]

I am experiencing the same problem with a Dell Latitude D410 and Hardy Heron.

This uses the intel driver:

(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
 965GM, 965GME/GLE, G33, Q35, Q33, Intel Integrated Graphics Device

I tried the panelsize option as described above, but no joy:

grep -i panel /var/log/Xorg.0.log:

   (WW) intel(0): Option "PanelSize" is not used

[John Gill (swfiua)]

Forgot to mention, the laptop/external monitor works fine with Gutsy.

[John Gill (swfiua)]

Update:

Adding a Display subsection to the Screen section of my xorg.conf, specifying a Virtual size
equal to the size of the external problem has solved the issue for me.

Section "Screen"
        Identifier "Default Screen"
        Monitor "Configured Monitor"
        Device "Configured Video Device"
        SubSection "Display"
            Virtual 1280 1024
        EndSubSection
EndSection

[Bryce Harrington (bryce)]

John, I think you must have an unrelated bug; please report it in a new bug report. Your issue actually sounds a bit like the tv-out issue which is common on intel gfx on dells. Try doing `xrandr --output TV --off`, and if that works, file a bug requesting the "tv-out quirk" with a description of the problem, and attach your Xorg.0.log.

[Brian Murray (brian-murray)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. In the development cycle for Intrepid there have been some vast improvements in the open source ati video driver and we could use your help testing them. Could you please download the latest Alpha CD image of Intrepid and test this particular bug just using the Live CD? You can find the latest image at http://www.ubuntu.com/testing . Your testing can help make Ubuntu and the open source ati driver even better! Thanks in advance.

[John Gill (swfiua)]

I'm afraid I'm in the process of moving to Canada.. so my separate display
is with the shippers until October at least -- unfortunately Intrepid will
be out by then I guess. I'll give it a test then and update the bug as
appropriate.

John

On Fri, Aug 15, 2008 at 2:41 AM, Brian Murray <email address hidden> wrote:

> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. In the development cycle for Intrepid there have been some vast
> improvements in the open source ati video driver and we could use your
> help testing them. Could you please download the latest Alpha CD image
> of Intrepid and test this particular bug just using the Live CD? You
> can find the latest image at http://www.ubuntu.com/testing . Your
> testing can help make Ubuntu and the open source ati driver even better!
> Thanks in advance.
>
> ** Changed in: xserver-xorg-video-ati (Ubuntu)
>
>

[Bryce Harrington (bryce)]

Mike, can you re-test against intrepid, and let us know if you can still reproduce it?

John, no problem - in fact if you could, please report it as a NEW bug since I suspect it is a different problem from Mike's.

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.