[ltp] T41, Radeon and external Monitor/Beamer

[Marius Gedminas]

--y0ulUmNC+osPPQO6
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 07, 2006 at 11:19:19AM +0100, Joerg Bruehe wrote:
> >You could try pressing Fn-F7, or doing
> >
> >  $ sudo -s
> >  # echo video_switch > /proc/acpi/ibm/video
> >
> >a few times to see if it helps.
>=20
> What do these commands do, or where do I find them documented?

Switches the video output between LCD, CRT and LCD+CRT.  Documentation
is here:

  http://ibm-acpi.sourceforge.net/README

> (Aside: I would like to see documentation for these "Fn-..." keys.)

You can find it somewhere on www.ibm.com.  Traditional meanings:

  Fn-F3 -- blank screen
  Fn-F4 -- suspend
  Fn-F5 -- toggle wireless/Bluetooth
  Fn-F7 -- toggle LCD / CRT / LCD+CRT
  Fn-F8 -- toggle screen expansion (when your chosen resolution is
           lower than the native LCD resolution)
  Fn-F12 -- hibernate

Some of these are handled by the software, and so might not work or work
differently (Fn-F7 and Fn-F8 only work if you specify Option
"BIOSHotkeys" "true" for the radeon driver.).

> Is it possible at all to run the internal screen at a reduced 1024x768=20
> resolution (be it by interpolation with loss of quality, or by reducing=
=20
> the virtual desktop), "wasting" the rest of 1400x1050 for that time?

It should be possible.

I noticed that you explicitly specify modelines.  Could that be why trying =
to
use 1024x768 causes a blank screen -- wrong modeline?

> I know that a MetaMode may only combine resolutions listed elsewhere -
> is that "elsewhere" the chain "Screen" -> "Display" -> "Modes",
> or is it "Screen" -> "Monitor" -> "UseModes" -> "Modeline",
> or some other definition I do not think of ?

'man radeon' says:

              Note:   Any mode you use in the MetaModes must be defined in =
the
              Screen section of your xorg.conf file.  Modes not defined  th=
ere
              will  be  ignored when the MetaModes are parsed since the dri=
ver
              uses them to make sure the monitors can handle those modes.

> Section "Monitor"
>   Option       "CalcAlgorithm" "CheckDesktopGeometry"
>   DisplaySize  340 270
>   HorizSync    30-90
>   Identifier   "Monitor[0]"
> # ModelName    "Thinkpad LCD Panel 1400x1050"
>   ModelName    "1400X1050@60HZ"
>   Option       "DPMS"
>   VendorName   "--> LCD"
>   VertRefresh  40-60
>   UseModes     "Modes[0]"
> EndSection
>=20
> Section "Monitor"
>   Option       "CalcAlgorithm" "CheckDesktopGeometry"
>   HorizSync    28-60
>   Identifier   "Monitor[1]"
> # ModelName    "Philips Brilliance 150 P"
>   ModelName    "1024X768@60HZ"
>   Option       "DPMS"
>   VendorName   "--> LCD"
>   VertRefresh  40-60
>   UseModes     "Modes[1]"
> EndSection
>=20
> Section "Modes"
>   Identifier   "Modes[0]"
>   Modeline      "800x600" 36.88 800 832 912 1024 600 601 604 621
>   Modeline      "1400x1050" 118.42 1400 1488 1640 1880 1050 1051 1054 1086
>   Modeline      "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087

I see no 1024x768 here.  Are standard modelines used in addition to those t=
hat
you specify explicitly, or do you need to list all modelines explicitly if =
you=20
use the "UseModes" directive?

> EndSection
>=20
> Section "Modes"
>   Identifier   "Modes[1]"
>   Modeline      "1024x768" 65.00 1024 1048 1184 1344 768 771 777 806
> # Modeline      "640x480" 23.06 640 656 720 800 480 481 484 497
> EndSection

Marius Gedminas
--=20
Mosher's Law of Software Engineering:
        Don't worry if it doesn't work right.
        If everything did, you'd be out of a job.

--y0ulUmNC+osPPQO6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)

iD4DBQFEDb2FkVdEXeem148RArpgAJ9S++ttOYZzXwTXj05GbenBZyge5QCWOWgt
jX1A1PUCH0SCVGUR6rJXFQ==
=PF17
-----END PGP SIGNATURE-----

--y0ulUmNC+osPPQO6--