Weird things with Xorg on amd54
Hi all,
since the last days there appears a strange thing on my amd64-system. When I
boot up, neither kdm, xdm or gdm will start automatically. But when I start
them manually by using "/etc/init.d/kdm start", everything works fine.
I examined the log files, but the only strange thing I saw in Xorg.log was
this:
--------
**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "acer_laptop"
(**) Option "xkb_layout" "de"
(**) Option "xkb_options" "lv3:ralt_switch,terminate:ctrl_alt_bksp"
(II) UnloadModule: "synaptics"
(II) "Power Button": Close
(II) UnloadModule: "evdev"
(II) "Video Bus": Close
(II) UnloadModule: "evdev"
(II) "Power Button": Close
(II) UnloadModule: "evdev"
(II) "Sleep Button": Close
(II) UnloadModule: "evdev"
(II) "USB Mouse": Close
(II) UnloadModule: "evdev"
(II) "Acer Crystal Eye webcam ": Close
(II) UnloadModule: "evdev"
(II) "AT Translated Set 2 keyboard": Close
(II) UnloadModule: "evdev"
(II) "Macintosh mouse button emulation": Close
(II) UnloadModule: "evdev"
(II) "ACPI Virtual Keyboard Device": Close
(II) UnloadModule: "evdev"
(II) "Acer hotkey driver": Close
(II) UnloadModule: "evdev"
(WW) xf86CloseConsole: VT_WAITACTIVE failed: Interrupted system call
--------
Somehow the evdev-handler is unloading some modules. This is strange, as when
starting X manually (as described above) or via "startx", everything works fine
and those entries do not appear in Xorg.log.
So, what is the difference by starting X manually or via initsript at boot???
This appears only on my amd64-system, my 32-bit system is fine.
I would file a bugreport, but I could still not find out, which package is
responsible for this.
Any ideas?
Best regards
Hans
Reply to: