fn+f8 (crt/lcd switch) does nothing

Thank you for reporting this bug in Ubuntu. It sounds sort of like bug 50243, however that has the issue with i810.

Can you please attach your /etc/X11/xorg.conf, /var/log/Xorg.0.log, and the output from lspci -vvnn?

I confirm that switching monitors does not work. In my case it's Fn-F5 and my notebook is a Toshiba U305-S5127 with Gutsy updated August 25 2007.
I will attach the same files you asked for John.

Hi, Bryce.

Any luck with this one?

I have the same issue on a new Dell Inspiron 6400 (UK). I tired the i810 driver with the 915resolution fix, and then fn F8 works to switch - but I get the same issues as bugs with that in that it dies after a few times and machines needs hard reset.

Using intel_driver works great with external monitor, but I cannot turn off laptop lcd panel at all - and if I close the lid, but monitors go off.

I have attached one report with card details, xorg.conf and Dell hotkeys-setup.

Nick

I believe the fn+f8 fix is in; can you retest and confirm? I don't know if fn+f5 is expected to also work or not.

Note you can also use 'xrandr --auto', if you're using hardware with xrandr 1.2 enabled drivers (-intel, -ati, and -nv for g80-class hw).

It works, with restrictions:

- fn+f8 when pressed the first time sends the signal to the external monitor, as expected;

- pressing it again it does nothing, but i was expecting it to switch:
 - external monitor only;
 - back to lcd only; (when pressed 3rd time)

fn+f8 works on my Dell Inspiron 6000, but only sending the signal to my TV (using SVideo). I can not get it back no matter how many times I press it. The fix for that is to unplug my s-video cord and hit fn+f8 then it comes back. Hopefully this is an easy fix for the devs!

Hi, I have a Dell 640m laptop with a 945GM graphics chip and a external LCD (LG l194wt), both using 1440x900 and have this problem. If any with 'intel' driver can make off the laptop lcd and use only de external monitor, please, put your xorg.conf.

This seems to be an acpi-support problem since it has no support for xrandr 1.2.
And I guess the title should be updated since it only effects Intel graphic hardware and not everyone has the monitor switch key on F8. Something like "switch video button has no effect on Intel hardware (no xrandr support)" would be more clear I think.

I found a solution using xrandr on http://yyhh.org/node/12 .

Simply using: xrandr --output LVDS --off

fn-f8 does not work on my Dell XPS M1210 laptop. I have an nVidia Geforce go 7400 gpu.

HDave - This bug is about Fn+F8 with an Intel video card and not an nVidia one. It would be best if you were to open a new bug report. Please attach your /etc/X11/xorg.conf, /var/log/Xorg.0.log, and the output from 'sudo lspci -vvnn' to your new bug report. Thanks for your cooperation.

Just confirming that this is still a problem in latest Hardy.

My hardware switch (fn+f4 here) has no effect. I've also not been able to reliably switch between the laptop and external screens without restarting X.

I believe Jonh Wendell's original problem is now fixed, with the new Screen Resolution tool in Hardy. Jonh, please test and feel free to re-open if it still occurs.

HDave and Peter, please file new bugs if you are also having problems with Hardy or Intrepid; these bugs are typically highly hardware-specific and occur for several unrelated reasons, so need to be handled individually.

I can still confirm this using latest intrepid beta.
I am using a dell xpsm1330 and nothing happens when pressing fn+f8 (crt/lcd switch).

mario@romario ~> lspci -v | grep Graphics
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)

It used to work with hardy.
Do you need any further information?

Mario, please file a new bug. There's been some various hotkey issues specific to intrepid, which aren't related to the original bug, so I'm guessing that's the case for you. File them against the 'hotkey-support' package please.

Closing out this bug since I suspect it's long since fixed, and there's been no comment from the original reporter for a while. Also, due to the number of changes to the input system in intrepid, if the key still fails, it would likely be for an unrelated reason and should be re-troubleshot.