Re: fedup 20 -> 21 -> xinit -> KDE -> open /dev/fb0: No such file or directory
by Ed Greshko
On 07/28/15 09:50, richard emberson wrote:
>
> grep "input device" /var/log/Xorg.0.log | grep XINPUT
> <nothing found>
>
> Its a Jetta laptop with touch pad (which, like the usb optical mouse, also does not work) and builtin keyboard.
What is in your /etc/X11/xorg.conf ? It should only contain....
# RPM Fusion - nvidia-xorg.conf
#
Section "Device"
Identifier "Videocard0"
Driver "nvidia"
EndSection
Also, what files do you have in the /etc/X11/xorg.conf.d directory?
[egreshko@meimei X11]$ ls -l xorg.conf.d/
total 12
-rw-r--r--. 1 root root 161 Dec 26 2012 00-anaconda-keyboard.conf
-rw-r--r--. 1 root root 108 Dec 2 2013 00-avoid-glamor.conf
-rw-r--r--. 1 root root 178 Feb 7 2014 99-nvidia.conf
I find the following odd in your log file....
>
> [ 10029.383] (==) Matched nvidia as autoconfigured driver 0
> [ 10029.383] (==) Matched nouveau as autoconfigured driver 1
> [ 10029.383] (==) Matched nv as autoconfigured driver 2
> [ 10029.383] (==) Matched nouveau as autoconfigured driver 3
> [ 10029.383] (==) Matched nv as autoconfigured driver 4
> [ 10029.383] (==) Matched modesetting as autoconfigured driver 5
> [ 10029.383] (==) Matched fbdev as autoconfigured driver 6
> [ 10029.383] (==) Matched vesa as autoconfigured driver 7
I don't see any mention of nouveau in my log files except in the kernel command line.
--
If I wanted a blog or social media I'd go elsewhere
8 years, 8 months
fedup 20 -> 21 -> xinit -> KDE -> open /dev/fb0: No such file or directory
by Rich Emberson
Still no mouse or keyboard. Don't know if this is the problem.
from /var/log/Xorg.0.log
START
[ 96.019] (II) Loading sub module "fb"
[ 96.019] (II) LoadModule: "fb"
[ 96.020] (II) Loading /usr/lib64/xorg/modules/libfb.so
[ 96.030] (II) Module fb: vendor="X.Org Foundation"
[ 96.030] compiled for 1.17.2, module version = 1.0.0
[ 96.030] ABI class: X.Org ANSI C Emulation, version 0.4
[ 96.030] (WW) Unresolved symbol: fbGetGCPrivateKey
[ 96.030] (II) Loading sub module "wfb"
[ 96.030] (II) LoadModule: "wfb"
[ 96.030] (II) Loading /usr/lib64/xorg/modules/libwfb.so
[ 96.041] (II) Module wfb: vendor="X.Org Foundation"
[ 96.041] compiled for 1.17.2, module version = 1.0.0
[ 96.041] ABI class: X.Org ANSI C Emulation, version 0.4
[ 96.041] (II) Loading sub module "ramdac"
[ 96.041] (II) LoadModule: "ramdac"
[ 96.041] (II) Module "ramdac" already built-in
[ 96.068] (WW) Falling back to old probe method for modesetting
[ 96.068] (WW) Falling back to old probe method for fbdev
[ 96.068] (II) Loading sub module "fbdevhw"
[ 96.068] (II) LoadModule: "fbdevhw"
[ 96.068] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[ 96.082] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 96.082] compiled for 1.17.2, module version = 0.0.2
[ 96.082] ABI class: X.Org Video Driver, version 19.0
[ 96.082] (EE) open /dev/fb0: No such file or directory
[ 96.082] (WW) Falling back to old probe method for vesa
[ 96.082] (II) NVIDIA(0): Creating default Display subsection in Screen
section
"Default Screen Section" for depth/fbbpp 24/32
[ 96.082] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 96.082] (==) NVIDIA(0): RGB weight 888
[ 96.082] (==) NVIDIA(0): Default visual is TrueColor
......
END
Thanks
Richard
8 years, 8 months
fedup 20 -> 21 -> xinit -> KDE -> No mouse/keyboard input
by Rich Emberson
Thanks for the suggestion.
Contents of /var/cache/akmods/akmods.log
START
2015/07/25 16:06:18 akmods: Checking kmods exist for 4.0.8-200.fc21.x86_64
2015/07/25 16:06:18 akmods: Building and installing nvidia-340xx-kmod
2015/07/25 16:06:18 akmods: Building RPM using the command
'/bin/akmodsbuild --target x86_64 --kernels 4.0.8-200.fc21.x86_64
/usr/src/akmods/nvidia-340xx-kmod.latest'
2015/07/25 16:07:03 akmods: Installing newly built rpms
2015/07/25 16:07:03 akmods: DNF detected
2015/07/25 16:07:20 akmods: Successful.
2015/07/25 17:22:20 akmods: Checking kmods exist for 4.0.8-300.fc22.x86_64
2015/07/25 17:22:20 akmods: Building and installing nvidia-340xx-kmod
2015/07/25 17:22:20 akmods: Building RPM using the command
'/bin/akmodsbuild --target x86_64 --kernels 4.0.8-300.fc22.x86_64
/usr/src/akmods/nvidia-340xx-kmod.latest'
2015/07/25 18:07:53 akmods: Checking kmods exist for 4.0.8-300.fc22.x86_64
2015/07/25 18:07:53 akmods: Building and installing nvidia-340xx-kmod
2015/07/25 18:07:54 akmods: Building RPM using the command
'/bin/akmodsbuild --target x86_64 --kernels 4.0.8-300.fc22.x86_64
/usr/src/akmods/nvidia-340xx-kmod.latest'
2015/07/26 14:05:01 akmods: Checking kmods exist for 4.0.8-300.fc22.x86_64
2015/07/26 14:05:01 akmods: Building and installing nvidia-340xx-kmod
2015/07/26 14:05:01 akmods: Building RPM using the command
'/bin/akmodsbuild --target x86_64 --kernels 4.0.8-300.fc22.x86_64
/usr/src/akmods/nvidia-340xx-kmod.latest'
2015/07/26 14:05:47 akmods: Installing newly built rpms
2015/07/26 14:05:47 akmods: DNF detected
2015/07/26 14:06:00 akmods: Successful.
END
ran:
/usr/sbin/akmods --force
and now the file has the additional line:
2015/07/27 14:54:21 akmods: Checking kmods exist for 4.0.8-300.fc22.x86_64
Still no mouse or keyboard.
Thanks
Richard
8 years, 8 months
dnf failed
by Patrick Dupre
Hello,
I run dnf update.
At package 3935/4000, it failed, probably because a network issue
(timeout)
I am surprise than all the downloaded packages have be erased.
When I restarted dnf update, it restart from scratch.
Why?
It could have just restart and continue downloading the missing
65 packages!
Regards.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
8 years, 8 months
Upgrade to fedora 22
by Patrick Dupre
Hello,
After I upgrade a fedora 20 to fedora 22, I run (by mistake)
yum update.
It is now running for more than 5 hours (on a machine 10 year old
with 3G of RAM and plenty of space on the disk). It looks like that it is stock on
Processing Dependency: xz-libs (x82-32)
I do not see anything else wrong!
Should I be more patient, or should I kill the process and run dnf?
Thank.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
8 years, 8 months
How to hide on desktop unmounted partitions
by François Patte
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bonjour,
I have on my disks some partitions which are not mounted at boot time
and they appear as icons on the desktop of every user... I want to
hide them.
Before systemd, I added some rules in udev directories
(/etc/udev/rules.d) to hide these partions:
KERNEL=="sda1", ENV{UDISKS_PRESENTATION_HIDE}="1"
KERNEL=="sda2", ENV{UDISKS_PRESENTATION_HIDE}="1"
ACTION=="add", KERNEL=="0000:00:02.0", SUBSYSTEM=="pci", RUN+="/bin/sh
- -c 'echo 1 > /sys/bus/pci/devices/0000:00:02.0/remove'"
And partitions sda1 and sda2 do not appear on desktop...
Is it possible to do the same with systemd-udevd? What is the right
syntax?
One more question: these partitions are members of raid arrays and lvm
groups, is it possible to use md2 or /dev/mapper/foo instead of sda1,
sda2....
Thank you for helping (I am very new to systemd...)
- --
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 8394 5849
http://www.math-info.univ-paris5.fr/~patte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlW1HtIACgkQdE6C2dhV2JVIXACgxbPjbAL7f9HO97iY1witKrza
QWkAoLzjouF+AOxTntLcryUktoVSd78o
=6SuX
-----END PGP SIGNATURE-----
8 years, 8 months
printing impossible
by François Patte
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bonjour,
What wrong with cups/ghostscript? I am unable to print on my system
(fedora 21) message:
ghostscript quit unexpectedly
ghostscript-core 9.15.6.fc21.x86_64
Thank you.
- --
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 8394 5849
http://www.math-info.univ-paris5.fr/~patte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlWzw8QACgkQdE6C2dhV2JUi/wCeNULg8AaaWO9w5MiEMz5yNJLd
WdAAn1JE2rgY0+uszvHtr+3ego3MFdBb
=EIZ8
-----END PGP SIGNATURE-----
8 years, 8 months
OT - NFS group ignored
by Emmett Culley
I just noticed that when accessing an NFS mount, the group is ignored.
For example, on the server that shares the files via NFS that lists from the NFS client as:
$ ls -l/nfs/web
-rw-rw-r-- 1 root web_prog 491 Oct 16 2012 parse.php
$ mount
web:/ on /lvh1/web type nfs4 (rw,noatime,vers=4.0,rsize=524288,wsize=524288,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.6.12,local_lock=none,addr=192.168.6.232)
A user on the client machine that is a member of group web_prog cannot write the file (parse.php). If the user is changed from root to the client user's UID via chown on the server, the user on the client machine can then write the file.
The server is on CentOS 7 and the client is on Fedora 21. If I do the same test from a CentOS 7 or CentOS 6 machine client, it works as expected. That is, the group permissions are honoured by the NFS client on those non-Fedora machines.
So, I figure there is something wrong with my Fedora NFS configuration. Nothing shows up that is related to this issue when searching the Internet.
What I have tried:
Insure that Domain in /etc/idmapd.conf is the same on both client and server. Though the fact that the user ID is honoured would indicate that is correct.
Insured that the numerical user ID and group ID match on both client and server, even though until now I always assumed that idmapd did not require the numerical IDs to match with NFS4
Any help would be appreciated.
Emmett
8 years, 9 months
fedup 20 -> 21 -> xinit -> KDE -> No mouse/keyboard input
by Rich Emberson
So, I am now at the point where xinit (calling startkde)
has the KDE screen appearing, but ...
The pointer-cursor appears but can not be moved by the mouse, and
(after some timeout and the login screen appears) keyboard
entry fails.
What does one do to enable both the mouse and keyboard.
Thanks
Richard
8 years, 9 months
fedup 20 -> 21 -> xinit -> error setting MTRR
by Rich Emberson
What is causing the MTRR error in the xinit output?
cat /proc/mtrr
reg00: base=0x000000000 ( 0MB), size= 4096MB, count=1: write-back
reg01: base=0x100000000 ( 4096MB), size= 1024MB, count=1: write-back
reg02: base=0x0c0000000 ( 3072MB), size= 1024MB, count=1: uncachable
Part of xinit output with a number of errors.
The MTRR error is the first one:
START xinit output
....
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Jul 26 11:27:32 2015
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
error setting MTRR (base = 0xfb000000, size = 0x00e00000, type = 1) Invalid
argument (22)
Failed to close file descriptor: Could not close fd 11
....
Failed to close file descriptor: Could not close fd 11
startkde: Starting up...
Qt: Session management error: networkIdsList argument is NULL
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Qt: Session management error: networkIdsList argument is NULL
kbuildsycoca5 running...
kf5.kded: kded module "proxyscout" has already been found using JSON
metadata, please don't install the now unneeded .desktop file
("kded/proxyscout.desktop").
kf5.kded: found kded module "statusnotifierwatcher" by prepending 'kded_'
to the library path, please fix your metadata.
....
powerdevil: No outputs have backlight property
"/home/emberson/.local/share/icc/.." is not an ICC profile
"/home/emberson/.local/share/icc/." is not an ICC profile
Qt: Session management error: networkIdsList argument is NULL
Service started, version: 6.2.0
QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought
it was ':1.27'
Unable to get EDID for output "default"
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it
was ':1.9'
Failed to create ICC profile on cmsCreateRGBProfile
....
Qt: Session management error: networkIdsList argument is NULL
Xlib: extension "GLX" missing on display ":0".
....
Could not initialize GLX
KCrash: Application 'krunner' crashing...
KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit
Invalid service name "/org/kde/polkit-kde-authentication-agent-1" using:
"/org/kde/polkitkdeauthenticationagent1"
kcminit not running? If we are running with mobile profile or in another
platform other than X11 this is normal.
....
kwin_core: screens: 1 desktops: 1
kwin_core: Done.
kwin_core: screens: 1 desktops: 1
kwin_core: Done.
Invalid pixmap specified.
....
kf5.kded: found kded module "touchpad" by prepending 'kded_' to the library
path, please fix your metadata.
Xlib: extension "GLX" missing on display ":0".
kmix: kmixd: Delayed initialization running now
kmix: kmixd: Delayed initialization done
Xlib: extension "GLX" missing on display ":0".
....
Application::crashHandler() called with signal 6; recent crashes: 1
KXMLGUI file found at deprecated location ("/usr/share/kmix/kmixui.rc") --
please use ${KXMLGUI_INSTALL_DIR} to install this file instead.
....
END xinit output
>From /var/log/X.org.0:
Why attempt to load nouveau and nv ?
Can not determine screen size.
START log
[ 109.258] (II) "glx" will be loaded by default.
[ 109.258] (II) LoadModule: "glx"
[ 109.278] (II) Loading /usr/lib64/nvidia-340xx/xorg/libglx.so
[ 110.766] (II) Module glx: vendor="NVIDIA Corporation"
[ 110.767] compiled for 4.0.2, module version = 1.0.0
[ 110.767] Module class: X.Org Server Extension
[ 110.771] (II) NVIDIA GLX Module 340.76 Thu Jan 22 11:24:42 PST 2015
[ 110.785] (==) Matched nouveau as autoconfigured driver 0
[ 110.785] (==) Matched nv as autoconfigured driver 1
[ 110.785] (==) Matched modesetting as autoconfigured driver 2
[ 110.785] (==) Matched fbdev as autoconfigured driver 3
[ 110.785] (==) Matched vesa as autoconfigured driver 4
[ 110.785] (==) Assigned the driver to the xf86ConfigLayout
[ 110.785] (II) LoadModule: "nouveau"
[ 110.820] (WW) Warning, couldn't open module nouveau
[ 110.820] (II) UnloadModule: "nouveau"
[ 110.820] (II) Unloading nouveau
[ 110.820] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 110.820] (II) LoadModule: "nv"
[ 110.821] (WW) Warning, couldn't open module nv
[ 110.821] (II) UnloadModule: "nv"
[ 110.821] (II) Unloading nv
[ 110.821] (EE) Failed to load module "nv" (module does not exist, 0)
[ 110.821] (II) LoadModule: "modesetting"
[ 110.821] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[ 110.828] (II) Module modesetting: vendor="X.Org Foundation"
[ 110.828] compiled for 1.17.2, module version = 1.17.2
[ 110.828] Module class: X.Org Video Driver
[ 110.828] ABI class: X.Org Video Driver, version 19.0
[ 110.828] (II) LoadModule: "fbdev"
[ 110.828] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so[
110.838] (II) Module fbdev: vendor="X.Org Foundation"
[ 110.838] compiled for 1.17.1, module version = 0.4.3
[ 110.838] Module class: X.Org Video Driver
[ 110.838] ABI class: X.Org Video Driver, version 19.0
[ 110.838] (II) LoadModule: "vesa"
[ 110.838] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[ 110.847] (II) Module vesa: vendor="X.Org Foundation"
[ 110.847] compiled for 1.17.1, module version = 2.3.2
[ 110.847] Module class: X.Org Video Driver
[ 110.847] ABI class: X.Org Video Driver, version 19.0
[ 110.847] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 110.847] (II) FBDEV: driver for framebuffer: fbdev
[ 110.847] (II) VESA: driver for VESA chipsets: vesa
[ 110.847] (--) using VT number 2
[ 110.853] (EE) open /dev/dri/card0: No such file or directory
[ 110.853] (WW) Falling back to old probe method for modesetting
[ 110.853] (EE) open /dev/dri/card0: No such file or directory
[ 110.853] (II) Loading sub module "fbdevhw"
[ 110.853] (II) LoadModule: "fbdevhw"
[ 110.853] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[ 110.869] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 110.869] compiled for 1.17.2, module version = 0.0.2
[ 110.869] ABI class: X.Org Video Driver, version 19.0
[ 110.869] (EE) open /dev/fb0: No such file or directory
[ 110.869] (WW) Falling back to old probe method for fbdev
[ 110.869] (II) Loading sub module "fbdevhw"
[ 110.869] (II) LoadModule: "fbdevhw"
[ 110.869] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[ 110.869] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 110.869] compiled for 1.17.2, module version = 0.0.2
[ 110.869] ABI class: X.Org Video Driver, version 19.0
[ 110.869] (EE) open /dev/fb0: No such file or directory
[ 110.869] (EE) Screen 0 deleted because of no matching config section.
[ 110.869] (II) UnloadModule: "modesetting"
[ 110.869] (EE) Screen 0 deleted because of no matching config section.
[ 110.869] (II) UnloadModule: "modesetting"
[ 110.869] (EE) Screen 0 deleted because of no matching config section.
[ 110.869] (II) UnloadModule: "fbdev"
[ 110.869] (II) UnloadSubModule: "fbdevhw"
[ 110.869] (II) Loading sub module "vbe"
[ 110.869] (II) LoadModule: "vbe"
[ 110.869] (II) Loading /usr/lib64/xorg/modules/libvbe.so
[ 110.880] (II) Module vbe: vendor="X.Org Foundation"
[ 110.880] compiled for 1.17.2, module version = 1.1.0
[ 110.880] ABI class: X.Org Video Driver, version 19.0
[ 110.880] (II) Loading sub module "int10"
[ 110.880] (II) LoadModule: "int10"
....
[ 111.491] (II) VESA(0): Total Memory: 224 64KB banks (14336kB)
[ 111.491] (II) VESA(0): <default monitor>: Using default hsync range of
31.50-48.00 kHz
[ 111.491] (II) VESA(0): <default monitor>: Using default vrefresh range
of 50.00-70.00 Hz
[ 111.491] (II) VESA(0): <default monitor>: Using default maximum pixel
clock of 65.00 MHz
[ 111.491] (WW) VESA(0): Unable to estimate virtual size
[ 111.491] (II) VESA(0): Not using built-in mode "1680x1050" (no mode of
this name)
[ 111.491] (II) VESA(0): Not using built-in mode "1280x1024" (no mode of
this name)
[ 111.491] (II) VESA(0): Not using built-in mode "1280x800" (no mode of
this name)
[ 111.491] (II) VESA(0): Not using built-in mode "1280x720" (no mode of
this name)
[ 111.491] (II) VESA(0): Not using built-in mode "1024x768" (no mode of
this name)
[ 111.491] (II) VESA(0): Not using built-in mode "800x600" (no mode of
this name)
[ 111.491] (II) VESA(0): Not using built-in mode "640x480" (no mode of
this name)
[ 111.491] (II) VESA(0): Not using built-in mode "640x400" (no mode of
this name)
[ 111.491] (II) VESA(0): Not using built-in mode "320x400" (no mode of
this name)
[ 111.491] (II) VESA(0): Not using built-in mode "320x240" (no mode of
this name)
[ 111.491] (II) VESA(0): Not using built-in mode "320x200" (no mode of
this name)
[ 111.491] (WW) VESA(0): No valid modes left. Trying less strict filter...
[ 111.491] (II) VESA(0): <default monitor>: Using hsync range of
31.50-48.00 kHz
[ 111.491] (II) VESA(0): <default monitor>: Using vrefresh range of
50.00-70.00 Hz
[ 111.491] (II) VESA(0): <default monitor>: Using maximum pixel clock of
65.00 MHz
[ 111.491] (WW) VESA(0): Unable to estimate virtual size
[ 111.491] (II) VESA(0): Not using built-in mode "1680x1050" (hsync out
of range)
[ 111.491] (II) VESA(0): Not using built-in mode "1280x1024" (hsync out
of range)
[ 111.491] (II) VESA(0): Not using built-in mode "1280x800" (hsync out of
range)
[ 111.491] (II) VESA(0): Not using built-in mode "640x400" (hsync out of
range)
[ 111.491] (II) VESA(0): Not using built-in mode "320x400" (hsync out of
range)
[ 111.491] (II) VESA(0): Not using built-in mode "320x240" (illegal
horizontal timings)
[ 111.491] (II) VESA(0): Not using built-in mode "320x200" (illegal
horizontal timings)
[ 111.491] (--) VESA(0): Virtual size is 1280x768 (pitch 1280)
[ 111.491] (**) VESA(0): *Built-in mode "1280x720"
[ 111.491] (**) VESA(0): *Built-in mode "1024x768"
[ 111.491] (**) VESA(0): *Built-in mode "800x600"
[ 111.491] (**) VESA(0): *Built-in mode "640x480"
[ 111.491] (==) VESA(0): DPI set to (96, 96)
[ 111.491] (II) VESA(0): Attempting to use 60Hz refresh for mode
"1024x768" (118)
[ 111.492] (II) VESA(0): Attempting to use 60Hz refresh for mode
"800x600" (115)
[ 111.492] (II) VESA(0): Attempting to use 60Hz refresh for mode
"640x480" (112)
[ 111.493] (**) VESA(0): Using "Shadow Framebuffer"
[ 111.493] (II) Loading sub module "shadow"
[ 111.493] (II) LoadModule: "shadow"
[ 111.493] (II) Loading /usr/lib64/xorg/modules/libshadow.so
[ 111.539] (II) Module shadow: vendor="X.Org Foundation"
[ 111.539] compiled for 1.17.2, module version = 1.1.0
[ 111.539] ABI class: X.Org ANSI C Emulation, version 0.4
[ 111.539] (II) Loading sub module "fb"
[ 111.539] (II) LoadModule: "fb"
[ 111.539] (II) Loading /usr/lib64/xorg/modules/libfb.so
[ 111.549] (II) Module fb: vendor="X.Org Foundation"
[ 111.549] compiled for 1.17.2, module version = 1.0.0
[ 111.549] ABI class: X.Org ANSI C Emulation, version 0.4
[ 111.549] (==) Depth 24 pixmap format is 32 bpp
[ 111.549] (II) Loading sub module "int10"
[ 111.549] (II) LoadModule: "int10"
[ 111.549] (II) Loading /usr/lib64/xorg/modules/libint10.so
[ 111.549] (II) Module int10: vendor="X.Org Foundation"
[ 111.549] compiled for 1.17.2, module version = 1.0.0
....
END log
This happens with kdm mananger enabled.
Thanks
Richard
8 years, 9 months