From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <gentoo-dev-return-13620-arch-gentoo-dev=gentoo.org@lists.gentoo.org> Received: (qmail 22034 invoked from network); 25 Jun 2004 16:29:33 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 25 Jun 2004 16:29:33 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1Bdta1-000426-0O for arch-gentoo-dev@lists.gentoo.org; Fri, 25 Jun 2004 16:29:33 +0000 Received: (qmail 4932 invoked by uid 89); 25 Jun 2004 16:29:32 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: <mailto:gentoo-dev@gentoo.org> List-Help: <mailto:gentoo-dev-help@gentoo.org> List-Unsubscribe: <mailto:gentoo-dev-unsubscribe@gentoo.org> List-Subscribe: <mailto:gentoo-dev-subscribe@gentoo.org> List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org> X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 28887 invoked from network); 25 Jun 2004 16:29:32 +0000 From: Kevin <gentoo-dev@gnosys.biz> To: gentoo-dev@lists.gentoo.org Date: Fri, 25 Jun 2004 12:29:31 -0400 User-Agent: KMail/1.6.2 References: <200406251020.44612.gentoo-dev@gnosys.biz> <1088175448.8304.39.camel@localhost> In-Reply-To: <1088175448.8304.39.camel@localhost> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <200406251229.31024.gentoo-dev@gnosys.biz> Subject: Re: [gentoo-dev] XOrg/Gnome problems with Xkb Options (was gdm-2.6.0.3, XOrg/Gnome...) X-Archives-Salt: 31048488-550e-4db4-abf8-e44968dd2561 X-Archives-Hash: a81393ac5078648e29994f725aca2a46 On Friday 25 June 2004 10:57, Chris Gianelloni wrote: <snip> > > You should probably check bugs.gentoo.org, which is where any show > stopping bugs would be that would block the upgrade. If there are no > such bugs, then it would be a good idea for you to submit a feature > request to have the newer version added to portage. Good idea. I should've done that before writing here I guess. Sorry. =20 =46rom Bug 46794, it looks like someone already brought this up in April,=20 so I'll drop it. Anyway, I already have the functionality that I want,=20 so it's moot for me now. <snip> > > xorg.conf file, X refuses to start at all. The server reports no > > devices found so I guess the fglrx driver does not support the > > Radeon IGP 340M, but isn't that driver from ATI? I tried the > > opengl-update ati command after putting fglrx in the Driver > > parameters of xorg.conf and before starting xdm (gdm), but no help > > there either. > > Are you sure the driver supports the card? ATI are a little slow and > getting drivers for newer cards into the package. If you are sure > that the driver supports your card, I would suggest filing a bug on > bugs.gentoo.org and letting the maintainer take a look at it. Actually, I'm pretty sure the fglrx driver does not support that=20 card/chip. This is based on what I see when I try using it in addition=20 to a vague memory of having read that somewhere---maybe on forums. But=20 I'll look into it further and post a bug if the driver advertises=20 support for that card/chip. <snip> > > Using the radeon driver, when I start X with XSESSION in make.conf > > set to Gnome (logging into gdm as root), I get a dialog that says: > > <snip> > <snip> > > Why not just remove all of the XKB stuff from your configuration? It > doesn't look like you need it at all, and xorg-x11 will function fine > without it. As an example, here is my InputDevice section with my > keyboard in it: > > Section "InputDevice" > Identifier "Keyboard0" > Driver "keyboard" > EndSection Well, I thought that maybe the pc105 option would be important since=20 it's a laptop---does XOrg autoprobe for stuff like that? I wasn't sure=20 if the others were defaults or not. I did try your suggestion, though, and oddly enough, Gnome still pops up=20 the same dialog when I log in as root. When I run the two commands=20 (xprop and gconftool-2), they show the same information as before. Is=20 this info cached by gnome or something? I would think that gnome would=20 get the info from the X server which I must assume is getting it from=20 xorg.conf. I restarted the machine to make sure that some stale cache=20 info wasn't lying around in some temp file or something, but it's still=20 there. Any thoughts on why this is happening and how to stop it? It seems like=20 gnome got its info from X once, stored it somewhere, and now is keeping=20 it---in spite of the change to xorg.conf. Is that what's happening? =20 Seems like a bad idea, but maybe I'm missing something. =2DKevin -- gentoo-dev@gentoo.org mailing list