Fail to switch bwteen CRT and LCD

Bug #163877 reported by alvin664
8
Affects Status Importance Assigned to Milestone
acpi-support (Ubuntu)
Invalid
Low
Unassigned

Bug Description

I have a Toshiba Laptop Satellite M20. After fresh install of Kubuntu Gutsy 7.10. Everything worked fine except I was not able to switch between my LCD and an external monitor (using Fn+F5).

I couldn't find similar bug. Any suggestion how I can fix this?

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

I guess this is acpi related.

Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

I have a similar problem, with a Satellite U305, intel 915 driver.
I can switch to external CRT with Fn-F5, but after that I cannot switched back (the CRT goes off but the LCD never come back on). No crash, no nothing, simply black screen.

Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

Could it be somehow related to:
http://bugs.freedesktop.org/show_bug.cgi?id=14481

(although probably not)

Revision history for this message
zexpe (rosscollins-uk) wrote :

This is certainly related to this bug:

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/145501

As it didn't occur in Feisty on my Toshiba Portege R200 (i810 driver) and apparently came in with Gutsy. I have these problems with Hardy (intel driver). If I press Fn-F5 enough times it works, but doesn't switch off the laptop screen any more. The toshset util switches correctly, but again doesn't switch off the laptop screen - just dims it.

I think it must be due to some kind of switch towards multiple screen support with "xrandr" instead of xinerama, which doesn't work well with toshutils

Revision history for this message
zexpe (rosscollins-uk) wrote :

I've written a script that upon successive executions gives me the behaviour that Fn-F5 used to provide. It can be triggered by a desktop global shortcut key to allow it to work like Fn-F5 used to work.

Apologies for my poor understanding of script language, but it works for me:

if toshset -q video | grep -q "internal: LCD"; then
  xrandr --output VGA --mode 1024x768
  toshset -video both
else
  if toshset -q video | grep -q "internal and external monitor"; then
    xrandr --output LVDS --off
    sudo toshset -video ext
  else
    if toshset -q video | grep -q "Video out: external monitor"; then
      xrandr --output LVDS --mode 1024x768
      sudo toshset -video int
      xrandr --output VGA --off
    else
      echo "Error: Unknown state"
    fi
  fi
fi

Revision history for this message
Michael Terry (mterry) wrote :

I'm attaching a pimped-out version of zexpe's script using xrandr, suitable to binding to a keyboard button.

It iterates the connected outputs, and toggles them in sequence, ending with all of them on.

Daniel T Chen (crimsun)
Changed in acpi-support:
importance: Undecided → Low
Revision history for this message
zexpe (rosscollins-uk) wrote :

Why is the importance of this bug set to low? This is a regression of something that worked perfectly in the Feisty distribution. It is also a piece of functionality that is vital to laptop users. Most laptop users own laptops to allow them to perform presentations by connecting their laptop to a projector at the meeting venue, or at least regularly connect them to external monitors when working. This simple lack of functionality is the kind of bug that gives Linux a bad name. Especially when it used to work.

Revision history for this message
Vu Ngoc San (san-vu-ngoc) wrote :

I agree with zexpe, this is crucial for professional laptop users.
We have bought a portege M750 for our seminar, but how can I advise on linux if you have to reboot everytime you connect a beamer ?

Revision history for this message
Steve Langasek (vorlon) wrote :

Hello,

Is this still an issue with the latest jaunty alpha? If so, please follow the instructions in https://wiki.ubuntu.com/Hotkeys/Troubleshooting and report your results here.

Changed in acpi-support:
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in acpi-support (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.