[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#435684: xserver-xorg: Error activating XKB configuration



Hi Brice, I'm frustrated with upgrades and Debian.

On 8/5/07, Brice Goglin <Brice.Goglin@ens-lyon.org> wrote:
> Kristis Makris wrote:
> > Every time I start x I get the following error message showing up in a
> > gnome window:
> >
>
> When did this problem start to occur? Did you upgrade some packages at
> this point? /var/log/dpkg.log and/or /var/log/aptitude might help.

I upgraded to Debian Etch. `apt-get dist-upgrade`

> Did you configure some keyboard stuff in gnome earlier? Are you running
> a plain Etch or do you have anything older or more recent? Your X
> packages seem to be from Etch. What about gnome? Can you upgrade the X
> packages to testing or unstable?

I'm running a plain Etch gnome and X.

I *can* upgrade the X packages to testing or unstable, but I *don't
want to*, given the current track record. e.g. the fact that upgrading
will bring down a ton of other ***unnecessary**** dependencies that
could have been avoided if the testing packages had been compiled
against the minimum dependencies (http://www.mkgnu.net/?q=node/103) of
the software. Not to mention that for the past 4 years after I start X
if I switch back to a text console the text looks jagged, permanently
(but not if the system is just booting).

At this point I want things to work as expected. It was working with
Debian 3.0. It should work now.

> > Section "InputDevice"
> > 	Identifier	"Generic Keyboard"
> > 	Driver		"kbd"
> > 	Option		"CoreKeyboard"
> > 	Option		"XkbRules"	"xorg"
> > 	Option		"XkbModel"	"pc104"
> > 	Option		"XkbLayout"	"dvorak"
> > 	Option		"XkbVariant"	"dvorak"
> > EndSection
> >
>
> Does it help if you comment XkbLayout and XkbVariant out?

I just tried this but it does not help. I still get the same error message.

> (unrelated) Remove GLcore from the module sections of your xorg.conf, it
> will loaded automatically when needed.

(unrelated) I just removed it.

> > (II) LoadModule: "speedo"
> > (WW) Warning, couldn't open module speedo
> > (II) UnloadModule: "speedo"
> > (EE) Failed to load module "speedo" (module does not exist, 0)
> >
>
> (unrelated) Remove speedo there too.

(unrelated) I just removed it. Of course, *I* never added those
modules there. The X tools did. If they are not loading, why don't the
X tools resolve this ?

> > (II) I810(0): [drm] DRM interface version 1.2
> > (II) I810(0): [drm] created "i915" driver at busid "pci:0000:00:02.0"
> > (II) I810(0): [drm] added 8192 byte SAREA at 0xf04dd000
> > (II) I810(0): [drm] mapped SAREA 0xf04dd000 to 0xb7b59000
> > (II) I810(0): [drm] framebuffer handle = 0xf0020000
> > (II) I810(0): [drm] added 1 reserved context for kernel
> > (WW) I810(0): i830 Kernel module detected, Use the i915 Kernel module
> > instead, aborting DRI init.
> >
>
> (unrelated) Are look loading the i830 kernel module explicitly in
> /etc/modules or so? You should remove it, i915 will be loaded
> automatically instead and it will give you DRI.

(unrelated) I just removed it.



Reply to: