View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 10 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Tue Jan 31, 2017 6:52 am 
Offline
Joined: Tue Jul 01, 2014 6:49 am
Posts: 65
When last we checked in with our intrepid explorers....My Atom based MBE died and I had a Celeron MB sitting around, so I swapped it out. The celeron based MBE just didn't have enough horse power to record 4 shows and stream a 5th, so I decided to jump to a more powerful 4 core i5 intel CPU. This is one of the new Kaby Lake versions, figured I would get something cutting edge to last a while.

So installed the new mother board, memory, cpu and used the old 3T hard drive, should have been a no brainer to do a simple upgrade and life is good! Nope...turns out one of the 4G memory sticks was keeping the system from Posting, figured that out and moved on to the upgrade.

Next issue was the 8.4.2 upgrade wouldn't load using the normal LinHes load (first choice offered), turns out some of the i915 components failed to load and so I would get "systemd [1] Linhes install service main process exited status 1/failure. So booted forcing Vesa and was able to get the upgrade and a system that works.

Now the issue I need help with, my kernel log is filling up with the errors shown below. All mythtv functions seem to work normally, so I'm not seeing an issue with functionality on the MBE or the 3 SBEs in my config. Trying to search for what the error means, they seem to point to either the microcode for intel not being loaded early enough (https://wiki.archlinux.org/index.php/microcode), based on the general protection errors or a problem with NFS, which I didn't think Mythtv used (but I could be wrong) and if it is enabled in my system, that would be a mistake on my part.

Here is an example of the logs:
Code:
Jan 31 06:22:33 mbe kernel: [59551.026069] do_general_protection: 1 callbacks suppressed
Jan 31 06:22:33 mbe kernel: [59551.026072] traps: rpc.statd[25883] general protection ip:7f3258c82400 sp:7ffeafd577d8 error:0 in libpthread-2.23.so[7f3258c70000+18000]
Jan 31 06:22:33 mbe kernel: [59551.197812] traps: rpc.mountd[25920] general protection ip:7fee27fda400 sp:7ffe6a6d1bf8 error:0 in libpthread-2.23.so[7fee27fc8000+18000]
Jan 31 06:22:34 mbe kernel: [59552.105170] traps: rpc.statd[25991] general protection ip:7fd9e6bd0400 sp:7fff3154dd78 error:0 in libpthread-2.23.so[7fd9e6bbe000+18000]
Jan 31 06:22:34 mbe kernel: [59552.234726] traps: rpc.mountd[26028] general protection ip:7f8f94393400 sp:7ffd6cca2f28 error:0 in libpthread-2.23.so[7f8f94381000+18000]


Can anyone weigh in and shed any light on what is going on?

Thanks
Bruce.


Top
 Profile  
 
PostPosted: Tue Jan 31, 2017 7:34 am 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 932
Location: SC
After installing did it boot with intel drivers? Check the Xorg.log.

It doesn't look like we have the microcode pkg in our repo or have any provisions to get it into the bootloader right now. By default for MBEs NFS is started. You can start by disabling NFS in LinHES Setting > File Sharing. That is just a workaround for now. I would really like to get to the core of what is causing the issue.


Top
 Profile  
 
PostPosted: Tue Jan 31, 2017 12:23 pm 
Offline
Joined: Tue Jul 01, 2014 6:49 am
Posts: 65
brfransen wrote:
After installing did it boot with intel drivers? Check the Xorg.log.

It doesn't look like we have the microcode pkg in our repo or have any provisions to get it into the bootloader right now. By default for MBEs NFS is started. You can start by disabling NFS in LinHES Setting > File Sharing. That is just a workaround for now. I would really like to get to the core of what is causing the issue.


When I did the upgrade I had to force VESA, so I'm not seeing any intel or i915 items loaded in xorg.0.log, just VESA.

On turning off nfs, I noticed two immediate item: on SBE, channel changes were not persistent, by that I mean enter live tv, change to a different channel, exit live tv. Enter live tv again, original channel is playing not changed to channel.

Audio was disabled AOOSS error shown entering live tv for the first time after disabling nfs on MBE. 2nd time into live tv audio functions.

Turning nfs back on clears up the channel change issue.

I will follow the wiki item to see if loading the micro code early changes anything and report back, and keep digging into logs to see what other clues turn up.

