Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
eee-control (EeePC management tool)
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4, 5, 6, 7  Next  
Reply to topic    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
SlashBeast
Moderator
Moderator


Joined: 23 May 2006
Posts: 2843

PostPosted: Tue Jan 13, 2009 11:19 am    Post subject: Reply with quote

gringo wrote:
Quote:
The volume doesn't work here either. But it's only about finding an application that is able to increase/decrease the volume on the comment line. So if anybody has an idea...


i guess you are talking about the "command line" here. If that´s the case have you looked to amixer ?


amixer work for me.
Code:
slashbeast@mizore ~ % grep Volume .fluxbox/keys
XF86AudioLowerVolume :ExecCommand amixer -q set Master 1- unmute
XF86AudioRaiseVolume :ExecCommand amixer -q set Master 1+ unmute
Back to top
View user's profile Send private message
lxg
Veteran
Veteran


Joined: 12 Nov 2005
Posts: 1019
Location: Aachen, Germany

PostPosted: Tue Jan 13, 2009 11:39 am    Post subject: Reply with quote

Yes, of course! Why didn't I think of amixer. :?

And, of course I meant command line, not "comment line" ...
_________________
lxg.de – codebits and tech talk
Back to top
View user's profile Send private message
lxg
Veteran
Veteran


Joined: 12 Nov 2005
Posts: 1019
Location: Aachen, Germany

PostPosted: Tue Jan 13, 2009 2:08 pm    Post subject: Reply with quote

A little update on the Bluetooth issue.

I have looked a bit deeper into the code of eee-control, and it does actually take advantage of rfkill. However, the rfkill interface itself appears not to work properly, at least not in 2.6.28-gentoo. I did some manual testing and got rather confused instead of enlightened. Maybe you guys like to join me in investigating this. (edit: Turns out to be a known bug, a patch exists and will hopefully be soon merged into the kernel. thx gringo)
_________________
lxg.de – codebits and tech talk


Last edited by lxg on Tue Jan 13, 2009 11:32 pm; edited 1 time in total
Back to top
View user's profile Send private message
lxg
Veteran
Veteran


Joined: 12 Nov 2005
Posts: 1019
Location: Aachen, Germany

PostPosted: Tue Jan 13, 2009 11:24 pm    Post subject: Reply with quote

Good news everybody ... I've hacked some code together and fixed the sound issue myself. With this, the keys to mute/unmute as well as increase/decrease the volume work fine. (For example, on the 901, F7 toggles mute/unmute, F8 and F9 increase/decrease the volume.)

For those already running on eee-control-0.8.3, you can download and directly apply the patch. As I decided to do it with Python itself instead of a command line tool, you also have to install a little extra Python module.

Code:

cd /usr/lib/python2.5/site-packages/
wget -O - http://www.zirona.com/misc/code/eee-control/eee-control-0.8.3-actions.py.patch | patch -p1
# isn't there a Python module for just everything?
emerge -av dev-python/pyalsaaudio


For those who are yet to upgrade to eee-control-0.8.3, I've updated the ebuild to include the patch.

Please test it on your respective EeePC models and let me know how if it works. I've tested it on my 901 only, but as far as I know, all EeePC models so far have the same audio hardware, so the controls should work on all models. (In the worst case, you will have no effect, so don't worry.)

