View unanswered posts    View active topics

Board index KnoppMyth Hardware

All times are UTC - 6 hours





Post new topic Reply to topic  Page 1 of 1
  [ 8 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
rando
PostPosted: Sun Jun 11, 2006 10:38 am 
Offline
Joined: Sat Feb 11, 2006 5:26 pm
Posts: 282
Location: Winnipeg - Canada
I've just recently reinstalled my system. I've done some hardware swapping and moved things around from what I had before (was running R5b7 previously).

My hardware:
Abit NF7-S motherboard (nforce 2 chipset)
AMD Athlon 2400+ Socket A processor
256mb (for now) of RAM
200gb PATA HD
AGP Geforce FX5200 card w svideo out
Hauppauge PVR150 MCE tuner
Hauppauge PVR150 non-MCE tuner w IRblaster/reciever
Generic DVD Burner

I think this is all relevant hardware info. Please let me know if I"m missing anything.

I'm running a coax cable feed into the MCE Tuner, and will be recording the regular analog channels in my area through that unit. This works fine, and is how I had my old system setup and running (with r5a30.2, r5b7, and briefly with r5c7). I've purchased the Non-MCE 150 card in hopes of getting the IR Blaster working and throwing a cable box into the mix to open up more channels to my mythbox. That's what's changed since my last successful install.

I've attempted to follow the directions at:

http://www.blushingpenguin.com/mark/blog/?p=24

and:

http://mysettopbox.tv/phpBB2/viewtopic. ... =irblaster

They basically seem to be the same thing as far as I can tell.

Following along from Mark's Braindump:

Quote:
1. Install ivtv-0.4.2+ (from this page). Earlier versions of ivtv _are not supported_.



I'm running KnoppMyth R5C7 which has IVTV 4.4 installed - I've therefore skipped step 1 of these directions.

Quote:
2. Get the pre-patched lirc 0.8.0pre4 (based on the released 0.8.0 lirc);
or alternatively the pre-patched lirc 0.8.1 CVS as of 2006-04-13. The latter
is required for 2.6.16 kernels (but is based on an unreleased version of lirc, as there is currently no release of lirc that supports
2.6.16).



I've downloaded the file in the first line of step 2. Saved it into my /usr/src directory

Quote:
3. Unpack the patched lirc:

cd /usr/src
tar xfj lirc-0.8.0pre4-pvr150.tar.bz2
cd lirc-0.8.0pre4-pvr150
./configure

Choose:
TV card
h - Hauppauge PVR-150 TV card (note: _NOT_ ‘g - Hauppauge TV card’)
Save configuration & run configure

then:

make && make install.


I've done this, didn't see any errors come up at all during this process.

Quote:
4. IR blaster only: Now you need the ‘firmware’. This is
a set of data blocks that correspond to those generated by the windows software. This goes in /usr/lib/hotplug/firmware on my
debian system. Depending on your system this might also be /usr/local/lib/firmware, /lib/firmware or /lib/modules.

Note that the entire firmware is kept in memory (currently 200K) so this makes the driver quite large.
(I have no plans to sort this out, memory is cheap).


I've downloaded the file indicated, and have placed it in /usr/lib/hotplug/firmware. There was already an existing file there, renamed it with a .bak extension prior to DL of this file. Are these the same version? Should I have kept the one that installed with R5C7?

Quote:
5. Check everything is working so far:

modprobe lirc_dev debug=1 && modprobe lirc_pvr150 debug=1

Check the syslog output. This should report something like:

Aug 28 02:09:11 soapbox kernel: lirc_pvr150: chip found with RX and TX
Aug 28 02:09:11 soapbox kernel: ivtv: i2c attach [client=Hauppauge PVR150 IR RX,
ok]
Aug 28 02:09:11 soapbox kernel: ivtv: i2c attach [client=Hauppauge PVR150 IR TX,
ok]
Aug 28 02:09:11 soapbox kernel: lirc_dev: lirc_register_plugin: sample_rate: 0
Aug 28 02:09:11 soapbox udev[5221]: creating device node ‘/dev/lirc0′
Aug 28 02:09:11 soapbox kernel: lirc_pvr150: firmware of size 20927 loaded
Aug 28 02:09:11 soapbox kernel: lirc_pvr150: 575 codesets loaded
Aug 28 02:09:11 soapbox kernel: lirc_pvr150: Hauppauge PVR-150 IR blaster: firmware version 1.3.0

This means that the driver has detected and initialised the IR blaster hardware — if you don’t see that then let me know.


This is where I seem to hit a wall. I don't get the expected output.

Code:
root@backend:~# date
Sun Jun 11 11:16:20 CDT 2006
root@backend:~# modprobe lirc_dev debug=1 && modprobe lirc_pvr150 debug=1
root@backend:~# tail /var/log/syslog
Jun 11 11:13:45 backend kernel: agpgart: Putting AGP V3 device at 0000:02:00.0 into 8x mode
Jun 11 11:13:49 backend lircd-0.8.0pre4-pvr150[3577]: accepted new client on /dev/lircd
Jun 11 11:16:25 backend kernel: kobject_register failed for i2c ir driver (-17)
Jun 11 11:16:25 backend kernel:  [kobject_register+54/96] kobject_register+0x36/0x60
Jun 11 11:16:25 backend kernel:  [bus_add_driver+64/160] bus_add_driver+0x40/0xa0
Jun 11 11:16:25 backend kernel:  [driver_register+66/80] driver_register+0x42/0x50
Jun 11 11:16:25 backend kernel:  [pg0+278435206/1067881472] i2c_add_driver+0x46/0xc0 [i2c_core]
Jun 11 11:16:25 backend kernel:  [pg0+277261610/1067881472] init_module+0x5a/0x60 [lirc_pvr150]
Jun 11 11:16:25 backend kernel:  [sys_init_module+338/528] sys_init_module+0x152/0x210
Jun 11 11:16:25 backend kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
root@backend:~#




Moving along throught following steps of course brings up more failure, each step is obviously dependant on the steps prior, and until I get this part here working I'd imagine it's silly to even really look at the further steps in this guide.

Is all of the relevant info needed for this present? Is there more I can provide to help clue into what I'm running into here?

At this point my install is pretty bare. It was a clean install, no upgrade, no importing from backups or anything like that. I'm totally open to re-installing again if needed. I dunno if I somehow borked something along the way here. Obviously fixing this install is my preferred approach.

Very grateful to anyone who can suggest anything here.
Top
 Profile  
 
rando
 Post subject:
PostPosted: Sun Jun 11, 2006 10:40 am 
Offline
Joined: Sat Feb 11, 2006 5:26 pm
Posts: 282
Location: Winnipeg - Canada
In addition, I suppose this is probably useful information.

Code:
Jun 11 11:13:09 backend kernel: lirc_dev: IR Remote Control driver registered, at major 61
Jun 11 11:13:09 backend kernel: ivtv:  ==================== START INIT IVTV ====================
Jun 11 11:13:09 backend kernel: ivtv:  version 0.4.4 (tagged release) loading
Jun 11 11:13:09 backend kernel: ivtv:  Linux version: 2.6.15-chw-2 SMP preempt 586 gcc-3.3
Jun 11 11:13:09 backend kernel: ivtv:  In case of problems please include the debug info between
Jun 11 11:13:09 backend kernel: ivtv:  the START INIT IVTV and END INIT IVTV lines, along with
Jun 11 11:13:09 backend kernel: ivtv:  any module options, when mailing the ivtv-users mailinglist.
Jun 11 11:13:09 backend kernel: ivtv0: Autodetected WinTV PVR 150 card (cx23416 based)
Jun 11 11:13:09 backend kernel: ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
Jun 11 11:13:09 backend kernel: ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [APC4] -> GSI 19 (level, high) -> IRQ 20
Jun 11 11:13:09 backend kernel: ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
Jun 11 11:13:09 backend kernel: ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
Jun 11 11:13:09 backend kernel: tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0)
Jun 11 11:13:09 backend kernel: ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
Jun 11 11:13:09 backend kernel: cx25840 2-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
Jun 11 11:13:13 backend kernel: cx25840 2-0044: loaded v4l-cx25840.fw firmware (14264 bytes)
Jun 11 11:13:13 backend kernel: ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44]
Jun 11 11:13:13 backend kernel: wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #0)
Jun 11 11:13:13 backend kernel: ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b]
Jun 11 11:13:13 backend kernel: tda9887 2-0043: chip found @ 0x86 (ivtv i2c driver #0)
Jun 11 11:13:13 backend kernel: ivtv0: i2c attach to card #0 ok [client=tda9887, addr=43]
Jun 11 11:13:14 backend kernel: tveeprom 2-0050: Hauppauge model 26552, rev E268, serial# 8354980
Jun 11 11:13:14 backend kernel: tveeprom 2-0050: tuner model is LG TAPE H001F MK3 (idx 68, type 47)
Jun 11 11:13:14 backend kernel: tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08)
Jun 11 11:13:14 backend kernel: tveeprom 2-0050: audio processor is CX25843 (idx 37)
Jun 11 11:13:14 backend kernel: tveeprom 2-0050: decoder processor is CX25843 (idx 30)
Jun 11 11:13:14 backend kernel: tveeprom 2-0050: has radio, has no IR remote
Jun 11 11:13:14 backend kernel: eth0: no IPv6 routers present
Jun 11 11:13:15 backend kernel: ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
Jun 11 11:13:15 backend kernel: ivtv0: Encoder revision: 0x02050032
Jun 11 11:13:15 backend kernel: ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
Jun 11 11:13:15 backend kernel: ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
Jun 11 11:13:15 backend kernel: ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
Jun 11 11:13:15 backend kernel: ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
Jun 11 11:13:15 backend kernel: ivtv0: Create encoder radio stream
Jun 11 11:13:15 backend kernel: tuner 2-0061: type set to 47 (LG NTSC (TAPE series))
Jun 11 11:13:16 backend kernel: ivtv0: Initialized WinTV PVR 150, card #0
Jun 11 11:13:16 backend kernel: ivtv:  ======================  NEXT CARD  ======================
Jun 11 11:13:16 backend kernel: ivtv1: Autodetected WinTV PVR 150 card (cx23416 based)
Jun 11 11:13:16 backend kernel: ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [APC3] -> GSI 18 (level, high) -> IRQ 16
Jun 11 11:13:16 backend kernel: ivtv1: Unreasonably low latency timer, setting to 64 (was 32)
Jun 11 11:13:16 backend kernel: ivtv1: i2c attach to card #1 ok [client=tveeprom, addr=50]
Jun 11 11:13:16 backend kernel: tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #1)
Jun 11 11:13:16 backend kernel: ivtv1: i2c attach to card #1 ok [client=(tuner unset), addr=61]
Jun 11 11:13:16 backend kernel: cx25840 3-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #1)
Jun 11 11:13:19 backend kernel: cx25840 3-0044: loaded v4l-cx25840.fw firmware (14264 bytes)
Jun 11 11:13:19 backend kernel: ivtv1: i2c attach to card #1 ok [client=cx25840, addr=44]
Jun 11 11:13:19 backend kernel: wm8775 3-001b: chip found @ 0x36 (ivtv i2c driver #1)
Jun 11 11:13:19 backend kernel: ivtv1: i2c attach to card #1 ok [client=wm8775, addr=1b]
Jun 11 11:13:20 backend kernel: tveeprom 3-0050: Hauppauge model 26032, rev C599, serial# 8384861
Jun 11 11:13:20 backend kernel: tveeprom 3-0050: tuner model is TCL 2002N 5H (idx 99, type 50)
Jun 11 11:13:20 backend kernel: tveeprom 3-0050: TV standards NTSC(M) (eeprom 0x08)
Jun 11 11:13:20 backend kernel: tveeprom 3-0050: audio processor is CX25841 (idx 35)
Jun 11 11:13:20 backend kernel: tveeprom 3-0050: decoder processor is CX25841 (idx 28)
Jun 11 11:13:20 backend kernel: tveeprom 3-0050: has no radio, has IR remote
Jun 11 11:13:20 backend kernel: ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
Jun 11 11:13:21 backend kernel: ivtv1: Encoder revision: 0x02050032
Jun 11 11:13:21 backend kernel: ivtv1: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
Jun 11 11:13:21 backend kernel: ivtv1: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
Jun 11 11:13:21 backend kernel: ivtv1: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
Jun 11 11:13:21 backend kernel: ivtv1: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
Jun 11 11:13:21 backend kernel: tuner 3-0061: type set to 50 (TCL 2002N)
Jun 11 11:13:21 backend kernel: ivtv1: Initialized WinTV PVR 150, card #1
Jun 11 11:13:21 backend kernel: ivtv:  ====================  END INIT IVTV  ====================
Jun 11 11:13:21 backend kernel: cx2388x v4l2 driver version 0.0.5 loaded
Jun 11 11:13:21 backend kernel: lirc_i2c: chip found @ 0x71 (Hauppauge IR (PVR150))
Jun 11 11:13:21 backend kernel: ivtv1: i2c attach to card #1 ok [client=Hauppauge IR (PVR150), addr=71]
Jun 11 11:13:21 backend kernel: lirc_dev: lirc_register_plugin: sample_rate: 10
Jun 11 11:13:21 backend lircd-0.8.0pre4-pvr150[3577]: lircd(all) ready



The line above, and 5 lines below the IVTV section were included because they looked to me to be relevant.
Top
 Profile  
 
rando
 Post subject:
PostPosted: Sun Jun 11, 2006 7:24 pm 
Offline
Joined: Sat Feb 11, 2006 5:26 pm
Posts: 282
Location: Winnipeg - Canada
Ok, totally reformatted this afternoon and reinstalled from scratch. Pulled out the MCE PVR 150 card just to simplify things as much as possible.

My hardware:
Abit NF7-S motherboard (nforce 2 chipset)
AMD Athlon 2400+ Socket A processor
256mb (for now) of RAM
200gb PATA HD
AGP Geforce FX5200 card w svideo out
Hauppauge PVR150 MCE tuner (not currently in the system - will be added in as soon as I can make this work)
Hauppauge PVR150 non-MCE tuner w IRblaster/reciever
Generic DVD Burner

I've done an Autoinstall from a boot off a R5C7 CD. Everything seems to go fine during the install. I end up booting into the frontend.

I selected NO for Serial IR blaster during the setup as my IRblaster is not connected via serial, it's built into my PVR 150 card (can someone verify that this was the correct choice?)

Once I'm up and running I"m opening an SSH session from my windows box to my mythtv box and following through the directions here.
http://www.blushingpenguin.com/mark/blog/?p=24.

Quote:
1. Install ivtv-0.4.2+ (from this page). Earlier versions of ivtv _are not supported_.


I have skipped this step altogether as R5B7 has .4.4 built in.

Quote:
2. Get the pre-patched lirc 0.8.0pre4 (based on the released 0.8.0 lirc);
or alternatively the pre-patched lirc 0.8.1 CVS as of 2006-04-13. The latter
is required for 2.6.16 kernels (but is based on an unreleased version of lirc, as there is currently no release of lirc that supports


I *think* that the version of that comes with R5B7 is the same as this, but I've done this step regardless.

Quote:
. Unpack the patched lirc:


cd /usr/src
tar xfj lirc-0.8.0pre4-pvr150.tar.bz2
cd lirc-0.8.0pre4-pvr150
./configure

Choose:
TV card
h - Hauppauge PVR-150 TV card (note: _NOT_ ‘g - Hauppauge TV card’)
Save configuration & run configure

then:

make && make install.


I've done this as well, and it seems to work. A few tiny differences I encountered here:

a) The directions say "choose TV card" The main menu once I load up ./configure doesn't give me an option for "TV card" If I go into "1 Driver configuration" i see the option for "5 TV card" This is what I have done.

b) The next step says "h - Hauppauge PVR-150 TV card (note: _NOT_ ‘g - Hauppauge TV card’)" is the choice I want, again I don't see quite exactly that, but I do pick option 'h' which says "Hauppauge PVR-150 TV Card (new I2C layer required).

That seems to go through fine. I save and run configure. Then run the make && make install which appears to go fine (though stuff goes by fast, there could very well be badness in here that I'm not seeing - in any event it completes without any obvious troubles).

Quote:
4. IR blaster only: Now you need the ‘firmware’. This is
a set of data blocks that correspond to those generated by the windows software. This goes in /usr/lib/hotplug/firmware on my
debian system. Depending on your system this might also be /usr/local/lib/firmware, /lib/firmware or /lib/modules.

Note that the entire firmware is kept in memory (currently 200K) so this makes the driver quite large.
(I have no plans to sort this out, memory is cheap).


I'm downloading the firmware file linked here and placing it in /usr/lib/hotplug/firmware. There is an existing haup-ir-blaster.bin file that I am naming haup-ir-blaster.bin.bak prior to the download.

Quote:
5. Check everything is working so far:

modprobe lirc_dev debug=1 && modprobe lirc_pvr150 debug=1

Check the syslog output. This should report something like:

Aug 28 02:09:11 soapbox kernel: lirc_pvr150: chip found with RX and TX
Aug 28 02:09:11 soapbox kernel: ivtv: i2c attach [client=Hauppauge PVR150 IR RX,
ok]
Aug 28 02:09:11 soapbox kernel: ivtv: i2c attach [client=Hauppauge PVR150 IR TX,
ok]
Aug 28 02:09:11 soapbox kernel: lirc_dev: lirc_register_plugin: sample_rate: 0
Aug 28 02:09:11 soapbox udev[5221]: creating device node ‘/dev/lirc0′
Aug 28 02:09:11 soapbox kernel: lirc_pvr150: firmware of size 20927 loaded
Aug 28 02:09:11 soapbox kernel: lirc_pvr150: 575 codesets loaded
Aug 28 02:09:11 soapbox kernel: lirc_pvr150: Hauppauge PVR-150 IR blaster: firmware version 1.3.0

This means that the driver has detected and initialised the IR blaster hardware — if you don’t see that then let me know.


This is again where I"m running into problems. The output of my syslog is as follows:

Code:
Jun 12 00:20:26 backend kernel: kobject_register failed for i2c ir driver (-17)
Jun 12 00:20:26 backend kernel: [kobject_register+54/96] kobject_register+0×36/0×60
Jun 12 00:20:26 backend kernel: [bus_add_driver+64/160] bus_add_driver+0×40/0xa0
Jun 12 00:20:26 backend kernel: [driver_register+66/80] driver_register+0×42/0×50
Jun 12 00:20:26 backend kernel: [pg0+273991046/1067881472] i2c_add_driver+0×46/0xc0 [i2c_core]
Jun 12 00:20:26 backend kernel: [pg0+276901162/1067881472] init_module+0×5a/0×60 [lirc_pvr150]
Jun 12 00:20:26 backend kernel: [sys_init_module+338/528] sys_init_module+0×152/0×210
Jun 12 00:20:26 backend kernel: [syscall_call+7/11] syscall_call+0×7/0xb


I'm pretty far out of my element at this point. I'm very comfortable in linux, so long as I have directions. Navigating around, moving files, editing files, all that stuff is easy peasy for me, but as far as a proper understanding of what is happening when stuff like this pops up, I'm pretty lost pretty fast.

There was talk in other posts of the hotplug and IVTV loading in the wrong order with some of the recent changes that have been made. tjc had directed other people to follow the directions in the second half of the "upgrading ivtv" knoppwiki page. I've checked that page, and I don't see anything there that isn't in place on my system. My md5sums match the firmware sums listed there. I don't have the ivtv module listed in my /etc/modules. I think that means I'm not running into the hotplug not being ready when ivtv loads problem, but i'm not sure.

The only thing that really pops to mind, is that when I select the hauppauge PVR 150 card in the ./configure of lirc it's suggesting that I need a new I2C layer. Do I already have the "new" layer that it says I need? How do I check, and if I don't have it, what do I need to do in order to get that happening?
Top
 Profile  
 
rando
 Post subject:
PostPosted: Mon Jun 12, 2006 11:09 am 
Offline
Joined: Sat Feb 11, 2006 5:26 pm
Posts: 282
Location: Winnipeg - Canada
Well, after several attempts at this, and a lack of the skills required to really dig into things and find out what is or isn't happening that's getting in my way, I think I'm gonna give up on the PVR 150's built in IR blaster and pickup a serial blaster.

It sounds like the serial blasters have much much better support and should basically just work without a bunch of fussing and mussing.
Top
 Profile  
 
drunnero
 Post subject:
PostPosted: Thu Aug 03, 2006 9:10 am 
Offline
Joined: Tue May 02, 2006 10:52 pm
Posts: 5
Location: West Virginia
Rando did you get your serial port blaster working? I'm trying to get mine up a running.
Top
 Profile  
 
rando
 Post subject:
PostPosted: Thu Aug 03, 2006 1:06 pm 
Offline
Joined: Sat Feb 11, 2006 5:26 pm
Posts: 282
Location: Winnipeg - Canada
Yes, actually I did. I ran through the IR setup script that's built into the mythtv setup and it detected and worked fine. I just had to fuss a tiny bit with a config file for my cable box so that it would be sending the right signals.
Top
 Profile  
 
mihanson
 Post subject:
PostPosted: Thu Aug 03, 2006 2:27 pm 
Offline
Joined: Sun Sep 25, 2005 3:50 pm
Posts: 1013
Location: Los Angeles
Rando,
Some of the directions you were following may be a bit out of date. Try the IVTV install on the wiki. It's the most up-to-date (and best, "drunken monkey") install doc for IVTV and KnoppMyth as far as I know.

Off the top of my head I think you need to re-name the firmware file you put in the hotplug directory.

Quote:
I selected NO for Serial IR blaster during the setup as my IRblaster is not connected via serial, it's built into my PVR 150 card (can someone verify that this was the correct choice?)


Yes, if you are using the PVR-150's IR Blaster, you say NO to the serial blaster question.

I think you may be complicating the IVTV install more than it needs to be. If you install R5B/C7 IVTV should install automagicly. It has for me in the recent past, anyway.

_________________
Mike
My Hardware Profile
Top
 Profile  
 
rando
 Post subject:
PostPosted: Thu Aug 03, 2006 3:13 pm 
Offline
Joined: Sat Feb 11, 2006 5:26 pm
Posts: 282
Location: Winnipeg - Canada
My system is running and working fine right now....

I was using the PVR 150 built in IR blaster, and it wasn't working (at that time i selected NO as it wasn't a serial blaster). I've since given up on the PVR 150 blaster, and bought a serial unit that works fine with the knoppmyth built in script.

My original post in this thread is from quite some time ago, I'm just replying to a post made by drunnero. My system has been up and runnign with the serial blaster for well over a month.
Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  Page 1 of 1
  [ 8 posts ] 


Board index KnoppMyth Hardware

All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 31 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:  
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu