[SOLVED] Display manager, GRUB and NTFS

Hello people
Yesterday I spent whole day on installling and configuring my arch but i still have 3 problems.
1st and most important is GRUB, i wanted to dual boot with windows vista, i have windows vista installed on another partition but now, after i installed arch, it doesnt show on GRUB. How can i solve that problem, i really need it because my family is not using linux.
2. I cant make the Display manager work, i could install xdm but when i type username and password it redirects to the same xdm. BTW, i followed the documentation from arch's website.
3. I can not open NTFS partitions, i have installed something called ntfs-3g but didn't help.
Thanks for help.:)
Btw, i need a network manager so it will connect to wifi network automatically like in ubuntu or windows, i dont want to do "iwconfig ..." evey time ...
Last edited by khajvah (2012-04-23 10:43:18)

DSpider wrote:
There's a wiki on XDM, with a very relevant entry to your problem: https://wiki.archlinux.org/index.php/XD … fter_login
But why use a display manager at all if you're the only one in your family using Linux? To keep away the plebeians?
https://wiki.archlinux.org/index.php/Start_X_at_Boot
Thank you very much, now i have windows and i dont care about display manager
I think you're confusing it with a bootloader.
- A display manager lets you choose a user, and depending on the manager perhaps even a desktop environment (GNOME, KDE, Xfce, etc) or a window manager (Openbox, xmonad, awesome, etc).
- A bootloader lets you choose which operating system you want to start.
Yeah, i meant, now, nobody from my family will call me and say "WTF have you done with the computer ", bc i am the only one who uses computer not only for inet. Now, they will use windows:)

Similar Messages

  • [SOLVED] Display manager

    I am new to Arch. I have installed Arch, X, Mate (as the DE) and Lightdm as the display manager.  Lightdm will only start in X, with the sudo lightdm command. From there, you can get into Mate.
    Mate seems to work just fine. However, it would be nice to be able to boot successfully to a display manager and then into a desktop environment.
    Before Lightdm, I had installed gdm with xfce. Gdm starts up properly but will not properly start either xfce or Mate. Gdm goes to a screen that is akin to the login screen but with nothing else. I just tried slim, which will not start up, either on boot up or from x.
    I am not sure what to post for logs on this. In any event, my computer is an old Dell Dimension 2400, with a pentium 4 processor, intel graphics and 2 gb of memory. I am not sure what log would be helpful here but, if someone could help me with my issue, it would be appreciated.
    My x-0-greeter.log reads:
    ** (process:290): WARNING **: Failed to open CK session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
    (lightdm-gtk-greeter:331): GLib-CRITICAL **: g_shell_parse_argv: assertion `command_line != NULL' failed
    ** (lightdm-gtk-greeter:331): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/remote-sessions': No such file or directory
    ** (lightdm-gtk-greeter:331): WARNING **: Failed to load user image: Failed to open file '/home/allen/.face': Permission denied
    ** (lightdm-gtk-greeter:331): WARNING **: Could not get accounts property XKeyboardLayouts
    ** (lightdm-gtk-greeter:331): WARNING **: Could not get accounts property XHasMessages
    (lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_get_type: assertion `value != NULL' failed
    (lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion `g_variant_type_check (type)' failed
    (lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_get_type_string: assertion `value != NULL' failed
    ** (lightdm-gtk-greeter:331): WARNING **: Unexpected accounts property type for XHasMessages: (null)
    (lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_unref: assertion `value != NULL' failed
    ** (lightdm-gtk-greeter:331): WARNING **: Could not get accounts property XKeyboardLayouts
    ** (lightdm-gtk-greeter:331): WARNING **: Could not get accounts property XHasMessages
    (lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_get_type: assertion `value != NULL' failed
    (lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion `g_variant_type_check (type)' failed
    (lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_get_type_string: assertion `value != NULL' failed
    ** (lightdm-gtk-greeter:331): WARNING **: Unexpected accounts property type for XHasMessages: (null)
    (lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_unref: assertion `value != NULL' failed
    That seems to include some errors. The x-0.log reads:
    X.Org X Server 1.14.2
    Release Date: 2013-06-25
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 3.9.7-1-ARCH i686
    Current Operating System: Linux archbox 3.9.9-1-ARCH #1 SMP PREEMPT Wed Jul 3 22:52:05 CEST 2013 i686
    Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=5eec6b5e-dd19-4f9d-8e3b-39b950052c48 ro quiet
    Build Date: 01 July 2013 10:52:25AM
    Current version of pixman: 0.30.0
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    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 Jul 24 22:13:55 2013
    (==) Using config directory: "/etc/X11/xorg.conf.d"
    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 SECURITY
    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
    (II) AIGLX: Suspending AIGLX clients for VT switch
    setversion 1.4 failed
    The lightdm.log reads:
    [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
    [+0.00s] DEBUG: Starting Light Display Manager 1.6.0, UID=0 PID=532
    [+0.00s] DEBUG: Loaded configuration from /etc/lightdm/lightdm.conf
    [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
    [+0.00s] DEBUG: Using Xephyr for X servers
    [+0.00s] DEBUG: Registered seat module xlocal
    [+0.00s] DEBUG: Registered seat module xremote
    [+0.00s] DEBUG: Adding default seat
    [+0.00s] DEBUG: Starting seat
    [+0.00s] DEBUG: Starting new display for greeter
    [+0.00s] DEBUG: Starting local X display
    [+0.02s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)
    [+0.02s] DEBUG: Using VT 7
    [+0.02s] DEBUG: Activating VT 7
    [+0.03s] DEBUG: Logging to /var/log/lightdm/x-2.log
    [+0.03s] DEBUG: Writing X server authority to /run/lightdm/root/:2
    [+0.03s] DEBUG: Launching X Server
    [+0.03s] DEBUG: Launching process 536: /usr/bin/Xephyr :2 -auth /run/lightdm/root/:2 -nolisten tcp vt7 -novtswitch
    [+0.06s] DEBUG: Waiting for ready signal from X server :2
    [+0.06s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
    [+0.06s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
    The log from slim reads:
    slim: waiting for X server to begin accepting connections.
    slim: pam_authentication(): Authentication failure
    slim: waiting for X server to shut down
    slim: waiting for X server to begin accepting connections.
    The xorg.0.log reads:
    [ 6.928]
    X.Org X Server 1.14.2
    Release Date: 2013-06-25
    [ 6.928] X Protocol Version 11, Revision 0
    [ 6.928] Build Operating System: Linux 3.9.7-1-ARCH i686
    [ 6.928] Current Operating System: Linux archbox 3.9.9-1-ARCH #1 SMP PREEMPT Wed Jul 3 22:52:05 CEST 2013 i686
    [ 6.929] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=5eec6b5e-dd19-4f9d-8e3b-39b950052c48 ro quiet
    [ 6.929] Build Date: 01 July 2013 10:52:25AM
    [ 6.929]
    [ 6.929] Current version of pixman: 0.30.0
    [ 6.929] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 6.929] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 6.929] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul 24 22:13:55 2013
    [ 6.958] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 6.978] (==) No Layout section. Using the first Screen section.
    [ 6.978] (==) No screen section available. Using defaults.
    [ 6.978] (**) |-->Screen "Default Screen Section" (0)
    [ 6.978] (**) | |-->Monitor "<default monitor>"
    [ 6.985] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 6.985] (==) Automatically adding devices
    [ 6.985] (==) Automatically enabling devices
    [ 6.985] (==) Automatically adding GPU devices
    [ 7.000] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 7.000] Entry deleted from font path.
    [ 7.000] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 7.000] Entry deleted from font path.
    [ 7.000] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 7.000] Entry deleted from font path.
    [ 7.000] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 7.000] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 7.000] Entry deleted from font path.
    [ 7.000] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 7.000] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/
    [ 7.000] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 7.000] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 7.005] (II) Loader magic: 0x8258620
    [ 7.005] (II) Module ABI versions:
    [ 7.005] X.Org ANSI C Emulation: 0.4
    [ 7.005] X.Org Video Driver: 14.1
    [ 7.005] X.Org XInput driver : 19.1
    [ 7.005] X.Org Server Extension : 7.0
    [ 7.006] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 7.007] (--) PCI:*(0:0:2:0) 8086:2562:1028:0160 rev 1, Mem @ 0xe8000000/134217728, 0xfeb80000/524288
    [ 7.008] Initializing built-in extension Generic Event Extension
    [ 7.008] Initializing built-in extension SHAPE
    [ 7.008] Initializing built-in extension MIT-SHM
    [ 7.008] Initializing built-in extension XInputExtension
    [ 7.008] Initializing built-in extension XTEST
    [ 7.008] Initializing built-in extension BIG-REQUESTS
    [ 7.008] Initializing built-in extension SYNC
    [ 7.008] Initializing built-in extension XKEYBOARD
    [ 7.008] Initializing built-in extension XC-MISC
    [ 7.008] Initializing built-in extension SECURITY
    [ 7.008] Initializing built-in extension XINERAMA
    [ 7.008] Initializing built-in extension XFIXES
    [ 7.008] Initializing built-in extension RENDER
    [ 7.008] Initializing built-in extension RANDR
    [ 7.008] Initializing built-in extension COMPOSITE
    [ 7.008] Initializing built-in extension DAMAGE
    [ 7.008] Initializing built-in extension MIT-SCREEN-SAVER
    [ 7.008] Initializing built-in extension DOUBLE-BUFFER
    [ 7.008] Initializing built-in extension RECORD
    [ 7.008] Initializing built-in extension DPMS
    [ 7.008] Initializing built-in extension X-Resource
    [ 7.008] Initializing built-in extension XVideo
    [ 7.008] Initializing built-in extension XVideo-MotionCompensation
    [ 7.008] Initializing built-in extension XFree86-VidModeExtension
    [ 7.008] Initializing built-in extension XFree86-DGA
    [ 7.008] Initializing built-in extension XFree86-DRI
    [ 7.008] Initializing built-in extension DRI2
    [ 7.008] (II) LoadModule: "glx"
    [ 7.027] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 7.042] (II) Module glx: vendor="X.Org Foundation"
    [ 7.042] compiled for 1.14.2, module version = 1.0.0
    [ 7.042] ABI class: X.Org Server Extension, version 7.0
    [ 7.042] (==) AIGLX enabled
    [ 7.042] Loading extension GLX
    [ 7.042] (==) Matched intel as autoconfigured driver 0
    [ 7.042] (==) Matched intel as autoconfigured driver 1
    [ 7.042] (==) Matched vesa as autoconfigured driver 2
    [ 7.042] (==) Matched modesetting as autoconfigured driver 3
    [ 7.043] (==) Matched fbdev as autoconfigured driver 4
    [ 7.043] (==) Assigned the driver to the xf86ConfigLayout
    [ 7.043] (II) LoadModule: "intel"
    [ 7.044] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 7.098] (II) Module intel: vendor="X.Org Foundation"
    [ 7.098] compiled for 1.14.2, module version = 2.21.12
    [ 7.098] Module class: X.Org Video Driver
    [ 7.098] ABI class: X.Org Video Driver, version 14.1
    [ 7.098] (II) LoadModule: "vesa"
    [ 7.098] (WW) Warning, couldn't open module vesa
    [ 7.098] (II) UnloadModule: "vesa"
    [ 7.098] (II) Unloading vesa
    [ 7.098] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 7.098] (II) LoadModule: "modesetting"
    [ 7.099] (WW) Warning, couldn't open module modesetting
    [ 7.099] (II) UnloadModule: "modesetting"
    [ 7.099] (II) Unloading modesetting
    [ 7.099] (EE) Failed to load module "modesetting" (module does not exist, 0)
    [ 7.099] (II) LoadModule: "fbdev"
    [ 7.099] (WW) Warning, couldn't open module fbdev
    [ 7.099] (II) UnloadModule: "fbdev"
    [ 7.099] (II) Unloading fbdev
    [ 7.099] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 7.099] (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), HD Graphics, HD Graphics 4600,
    Haswell Desktop (GT3), HD Graphics, HD Graphics 4600,
    Haswell Mobile (GT3), HD Graphics, HD Graphics P4600/P4700,
    Haswell Server (GT3), Haswell (GT1), Haswell (GT2), Haswell (GT3),
    HD Graphics, Haswell (GT2), Haswell (GT3), Haswell SDV Desktop (GT1),
    Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT3),
    Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
    Haswell SDV Mobile (GT3), Haswell SDV Server (GT1),
    Haswell SDV Server (GT2), Haswell SDV Server (GT3),
    Haswell SDV (GT1), Haswell SDV (GT2), Haswell SDV (GT3),
    Haswell SDV (GT1), Haswell SDV (GT2), Haswell SDV (GT3),
    Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
    Iris(TM) Graphics 5100, HD Graphics, HD Graphics 4400,
    HD Graphics 5000, Haswell ULT Server (GT1), Haswell ULT Server (GT2),
    Iris(TM) Graphics 5100, Haswell ULT (GT1), Haswell ULT (GT2),
    Iris(TM) Graphics 5100, HD Graphics, HD Graphics 4200,
    Iris(TM) Graphics 5100, Haswell CRW Desktop (GT1), HD Graphics 4600,
    Iris(TM) Pro Graphics 5200, Haswell CRW Mobile (GT1),
    HD Graphics 4600, Iris(TM) Pro Graphics 5200,
    Haswell CRW Server (GT1), Haswell CRW Server (GT2),
    Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2),
    Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2),
    Iris(TM) Pro Graphics 5200, ValleyView PO board
    [ 7.101] (++) using VT number 7
    [ 7.101] (II) intel(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 7.101] (==) intel(0): Depth 24, (--) framebuffer bpp 32
    [ 7.101] (==) intel(0): RGB weight 888
    [ 7.101] (==) intel(0): Default visual is TrueColor
    [ 7.101] (--) intel(0): Integrated Graphics Chipset: Intel(R) 845G
    [ 7.101] (**) intel(0): Relaxed fencing disabled
    [ 7.102] (**) intel(0): Wait on SwapBuffers? enabled
    [ 7.102] (**) intel(0): Triple buffering? enabled
    [ 7.102] (**) intel(0): Framebuffer tiled
    [ 7.102] (**) intel(0): Pixmaps tiled
    [ 7.102] (**) intel(0): 3D buffers tiled
    [ 7.102] (**) intel(0): SwapBuffers wait enabled
    [ 7.103] (==) intel(0): video overlay key set to 0x101fe
    [ 7.303] (II) intel(0): Output VGA1 has no monitor section
    [ 7.443] (II) intel(0): EDID for output VGA1
    [ 7.443] (II) intel(0): Manufacturer: DEL Model: 3142 Serial#: 894121267
    [ 7.443] (II) intel(0): Year: 1999 Week: 29
    [ 7.443] (II) intel(0): EDID Version: 1.2
    [ 7.443] (II) intel(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
    [ 7.443] (II) intel(0): Sync: Separate
    [ 7.443] (II) intel(0): Max Image Size [cm]: horiz.: 32 vert.: 24
    [ 7.443] (II) intel(0): Gamma: 2.27
    [ 7.443] (II) intel(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
    [ 7.443] (II) intel(0): First detailed timing is preferred mode
    [ 7.443] (II) intel(0): redX: 0.645 redY: 0.321 greenX: 0.285 greenY: 0.600
    [ 7.443] (II) intel(0): blueX: 0.142 blueY: 0.057 whiteX: 0.283 whiteY: 0.298
    [ 7.443] (II) intel(0): Supported established timings:
    [ 7.443] (II) intel(0): 720x400@70Hz
    [ 7.443] (II) intel(0): 640x480@60Hz
    [ 7.443] (II) intel(0): 640x480@75Hz
    [ 7.443] (II) intel(0): 800x600@60Hz
    [ 7.443] (II) intel(0): 800x600@75Hz
    [ 7.443] (II) intel(0): 1024x768@60Hz
    [ 7.443] (II) intel(0): 1024x768@75Hz
    [ 7.443] (II) intel(0): 1280x1024@75Hz
    [ 7.443] (II) intel(0): Manufacturer's mask: 0
    [ 7.443] (II) intel(0): Supported standard timings:
    [ 7.443] (II) intel(0): #0: hsize: 1024 vsize 768 refresh: 85 vid: 22881
    [ 7.443] (II) intel(0): #1: hsize: 800 vsize 600 refresh: 85 vid: 22853
    [ 7.443] (II) intel(0): #2: hsize: 640 vsize 480 refresh: 85 vid: 22833
    [ 7.443] (II) intel(0): Supported detailed timing:
    [ 7.443] (II) intel(0): clock: 94.5 MHz Image Size: 306 x 230 mm
    [ 7.444] (II) intel(0): h_active: 1024 h_sync: 1072 h_sync_end 1168 h_blank_end 1376 h_border: 0
    [ 7.444] (II) intel(0): v_active: 768 v_sync: 769 v_sync_end 772 v_blanking: 808 v_border: 0
    [ 7.444] (II) intel(0): Serial No: 5322DE5K5379
    [ 7.444] (II) intel(0): Monitor name: DELL M780
    [ 7.444] (II) intel(0): Ranges: V min: 50 V max: 160 Hz, H min: 30 H max: 85 kHz,
    [ 7.444] (II) intel(0): EDID (in hex):
    [ 7.444] (II) intel(0): 00ffffffffffff0010ac423133354b35
    [ 7.444] (II) intel(0): 1d0901020820187fea1269a552499924
    [ 7.444] (II) intel(0): 0e484ca54b0061594559315901010101
    [ 7.444] (II) intel(0): 010101010101ea240060410028303060
    [ 7.444] (II) intel(0): 130032e61000001e000000ff00353332
    [ 7.444] (II) intel(0): 324445354b353337390a000000fc0044
    [ 7.444] (II) intel(0): 454c4c204d3738300a202020000000fd
    [ 7.444] (II) intel(0): 0032a01e55ff000a20202020202000e3
    [ 7.444] (II) intel(0): Printing probed modes for output VGA1
    [ 7.444] (II) intel(0): Modeline "1024x768"x85.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz eP)
    [ 7.444] (II) intel(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 7.444] (II) intel(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 7.444] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 7.444] (II) intel(0): Modeline "800x600"x85.1 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz e)
    [ 7.444] (II) intel(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 7.444] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 7.444] (II) intel(0): Modeline "640x480"x85.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz e)
    [ 7.444] (II) intel(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 7.444] (II) intel(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 7.444] (II) intel(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 7.444] (II) intel(0): Output VGA1 connected
    [ 7.444] (II) intel(0): Using exact sizes for initial modes
    [ 7.444] (II) intel(0): Output VGA1 using initial mode 1024x768
    [ 7.444] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 7.444] (II) intel(0): Kernel page flipping support detected, enabling
    [ 7.444] (==) intel(0): DPI set to (96, 96)
    [ 7.444] (II) Loading sub module "fb"
    [ 7.444] (II) LoadModule: "fb"
    [ 7.444] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 7.458] (II) Module fb: vendor="X.Org Foundation"
    [ 7.458] compiled for 1.14.2, module version = 1.0.0
    [ 7.458] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 7.458] (II) Loading sub module "dri2"
    [ 7.458] (II) LoadModule: "dri2"
    [ 7.458] (II) Module "dri2" already built-in
    [ 7.458] (==) Depth 24 pixmap format is 32 bpp
    [ 7.466] (II) intel(0): [DRI2] Setup complete
    [ 7.466] (II) intel(0): [DRI2] DRI driver: i915
    [ 7.466] (II) intel(0): Allocated new frame buffer 1024x768 stride 4096, tiled
    [ 7.478] (II) UXA(0): Driver registered support for the following operations:
    [ 7.478] (II) solid
    [ 7.478] (II) copy
    [ 7.478] (II) composite (RENDER acceleration)
    [ 7.478] (II) put_image
    [ 7.478] (II) get_image
    [ 7.478] (==) intel(0): Backing store disabled
    [ 7.478] (==) intel(0): Silken mouse enabled
    [ 7.478] (II) intel(0): Initializing HW Cursor
    [ 7.478] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 7.480] (==) intel(0): DPMS enabled
    [ 7.480] (==) intel(0): Intel XvMC decoder disabled
    [ 7.480] (II) intel(0): Set up overlay video
    [ 7.480] (II) intel(0): direct rendering: DRI2 Enabled
    [ 7.480] (==) intel(0): hotplug detection: "enabled"
    [ 7.540] (--) RandR disabled
    [ 7.689] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 7.689] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 7.689] (II) AIGLX: enabled GLX_ARB_create_context
    [ 7.689] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 7.689] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 7.689] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 7.689] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 7.689] (II) AIGLX: Loaded and initialized i915
    [ 7.689] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 7.690] (II) intel(0): Setting screen physical size to 270 x 203
    [ 7.924] (II) config/udev: Adding input device Power Button (/dev/input/event3)
    [ 7.924] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 7.924] (II) LoadModule: "evdev"
    [ 7.925] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 7.943] (II) Module evdev: vendor="X.Org Foundation"
    [ 7.943] compiled for 1.14.2, module version = 2.8.1
    [ 7.943] Module class: X.Org XInput Driver
    [ 7.943] ABI class: X.Org XInput driver, version 19.1
    [ 7.943] (II) Using input driver 'evdev' for 'Power Button'
    [ 7.943] (**) Power Button: always reports core events
    [ 7.943] (**) evdev: Power Button: Device: "/dev/input/event3"
    [ 7.943] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 7.943] (--) evdev: Power Button: Found keys
    [ 7.943] (II) evdev: Power Button: Configuring as keyboard
    [ 7.943] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
    [ 7.943] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 7.943] (**) Option "xkb_rules" "evdev"
    [ 7.943] (**) Option "xkb_model" "pc104"
    [ 7.943] (**) Option "xkb_layout" "us"
    [ 7.980] (II) config/udev: Adding input device Power Button (/dev/input/event2)
    [ 7.980] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 7.980] (II) Using input driver 'evdev' for 'Power Button'
    [ 7.980] (**) Power Button: always reports core events
    [ 7.980] (**) evdev: Power Button: Device: "/dev/input/event2"
    [ 7.980] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 7.980] (--) evdev: Power Button: Found keys
    [ 7.980] (II) evdev: Power Button: Configuring as keyboard
    [ 7.981] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2/event2"
    [ 7.981] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 7.981] (**) Option "xkb_rules" "evdev"
    [ 7.981] (**) Option "xkb_model" "pc104"
    [ 7.981] (**) Option "xkb_layout" "us"
    [ 7.981] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 7.982] (II) config/udev: Adding input device OM (/dev/input/event1)
    [ 7.982] (**) OM: Applying InputClass "evdev pointer catchall"
    [ 7.982] (II) Using input driver 'evdev' for 'OM'
    [ 7.982] (**) OM: always reports core events
    [ 7.982] (**) evdev: OM: Device: "/dev/input/event1"
    [ 7.982] (--) evdev: OM: Vendor 0x4f3 Product 0x232
    [ 7.982] (--) evdev: OM: Found 3 mouse buttons
    [ 7.982] (--) evdev: OM: Found scroll wheel(s)
    [ 7.982] (--) evdev: OM: Found relative axes
    [ 7.982] (--) evdev: OM: Found x and y relative axes
    [ 7.982] (II) evdev: OM: Configuring as mouse
    [ 7.982] (II) evdev: OM: Adding scrollwheel support
    [ 7.982] (**) evdev: OM: YAxisMapping: buttons 4 and 5
    [ 7.982] (**) evdev: OM: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 7.982] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0/input/input1/event1"
    [ 7.982] (II) XINPUT: Adding extended input device "OM" (type: MOUSE, id 8)
    [ 7.982] (II) evdev: OM: initialized for relative axes.
    [ 7.983] (**) OM: (accel) keeping acceleration scheme 1
    [ 7.983] (**) OM: (accel) acceleration profile 0
    [ 7.983] (**) OM: (accel) acceleration factor: 2.000
    [ 7.983] (**) OM: (accel) acceleration threshold: 4
    [ 7.983] (II) config/udev: Adding input device OM (/dev/input/mouse0)
    [ 7.983] (II) No input driver specified, ignoring this device.
    [ 7.983] (II) This device may have been added with another device file.
    [ 7.984] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 7.984] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 7.984] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 7.984] (**) AT Translated Set 2 keyboard: always reports core events
    [ 7.984] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 7.984] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 7.984] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 7.984] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 7.984] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 7.984] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
    [ 7.984] (**) Option "xkb_rules" "evdev"
    [ 7.984] (**) Option "xkb_model" "pc104"
    [ 7.984] (**) Option "xkb_layout" "us"
    [ 7.985] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
    [ 7.985] (II) No input driver specified, ignoring this device.
    [ 7.985] (II) This device may have been added with another device file.
    [ 29.826] (II) AIGLX: Suspending AIGLX clients for VT switch
    [ 53.275] (II) AIGLX: Resuming AIGLX clients after VT switch
    [ 53.426] (II) intel(0): EDID vendor "DEL", prod id 12610
    [ 53.427] (II) intel(0): Using EDID range info for horizontal sync
    [ 53.427] (II) intel(0): Using EDID range info for vertical refresh
    [ 53.427] (II) intel(0): Printing DDC gathered Modelines:
    [ 53.427] (II) intel(0): Modeline "1024x768"x0.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz eP)
    [ 53.427] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 53.427] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 53.427] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 53.427] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 53.427] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 53.427] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 53.427] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 53.427] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 53.427] (II) intel(0): Modeline "800x600"x0.0 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz e)
    [ 53.427] (II) intel(0): Modeline "640x480"x0.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz e)
    [ 53.433] setversion 1.4 failed
    [ 57.450] (II) intel(0): EDID vendor "DEL", prod id 12610
    [ 57.450] (II) intel(0): Using hsync ranges from config file
    [ 57.450] (II) intel(0): Using vrefresh ranges from config file
    [ 57.450] (II) intel(0): Printing DDC gathered Modelines:
    [ 57.450] (II) intel(0): Modeline "1024x768"x0.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz eP)
    [ 57.450] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 57.450] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 57.450] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 57.450] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 57.450] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 57.450] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 57.450] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 57.450] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 57.450] (II) intel(0): Modeline "800x600"x0.0 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz e)
    [ 57.450] (II) intel(0): Modeline "640x480"x0.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz e)
    [ 57.590] (II) intel(0): EDID vendor "DEL", prod id 12610
    [ 57.590] (II) intel(0): Using hsync ranges from config file
    [ 57.590] (II) intel(0): Using vrefresh ranges from config file
    [ 57.590] (II) intel(0): Printing DDC gathered Modelines:
    [ 57.590] (II) intel(0): Modeline "1024x768"x0.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz eP)
    [ 57.590] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 57.590] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 57.590] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 57.590] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 57.590] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 57.590] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 57.590] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 57.590] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 57.590] (II) intel(0): Modeline "800x600"x0.0 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz e)
    [ 57.590] (II) intel(0): Modeline "640x480"x0.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz e)
    [ 57.763] (II) intel(0): EDID vendor "DEL", prod id 12610
    [ 57.763] (II) intel(0): Using hsync ranges from config file
    [ 57.763] (II) intel(0): Using vrefresh ranges from config file
    [ 57.763] (II) intel(0): Printing DDC gathered Modelines:
    [ 57.763] (II) intel(0): Modeline "1024x768"x0.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz eP)
    [ 57.763] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 57.763] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 57.763] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 57.763] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 57.763] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 57.763] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 57.763] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 57.763] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 57.763] (II) intel(0): Modeline "800x600"x0.0 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz e)
    [ 57.763] (II) intel(0): Modeline "640x480"x0.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz e)
    [ 57.903] (II) intel(0): EDID vendor "DEL", prod id 12610
    [ 57.903] (II) intel(0): Using hsync ranges from config file
    [ 57.903] (II) intel(0): Using vrefresh ranges from config file
    [ 57.903] (II) intel(0): Printing DDC gathered Modelines:
    [ 57.903] (II) intel(0): Modeline "1024x768"x0.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz eP)
    [ 57.903] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 57.903] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 57.903] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 57.903] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 57.903] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 57.903] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 57.903] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 57.903] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 57.903] (II) intel(0): Modeline "800x600"x0.0 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz e)
    [ 57.903] (II) intel(0): Modeline "640x480"x0.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz e)
    No doubt I have missed the pertinent log.
    Last edited by nef131 (2013-07-31 12:47:23)

    Oxyd,
    The current state of things, after removing gdm, slim and reinstalling lightdm, is that nothing has changed. In any event, below is the results of pacman -Qs lightdm:
    [allen@archbox ~]$ pacman -Qs lightdm
    local/lightdm 1:1.6.0-5 (lightdm)
    A lightweight display manager
    local/lightdm-gtk3-greeter 1:1.6.0-1
    GTK+ greeter for LightDM
    [allen@archbox ~]$
    The result of is cat /etc/lightdm/lightdm.conf:
    [allen@archbox ~]$ cat /etc/lightdm/lightdm.conf
    # General configuration
    # start-default-seat = True to always start one seat if none are defined in the configuration
    # greeter-user = User to run greeter as
    # minimum-display-number = Minimum display number to use for X servers
    # minimum-vt = First VT to run displays on
    # lock-memory = True to prevent memory from being paged to disk
    # user-authority-in-system-dir = True if session authority should be in the system location
    # guest-account-script = Script to be run to setup guest account
    # log-directory = Directory to log information to
    # run-directory = Directory to put running state in
    # cache-directory = Directory to cache to
    # xsessions-directory = Directory to find X sessions
    # remote-sessions-directory = Directory to find remote sessions
    # xgreeters-directory = Directory to find X greeters
    [LightDM]
    #start-default-seat=true
    #greeter-user=lightdm
    #minimum-display-number=0
    #minimum-vt=7
    #lock-memory=true
    #user-authority-in-system-dir=false
    #guest-account-script=guest-account
    #log-directory=/var/log/lightdm
    run-directory=/run/lightdm
    #cache-directory=/var/cache/lightdm
    #xsessions-directory=/usr/share/xsessions
    #remote-sessions-directory=/usr/share/lightdm/remote-sessions
    #xgreeters-directory=/usr/share/xgreeters
    # Seat defaults
    # type = Seat type (xlocal, xremote)
    # xserver-command = X server command to run (can also contain arguments e.g. X -special-option)
    # xserver-layout = Layout to pass to X server
    # xserver-config = Config file to pass to X server
    # xserver-allow-tcp = True if TCP/IP connections are allowed to this X server
    # xdmcp-manager = XDMCP manager to connect to (implies xserver-allow-tcp=true)
    # xdmcp-port = XDMCP UDP/IP port to communicate on
    # xdmcp-key = Authentication key to use for XDM-AUTHENTICATION-1 (stored in keys.conf)
    # greeter-session = Session to load for greeter
    # greeter-hide-users = True to hide the user list
    # greeter-allow-guest = True if the greeter should show a guest login option
    # greeter-show-manual-login = True if the greeter should offer a manual login option
    # greeter-show-remote-login = True if the greeter should offer a remote login option
    # user-session = Session to load for users
    # allow-guest = True if guest login is allowed
    # guest-session = Session to load for guests (overrides user-session)
    # session-wrapper = Wrapper script to run session with
    # display-setup-script = Script to run when starting a greeter session (runs as root)
    # greeter-setup-script = Script to run when starting a greeter (runs as root)
    # session-setup-script = Script to run when starting a user session (runs as root)
    # session-cleanup-script = Script to run when quitting a user session (runs as root)
    # autologin-guest = True to log in as guest by default
    # autologin-user = User to log in with by default (overrides autologin-guest)
    # autologin-user-timeout = Number of seconds to wait before loading default user
    # autologin-session = Session to load for automatic login (overrides user-session)
    # exit-on-failure = True if the daemon should exit if this seat fails
    [SeatDefaults]
    #type=xlocal
    #xserver-command=X
    #xserver-layout=
    #xserver-config=
    #xserver-allow-tcp=false
    #xdmcp-manager=
    #xdmcp-port=177
    #xdmcp-key=
    #greeter-session=example-gtk-gnome
    #greeter-hide-users=false
    #greeter-allow-guest=true
    #greeter-show-manual-login=false
    #greeter-show-remote-login=true
    #user-session=default
    #allow-guest=true
    #guest-session=UNIMPLEMENTED
    session-wrapper=/etc/lightdm/xsession
    #display-setup-script=
    #greeter-setup-script=
    #session-setup-script=
    #session-cleanup-script=
    #autologin-guest=false
    #autologin-user=
    #autologin-user-timeout=0
    #autologin-session=UNIMPLEMENTED
    pam-service=lightdm-autologin
    #exit-on-failure=false
    # Seat configuration
    # Each seat must start with "Seat:".
    # Uses settings from [SeatDefaults], any of these can be overriden by setting them in this section.
    #[Seat:0]
    # XDMCP Server configuration
    # enabled = True if XDMCP connections should be allowed
    # port = UDP/IP port to listen for connections on
    # key = Authentication key to use for XDM-AUTHENTICATION-1 or blank to not use authentication (stored in keys.conf)
    # The authentication key is a 56 bit DES key specified in hex as 0xnnnnnnnnnnnnnn. Alternatively
    # it can be a word and the first 7 characters are used as the key.
    [XDMCPServer]
    #enabled=false
    #port=177
    #key=
    # VNC Server configuration
    # enabled = True if VNC connections should be allowed
    # command = Command to run Xvnc server with
    # port = TCP/IP port to listen for connections on
    # width = Width of display to use
    # height = Height of display to use
    # depth = Color depth of display to use
    [VNCServer]
    #enabled=false
    #command=Xvnc
    #port=5900
    #width=1024
    #height=768
    #depth=8
    The result of cat /etc/lightdm/lightdm-gtk-greeter.conf is :
    [allen@archbox ~]$ cat /etc/lightdm/lightdm-gtk-greeter.conf
    # background = Background file to use, either an image path or a color (e.g. #772953)
    # theme-name = GTK+ theme to use
    # icon-theme-name = Icon theme to use
    # font-name = Font to use
    # xft-antialias = Whether to antialias Xft fonts (true or false)
    # xft-dpi = Resolution for Xft in dots per inch (e.g. 96)
    # xft-hintstyle = What degree of hinting to use (none, slight, medium, or full)
    # xft-rgba = Type of subpixel antialiasing (none, rgb, bgr, vrgb or vbgr)
    # show-language-selector (true or false)
    # show-indicators = semi-colon ";" separated list of allowed indicator modules (e.g. libsoundmenu.so)
    # show-clock (true or false)
    # clock-format = strftime-format string, e.g. %H:%M
    # keyboard = command to launch on-screen keyboard
    [greeter]
    #background=
    #theme-name=
    #icon-theme-name=
    #font-name=
    #xft-antialias=
    #xft-dpi=
    #xft-hintstyle=
    #xft-rgba=
    #show-language-selector=
    #show-indicators=
    #show-clock=
    #clock-format=
    #keyboard=
    Cfr: "Did you test X following the Beginners' Guide?"
    Yes. I tested X. I believe that I followed the Beginner's Guide to the letter. Of course, I am new to Arch, so it is possible I misunderstood something. I believe what I did was to enter the following command to install X: pacman -S xorg-server xorg-server-utils xorg-xinit and then, as provided in the guide, I installed mesa.
    I have, per your suggestion, removed xorg-server-xephyr. I note, however, that the guide for installing lightdm indicates that the package should be installed initially, in order to test to see if lightdm works. In any event, removing it does not alter how the system starts up.
    You are correct that I am starting the computer directly to lightdm - and not starting lightdm from X - but lightdm leaves a blank page, as I noted. I can click around on the blank page and stuff pops up. On looking at Oxyd's suggested outputs, I wonder if my problem is that nearly everything in the configuration file has been commented out.

  • [SOLVED] display-manager.service

    How can I find out what is trying to load this service?
    I see this in my dmesg and while I don't think it's a problem, I'm just trying to make my server as robust/bug/error free as possible.
    [ 4.058436] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
    Not an actual server, but an old quad core PC that has no onboard, and no video card. It's just a spare box used like a server.
    Last edited by Naijeru (2012-09-18 14:54:33)

    Naijeru, there is documentation for a purpose. In this case: https://wiki.archlinux.org/index.php/Sy … _boot_into
    Please don't be a help vampire. And read our forum etiquette.

  • [Solved] The framebuffer, Grub, and graphics card driver

    I'm running Arch on a 15.1" laptop, and the natural resolution for my LCD is 1366x768.
    X has no problem of adjusting itself to the right resolution. The console can do this too, but only when I have the open-source graphics card driver (xf86-video-ati). If I try catalyst in the AUR, the console falls back to 800x600, characters being wide and blur. Grub seems to suffer from a similar problem. It always present me with a 800x600 menu, and the early userspace booting is in this resolution too.
    I followed the instructions in https://wiki.archlinux.org/index.php/Gr … resolution and the following is what I found out.
    I couldn't find the package lrmi in the repo. (I doubt the wiki page is outdated.) I did find vbetool, but it doesn't provide vbetest. Taking the next approach, running sudo hwinfo --framebuffer gives:
    02: None 00.0: 11001 VESA Framebuffer
    [Created at bios.459]
    Unique ID: rdCR.A3Y7SCr7Y49
    Hardware Class: framebuffer
    Model: "(C) 1988-2005, ATI M92"
    Vendor: "(C) 1988-2005, ATI Technologies Inc."
    Device: "M92"
    SubVendor: "ATI ATOMBIOS"
    SubDevice:
    Revision: "01.00"
    Memory Size: 16 MB
    Memory Range: 0xd0000000-0xd0ffffff (rw)
    Mode 0x0300: 640x400 (+640), 8 bits
    Mode 0x0301: 640x480 (+640), 8 bits
    Mode 0x0303: 800x600 (+832), 8 bits
    Mode 0x0305: 1024x768 (+1024), 8 bits
    Mode 0x0310: 640x480 (+1280), 15 bits
    Mode 0x0311: 640x480 (+1280), 16 bits
    Mode 0x0313: 800x600 (+1600), 15 bits
    Mode 0x0314: 800x600 (+1600), 16 bits
    Mode 0x0316: 1024x768 (+2048), 15 bits
    Mode 0x0317: 1024x768 (+2048), 16 bits
    Mode 0x030d: 320x200 (+640), 15 bits
    Mode 0x030e: 320x200 (+640), 16 bits
    Mode 0x0320: 320x200 (+1280), 24 bits
    Mode 0x0393: 320x240 (+320), 8 bits
    Mode 0x0395: 320x240 (+640), 16 bits
    Mode 0x0396: 320x240 (+1280), 24 bits
    Mode 0x03b3: 512x384 (+512), 8 bits
    Mode 0x03b5: 512x384 (+1024), 16 bits
    Mode 0x03b6: 512x384 (+2048), 24 bits
    Mode 0x03c3: 640x350 (+640), 8 bits
    Mode 0x03c5: 640x350 (+1280), 16 bits
    Mode 0x03c6: 640x350 (+2560), 24 bits
    Mode 0x0333: 720x400 (+768), 8 bits
    Mode 0x0335: 720x400 (+1472), 16 bits
    Mode 0x0336: 720x400 (+2944), 24 bits
    Mode 0x0360: 848x480 (+896), 8 bits
    Mode 0x0361: 848x480 (+1728), 16 bits
    Mode 0x0362: 848x480 (+3456), 24 bits
    Mode 0x0321: 640x480 (+2560), 24 bits
    Mode 0x0322: 800x600 (+3200), 24 bits
    Mode 0x0323: 1024x768 (+4096), 24 bits
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    No 1366x768. Taking the last approach, I added "vga=ask" to the Grub entry. Again no 1366x768. How can I get the resolution set to 1366x768 during Grub and/or early userspace booting? Or is it simply impossible?
    Last edited by xiaq (2011-03-07 09:23:10)

    Mr.Elendig wrote:The only way to really do it is to use kms and the free driver for X.
    So...  I should follow https://wiki.archlinux.org/index.php/AT … _KMS_start, since I have an ATI card and I've decided to stick with the free driver(at least for now).
    Still one question: to use KMS early(this is what I want), I need to regenerate the initial image(mkinitcpio). What's the worst result if it fails? Will mkinitcpio make no complaints but give me an unusable image? I'm asking the questions both in general and in my specific case(trying to enable KMS during early start).

  • [SOLVED] Issues with GRUB and rc.conf

    I've just performed a full system upgrade and I've found these errors:
    -> When I restart my system, GRUB doesn't load at all. It takes severak seconds until it displays "GRUB Stage 1.5" and right after that it then enters in a loop displaying the message until forever
    GRUB Stage 1.5
    GRUB Stage 1.5
    GRUB Stage 1.5
    GRUB Stage 1.5
    GRUB Stage 1.5
    and so on.
    It only happens when I restart the system from my DE. If I turn off and on the system everythings works fine again. I've also tried to reinstall grub but the problem persists, Any idea on this issue??
    -> I use Xfce4 as my desktop enviroment and after the upgrade it ignores the KEYMAP entry in my rc.conf file. It is set to "es" but somehow it uses a us layout. I can change the layout in the Xfce menu but why is this happening? Why is it ignoring the rc.conf file?
    UPDATE: I solved this issue by doing this: http://wiki.archlinux.org/index.php/Xor … _US_layout
    Any clues on the issues are appreciated.
    Thanks in advance!
    Last edited by flight243 (2010-09-17 22:31:50)

    UPDATE2: Surprisingly the GRUB problem does not happen to me anymore and I have not changed anything. How weird....
    Anyway, this thread is SOLVED.
    Thanks for reading!

  • Solved: Display blanks out and does not turn on untill reboot.

    Hardware:
    ======
    Intel i7 prossesor (x86)
    Asus motherboard with UEIF
    ATI radeon 5770 graphics
    Partitioneng:
    ========
    sda: windows file system partitions
    sdb1: /boot (FAT32) - GRUB UIEF
    sdb2: / (ext4)
    sdc: windows bootloader and os
    Software:
    =====
    Regular instal acording to Beginers guid and ATI drivers page.
    Graphics drivers are the big free ATI driver package.
    Problem.
    ======
    After a random amount of time, usialy a fiew minutes after the computer starts, the display turns of.
    This happens in the BIOS menu, the live arch tty, arch tty and gnome.
    This does not happen if i boot into windows or a Ubutu live cd.
    When the display blanks out in a tty i am still able to interact with it,  eg: if i blindly type 'reboot[enter]' the stystem reboots, ore 'man[space]ls[up][up]' computer peeps.
    When the display blanks out in Gnome the keyboard gets disabled aswell.
    I am able to ssh into the computer if it blanks out while i am runnig arch.
    When the computer blanks out nothing but a hardware shutdown and restart seams to turn on the dispaly again. doing a reboot comand (while blanked out) thorugh ssh causes the computer to reboot but the display is still disabled after the reboot.
    Atempted fix
    =======
    attempted to run in bash:
      xset s off
      xset -dpms
    no aperent efect.
    Coment
    ======
    It might be some motherbord fiture that blanks out the screen, what is curious though is thet Windows and Ubuntu never blankout, not even temporarely. So there must be somthing that can be done from the OS side.
    Another weird thing is that I would exect it to blank out when the user input is inactive if it was a pawer saving fiture, but it usialy blanks out while i am typing.
    I am grateful for all the help I can get.
    Last edited by pintjuk (2013-12-23 18:42:14)

    okej, found something interesting.
    this is from a more resent blanking
    not sure what it meens though, is it bugs in the video drivers?.
    dec 23 16:49:26 localhost kernel: radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
    dec 23 16:49:26 localhost kernel: radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000002633 last fence id 0x0000000000002632)
    dec 23 16:49:26 localhost kernel: [drm] Disabling audio 0 support
    dec 23 16:49:26 localhost kernel: BUG: unable to handle kernel paging request at ffffc9040bcbcffc
    dec 23 16:49:26 localhost kernel: IP: [<ffffffffa0880b18>] radeon_ring_backup+0xc8/0x160 [radeon]
    dec 23 16:49:26 localhost kernel: PGD 22680f067 PUD 0
    dec 23 16:49:26 localhost kernel: Oops: 0000 [#1] PREEMPT SMP
    dec 23 16:49:26 localhost kernel: Modules linked in: nls_utf8 isofs fuse btusb iTCO_wdt iTCO_vendor_support snd_hda_codec_hdmi snd_hda_codec_realtek x86_pkg_temp_thermal intel_powerclamp co
    dec 23 16:49:26 localhost kernel: ehci_pci xhci_hcd ehci_hcd firewire_ohci scsi_mod firewire_core crc_itu_t usbcore usb_common
    dec 23 16:49:26 localhost kernel: CPU: 2 PID: 297 Comm: Xorg Not tainted 3.12.5-1-ARCH #1
    dec 23 16:49:26 localhost kernel: Hardware name: System manufacturer System Product Name/P8Z68 DELUXE, BIOS 3603 11/09/2012
    dec 23 16:49:26 localhost kernel: task: ffff88000c394e30 ti: ffff88000c118000 task.ti: ffff88000c118000
    dec 23 16:49:26 localhost kernel: RIP: 0010:[<ffffffffa0880b18>] [<ffffffffa0880b18>] radeon_ring_backup+0xc8/0x160 [radeon]
    dec 23 16:49:26 localhost kernel: RSP: 0018:ffff88000c119ca0 EFLAGS: 00010246
    dec 23 16:49:26 localhost kernel: RAX: ffff880211d00000 RBX: ffff88022185d2d0 RCX: 0000000000000000
    dec 23 16:49:26 localhost kernel: RDX: ffffc9000bcbd000 RSI: 0000000000000000 RDI: ffffc9040bcbcffc
    dec 23 16:49:26 localhost kernel: RBP: ffff88000c119cd0 R08: 0000000000031e04 R09: 0000000000000006
    dec 23 16:49:26 localhost kernel: R10: 0000000000000040 R11: 0000000000000000 R12: 00000000ffffffff
    dec 23 16:49:26 localhost kernel: R13: ffff88022185d2a0 R14: 000000000000c781 R15: ffff88000c119d18
    dec 23 16:49:26 localhost kernel: FS: 00007f2dca10b880(0000) GS:ffff88022f280000(0000) knlGS:0000000000000000
    dec 23 16:49:26 localhost kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    dec 23 16:49:26 localhost kernel: CR2: ffffc9040bcbcffc CR3: 000000000c152000 CR4: 00000000000407e0
    dec 23 16:49:26 localhost kernel: Stack:
    dec 23 16:49:26 localhost kernel: ffff88000c119cb8 ffff88022185c000 ffff88022185d2d0 0000000000000000
    dec 23 16:49:26 localhost kernel: 0000000000000000 ffff88000c119d18 ffff88000c119d70 ffffffffa08513d7
    dec 23 16:49:26 localhost kernel: ffff88022185d2d0 000000010c119cf8 ffff88022185ca38 ffff88022185c018
    dec 23 16:49:26 localhost kernel: Call Trace:
    dec 23 16:49:26 localhost kernel: [<ffffffffa08513d7>] radeon_gpu_reset+0xa7/0x240 [radeon]
    dec 23 16:49:26 localhost kernel: [<ffffffff814f221d>] ? ww_mutex_unlock+0x3d/0xa0
    dec 23 16:49:26 localhost kernel: [<ffffffffa087ea5e>] radeon_gem_handle_lockup.part.5+0xe/0x20 [radeon]
    dec 23 16:49:26 localhost kernel: [<ffffffffa087f528>] radeon_gem_wait_idle_ioctl+0x98/0xf0 [radeon]
    dec 23 16:49:26 localhost kernel: [<ffffffffa05dcc62>] drm_ioctl+0x502/0x630 [drm]
    dec 23 16:49:26 localhost kernel: [<ffffffff810725e2>] ? __set_task_blocked+0x32/0x70
    dec 23 16:49:26 localhost kernel: [<ffffffff81074e2c>] ? signal_delivered+0x5c/0x80
    dec 23 16:49:26 localhost kernel: [<ffffffff81074e8c>] ? signal_setup_done+0x3c/0x60
    dec 23 16:49:26 localhost kernel: [<ffffffff8101462a>] ? do_signal+0x19a/0x940
    dec 23 16:49:26 localhost kernel: [<ffffffff8101f7a7>] ? __restore_xstate_sig+0x87/0x640
    dec 23 16:49:26 localhost kernel: [<ffffffff811b7275>] do_vfs_ioctl+0x2e5/0x4d0
    dec 23 16:49:26 localhost kernel: [<ffffffff811b74e1>] SyS_ioctl+0x81/0xa0
    dec 23 16:49:26 localhost kernel: [<ffffffff814fcfed>] system_call_fastpath+0x1a/0x1f
    dec 23 16:49:26 localhost kernel: Code: 48 85 c0 49 89 07 74 7b 41 8d 56 ff 31 c9 4c 8d 04 95 04 00 00 00 eb 06 0f 1f 00 49 8b 07 48 8b 53 08 41 8d 74 24 01 4a 8d 3c a2 <8b> 3f 89 3c 08 23
    dec 23 16:49:26 localhost kernel: RIP [<ffffffffa0880b18>] radeon_ring_backup+0xc8/0x160 [radeon]
    dec 23 16:49:26 localhost kernel: RSP <ffff88000c119ca0>
    dec 23 16:49:26 localhost kernel: CR2: ffffc9040bcbcffc
    dec 23 16:49:26 localhost kernel: ---[ end trace 1a11fa07f6928c93 ]---
    Last edited by pintjuk (2013-12-23 15:59:03)

  • [SOLVED]Network Manager Applet and nmcli failing after GCC upgrade

    Hi All,
    So I went to update my system today and there were only like 8 or 9 updates. Like many other people I had an issue with gcc and pacman. To fix this I ran
    pacman -S gcc
    Then I ran:
    pacman -Su
    which updated pacman itself. On reboot though I noticed network manager applet was unable to find any of my network devices despite the fact that network manager was running and I had an IP address. I killed nm-applet and re-ran it and it spewed errors about not being able to connect to network manager. I tried running nmcli and it did the same thing. However, when I run nmcli as root it works. Looking at the arch wiki they suggest you be a part of the wheel and network group which I made sure I was. Everything was working up until I ran those two updates though. Anyone else have this happen or have any idea what is wrong?
    Thanks,
    Hemmar
    EDIT: Never mind - a patch was released for consolekit which fixes the problem.
    Last edited by hemmar (2012-04-13 00:36:49)

    Hi guz46
    I have already tried removing the ! and the same thing happened ... but I realised today that I was being automatically connected to "Auto eth0" despite there being no cable present. When automatic connection was disabled on "Auto eth0" my 3G connection (ppp0) connected fine.
    Could you clarify that the preferred set-up in the /etc/rc.conf for the interfaces is without the !. The Wiki for networkmanager says to disable them, but then states that some may need to be reenabled with no explanation. The purpose of this confuses me!
    Thanks for you help anyways,
    Scott
    EDIT:
    I appear to have fixed my problem with the auto connection on the various interfaces by updating my /etc/rc.conf file to:
    #Static IP example
    #eth0="dhcp"
    ppp0="dhcp"
    wlan0="dhcp"
    eth0="dhcp"
    INTERFACES=(ppp0 wlan0 eth0)
    Thus ensuring that I can connect in order of preference.
    Last edited by ScottArch (2009-11-03 18:48:47)

  • [Solved] Display Manager reject my (correct) password

    I primarily use gnome and gdm tells me my password is wrong "Try again"...
    I changed my password with /usr/bin/passwd and still have this problem. Even with slim and lightdm the same problem occurs.
    However, I can still login with my fingerprint that I registered about a year ago.
    Does anyone have an idea how to fix this? I am considering wiping my / partition and reinstalling...
    Last edited by themax (2015-02-11 10:57:42)

    Hi,
    Is your keyboard properly configured and do you use symbols in your password? For example, if you have a UK keyboard that's not properly set up you may be using a US configuration, meaning some symbols (", @, #, ~ etc) are going to be in a different positions. Just a thought.
    Regards,
    Last edited by CH2IS (2015-02-11 02:40:12)

  • [Solved] Display manager failing after Nvidia driver install

    I installed Nvidia-304xx drivers from the website due to which xorg stopped working. I fixed it by following the wiki by installing bumblebee and using intel graphics for screen.
    However now when I boot I am getting an error saying "Oh no something has gone wrong. A problem has occoured and the system can't recover"
    Please help.
    Note: I am using 64 bit system
              Startx works on ttyx
    Last edited by harshsahil48 (2014-02-16 18:15:23)

    GDM log
    X.Org X Server 1.15.0
    Release Date: 2013-12-27
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 3.12.5-1-ARCH x86_64
    Current Operating System: Linux harsh 3.12.9-2-ARCH #1 SMP PREEMPT Fri Jan 31 10:22:54 CET 2014 x86_64
    Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=9d527456-8b84-4444-9997-a970795972df rw quiet
    Build Date: 09 January 2014 08:47:24AM
    Current version of pixman: 0.32.4
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    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: Sat Feb 15 12:34:27 2014
    (==) Using config file: "/etc/X11/xorg.conf"
    (==) Using config directory: "/etc/X11/xorg.conf.d"
    (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    (==) ServerLayout "Layout0"
    (**) |-->Screen "Screen0" (0)
    (**) | |-->Monitor "Monitor0"
    (**) | |-->Device "Device0"
    (**) |-->Input Device "Keyboard0"
    (**) |-->Input Device "Mouse0"
    (==) Automatically adding devices
    (==) Automatically enabling devices
    (==) Automatically adding GPU devices
    (==) 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/
    (==) ModulePath set to "/usr/lib/xorg/modules"
    (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
    (WW) Disabling Keyboard0
    (WW) Disabling Mouse0
    (II) xfree86: Adding drm device (/dev/dri/card0)
    (--) PCI:*(0:0:2:0) 8086:0116:1028:0491 rev 9, Mem @ 0xd2400000/4194304, 0xc0000000/268435456, I/O @ 0x00007000/64
    (--) PCI: (0:1:0:0) 10de:124d:1028:0491 rev 161, Mem @ 0xd0000000/33554432, 0xa0000000/268435456, 0xb0000000/67108864, I/O @ 0x00006000/128, BIOS @ 0x????????/524288
    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 SECURITY
    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 Present
    Initializing built-in extension DRI3
    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
    (II) "glx" will be loaded by default.
    (WW) Warning, couldn't open module glamoregl
    (II) Unloading glamoregl
    (EE) Failed to load module "glamoregl" (module does not exist, 0)
    (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    (II) Module glx: vendor="NVIDIA Corporation"
    compiled for 4.0.2, module version = 1.0.0
    (II) NVIDIA GLX Module 331.38 Wed Jan 8 19:10:17 PST 2014
    Loading extension GLX
    (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    (II) Module intel: vendor="X.Org Foundation"
    compiled for 1.15.0, module version = 2.99.910
    (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
    (II) intel: Driver for Intel(R) HD Graphics: 2000-5000
    (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100
    (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200
    (++) using VT number 1
    (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 3000
    (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx
    (**) intel(0): Depth 24, (--) framebuffer bpp 32
    (==) intel(0): RGB weight 888
    (==) intel(0): Default visual is TrueColor
    (**) intel(0): Framebuffer tiled
    (**) intel(0): Pixmaps tiled
    (**) intel(0): "Tear free" disabled
    (**) intel(0): Forcing per-crtc-pixmaps? no
    (II) intel(0): Output LVDS1 using monitor section Monitor0
    (--) intel(0): found backlight control interface acpi_video0 (type 'firmware')
    (II) intel(0): Output VGA1 has no monitor section
    (II) intel(0): Output HDMI1 has no monitor section
    (II) intel(0): Output DP1 has no monitor section
    (II) intel(0): Output VIRTUAL1 has no monitor section
    (--) intel(0): Output LVDS1 using initial mode 1600x900 on pipe 0
    (==) intel(0): DPI set to (96, 96)
    (==) Depth 24 pixmap format is 32 bpp
    (II) intel(0): SNA initialized with Sandybridge (gen6, gt2) backend
    (==) intel(0): Backing store enabled
    (==) intel(0): Silken mouse enabled
    (II) intel(0): HW Cursor enabled
    (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    (**) intel(0): DPMS enabled
    (II) intel(0): [DRI2] Setup complete
    (II) intel(0): [DRI2] DRI driver: i965
    (II) intel(0): [DRI2] VDPAU driver: i965
    (II) intel(0): direct rendering: DRI2 Enabled
    (==) intel(0): hotplug detection: "enabled"
    (--) RandR disabled
    (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
    (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    (II) intel(0): Setting screen physical size to 423 x 238
    (II) config/udev: Adding input device Power Button (/dev/input/event4)
    (**) Power Button: Applying InputClass "evdev keyboard catchall"
    (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    (II) Module evdev: vendor="X.Org Foundation"
    compiled for 1.15.0, module version = 2.8.2
    (II) Using input driver 'evdev' for 'Power Button'
    (**) Power Button: always reports core events
    (**) evdev: Power Button: Device: "/dev/input/event4"
    (--) evdev: Power Button: Vendor 0 Product 0x1
    (--) evdev: Power Button: Found keys
    (II) evdev: Power Button: Configuring as keyboard
    (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    (II) config/udev: Adding input device Video Bus (/dev/input/event13)
    (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    (II) Using input driver 'evdev' for 'Video Bus'
    (**) Video Bus: always reports core events
    (**) evdev: Video Bus: Device: "/dev/input/event13"
    (--) evdev: Video Bus: Vendor 0 Product 0x6
    (--) evdev: Video Bus: Found keys
    (II) evdev: Video Bus: Configuring as keyboard
    (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
    (II) config/udev: Adding input device Video Bus (/dev/input/event12)
    (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    (II) Using input driver 'evdev' for 'Video Bus'
    (**) Video Bus: always reports core events
    (**) evdev: Video Bus: Device: "/dev/input/event12"
    (--) evdev: Video Bus: Vendor 0 Product 0x6
    (--) evdev: Video Bus: Found keys
    (II) evdev: Video Bus: Configuring as keyboard
    (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
    (II) config/udev: Adding input device Lid Switch (/dev/input/event3)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding drm device (/dev/dri/card0)
    (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event5)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event9)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event8)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event7)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event10)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/event1)
    (**) Logitech USB Optical Mouse: Applying InputClass "evdev pointer catchall"
    (II) Using input driver 'evdev' for 'Logitech USB Optical Mouse'
    (**) Logitech USB Optical Mouse: always reports core events
    (**) evdev: Logitech USB Optical Mouse: Device: "/dev/input/event1"
    (--) evdev: Logitech USB Optical Mouse: Vendor 0x46d Product 0xc05a
    (--) evdev: Logitech USB Optical Mouse: Found 3 mouse buttons
    (--) evdev: Logitech USB Optical Mouse: Found scroll wheel(s)
    (--) evdev: Logitech USB Optical Mouse: Found relative axes
    (--) evdev: Logitech USB Optical Mouse: Found x and y relative axes
    (II) evdev: Logitech USB Optical Mouse: Configuring as mouse
    (II) evdev: Logitech USB Optical Mouse: Adding scrollwheel support
    (**) evdev: Logitech USB Optical Mouse: YAxisMapping: buttons 4 and 5
    (**) evdev: Logitech USB Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "Logitech USB Optical Mouse" (type: MOUSE, id 9)
    (II) evdev: Logitech USB Optical Mouse: initialized for relative axes.
    (**) Logitech USB Optical Mouse: (accel) keeping acceleration scheme 1
    (**) Logitech USB Optical Mouse: (accel) acceleration profile 0
    (**) Logitech USB Optical Mouse: (accel) acceleration factor: 2.000
    (**) Logitech USB Optical Mouse: (accel) acceleration threshold: 4
    (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/mouse0)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device Laptop_Integrated_Webcam_2M (/dev/input/event11)
    (**) Laptop_Integrated_Webcam_2M: Applying InputClass "evdev keyboard catchall"
    (II) Using input driver 'evdev' for 'Laptop_Integrated_Webcam_2M'
    (**) Laptop_Integrated_Webcam_2M: always reports core events
    (**) evdev: Laptop_Integrated_Webcam_2M: Device: "/dev/input/event11"
    (--) evdev: Laptop_Integrated_Webcam_2M: Vendor 0xc45 Product 0x6430
    (--) evdev: Laptop_Integrated_Webcam_2M: Found keys
    (II) evdev: Laptop_Integrated_Webcam_2M: Configuring as keyboard
    (II) XINPUT: Adding extended input device "Laptop_Integrated_Webcam_2M" (type: KEYBOARD, id 10)
    (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    (**) AT Translated Set 2 keyboard: always reports core events
    (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    (--) evdev: AT Translated Set 2 keyboard: Found keys
    (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
    (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event14)
    (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
    (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
    (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
    (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
    (II) Module synaptics: vendor="X.Org Foundation"
    compiled for 1.15.0, module version = 1.7.3
    (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
    (**) SynPS/2 Synaptics TouchPad: always reports core events
    (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
    (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5782 (res 57)
    (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4972 (res 96)
    (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
    (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
    (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
    (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
    (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    (**) SynPS/2 Synaptics TouchPad: always reports core events
    (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 12)
    (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
    (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
    (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.036
    (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
    (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
    (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
    (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
    (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
    (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
    (II) config/udev: Adding input device PC Speaker (/dev/input/event2)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device Dell WMI hotkeys (/dev/input/event6)
    (**) Dell WMI hotkeys: Applying InputClass "evdev keyboard catchall"
    (II) Using input driver 'evdev' for 'Dell WMI hotkeys'
    (**) Dell WMI hotkeys: always reports core events
    (**) evdev: Dell WMI hotkeys: Device: "/dev/input/event6"
    (--) evdev: Dell WMI hotkeys: Vendor 0 Product 0
    (--) evdev: Dell WMI hotkeys: Found keys
    (II) evdev: Dell WMI hotkeys: Configuring as keyboard
    (II) XINPUT: Adding extended input device "Dell WMI hotkeys" (type: KEYBOARD, id 13)
    (II) config/udev: removing device Logitech USB Optical Mouse
    (II) evdev: Logitech USB Optical Mouse: Close
    (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/mouse0)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/event1)
    (**) Logitech USB Optical Mouse: Applying InputClass "evdev pointer catchall"
    (II) Using input driver 'evdev' for 'Logitech USB Optical Mouse'
    (**) Logitech USB Optical Mouse: always reports core events
    (**) evdev: Logitech USB Optical Mouse: Device: "/dev/input/event1"
    (--) evdev: Logitech USB Optical Mouse: Vendor 0x46d Product 0xc05a
    (--) evdev: Logitech USB Optical Mouse: Found 3 mouse buttons
    (--) evdev: Logitech USB Optical Mouse: Found scroll wheel(s)
    (--) evdev: Logitech USB Optical Mouse: Found relative axes
    (--) evdev: Logitech USB Optical Mouse: Found x and y relative axes
    (II) evdev: Logitech USB Optical Mouse: Configuring as mouse
    (II) evdev: Logitech USB Optical Mouse: Adding scrollwheel support
    (**) evdev: Logitech USB Optical Mouse: YAxisMapping: buttons 4 and 5
    (**) evdev: Logitech USB Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "Logitech USB Optical Mouse" (type: MOUSE, id 9)
    (II) evdev: Logitech USB Optical Mouse: initialized for relative axes.
    (**) Logitech USB Optical Mouse: (accel) keeping acceleration scheme 1
    (**) Logitech USB Optical Mouse: (accel) acceleration profile 0
    (**) Logitech USB Optical Mouse: (accel) acceleration factor: 2.000
    (**) Logitech USB Optical Mouse: (accel) acceleration threshold: 4
    (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    (II) intel(0): EDID vendor "SEC", prod id 21579
    (II) intel(0): Printing DDC gathered Modelines:
    (II) intel(0): Modeline "1600x900"x0.0 120.53 1600 1648 1680 2160 900 902 907 930 +hsync -vsync (55.8 kHz eP)
    (II) intel(0): Modeline "1600x900"x0.0 74.09 1600 1648 1680 1992 900 902 907 930 +hsync -vsync (37.2 kHz e)
    (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    setversion 1.4 failed: Permission denied
    (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    (II) config/udev: removing device Logitech USB Optical Mouse
    (II) evdev: Logitech USB Optical Mouse: Close
    (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/mouse0)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/event1)
    (**) Logitech USB Optical Mouse: Applying InputClass "evdev pointer catchall"
    (II) Using input driver 'evdev' for 'Logitech USB Optical Mouse'
    (**) Logitech USB Optical Mouse: always reports core events
    (**) evdev: Logitech USB Optical Mouse: Device: "/dev/input/event1"
    (--) evdev: Logitech USB Optical Mouse: Vendor 0x46d Product 0xc05a
    (--) evdev: Logitech USB Optical Mouse: Found 3 mouse buttons
    (--) evdev: Logitech USB Optical Mouse: Found scroll wheel(s)
    (--) evdev: Logitech USB Optical Mouse: Found relative axes
    (--) evdev: Logitech USB Optical Mouse: Found x and y relative axes
    (II) evdev: Logitech USB Optical Mouse: Configuring as mouse
    (II) evdev: Logitech USB Optical Mouse: Adding scrollwheel support
    (**) evdev: Logitech USB Optical Mouse: YAxisMapping: buttons 4 and 5
    (**) evdev: Logitech USB Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "Logitech USB Optical Mouse" (type: MOUSE, id 9)
    (II) evdev: Logitech USB Optical Mouse: initialized for relative axes.
    (**) Logitech USB Optical Mouse: (accel) keeping acceleration scheme 1
    (**) Logitech USB Optical Mouse: (accel) acceleration profile 0
    (**) Logitech USB Optical Mouse: (accel) acceleration factor: 2.000
    (**) Logitech USB Optical Mouse: (accel) acceleration threshold: 4

  • [SOLVED] systemd display-manager.service problem

    Hi!
    After the upgrade of systemd, i noticed today this error in dmesg:
    systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
    systemctl status display-manager.service
    display-manager.service
    Loaded: error (Reason: No such file or directory)
    Active: inactive (dead)
    The strange thing is why systemd tries to load a service that doesn't exist! And what is this unit for? I'm using slim to load my xfce desktop, and everything works well...
    Any idea?
    Thanks!
    EDIT: Uhm, may be the alias in slim.service, set to display-manager.service, is the problem? Or may be this is not a problem, but it is its normal behaviour , and i misunderstood something! Is it?
    Last edited by nierro (2012-07-15 17:13:42)

    nierro wrote:
    Hi!
    After the upgrade of systemd, i noticed today this error in dmesg:
    systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
    systemctl status display-manager.service
    display-manager.service
    Loaded: error (Reason: No such file or directory)
    Active: inactive (dead)
    The strange thing is why systemd tries to load a service that doesn't exist! And what is this unit for? I'm using slim to load my xfce desktop, and everything works well...
    Any idea?
    Thanks!
    EDIT: Uhm, may be the alias in slim.service, set to display-manager.service, is the problem? Or may be this is not a problem, but it is its normal behaviour , and i misunderstood something! Is it?
    There has been a change regarding display managers. up until now they were WantedBy graphical.target, which was kind of stupid because this allowed you to enable multiple display managers.
    Instead graphical.target now Wants display-manager.service and all display managers are supposed to install the appropriate Alias. Afaik all display manager service files have been updated ragarding this and a "systemctl reenable slim.service" should fix it.

  • [NEWS] LXDM – New Display Manager

    LXDE finally has its own display manager, lxdm, and doesn't need to rely on GDM or KDM from now on.
    To see is to believe.
    lxdm screenshot
    Recently, a new developer dgod from China joined us and contributed a new project, lxdm, a lightweight display manager aimed to replace gdm. Later, I modified his code, and re-implement the UI with GTK+. So, this is how it look like. It's still in very early stage, and things are not expected to work correctly. For now, it only work smoothly with Fedora. On Ubuntu or others, there might be some issues. However we'll work on fixing those problems and finish this new display manager.
    The code is in LXDE svn repo. For someone who wants to try it, use at you own risk and have fun!
    Links
    * LXDE Wiki: http://wiki.lxde.org/en/LXDM
    Source: http://blog.lxde.org/?p=531
    Source: http://blog.lxde.org/?p=531
    Source: http://blog.lxde.org/?p=531
    Source: http://blog.lxde.org/?p=531

    http://aur.archlinux.org/packages.php?ID=30050 for archers

  • Logitech F310 Gamepad only works with Display Manager [SOLVED]

    So I bought a couple Logitech F310 gamepads, for, well, gaming, and I had a hell of a time trying to get my games to respond to them. I run XMonad, and boot it directly via xinit. On a whim, I tried activating gdm and logging into a gnome session, and presto, my controllers worked. I got a bare bones xmonad session file going, and eventually switched over to lxdm just for testing purposes, and the controllers would continue to work like a charm.
    Now, I would prefer to not to have to use a display manager, though it's not a deal breaker (though they seem to introduce other problems -- now systemd hangs on shutdown when I'm using lxdm). Still, I'm curious as to what kind of an effect the mere activation of a display manager could have on the system which would cause it to properly recognize the gamepads. To be clear, without a display manager, the pads are detected, are correctly listed in /dev/input. and I can even run jstest and see that they respond well (though they seem oddly configured), but games will not recognize their existence, and so they're effectively useless.
    Any help would be appreciated.
    Last edited by alex404 (2014-04-08 21:16:07)

    It would appear that this is related to this post as well:
    https://bbs.archlinux.org/viewtopic.php?pid=1368721
    Here's a list of processes that run when I'm using LXDM, versus XMonad:
    kworker/u16:8
    kworker/6:2
    irq/46-iwlwifi
    login
    xinit
    irq/44-iwlwifi
    kworker/2:2
    kworker/2:3
    lxdm-binary
    lxdm-session
    gnome-keyring-d
    pulseaudio
    rtkit-daemon
    gconf-helper
    gconfd-2
    The modules being listed are the same. Definitely an odd problem. I'm just resorting to using LXDM for now, even though I'd rather not.

  • Service Manager Portal not displaying VM console and related details

    Hi All,
    We have deployed private cloud with system center products using Cloud Services Process Pack and we have deployed Service Manger portal for VM provisioning in Cloud
    The Service Manger portal does not display VM console and VM details
    I have following queries
    How to take remote console of VM deployed by end user through service manager portal
    How will user come to know quota limit utilized in cloud under his account
    The VM are deployed through SCSM portal are in shutdown state how to auto start the VM after provisioning
    Please help since we are not able to find any solution for the above
    Appreciate if any workaround is available for the same
    Thanks
    Manzoor Ahmed

    The component of System Center that is capable to give console access to your VMs, is App Controller.
    Once the user are logged in here, they should see their quota, limits and resources available.
    Yes, the VMs are powered off by default when using the CSPP. You can edit the runbooks and add a task that will start them after provisioning.
    For your information:
    Many things has changed since the release of Cloud Service Process Pack. A new set of tools are provided with Windows Azure Pack to have a streamlined Infrastructure as a Service offering within the enterprise. Windows Azure Pack will leverage VMM (in the
    same way as SCSM does) but in conjunction with SPF (component within Orchestrator) to give you a framework that is identical to Windows Azure (Microsoft's own cloud) running on-premise.
    -kn
    Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

  • [SOLVED] K Display Manager won't start up at boot

    EDIT: I'm retarded. I hadn't even checked to see xorg-server was installed. It wasn't.
    Hi,
    I just installed package group kde-meta for a full KDE installation including KDM, installed xf86-video-ati for video card drivers, and then ran:
    systemctl enable kdm.service
    systemctl disable getty@tty1
    Now, when I start up, I just get the messages "Starting K Display Manager..." and "Started K Display Manager." but the X server doesn't start up at all. Those messages are left on the screen. Using 'systemctl start kdm.service' does nothing. Literally no output or anything.
    What should I do? Also, I know there's not much information, but if you give me some commands I can get some logs. I just don't know where to look for them...
    Thanks in advance.
    Last edited by Archimaredes (2013-01-25 19:06:33)

    I've just been experiencing a similar issue. The local Apple Store just replaced my logic board (was overheating without secondary cooling when processor was under a full load, and the fans weren't kicking) for a little more trivial problem. Now that I just got it back, it ran for about 5 minutes before it spontaneously shutdown. I started it back immediately after that, and it went for only another couple minutes before it gave up yet again. After that, it just plain old wouldn't boot. Tried to reset the PRAM...wouldn't even get that far. Tried to reset the PMU...saw no change.
    Whenever I try to boot it, I can hear the fan on the left start up and the hard drive attempt to spin up. Shortly after, it makes a subtle chirp-like noise and promptly shuts off. Mind you, I'm getting no display or anything 'cept these noises. I'm trying to get it to the point that I can run the diagnostics program from the OS X disc, but I think I'm going to be lucky to even get that far.
    I'm thinking twice before taking my MacBook Pro to get serviced for something that isn't work-impairing now!

  • [SOLVED] Can't load up display manager. Getting '... File Exists."

    I'm trying to get `slim` working by the systemd method, but I get the following:
    [root@arch ~]# systemctl enable slim.service
    Failed to issue method call: File exists
    I've tried other display managers like qingy, lxdm, etc. and they all provide this same message. I was also able to get the display manager to work using the `inittab` method, but I'm trying to have a full systemd integration.
    Not sure if it matters, but I was previously able to get the above `systemctl enable` command to work with gdm. Later, I decided that I wanted a more lightweight display manager so I switched to `slim` and proceeded to uninstall `gdm`. However, it now seems I'm unable to `systemctl enable` any display manager. I appreciate your help!
    Last edited by nil (2012-10-21 18:47:03)

    I have the same problem. I uninstalled lightdm and installed gdm and not I can't seem to enable gdm. It starts fine.
    [arch@arch ~]$ systemctl list-unit-files | grep lightdm
    [arch@arch ~]$ systemctl list-unit-files | grep gdm
    gdm.service disabled
    [arch@arch ~]$ systemctl list-unit-files | grep display
    display-manager.service enabled
    [arch@arch ~]$ sudo systemctl disable display-manager.service
    Failed to issue method call: No such file or directory
    [arch@arch ~]$ sudo systemctl disable lightdm.service
    Failed to issue method call: No such file or directory
    [arch@arch ~]$ sudo systemctl disable gdm.service
    [arch@arch ~]$ sudo systemctl enable gdm.service
    Failed to issue method call: File exists
    [arch@arch ~]$ systemctl list-unit-files | grep gdm
    gdm.service disabled

Maybe you are looking for

  • Unable to finish off video.

    I've just finished making a video and its unable to finalize, or export or publish etc. and it says that the project is unable to load because of an error or something? ("The movie could not be exported because an error occurred. (-108)")

  • Getting Stuck in Start-up

    I recently did the weekly update on my computer and my macbook froze during the process. I had to shut down my computer by holding down the power button. I then tried to start it back up, and it gets stuck in the start up screen with the apple. It is

  • Is it possible to rotate video horiz/vert?

    As a photographer, I frequently turn my camera vertically to shoot. Well, the new camera has video capabilities, and I did the same thing without thinking. Is there a way to rotate the video clip the way photos can be rotated? I have checked QTPro an

  • Re:ALV Header Text

    Hi, i am using Reuse_alv_grid_display FM to display the output.I want my header-text in the following format.                                  STORAGE LOCATION       Mat no                            L1      L2      L3                    Total Quanti

  • Running total with Layout Editor with BI Publisher 11g

    Hello, I'm trying to create a report with BI Publisher Layout Editor using the "running total" option. My XML looks like this: <G_1> <REGION>MZ</REGION> <G_2> <INVOICE_NB>1</INVOICE_NB> <VALUE>1000</VALUE> </G_2> <G_2> <INVOICE_NB>2</INVOICE_NB> <VAL