linux (2.6.31-19.57~ppa2~loms~karmic) karmic; urgency=low
...
* Fix FN keys release on Samsung N120, N130, N140, N310, N510, X120.
* Apply 'libata-ata_piix-clear-spurious-IRQ.patch' to fix the
SATA freezing problem on Samsung N130/N140.
Thanks a lot.
I edited the file you mentioned and rebooted.
I tried the Fn/F2 combination (battery level): the icon appeared on the screen, and a window I was unable to close (self-repeating).
I tried the Fn/Brightness up, the icon appeared on the screen for some time (nothing changed for brightness itself, of course)
Moreover, the whole keyboard became unresponsive,I could not even close the terminal where xev was opened and I was even unable to answer your message and no way to stop the netbook when clicking on the stop button in the menu .
I had to stop through the on/off button (not good at all for the HDD...).
This message come from my desktop machine..
So I guess N510 has the same Fn_key_release problem.
I hope I am able to restart my netbook and undo the editing...
Just suspend (Fn-Esc) then resume the machine to unlock the stuck keys (well, this works on other models).
You can easily undo the changes, just don't use any Fn key in the meanwhile.
Please test the new kernel as soon as it's available, and let me know if the keys start to work correctly.
Please consider a little donation to keep the 'Linux On My Samsung' project up and running. Thank you!
I had first to remove N510 from the /lib/udev/rules.d/95-keymap.rules.
That's what I did, checking no | or * was missing, closing the file with modification, restarting the machine, logging..
I checked that the non-working Fn keys where again non-working: OK
I checked that the working Fn keys still worked:OK again.
Then comes the nightmare : the keyboard assignation has been completely modified, although I do not even know how this could be ever done!
My keyboard is (well, was..) a french keyboard.
Instead of azertyuiop
it reads azerty456*
Instead of qsdfghjklmù
it reads qsdfgh123-"blank"
So, some 6 letters are gone and replaced by figures that remain available in the upper row of the keyboard.
I am then unable to enter any password in gaphical mode, an a sudo apt-get becomes s4d6 a*t-get.
Of course, same happens if I type anything in OpenOffice...
Checking directly with the file navigator in the 95-keymap.rules shows that N510 is no more in the SAMSUNG vendor list, which is correct.
I wuold like first to get my keyboard work as it used to.
Any idea of what happened, and how to go back to the ab-origine situation?Thanks.
You perfectly understood I was quite stupid at times...
Well the N510 is missing a LED telling NumLock is ON, as there is one for the CapsLock!
I installed 2.6.31-19.57 as requested.
I did not understand how and where to find the new udev you mentioned.Omitted then that step.
Failure to find the NVIDIA pilot during the process of building.
GRUB correct (on top now is 2.6.31-19 [generic]
Booting on 2.6.31-19: starts in low graphic mode (as expected following the abovementioned failure).
Installing again the nvidia GRAPHICS: no f&ailrue during install.
Editing the 95-keymap.rules file to include N510 in the SAMSUNG line (assuming this was the only modification you made for the "new" udev), t henclosing and booting again on 2.6.31.19.
Xserver is happy, back to the 1368 *768 screen.
What I had time to test only:
FN/F2: works in my opinion, the battery info. icon appears on the screen for approx. 5 seconds and then disappears.
If maintaining Fn down I type (exemple) 4 times on F2 , the battery icon will appear 4 times for 5 seconds each.The information displayed in this icon matches the one displayed when pointing the battery symbol in the menu.
Fn / Brightness up and down : displays the correct icon,From 0 to the maximum (those included) 7 brightness levels are available.
As you mentioned earlier, this makes no change to the real screen brightness.
Fn/F4 and Fn/F5: nothing happens
What else do you want me to test?
Thanks a lot for what you are doing.
Julian2010 wrote:You perfectly understood I was quite stupid at times...
Hehe, it happens to everybody from time to time
Julian2010 wrote:
I did not understand how and where to find the new udev you mentioned.Omitted then that step.
Just perform a system update after the repository addition, and 'udev' will be automatically updated to the latest version.
Julian2010 wrote:
What else do you want me to test?
Please test all the FN keys (by the way, are you using my scripts?). Also, please check with 'xev' command line utility if the non-working FN keys are actually recognized.
Please consider a little donation to keep the 'Linux On My Samsung' project up and running. Thank you!
Hello,
I installed the samsung-scripts on my N510 but did not yet tested them not knowing if anything special for the N510 had to be done before.Please let me know if needed.
I only checked via Compiz/Commands that 6 command lines had been created.
FN/Fx tests:
Fn/F2: battery status display: OK.Not a toggle action.Displays battery status for 5 seconds.
Fn/F3: no action in OpenOfficeWriter (should type the Euro symbol)
Fn/F4: no action, but I did not connect a VGA display, so test status is in fact "not tested".Can be done later on if this can help other users.
Fn/F5: Sceen ON/OF (or backlight if prefered): no action
Fn/F6: Sound ON/OFF: OK, as before
Fn/F7: Bluetooth ON/OFF: OK.Toggle action.The displayed status matches the one appearing in the menu bar (which is highlighted when ON and shaded when OFF).I never linked however any bluetooth device with my N510..The blue symbol on the F7 key is a Red Cross bag.
Fn/F8: processor speed ("runner"): no action.I control this through the ad-hoc applet in the menu.
Fn/F9: no action (should be WIFI ON/OFF).
Fn/F10: touchpad ON/OFF : OK as before
Fn/F11: NumLock ON/OFF: OK as before
Fn/F12: I do not know what this should do (I mean when and where..)
Fn/Sound UP and DOWN: OK as before
Fn/Brightness UP and down: displays brightness symbol and level, which can be modified Up or Down in the displayed icon, but no change for the real screen brightness itself.
Fn/End ("Fin" on my french keyboard): Don't know what this should do ( I mean where and when ,as for Fn/F12).
That's all for now.
I will have a look and try xev (never used before) later on.
Thank you again.
Fn/F3 (Euro symbol)
I do not copy everything, it's far too long and seems chaotic!
I repeated twice the procedure with an "a" press before and another "a" after the Fn/F3 itself to see exactly the beginning and the end of it...
So this is what happens when typing once Fn/F3:
a Keypress event serial 36 with state 0x0, keycode 64 & keysym 0xffe9, Alt_L
a keypress event serial 36 with state 0x8, keycode 90 & keysym 0xff9e, KP_Insert
a KeyRelease event with state 0x8 ,keycode 90 & keysym 0xff9e, KP_Insert
a KeyPress event with state 0x8, keycode 87 &keysym 0xff9c, KP_End
a KeyRelease event with state 0x8, keycode 87 &keysym 0xff9c, KP_End
a KeyPress event with state 0x8, keycode 88 &keysym 0xff99, KP_Down
a KeyRelease event with state 0x8, keycode 88&keysym 0xff99, KP_Down
a KeyPressEvent with state 0x8, keycode 80 &keysym 0xff97, KP_Up
a KeyreleaseEvent with state 0x8, keycode 80&keysym0xff97,KP_Up
a KeyReleaseEvent with state 0x8, keycode 64 &keysym 0xffe9, Alt_L
For each event:once
XLookupString gives 0 bytes
XmbLookupString gives 0 bytes (for the KeyPress events only)
XFilterEvent returns: False.
So, all the Fn keys are correctly mapped now.
The Fn-F3 behavior is also correct.
Now customize the samsung-scripts options as you need in '/etc/default/samsung-scripts' (just follow the instructions inside it), make sure the compiz 'commands' plugin is enabled, then restart your desktop session, and the scripts should then work.
For more info about the scripts and how they work, reference to this thread.
Please consider a little donation to keep the 'Linux On My Samsung' project up and running. Thank you!
I used the samsung-scripts on the N510.
Results are:
-for the webcam: I installed XawTV to get at least an application using the webcam (never used before!)
The shortcut works as expected: the bubble telling the state of the webcam appears, and is toggled with the shortcut.
Once the webcam has been stopped with the shortcut, XawTV cannot be launched anymore.
When the webcam has been activated with the shortcut and XawTV then launched, the webcam shorcut has no more action to stop the webcam.
All this sounds quite logical.
By the way, in my opinion, the webcam on N510 gives a low quality display.
-for the wireless: as already said, , Fn/F9 has no action.
In the samsung-scripts WIRELESS_MODULE="ath5k", while in my N510 it is not an Atheros WIFI module.So I did not even tried setting WIRELESS_TOGGLE_METHOD to 1.
Please remember I had the 8192 WIFI module set to work through ndiswrapper (I was not aware of your site at that time.....), so NOT with your wireless package.
So would the Fn/F9 work if the 8192 WIFI had been set to work through your wireless package?
Anyway I guess that the WIRELESS_MODULE value should then be altered in the samsung-scripts to match the real WIFI hardware of the machine.
I am not "running after" Fn/F9 working, it's just for my undersatnding of how things work (and do not as well).
-for the LAST-STATUS-RESTORE: left to 1.
I tried different combinations ON/OFF for the different devices.On rebooting the last set configuration was correct against the one set before halting the machine.
So, nice job you did there.
My regret is that nothing can be done for brightness and backlight real settings on the N510, even with the correct keymapping and key release management you implemented nicely, as these two things are the real ones I miss on my machine.
Julian2010 wrote:
-for the wireless: as already said, , Fn/F9 has no action.
In the samsung-scripts WIRELESS_MODULE="ath5k", while in my N510 it is not an Atheros WIFI module.So I did not even tried setting WIRELESS_TOGGLE_METHOD to 1.
Please remember I had the 8192 WIFI module set to work through ndiswrapper (I was not aware of your site at that time.....), so NOT with your wireless package.
So would the Fn/F9 work if the 8192 WIFI had been set to work through your wireless package?
Anyway I guess that the WIRELESS_MODULE value should then be altered in the samsung-scripts to match the real WIFI hardware of the machine.
Exactly. Set WIRELESS_TOGGLE_METHOD=1 and WIRELESS_MODULES="ndiswrapper", and everything should work well.
Julian2010 wrote:
My regret is that nothing can be done for brightness and backlight real settings on the N510, even with the correct keymapping and key release management you implemented nicely, as these two things are the real ones I miss on my machine.
As far as I know, the problem can be fixed somehow. I will investigate it.
Please consider a little donation to keep the 'Linux On My Samsung' project up and running. Thank you!
Sorry, it does not work.By the way, I used the graphical equivalent of ndiswrapper to set the 8192 module, but this should not change anything, as it uses ndiswrapper to do it...