[clue-tech] Gentoo Xserver Error

[June Tate-Gans]

On Wed, Jan 13, 2010 at 11:51 PM, Jason Ash <wizardofki at gmail.com> wrote:
>

...snip...

> X.Org X Server 1.6.5
> Release Date: 2009-10-11
> X Protocol Version 11, Revision 0
> Build Operating System: Linux 2.6.31-gentoo-r6 i686
> Current Operating System: Linux tux2 2.6.31-gentoo-r6 #1 SMP Thu Jan
> 14 05:10:01 MST 2010 i686
> Build Date: 14 January 2010  04:33:18AM
>
>        Before reporting problems, check http://wiki.x.org
>        to make sure that you have the latest version.
> Markers: (--) probed, (**) from config file, (==) default setting,
>        (++) from command line, (!!) notice, (II) informational,
>        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jan 14 06:00:19 2010
> (==) Using default built-in configuration (39 lines)
> (EE) Failed to load module "i810" (module does not exist, 0)
> (EE) Failed to load module "vesa" (module does not exist, 0)
> (EE) Failed to load module "fbdev" (module does not exist, 0)
> FATAL: Module fbcon not found.

Looks like Xorg disagrees with your driver selection -- it's
attempting to load the i810 driver instead of the intel driver. You'll
probably want to setup an /etc/X11/xorg.conf file to include a Device
section with the line 'Driver "intel"' in it. I think the wiki page
mentions this just below the kernel config section. You'll probably
want to do this anyway to help improve your video performance (choice
of EXA or UXA acceleration -- UXA is faster if you have it).

> Setting master
> expected keysym, got XF86TouchpadToggle: line 122 of inet
> /etc/X11/xinit/xinitrc: line 58: twm: command not found
> /etc/X11/xinit/xinitrc: line 59: xclock: command not found
> /etc/X11/xinit/xinitrc: line 60: xterm: command not found
> /etc/X11/xinit/xinitrc: line 61: xterm: command not found
> /etc/X11/xinit/xinitrc: line 62: exec: xterm: not found

Seems here you've only emerged X itself. In Gentoo, you'll need to
emerge the packages you want -- remember that since X is a network
protocol, you can have a server on one machine and run all your apps
on a completely different one. As a result, you'll need to emerge any
core X apps you want by hand. I'm pointing this one out because some
folks tend to forget to emerge these things and it can increase the
frustration level a bit once you've actually got the X server working.

One other hint: if you're attempting to test your X config from the
command line by running X directly, make sure you add the -retro
command line option. The Xorg guys "helpfully" decided that showing a
black bear in a coal mine at midnight is more useful than actually
showing some sort of test pattern or mouse cursor. -retro alleviates
this by reverting to the old behavior of showing an X cursor and a
hash pattern on the root window.

Hope that helps some.

-- 
June Tate-Gans    | Don't try to outweird me, three-eyes. I get stranger things
www.theonelab.com | than you free with my breakfast cereal. -- Zaphod Beeblebrox