View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 42 posts ] 
Go to page Previous  1, 2, 3  Next

Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Sun Mar 18, 2012 10:22 pm 
Offline
Joined: Tue Mar 22, 2005 9:18 pm
Posts: 1394
Location: Brisbane, Queensland, Australia
Thanks goofee, where do I put this file and then to I have to tell the system to load it?

_________________
Girkers


Top
 Profile  
 
PostPosted: Mon Mar 19, 2012 12:02 am 
Offline
Joined: Sat Feb 03, 2007 12:52 am
Posts: 187
Location: Manitoba, Canada
To test it I would
Code:
rmmod hid_twinhan
rmmod usbhid
insmod usbkbd.ko

if it works copy it to /lib/modules/2.6.39-LinHES/kernel/drivers/hid/usbhid/usbkbd.ko
then run depmod to update the module list. you may have to blacklist the hid_twinhan module from loading again,


Top
 Profile  
 
PostPosted: Mon Mar 19, 2012 7:08 am 
Offline
Joined: Tue Mar 22, 2005 9:18 pm
Posts: 1394
Location: Brisbane, Queensland, Australia
Sorry goofee no goood. I tried your commands and nothing happened. I then tried to "install" the file as suggested and this had no affect.

I unpluedg and replugged my reciever in and this is the code I get in dmesg:
Code:
[  284.895016] usbcore: deregistering interface driver usbhid
[  296.704037] usb 3-1: USB disconnect, device number 2
[  299.366014] usb 3-1: new low speed USB device number 3 using uhci_hcd
[  299.613057] usbcore: registered new interface driver usbhid
[  299.613059] usbhid: USB HID core driver
[  299.647099] input: Twinhan Tech Remote Control as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/input/input6
[  299.647229] twinhan 0003:6253:0100.0003: input,hidraw0: USB HID v1.10 Keyboard [Twinhan Tech Remote Control] on usb-0000:00:1d.1-1/input0
[  299.660429] input: Twinhan Tech Remote Control as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.1/input/input7
[  299.660548] twinhan 0003:6253:0100.0004: input,hidraw1: USB HID v1.10 Mouse [Twinhan Tech Remote Control] on usb-0000:00:1d.1-1/input1


Thanks goofee I appreciate your efforts.

At this stage I would be willing to look at alternative receivers (as I perceive this as the problem) however where would I find one that is support by 7.2 of LinHES and what do they cost?

_________________
Girkers


Top
 Profile  
 
PostPosted: Thu Mar 22, 2012 2:26 am 
Offline
Joined: Tue Mar 22, 2005 9:18 pm
Posts: 1394
Location: Brisbane, Queensland, Australia
I can now prove the the ir receiver is actually being recognised by the system as when I run evtest (installed via pacman) I get this:
Code:
[root@myth-office ~]# evtest /dev/input/by-id/usb-Twinhan_Tech_Remote_Control_11                                                                                                                                                             11111-event-if00
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x6253 product 0x100 version 0x110
Input device name: "Twinhan Tech Remote Control"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 15 (Tab)
    Event code 113 (Mute)
    Event code 114 (VolumeDown)
    Event code 115 (VolumeUp)
    Event code 119 (Pause)
    Event code 128 (Stop)
    Event code 159 (Forward)
    Event code 167 (Record)
    Event code 168 (Rewind)
    Event code 207 (Play)
    Event code 210 (Print)
    Event code 223 (Cancel)
    Event code 356 (Power2)
    Event code 362 (Program)
    Event code 364 (Favorites)
    Event code 365 (EPG)
    Event code 375 (Screen)
    Event code 388 (Text)
    Event code 395 (List)
    Event code 402 (ChannelUp)
    Event code 403 (ChannelDown)
    Event code 408 (Restart)
    Event code 512 (Numeric 0)
    Event code 513 (Numeric 1)
    Event code 514 (Numeric 2)
    Event code 515 (Numeric 3)
    Event code 516 (Numeric 4)
    Event code 517 (Numeric 5)
    Event code 518 (Numeric 6)
    Event code 519 (Numeric 7)
    Event code 520 (Numeric 8)
    Event code 521 (Numeric 9)
  Event type 4 (Misc)
    Event code 4 (ScanCode)
  Event type 17 (LED)
    Event code 0 (NumLock)
    Event code 1 (CapsLock)
    Event code 2 (ScrollLock)
    Event code 3 (Compose)
    Event code 4 (Kana)
