216 replies to this topic

[Graves]

THE MOST RECENT VERSION IS VERSION 2.1.
YOU CAN DOWNLOAD THAT VERSION AND ALL PREVIOUS VERSIONS FROM

http://code.google.c...e+DownloadCount

*CHANGELOG*

v2.1    - added configfile functionality
    - position of the osd can be altered
    - osd-imagetheme can be changed
    - improved wifi-on-off script
    - added command to fn+f6 hotkey
    - various minor bugfixes

v2.0    - scriptpack now uses a customized version
      of the asusosd application, so it does
      not have to be built around the asusosd
      application anymore but can make real
      use of it
    - a lot of the external scripts could be
      removed since their functionality was
      moved into the custom asusosd executable
    - the issue with slow or leaping display
      of volume level should be improved a lot
      with this release
    - the installer script was modified so it
      can be used to upgrade an older version
      without any precautions necessary (this
      behaviour will be kept for any future
      version)

v1.1     - removed unnecessary debug-output in 
      volume_control.sh 
    - create a lot more sophisticated install
      script which will make sure directories
      exist and files and directories get the
      needed permissions
    - added logging to the install script so
      that progress and errors are logged to
      logfiles for easier debugging

v1.0     - the initial version of the scriptpack

Okay, i had a day off from university today and put together a small scriptpack that will enable the asus osd that is used in xandros in our eeeXubuntu.

Because i already wrote a README file for the pack i am just copying the contents in here so you can read yourselves what it can do.

I have only tested this on my eeeXubuntu r3 install and it runs flawless with compiz and without this does not mean it will run on your install of eeeXubuntu as well. Thats why i need your feedback and info whether it works for you or not so i can further improve the scripts.

you can download the scriptpack from:

http://code.google.c...e+DownloadCount

to install simply save the file, then open a console and move to the directory where you stored the file and execute these commands

tar xvfz eeexubuntu-osd.tar.gz
cd eeexubuntu-osd
sudo ./install.sh

after the installation has finished you need to reboot to make everything work.


here comes the content of the readme file:

.------------------------------------------------.
|                                                |
|      eeeXubuntu ASUS OSD Scriptpack v1.0       |
|                   by Graves                    |
|                                                |
.------------------------------------------------.

*INFO*

This scriptpack will enable the standard asus osd 
(from preinstalled xadros) for acpi events under 
eeeXubuntu.

This scriptpack was written and tested with
eeeXubuntu r3.


*FEATURES*

- Support for switching wifi on and off with 
  On screen display (OSD) of wifi status
- Changing Brightness with OSD of current
  Brightness
- Changing Volume and muting sound with OSD 
  of sound status


*INSTALL*

To install simply go to the folder where you 
extracted the zipfile and invoke the install.sh
script as root:

sudo ./install.sh

After installation has finished you have to reboot
to make the scriptpack work.


*DISCLAIMER*

The author takes no responsibility for any damage
or harm these scripts might cause to your system.
Use this scriptpack at your own risk and make sure
to backup your files before installation.


*CHANGELOG*

v1.0 - the initial version of the scriptpack


*CONTACT*

For questions and feedback you can mail to
eee-osd@graves666.de

Edited by Graves, 28 February 2008 - 02:27 AM.

[StirfryNinja]

Sounds good. I'll test it when I get home :)

Edit: Just looking through the scripts now. The volume control script in usr/local/bin seems to have references to your own home directory in it?

Edited by StirfryNinja, 31 January 2008 - 05:28 AM.

[kevin_stevens]

The script to turn the wifi off/on seems to work properly, but after an off/on cycle the ath0 and wifi0 interfaces are not recreated. I'm not an expert, but I think you need to call the network reconfiguration script after turning it back on?

Everything else seems to work great. I had a minor issue because I didn't follow instructions exactly - I invoked root as sudo -i and ran the install script, so it tried to install to root's $HOME directory instead of my user. My fault, just noting it.

KeS

[StirfryNinja]

Everything works for me. I used my own wireless on-off script which i had installed previously though as I knew it worked. But the OSD and everything works. The volume OSD slider jumps around a bit though, sometimes going down when I'm increasing the volume then jumping back up. The actual volume seems to go up so it looks like a gui thing?

[Graves]

about the wifi-script working or not, this seems to be a strange issue. for me personally the script i have included in the package works quite well, even after 10 on/off cycles the wifi gets back on and after ~10-15 seconds connects me to my wlan again.

@StirfryNinja

regarding the sound. i used to have that behaviour as well when i still in/decreased volume in stepts of 10%. i then changed that to 5% in /etc/acpi/volupbtn.sh and voldownbtn.sh and with those settings it worked a lot smoother for me. when are those "leaps" happening? if you quickly change the volume to one direction or if you change it back and forth back and forth?

@kevin

yes i maybe should have pointed out that running the script while actually being logged in as root wont work. the autostart-file has to be moved in the users folder and i found no better way then using $HOME and invoking the script with sudo ./ but good that you figured that out yourself ;)

[khanjal]

Great work! Seems to be functioning like normal again. I had noticed that if you turn the volume up or down too fast it does jump but it stays accurate with the volume in the taskbar.

[Deckard]

Seems to be ok, thank you.
Just a small thing : I didn't have any dir named autostart in .config. So the first time I try, it failed.
I've created the dir manually and it's ok now.

[StirfryNinja]

Quote

regarding the sound. i used to have that behaviour as well when i still in/decreased volume in stepts of 10%. i then changed that to 5% in /etc/acpi/volupbtn.sh and voldownbtn.sh and with those settings it worked a lot smoother for me. when are those "leaps" happening? if you quickly change the volume to one direction or if you change it back and forth back and forth?

It happens in both the instances you described there. Changing the volume up or down too fast will cause it to jump about. Changing it back and forth will also cause that to happen

[cstross]

I had the same issue as Deckard (no ~/.config/autostart). So I created it and re-ran the script via sudo.

When I rebooted, nothing showed up on screen when I used the brightness/volume keys (although the brightness and volume were stepping up/down correctly). So I ran /usr/local/bin/asusosd from the command line and tried the volume up/down keys: it reported "image_open error."

Where are the image files supposed to live, and what permissions/ownership do they need?

Edited by cstross, 31 January 2008 - 04:20 PM.

[dvm]

Quote

So I ran /usr/local/bin/asusosd from the command line and tried the volume up/down keys: it reported "image_open error."

The script installs well but I also got the same error. No OSD shown and running this command shows the same error.
Thanks for the work!

BTW my 701 is running the patched kernel (2.6.24) from this forum.

[Graves]

the images reside in

/usr/local/share/asus-osd/

permission necessary is rw+r+r (chmod 644) although r+r+r (444) would be sufficient.


i will look into the issue with the installer and the not present autostart dir. i thought the dir was always there but it seems that it is only created after you install the first command as autorun via the settings entry.


to those guys who get the problem with the images. can you please have a look in the folder named above and tell me if the files are present and who is owner and what are the file permissions? if its a permission problem i will include forced setting of file permissions in the installer script, though i thought that would not be necessary as the files keep their permission when archived/extracted

@Deckard can you confirm that after creating the autostart dir in .config the autostart of the asusosd binary actually works? for the others who created it, it does not seem to work with manual dir creation so i thought maybe the system will not look for the autostart dir if you create it manually

@cstross & dvm what permissions did you give the autostart folder you created? it does at least need read/write/execute (chmod 700) for the owner of the directory.

@StirfryNinja its not possible that you make a video of that issue i suppose? the problem is somewhat not repeatable for me. what about the others? do you have similar issues with the volume up/down?


A GENERAL NOTE TO EVERYONE:

if you report bugs it would be great if you can give some informations about your system. if you run the stock kernel or upgraded kernel, did you install any kernel modules that were not part of the basic eeeXubuntu install and what else you altered from the basic eeeXubuntu install.

[Anthrix]

Hello linux i am using not for so long but then i try to install this script i had one problem. Folder autostar didn't exist i thin need to put one line :) before coping the file this line looks
mkdir -v $home/.config/autostart/

For me this think works.
Sorry for bad English

[dvm]

Hey, after installing there is no /usr/local/share/asus-osd/ ... :)

[Anthrix]

Strange :/

[Deckard]

Quote

@Deckard can you confirm that after creating the autostart dir in .config the autostart of the asusosd binary actually works? for the others who created it, it does not seem to work with manual dir creation so i thought maybe the system will not look for the autostart dir if you create it manually

Confirmed ;) It works just fine after reboot.

[marco.s]

Great script, thanks a lot :)

Works fine for me, also the wireless - but i can confirm the sluggish response to the volume keys, it takes a bit till the OSD comes up and sometimes it goes two steps forward and one back, making it kinda hard to change it how you want it to have.

The volume controls were kinda sluggish as well though on the original Xandros for me, responded rather slow on my eeepc...

[Graves]

@dwm can you have a look in folder where you unzipped the file and check if in the subfolder usr/local/share/ there is the asus-osd folder? maybe the unzipping did not work correctly?

i will now start and improve the installer script a bit. include the issue with directory creating and force setting of file permissions. maybe that will help with the problem s some seem to encounter here...

for those who encounter sluggish response from the volume buttons, i need a little further input. is that the case for all of you or can some report the volume up/down osd as responding well as it is the case on my computer?

what those who have sluggish response can try is do:

sudo mousepad /usr/local/bin/volume_control.sh

there is a line that reads

sleep 0.1

and try to alter that value. 0.0, 0.2, 0.3, 0.4 and 0.5 for example. then save the script and try hitting the volume buttons and see how that improves the responsiveness.

oh and before i forget, i just noticed that i left in 2 outputs there that should not be there anymore in release version, these are in the same file and read

echo status >> /home/graves/out.txt

you can remove those two lines and remove the folder /home/graves with all its content (should only be the file called out.txt...
i will fix that in the next release as well...

[Graves]

Quote

Hey, after installing there is no /usr/local/share/asus-osd/ ... :)

i had a slight typo earlier, the dir actually is

/usr/local/share/asus_osd/

[filo1234]

on eeexubuntu not running F7 F8 F9 for volume control why?? ihave installed the script

[reve_etrange]

@Graves: Much obliged, thank you.