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

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

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.

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?

Last edited by cstross (2008-01-31 11:20:39 am)

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.

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

Graves wrote:

@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.

@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...

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

okay folks, i got busy again and put together version 1.1 of the scriptpack.

there are no changes regarding to features of the scriptpack itself but i hope the changes will help a bit to get the scriptpack running for those who encountered problems when installing.

the changelog for v1.1 reads as follows:

*CHANGELOG*

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

the direct link to the new version is:

http://www.informatik.uni-oldenburg.de/ … 1.1.tar.gz

all versions of the scriptpack will from now on be available through

http://www.informatik.uni-oldenburg.de/ … buntu-osd/

and i will always edit the initial post in this topic to reflect the current version.

i am looking forward to feedback especially from those who had trouble installing before.

the install script creates 2 files... install.log and error.log you can include those files in your posts when reporting bugs so i might have a clue whats going wrong already.

i will further look into that issue... the biggest problem with this script-pack is that it is built around the original asusosd binary which is used in xandros and i do not have the sourcecode and for that reason no ability to alter it. so i have to wrap the funtionality around that application. this is a real bottleneck. maybe i will come up with my own self built osd daemon in one of the upcoming releases... that would solve a lot of problems

Hey Graves,

I have that wifi on/off script that you posted in the "eeeXubuntu Fn+F2 not working" thread.  I was wondering if I have to uninstall that script before installing this pack.  If so, how?