Testing ... (interrupt to exit)

Okay, I push the up, down, left and right buttons and:
Code:
Event: time 1332404023.592152, type 4 (Misc), code 4 (ScanCode), value 7004b
Event: time 1332404023.592159, type 1 (Key), code 402 (ChannelUp), value 1
Event: time 1332404023.592161, -------------- Report Sync ------------
Event: time 1332404023.608144, type 4 (Misc), code 4 (ScanCode), value 7004b
Event: time 1332404023.608149, type 1 (Key), code 402 (ChannelUp), value 0
Event: time 1332404023.608150, -------------- Report Sync ------------
Event: time 1332404025.679972, type 4 (Misc), code 4 (ScanCode), value 7004e
Event: time 1332404025.679979, type 1 (Key), code 403 (ChannelDown), value 1
Event: time 1332404025.679980, -------------- Report Sync ------------
Event: time 1332404025.687971, type 4 (Misc), code 4 (ScanCode), value 7004e
Event: time 1332404025.687976, type 1 (Key), code 403 (ChannelDown), value 0
Event: time 1332404025.687977, -------------- Report Sync ------------
Event: time 1332404030.487573, type 4 (Misc), code 4 (ScanCode), value 70051
Event: time 1332404030.487582, type 1 (Key), code 114 (VolumeDown), value 1
Event: time 1332404030.487584, -------------- Report Sync ------------
Event: time 1332404030.495576, type 4 (Misc), code 4 (ScanCode), value 70051
Event: time 1332404030.495582, type 1 (Key), code 114 (VolumeDown), value 0
Event: time 1332404030.495584, -------------- Report Sync ------------
Event: time 1332404031.575491, type 4 (Misc), code 4 (ScanCode), value 70052
Event: time 1332404031.575499, type 1 (Key), code 115 (VolumeUp), value 1
Event: time 1332404031.575501, -------------- Report Sync ------------
Event: time 1332404031.583485, type 4 (Misc), code 4 (ScanCode), value 70052
Event: time 1332404031.583491, type 1 (Key), code 115 (VolumeUp), value 0
Event: time 1332404031.583493, -------------- Report Sync ------------


Looking at christ's documentation http://linhes.org/projects/linhes/wiki/Architecture_and_Customization doesn't help in trouble shooting as my problem is falling through the cracks.

As the command lsusb finds the device something is not being created, as mode2 report no /dev/lirc and ir-keytable says Couldn't find any node at /sys/class/rc/rc*. So something is not happening somewhere.

Any help?

_________________
Girkers


Top
 Profile  
 
PostPosted: Thu Mar 22, 2012 8:17 am 
Offline
Joined: Mon Dec 24, 2007 9:47 am
Posts: 535
Location: Ottawa, Canada
Girkers wrote:
Looking at christ's documentation http://linhes.org/projects/linhes/wiki/Architecture_and_Customization doesn't help in trouble shooting as my problem is falling through the cracks.

As the command lsusb finds the device something is not being created, as mode2 report no /dev/lirc and ir-keytable says Couldn't find any node at /sys/class/rc/rc*. So something is not happening somewhere.

Any help?

If you have nothing in /sys/class/rc then I expect this is not viewed as a "remote class" and hence it is viewed as a standard keyboard. I believe you also mentioned this earlier. My guide really just addresses devices that come up as remotes. However my guide does give you the message path for a standard keyboard.

If you are getting scan codes through input then a driver does exist. Based on a comment brfransen made a while back, it looks like there may be something you need to do in Xorg to ensure the device is properly discovered.

Also though you followed goofee's suggestions, your message log output looks like usbhid and the twinham device were not removed from the modules list. After executing goofee's suggestion you can verify the modules with "lsmod".

If I get a bit of time to research this I will help more but I'm a bit pressed these days and just want to help at least a bit to get you going. It sounds like goofee may be in a better position to help you.


Top
 Profile  
 
