Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
KDE wont go past login screen
View unanswered posts
View posts from last 24 hours
View posts from last 7 days

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
rabcor
Apprentice
Apprentice


Joined: 05 Apr 2012
Posts: 200

PostPosted: Wed Dec 26, 2012 6:16 am    Post subject: KDE wont go past login screen Reply with quote

I haven't tried logging in as root, since it says root login is not allowed and i'd rather not be logged in as root anyways.

What happened the first time i tried to login KDE started loading up, and then partway through the loading animations it took me right back to login. otherwise now i mostly just get a black screen with a ticking underscore at the top left corner and then get taken right back to the login screen.

My laptop model is Lenovo Thinkpad T410 with an i5 and an intel intergrated 5700MHD graphics card. i'm running on 4gbs of RAM atm (i want to try to upgrade to 8, but it didn't seem to fond of the 4gb corsair memory sticks i put into it, so im gonna try some other things next)

This is a fresh install. i emerged xorg-x11 and kdebase-meta and cleaning the tmp directory and erasing the kde config file in my user home folder didn't do anything (did save someone else tho)
_________________
This picture was my biggest reason for ever trying Gentoo <3
Back to top
View user's profile Send private message
Unknown-Creation
n00b
n00b


Joined: 25 Nov 2011
Posts: 11

PostPosted: Thu Dec 27, 2012 2:51 am    Post subject: Reply with quote

What are the contents of /var/log/Xorg.0.log ?
Back to top
View user's profile Send private message
rabcor
Apprentice
Apprentice


Joined: 05 Apr 2012
Posts: 200

PostPosted: Thu Dec 27, 2012 3:49 am    Post subject: Reply with quote

double post
_________________
This picture was my biggest reason for ever trying Gentoo <3


Last edited by rabcor on Thu Dec 27, 2012 6:57 am; edited 2 times in total
Back to top
View user's profile Send private message
rabcor
Apprentice
Apprentice


Joined: 05 Apr 2012
Posts: 200

PostPosted: Thu Dec 27, 2012 3:51 am    Post subject: Reply with quote

Xorg.0.log
Code:
[   109.769]
X.Org X Server 1.13.0
Release Date: 2012-09-05
[   109.769] X Protocol Version 11, Revision 0
[   109.769] Build Operating System: Linux 3.6.11-gentoo x86_64 Gentoo
[   109.769] Current Operating System: Linux Knightmare 3.6.11-gentoo #1 SMP PREEMPT Wed Dec 26 05:26:57 Local time zone must be set-- x86_64
[   109.769] Kernel command line: root=/dev/ram0 real_root=/dev/sda6 i915.modeset=1
[   109.769] Build Date: 25 December 2012  02:25:50PM
[   109.769] 
[   109.769] Current version of pixman: 0.28.0
[   109.769]    Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
[   109.769] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   109.769] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Dec 27 04:08:45 2012
[   109.769] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   109.769] (==) No Layout section.  Using the first Screen section.
[   109.769] (==) No screen section available. Using defaults.
[   109.769] (**) |-->Screen "Default Screen Section" (0)
[   109.769] (**) |   |-->Monitor "<default monitor>"
[   109.769] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
[   109.769] (==) Automatically adding devices
[   109.769] (==) Automatically enabling devices
[   109.769] (==) Automatically adding GPU devices
[   109.769] (==) FontPath set to:
   /usr/share/fonts/misc/,
   /usr/share/fonts/TTF/,
   /usr/share/fonts/OTF/,
   /usr/share/fonts/Type1/,
   /usr/share/fonts/100dpi/,
   /usr/share/fonts/75dpi/
[   109.769] (==) ModulePath set to "/usr/lib64/xorg/modules"
[   109.769] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
[   109.769] (II) Loader magic: 0x80dc00
[   109.769] (II) Module ABI versions:
[   109.769]    X.Org ANSI C Emulation: 0.4
[   109.769]    X.Org Video Driver: 13.0
[   109.769]    X.Org XInput driver : 18.0
[   109.769]    X.Org Server Extension : 7.0
[   109.770] (II) config/udev: Adding drm device (/dev/dri/card0)
[   109.772] (--) PCI:*(0:0:2:0) 8086:0046:17aa:215a rev 2, Mem @ 0xf2000000/4194304, 0xd0000000/268435456, I/O @ 0x00001800/8
[   109.772] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[   109.772] Initializing built-in extension Generic Event Extension
[   109.772] Initializing built-in extension SHAPE
[   109.772] Initializing built-in extension MIT-SHM
[   109.772] Initializing built-in extension XInputExtension
[   109.772] Initializing built-in extension XTEST
[   109.772] Initializing built-in extension BIG-REQUESTS
[   109.772] Initializing built-in extension SYNC
[   109.772] Initializing built-in extension XKEYBOARD
[   109.772] Initializing built-in extension XC-MISC
[   109.772] Initializing built-in extension XINERAMA
[   109.772] Initializing built-in extension XFIXES
[   109.772] Initializing built-in extension RENDER
[   109.772] Initializing built-in extension RANDR
[   109.772] Initializing built-in extension COMPOSITE
[   109.772] Initializing built-in extension DAMAGE
[   109.772] Initializing built-in extension MIT-SCREEN-SAVER
[   109.772] Initializing built-in extension DOUBLE-BUFFER
[   109.772] Initializing built-in extension RECORD
[   109.772] Initializing built-in extension DPMS
[   109.772] Initializing built-in extension X-Resource
[   109.772] Initializing built-in extension XVideo
[   109.772] Initializing built-in extension XVideo-MotionCompensation
[   109.772] Initializing built-in extension XFree86-VidModeExtension
[   109.772] Initializing built-in extension XFree86-DGA
[   109.772] Initializing built-in extension XFree86-DRI
[   109.772] Initializing built-in extension DRI2
[   109.772] (II) LoadModule: "glx"
[   109.772] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[   109.772] (II) Module glx: vendor="X.Org Foundation"
[   109.772]    compiled for 1.13.0, module version = 1.0.0
[   109.772]    ABI class: X.Org Server Extension, version 7.0
[   109.772] (==) AIGLX enabled
[   109.772] Loading extension GLX
[   109.772] (==) Matched intel as autoconfigured driver 0
[   109.772] (==) Matched intel as autoconfigured driver 1
[   109.772] (==) Matched vesa as autoconfigured driver 2
[   109.772] (==) Matched modesetting as autoconfigured driver 3
[   109.772] (==) Matched fbdev as autoconfigured driver 4
[   109.772] (==) Assigned the driver to the xf86ConfigLayout
[   109.772] (II) LoadModule: "intel"
[   109.772] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
[   109.772] (II) Module intel: vendor="X.Org Foundation"
[   109.772]    compiled for 1.13.0, module version = 2.20.13
[   109.772]    Module class: X.Org Video Driver
[   109.772]    ABI class: X.Org Video Driver, version 13.0
[   109.772] (II) LoadModule: "vesa"
[   109.773] (WW) Warning, couldn't open module vesa
[   109.773] (II) UnloadModule: "vesa"
[   109.773] (II) Unloading vesa
[   109.773] (EE) Failed to load module "vesa" (module does not exist, 0)
[   109.773] (II) LoadModule: "modesetting"
[   109.773] (WW) Warning, couldn't open module modesetting
[   109.773] (II) UnloadModule: "modesetting"
[   109.773] (II) Unloading modesetting
[   109.773] (EE) Failed to load module "modesetting" (module does not exist, 0)
[   109.773] (II) LoadModule: "fbdev"
[   109.773] (WW) Warning, couldn't open module fbdev
[   109.773] (II) UnloadModule: "fbdev"
[   109.773] (II) Unloading fbdev
[   109.773] (EE) Failed to load module "fbdev" (module does not exist, 0)
[   109.773] (II) intel: Driver for Intel 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, B43, Clarkdale, Arrandale,
   Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
   Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
   Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
   Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
   Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
   Ivybridge Server (GT2), Haswell Desktop (GT1), Haswell Desktop (GT2),
   Haswell Desktop (GT2+), Haswell Mobile (GT1), Haswell Mobile (GT2),
   Haswell Mobile (GT2+), Haswell Server (GT1), Haswell Server (GT2),
   Haswell Server (GT2+), Haswell SDV Desktop (GT1),
   Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT2+),
   Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
   Haswell SDV Mobile (GT2+), Haswell SDV Server (GT1),
   Haswell SDV Server (GT2), Haswell SDV Server (GT2+),
   Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
   Haswell ULT Desktop (GT2+), Haswell ULT Mobile (GT1),
   Haswell ULT Mobile (GT2), Haswell ULT Mobile (GT2+),
   Haswell ULT Server (GT1), Haswell ULT Server (GT2),
   Haswell ULT Server (GT2+), Haswell CRW Desktop (GT1),
   Haswell CRW Desktop (GT2), Haswell CRW Desktop (GT2+),
   Haswell CRW Mobile (GT1), Haswell CRW Mobile (GT2),
   Haswell CRW Mobile (GT2+), Haswell CRW Server (GT1),
   Haswell CRW Server (GT2), Haswell CRW Server (GT2+),
   ValleyView PO board