Thanks!


Top
 Profile  
 
PostPosted: Tue Jan 31, 2017 5:32 pm 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 932
Location: SC
Can you run xconfig.sh and post the output. If it doesn't work you can force vesa as shown here: http://linhes.org/projects/linhes/wiki/ ... #xconfigsh

The live tv and NFS off issue strike me a coincidence. The live tv channel should be coming from the mythtv db and that isn't using NFS in any way but rather the myth protocol. Anything in the logs of the SBE?


Top
 Profile  
 
PostPosted: Wed Feb 01, 2017 5:43 am 
Offline
Joined: Tue Jul 01, 2014 6:49 am
Posts: 65
Bit of a useless update since no log info and weak observations...

Blame it on lack of coffee or short troubles shooting window, but here goes:

Got up early this am, opened a terminal and ran xconfig.sh, I've not ran it before, so not sure what I was to see. So it detected intel, the last line showed plymouthd, then it exited, no error or success message just back to #.

So I rebooted and the system started to load and got hung up in a loop, I should have written down what was being displayed.

I couldn't remember how to modify my grub boot to force VESA, so I had to perform an upgrade to recover the system. I did try the standard upgrade and it errored out as described above, so used forced VESA and recovered the system.

When I have a decent window, I will try again and capture notes/log files.

On the nfs and channel change, I will retest, but as soon as I reenabled nfs, Channel changes worked as normal.

Also on the microcode item, I installed it and modified the boot to early start it, but no change, it appears the CPU is too new to have updates.

More to come...


Top
 Profile  
 
PostPosted: Thu Feb 02, 2017 10:44 am 
Offline
Joined: Tue Jul 01, 2014 6:49 am
Posts: 65
Tried xconfig.sh again this am (with coffee on board and time to play).

What I saw running
Code:
[mythtv@mbe ~]$ sudo xconfig.sh:
Detected Intel as the video card type
  Checking for xf86-video-intel in cache or online
  Checking for mesa-libgl in cache or online
Installing Intel Driver
Running plymouth config
[mythtv@mbe ~]$


Rather than rebooting, I tried startx, it dumped me into the following log: (Xorg.1.log)
Code:
[   767.524]
X.Org X Server 1.18.4
Release Date: 2016-07-19
[   767.524] X Protocol Version 11, Revision 0
[   767.524] Build Operating System: Linux 4.4.13-1-ARCH x86_64
[   767.524] Current Operating System: Linux mbe 4.4.26-1-ARCH #1 SMP PREEMPT Fri Oct 21 16:25:30 UTC 2016 x86_64
[   767.524] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=6665dec6-8d3d-4daa-8995-6c70965f9c91 ro init=/sbin/runit
[   767.524] Build Date: 29 July 2016  04:57:17PM
[   767.524] 
[   767.524] Current version of pixman: 0.32.8
[   767.524]    Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
[   767.524] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   767.524] (==) Log file: "/var/log/Xorg.1.log", Time: Thu Feb  2 06:50:44 2017
[   767.524] (==) Using config directory: "/etc/X11/xorg.conf.d"
[   767.524] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   767.524] (==) No Layout section.  Using the first Screen section.
[   767.524] (==) No screen section available. Using defaults.
[   767.524] (**) |-->Screen "Default Screen Section" (0)
[   767.524] (**) |   |-->Monitor "<default monitor>"
[   767.524] (==) No device specified for screen "Default Screen Section".
   Using the first device section listed.