Please note: If you want to re-install 0.8.3 to get the changes, you must first remove already downloaded packages and the Manifest (rm -rf /usr/portage/distfiles/eee-control* /usr/local/portage/sys-apps/eee-control/*), then run the install routine again. Elsewise, you will only install the package already existing on your machine.

P.S. In the earlier version of the patch I forgot to include the line import alsaaudio at the top of the file. If you installed the patch already, please add this line below the other import statements to actions.py. Sorry.
_________________
lxg.de – codebits and tech talk
Back to top
View user's profile Send private message
lxg
Veteran
Veteran


Joined: 12 Nov 2005
Posts: 1019
Location: Aachen, Germany

PostPosted: Thu Jan 15, 2009 10:05 am    Post subject: Reply with quote

I've updated the ebuild for 0.8.3 again. As i2c-tools has been fixed, we now use that package, instead of a binary of py-smbus.

You can, if you want, re-install eee-control 0.8.3, yet it won't make any difference in the user experience. (However, the revised 0.8.3 ebuild also applies the above-mentioned ALSA Fn-key patch.) Please have a look at the upgrade instructions to upgrade/reinstall to the new 0.8.3 ebuild.
_________________
lxg.de – codebits and tech talk
Back to top
View user's profile Send private message
himpierre
l33t
l33t


Joined: 31 Aug 2002
Posts: 863
Location: Berlin

PostPosted: Fri Jan 16, 2009 4:54 pm    Post subject: Reply with quote

Hello.

I get:

>>> Creating Manifest for /usr/local/portage/sys-apps/eee-control
digest.assumed 5
eee-control-0.8.2::eee-control-0.8.2-dbus-plugdev.patch
eee-control-0.8.2::eee-control-0.8.2-gentooinit
eee-control-0.8.2::eee-control-0.8.2.tar.gz
eee-control-0.8.2::smbus-1.1.egg-info
eee-control-0.8.2::smbus.so
>>> Compiling source in /var/tmp/portage/sys-apps/eee-control-0.8.3/work/eee-control-0.8.3 ...
/var/tmp/portage/sys-apps/eee-control-0.8.3/temp/environment: line 2059: distutils_src_compile: command not found
*
* ERROR: sys-apps/eee-control-0.8.3 failed.
Back to top
View user's profile Send private message
lxg
Veteran
Veteran


Joined: 12 Nov 2005
Posts: 1019
Location: Aachen, Germany

PostPosted: Fri Jan 16, 2009 5:11 pm    Post subject: Reply with quote

I wonder, why does part of your output say 0.8.2, and another part 0.8.3? Did you edit the ebuild yourself?

And the currently available 0.8.3 ebuild doesn't ship smbus.* anymore, it now uses sys-apps/i2c-tools.
_________________
lxg.de – codebits and tech talk
Back to top
View user's profile Send private message
himpierre
l33t
l33t


Joined: 31 Aug 2002
Posts: 863
Location: Berlin

PostPosted: Fri Jan 16, 2009 6:21 pm    Post subject: Reply with quote

I pasted the wrong content. Here is the build.log.

ee eee-control # cat /var/tmp/portage/sys-apps/eee-control-0.8.3/temp/build.log
>>> Unpacking source...
>>> Unpacking eee-control-0.8.3-gentooinit to /var/tmp/portage/sys-apps/eee-control-0.8.3/work
unpack eee-control-0.8.3-gentooinit: file format not recognized. Ignoring.
>>> Unpacking eee-control-0.8.3-dbus-plugdev.patch to /var/tmp/portage/sys-apps/eee-control-0.8.3/work
unpack eee-control-0.8.3-dbus-plugdev.patch: file format not recognized. Ignoring.
>>> Unpacking eee-control-0.8.3.tar.gz to /var/tmp/portage/sys-apps/eee-control-0.8.3/work
>>> Unpacking eee-control-0.8.3-actions.py.patch to /var/tmp/portage/sys-apps/eee-control-0.8.3/work
unpack eee-control-0.8.3-actions.py.patch: file format not recognized. Ignoring.
>>> Source unpacked in /var/tmp/portage/sys-apps/eee-control-0.8.3/work
>>> Compiling source in /var/tmp/portage/sys-apps/eee-control-0.8.3/work/eee-control-0.8.3 ...
/var/tmp/portage/sys-apps/eee-control-0.8.3/temp/environment: line 2059: distutils_src_compile: command not found
*
* ERROR: sys-apps/eee-control-0.8.3 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 2059: Called die
* The specific snippet of code:
* distutils_src_compile || die "Building the package failed!"
* The die message:
* Building the package failed!
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/sys-apps/eee-control-0.8.3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-apps/eee-control-0.8.3/temp/environment'.
* This ebuild is from an overlay named 'portage-local': '/usr/local/portage/'
*
eee eee-control #
Back to top
View user's profile Send private message
lxg
Veteran
Veteran


Joined: 12 Nov 2005
Posts: 1019
Location: Aachen, Germany

PostPosted: Fri Jan 16, 2009 6:50 pm    Post subject: Reply with quote

Oops, this is my mistake ... I changed a simple line to use Gentoo's native tools for building the Python package, but this seems not to have worked. I can't fix it right now (adding distutils to inherit doesn't do, there's another weird error). So I reverted back to the old behaviour, which is perfectly fine from the enduser's view.

To fix your problem, please download the ebuild again, then try again emerging:

Code:
#install the ebuild
EBUILD="eee-control-0.8.3.ebuild"
wget -O /usr/local/portage/sys-apps/eee-control/$EBUILD http://www.zirona.com/misc/code/eee-control/$EBUILD
ebuild /usr/local/portage/sys-apps/eee-control/$EBUILD manifest
emerge -av eee-control


Sorry for the hassle.
_________________
lxg.de – codebits and tech talk
Back to top
View user's profile Send private message
himpierre
l33t
l33t


Joined: 31 Aug 2002
Posts: 863
Location: Berlin

PostPosted: Fri Jan 16, 2009 7:09 pm    Post subject: Reply with quote

Yeah, added distutils to inherit myself. Next error. :-) Well, now it works again. Thanks.
Back to top
View user's profile Send private message
Coin Coin
n00b
n00b


Joined: 28 Oct 2008
Posts: 42

PostPosted: Mon Jan 19, 2009 8:36 am    Post subject: Reply with quote

Kernel 2.6.27-r5
EeePC 1000h
eee-control 0.8.3

I've got this message:
Adding hotkey mappings to /usr/share/hotkey-setup/asus.hk
/usr/bin/eee-control-setup.sh: line 85: /usr/share/hotkey-setup/asus.hk: Aucun fichier ou répertoire de ce type (It means: File or Folder not found)
Look like I have to install hotkey-setup, but where can I find it?
Back to top
View user's profile Send private message
lxg
Veteran
Veteran


Joined: 12 Nov 2005
Posts: 1019
Location: Aachen, Germany

PostPosted: Mon Jan 19, 2009 8:43 am    Post subject: Reply with quote

You don't have to execute /usr/bin/eee-control-setup.sh at all. It's for manual installations, and Ubuntu only anyway.

(Note to self: Have this file deleted when building the package.)

You don't need /usr/share/hotkey-setup/asus.hk anymore. It contains obsolete acpid hotkey definitions for brightness and volume. The brightness is handled internally by eee-control in recent versions, the volume is handled by the patch I wrote.
_________________
lxg.de – codebits and tech talk
Back to top
View user's profile Send private message
ns4683
n00b
n00b


Joined: 25 Jan 2009
Posts: 13

PostPosted: Sun Jan 25, 2009 2:11 am    Post subject: Reply with quote

I am getting this error message:

Code:
eee nick # eee-control-tray
sh: synclient: command not found
libnotify-Message: Unable to get session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Traceback (most recent call last):
  File "/usr/bin/eee-control-tray", line 21, in <module>
      EeeControl.tray.EeeControlTray()
        File "usr/lib/python2.5/site-packages/EeeControl/tray.py", line 67, in __init__
     File "usr/lib/python2.5/site-packages/EeeControl/tray.py", line 286, in register_notifications
     AttributeError: 'pynotify.Notification' object has no attribute 'attach_to_status_icon'


I'm using Xfce and I have an EeePC 900A. Any idea what's causing this? Is it the synclient? Is that for a Synaptics touchpad?
Back to top
View user's profile Send private message
gringo
Advocate
Advocate


Joined: 27 Apr 2003
Posts: 3793

PostPosted: Mon Jan 26, 2009 10:10 am    Post subject: Reply with quote

Quote:
sh: synclient: command not found


synclient is part of synaptics package afaik.

Quote:
libnotify-Message: Unable to get session bus: Did not receive a reply


not sure, hald/dbus not running maybe ?


I tried eee-control over the weekend in my 901 with latest kernel pulled from git (2.6.29-rc2-git1 or sth like that) and eee-control is broken there as expected.
RFKILL interfaces look like they are switched ( rfkill for wlan kills bluetooth, rfkill for bluetooth kills wlan); fsb control is missing; hotkeys apparently work quite well.
I wasn´t able to find a working interface to control the fan either ( hwmon interface does nothing apparently...).

There are a few patches pending upstream, let´s see if they get this fixed.

Thanks for your work :)

cheers
_________________
Error: Failing not supported by current locale
Back to top
View user's profile Send private message
lxg
Veteran
Veteran


Joined: 12 Nov 2005
Posts: 1019
Location: Aachen, Germany

PostPosted: Mon Jan 26, 2009 12:08 pm    Post subject: Reply with quote

ns4683:
According to equery, synclient is a part of x11-drivers/xf86-input-synaptics. However, the fact that you see the error message is (as far as I see) only a minor bug, as the call to synclient is only used to determine if a device exists, and the author simply didn't redirect STDERR to /dev/null. If I see correctly, there is a fallback routine if synclient and the synaptics driver aren't available. So you can IMO simply ignore that line.

As for that other message: In case you have hald and dbus running, is it possible that you forget to add yourself to the plugdev and messagebus group? Can you please post the output of groups <your eee-control-tray user>?
_________________
lxg.de – codebits and tech talk


Last edited by lxg on Mon Jan 26, 2009 1:06 pm; edited 2 times in total
Back to top
View user's profile Send private message
lxg
Veteran
Veteran


Joined: 12 Nov 2005
Posts: 1019
Location: Aachen, Germany

PostPosted: Mon Jan 26, 2009 12:25 pm    Post subject: Reply with quote

gringo wrote:
I tried eee-control over the weekend in my 901 with latest kernel pulled from git (2.6.29-rc2-git1 or sth like that) and eee-control is broken there as expected.
RFKILL interfaces look like they are switched ( rfkill for wlan kills bluetooth, rfkill for bluetooth kills wlan);


Geez, and I thought they finally fixed RFKILL. :( But that shouldn't be hard to fix.


gringo wrote:
fsb control is missing;


FSB setting should work. Please try the following:
- Stop the eee-control init service
- Start eee-control-daemon -V as root in a terminal (will foreground the process and show actions)
- Then left-click on the eee-control tray icon and change the settings in Performance.
- You should see in the terminal that the bus speed is (apparently) changed

Ok, I don't know if it actually changes the speed when it prints the message. Do you possibly know a way for testing this?

gringo wrote:
I wasn´t able to find a working interface to control the fan either ( hwmon interface does nothing apparently...).


I think you must install gnome-power-manager for that. I don't have installed it, so I don't know about that one.

gringo wrote:
There are a few patches pending upstream, let´s see if they get this fixed.


AFAIK, Greg is already working on 0.8.4, but he seems to have few time lately. There is a preliminary version of 0.8.4, but I really can't say if it fixes anything, not to talk about damaging things. So I'd recommend not to touch it. (If you're really curious, have a look in the src directory. ;))

Anyway ... congrats on your 901. I really enjoy mine, it's a wonderful piece of technology.
_________________
lxg.de – codebits and tech talk
Back to top
View user's profile Send private message
gringo
Advocate
Advocate


Joined: 27 Apr 2003
Posts: 3793

PostPosted: Mon Jan 26, 2009 2:23 pm    Post subject: Reply with quote

Quote:
Geez, and I thought they finally fixed RFKILL. :( But that shouldn't be hard to fix.


They have actually moved the drivers to drivers/platform/x86/ now, and therefore the patches have to be reworked.
But yeah, no biggie of course. My intention was just to let everyone know what i found so far, no bitching intended btw ;)

Quote:
- Stop the eee-control init service
- Start eee-control-daemon -V as root in a terminal (will foreground the process and show actions)
- Then left-click on the eee-control tray icon and change the settings in Performance.
- You should see in the terminal that the bus speed is (apparently) changed


will have a look and let you know, but the "fsb settings menu" on the applet was not even selectable, which made me think that the interface in /proc was completely missing. Will triplecheck.
Not that im worried about this, i use the ondemand governor that switches cpufreq according to the load. I know i don´t have the 1800 Mhz option this way but i can live with that for now.

Quote:
Ok, I don't know if it actually changes the speed when it prints the message. Do you possibly know a way for testing this?


you could just check /proc/cpuinfo or some interface in /sys, both should tell you the current clock speed. I know the ondemand governor works because i see the clock speed changing if i put some load on the system.

Quote:
I think you must install gnome-power-manager for that. I don't have installed it, so I don't know about that one.


i don´t think so, i have gnome installed ( well, a stripped down gnome-light but with gnome-power-manager added) and i don´t see how this gnome applet could do this without proper kernel support.
Hwmon support is enabled by default if you select eee-laptop module in the kernel iirc ( like rfkill in current git) and you will get a /sys/class/hwmon interface, but it doesn´l look like it is working. Or i wasn´t able to do anything with it at least ... i think i´m missing some kernel option here.

These are just some rough edges that will be fixed in short i guess. As said, some more patches are pending for upstream and hopefully they will ship with 2.6.29.

Quote:
AFAIK, Greg is already working on 0.8.4, but he seems to have few time lately. There is a preliminary version of 0.8.4, but I really can't say if it fixes anything, not to talk about damaging things. So I'd recommend not to touch it. (If you're really curious, have a look in the src directory. ;))


maybe i will have a look to it but i would just wait till the interfaces settle, it´s a pain to maintain if the kernel guys are changing /sys or /dev interfaces every kernel release.

Quote:
Anyway ... congrats on your 901. I really enjoy mine, it's a wonderful piece of technology.


thanks :) - yeah , i love this hardware too, it does exactly what i was looking for !

cheers
_________________
Error: Failing not supported by current locale
Back to top
View user's profile Send private message
gringo
Advocate
Advocate


Joined: 27 Apr 2003
Posts: 3793

PostPosted: Mon Jan 26, 2009 7:26 pm    Post subject: Reply with quote

apologies for the noise, i just realized my kernel conf was wrong and some i2c stuff was missing. I was trying several kernel confgurations and apparently used a crappy one in the end ... which may also mean the other pending patches are already apllied upstream.

After rebuilding the kernel i can confirm that the switches to disable/enable bluetooth,wlan and camera do work. I dont know about the cardreader, when you switch it on/off i see no changes in the logs and i dont use this stuff myself. Fan rpm / sys temps are now also displayed as well. Fsb control is displayed nowtoo but doesnt work, could be because of the ondemand governor, haven tried yet without it.

Thanks for the tip of manually starting the daemon, it helped a lot :)

cheers
_________________
Error: Failing not supported by current locale
Back to top
View user's profile Send private message
lxg
Veteran
Veteran


Joined: 12 Nov 2005
Posts: 1019
Location: Aachen, Germany

PostPosted: Mon Jan 26, 2009 7:56 pm    Post subject: Reply with quote

I also don't use the card reader (yet). But switching it on/off appears to work: There are these files in /sys/devices/platform/eeepc/, and you can echo 0/1 to them to toggle their status. This definitely works for wlan and camera, so I assume that cardr also works. This is the way eee-control handles these devices (it does however prefer RFKILL for WLAN and Bluetooth, if available).

Good to know that toggling Bluetooth finally works in 2.6.29. :)
_________________
lxg.de – codebits and tech talk
Back to top
View user's profile Send private message
ns4683
n00b
n00b


Joined: 25 Jan 2009
Posts: 13

PostPosted: Wed Jan 28, 2009 12:45 pm    Post subject: Reply with quote

lxg wrote:
ns4683:
According to equery, synclient is a part of x11-drivers/xf86-input-synaptics. However, the fact that you see the error message is (as far as I see) only a minor bug, as the call to synclient is only used to determine if a device exists, and the author simply didn't redirect STDERR to /dev/null. If I see correctly, there is a fallback routine if synclient and the synaptics driver aren't available. So you can IMO simply ignore that line.

As for that other message: In case you have hald and dbus running, is it possible that you forget to add yourself to the plugdev and messagebus group? Can you please post the output of groups <your eee-control-tray user>?


I'm using the root user for now until I get things set up, so my "groups root" output is: root bin daemon sys adm disk wheel floppy dialout tape video messagebus plugdev". I installed the synaptics X driver, so the synclient error went away but the rest of the error from traceback remains.
Back to top
View user's profile Send private message
ns4683
n00b
n00b


Joined: 25 Jan 2009
Posts: 13

PostPosted: Wed Feb 11, 2009 7:34 pm    Post subject: Reply with quote

Can anyone help out with this? I keep getting the error.
Back to top
View user's profile Send private message
lxg
Veteran
Veteran


Joined: 12 Nov 2005
Posts: 1019
Location: Aachen, Germany

PostPosted: Fri Feb 13, 2009 6:40 pm    Post subject: Reply with quote

Really hard to put a finger on it ... Maybe your Python modules are not upgraded (run python-upgrader?), or you have an old version of some of the Python modules. What does emerge -pve eee-control output?
_________________
lxg.de – codebits and tech talk
Back to top
View user's profile Send private message
ns4683
n00b
n00b


Joined: 25 Jan 2009
Posts: 13

PostPosted: Sat Feb 14, 2009 9:32 pm    Post subject: Reply with quote

Well, I got it to work by upgrading to the latest notify-python ebuild in portage. I had 0.1.1 installed originally and after upgrading to 0.1.1-r1 the application works.
Back to top
View user's profile Send private message
keulemaster
n00b
n00b


Joined: 10 Mar 2009
Posts: 1

PostPosted: Tue Mar 10, 2009 4:57 pm    Post subject: Reply with quote

i have problems to start the eee-control-tray

Code:


eee1000h ~ # /etc/init.d/eee-control start
 * Starting eee-control daemon ...
Cannot access I2C control files, performance control will be unavailable.                                [ ok ]
eee1000h ~ # eee-control-tray

(eee-control-tray:4225): Gtk-WARNING **: Locale not supported by C library.
   Using the fallback 'C' locale.
Can't access shared memory area. SHMConfig disabled?
libnotify-Message: Unable to get session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Traceback (most recent call last):
  File "/usr/bin/eee-control-tray", line 21, in <module>
    EeeControl.tray.EeeControlTray()
  File "usr/lib/python2.5/site-packages/EeeControl/tray.py", line 67, in __init__
  File "usr/lib/python2.5/site-packages/EeeControl/tray.py", line 286, in register_notifications
AttributeError: 'pynotify.Notification' object has no attribute 'attach_to_status_icon'


eee1000h ~ # uname -r
2.6.27-gentoo-r8
eee1000h ~ #
eee1000h ~ # eee-control-setup.sh
Kernel module eeepc_acpi/eeepc_laptop found. Good.
Cleaning up /etc/modules
Adding modules to /etc/modules
Adding options to /etc/modprobe.d/eee-control
Adding hotkey mappings to /usr/share/hotkey-setup/asus.hk
/usr/bin/eee-control-setup.sh: line 85: /usr/share/hotkey-setup/asus.hk: No such file or directory
Moving conflicting ACPI scripts to /etc/acpi/events-old/
Restarting acpid
 * Stopping eee-control daemon ...                                                                       [ ok ]
 * Stopping acpid ...                                                                                    [ ok ]
 * Starting acpid ...                                                                                    [ ok ]
 * Starting eee-control daemon ...
Cannot access I2C control files, performance control will be unavailable.                                [ ok ]
Reloading hotkey-setup
/usr/bin/eee-control-setup.sh: line 102: /etc/init.d/hotkey-setup: No such file or directory
Loading modules...





whats wrong i have no idea
pleas help

thanks
Back to top
View user's profile Send private message
lxg
Veteran
Veteran


Joined: 12 Nov 2005
Posts: 1019
Location: Aachen, Germany

PostPosted: Fri Mar 13, 2009 10:10 am    Post subject: Reply with quote

Hm, that's hard to tell. Looks a bit like your kernel is not set up correctly, or you the dbus config is incorrect.

Besides, there was no mention in the tutorial that you should use the eee-control-setup.sh script. Don't use it, it doesn't do any useful on Gentoo.

Please retry the installation, following the tutorial to the letter, which includes compiling your kernel with the config provided in the tutorial.
_________________
lxg.de – codebits and tech talk
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Unsupported Software All times are GMT
Goto page Previous  1, 2, 3, 4, 5, 6, 7  Next
Page 2 of 7

 
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