[   109.773] (++) using VT number 7

[   109.773] (II) intel(0): using device path '/dev/dri/card0'
[   109.774] (II) intel(0): Creating default Display subsection in Screen section
   "Default Screen Section" for depth/fbbpp 24/32
[   109.774] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[   109.774] (==) intel(0): RGB weight 888
[   109.774] (==) intel(0): Default visual is TrueColor
[   109.774] (--) intel(0): Integrated Graphics Chipset: Intel(R) Arrandale
[   109.774] (**) intel(0): Framebuffer tiled
[   109.774] (**) intel(0): Pixmaps tiled
[   109.774] (**) intel(0): 3D buffers tiled
[   109.774] (**) intel(0): Throttling enabled
[   109.774] (**) intel(0): Delayed flush enabled
[   109.774] (**) intel(0): "Tear free" disabled
[   109.774] (**) intel(0): Forcing per-crtc-pixmaps? no
[   109.774] (II) intel(0): Output LVDS1 has no monitor section
[   109.774] (--) intel(0): found backlight control interface acpi_video0 (type 'firmware')
[   109.778] (II) intel(0): Output VGA1 has no monitor section
[   109.794] (II) intel(0): Output HDMI1 has no monitor section
[   109.818] (II) intel(0): Output DP1 has no monitor section
[   109.822] (II) intel(0): Output HDMI2 has no monitor section
[   109.826] (II) intel(0): Output HDMI3 has no monitor section
[   109.850] (II) intel(0): Output DP2 has no monitor section
[   109.874] (II) intel(0): Output DP3 has no monitor section
[   109.874] (II) intel(0): EDID for output LVDS1
[   109.874] (II) intel(0): Manufacturer: LEN  Model: 4036  Serial#: 0
[   109.874] (II) intel(0): Year: 2009  Week: 1
[   109.874] (II) intel(0): EDID Version: 1.3
[   109.874] (II) intel(0): Digital Display Input
[   109.874] (II) intel(0): Max Image Size [cm]: horiz.: 30  vert.: 19
[   109.874] (II) intel(0): Gamma: 2.20
[   109.874] (II) intel(0): DPMS capabilities: StandBy Suspend Off
[   109.874] (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[   109.874] (II) intel(0): First detailed timing is preferred mode
[   109.874] (II) intel(0): redX: 0.593 redY: 0.343   greenX: 0.339 greenY: 0.566
[   109.874] (II) intel(0): blueX: 0.147 blueY: 0.125   whiteX: 0.313 whiteY: 0.329
[   109.874] (II) intel(0): Manufacturer's mask: 0
[   109.874] (II) intel(0): Supported detailed timing:
[   109.874] (II) intel(0): clock: 101.3 MHz   Image Size:  303 x 189 mm
[   109.874] (II) intel(0): h_active: 1440  h_sync: 1488  h_sync_end 1520 h_blank_end 1834 h_border: 0
[   109.874] (II) intel(0): v_active: 900  v_sync: 903  v_sync_end 909 v_blanking: 920 v_border: 0
[   109.874] (II) intel(0): Supported detailed timing:
[   109.874] (II) intel(0): clock: 101.3 MHz   Image Size:  303 x 189 mm
[   109.874] (II) intel(0): h_active: 1440  h_sync: 1488  h_sync_end 1520 h_blank_end 1904 h_border: 0
[   109.874] (II) intel(0): v_active: 900  v_sync: 903  v_sync_end 909 v_blanking: 1064 v_border: 0
[   109.874] (II) intel(0): Unknown vendor-specific block f
[   109.874] (II) intel(0):  B141PW04 V0
[   109.874] (II) intel(0): EDID (in hex):
[   109.874] (II) intel(0):    00ffffffffffff0030ae364000000000
[   109.874] (II) intel(0):    01130103801e1378eafcc59757569125
[   109.874] (II) intel(0):    20505400000001010101010101010101
[   109.874] (II) intel(0):    0101010101019227a08a518414303020
[   109.874] (II) intel(0):    36002fbd100000189127a0d05184a430
[   109.874] (II) intel(0):    302036002fbd100000180000000f0095
[   109.874] (II) intel(0):    0a32950a2816090006af5630000000fe
[   109.874] (II) intel(0):    004231343150573034205630200a0045
[   109.874] (II) intel(0): EDID vendor "LEN", prod id 16438
[   109.874] (II) intel(0): Printing DDC gathered Modelines:
[   109.874] (II) intel(0): Modeline "1440x900"x0.0  101.30  1440 1488 1520 1834  900 903 909 920 -hsync -vsync (55.2 kHz eP)
[   109.874] (II) intel(0): Modeline "1440x900"x0.0  101.29  1440 1488 1520 1904  900 903 909 1064 -hsync -vsync (53.2 kHz e)
[   109.874] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
[   109.874] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[   109.874] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[   109.874] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
[   109.874] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
[   109.874] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
[   109.874] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
[   109.874] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
[   109.874] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
[   109.874] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
[   109.874] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
[   109.874] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported)
[   109.874] (II) intel(0): Printing probed modes for output LVDS1
[   109.874] (II) intel(0): Modeline "1440x900"x60.0  101.30  1440 1488 1520 1834  900 903 909 920 -hsync -vsync (55.2 kHz eP)
[   109.874] (II) intel(0): Modeline "1440x900"x50.0  101.29  1440 1488 1520 1904  900 903 909 1064 -hsync -vsync (53.2 kHz e)
[   109.874] (II) intel(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz d)
[   109.874] (II) intel(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz d)
[   109.874] (II) intel(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz d)
[   109.874] (II) intel(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz d)
[   109.878] (II) intel(0): EDID for output VGA1
[   109.894] (II) intel(0): EDID for output HDMI1
[   109.918] (II) intel(0): EDID for output DP1
[   109.922] (II) intel(0): EDID for output HDMI2
[   109.926] (II) intel(0): EDID for output HDMI3
[   109.950] (II) intel(0): EDID for output DP2
[   109.974] (II) intel(0): EDID for output DP3
[   109.974] (II) intel(0): Output LVDS1 connected
[   109.974] (II) intel(0): Output VGA1 disconnected
[   109.974] (II) intel(0): Output HDMI1 disconnected
[   109.974] (II) intel(0): Output DP1 disconnected
[   109.974] (II) intel(0): Output HDMI2 disconnected
[   109.974] (II) intel(0): Output HDMI3 disconnected
[   109.974] (II) intel(0): Output DP2 disconnected
[   109.974] (II) intel(0): Output DP3 disconnected
[   109.974] (II) intel(0): Using exact sizes for initial modes
[   109.974] (II) intel(0): Output LVDS1 using initial mode 1440x900
[   109.974] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[   109.974] (**) intel(0): Display dimensions: (300, 190) mm
[   109.974] (**) intel(0): DPI set to (121, 120)
[   109.974] (II) Loading sub module "dri2"
[   109.974] (II) LoadModule: "dri2"
[   109.974] (II) Module "dri2" already built-in
[   109.974] (==) Depth 24 pixmap format is 32 bpp
[   109.974] (II) intel(0): SNA initialized with Ironlake backend
[   109.974] (==) intel(0): Backing store disabled
[   109.974] (==) intel(0): Silken mouse enabled
[   109.974] (II) intel(0): HW Cursor enabled
[   109.974] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[   109.976] (==) intel(0): DPMS enabled
[   109.976] (II) intel(0): [DRI2] Setup complete
[   109.976] (II) intel(0): [DRI2]   DRI driver: i965
[   109.976] (II) intel(0): direct rendering: DRI2 Enabled
[   109.976] (==) intel(0): hotplug detection: "enabled"
[   109.976] (--) RandR disabled
[   109.983] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[   109.983] (II) AIGLX: enabled GLX_INTEL_swap_event
[   109.983] (II) AIGLX: enabled GLX_ARB_create_context
[   109.983] (II) AIGLX: enabled GLX_ARB_create_context_profile
[   109.983] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[   109.983] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[   109.983] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[   109.983] (II) AIGLX: Loaded and initialized i965
[   109.983] (II) GLX: Initialized DRI2 GL provider for screen 0
[   109.983] (II) intel(0): switch to mode 1440x900 on crtc 3 (pipe 0)
[   110.010] (II) intel(0): Setting screen physical size to 381 x 238
[   110.142] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[   110.142] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[   110.142] (II) LoadModule: "evdev"
[   110.142] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
[   110.142] (II) Module evdev: vendor="X.Org Foundation"
[   110.142]    compiled for 1.13.0, module version = 2.7.3
[   110.142]    Module class: X.Org XInput Driver
[   110.142]    ABI class: X.Org XInput driver, version 18.0
[   110.142] (II) Using input driver 'evdev' for 'Power Button'
[   110.142] (**) Power Button: always reports core events
[   110.142] (**) evdev: Power Button: Device: "/dev/input/event2"
[   110.142] (--) evdev: Power Button: Vendor 0 Product 0x1
[   110.142] (--) evdev: Power Button: Found keys
[   110.142] (II) evdev: Power Button: Configuring as keyboard
[   110.142] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[   110.142] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[   110.142] (**) Option "xkb_rules" "evdev"
[   110.142] (**) Option "xkb_model" "evdev"
[   110.142] (**) Option "xkb_layout" "us"
[   110.164] (II) config/udev: Adding input device Video Bus (/dev/input/event7)
[   110.164] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[   110.164] (II) Using input driver 'evdev' for 'Video Bus'
[   110.164] (**) Video Bus: always reports core events
[   110.164] (**) evdev: Video Bus: Device: "/dev/input/event7"
[   110.164] (--) evdev: Video Bus: Vendor 0 Product 0x6
[   110.164] (--) evdev: Video Bus: Found keys
[   110.164] (II) evdev: Video Bus: Configuring as keyboard
[   110.164] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input7/event7"
[   110.164] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[   110.164] (**) Option "xkb_rules" "evdev"
[   110.164] (**) Option "xkb_model" "evdev"
[   110.164] (**) Option "xkb_layout" "us"
[   110.165] (II) config/udev: Adding input device Lid Switch (/dev/input/event0)
[   110.165] (II) No input driver specified, ignoring this device.
[   110.165] (II) This device may have been added with another device file.
[   110.165] (II) config/udev: Adding input device Sleep Button (/dev/input/event1)
[   110.165] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[   110.165] (II) Using input driver 'evdev' for 'Sleep Button'
[   110.165] (**) Sleep Button: always reports core events
[   110.165] (**) evdev: Sleep Button: Device: "/dev/input/event1"
[   110.165] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[   110.165] (--) evdev: Sleep Button: Found keys
[   110.165] (II) evdev: Sleep Button: Configuring as keyboard
[   110.165] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input1/event1"
[   110.165] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[   110.165] (**) Option "xkb_rules" "evdev"
[   110.165] (**) Option "xkb_model" "evdev"
[   110.165] (**) Option "xkb_layout" "us"
[   110.165] (II) config/udev: Adding drm device (/dev/dri/card0)
[   110.166] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event3)
[   110.166] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[   110.166] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[   110.166] (**) AT Translated Set 2 keyboard: always reports core events
[   110.166] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event3"
[   110.166] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[   110.166] (--) evdev: AT Translated Set 2 keyboard: Found keys
[   110.166] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[   110.166] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input3/event3"
[   110.166] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
[   110.166] (**) Option "xkb_rules" "evdev"
[   110.166] (**) Option "xkb_model" "evdev"
[   110.166] (**) Option "xkb_layout" "us"
[   110.166] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event4)
[   110.166] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[   110.166] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[   110.166] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
[   110.166] (II) LoadModule: "synaptics"
[   110.166] (II) Loading /usr/lib64/xorg/modules/input/synaptics_drv.so
[   110.166] (II) Module synaptics: vendor="X.Org Foundation"
[   110.166]    compiled for 1.13.0, module version = 1.6.2
[   110.166]    Module class: X.Org XInput Driver
[   110.166]    ABI class: X.Org XInput driver, version 18.0
[   110.166] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[   110.166] (**) SynPS/2 Synaptics TouchPad: always reports core events
[   110.166] (**) Option "Device" "/dev/input/event4"
[   110.192] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
[   110.192] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5888
[   110.192] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4820
[   110.192] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[   110.192] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[   110.192] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
[   110.192] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[   110.192] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[   110.192] (**) SynPS/2 Synaptics TouchPad: always reports core events
[   110.202] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input4/event4"
[   110.202] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 10)
[   110.202] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[   110.202] (**) synaptics: SynPS/2 Synaptics TouchPad: MaxSpeed is now 1.75
[   110.202] (**) synaptics: SynPS/2 Synaptics TouchPad: AccelFactor is now 0.036
[   110.202] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[   110.202] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[   110.202] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[   110.202] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[   110.202] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[   110.202] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[   110.202] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
[   110.202] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/event5)
[   110.202] (**) TPPS/2 IBM TrackPoint: Applying InputClass "evdev pointer catchall"
[   110.202] (II) Using input driver 'evdev' for 'TPPS/2 IBM TrackPoint'
[   110.202] (**) TPPS/2 IBM TrackPoint: always reports core events
[   110.202] (**) evdev: TPPS/2 IBM TrackPoint: Device: "/dev/input/event5"
[   110.202] (--) evdev: TPPS/2 IBM TrackPoint: Vendor 0x2 Product 0xa
[   110.202] (--) evdev: TPPS/2 IBM TrackPoint: Found 3 mouse buttons
[   110.202] (--) evdev: TPPS/2 IBM TrackPoint: Found relative axes
[   110.202] (--) evdev: TPPS/2 IBM TrackPoint: Found x and y relative axes
[   110.202] (II) evdev: TPPS/2 IBM TrackPoint: Configuring as mouse
[   110.202] (**) evdev: TPPS/2 IBM TrackPoint: YAxisMapping: buttons 4 and 5
[   110.202] (**) evdev: TPPS/2 IBM TrackPoint: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[   110.202] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/serio2/input/input5/event5"
[   110.202] (II) XINPUT: Adding extended input device "TPPS/2 IBM TrackPoint" (type: MOUSE, id 11)
[   110.203] (II) evdev: TPPS/2 IBM TrackPoint: initialized for relative axes.
[   110.203] (**) TPPS/2 IBM TrackPoint: (accel) keeping acceleration scheme 1
[   110.203] (**) TPPS/2 IBM TrackPoint: (accel) acceleration profile 0
[   110.203] (**) TPPS/2 IBM TrackPoint: (accel) acceleration factor: 2.000
[   110.203] (**) TPPS/2 IBM TrackPoint: (accel) acceleration threshold: 4
[   110.203] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/mouse1)
[   110.203] (II) No input driver specified, ignoring this device.
[   110.203] (II) This device may have been added with another device file.
[   110.203] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
[   110.203] (II) No input driver specified, ignoring this device.
[   110.203] (II) This device may have been added with another device file.
[   116.028] (II) AIGLX: Suspending AIGLX clients for VT switch


kdm.log
Code:
********************************************************************************
Note that your system uses syslog. All of kdm's internally generated messages
(i.e., not from libraries and external programs/scripts it uses) go to the
daemon.* syslog facility; check your syslog configuration to find out to which
file(s) it is logged. PAM logs messages related to authentication to authpriv.*.
********************************************************************************

Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
klauncher(13091) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(13085)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed:  "Not connected to D-Bus server"

kdmgreet(13085)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
Server terminated successfully (0). Closing log file.
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
klauncher(13221) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(13215)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed:  "Not connected to D-Bus server"

kdmgreet(13215)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
Server terminated successfully (0). Closing log file.
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
klauncher(13277) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(13271)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed:  "Not connected to D-Bus server"

kdmgreet(13271)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned

Dbus is confirmed installed, and set to start at boot.

Edit 1: I did some googling and found this. testing that now. emerging sqlite didn't seem to do much, installing the other things (plasma-runtime) i saw it wants to install qt-webkit 4, i had to unemerge it when i installed chromium earlier but forgot to confirm that chromium had reinstalled it. this may have been the problem. waiting to make sure.

Edit 2: still not fixed, no visible change. emerging krunner and plasma-workspace. still not fixed and kdm gives same error.

Edit 3: shocking realization, i got a Buffer I/O error on my root partition and it said that the ext4 fs detected aborted journal.

