tomek-fedora10 Napisano Styczeń 6, 2015 Zgłoszenie Share Napisano Styczeń 6, 2015 Od jakiegoś czasu posiadam Raspberry Pi. Do tej pory używałem Raspbiana ale skoro na laptopie używam Fedory to postanowiłem na RPi zainstalować Pidorę. I tu zaczynają schody, bo nie mogę uruchomić systemu w trybie graficznym. Na ekranie otrzymuję komunikat, że "coś poszło nie tak". Mam plik Xorg.0.log. Czy ktoś może na niego spojrzeć? [ 510.608]X.Org X Server 1.14.4Release Date: 2013-10-31[ 510.609] X Protocol Version 11, Revision 0[ 510.609] Build Operating System: 3.6.10-8.fc18.armv7hl.highbank[ 510.610] Current Operating System: Linux pidora.local 3.12.23-1.20140626git25673c3.rpfr20.armv6hl.bcm2708 #1 PREEMPT Wed Jul 2 15:13:43 EDT 2014 armv6l[ 510.611] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1794 bcm2708_fb.fbheight=954 bcm2708.boardrev=0x10 bcm2708.serial=0x7ad4dc99 smsc95xx.macaddr=B8:27:EB:D4:DC:99 bcm2708.disk_led_gpio=47 bcm2708.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p6 ro rootfstype=ext4 rootwait quiet[ 510.614] Build Date: 24 May 2014 11:49:24AM[ 510.614] Build ID: xorg-x11-server 1.14.4-9.fc20[ 510.614] Current version of pixman: 0.30.0[ 510.615] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version.[ 510.615] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, () notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown.[ 510.618] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jan 5 21:30:54 2015[ 510.625] (==) Using config directory: "/etc/X11/xorg.conf.d"[ 510.625] (==) Using system config directory "/usr/share/X11/xorg.conf.d"[ 510.629] (==) No Layout section. Using the first Screen section.[ 510.630] (==) No screen section available. Using defaults.[ 510.630] (**) |-->Screen "Default Screen Section" (0)[ 510.630] (**) | |-->Monitor "<default monitor>"[ 510.632] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration.[ 510.633] (==) Automatically adding devices[ 510.633] (==) Automatically enabling devices[ 510.633] (==) Automatically adding GPU devices[ 510.633] (==) FontPath set to: catalogue:/etc/X11/fontpath.d, built-ins[ 510.633] (==) ModulePath set to "/usr/lib/xorg/modules"[ 510.634] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices.[ 510.634] (II) Loader magic: 0x1c2e9c[ 510.634] (II) Module ABI versions:[ 510.634] X.Org ANSI C Emulation: 0.4[ 510.634] X.Org Video Driver: 14.1[ 510.635] X.Org XInput driver : 19.2[ 510.635] X.Org Server Extension : 7.0[ 510.636] Initializing built-in extension Generic Event Extension[ 510.637] Initializing built-in extension SHAPE[ 510.637] Initializing built-in extension MIT-SHM[ 510.638] Initializing built-in extension XInputExtension[ 510.638] Initializing built-in extension XTEST[ 510.638] Initializing built-in extension BIG-REQUESTS[ 510.639] Initializing built-in extension SYNC[ 510.639] Initializing built-in extension XKEYBOARD[ 510.640] Initializing built-in extension XC-MISC[ 510.640] Initializing built-in extension XINERAMA[ 510.641] Initializing built-in extension XFIXES[ 510.641] Initializing built-in extension RENDER[ 510.641] Initializing built-in extension RANDR[ 510.642] Initializing built-in extension COMPOSITE[ 510.642] Initializing built-in extension DAMAGE[ 510.643] Initializing built-in extension MIT-SCREEN-SAVER[ 510.643] Initializing built-in extension DOUBLE-BUFFER[ 510.643] Initializing built-in extension RECORD[ 510.644] Initializing built-in extension DPMS[ 510.644] Initializing built-in extension X-Resource[ 510.645] Initializing built-in extension XVideo[ 510.645] Initializing built-in extension XVideo-MotionCompensation[ 510.645] Initializing built-in extension SELinux[ 510.646] Initializing built-in extension XFree86-VidModeExtension[ 510.646] Initializing built-in extension XFree86-DGA[ 510.646] Initializing built-in extension XFree86-DRI[ 510.647] Initializing built-in extension DRI2[ 510.647] (II) LoadModule: "glx"[ 510.649] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so[ 510.652] (II) Module glx: vendor="X.Org Foundation"[ 510.652] compiled for 1.14.4, module version = 1.0.0[ 510.653] ABI class: X.Org Server Extension, version 7.0[ 510.653] (==) AIGLX enabled[ 510.658] Loading extension GLX[ 510.659] (==) Matched modesetting as autoconfigured driver 0[ 510.659] (==) Matched fbdev as autoconfigured driver 1[ 510.660] (==) Assigned the driver to the xf86ConfigLayout[ 510.660] (II) LoadModule: "modesetting"[ 510.663] (WW) Warning, couldn't open module modesetting[ 510.664] (II) UnloadModule: "modesetting"[ 510.664] (II) Unloading modesetting[ 510.664] (EE) Failed to load module "modesetting" (module does not exist, 0)[ 510.664] (II) LoadModule: "fbdev"[ 510.665] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so[ 510.666] (II) Module fbdev: vendor="X.Org Foundation"[ 510.667] compiled for 1.14.2, module version = 0.4.3[ 510.667] Module class: X.Org Video Driver[ 510.667] ABI class: X.Org Video Driver, version 14.1[ 510.668] (II) FBDEV: driver for framebuffer: fbdev[ 510.668] (++) using VT number 1[ 510.669] (WW) Falling back to old probe method for fbdev[ 510.669] (II) Loading sub module "fbdevhw"[ 510.669] (II) LoadModule: "fbdevhw"[ 510.671] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so[ 510.673] (II) Module fbdevhw: vendor="X.Org Foundation"[ 510.673] compiled for 1.14.4, module version = 0.0.2[ 510.673] ABI class: X.Org Video Driver, version 14.1[ 510.674] (II) FBDEV(0): using default device[ 510.674] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support[ 510.675] (II) FBDEV(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 16/16[ 510.675] (==) FBDEV(0): Depth 16, (==) framebuffer bpp 16[ 510.676] (==) FBDEV(0): RGB weight 565[ 510.676] (==) FBDEV(0): Default visual is TrueColor[ 510.676] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)[ 510.676] (II) FBDEV(0): hardware: BCM2708 FB (video memory: 3368kB)[ 510.677] (II) FBDEV(0): checking modes against framebuffer device...[ 510.677] (II) FBDEV(0): checking modes against monitor...[ 510.677] (--) FBDEV(0): Virtual size is 1794x954 (pitch 1794)[ 510.678] (**) FBDEV(0): Built-in mode "current"[ 510.678] (==) FBDEV(0): DPI set to (96, 96)[ 510.678] (II) Loading sub module "fb"[ 510.678] (II) LoadModule: "fb"[ 510.680] (II) Loading /usr/lib/xorg/modules/libfb.so[ 510.684] (II) Module fb: vendor="X.Org Foundation"[ 510.684] compiled for 1.14.4, module version = 1.0.0[ 510.684] ABI class: X.Org ANSI C Emulation, version 0.4[ 510.685] (**) FBDEV(0): using shadow framebuffer[ 510.685] (II) Loading sub module "shadow"[ 510.685] (II) LoadModule: "shadow"[ 510.686] (II) Loading /usr/lib/xorg/modules/libshadow.so[ 510.688] (II) Module shadow: vendor="X.Org Foundation"[ 510.688] compiled for 1.14.4, module version = 1.1.0[ 510.688] ABI class: X.Org ANSI C Emulation, version 0.4[ 510.690] (EE) FBDEV(0): FBIOBLANK: Operation not permitted[ 510.692] (==) FBDEV(0): Backing store disabled[ 510.694] (==) FBDEV(0): DPMS enabled[ 510.694] (==) RandR enabled[ 510.791] (II) SELinux: Disabled on system[ 510.806] (II) AIGLX: Screen 0 is not DRI2 capable[ 510.806] (II) AIGLX: Screen 0 is not DRI capable[ 511.337] (II) AIGLX: Loaded and initialized swrast[ 511.337] (II) GLX: Initialized DRISWRAST GL provider for screen 0[ 511.907] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/event0)[ 511.908] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "evdev keyboard catchall"[ 511.908] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"[ 511.908] (II) LoadModule: "evdev"[ 511.910] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so[ 511.913] (II) Module evdev: vendor="X.Org Foundation"[ 511.914] compiled for 1.14.4, module version = 2.8.4[ 511.914] Module class: X.Org XInput Driver[ 511.914] ABI class: X.Org XInput driver, version 19.2[ 511.914] (II) Using input driver 'evdev' for 'Microsoft Microsoft® 2.4GHz Transceiver v8.0'[ 511.915] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: always reports core events[ 511.915] (**) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Device: "/dev/input/event0"[ 511.916] (--) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Vendor 0x45e Product 0x745[ 511.916] (--) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Found keys[ 511.916] (II) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Configuring as keyboard[ 511.917] (**) Option "config_info" "udev:/sys/devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2:1.0/input/input0/event0"[ 511.917] (II) XINPUT: Adding extended input device "Microsoft Microsoft® 2.4GHz Transceiver v8.0" (type: KEYBOARD, id 6)[ 511.917] (**) Option "xkb_rules" "evdev"[ 511.918] (**) Option "xkb_model" "pc105"[ 511.918] (**) Option "xkb_layout" "pl"[ 511.918] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"[ 512.261] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/event1)[ 512.261] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "evdev pointer catchall"[ 512.261] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "evdev keyboard catchall"[ 512.262] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"[ 512.262] (II) Using input driver 'evdev' for 'Microsoft Microsoft® 2.4GHz Transceiver v8.0'[ 512.262] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: always reports core events[ 512.263] (**) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Device: "/dev/input/event1"[ 512.263] (--) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Vendor 0x45e Product 0x745[ 512.263] (--) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Found 9 mouse buttons[ 512.264] (--) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Found scroll wheel(s)[ 512.264] (--) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Found relative axes[ 512.264] (--) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Found x and y relative axes[ 512.264] (--) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Found absolute axes[ 512.264] (II) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Forcing absolute x/y axes to exist.[ 512.264] (--) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Found keys[ 512.265] (II) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Configuring as mouse[ 512.265] (II) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Configuring as keyboard[ 512.265] (II) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Adding scrollwheel support[ 512.266] (**) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: YAxisMapping: buttons 4 and 5[ 512.266] (**) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200[ 512.266] (**) Option "config_info" "udev:/sys/devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2:1.1/input/input1/event1"[ 512.266] (II) XINPUT: Adding extended input device "Microsoft Microsoft® 2.4GHz Transceiver v8.0" (type: KEYBOARD, id 7)[ 512.267] (**) Option "xkb_rules" "evdev"[ 512.267] (**) Option "xkb_model" "pc105"[ 512.267] (**) Option "xkb_layout" "pl"[ 512.268] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"[ 512.271] (II) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: initialized for relative axes.[ 512.271] (WW) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: ignoring absolute axes.[ 512.273] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: (accel) keeping acceleration scheme 1[ 512.274] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: (accel) acceleration profile 0[ 512.274] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: (accel) acceleration factor: 2.000[ 512.274] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: (accel) acceleration threshold: 4[ 512.280] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/mouse0)[ 512.281] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"[ 512.281] (II) No input driver specified, ignoring this device.[ 512.281] (II) This device may have been added with another device file.[ 512.288] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/event2)[ 512.288] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "evdev keyboard catchall"[ 512.288] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"[ 512.288] (II) Using input driver 'evdev' for 'Microsoft Microsoft® 2.4GHz Transceiver v8.0'[ 512.289] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: always reports core events[ 512.289] (**) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Device: "/dev/input/event2"[ 512.290] (II) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Using mtdev for this device[ 512.291] (--) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Vendor 0x45e Product 0x745[ 512.291] (--) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Found 1 mouse buttons[ 512.292] (--) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Found scroll wheel(s)[ 512.292] (--) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Found relative axes[ 512.292] (--) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Found absolute axes[ 512.292] (--) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Found absolute multitouch axes[ 512.292] (--) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Found x and y absolute axes[ 512.293] (--) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Found keys[ 512.293] (II) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Forcing relative x/y axes to exist.[ 512.293] (II) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Configuring as mouse[ 512.293] (II) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Configuring as keyboard[ 512.293] (II) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Adding scrollwheel support[ 512.294] (**) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: YAxisMapping: buttons 4 and 5[ 512.294] (**) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200[ 512.294] (**) Option "config_info" "udev:/sys/devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2:1.2/input/input2/event2"[ 512.295] (II) XINPUT: Adding extended input device "Microsoft Microsoft® 2.4GHz Transceiver v8.0" (type: KEYBOARD, id 8)[ 512.295] (**) Option "xkb_rules" "evdev"[ 512.295] (**) Option "xkb_model" "pc105"[ 512.295] (**) Option "xkb_layout" "pl"[ 512.296] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"[ 512.299] (II) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: initialized for relative axes.[ 512.299] (WW) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: ignoring absolute axes.[ 512.301] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: (accel) keeping acceleration scheme 1[ 512.301] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: (accel) acceleration profile 0[ 512.302] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: (accel) acceleration factor: 2.000[ 512.302] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: (accel) acceleration threshold: 4[ 512.308] (II) config/udev: Adding input device Microsoft Microsoft® 2.4GHz Transceiver v8.0 (/dev/input/js0)[ 512.308] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"[ 512.308] (II) No input driver specified, ignoring this device.[ 512.308] (II) This device may have been added with another device file.[ 512.382] (EE) FBDEV(0): FBIOBLANK: Operation not permitted[ 532.707] (II) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Close[ 532.708] (II) UnloadModule: "evdev"[ 532.708] (II) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Close[ 532.709] (II) UnloadModule: "evdev"[ 532.709] (II) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Close[ 532.709] (II) UnloadModule: "evdev"[ 532.748] (EE) Server terminated successfully (0). Closing log file. Odnośnik do komentarza Udostępnij na innych stronach More sharing options...
tele Napisano Styczeń 6, 2015 Zgłoszenie Share Napisano Styczeń 6, 2015 [ 510.664] (EE) Failed to load module "modesetting" (module does not exist, 0) Chyba bys musial wylaczyc w grubie by system startowal bez KMS. Odnośnik do komentarza Udostępnij na innych stronach More sharing options...
Mentat Napisano Styczeń 6, 2015 Zgłoszenie Share Napisano Styczeń 6, 2015 Mało mogę pomóc bo ani ekspertem od logów X'ów nie jestem a mój rPi działa w headless mode bo nie mam monitora z hdmi ale: 1) wydaje mi się że kombinowałeś coś z linią komend kernela Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1794 bcm2708_fb.fbheight=954 bcm2708.boardrev=0x10 bcm2708.serial=0x7ad4dc99 smsc95xx.macaddr=B8:27:EB:D4:DC:99 bcm2708.disk_led_gpio=47 bcm2708.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p6 ro rootfstype=ext4 rootwait quiet szczególnie "bcm2708_fb.fbwidth=1794 bcm2708_fb.fbheight=954" 2) powinieneś popatrzeć do katalogu /boot, są tam pliki cmdline.txt (z linia komend dla kernela właśnie) oraz kilka wersji pliku config.txt dla różnych monitorów i wyświetlaczy. Być może musisz dobrać odpowiednią wersję. Odnośnik do komentarza Udostępnij na innych stronach More sharing options...
tomek-fedora10 Napisano Styczeń 6, 2015 Autor Zgłoszenie Share Napisano Styczeń 6, 2015 Mało mogę pomóc bo ani ekspertem od logów X'ów nie jestem a mój rPi działa w headless mode bo nie mam monitora z hdmi ale: 1) wydaje mi się że kombinowałeś coś z linią komend kernela Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1794 bcm2708_fb.fbheight=954 bcm2708.boardrev=0x10 bcm2708.serial=0x7ad4dc99 smsc95xx.macaddr=B8:27:EB:D4:DC:99 bcm2708.disk_led_gpio=47 bcm2708.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p6 ro rootfstype=ext4 rootwait quiet szczególnie "bcm2708_fb.fbwidth=1794 bcm2708_fb.fbheight=954" 2) powinieneś popatrzeć do katalogu /boot, są tam pliki cmdline.txt (z linia komend dla kernela właśnie) oraz kilka wersji pliku config.txt dla różnych monitorów i wyświetlaczy. Być może musisz dobrać odpowiednią wersję. Pkt. 1 nie robiłem z nic z linią komend kernela. Pkt. 2 sprawdzę jutro bo już dzisiaj Raspbiana postawiłem. Jutro przełożę kartę z Pidorą i sprawdzę. Odnośnik do komentarza Udostępnij na innych stronach More sharing options...
Rekomendowane odpowiedzi
Jeśli chcesz dodać odpowiedź, zaloguj się lub zarejestruj nowe konto
Jedynie zarejestrowani użytkownicy mogą komentować zawartość tej strony.
Zarejestruj nowe konto
Załóż nowe konto. To bardzo proste!
Zarejestruj sięZaloguj się
Posiadasz już konto? Zaloguj się poniżej.
Zaloguj się