PostPosted: Fri Mar 23, 2012 1:45 pm 
Offline
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1304
Location: Orlando FL
I an say that my streamzap remote worked with 7.1 and they are on ebay for $35. I'm not trying to be a smart alec but I never upgrade my working system. I always use another hard drive to upgrade so that if it all goes to crap I just change the boot order in BIOS and I still have a working MythTV.

_________________
My System


Top
 Profile  
 
PostPosted: Fri Mar 23, 2012 10:00 pm 
Offline
Joined: Sat Feb 03, 2007 12:52 am
Posts: 187
Location: Manitoba, Canada
Sorry for the delay. I see a couple things happening here.

Seems the usbkbd didn't work, my dmesg shows
Code:
 usbcore: registered new interface driver usbkbd
 usbkbd: :USB HID Boot Protocol keyboard driver
I didn't unplug it, just rmmod both modules and insmod the new one.

I played a little with evtest using the hid_twinhan module. I see that the only keycode that should and does work is the tab key (code15). The rest are all mapped quite a bit higher. I played with xmodmap to remap the keys to work as expected. Some of them worked. The problem is if you attach a keyboard, it remapps the keys on the keyboard too. Also the numeric keys start at keycode 500 and xmodmap complains that it's out of range. My logitech keyboard only goes to 255.
Code:
evtest  /dev/input/by-id/usb-Logitech_USB_Receiver-event-kbd
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x46d product 0xc517 version 0x110
Input device name: "Logitech USB Receiver"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 1 (Esc)
    Event code 2 (1)
    Event code 3 (2)
    Event code 4 (3)
    Event code 5 (4)
    Event code 6 (5)
    Event code 7 (6)
    Event code 8 (7)
    Event code 9 (8)
    Event code 10 (9)
    Event code 11 (0)
    Event code 12 (Minus)
    Event code 13 (Equal)
    Event code 14 (Backspace)
    Event code 15 (Tab)
    Event code 16 (Q)
    Event code 17 (W)
    Event code 18 (E)
    Event code 19 (R)
    Event code 20 (T)
    Event code 21 (Y)
    Event code 22 (U)
    Event code 23 (I)
    Event code 24 (O)
    Event code 25 (P)
    Event code 26 (LeftBrace)
    Event code 27 (RightBrace)
    Event code 28 (Enter)
    Event code 29 (LeftControl)
    Event code 30 (A)
    Event code 31 (S)
    Event code 32 (D)
    Event code 33 (F)
    Event code 34 (G)
    Event code 35 (H)
    Event code 36 (J)
    Event code 37 (K)
    Event code 38 (L)
    Event code 39 (Semicolon)
    Event code 40 (Apostrophe)
    Event code 41 (Grave)
    Event code 42 (LeftShift)
    Event code 43 (BackSlash)
    Event code 44 (Z)
    Event code 45 (X)
    Event code 46 (C)
    Event code 47 (V)
    Event code 48 (B)
    Event code 49 (N)
    Event code 50 (M)
    Event code 51 (Comma)
    Event code 52 (Dot)
    Event code 53 (Slash)
    Event code 54 (RightShift)
    Event code 55 (KPAsterisk)
    Event code 56 (LeftAlt)
    Event code 57 (Space)
    Event code 58 (CapsLock)
    Event code 59 (F1)
    Event code 60 (F2)
    Event code 61 (F3)
    Event code 62 (F4)
    Event code 63 (F5)
    Event code 64 (F6)
    Event code 65 (F7)
    Event code 66 (F8)
    Event code 67 (F9)
    Event code 68 (F10)
    Event code 69 (NumLock)
    Event code 70 (ScrollLock)
    Event code 71 (KP7)
    Event code 72 (KP8)
    Event code 73 (KP9)
    Event code 74 (KPMinus)
    Event code 75 (KP4)
    Event code 76 (KP5)
    Event code 77 (KP6)
    Event code 78 (KPPlus)
    Event code 79 (KP1)
    Event code 80 (KP2)
    Event code 81 (KP3)
    Event code 82 (KP0)
    Event code 83 (KPDot)
    Event code 85 (Zenkaku/Hankaku)
    Event code 86 (102nd)
    Event code 87 (F11)
    Event code 88 (F12)
    Event code 89 (RO)
    Event code 90 (Katakana)
    Event code 91 (HIRAGANA)
    Event code 92 (Henkan)
    Event code 93 (Katakana/Hiragana)
    Event code 94 (Muhenkan)
    Event code 95 (KPJpComma)
    Event code 96 (KPEnter)
    Event code 97 (RightCtrl)
    Event code 98 (KPSlash)
    Event code 99 (SysRq)
    Event code 100 (RightAlt)
    Event code 102 (Home)
    Event code 103 (Up)
    Event code 104 (PageUp)
    Event code 105 (Left)
    Event code 106 (Right)
    Event code 107 (End)
    Event code 108 (Down)
    Event code 109 (PageDown)
    Event code 110 (Insert)
    Event code 111 (Delete)
    Event code 113 (Mute)
    Event code 114 (VolumeDown)
    Event code 115 (VolumeUp)
    Event code 116 (Power)
    Event code 117 (KPEqual)
    Event code 119 (Pause)
    Event code 121 (KPComma)
    Event code 122 (Hanguel)
    Event code 123 (Hanja)
    Event code 124 (Yen)
    Event code 125 (LeftMeta)
    Event code 126 (RightMeta)
    Event code 127 (Compose)
    Event code 128 (Stop)
    Event code 129 (Again)
    Event code 130 (Props)
    Event code 131 (Undo)
    Event code 132 (Front)
    Event code 133 (Copy)
    Event code 134 (Open)
    Event code 135 (Paste)
    Event code 136 (Find)
    Event code 137 (Cut)
    Event code 138 (Help)
    Event code 183 (F13)
    Event code 184 (F14)
    Event code 185 (F15)
    Event code 186 (F16)
    Event code 187 (F17)
    Event code 188 (F18)
    Event code 189 (F19)
    Event code 190 (F20)
    Event code 191 (F21)
    Event code 192 (F22)
    Event code 193 (F23)
    Event code 194 (F24)
    Event code 240 (Unknown)
  Event type 4 (Misc)
    Event code 4 (ScanCode)
  Event type 17 (LED)
    Event code 0 (NumLock)
    Event code 1 (CapsLock)
    Event code 2 (ScrollLock)
    Event code 3 (Compose)
    Event code 4 (Kana)
  Event type 20 (Repeat)
