Code: Select all
sudo samsung-scripts wifi
Code: Select all
sudo samsung-scripts wifi
Code: Select all
sudo apt-get install nvidia-common=0.2.15.1 && sudo apt-get purge nvidia-190-modaliases nvidia-195-modaliases
Then check if the command is correctly binded to the FN key.Julian2010 wrote:It does work through the terminal command, so it's related to a wrong keybinding.
Code: Select all
sudo apt-get install compizconfig-settings-manager
compizconfig was already on my machine.voRia wrote:Then check if the command is correctly binded to the FN key.Julian2010 wrote:It does work through the terminal command, so it's related to a wrong keybinding.
- Install 'compizconfig-settings-manager':- Start it from 'System'->'Preferences'->'CompizConfig Settings Manager'.Code: Select all
sudo apt-get install compizconfig-settings-manager
- Click on the 'Commands' plugin (the first one in the list).
- Check the command in the 'Command line 2' text field, it has to be 'sudo samsung-scripts wifi' (with no quotes).
- Go to the 'Key Bindings' tab.
- Check the assigned key for 'Run command 2', it has to be 'XF86WLAN'. If it's not, click on the currently assigned key, then on 'Grab key combination' and press Fn-F9.
Just a note (for the record):
from here you can bind the unused Fn keys (like Fn-F3) in order to launch custom commands. Just use the empty commands fields.
Why do you have brightness up and down?Julian2010 wrote: It will be command line 6 (0 is brightness-up, 1 is Brightness-down 2 is for WIFI now, 3 for bluetooth, 4 for webcam and 5 for wmswithcher.sh:for VGA display).
What about the Fn-up and down? Do they work too now? From your words I assume it is, and if so, I'll add this nvidia driver to the official repository.Julian2010 wrote: I uploaded from your archive repository the 190.53 NVIDIA driver, rebooted, and then tested the Fn/F5 action: good news, it works!
...
So as a whole, backlight control is a success on the N510, with the minor ( in my view) defect of the number of Fn/F5 needed strikes.
I can't figure out why it behaves this way. The script for managing the backlight on/off use the 'vbetool' command line utility which, as far as I know, should work good in any case.Julian2010 wrote: However, strangely, in the same session the Fn/F5 does not always shut down the backlight at the first strike, and at times a second Fn/F5 strike is needed
When backlight is OFF, two strikes may also be needed to get the backlight ON again.
Code: Select all
sudo samsung-scripts lcd
Well, I was thinking about rewriting the howto for using the repository in a better way, by adding specific instructions for netbooks that need some further step. But I'm really out of time lately, so it's not a thing I can do for now.Julian2010 wrote: May I suggest that all this could be summarized in a separate tutorial , specific to the N510?
So, thank you again.
My fault, I misunderstood your report.Julian2010 wrote:It seems there is a misunderstanding about brightness control , specially as regards the last line of my previous answer, which I thought was self-explanatory about the remaining issue: I only stated in that post that now the Fn/F5 works (with some trouble sometimes),which was not the case before, but that the brightness control problem remains unsolved.
In fact in that last answer I said nothing about the Fn/Up & DOWN, which means they still do not have any effect on the real brightness of the screen, although the brightness bubble is correctly displayed and the level it shows is increased/decreased by the Fn/UP or DOWN action.
Yes, I think you should try the beta driver.Julian2010 wrote:As already told, as the Fn/F5 works with the 190.53 driver, I did not even try the beta 195 NVIDIA driver you mentioned as I thought is was then useless.
Do you think I should have a go with this beta driver for the Fn /UP & DOWN...and what are my risks?
I would not like to break everything and restart from scratch if the Xserver is not pleased with that driver....
Code: Select all
sudo apt-get install nvidia-glx-190
Please redo the same test by using these commands instead:Julian2010 wrote:About the backlight command using the terminal, it seems it does not always work well.
...
When it does not work properly , I have to type Fn/F5 to have backlight ON again..and read what has happened in the terminal.
In that case, hand has not been given back to terminal, so the second typed command has not been executed, as the line does not begin by xxxx@MyNetbook:~$
It can be the other way around: backlight is on, I type the command in terminal, backlight stays ON, and I can see that the second command line (for backlight OFF) is just at the beginning of the next line, meaning that also in this cas hand has not been given back to the terminal.
Code: Select all
sudo vbetool dpms off
Code: Select all
sudo vbetool dpms on