Active Topics
-
Firefox with Leste (5)
to Maemo 7 / Leste by teroyk - 4 days, 10 hrs ago -
Handbook (2)
to Maemo 7 / Leste by teroyk - 5 days, 9 hrs ago - more...
 |
|
2012-07-25
, 23:34
|
|
Posts: 889 |
Thanked: 2,087 times |
Joined on Sep 2010
@ Manchester
|
#2
|
I've had similar symptoms to those you've experienced. Sometimes when I try to connect to a LAN, it fails then I get the "Failed to connect, retry?" dialogue, but a retry fails. I have 2 LANs and neither can be connected until I reboot.
| The Following 2 Users Say Thank You to mrsellout For This Useful Post: | ||
|
|
2012-07-25
, 23:37
|
|
Posts: 2,290 |
Thanked: 4,133 times |
Joined on Apr 2010
@ UK
|
#3
|
So I am not alone but why is it happening?
__________________
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
|
|
2012-07-26
, 08:45
|
|
Posts: 1,808 |
Thanked: 4,272 times |
Joined on Feb 2011
@ Germany
|
#4
|
any chance of installing syslog (package: "sysklogd") and posting the syslog somewhere, or just having a look by yourself in case you spot the problem?
although not as useful, you might want to run "dmesg" from the terminal when this happens, and see if it dumps anything that might seem relevant.
although not as useful, you might want to run "dmesg" from the terminal when this happens, and see if it dumps anything that might seem relevant.
| The Following User Says Thank You to reinob For This Useful Post: | ||
|
|
2012-07-26
, 11:08
|
|
Posts: 2,290 |
Thanked: 4,133 times |
Joined on Apr 2010
@ UK
|
#5
|
Originally Posted by reinob
Why didn't I think of that.
although not as useful, you might want to run "dmesg" from the terminal when this happens, and see if it dumps anything that might seem relevant.
dmesg is repeating a message over and over.
Code:
ADDRCONF (NETDEV_UP): wlan0: link is not ready wl1251: down wl1251: 151 tx blocks at 0x3b788, 35 rx blocks at 0x3a780 wl1251: firmware booted ( rev4.0.4.3.7)
__________________
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
Last edited by sixwheeledbeast; 2012-07-26 at 11:11.
| The Following User Says Thank You to sixwheeledbeast For This Useful Post: | ||
|
|
2012-07-26
, 11:39
|
|
Posts: 1,808 |
Thanked: 4,272 times |
Joined on Feb 2011
@ Germany
|
#6
|
I suppose you're not using any autodisconnect-like program or special modules for the wlan are you?
One thing you could try is: next time the problem occurs, do, as root, "rmmod wl12xx" and then "modprobe wl12xx", and see if that solves the problem.
One thing you could try is: next time the problem occurs, do, as root, "rmmod wl12xx" and then "modprobe wl12xx", and see if that solves the problem.
| The Following 3 Users Say Thank You to reinob For This Useful Post: | ||
|
|
2012-07-26
, 17:14
|
|
Posts: 2,290 |
Thanked: 4,133 times |
Joined on Apr 2010
@ UK
|
#7
|
the fault is still there, I am purposely trying to do without WLAN so I can help diagnose the problem. If I reboot it disappear and may not appear for another 3 months or more...
wifi switcher.
no autodisconnect installed ever.
Used wlan driver selecter applet, this had been uninstalled via HAM a long time ago.
tried rmmod and modprobe the wlan tries to connect but it doesn't make the issue change in anyway.
I suppose wifi switcher does the same thing and I have tried toggling that a couple of times too.
Last edited by sixwheeledbeast; 2012-07-26 at 20:31.
wifi switcher.
no autodisconnect installed ever.
Used wlan driver selecter applet, this had been uninstalled via HAM a long time ago.
tried rmmod and modprobe the wlan tries to connect but it doesn't make the issue change in anyway.
I suppose wifi switcher does the same thing and I have tried toggling that a couple of times too.
__________________
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
Last edited by sixwheeledbeast; 2012-07-26 at 20:31.
| The Following User Says Thank You to sixwheeledbeast For This Useful Post: | ||
|
|
2012-07-26
, 19:54
|
|
Posts: 2,290 |
Thanked: 4,133 times |
Joined on Apr 2010
@ UK
|
#8
|
Seems there maybe a similar bug report.
https://bugs.maemo.org/show_bug.cgi?id=9101#c16
Possibly to do with power saving mode?
Disabled Power saving on my connection it didn't help.
The weird thing about this is it can see the AP in the connection manager but nothing else can see any connections (wifiinfo) etc.
https://bugs.maemo.org/show_bug.cgi?id=9101#c16
Possibly to do with power saving mode?
Disabled Power saving on my connection it didn't help.
The weird thing about this is it can see the AP in the connection manager but nothing else can see any connections (wifiinfo) etc.
__________________
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
|
|
2012-07-28
, 17:46
|
|
Posts: 2,290 |
Thanked: 4,133 times |
Joined on Apr 2010
@ UK
|
#9
|
Anybody got any more ideas how diagnose/fix before I reboot?
Could do with wlan connection back.
Thanks
Could do with wlan connection back.
Thanks
__________________
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
|
|
2012-07-29
, 12:35
|
|
Posts: 2,290 |
Thanked: 4,133 times |
Joined on Apr 2010
@ UK
|
#10
|
Ok so I had to reboot as for some unknown reason the device locked up while searching in MyDocs with filebox.
Now since rebooting twice the device has been warm and battery life is poor (full charge used in 4 hours).
Looking at powertop i can see a stupid amount of hardware wake ups.
This has ever happened before so I am not sure if it's releted to the original issue.
Now since rebooting twice the device has been warm and battery life is poor (full charge used in 4 hours).
Looking at powertop i can see a stupid amount of hardware wake ups.
This has ever happened before so I am not sure if it's releted to the original issue.
Code:
$ uname -r 2.6.28.10-power50
Code:
$ sudo powertop
Powertop 1.13.3
status: Unknown job: pmtrackerdaemon
Sleeping for 11 seconds before sampling
Collecting data for 30 seconds
Sample interval was 00m 30s 90973us
C# | Ratio | Avg/dura | Frequency | Ratio
--------+--------+----------+-----------+--------+
C0 | 51.7% | | 1150 MHz | nan% |
C1 | 0.1% | 0.6ms |
C2 | 4.0% | 4.7ms |
C3 | 24.5% | 71.6ms |
C4 | 19.6% | 92.3ms |
IRQ# | Activity | Type | Name
--------+------------+----------------+---------------------------
12 | 6322 | INTC | DMA
37 | 2127 | INTC | gp
86 | 1580 | INTC | mmc1
67 | 492 | INTC | ssi_p1_mpu_irq0
56 | 408 | INTC | i2c_omap
202 | 294 | GPIO | wl1251
11 | 255 | INTC | prcm
83 | 244 | INTC | mmc0
71 | 197 | INTC | ssi_gdd
311 | 194 | GPIO | ssi_p1_cawake_gpio
225 | 140 | GPIO | omap2-onenand
57 | 67 | INTC | i2c_omap
21 | 10 | INTC | SGX
PID# | Activity | Name | Function Entry (Expire)
--------+------------+----------------+---------------------------
0 | 2029 | <kernel core> | tick_nohz_restart_sched_tick (tick_sched_timer)
613 | 125 | mmcqd | cfq_completed_request (cfq_idle_slice_timer)
38 | 86D| awk | cpufreq_governor_dbs (delayed_work_timer_fn)
15 | 79 | kswapd0 | schedule_timeout (process_timeout)
1382 | 35 | hildon-desktop | schedule_hrtimeout_range (hrtimer_wakeup)
613 | 34 | mmcqd | queue_delayed_work (delayed_work_timer_fn)
580 | 20 | mmcqd | queue_delayed_work (delayed_work_timer_fn)
1810 | 17 | osso-xterm | schedule_hrtimeout_range (hrtimer_wakeup)
702 | 14 | dsme | __enqueue_rt_entity (sched_rt_period_timer)
750 | 14 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
0 | 13 | <kernel core> | hrtimer_start (tick_sched_timer)
1843 | 13 |osso-addressboo | schedule_timeout (process_timeout)
1850 | 10 |rtcom-messaging | schedule_timeout (process_timeout)
580 | 7 | mmcqd | schedule_timeout (process_timeout)
1846 | 7 | rtcom-call-ui | blk_plug_device (blk_unplug_timeout)
750 | 6 | bme_RX-51 | sys_timer_settime (posix_timer_fn)
750 | 6 | bme_RX-51 | schedule_timeout (process_timeout)
613 | 6 | mmcqd | schedule_timeout (process_timeout)
1846 | 6 | rtcom-call-ui | schedule_timeout (process_timeout)
1068 | 5 | Xorg | hrtimer_start (it_real_fn)
15 | 5 | kswapd0 | blk_plug_device (blk_unplug_timeout)
1852 | 5 | rtcom-call-ui | schedule_timeout (process_timeout)
1 | 3D| <kernel core> | queue_delayed_work (delayed_work_timer_fn)
1852 | 3 | rtcom-call-ui | blk_plug_device (blk_unplug_timeout)
14 | 3 | pdflush | schedule_timeout (process_timeout)
1015 | 2 | sgx_perf | queue_delayed_work (delayed_work_timer_fn)
702 | 2 | dsme | do_nanosleep (hrtimer_wakeup)
730 | 2D|<kernel module> | queue_delayed_work (delayed_work_timer_fn)
750 | 2 | bme_RX-51 | do_nanosleep (hrtimer_wakeup)
957 | 2 | ohmd | schedule_hrtimeout_range (hrtimer_wakeup)
1850 | 2 |rtcom-messaging | blk_plug_device (blk_unplug_timeout)
1863 | 2 | browserd | futex_wait (hrtimer_wakeup)
1068 | 1 | Xorg | queue_delayed_work (delayed_work_timer_fn)
1373 | 1 |hildon-status-m | schedule_hrtimeout_range (hrtimer_wakeup)
0 | 1 | <kernel core> | addrconf_verify (addrconf_verify)
993 | 1 | mce | schedule_hrtimeout_range (hrtimer_wakeup)
580 | 1 | mmcqd | schedule_timeout (process_timeout)
1846 | 1 | rtcom-call-ui | schedule_timeout (process_timeout)
1849 | 1 | dbus-daemon | schedule_timeout (process_timeout)
1847 | 1 |e-addressbook-f | futex_wait (hrtimer_wakeup)
1850 | 1 |rtcom-messaging | schedule_timeout (process_timeout)
1851 | 1 |e-addressbook-f | futex_wait (hrtimer_wakeup)
984 | 1 | csd | schedule_hrtimeout_range (hrtimer_wakeup)
580 | 1 | mmcqd | laptop_io_completion (laptop_timer_fn)
1117 | 1 | hald-addon-bme | schedule_hrtimeout_range (hrtimer_wakeup)
14 | 1 | pdflush | schedule_timeout (process_timeout)
1852 | 1 | rtcom-call-ui | schedule_timeout (process_timeout)
14 | 1 | pdflush | blk_plug_device (blk_unplug_timeout)
1339 | 1 | iphbd | schedule_hrtimeout_range (hrtimer_wakeup)
1856 | 1 |e-addressbook-f | futex_wait (hrtimer_wakeup)
1858 | 1 |osso-addressboo | schedule_timeout (process_timeout)
1858 | 1 |osso-addressboo | blk_plug_device (blk_unplug_timeout)
1860 | 1 |e-addressbook-f | futex_wait (hrtimer_wakeup)
1859 | 1 |e-addressbook-f | futex_wait (hrtimer_wakeup)
1852 | 1 | rtcom-call-ui | ubifs_wbuf_write_nolock (wbuf_timer_callback_nolock)
1854 | 1 | browserd | journal_get_write_access (commit_timeout)
14 | 1 | pdflush | ubifs_wbuf_write_nolock (wbuf_timer_callback_nolock)
1381 | 1 | hildon-home | queue_delayed_work (delayed_work_timer_fn)
1838 | 1 | powertop | do_nanosleep (hrtimer_wakeup)
Power domain activity breakdown
Domain | % of time spent in states
--------+---------+---------+---------+---------+----------
usbhost |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
sgx |OFF: 97%|RET: 0%|INA: 0%| ON: 2%| now:(OFF)
per |OFF: 43%|RET: 4%|INA: 0%| ON: 51%| now:(ON)
dss |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
cam |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
core |OFF: 19%|RET: 23%|INA: 2%| ON: 54%| now:(ON)
neon |OFF: 19%|RET: 24%|INA: 3%| ON: 51%| now:(ON)
mpu |OFF: 19%|RET: 24%|INA: 3%| ON: 51%| now:(ON)
iva2 |OFF: 100%|RET: 0%|INA: 0%| ON: 0%| now:(OFF)
Clock activity breakdown at end of period
Domain | Active clocks
--------+---------------+---------------+------------------
core | SDRC | HSOTGUSB_IDLE | OMAPCTRL
| MAILBOXES | MMC2 |
core3 | USBTLL
wkup | GPT1 | 32KSYNC | GPIO1
| SR1 | SR2 |
ckgen | CORE | PERI | 96M
| 48M | 12M | 54M
| EMU_CORE |
per | GPIO2 | GPIO3 | GPIO4
| GPIO5 | GPIO6 |
Total wakeups 14922, 497.4/s | IRQ 12330, 411.0/s | Timers 2592, 86.4/s
HW wakeups 255, 8.5/s | Real gp_timers expired 79, 2.6/s
~ $
Code:
[ 4745.442108] wlan0: associated [ 4746.361053] wlan0: roaming signal from driver, sending LOWSIGNAL [ 4806.819976] wlan0: authenticate with AP 00:1e:e5:8e:c0:4a [ 4807.359985] wlan0: authenticate with AP 00:14:bf:6f:19:2e [ 4807.364593] wlan0: authenticated [ 4807.364685] wlan0: associate with AP 00:14:bf:6f:19:2e [ 4807.371246] wlan0: RX AssocResp from 00:14:bf:6f:19:2e (capab=0x471 status=0 aid=1) [ 4807.371337] wlan0: associated [ 4808.315582] wlan0: roaming signal from driver, sending LOWSIGNAL [ 4814.767272] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 4815.791290] wlan0: roaming signal from driver, sending LOWSIGNAL [ 4820.502197] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 4821.526275] wlan0: roaming signal from driver, sending LOWSIGNAL [ 4824.802703] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 4826.441162] wlan0: roaming signal from driver, sending LOWSIGNAL [ 4827.465423] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 4828.489471] wlan0: roaming signal from driver, sending LOWSIGNAL [ 4849.789306] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 4851.120605] wlan0: roaming signal from driver, sending LOWSIGNAL [ 4886.655151] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 4887.679199] wlan0: roaming signal from driver, sending LOWSIGNAL [ 4888.703002] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 4889.727294] wlan0: roaming signal from driver, sending LOWSIGNAL [ 4891.553955] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 4892.594390] wlan0: roaming signal from driver, sending LOWSIGNAL [ 4894.027984] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 4895.871337] wlan0: roaming signal from driver, sending LOWSIGNAL [ 4897.457519] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 4900.581939] wlan0: roaming signal from driver, sending LOWSIGNAL [ 4901.593292] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 4902.630157] wlan0: roaming signal from driver, sending LOWSIGNAL [ 4905.804870] wlan0: direct probe to AP 00:1e:e5:8e:c0:4a try 1 [ 4906.374664] wlan0: direct probe to AP 00:14:bf:6f:19:2e try 1 [ 4906.379180] wlan0 direct probe responded [ 4906.379272] wlan0: authenticate with AP 00:14:bf:6f:19:2e [ 4906.383575] wlan0: authenticated [ 4906.383789] wlan0: associate with AP 00:14:bf:6f:19:2e [ 4906.390258] wlan0: RX AssocResp from 00:14:bf:6f:19:2e (capab=0x471 status=0 aid=1) [ 4906.390350] wlan0: associated [ 4907.340850] wlan0: roaming signal from driver, sending LOWSIGNAL [ 4925.466430] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 4926.490447] wlan0: roaming signal from driver, sending LOWSIGNAL [ 4928.128662] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 4930.586425] wlan0: roaming signal from driver, sending LOWSIGNAL [ 4933.453948] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 4934.478302] wlan0: roaming signal from driver, sending LOWSIGNAL [ 4939.905395] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 4941.236816] wlan0: roaming signal from driver, sending LOWSIGNAL [ 4957.416839] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 4958.440582] wlan0: roaming signal from driver, sending LOWSIGNAL [ 4959.669219] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 4960.795715] wlan0: roaming signal from driver, sending LOWSIGNAL [ 5005.444213] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 5006.468292] wlan0: roaming signal from driver, sending LOWSIGNAL [ 5008.797912] wlan0: authenticate with AP 00:1e:e5:8e:c0:4a [ 5009.382537] wlan0: direct probe to AP 00:14:bf:6f:19:2e try 1 [ 5009.387054] wlan0 direct probe responded [ 5009.387145] wlan0: authenticate with AP 00:14:bf:6f:19:2e [ 5009.391448] wlan0: authenticated [ 5009.391662] wlan0: associate with AP 00:14:bf:6f:19:2e [ 5009.398345] wlan0: RX AssocResp from 00:14:bf:6f:19:2e (capab=0x471 status=0 aid=1) [ 5009.398437] wlan0: associated [ 5010.359649] wlan0: roaming signal from driver, sending LOWSIGNAL [ 5027.461151] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 5029.261169] wlan0: roaming signal from driver, sending LOWSIGNAL [ 5042.924530] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 5044.767822] wlan0: roaming signal from driver, sending LOWSIGNAL [ 5105.851837] wlan0: authenticate with AP 00:1e:e5:8e:c0:4a [ 5106.421203] wlan0: authenticate with AP 00:14:bf:6f:19:2e [ 5106.425811] wlan0: authenticated [ 5106.425903] wlan0: associate with AP 00:14:bf:6f:19:2e [ 5106.432525] wlan0: RX AssocResp from 00:14:bf:6f:19:2e (capab=0x471 status=0 aid=1) [ 5106.432586] wlan0: associated [ 5107.443420] wlan0: roaming signal from driver, sending LOWSIGNAL [ 5146.352416] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 5147.376770] wlan0: roaming signal from driver, sending LOWSIGNAL [ 5147.595184] slide (GPIO 71) is now open [ 5150.122772] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 5151.148406] wlan0: roaming signal from driver, sending LOWSIGNAL [ 5165.073608] wlan0: roaming signal from driver, sending HIGHSIGNAL [ 5166.097717] wlan0: roaming signal from driver, sending LOWSIGNAL [ 5168.032440] slide (GPIO 71) is now closed [ 5168.789245] wlan0: direct probe to AP 00:1e:e5:8e:c0:4a try 1 [ 5169.323303] wlan0: authenticate with AP 00:14:bf:6f:19:2e [ 5169.327087] wlan0: authenticated [ 5169.327178] wlan0: associate with AP 00:14:bf:6f:19:2e [ 5169.331481] wlan0: RX AssocResp from 00:14:bf:6f:19:2e (capab=0x471 status=0 aid=1)
Code:
$ sudo kernel-config show current kernel configuration: current frequency: 600 supported frequencies: 125 250 500 550 600 720 805 850 900 950 1000 1100 1150 min. frequency: 125 max. frequency: 600 avoid frequencies: active frequencies: 125:22,90 250:25,180 500:37,360 550:39,400 600:42,430 720:60,520 805:60,520 850:60,520 900:60,520 950:60,520 1000:60,520 1100:72,520 1150:72,520 SmartReflex VDD1=1, VDD2=1 governor ondemand: ignore nice load= 0, up threshold= 95, sampling rate= 300000, powersave bias= 0 ~ $
__________________
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
It has happened occasionally before but not for a good while.
Normally a reboot fixes, I assume it will this time; but wondering if anybody know why and if it's happened before?
The wlan is set to autoconnect. I locked and secured the N900 before entering a building with an AP I already setup.
Came back to it 2 hours later unlocked a there was a banner "Failed to connect, retry?"
From this point on it will not connect to any wlan connection, although 2G/3G is fine.
sudo ifconfig is missing wlan0 and wmaster.
Doing wlan0 up and wmaster0 up makes them appear in ifconfig again.
Although trying to connect to an AP makes wlan0 and wmaster0 disappear again.
It's not easy to get the full output of ifconfig pasted up here but if it's necessary I can do that.
lo and phonet0 output seems normal.
Thanks for any help in advance.
Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -
Before posting or starting a thread please try this.
Last edited by sixwheeledbeast; 2012-07-29 at 12:00.