Testing ... (interrupt to exit)


I found this to be an interesting read, didn't get it to work for me though.

I found inputlirc to be very interesting. inputlirc is a simplified LIRC daemon which works just for input devices.
Code:
inputlircd /dev/input/by-id/usb-Twinhan_Tech_Remote_Control_1111111-event-if00
irw
201 0 KEY_NUMERIC_1 /dev/input/by-id/usb-Twinhan_Tech_Remote_Control_1111111-event-if00
201 0 KEY_NUMERIC_1 /dev/input/by-id/usb-Twinhan_Tech_Remote_Control_1111111-event-if00
202 0 KEY_NUMERIC_2 /dev/input/by-id/usb-Twinhan_Tech_Remote_Control_1111111-event-if00
205 0 KEY_NUMERIC_5 /dev/input/by-id/usb-Twinhan_Tech_Remote_Control_1111111-event-if00
205 0 KEY_NUMERIC_5 /dev/input/by-id/usb-Twinhan_Tech_Remote_Control_1111111-event-if00
205 0 KEY_NUMERIC_5 /dev/input/by-id/usb-Twinhan_Tech_Remote_Control_1111111-event-if00
192 0 KEY_CHANNELUP /dev/input/by-id/usb-Twinhan_Tech_Remote_Control_1111111-event-if00
192 0 KEY_CHANNELUP /dev/input/by-id/usb-Twinhan_Tech_Remote_Control_1111111-event-if00
72 0 KEY_VOLUMEDOWN /dev/input/by-id/usb-Twinhan_Tech_Remote_Control_1111111-event-if00
All that's left is to write an lircrc file. Seems pretty simple. There is a PKGBUILD in arch aur but it doesn't look like it's setup for LinHES runit scripts. Not very responsive, but I think that's why I haven't used this remote in a while. I'm using a homebrew serial receiver from irblaster.info. It works great as long as you have a serial port. I then use a remote from an old dvd player.


Top
 Profile  
 
PostPosted: Fri Apr 06, 2012 11:46 pm 
Offline
Joined: Tue Mar 22, 2005 9:18 pm
Posts: 1394
Location: Brisbane, Queensland, Australia
goofee wrote:
To test it I would
Code:
rmmod hid_twinhan
rmmod usbhid
insmod usbkbd.ko

if it works copy it to /lib/modules/2.6.39-LinHES/kernel/drivers/hid/usbhid/usbkbd.ko
then run depmod to update the module list. you may have to blacklist the hid_twinhan module from loading again,


Obviously the first time I tested this I was not holding my tongue right, because as soon as I did it this time, it worked as expected. Then I had the arduous task of working out how to make this work full time.

Looking in the arch documentation was useless as I tried creating a file called /etc/modprobe.d/blacklist.conf with my modules blacklisted but they still loaded. I added the items to the blacklist in the file /etc/rc.conf, still no joy. I then thought of a different tack on how to implement this.

I first started researching how to add the commands to the startup, but then I read that even though you could do that, another module or command later could load the module even though you don't want it. So I thought about putting in the startup of X. I created a small script /home/myth/fix_twinhan.sh, it looked like this:
Code:
#!/bin/bash

#Remove modules for hid and then load the usbkbd.ko module
sudo rmmod hid_twinhan
sudo rmmod usbhid
insmode /lib/modules/2.6.39-LinHES/kernel/drivers/hid/usbhid/usbkbd.ko


I then edited /home/mythtv/.fluxbox/apps and added the line:
Code:
[startup] {/home/mythtv/fix_twinhan.sh}

before the LinHES run command.

After rebooting found that the remote still did not work, I check the module listing and found that hid_twinhan was gone from the list, but usbhid was still there and no usbkbd.ko.

I then moved the startup command to AFTER the LinHES run command and rebooted again and now it works perfectly.

I would like to thank christ and especially goofee for taking the time to help me out and get this working, whilst the WAF was OK as I taught her the keyboard shortcuts, the WAF should now rise back to the glory of yester-year (it seems that long ago since the remote worked :P )

_________________
Girkers


Top
 Profile  
 
PostPosted: Sat Apr 07, 2012 10:23 am 
Offline
Joined: Mon Dec 24, 2007 9:47 am
Posts: 535
Location: Ottawa, Canada
Girkers wrote:
Looking in the arch documentation was useless as I tried creating a file called /etc/modprobe.d/blacklist.conf with my modules blacklisted but they still loaded.

That is strange. If you added a file called say "/etc/modprobe.d/twinham_blacklist.conf" and added:
Code:
blacklist hid_twinhan
blacklist usbhid

And then I think you might still need to add the "install" for adding usbkbd.

If blacklist didn't work then I think the following would work (though I have never done this) assuming your drivers are in conflict with an insert:
Code:
install hid_twinhan /bin/true
install usbhid /bin/true

Insert has a higher priority.

Or possibly something like:
Code:
install hid_twinhan /sbin/modprobe usbkbd ; /sbin/modprobe --ignore-install hid_twinhan
install usbhid /sbin/modprobe usbkbd ; /sbin/modprobe --ignore-install usbhid


Top
 Profile  
 
PostPosted: Sat Apr 07, 2012 6:18 pm 
Offline
Joined: Tue Mar 22, 2005 9:18 pm
Posts: 1394
Location: Brisbane, Queensland, Australia
christ wrote:
Girkers wrote:
Looking in the arch documentation was useless as I tried creating a file called /etc/modprobe.d/blacklist.conf with my modules blacklisted but they still loaded.

That is strange. If you added a file called say "/etc/modprobe.d/twinham_blacklist.conf" and added:
Code:
blacklist hid_twinhan
blacklist usbhid

And then I think you might still need to add the "install" for adding usbkbd.

If blacklist didn't work then I think the following would work (though I have never done this) assuming your drivers are in conflict with an insert:
Code:
install hid_twinhan /bin/true
install usbhid /bin/true

Insert has a higher priority.