i wonder if my partitions somehow got corrupt... that is pretty odd. I/O error to superblock detected... and then it remounted the filesystem to read-only which locked up my system of course... any idea what might have caused this? to my knowledge my HDD has worked perfectly fine so far, its not old either. i ran the livecd and ran
Code:
fsck.ext4 -cDfty -C 0 /dev/sda6
which went through perfectly fine, this didn't help at all btw.
_________________
This picture was my biggest reason for ever trying Gentoo <3
Back to top
View user's profile Send private message
wfahren
n00b
n00b


Joined: 04 Aug 2007
Posts: 32

PostPosted: Fri Dec 28, 2012 4:42 am    Post subject: Reply with quote

Did you start consolekit?

If you have consolekit USE flag for KDM you need to start it.

$ equery h consolekit
* Searching for USE flag consolekit ...
[IP-] [ ] kde-base/kdm-4.9.3:4
[IP-] [ ] net-wireless/bluez-4.99:0
[IP-] [ ] sys-auth/pambase-20101024-r2:0
Back to top
View user's profile Send private message
rabcor
Apprentice
Apprentice


Joined: 05 Apr 2012
Posts: 200

PostPosted: Fri Dec 28, 2012 5:18 am    Post subject: Reply with quote

I emerged consolekit and added it to default runlevel.
nothing changed.
_________________
This picture was my biggest reason for ever trying Gentoo <3
Back to top
View user's profile Send private message
The Doctor
Moderator
Moderator


Joined: 27 Jul 2010
Posts: 2678

PostPosted: Fri Dec 28, 2012 5:21 am    Post subject: Reply with quote

rabcor, you may want to do a more complete test. smartmontools can help with that.

One test is to log in on the command line and use startkde and see if that is successful. It may help narrow the problem space.

EDIT
What profile are you using? consolekit should have been forced for kdm using the kde profile... (KDE works without consolekit, but upstream requires it to support the release.)
_________________
First things first, but not necessarily in that order.

Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box.
Back to top
View user's profile Send private message
rabcor
Apprentice
Apprentice


Joined: 05 Apr 2012
Posts: 200

PostPosted: Fri Dec 28, 2012 7:05 am    Post subject: Reply with quote

i'm using the KDE profile, i even double checked that recently. but i will be trying that smartmon thing you recommended in a bit.
_________________
This picture was my biggest reason for ever trying Gentoo <3
Back to top
View user's profile Send private message
acidrums4
Tux's lil' helper
Tux's lil' helper


Joined: 05 Feb 2009
Posts: 147
Location: Al otro lado del monitor

PostPosted: Fri Dec 28, 2012 1:05 pm    Post subject: Reply with quote

I'm having the same issue but is because I have a broken installation of Qt-Webkit (see https://forums.gentoo.org/viewtopic-t-946090.html). Have you checked you have a sane installation of Qt-libraries and KDE core packages?
Back to top
View user's profile Send private message
wfahren
n00b
n00b


Joined: 04 Aug 2007
Posts: 32

PostPosted: Fri Dec 28, 2012 3:27 pm    Post subject: Reply with quote

How about trying this - will rebuild the xorg server and drivers.
This has worked for me a couple of times. (remove the "p" of course to actually rebuild)

emerge -1p $(qlist -IC x11-drivers xorg)

BTY I have the same dbus error in my kdm.log and I'm working fine. Might look at your .xsession-errors to see if there is any clue in there.

klauncher(10547) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
Back to top
View user's profile Send private message
rabcor
Apprentice
Apprentice


Joined: 05 Apr 2012
Posts: 200

PostPosted: Sat Dec 29, 2012 6:16 pm    Post subject: Reply with quote

thanks a lot for your input guys i'll definetly be keeping track of that qt thread.

wfahren i'm unsure if your recommendation helped at all or not, but certainly a good thing to know, i was able to log in to kde by typing startx, and then startkde in X.

It loaded just fine

If i however start kdm (or i think thats what you call it)

and login to my user account, i still just go back to the login screen.

now i pulled a little experiment, i logged in from the console to my user account, and did the same thing, now it loads KDE just like i'd expect it to. :O

that is odd.
_________________
This picture was my biggest reason for ever trying Gentoo <3
Back to top
View user's profile Send private message
wfahren
n00b
n00b


Joined: 04 Aug 2007
Posts: 32

PostPosted: Sat Dec 29, 2012 6:44 pm    Post subject: Reply with quote

Was playing with this and was able to simulate your problem. By stopping consolekit and trying to login in.

From your kdm.log
kdeinit4: Communication error with launcher. Exiting!

Seems to be something wrong with KDM, since startkde works right?

I was able to start KDE by selecting "KDE Plasma Workspace (failsafe session)" From the kdm session select drop down. Logged back out then selected without failsafe that worked too. Will play with it and see if I can find why it does that. There must be a temp file somewhere that stores your last kdm session selection. I think if I would have just selected "KDE Plasma it would have worked too????
Back to top
View user's profile Send private message
wfahren
n00b
n00b


Joined: 04 Aug 2007
Posts: 32

PostPosted: Sun Dec 30, 2012 4:37 am    Post subject: Reply with quote

rabcor - played around a bit with KDM....hope this sheds some light on know it works.

There is some good documentation in the KDE Help Center under [Control Center Modules --> Login Screen] about KDM. That is where I found some of this information.

Since KDM is just a graphical interface that prompts for login (username) and password, authenticates the user and starts a “session”. Most of the work behind it is still shell scripts. The directory where gentoo installs the startup/shutdown scripts and configuration files is in /usr/share/config/kdm.

Code:
/usr/share/config/kdm $ ls -l
total 96
-rw-r--r-- 1 root root   674 Dec 29 20:03 README
-rw-r--r-- 1 root root  1924 Dec 29 20:03 Xaccess
-rwxr-xr-x 1 root root   318 Dec 29 20:03 Xreset
-rwxr-xr-x 1 root root  2290 Dec 29 20:03 Xsession
-rwxr-xr-x 1 root root   160 Dec 29 20:03 Xsetup
-rwxr-xr-x 1 root root   598 Dec 29 20:03 Xstartup
-rwxr-xr-x 1 root root   285 Dec 29 20:03 Xwilling
-rw-r--r-- 1 root root   318 Dec 29 20:03 backgroundrc
-rw-r--r-- 1 root root 22708 Dec 29 20:03 kdmrc
drwxr-xr-x 2 root root  4096 Dec 29 20:03 sessions

Most are not used only the Xsession (picks the shell you are using and the windows manager to use KDE in this case passed by KDM which is default) and kdmrc (most of the option are configurable under the systemsettings Login Screen) don't mess with the Xsession script and you shouldn't need to modify anything in the kdmrc unless you want to use XDMCP remote X access control (headless systems)...I have two that I use that for, so I have modified that manually.

If you supect something wrong with the scripts or kdmrc file you can rebuild all the files to default in /usr/share/config/kdm by using genkdmconf use the help option to get a list of options.
Code:
genkdmconf --help

If you do a
Code:
genkdmconf --no-old

it will rebuild all the files and make a backup of the old, so safe to do.

Couple of other undocumented things:

The previous selected session (ie windows manger) is stored in $HOME/.dmrc
Code:
$ cat ~/.dmrc
[Desktop]
Session=default

Since it is by user it will change depending on the user ID you input in the login screen. It will show (pervious) behind the session manager option in the pull down menu. I'm guessing that is where your problem is. The wrong session manger was selected or something was wrong with starkde...which you already tested.

Second undocumented thing I found was where the errors are logged (pointed out in a previous post).

If you look at the ~/.xsession-errors log file (option in kdmrc) you will see messages about the session. If you don't have xtrem installed and you select failsafe it will return you to the KDM login screen and put an error in the ~/.xsession-error telling you it couldn't find xterm. If you installed xterm it will load xterm in the window, good why to test Xorg, just type exit and it will return you to the KDM login screen.


One last thing.........

To test KDE without KDM you can use

Code:
xinit `which startkde`
or
xinit /usr/bin/startkde


little easier that startx then starkde, but as you know both ways work.

Happy hacking :)
Back to top
View user's profile Send private message
rabcor
Apprentice
Apprentice


Joined: 05 Apr 2012
Posts: 200

PostPosted: Thu Jan 03, 2013 3:17 pm    Post subject: Reply with quote

Thanks immensely for your help wfahren. i tried doing the same stuff as you did, (start in failsafe session then go to a non-failsafe plasma workspace session) and now default which as you said is previous session works great, it makes me feel kindof stupid not to have figured out to go to a failsafe session (altho i am pretty damn sure that i did at one point try that but it just crashed, don't know what happened inbetween but well...)

I took a break from solving this issue since i really didn't need to have my laptop set up until school starts which is roughly a week from right now, but i decided now would be the time to start to be on the safe side so it'll definetly be ready when school starts.

Now with the issue solved thanks again wfahren for your help! and i'm pretty sure that info on kde you gave me will also be of use to me later and at least now i understand KDM better. :D
_________________
This picture was my biggest reason for ever trying Gentoo <3
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
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 vote in polls in this forum