Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[HOWTO] Sony Vaio FS series FN keys
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8, 9  Next  
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks
View previous topic :: View next topic  
Author Message
at240
l33t
l33t


Joined: 12 Aug 2005
Posts: 603
Location: UK

PostPosted: Sat Jul 08, 2006 1:42 pm    Post subject: Reply with quote

pijalu

OSD is suddenly not working, even though fsfn is (i.e. volume/brightness change, but without on-screen display).

I'm guessing that the upgrade to xorg7 has done this. (But other applications that used OSD (e.g. amarok, K3B) are still working with it successfully.)

Any idea how I can get it working again? Let me know what information you need.

Many thanks. :)
Back to top
View user's profile Send private message
pijalu
Guru
Guru


Joined: 04 Oct 2004
Posts: 365

PostPosted: Sat Jul 08, 2006 2:51 pm    Post subject: Reply with quote

Hmm.... sound strange since I am using Xorg7 (with and without Xgl) without any troubles....
K3B et amarok use another code for osd, but not xosd as far as I know

Are you sure the fsfn -o is started ?
If yes, do you have some syslog fsfn message ?

One thing to try is to re-emerge xosd then fsfn in case of a broken deps and try osd_cat
(see osd_cat --help or man osd_cat) to try it in stand-alone way
Back to top
View user's profile Send private message
at240
l33t
l33t


Joined: 12 Aug 2005
Posts: 603
Location: UK

PostPosted: Sat Jul 08, 2006 3:08 pm    Post subject: Reply with quote

Thanks for such a quick reply! Much appreciated.
pijalu wrote:

Are you sure the fsfn -o is started ?

Definitely.
pijalu wrote:

If yes, do you have some syslog fsfn message ?

Yes. Whenever I hit Fn+whatever...

Code:
Jul  8 16:06:09 localhost fsfn[7895]: Failed critical setup onscreen display: (null)

appears in the log.
pijalu wrote:

One thing to try is to re-emerge xosd then fsfn in case of a broken deps and try osd_cat
(see osd_cat --help or man osd_cat) to try it in stand-alone way

Re-emerged both. I can get output that way via osd_cat, but still nothing from fsfn.

Thanks again.
Back to top
View user's profile Send private message
pijalu
Guru
Guru


Joined: 04 Oct 2004
Posts: 365

PostPosted: Sat Jul 08, 2006 3:51 pm    Post subject: Reply with quote

Ok,
I just made a few change to osd code to get less critical part in xosd init and more details error output, you can get the latest tarball at http://users.skynet.be/muaddib/fsfn/fsfn-1.2-r1.tar.gz .... Give me the syslog output and cross your finger ;-)
Back to top
View user's profile Send private message
at240
l33t
l33t


Joined: 12 Aug 2005
Posts: 603
Location: UK

PostPosted: Sat Jul 08, 2006 6:01 pm    Post subject: Reply with quote

Still not appearing, I'm afraid. Error is slightly different: it cycles through these three on each Fn+whatever keypress. :?

Code:
Jul  8 18:55:49 localhost fsfn[12468]: Failed critical setup onscreen display: (null)
Jul  8 18:55:49 localhost fsfn[12499]: Failed critical setup onscreen display: (null)
Jul  8 18:55:49 localhost fsfn[12506]: Failed critical setup onscreen display: (null)


Weird. Any more ideas? I keep trying to figure out if I've done something stupid to cause this, but I really can't think of anything.

Thanks. :)
Back to top
View user's profile Send private message
pijalu
Guru
Guru


Joined: 04 Oct 2004
Posts: 365

PostPosted: Sat Jul 08, 2006 6:41 pm    Post subject: Reply with quote

Are you sure this is the "latest" version log ?

I changed the code to show the function name who gave error :?:
Code:

$ grep "Failed cr"  berlios-svn/fsfn/src/*.c
berlios-svn/fsfn/src/osd.c:   syslog (LOG_CRIT, "Failed critical setup onscreen display: %s : %s\n","xosd_set_bar_length", xosd_error);
berlios-svn/fsfn/src/osd.c:   syslog (LOG_CRIT, "Failed critical setup onscreen display: %s : %s\n","xosd_set_pos", xosd_error);
berlios-svn/fsfn/src/osd.c:          syslog (LOG_CRIT, "Failed critical setup onscreen display: %s : %s\n","xosd_set_align", xosd_error);
berlios-svn/fsfn/src/osd.c:          syslog (LOG_CRIT, "Failed critical setup onscreen display: %s : %s\n","xosd_set_vertical_offset", xosd_error);
berlios-svn/fsfn/src/osd.c:   syslog (LOG_CRIT, "Failed critical setup onscreen display: %s : %s\n","xosd_set_bar_length", xosd_error);
berlios-svn/fsfn/src/osd.c:   syslog (LOG_CRIT, "Failed critical setup onscreen display: %s : %s\n","xosd_set_pos", xosd_error);
berlios-svn/fsfn/src/osd.c:          syslog (LOG_CRIT, "Failed critical setup onscreen display: %s : %s\n","xosd_set_align", xosd_error);
berlios-svn/fsfn/src/osd.c:          syslog (LOG_CRIT, "Failed critical setup onscreen display: %s : %s\n","xosd_set_vertical_offset", xosd_error);


==>Message should be "Failed critical onscreen display: function : specific error code"
Back to top
View user's profile Send private message
at240
l33t
l33t


Joined: 12 Aug 2005
Posts: 603
Location: UK

PostPosted: Sat Jul 08, 2006 8:11 pm    Post subject: Reply with quote

pijalu

I'm an idiot. :P Sorry.

I tried the new version and it is working again. However, for your information, errors are still being reported in the log:

Code:
Jul  8 21:08:40 localhost fsfn[17440]: Failed non critical setup onscreen display: xosd_set_color : (null)
Jul  8 21:08:40 localhost fsfn[17440]: Failed some non-critical setup onscreen display
happens on each fn+whatever keypress.

Thanks so much for the help---appreciate it. :D
Back to top
View user's profile Send private message
pijalu
Guru
Guru


Joined: 04 Oct 2004
Posts: 365

PostPosted: Sun Jul 09, 2006 12:29 am    Post subject: Reply with quote

at240 wrote:
pijalu

I'm an idiot. :P Sorry.

I tried the new version and it is working again. However, for your information, errors are still being reported in the log:

Code:
Jul  8 21:08:40 localhost fsfn[17440]: Failed non critical setup onscreen display: xosd_set_color : (null)
Jul  8 21:08:40 localhost fsfn[17440]: Failed some non-critical setup onscreen display
happens on each fn+whatever keypress.

Thanks so much for the help---appreciate it. :D


No prob - so it looks like xosd has a hard time to set color... hmm... You can try to create (if not yet created) a file: /etc/fsfn.conf and put/add these lines:
Code:

OSD_VCOLOR=green
OSD_VCOLORZ=red
OSD_BCOLOR=LawnGreen

(if you already have a /etc/fsfn.conf or a .fsfn.conf , check if you have any settings associated to these keys - if yes, put them in comment (#) or try with the one i just gave...)
Back to top
View user's profile Send private message
at240
l33t
l33t


Joined: 12 Aug 2005
Posts: 603
Location: UK

PostPosted: Sun Jul 09, 2006 9:53 pm    Post subject: Reply with quote

OK, I tried that---still the same error:

Code:
Jul  9 22:46:39 localhost fsfn[16871]: Failed non critical setup onscreen display: xosd_set_color : (null)
Jul  9 22:46:39 localhost fsfn[16871]: Failed some non critical setup onscreen display

It's definitely loading those settings you gave me, because I can see them reported in the syslog earlier when fsfn is started.

Now you mention it, I've realised that since it's started working again, the colour of the OSD bars is white---before, it was red. So someting has changed.

I'm also suddenly seeing this in syslog now:
Code:
Jul  9 20:32:15 localhost ACPI Error (psargs-0353): [PKG0] Namespace lookup failure, AE_NOT_FOUND
Jul  9 20:32:15 localhost ACPI Error (psparse-0517): Method parse/execution failed [\_SB_.BAT0._BST] (Node dfec81e0), AE_NOT_FOUND

But I'm assuming this is nothing to do with the sonyacpi module and is something else entirely---am I right?

Thanks again for the help---despite those syslog messages, it seems to be functioning OK.
Back to top
View user's profile Send private message
pijalu
Guru
Guru


Joined: 04 Oct 2004
Posts: 365

PostPosted: Sun Jul 09, 2006 10:08 pm    Post subject: Reply with quote

Just wanted to be sure about the error... for some reason, your xosd seems to not be able to handle colors anymore... pretty strange... the only way to solve this will be to actually debug it and see why your install don't handle colors anymore on xosd... Until then, your OSD will have default colors - but at least it will continue to work

For your acpi error, this is not a big deal, just ACPI trying to map an entry not existing in your ACPI or a buggy sony acpi method call... but it's not a big deal... maybe just unexact battery levels...
Back to top
View user's profile Send private message
at240
l33t
l33t


Joined: 12 Aug 2005
Posts: 603
Location: UK

PostPosted: Sun Jul 09, 2006 10:16 pm    Post subject: Reply with quote

Well, I can live with that!

Once again, thanks for the great responses---much appreciated. :)
Back to top
View user's profile Send private message
LaintalAy
n00b
n00b


Joined: 30 Dec 2003
Posts: 10

PostPosted: Sat Sep 23, 2006 9:24 am    Post subject: Reply with quote

After upgrading the kernel to an 2.6.17 version, the node /dev/input/event0 disappeared but everything else was fine and none of the other event interfaces works with fsfn.

If anyone has this problem, it can be solved creating the node

Code:
 mknod /dev/input/event0 c 13 64



It was a desesperate bet to getting FN keys working after several hours searching a solution without results... and it works :)
Back to top
View user's profile Send private message
Phk
Guru
Guru


Joined: 02 Feb 2004
Posts: 428
Location: [undef], Lisbon, Portugal, Europe, Earth, SolarSystem, MilkyWay, 23Q Radius, Forward Time

PostPosted: Tue Oct 31, 2006 11:38 pm    Post subject: Reply with quote

Hi there everyone

First of all, congrats!! Great tool :)

I made exactly like it was written here, but manually setting brightness fails, and the "fnkey" file does not exist..

Also, when i "cat /dev/input/event0" the "FN" key does nothing, no bogus garbage.... :(
your module loads perfectly, no bad output messages..

I have a sony vaio fe31m. Is this the main problem...? :oops:


cheers :)
_________________
"# cat /dev/urandom >> /tmp/life"
Back to top
View user's profile Send private message
Frez
Apprentice
Apprentice


Joined: 29 Aug 2003
Posts: 166

PostPosted: Fri Dec 08, 2006 11:59 am    Post subject: Reply with quote

Phk wrote:

I made exactly like it was written here, but manually setting brightness fails, and the "fnkey" file does not exist..


Hi. sony_acpi seems to fail on my FE31M too (no fnkey, brigthness setting doesn't work).
I use smartdimmer to set brightness.

I'm still fighting against FN keys.
Almost no hope to see my face through the motion eye camera :(
_________________
There is one more thing ... it's been emotional
Back to top
View user's profile Send private message
pijalu
Guru
Guru


Joined: 04 Oct 2004
Posts: 365

PostPosted: Fri Dec 08, 2006 3:53 pm    Post subject: Reply with quote

Hi guys,

Did you give a shoot with sonypi ?
The main issue of Sony is they don't keep a "one way" to do things... and since I don't have the same model, I sadly cannot really help on this issue...

Anyway, when you do cat of /proc/acpi/fnkey, did you see the value change following the fnkeys pressed ?
Back to top
View user's profile Send private message
Phk
Guru
Guru


Joined: 02 Feb 2004
Posts: 428
Location: [undef], Lisbon, Portugal, Europe, Earth, SolarSystem, MilkyWay, 23Q Radius, Forward Time

PostPosted: Sun Dec 10, 2006 12:52 pm    Post subject: Reply with quote

Hi!

For now i've managed to work with brightness and volume using xsetkeys... but.... Not using the FN key.. I'm using the LeftControl key instead :oops: heh! At least it works! :P

pijalu wrote:
Anyway, when you do cat of /proc/acpi/fnkey, did you see the value change following the fnkeys pressed ?


I am almost sure that nothing happened, however, i'll try it again later today.

cheers!
_________________
"# cat /dev/urandom >> /tmp/life"
Back to top
View user's profile Send private message
Hadriel
Tux's lil' helper
Tux's lil' helper


Joined: 28 Jul 2005
Posts: 75

PostPosted: Fri Dec 15, 2006 1:07 pm    Post subject: Reply with quote

@frez
glad to see a fellow vaio FE owner (mine is the fe21h).
i have the same problem with the fn keys (and the webcam) as you. i tried spca5xx drivers, with no luck.i should write an email to the devs and send them some information on the device ;)
thx for posting that smartdimmer link, works like a charm. do you know if it really uses less energy? would be cool if this actually extends the battery time.
i am going to build that into my battery mode :)

found out that the cam will possibly be included in the next release of the gspca drivers. not sure tho.
Back to top
View user's profile Send private message
G2k
l33t
l33t


Joined: 06 Mar 2004
Posts: 672
Location: Rome, Italy

PostPosted: Mon Jan 22, 2007 6:08 pm    Post subject: Reply with quote

two questions:
is there an ebuild for the most recent fsfn version?
and
where do I put the startup command "fsfn -o" if I'm using GNOME?
Thanks :)
_________________
Animula vagula blandula,
Hospes comesque corporis,
Quae nunc abibis in loca
Pallidula rigida nudula,
Nec ut soles dabis iocos...
- Imp. Caesar Hadrianus
Back to top
View user's profile Send private message
pijalu
Guru
Guru


Joined: 04 Oct 2004
Posts: 365

PostPosted: Mon Jan 22, 2007 7:25 pm    Post subject: Reply with quote

G2k wrote:
two questions:
is there an ebuild for the most recent fsfn version?
and
where do I put the startup command "fsfn -o" if I'm using GNOME?
Thanks :)


1) http://users.skynet.be/muaddib/fsfn/fsfn-1.3.ebuild (no big changes btw)
2) System / Preferences / Sessions
Startup Programs Tab => add an entry with "fsfn -o"
Back to top
View user's profile Send private message
G2k
l33t
l33t


Joined: 06 Mar 2004
Posts: 672
Location: Rome, Italy

PostPosted: Mon Jan 22, 2007 7:44 pm    Post subject: Reply with quote

Code:
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/fsfn-1.3/work/fsfn-1.3 ...
 *
 * xosd support built in
 * To enable it, please add 'fsfn -o' to your x session
 *
 * econf: updating fsfn-1.3/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating fsfn-1.3/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --build=i686-pc-linux-gnu
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... configure: error: newly created file is older than distributed files!
Check your system clock

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/fsfn-1.3/work/fsfn-1.3/config.log

!!! ERROR: app-laptop/fsfn-1.3 failed.
Call stack:
  ebuild.sh, line 1546:   Called dyn_compile
  ebuild.sh, line 937:   Called src_compile
  fsfn-1.3.ebuild, line 36:   Called econf
  ebuild.sh, line 540:   Called die

!!! econf failed
!!! If you need support, post the topmost build error, and the call stack if relevant.

!!! This ebuild is from an overlay: '/usr/local/portage'
the 1.0 ebuild worked fine though...
_________________
Animula vagula blandula,
Hospes comesque corporis,
Quae nunc abibis in loca
Pallidula rigida nudula,
Nec ut soles dabis iocos...
- Imp. Caesar Hadrianus
Back to top
View user's profile Send private message
pijalu
Guru
Guru


Joined: 04 Oct 2004
Posts: 365

PostPosted: Mon Jan 22, 2007 8:36 pm    Post subject: Reply with quote

Since I just rebuild the tar for my previous post, could be some timing issue between my system and yours....
Retry in a few hours and tell me if it worked :-)
Back to top
View user's profile Send private message
alien275
n00b
n00b


Joined: 03 Mar 2007
Posts: 3

PostPosted: Sat Mar 03, 2007 10:07 am    Post subject: Reply with quote

Hello,

I have a Sony VAIO VGN-C2S and the FN key doesn't work. I use sony_acpi driver because sonypi doesn't work for me. I can change the brightness of my screen with this command :
echo 4 > /proc/acpi/sony/brightness

After I look into the source code of sony_acpi and in my dsdt file, I find why it doesn't work. In fact, I doesn't have the GHKE operation in my dsdt file and that's why the sony_acpi module doesn't create /proc/acpi/sony/fnfey. I try to look for an other function in my DSDT file (for FN key) but I can't find it.

Has anybody any idea how I can get the right operation or help me to find it ??

Thanks
Back to top
View user's profile Send private message
Adwin
Tux's lil' helper
Tux's lil' helper


Joined: 13 Mar 2005
Posts: 128
Location: Poland

PostPosted: Thu Mar 15, 2007 6:14 pm    Post subject: Reply with quote

I'm having the same trouble with a VGN-FS980

The module builds just fine on a 2.6.21-rc3 kernel
But /proc/acpi/sony is empty.

I tried the other solutions. None work ...
Back to top
View user's profile Send private message
|Quantum|
Tux's lil' helper
Tux's lil' helper


Joined: 24 Jan 2004
Posts: 133
Location: Belgium

PostPosted: Fri May 11, 2007 9:42 am    Post subject: Reply with quote

I have a very stupid question:

I'm using Gentoo on AMD64 on Sony VAIO FE41S.
The doc file is there, but I can't find the sonypid-driver ANYWHERE in the kernel config (not even in Drivers->Char->...).
Anyone with the same problem?
Back to top
View user's profile Send private message
pijalu
Guru
Guru


Joined: 04 Oct 2004
Posts: 365

PostPosted: Fri May 11, 2007 11:03 am    Post subject: Reply with quote

Adwin wrote:
I'm having the same trouble with a VGN-FS980

The module builds just fine on a 2.6.21-rc3 kernel
But /proc/acpi/sony is empty.

I tried the other solutions. None work ...


Just for info, kernel 2.6.21 now contains a new sony acpi that should contains fnkey.... did not try it yet but should work out of the box :-)

EDIT: The new module is sony_laptop but currently only the SVN version works on it (so it's not out-of-the-box yet).
I'll do the package when I found some times
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks All times are GMT
Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8, 9  Next
Page 7 of 9

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum