missing xorg drivers - "failed to load module" errors

bananabrain · 2010-09-12 12:15:01

Hi all,

My /var/log/Xorg.0.log shows a couple of errors as follows:

[ 56.404] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 56.405] (EE) Failed to load module "fbdev" (module does not exist, 0)

I can make these errors disappear just by installing packages xf86-video-vesa and xf86-video-fbdev but since I don't want or need these, I wondered if it's possible to tell the system not to try loading these drivers?

Thanks in advance.

x33a · 2010-09-12 12:23:37

Which graphics driver are you using?

karol · 2010-09-12 12:40:11

I think those errors are harmless.

bananabrain · 2010-09-12 13:55:26

I'm using xf86-video-ati on one machine, xf86-video-intel on another. Is that relevant to how I prevent some selected xorg modules from loading?

Yes, the errors aren't show-stoppers, but they are errors. As well as trying to better understand how to control X in this world of "disabling hot-plugging is not recommended!", I was also indulging my OCD.

Thanks for the replies guys.

mhertz · 2010-09-12 14:21:47

You can avoid those errors by specifically specifying a driver in xorg.conf(besides of course by installing vesa and fbdev!).

I have the same issue with an ati board and also had it on my previous nvidia board.

I must admit that I have no explenation for why the errors occure upon xorg auto-detection(without xorg.conf) and I would be happy if someone in the know could come with the answer to this ?

When reading Xorg.0.log, then it looks like it first lists the compatible drivers for the board in preffered order i.e. in my case 1. ati - 2. vesa - 3. fbdev, and then also that it selects the first choise i.e. the correct driver, but then why it insists upon also loading the other drivers additionally afterwards is a mystery to me?

I don't specify a driver in xorg.conf, as it loads the correct driver anyways, and then I just ignore those vesa and fbdev errors, but still, I would love to get to know the reason for those?

Last edited by mhertz (2010-09-12 14:33:20)

.:B:. · 2010-09-12 14:38:10

It's probably the fallback routine that (I suspect) is hardcoded into Xorg. Nothing to worry about, really.

mhertz · 2010-09-12 15:21:58

Thanks alot, mate - much appreciated!

CU, Martin.

skottish · 2010-09-12 15:31:01

When I used a /etc/X11/xorg.conf file, xorg still tried to auto-detect stuff regardless if I specied a driver or not. Now that I put my nVidia setup in /etc/X11/xorg.conf.d/10-monitor.conf, it stopped looking for additional drivers.

bananabrain · 2010-09-12 16:21:20

skottish wrote:

When I used a /etc/X11/xorg.conf file, xorg still tried to auto-detect stuff regardless if I specied a driver or not. Now that I put my nVidia setup in /etc/X11/xorg.conf.d/10-monitor.conf, it stopped looking for additional drivers.

Eureka - this seems to be it.

If autodetection is left to is own ways, the correct driver is loaded if it is available (in my case, intel) but an attempt is still made to load the unrequired vesa and fbdev modules. (Why? Probably just an effort at failsafe fallback as .:B:. suggests.)

If a driver is specified in /etx/X11/xorg.conf.d/??-monitor.conf, no attempt is made to load vesa or fbdev and you have two less "EE" in your log.

Thanks skottish.

mhertz · 2010-09-12 17:04:59

Hmm, strange... I can get those errors go away with adding a driver section to xorg.conf and nothing else, with both ati and nvidia boxes(without having made any changes to files in xorg.conf.d directory)... (just checked again and 100% reproducible)

Last edited by mhertz (2010-09-12 17:06:57)

bananabrain · 2010-09-12 17:53:42

mhertz wrote:

Hmm, strange... I can get those errors go away with adding a driver section to xorg.conf and nothing else, with both ati and nvidia boxes(without having made any changes to files in xorg.conf.d directory)... (just checked again and 100% reproducible)

Maybe either method works.
I don't have a traditional xorg.conf, but use the new xorg 1.8 structure under /etc/X11/xorg.conf.d.
Are you using both?

mhertz · 2010-09-13 07:32:14

No I don't use both.

I let xorg auto-detect everything and then for the parts xorg detects wrong or entirelly misses, I then add sections for in xorg.conf.

In my case then everything is auto-detected correctly and so I only mis danish keyboard layout and so that's the only thing I add to my xorg.conf(+enabling ctrl+alt+backspace for killing X quickly).

This is the recommended way, i.e. the xorg.conf.d directory should be left alone for the distribution to administer and xorg.conf should be used for user-specific changes, allthough you could still add a new custom config-file to xorg.conf.d instead of xorg.conf if preffering that, but I wouldn't recommend changing the actual configs the distro has placed in xorg.cond.d, because of the risk of those getting overridden upon upgrades.

Last edited by mhertz (2010-09-13 07:37:18)

Arch Linux

#1 2010-09-12 12:15:01

missing xorg drivers - "failed to load module" errors

#2 2010-09-12 12:23:37

Re: missing xorg drivers - "failed to load module" errors

#3 2010-09-12 12:40:11

Re: missing xorg drivers - "failed to load module" errors

#4 2010-09-12 13:55:26

Re: missing xorg drivers - "failed to load module" errors

#5 2010-09-12 14:21:47

Re: missing xorg drivers - "failed to load module" errors

#6 2010-09-12 14:38:10

Re: missing xorg drivers - "failed to load module" errors

#7 2010-09-12 15:21:58

Re: missing xorg drivers - "failed to load module" errors

#8 2010-09-12 15:31:01

Re: missing xorg drivers - "failed to load module" errors

#9 2010-09-12 16:21:20

Re: missing xorg drivers - "failed to load module" errors

#10 2010-09-12 17:04:59

Re: missing xorg drivers - "failed to load module" errors

#11 2010-09-12 17:53:42

Re: missing xorg drivers - "failed to load module" errors

#12 2010-09-13 07:32:14

Re: missing xorg drivers - "failed to load module" errors

Board footer