Or possibly something like:
Code:
install hid_twinhan /sbin/modprobe usbkbd ; /sbin/modprobe --ignore-install hid_twinhan
install usbhid /sbin/modprobe usbkbd ; /sbin/modprobe --ignore-install usbhid


My file 'etc/modprobe.d/blacklist.conf' looked like:
Code:
blacklist hid_twinhan
blacklist usbhid

Didn't work, modules are still loaded.

I changed my file to look like this:
Code:
install hid_twinhan /bin/false
install usbhid /bin/false

Didn't work, modules are still loaded.

I changed my file to look like this:
Code:
install hid_twinhan /bin/true
install usbhid /bin/true

Didn't work, modules are still loaded.

I changed my file to look like this:
Code:
install hid_twinhan /sbin/modprobe usbkbd ; /sbin/modprobe --ignore-install hid_twinhan
install usbhid /sbin/modprobe usbkbd ; /sbin/modprobe --ignore-install usbhid

Didn't work, modules are still loaded.

_________________
Girkers


Top
 Profile  
 
PostPosted: Tue May 08, 2012 4:39 am 
Offline
Joined: Mon Jun 21, 2004 5:28 am
Posts: 700
Location: Germany
I had the same blacklist problem. I had to do a:
Code:
sudo update-initramfs -u
after updating the blacklist files to get it to work.

Additional note: removing usbhid broke my USB mouse. I got the remote to work by just blacklisting hid_twinhan and then adding usbkbd.

Now I just have to sort out the keymaps... it seems the remote is now detected as a regular keyboard instead of a remote and neither ir-keymap nor lirc recognise it. I found this and I will try later:

http://askubuntu.com/questions/69804/ho ... -presenter

(Note: I'm not using linhes at the moment, but this should still apply)

_________________
ASUS AT3N7A-I (Atom 330)
TBS 8922 PCI (DVB-S2)


Top
 Profile  
 
PostPosted: Tue May 08, 2012 10:00 pm 
Offline
Joined: Tue Mar 22, 2005 9:18 pm
Posts: 1394
Location: Brisbane, Queensland, Australia
To sort out the keymap, it is as simple as importing into the MythTV. This way a normal keyboard will still work, just the keymappings in MythTV are mapped to the buttons on the remote.

A lot simplier and cleaner then having to play with udev. Let me know and I will get the keymappings out of my database and shoot them across to you.

_________________
Girkers


Top
 Profile  
 
PostPosted: Wed May 09, 2012 6:59 am 
Offline
Joined: Mon Jun 21, 2004 5:28 am
Posts: 700
Location: Germany
Girkers wrote:
To sort out the keymap, it is as simple as importing into the MythTV. This way a normal keyboard will still work, just the keymappings in MythTV are mapped to the buttons on the remote.
Maybe you are right. Some of the keys aren't even close and I was reluctant to polute the mythtv keymaps for something I hope is temporary. But at this point, I just want it to work.

_________________
ASUS AT3N7A-I (Atom 330)
TBS 8922 PCI (DVB-S2)


Top
 Profile  
 
PostPosted: Wed May 09, 2012 5:03 pm 
Offline
Joined: Tue Mar 22, 2005 9:18 pm
Posts: 1394
Location: Brisbane, Queensland, Australia
Alien,

You could extract the keymappings as they are now from the DB using (untested on 7.2):
Code:
mysql -t -u root mythconverg keybindings > kb.sql


This will extract the keybindings table to a file in the local directory called kb.sql. You can then take a copy of that file, then modify the values to reflect your remote and then import them back into the DB using (not test in 7.2):
Code:
mysql -u root mythconverg < kb.sql

_________________
Girkers


Top
 Profile  
 
PostPosted: Wed May 16, 2012 11:42 am 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1175
Location: SC
For those of you with this remote please test the new twinham-remote package and report back.
Code:
sudo pacman -U http://linhes.org/repo/i686/extra-testing/twinhan-remote-1-1-i686.pkg.tar.xz


This package will install the usbkbd.ko module and blacklist hid_twinhan. When testing don't forget to disable the scripts that fixed this for you.


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 42 posts ] 
Go to page Previous  1, 2, 3  Next



All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 4 guests


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 post attachments in this forum

Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu