From: Beso <givemesugarr@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] X keyboard problem on my amd64 box
Date: Fri, 29 Jun 2007 12:29:29 +0200 [thread overview]
Message-ID: <d257c3560706290329o3b9bdad7n5a2dcf577d2a18e0@mail.gmail.com> (raw)
In-Reply-To: <op.tuogwnchab57r0@localhost>
[-- Attachment #1: Type: text/plain, Size: 4624 bytes --]
2007/6/29, Lukas Oliva <xoliva02@stud.feec.vutbr.cz>:
>
>
> >> My graphic card is Nvidia FX Go 5700.
> >
> >
> > you should install also the nvidia drivers and then eselect the nvidia
> > opengl instead of the xorg one, cause it's much more performant....
> > follow
> > the nvidia howtos on gentoo-wiki for that if you haven't done it yet....
>
> I did so and nvidia is correctly running.
>
> > anyway this is only the xorg server package, not the
> > internationalizzation
> > package which has the voices about the linguas.... for me (kde user) is
> > kde-base/kde-i18n which has various linguas compiled....
> well, I prefer gnome and fluxbox if performance neede. But it was all
> running ok till some update, but I had not time to solve it at that time.
you'll need to look for that update and try to fix it cause it may be that
one that is breaking you keyb layout....
> the absence of the
> > voice "LINGUAS ="en cz"" may say that it should have installed all the
> > default languages.... if you're using some other window manager than kde
> > you
> > should search on which is the internazionalization package on your
> > windowmanager....
>
> Oh, this is interesting, I thought, it should be "en cs" that I am using.
> Sorry for being confusing, I will attach the make.conf. In my mind, this
> isn't problem of window manager as gnome was running and it has no
> localization package.
hold on a sec, i don't know if is cz or cs.... you should look for you
internazionalizzation settings....
> but first i have forgotten of the x11-apps/setxkbmap package which
> > controls
> > the x keyb changer.... see if it's installed....
> Yes, it is, currenlty I use these packages perhaps related to xkb
> [ I] x11-apps/setxkbmap (1.0.2): Controls the keyboard layout of a
> running X server.
> [ I] x11-apps/xkbcomp (1.0.3): compile XKB keyboard description
> [ I] x11-apps/xkbutils (1.0.1): X.Org xkbutils application
> [ I] x11-libs/libxkbfile (1.0.4): X.Org xkbfile library
> [ I] x11-libs/libxkbui (1.0.2): X.Org xkbui library
> [ I] x11-libs/libxklavier (3.1): High level XKB library
> [ I] x11-misc/xkbdata (1.0.1): X.Org xkbdata data
> [ I] x11-misc/xxkb (1.10): eXtended XKB - assign different keymaps to
> different windows
> [ I] x11-plugins/gkrellm-xkb (1.05): XKB keyboard switcher for
> gkrellm2
wow.... you have a lot of packages installed but i don't see the one that i
was telling you about.... try emerging it....
> it may be due to it that
> > the system doesn't switch the keyb layout.... and another thing, on kde,
> > you
> > should first enable the shortcut on the kde admin pannel....
> This is not afaik necessary in gnome.
i don't know how gnome works, cause i hate it!!!! i'm a true kde crusader
against gnome/evolution/mono, which now are more and more integrated as
windows and internet exploder....
>
> >>
> > then you're using the 2007 layout.... when you update world you update
> > many
> > system packages, as gcc, libtool or baselayout.... the experimental
> > issue is
> > only is you use the tilde packages, which are still unstable.... you
> > should
> > not use this as an universal keyword in make.conf, but the packages that
> > you
> > need and that are still under the unstable branch should be put in the
> > /etc/portage/package.keywords file.... if you're using only stable packs
> > you
> > will not have any issue due to experimental things.... at least for what
> > i
> > know of it....
>
> Well, sorry I should not say experimental but I was told that there can be
> some problems on 2007.1, so I have not switched yet.
> ls -l /etc/ | grep make.profile
> lrwxrwxrwx 1 root root 51 2007-05-06 14:42 make.profile ->
> ..//usr/portage/profiles/default-linux/amd64/2006.1
> Maybe it would be good idea to switch, if you have not experienced any
> problems.
hmmm.... you've already switched to it.... the configuration in the profile
is not much changed and the packages you're using are udated.... this is the
best thing on gentoo: it isn't bonded anymore to versioning as other
distributions.... i've started with 2007.0 and now i'm using a very tainted
gentoo, with sabayon packages, i've updated the baselayout and with a lot
of tilde packages and with paludis instead of portage and my system is
stable and i haven't experienced any great issue.... if you look at the two
profiles you'll see that there are 2 use flags changed and you probably have
already enabled the 2 use flags that are enabled by default.... these are
the changes between the 2007.0 and 2006.1....
Lukas
>
--
beso
d-_-b
[-- Attachment #2: Type: text/html, Size: 6342 bytes --]
next prev parent reply other threads:[~2007-06-29 10:31 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
2007-06-29 9:39 ` Beso
2007-06-29 10:03 ` Lukas Oliva
2007-06-29 10:29 ` Beso [this message]
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=d257c3560706290329o3b9bdad7n5a2dcf577d2a18e0@mail.gmail.com \
--to=givemesugarr@gmail.com \
--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