From: "Lukas Oliva" <xoliva02@stud.feec.vutbr.cz>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] X keyboard problem on my amd64 box
Date: Fri, 29 Jun 2007 00:19:18 +0200 [thread overview]
Message-ID: <op.tunkagivab57r0@localhost> (raw)
In-Reply-To: <d257c3560706280404m7185006bn10c4733b22f339b3@mail.gmail.com>
On Thu, 28 Jun 2007 13:04:08 +0200, Beso <givemesugarr@gmail.com> wrote:
> 2007/6/27, Lukas Oliva <xoliva02@stud.feec.vutbr.cz>:
>>
>> Hi,
>> I use AMD64 gentoo o my box and I experience problems with keyboard
>> switching. Namely it is impossible o switch with Shift-Shift that is
>> specified in xorg.conf and even worse, if I specify two keyboards (czech
>> and english) in xorg.conf it is impossible to switch to the console.
>
>
> have you actually specified them also in the make.conf?!?! if you don't
> specify them there you may have troubles.... try to look at the use flags
> with whom you've compiled x (use euse for that)....
Hi, in my make.conf I have these INPUT_DEVICES and VIDEO_CARDS
INPUT_DEVICES="evdev keyboard mouse synaptics"
VIDEO_CARDS="nvidia nv v4l vesa"
My server is compiled with these USE FLAGs that I think worked for me
x11-base/xorg-server-1.2.0-r3 USE="dri ipv6 nptl sdl xorg xprint (-3dfx)
-debug -dmx -kdrive -minimal" INPUT_DEVICES="evdev keyboard mouse
synaptics -acecad -aiptek -calcomp -citron -digitaledge -dmc -dynapro
-elo2300 -elographics -fpit -hyperpen -jamstudio -joystick -magellan
-microtouch -mutouch -palmax -penmount -spaceorb -summa -tek4957 -ur98
-vmmouse -void -wacom" VIDEO_CARDS="nv nvidia v4l vesa -apm -ark -chips
-cirrus -cyrix -dummy -epson -fbdev -fglrx -glint -i128 (-i740) -i810
(-impact) (-imstt) -mach64 -mga -neomagic (-newport) (-nsc) -r128 -radeon
-rendition -s3 -s3virge -savage -siliconmotion -sis -sisusb (-sunbw2)
(-suncg14) (-suncg3) (-suncg6) (-sunffb) (-sunleo) (-suntcx) -tdfx -tga
-trident -tseng -vga -via -vmware -voodoo"
My graphic card is Nvidia FX Go 5700.
>
>
> This
>> results in the gnome start error saying that there could be several
>> souces
>> of problems (xkb, X, libxklavier). I am not sure where the problem could
>> be. I tried to recompile everything connected to xkb and Xorgand also
>> different versions, but it persists. Fortunately setxkb works, but I do
>> not consider it to be satisfying. Could anyone advise? It would be
>> helpful
>> also t point to some way of debugging as I have no idea.
>> I attach my xorg.conf. My gcc is x86_64-pc-linux-gnu-4.1.2 *, profile
>> 2006.1.
>
>
> have you actually done a emerge --sync and updated world with the new
> packages version?!?! the 2006.1 is very old as packages and baselayout,
> which had some great changes....
Yes, I sync at least twice a week and I do emerge -upvDN world &&
revdep-rebuild. I considered 2006.1 to be somehow old, but I was advised
on #gentoo-amd64 not to leave it as the next one could be still somehow
experimental.
>
> Thanks for advices
>> Lukas
>>
>
>
>
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2007-06-28 22:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 19:30 [gentoo-amd64] X keyboard problem on my amd64 box Lukas Oliva
2007-06-28 11:04 ` Beso
2007-06-28 22:19 ` Lukas Oliva [this message]
2007-06-29 9:39 ` Beso
2007-06-29 10:03 ` Lukas Oliva
2007-06-29 10:29 ` Beso
2007-06-29 12:56 ` Lukas Oliva
2007-06-29 16:37 ` Beso
2007-06-29 9:43 ` Beso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=op.tunkagivab57r0@localhost \
--to=xoliva02@stud.feec.vutbr.cz \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox