Failed services in runlevel 5: kbd

I use to see this error message while booting openSUSE 11.0 :
Failed services in runlevel 5: kbd

The error is still there now I’ve updated to 11.1. It does not seem to affect anything (if it’s related to keyboard, my keyboard is working properly).
I’m wondering what it means and how I can cleanup this error (?)

You could just open the runlevel editor in yast and disable it. Though you may just want to confirm it is. I think it is related keyboard and xorg now uses auto detecting.

Looking at cat /etc/rc.d/kbd it certainly seems to be, I would just try restarting it first, with
rckbd restart

Make sure it really is failing it’s just, if it is being used, could you actually get to the configuration without a keyboard. Entering the password would seem tricky to me.

You could just open the runlevel editor in yast and disable it … ] Looking at cat /etc/rc.d/kbd it certainly seems to be

Seen this in /etc/rc.d/kbd :eek: :


# Description:          Keyboard settings (don't disable!)

I would just try restarting it first, with rckbd restart


# rckbd restart
Loading console font lat9w-16.psfu  -m trivial G0:loadable
setfont: putfont: 256,8x16:  failed: -1
putfont: KDFONTOP: Invalid argument
setfont: putfont: 256,8x16:  failed: -1
putfont: KDFONTOP: Invalid argument
setfont: putfont: 256,8x16:  failed: -1
putfont: KDFONTOP: Invalid argument
setfont: putfont: 256,8x16:  failed: -1
putfont: KDFONTOP: Invalid argument
setfont: putfont: 256,8x16:  failed: -1
putfont: KDFONTOP: Invalid argument
setfont: putfont: 256,8x16:  failed: -1
putfont: KDFONTOP: Invalid argument                                  failed
Loading keymap i386/azerty/be-latin1.map.gz                          done
Loading compose table latin1.add                                     done
Start Unicode mode                                                   done

Sorry no just did a quick glance and from the looks of things isn’t completely failing. Though confirms what I thought disabling keyboard would of probably involved some work round.

Hopefully someone else can finish it off for you. You certainly now have a specific error to google.

What I saw after Googling a bit seems to indicate that it could be due to a bad xorg configuration.

I ran Sax2, check the keyboard settings, and found nothing wrong. Saved again, and no error shown.

Then I had a look at /var/log/Xorg.0.log and saw a few problems (only printing here the warning and error relative sections) :


(WW) The directory "/usr/share/fonts/local" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/PEX" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/latin2/misc" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/latin2/75dpi" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/latin2/100dpi" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/latin2/Type1" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/latin7/75dpi" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/baekmuk" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/japanese" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/kwintv" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/uni" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/CID" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/ucs/misc" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/ucs/75dpi" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/ucs/100dpi" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/hellas/misc" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/hellas/75dpi" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/hellas/100dpi" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/hellas/Type1" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/misc/sgi" does not exist.
	Entry deleted from font path.
(WW) The directory "/usr/share/fonts/xtest" does not exist.
	Entry deleted from font path.


(II) LoadModule: "type1"

(WW) Warning, couldn't open module type1
(II) UnloadModule: "type1"
(EE) Failed to load module "type1" (module does not exist, 0)


(EE) AIGLX error: dlopen of /usr/lib/dri/mga_dri.so failed (/usr/lib/dri/mga_dri.so: cannot open shared object file: No such file or directory)
(EE) AIGLX: reverting to software rendering
(II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so

So, missing fonts ?? Something else ?

Need to practise your google-fu :wink:

https://bugzilla.novell.com/show_bug.cgi?id=335267
Search string
putfont: KDFONTOP: Invalid argument - Google Search

Your aiglx errors are funny though do you have glxinfo rendering yes? Or is this to expected?

Erm, indeed :shame: :slight_smile:

Access Denied
Search string
putfont: KDFONTOP: Invalid argument - Google Search

Thanks ! I’m going to have a deep read.

Your aiglx errors are funny though do you have glxinfo rendering yes? Or is this to expected?

I don’t really know what this AIGLX is for, but I don’t have any display problem. The output of glxinfo seems right, though not talking too much for me.
Maybe this issue is due to my Matrox G400 DH (Dual Heads) board (?) Since I’ve updated to 11.1, I have a new “Display Settings” icon in the task bar (service). It’s look like a tool to move the desktop across multiple monitors; and if so, xorg is again assuming that I have 2 monitors connected to my gfx board (I have only one). I’ll check that later.

The error about loading a type1 module that is not available also make me curious. But again, that’s another (non-related) issue (so I put that on hold for the moment).

AIGLX is some kind of native compositing(I think) Wiki has a far better explanation than I could give. but if you have all the bling then I guess not.
glxinfo | grep rendering
Should give you yes but I know little about matrox cards.

As for the others one day I’ll find out what the type1 module is but across a variety of distro’s I’ve encountered it. I ignored them quite quickly, WW aren’t to be concerned with they are just warnings.

But EE are errors. Font paths I just edit them out of my xorg.conf ditto with the type1 module.

Edit…
As for google-fu I did the first error msg first, didn’t like the look. So tried the next one and got that google hit. I tend to look for as much as possible to start with slowly making it smaller. I also ignore distro’s and found the link from the arch forum.

Yes, it does.


 glxinfo | grep rendering
direct rendering: Yes

(Althought xorg failed to load /usr/lib/dri/mga_dri.so , it successfully fall back to /usr/lib/dri/swrast_dri.so )

I don’t worry too much for now about the other warnings and errors, as after all, I don’t experience any keyboard/mouse/display trouble.

(I’ve given you a 1 Rep. :wink: , but I don’t see where it shows.)

I’ve had that in my sig for ages lol I pay little attention to it. I don’t help for the rep points. Like you just giving back and after using a multiple of distro’s I find Suse relatively easy. Though I have to remember the Suse quirks. Quick chroot into Suse normally does that or just a look at file. I get more lost when i have to find a gui solution been a long time since I went that way.

Couldn’t really care less one way or the other not sure people judge on whether it has little green sqrs or not. Certainly I don’t, some of the guys from NTTP really know there stuff but they will never get rep points.

They actually show in your user control panel. With comments I’ll give you one as an example on the last post.