[   767.524] (**) |   |-->Device "Intel Graphics"
[   767.524] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
[   767.524] (==) Automatically adding devices
[   767.524] (==) Automatically enabling devices
[   767.524] (==) Automatically adding GPU devices
[   767.524] (==) Max clients allowed: 256, resource mask: 0x1fffff
[   767.524] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[   767.524]    Entry deleted from font path.
[   767.524] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[   767.524]    Entry deleted from font path.
[   767.524] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[   767.524]    Entry deleted from font path.
[   767.524]    (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[   767.524] (==) FontPath set to:
   /usr/share/fonts/misc/,
   /usr/share/fonts/TTF/,
   /usr/share/fonts/100dpi/
[   767.525] (==) ModulePath set to "/usr/lib/xorg/modules"
[   767.525] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
[   767.525] (II) Loader magic: 0x563ecf553ca0
[   767.525] (II) Module ABI versions:
[   767.525]    X.Org ANSI C Emulation: 0.4
[   767.525]    X.Org Video Driver: 20.0
[   767.525]    X.Org XInput driver : 22.1
[   767.525]    X.Org Server Extension : 9.0
[   767.525] (--) PCI:*(0:0:2:0) 8086:5912:1849:5912 rev 4, Mem @ 0xde000000/16777216, 0xc0000000/268435456, I/O @ 0x0000f000/64
[   767.525] (II) Open ACPI successful (/var/run/acpid.socket)
[   767.525] (II) LoadModule: "glx"
[   767.526] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   767.527] (II) Module glx: vendor="X.Org Foundation"
[   767.527]    compiled for 1.18.4, module version = 1.0.0
[   767.527]    ABI class: X.Org Server Extension, version 9.0
[   767.527] (==) AIGLX enabled
[   767.527] (II) LoadModule: "intel"
[   767.527] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[   767.558] (II) Module intel: vendor="X.Org Foundation"
[   767.558]    compiled for 1.18.4, module version = 2.99.917
[   767.558]    Module class: X.Org Video Driver
[   767.558]    ABI class: X.Org Video Driver, version 20.0
[   767.558] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
   i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
   915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
   Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
   GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[   767.558] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[   767.558] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[   767.558] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300
[   767.558] (--) using VT number 5

[   767.903] (EE) No devices detected.
[   767.903] (EE)
Fatal server error:
[   767.903] (EE) no screens found(EE)
[   767.903] (EE)
Please consult the The X.Org Foundation support
    at http://wiki.x.org
 for help.
[   767.903] (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information.
[   767.903] (EE)


Next I rebooted, just to see if the endless loop happened, it did, what I saw was (sorry for any typos, could find a log with these in them):
Code:
:: Starting NFSD
 >    Using
:: Starting NFS-common: nfs-common
>    NFS-common: sm-notify
>    NFS-common: rpc.idmapd
>    NFS-common: rpc.gssd
./run: line 83: 12923 Segmentation fault   (core dumped) $ STATD -F > /dev/null 2> /dev/null
:: Stopping rpc.gssd daemon
:: Stopping rpc.idmapd daemon
:: Stopping rpc.statd daemon
:: Starting NFSD
...


The "Starting NFSD" loops continuously (number before Segmentation fault would change) until rebooting and upgrading with force VESA.

Let me know if there is some other log info I can capture or other thing you would like me to try and capture.

Thanks
Bruce.


Top
 Profile  
 
PostPosted: Thu Feb 02, 2017 11:30 am 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 932
Location: SC
Can you post the /tmp/xconfig.sh after running xconfig.sh? Maybe pacman -Syu as there is some additional logging in xconfig.sh that is newer than the R8.4.2 ISO.

Until you are able to get X to run with the intel drivers don't bother rebooting. To force vesa back after installing the intel drivers:
Code:
sudo VGACARDTYPE="vesa" xconfig.sh


Try experimenting with these various options: https://wiki.archlinux.org/index.php/In ... tel_driver in /etc/X11/xorg.conf.d/20-automv.conf


Top
 Profile  
 
PostPosted: Thu Feb 02, 2017 4:47 pm 
Offline
Joined: Tue Jul 01, 2014 6:49 am
Posts: 65
here is xconfig.log:

After a number of back and forth, the last section is the Intel load, where I then did a startx, but still no monitors found in the Xorg.1.log, so no luck on the intel side yet.
Code:
resolving dependencies...

Package (1)           Old Version  New Version  Net Change

core/xf86-video-vesa  2.3.4-2      2.3.4-2        0.00 MiB

Total Download Size:  0.00 MiB

:: Proceed with download? [Y/n]
checking keyring...
checking package integrity...
resolving dependencies...

Package (1)      Old Version  New Version  Net Change

core/mesa-libgl  12.0.3-3     12.0.3-3       0.00 MiB

Total Download Size:  0.00 MiB

:: Proceed with download? [Y/n]
checking keyring...
checking package integrity...
Installing Vesa driver
error: target not found: libva-intel-driver

Package (1)  Old Version  Net Change

mesa-libgl   12.0.3-3      -0.01 MiB

Total Removed Size:  0.01 MiB

:: Do you want to remove these packages? [Y/n]
:: Processing package changes...
removing mesa-libgl...
error: target not found: nvidia
error: target not found: nvidia-utils
error: target not found: nvidia-libgl
error: target not found: opencl-nvidia
error: target not found: nvidia-settings
error: target not found: libglvnd
error: target not found: nvidia-304xx
error: target not found: nvidia-304xx-utils
error: target not found: nvidia-304xx-libgl
error: target not found: opencl-nvidia-304xx
error: target not found: nvidia-340xx
error: target not found: nvidia-340xx-utils
error: target not found: nvidia-340xx-libgl
error: target not found: opencl-nvidia-340xx
error: target not found: ati-dri
error: target not found: xf86-video-ati
error: target not found: intel-dri
error: target not found: xf86-video-intel
error: target not found: mga-dri
error: target not found: xf86-video-mga
error: target not found: savage-dri
error: target not found: xf86-video-savage
error: target not found: sis-dri
error: target not found: xf86-video-sis
error: target not found: unichrome-dri
error: target not found: xf86-video-unichrome
warning: xf86-video-vesa-2.3.4-2 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Package (2)           Old Version  New Version  Net Change

core/mesa-libgl                    12.0.3-3       0.01 MiB
core/xf86-video-vesa  2.3.4-2      2.3.4-2        0.00 MiB

Total Installed Size:  0.04 MiB
Net Upgrade Size:      0.01 MiB

:: Proceed with installation? [Y/n]
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
:: Processing package changes...
reinstalling xf86-video-vesa...
installing mesa-libgl...
    plymouth_config: found videocard vesa
    plymouth_config: no changes made
resolving dependencies...

Package (1)           Old Version  New Version  Net Change

core/xf86-video-vesa  2.3.4-2      2.3.4-2        0.00 MiB

Total Download Size:  0.00 MiB

:: Proceed with download? [Y/n]
checking keyring...
checking package integrity...
resolving dependencies...

Package (1)      Old Version  New Version  Net Change

core/mesa-libgl  12.0.3-3     12.0.3-3       0.00 MiB

Total Download Size:  0.00 MiB

:: Proceed with download? [Y/n]
checking keyring...
checking package integrity...
Installing Vesa driver
error: target not found: libva-intel-driver

Package (1)  Old Version  Net Change

mesa-libgl   12.0.3-3      -0.01 MiB

Total Removed Size:  0.01 MiB

:: Do you want to remove these packages? [Y/n]
:: Processing package changes...
removing mesa-libgl...
error: target not found: nvidia
error: target not found: nvidia-utils
error: target not found: nvidia-libgl
error: target not found: opencl-nvidia
error: target not found: nvidia-settings
error: target not found: libglvnd
error: target not found: nvidia-304xx
error: target not found: nvidia-304xx-utils
error: target not found: nvidia-304xx-libgl
error: target not found: opencl-nvidia-304xx
error: target not found: nvidia-340xx
error: target not found: nvidia-340xx-utils
error: target not found: nvidia-340xx-libgl
error: target not found: opencl-nvidia-340xx
error: target not found: ati-dri
error: target not found: xf86-video-ati
error: target not found: intel-dri
error: target not found: xf86-video-intel
error: target not found: mga-dri
error: target not found: xf86-video-mga
error: target not found: savage-dri
error: target not found: xf86-video-savage
error: target not found: sis-dri
error: target not found: xf86-video-sis
error: target not found: unichrome-dri
error: target not found: xf86-video-unichrome
warning: xf86-video-vesa-2.3.4-2 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Package (2)           Old Version  New Version  Net Change

core/mesa-libgl                    12.0.3-3       0.01 MiB
core/xf86-video-vesa  2.3.4-2      2.3.4-2        0.00 MiB

Total Installed Size:  0.04 MiB
Net Upgrade Size:      0.01 MiB

:: Proceed with installation? [Y/n]
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
:: Processing package changes...
reinstalling xf86-video-vesa...
installing mesa-libgl...
    plymouth_config: found videocard vesa
    plymouth_config: no changes made
resolving dependencies...

Package (1)            New Version                Net Change

core/xf86-video-intel  1:2.99.917+730+gdad64e9-1    2.20 MiB

Total Download Size:  0.00 MiB

:: Proceed with download? [Y/n]
checking keyring...
checking package integrity...
resolving dependencies...

Package (1)      Old Version  New Version  Net Change

core/mesa-libgl  12.0.3-3     12.0.3-3       0.00 MiB

Total Download Size:  0.00 MiB

:: Proceed with download? [Y/n]
checking keyring...
checking package integrity...
Installing Intel driver
error: target not found: libva-intel-driver

Package (1)  Old Version  Net Change

mesa-libgl   12.0.3-3      -0.01 MiB

Total Removed Size:  0.01 MiB

:: Do you want to remove these packages? [Y/n]
:: Processing package changes...
removing mesa-libgl...
error: target not found: nvidia
error: target not found: nvidia-utils
error: target not found: nvidia-libgl
error: target not found: opencl-nvidia
error: target not found: nvidia-settings
error: target not found: libglvnd
error: target not found: nvidia-304xx
error: target not found: nvidia-304xx-utils
error: target not found: nvidia-304xx-libgl
error: target not found: opencl-nvidia-304xx
error: target not found: nvidia-340xx
error: target not found: nvidia-340xx-utils
error: target not found: nvidia-340xx-libgl
error: target not found: opencl-nvidia-340xx
error: target not found: ati-dri
error: target not found: xf86-video-ati
error: target not found: intel-dri
error: target not found: xf86-video-intel
error: target not found: mga-dri
error: target not found: xf86-video-mga
error: target not found: savage-dri
error: target not found: xf86-video-savage
error: target not found: sis-dri
error: target not found: xf86-video-sis
error: target not found: unichrome-dri
error: target not found: xf86-video-unichrome
resolving dependencies...
looking for conflicting packages...

Package (3)               New Version                Net Change

extra/libva-intel-driver  1.7.3-1                      2.02 MiB
core/mesa-libgl           12.0.3-3                     0.01 MiB
core/xf86-video-intel     1:2.99.917+730+gdad64e9-1    2.20 MiB

Total Installed Size:  4.23 MiB

:: Proceed with installation? [Y/n]
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
:: Processing package changes...
installing xf86-video-intel...
>>> This driver now uses DRI3 as the default Direct Rendering
    Infrastructure. You can try falling back to DRI2 if you run
    into trouble. To do so, save a file with the following
    content as /etc/X11/xorg.conf.d/20-intel.conf :
      Section "Device"
        Identifier  "Intel Graphics"
        Driver      "intel"
        Option      "DRI" "2"             # DRI3 is now default
        #Option      "AccelMethod"  "sna" # default
        #Option      "AccelMethod"  "uxa" # fallback
      EndSection
Optional dependencies for xf86-video-intel
    libxrandr: for intel-virtual-output [installed]
    libxinerama: for intel-virtual-output [installed]
    libxcursor: for intel-virtual-output [installed]
    libxtst: for intel-virtual-output [installed]
    libxss: for intel-virtual-output [installed]
installing mesa-libgl...
installing libva-intel-driver...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 4.4.26-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
  -> Running build hook: [plymouth]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 4.4.26-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
  -> Running build hook: [plymouth]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
    plymouth_config: found videocard intel
    plymouth_config: Running mkinitcpio


Top
 Profile  
 
PostPosted: Wed Feb 15, 2017 2:15 pm 
Offline
Joined: Tue Jul 01, 2014 6:49 am
Posts: 65
Had a chance to troubleshoot some more, I had a new hard drive to play with, so I tried a full install and see the same result as an upgrade, I'm sure that's not a surprise, just wanted to confirm that is what happening. I switched to the new harddrive / new install to see if I could identify any changes from my in use harddrive.

So on the new HD, did a full install forcing vesa, once on line I opened a terminal and did a paceman -Syu, when that finished i ran xconfig.sh. Once that completed I played with the various options in etc/X11/xorg.conf.d/20-automv.conf as outlined in the wiki.

Same results as previously, xorg errors out with "no device detected, no screens found errors.

Any further places to look, feel free to suggest!

Thanks
Bruce


Top
 Profile  
 
PostPosted: Wed Feb 15, 2017 4:03 pm 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 932
Location: SC
Maybe something with the i915 module is needed: https://wiki.archlinux.org/index.php/Ke ... _KMS_start


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 10 posts ] 


All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 1 guest


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