| Summary: | kde-base/kdm-4.1.3 fails to start on system start | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Serge Ratke <serge.ratke> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | a+gentoobugs |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Serge Ratke
2008-11-10 22:22:47 UTC
After updating from kde-4.0 to kde-4.1 kdm also quit working for me. And, I was able to start kdm manually, but otherwise if I ran the xdm service, I would get xdm. The fix I found in forums was to set these: in /etc/conf.d/xdm DISPLAYMANAGER="kdm" in /etc/env.d/90xsession XSESSION="kde-4.1" starting the xdm service now works to start kdm. i had XSESSION="kde" previously in that config file. now with the kde-4.1 it doesn't work either. here's my xorg.conf
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/OTF"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/75dpi/"
EndSection
Section "Module"
Load "GLcore"
Load "glx"
Load "record"
Load "dri"
Load "dbe"
Load "extmod"
Load "xtrap"
Load "freetype"
# Load "type1"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "de"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
#DisplaySize 470 300 # mm
Identifier "Monitor0"
VendorName "BNQ"
ModelName "BenQ FP222W"
### Comment all HorizSync and VertRefresh values to use DDC:
HorizSync 30.0 - 84.0
VertRefresh 56.0 - 76.0
Option "DPMS"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "SWcursor" # [<bool>]
#Option "Dac6Bit" # [<bool>]
#Option "Dac8Bit" # [<bool>]
#Option "BusType" # [<str>]
#Option "CPPIOMode" # [<bool>]
#Option "CPusecTimeout" # <i>
Option "AGPMode" "4" # <i>
#Option "AGPFastWrite" "True" # [<bool>]
#Option "AGPSize" # <i>
#Option "GARTSize" # <i>
#Option "RingSize" # <i>
#Option "BufferSize" # <i>
#Option "EnableDepthMoves" # [<bool>]
Option "EnablePageFlip" "1" # [<bool>]
#Option "NoBackBuffer" # [<bool>]
#Option "DMAForXv" # [<bool>]
#Option "FBTexPercent" # <i>
#Option "DepthBits" # <i>
#Option "PCIAPERSize" # <i>
Option "AccelDFS" "1" # [<bool>]
#Option "DDCMode" # [<bool>]
#Option "IgnoreEDID" # [<bool>]
#Option "DisplayPriority" # [<str>]
#Option "PanelSize" # [<str>]
#Option "ForceMinDotClock" # <freq>
#Option "ColorTiling" "1" # [<bool>]
#Option "VideoKey" # <i>
#Option "RageTheatreCrystal" # <i>
#Option "RageTheatreTunerPort" # <i>
#Option "RageTheatreCompositePort" # <i>
#Option "RageTheatreSVideoPort" # <i>
#Option "TunerType" # <i>
#Option "RageTheatreMicrocPath" # <str>
#Option "RageTheatreMicrocType" # <str>
#Option "ScalerWidth" # <i>
#Option "RenderAccel" "1" # [<bool>]
#Option "SubPixelOrder" # [<str>]
#Option "ShowCache" # [<bool>]
#Option "DynamicClocks" # [<bool>]
#Option "VGAAccess" # [<bool>]
#Option "ReverseDDC" # [<bool>]
#Option "LVDSProbePLL" # [<bool>]
Option "AccelMethod" "EXA" # <str>
#Option "DRI" # [<bool>]
#Option "ConnectorTable" # <str>
#Option "DefaultConnectorTable" # [<bool>]
#Option "DefaultTMDSPLL" # [<bool>]
#Option "TVDACLoadDetect" # [<bool>]
#Option "ForceTVOut" # [<bool>]
#Option "TVStandard" # <str>
#Option "IgnoreLidStatus" # [<bool>]
Identifier "Card0"
Driver "radeon"
VendorName "ATI Technologies Inc"
BoardName "RV350 AR [Radeon 9600]"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "dri"
Mode 0666
EndSection
Section "Extensions"
Option "Composite" "Enable"
EndSection
You should use the following for KDE-4.1: DISPLAYMANAGER="kdm" XSESSION="kde-4.1" (In reply to comment #0) > (EE) Failed to load module "evdev" (module does not exist, 0) > (EE) No input driver matching `evdev' > (EE) config/hal: NewInputDeviceRequest failed > (EE) Failed to load module "evdev" (module does not exist, 0) > (EE) No input driver matching `evdev' > (EE) config/hal: NewInputDeviceRequest failed Do you have the evdev module? i have those entries in the config files already.
emerging the evdev package and using it in the xorg.conf didn't change anything.
Section "InputDevice"
Identifier "Keyboard0"
# Driver "kbd"
Driver "evdev"
Option "XkbLayout" "de"
EndSection
Now i have this message in the /var/log/Xorg.log:
(EE) Keyboard0: No device specified.
(EE) PreInit returned NULL for "Keyboard0"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
Have you tried moving xorg.conf elsewhere and start X with an empty or non-existent xorg.conf? here's the /var/log/kdm.log content after i moved xorg.conf
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.27-gentoo-r2 i686
Current Operating System: Linux gentoo 2.6.27-gentoo-r2 #7 SMP Sat Nov 1 11:17:37 CET 2008 i686
Build Date: 02 November 2008 09:14:58AM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Nov 12 12:41:49 2008
(EE) Unable to locate/open config file
New driver is "ati"
(==) Using default built-in configuration (30 lines)
(EE) Failed to load module "fbdev" (module does not exist, 0)
(EE) Failed to load module "vesa" (module does not exist, 0)
NTSC PAL
finished output detect: 0
finished output detect: 1
finished output detect: 2
finished all detect
before xf86InitialConfiguration
in RADEONProbeOutputModes
after xf86InitialConfiguration
Entering TV Save
Save TV timing tables
saveTimingTables: reading timing tables
TV Save done
init memmap
init common
init crtc1
init pll1
freq: 146250000
best_freq: 146250000
best_feedback_div: 65
best_ref_div: 6
best_post_div: 2
restore memmap
restore common
restore crtc1
restore pll1
finished PLL1
restore dac
found some more output in /var/log/messages, don't know if it's related Nov 11 11:42:05 gentoo [ 31.162296] X:2130 conflicting memory types e8000000-f0000000 write-combining<->uncached-minus Nov 11 11:42:05 gentoo [ 31.162306] reserve_memtype failed 0xe8000000-0xf0000000, track write-combining, req write-combining Nov 11 11:42:05 gentoo cron[2209]: (CRON) STARTUP (V5.0) Nov 11 11:42:06 gentoo [ 32.497776] X:2130 conflicting memory types e8000000-f0000000 write-combining<->uncached-minus Nov 11 11:42:06 gentoo [ 32.497788] reserve_memtype failed 0xe8000000-0xf0000000, track write-combining, req write-combining Nov 11 11:42:06 gentoo [ 32.499300] X:2241 freeing invalid memtype e8000000-f0000000 Nov 11 11:42:07 gentoo kdm[2116]: X server startup timeout, terminating Nov 11 11:42:07 gentoo [ 33.267460] [drm] Num pipes: 1 Nov 11 11:42:07 gentoo [ 33.343988] X:2130 freeing invalid memtype e8000000-f0000000 maybe this one is more related to my problem (/var/log/messages? Nov 12 13:04:29 gentoo hald[1987]: 13:04:29.883 [I] osspec.c:241: SEQNUM=1097, ACTION=remove, SUBSYSTEM=vc, DEVPATH=/sys/devices/virtual/vc/vcs7, DEVNAME=/dev/vcs7, IFINDEX=0 Nov 12 13:04:29 gentoo hald[1987]: 13:04:29.883 [I] device.c:4476: remove_dev: subsys=vc sysfs_path=/sys/devices/virtual/vc/vcs7 Nov 12 13:04:29 gentoo hald[1987]: 13:04:29.883 [W] device.c:4480: Error removing device Nov 12 13:04:29 gentoo kdm[2061]: X server for display :0 cannot be started, session disabled Nov 12 13:04:29 gentoo hald[1987]: 13:04:29.886 [I] osspec.c:241: SEQNUM=1098, ACTION=remove, SUBSYSTEM=vc, DEVPATH=/sys/devices/virtual/vc/vcsa7, DEVNAME=/dev/vcsa7, IFINDEX=0 Nov 12 13:04:29 gentoo hald[1987]: 13:04:29.886 [I] device.c:4476: remove_dev: subsys=vc sysfs_path=/sys/devices/virtual/vc/vcsa7 Nov 12 13:04:29 gentoo hald[1987]: 13:04:29.886 [W] device.c:4480: Error removing device got it fixed by editing the /usr/share/config/kdm/kdmrc file and raising up the value ServerTimeout from 15 (default) to 60. Found this solution in this thread http://forums.pcbsd.org/viewtopic.php?p=58892&sid=b43e984d5978f2ca36eb067a12851795#p58892 (In reply to comment #10) > got it fixed by editing the /usr/share/config/kdm/kdmrc file and raising up the > value ServerTimeout from 15 (default) to 60. Found this solution in this thread > http://forums.pcbsd.org/viewtopic.php?p=58892&sid=b43e984d5978f2ca36eb067a12851795#p58892 > Thanks for finding out the problem. I've now added a note to pkg_postinst about this. I'll try to add a note in the kde4-guide as well. 15 Nov 2008; Jorge Manuel B. S. Vicetto <jmbsvicetto@gentoo.org> kdm-4.1.3.ebuild: Added a note on the ServerTimeout option in case kdm dies for X taking too long to startup. I have the same issue, but raising ServerTimeout from 15 to 60 (or even 120) didn't solve the problem for me. could you provide more information? such as your xorg log file, kdm log file, dmesg output My apologies. It seems that I had not saved the file after my last edit. Changing ServerTimeout from 15 to 120 in /usr/share/config/kdm/kdmrc did indeed fix this issue for me. It doesn't work with ServerTimeout set to 60 for me though. yeah, for some reason i had to raise the value to 70 in order for kdm to work. weird :/ i had to increase the value of ServerTimeout by 10 again -- now being 80. what's wrong? Why is this bug marked as fixed/resolved? ServerTimeout 120 stopped working for me.. increased to 240 and all is well. |
