Ubuntu-fr

JB-home

AsusOled G1/G2/G50/G70/G71

ASUS G1/G2/G50/G70/G71 OLED Daemon

Les portables Asus et plus particulièrement les séries G1 et G2 possèdent un écran OLED de 128 × 32 pixels affichant par défaut « ASUS ».

This Java daemon displays system monitoring information on the small (256x32) OLED display found on ASUS G50/G70/G71 (USB ID: 0b05:175b).
It also works for ASUS G1/G2 (128x32 / USB ID: 0b05:1726)

Voici comment installer le daemon Oled ( j'ai testé sur mon Asus G2P, ça fonctionne impec )

tout d'abord il vous faut avoir java d'installé.

on commence par installer l'ancienne version d'asus_oled ( sans celle-ci la nouvelle version n'a pas l'air de vouloir fonctionner )
/!\ Cette étape est à renouveler à chaque nouveau noyaux. /!\

il faut être en root biensur.

cd /usr/src/
svn co svn://svn.berlios.de/lapsus/asus_oled/trunk asus_oled
cd asus_oled
make
make install

puis on installe le daemon : ( toujours en root )

cd /opt/
wget http://asusg50oled.sourceforge.net/download/asusg50oled.tgz
tar -xzf asusg50oled.tgz
cd asusg50oled
./start.sh
utils/install.sh

voilà redémarrer le pc et normalement votre Oled n'affichera plus "ASUS" mais des infos systèmes.
Pour modifier l'affichage ça se passe dans "/opt/asusg50oled/config.properties" où "/opt/asusg50oled/config.properties.G1" pour les Asus G1

par exemple , voici mon config.properties :

# What to display
# ---------------

# Choose the modules that you to see on the screen
# A special separator ('|') is used to indicate alternatives, meaning that if there is no information
# to display by the main module, display instead the alternative modules (separated by ';' in this case)

modules=leds.modules.Amarok|leds.modules.Kaffeine|leds.modules.CPUUsage;leds.modules.DateTime
        
# Other available modules not used by default
#	leds.modules.GPUTemperature		(suggestion: replace HDDTemperature with this; needs "nvclock")

# Arrange them as you like

Line1.Y=0
Line2.Y=10
Line3.Y=22


leds.modules.Load.x=0
leds.modules.Load.y=${Line1.Y}


leds.modules.CPUUsage.x=10
leds.modules.CPUUsage.y=${Line1.Y}


leds.modules.NetIO.x=182
leds.modules.NetIO.y=${Line1.Y}

# whether or not to ignore the loopback traffic
leds.modules.NetIO.substract_loopback=true

# what formatting should be applied to the numbers? see below for options:
# http://java.sun.com/j2se/1.4.2/docs/api/java/text/DecimalFormat.html
leds.modules.NetIO.format=###

# show both IN and OUT with the same size, even if the numbers have totally different orders of magnitude
leds.modules.NetIO.same_size=false

leds.modules.Battery.x=10
leds.modules.Battery.y=${Line2.Y}

leds.modules.Battery.width=12
leds.modules.Battery.height=19


leds.modules.DateTime.x=10
leds.modules.DateTime.y=${Line3.Y}

# If you want to display here another timezone then put here the offset in hours
leds.modules.DateTime.offset=0

# How should I display the time? See here for options:
# http://java.sun.com/j2se/1.4.2/docs/api/java/text/SimpleDateFormat.html
#
# leds.modules.DateTime.format=HH:mm dd.MM.yyyy
# leds.modules.DateTime.format=HH:mm
leds.modules.DateTime.format=HH:mm Edd MMM

# System uptime is by default replacing date and time for a few seconds
leds.modules.Uptime.x=0
leds.modules.Uptime.y=${Line3.Y}

# These parameters control for how long the module is active. The values are in seconds.
# Set them to 0 to have the module always active
leds.modules.Uptime.active_time=5
leds.modules.Uptime.sleep_time=30

leds.modules.Amarok.x=0
leds.modules.Amarok.y=0

leds.modules.Amarok.width=170
leds.modules.Amarok.height=21

leds.modules.Amarok.fontsize=10

leds.modules.Amarok.progressBar=true

# for the complete list of tags, see the code, or roughly `dcop amarok player | grep ^QString`
leds.modules.Amarok.line1=%currentTimePad% %title%
leds.modules.Amarok.line2=%totalTimePad% %artist%

# how many characters to advance when scrolling a long title/artist/... set this to 0 to disable scrolling
leds.modules.Amarok.scroll_advance=1

# how many refreshes to wait before (re)starting the scroll
leds.modules.Amarok.scroll_pause=3


leds.modules.Kaffeine.width=${leds.modules.Amarok.width}
leds.modules.Kaffeine.height=${leds.modules.Amarok.height}

leds.modules.Kaffeine.fontsize=${leds.modules.Amarok.fontsize}
leds.modules.Kaffeine.progressBar=${leds.modules.Amarok.progressBar}

leds.modules.Kaffeine.line1=%title%
leds.modules.Kaffeine.line2=%currentTime% / %totalTime% (-%remainingTime%)


leds.modules.CPUFreq.x=65
leds.modules.CPUFreq.y=${Line3.Y}


leds.modules.BatteryStatus.x=255
leds.modules.BatteryStatus.y=${Line3.Y}


leds.modules.CPUTemperature.x=230
leds.modules.CPUTemperature.y=${Line3.Y}


leds.modules.HDDTemperature.x=195
leds.modules.HDDTemperature.y=${Line3.Y}


# if you enable GPUTemperature instead of HDDTemperature, use the same position
leds.modules.GPUTemperature.x=195
leds.modules.GPUTemperature.y=${Line3.Y}


# Which is the device for which we ask for the temperature using smartctl ?
# You should install the smartmontools package for this, and run the application
# as root, otherwise it won't be able to get the temperature
leds.modules.HDDTemperature.device=/dev/sda
# How often to execute smartctl to get the temperature?
# By default we only call it at most at 30 seconds
leds.modules.HDDTemperature.check_interval=30000


# Sleep time, in milliseconds, between screen redraws
redraw_interval=3000


# How often to check for changes in this file, in milliseconds
# A negative or zero value disables the checking. This option
# allows you to dynamically change the parameters above without
# restarting the application. However, this is the only option
# that cannot be applied on the fly :) So, restart the application
# once after changing this option to a positive integer.
config.check_changes=0
# config.check_changes=${redraw_interval}


# By default both TCP and UDP server are listening on localhost:1196 for commands
# See the scripts in utils/ for usage examples
server.start=true
server.tcp.port=1196
server.tcp.address=127.0.0.1
server.udp.port=${server.tcp.port}
server.udp.address=${server.tcp.address}

# Invert pixels (write with black on blue) on new message received
invert_on_new_message=true

# What led to flicker when a new message is received
# An empty string means no flickering
flicker_on_new_message=/sys/class/leds/asus::touchpad/brightness

# How often to turn the led on and off (in milliseconds)
flicker_on_new_message.how_often=500

# How long to keep flickering after a message has been received
# Defaults to the expiration time of the messages
flicker_on_new_message.for_how_long=${notifications.expire}


# Display the latest 3 messages, even if the old ones haven't expired yet
notifications.purge_old=true

# How long to keep the notification on screen ?
# Expiration time is in milliseconds
notifications.expire=15000

# How many lines of notifications to display ?
# You can choose between 0 (no notifications displayed) to 3 (we only have so many lines)
notifications.lines=3

le site d'asusg50oled -> http://asusg50oled.sourceforge.net/

Dernière modification par z0rg> (Le 06/06/2010, à 23:49)

dondon

Re : AsusOled G1/G2/G50/G70/G71

salut z0rg>,

j'ai un G2PC comme toi avec la version  d'ubuntu 10.04 mais ce script ne fonctionne pas... en effet, le script "./start.h" ne m'affiche pas le message "republic of gamers"...

@ toute p-e...

JB-home

Re : AsusOled G1/G2/G50/G70/G71

il ne me l'affiche non plus pas , mais au redémarrage, j'ai bien un Oled personnalisé.

dondon

Re : AsusOled G1/G2/G50/G70/G71

ahh oki ... je vais voir ça....

dondon

Re : AsusOled G1/G2/G50/G70/G71

ben non... il ne veut toujours pas... les leds m'affichent toujours le asus de base.... je ne comprends pas alors que j'utilisais ce script avec le 9.04 et il fonctionnait très bien...

JB-home

Re : AsusOled G1/G2/G50/G70/G71

sur ubuntu 9.04, moi ça ne fonctionné pas .

tu a bien JAVA d'installé ?

sinon regarde les fichiers "README" et "INSTALL" en suivant pas à pas la procédure peut être que...

notamment cette étape ( que je n'ai pas eu besoin de faire d'ailleurs ):

rmmod usbhid
modprobe asus_oled
modprobe usbhid
dmesg | grep asus-oled