LinuxQuestions.org - [SOLVED] X suddenly stopped working

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - X suddenly stopped working - Failed to activate core devices (https://www.linuxquestions.org/questions/slackware-14/x-suddenly-stopped-working-failed-to-activate-core-devices-845044/)

X suddenly stopped working - Failed to activate core devices

Booting up this morning, no problem. But I accidentally let my laptop go into suspend mode, which doesn't work, so I had to force a restart (Suspend mode on my laptop won't allow me to wake it up again).

Now, on rebooting, X doesn't work. I usually boot to RL3 then use startx. Now it just flashes the screen then gives me this error -

Code:



(EE) Error compiling keymap (server-0)

(EE) XKB: Couldn't compile keymap

XKB: Failed to compile keymap

Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.



Fatal server error:

Failed to activate core devices.



Please consult the The X.Org Foundation support 

at http://wiki.x.org

for help. 

Please also check the log file at "/var/log/Xorg.0.log" for additional information.

..and from Xorg.0.log -

Code:

(II) intel(0): Initializing HW Cursor

(II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.

(==) intel(0): DPMS enabled

(==) intel(0): Intel XvMC decoder enabled

(II) intel(0): Set up textured video

(II) intel(0): Set up overlay video

(II) intel(0): [XvMC] i965_xvmc driver initialized.

(II) intel(0): direct rendering: DRI2 Enabled

(--) RandR disabled

(II) Initializing built-in extension Generic Event Extension

(II) Initializing built-in extension SHAPE

(II) Initializing built-in extension MIT-SHM

(II) Initializing built-in extension XInputExtension

(II) Initializing built-in extension XTEST

(II) Initializing built-in extension BIG-REQUESTS

(II) Initializing built-in extension SYNC

(II) Initializing built-in extension XKEYBOARD

(II) Initializing built-in extension XC-MISC

(II) Initializing built-in extension XINERAMA

(II) Initializing built-in extension XFIXES

(II) Initializing built-in extension RENDER

(II) Initializing built-in extension RANDR

(II) Initializing built-in extension COMPOSITE

(II) Initializing built-in extension DAMAGE

(II) AIGLX: enabled GLX_MESA_copy_sub_buffer

(II) AIGLX: enabled GLX_SGI_make_current_read

(II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects

(II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/i965_dri.so

(II) GLX: Initialized DRI2 GL provider for screen 0

(II) intel(0): Setting screen physical size to 338 x 211

(EE) Error compiling keymap (server-0)

(EE) XKB: Couldn't compile keymap

XKB: Failed to compile keymap

Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.



Fatal server error:

Failed to activate core devices.



Please consult the The X.Org Foundation support 

        at http://wiki.x.org

 for help. 

Please also check the log file at "/var/log/Xorg.0.log" for additional information.

If I su - to root and then do "init 4", I get to xdm, and I can log in. X then starts, but with no sound, wrong keymaps, launchers not working; all sorts of things wrong.

If I startx as root I get a normal desktop. I have tried copying root's xinitrc to /home/spoovy, but makes no difference.

Seems like a permissions thing, but what? I can't think of anything I changed that might've broken it.

What on earth is going on here?

Thanks in advance

Spoov

This problem (or a very similar one it would appear) has cropped up before -

http://www.linuxquestions.org/questi...errors-833887/

It was suggested there that the questioner supply the following info, so I am doing so here -

Code:

root@poppy:/home/spoovy# egrep 'WW|EE' /var/log/Xorg.0.log

        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.

(WW) The directory "/usr/share/fonts/local" does not exist.

(WW) The directory "/usr/share/fonts/CID" does not exist.

(WW) The directory "/usr/share/fonts/local" does not exist.

(WW) The directory "/usr/share/fonts/CID" does not exist.

(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.

(WW) Disabling Mouse0

(WW) Disabling Keyboard0

(II) Loading extension MIT-SCREEN-SAVER

My mistake, sorry all. Problem was that the / dir was full.

live n learn..

X refuses to start

Spoovy wrote, "Problem was that the / dir was full."

Thanks, mate, for posting this! I had the same problem with X refusing to start (on Fedora 14) and it was due to the same problem: a 100% full root.

Even long-time Linux users learn stuff every day.

Could you elaborate on what you meant by the directory was full? Which directory and how did you clear it? Thanks a lot!

The "root" directory, aka "/", meaning the partition on which the core filesystem was installed. Xorg needs to write data to the drive when it starts up; since the drive was completely full, it failed. This could be remedied by deleting files out of the /tmp directory, assuming /tmp is on the same partition as the root filesystem.

can someone teach me step by step how to delete files out of the /tmp directory? I am newbie to this software and i hope someone can help me with this. Thanks

If you are using Slackware, you can solve the problem permanently ...

Code:

# > /etc/rc.d/rc.local_shutdown

# chmod a+rx /etc/rc.d/rc.local_shutdown

# cat <<EOT >/etc/rc.d/rc.local_shutdown

#!/bin/sh

echo ":: cleaning up /tmp ..."

/usr/bin/find -mindepth 1 -maxdepth 1 -print0 | /usr/bin/xargs -r0 /bin/rm -rf

EOT

#

and then reboot ...

I'm using ubuntu server.

cd /tmp when you are inside /tmp "rm file1" "rm file2" etc. minus the quotes.

Quote:

Originally Posted by perbh (Post 5018596)

If you are using Slackware, you can solve the problem permanently ...

Code:

# > /etc/rc.d/rc.local_shutdown

# chmod a+rx /etc/rc.d/rc.local_shutdown

# cat <<EOT >/etc/rc.d/rc.local_shutdown

#!/bin/sh

echo ":: cleaning up /tmp ..."

/usr/bin/find -mindepth 1 -maxdepth 1 -print0 | /usr/bin/xargs -r0 /bin/rm -rf

EOT

#

and then reboot ...

I know this is a late reply, but this doesn't specify that the find should start in /tmp.

You might end up deleting your entire disk :-(

Quote:

Originally Posted by leifnel (Post 5966441)

I know this is a late reply, but this doesn't specify that the find should start in /tmp.

You might end up deleting your entire disk :-(

Well... this is a valid reason to necropost if I've ever seen one.

Easy Solution - Buy a larger drive and clone your old one while making each partition substantially larger These days even 200GB is tiny and cheap. In fact a quick search had the top hit for a WD Blue 7200rpm 1TB SATA Brand New full size hdd from Amazon for 50bux USD.

Quote:

Originally Posted by enorbet (Post 5966444)

Welcome to the crypt.

When the disk runs full, You might start by investigating why. It could for instance be a log cleanup failure, in which the problem will just reappear later.