0

When I prees Fn+F2 my screen turn black what does it do? I want to know what change does it make. When at window7 I press Fn+F2 it will turn on wifi. After I restart nothing happen , did it will make eror?

sorry about my bad english

shukry
  • 1
  • 1
  • 1
  • 2
  • I guess you're on a laptop, aren't you ? The result of Fn+Fxx depends of your laptop and its bios, and the support or lack of support of its specifics on Linux... What laptop model are you using ? – alci Sep 06 '13 at 08:07
  • yes i'm using laptop asus brand,, but when i press again Fn+F2 after restart nothing happen ... – shukry Sep 06 '13 at 09:05
  • It is probably a software dependent keypress, only work in windows... we need the model name and number, "asus" is the maker so it is too generic to look up specific problems about certain laptops. – Mateo Sep 06 '13 at 17:19

1 Answers1

2

After pressing Fn+F2, try and see if Fn+F7 or Alt+F7 bring you back to the GUI. It sounds from your description that Fn may be behaving like Ctrl+Alt. If that's the case, then it's switching virtual consoles. The seventh virtual console is typically your GUI; lower-numbered ones behave as text terminals.

See:

However, if the screen turns completely black, then that's probably not what's going on. In that case, it probably dims or turns off the screen.

So another combination should brighten or turn on the screen. Assuming you've tried pressing Fn+F2 again to see if it toggles things back to the way they were before, you might try Fn+F1 or Fn+F3 to see if you can reverse the effect of Fn+F2.

If this was a one-time occurrence and the question is whether or not it represents a problem you have to worry about, the answer is probably not. In that case, I'm not sure of the cause, but it could be:

  • There was a bug, and an update fixed it (perhaps an update installed before the first time you pressed Fn+F2, but which did not take effect until the next boot-up).
  • Some other key was accidentally pressed at the same time.
  • Some program interpreted that key as input, and triggered a problem.

All of these explanations suggest a bug, but there are probably other explanations. If the problem happens again, then I recommend editing your question to provide more information (or posting a new one if the situation has changed considerably). In that case, the main question will be whether or not it's a bug and, if so, what package to report the bug as affecting.

Community
  • 1
Eliah Kagan
  • 117,780