Re: [osol-help] up nv106-nv107 breaks keyboard layout to US
This is the easiest way I found to change the keyboard layout: 1. vi /etc/default/kbd 2. Go to line with: LAYOUT= 3. Change to your desired language (run kbd -s to view the available languages you can enter) 4. :wq (write & quit) 5. reboot (please let me know if there is a service that can be restarted instead) I am only learning OpenSolaris myself. >From this thread I learnt of the kbd command but not the answer. 'man kbd' helped me find the answer. Hope this helps someone who had the same problem as I. -- This message posted from opensolaris.org ___ opensolaris-help mailing list opensolaris-help@opensolaris.org
Re: [osol-help] up nv106-nv107 breaks keyboard layout to US
Thanks, Alan! For everyone else, the correct one is this: Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "de_CH" #Option "XkbVariant" "ch" EndSection The driver is 'kbd'; the one I mentioned before was wrong. And I locked myself out with the XkbVariant; this is not supported it seems. With Option "XkbLayout" "de" Option "XkbVariant" "ch" the keyboard turned dead and I couldn't even shut down properly. Therefore, better do something like % cat /usr/X11/lib/X11/xkb/rules/base | grep " ch " or likewise with the language of choice to gather the support it gives you. Uwe -- This message posted from opensolaris.org ___ opensolaris-help mailing list opensolaris-help@opensolaris.org
Re: [osol-help] up nv106-nv107 breaks keyboard layout to US
Jürgen Keil wrote: >> There are no more 'base' rules. >> How can I change the default layout, since there are >> no more alternatives? > > Have a look at this thread: > http://www.opensolaris.org/jive/thread.jspa?threadID=86953&tstart=15 > > Apparently the keyboard layout is configured > in /etc/hal/fdi/preprobe/10osvendor/10-x11-input.fdi Except that the ON changes to make hal pass the input device information through didn't integrate yet, as noted in: http://www.opensolaris.org/jive/thread.jspa?threadID=89998&tstart=0 -- -Alan Coopersmith- alan.coopersm...@sun.com Sun Microsystems, Inc. - X Window System Engineering ___ opensolaris-help mailing list opensolaris-help@opensolaris.org
Re: [osol-help] up nv106-nv107 breaks keyboard layout to US
Uwe Dippel wrote: > [i]I might as well put it into xorg[/i] > > No, not that easy any more. It seems, Xorg has left this solution behind: > > Section "InputDevice" > Identifier "Keyboard0" > Driver "Keyboard" > Option "XkbRules" "xorg" > Option "XkbModel" "pc105" > Option "XkbLayout" "de" > # Option "XkbVariant" "ch" > EndSection That's the correct workaround for this bug for now, but needs one more step: > (II) Initializing extension GLX > (EE) XKB: Couldn't open rules file /usr/X11/lib/X11/xkb/rules/base you'll also need to workaround that bug by making a symlink from base to xorg in that directory. -- -Alan Coopersmith- alan.coopersm...@sun.com Sun Microsystems, Inc. - X Window System Engineering ___ opensolaris-help mailing list opensolaris-help@opensolaris.org
Re: [osol-help] up nv106-nv107 breaks keyboard layout to US
> There are no more 'base' rules. > How can I change the default layout, since there are > no more alternatives? Have a look at this thread: http://www.opensolaris.org/jive/thread.jspa?threadID=86953&tstart=15 Apparently the keyboard layout is configured in /etc/hal/fdi/preprobe/10osvendor/10-x11-input.fdi And the workaround for the missing "base" rules file is to install a link to the xorg rules file... -- This message posted from opensolaris.org ___ opensolaris-help mailing list opensolaris-help@opensolaris.org
Re: [osol-help] up nv106-nv107 breaks keyboard layout to US
[i]I might as well put it into xorg[/i] No, not that easy any more. It seems, Xorg has left this solution behind: Section "InputDevice" Identifier "Keyboard0" Driver "Keyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "de" # Option "XkbVariant" "ch" EndSection (II) Initializing extension GLX (EE) XKB: Couldn't open rules file /usr/X11/lib/X11/xkb/rules/base (EE) XKB: No components provided for device Virtual core keyboard (WW) Couldn't load XKB keymap, falling back to pre-XKB keymap (II) : Setting Device option to "/dev/mouse" (**) : Protocol: VUID (**) Option "CorePointer" (**) : always reports core events (**) Option "Device" "/dev/mouse" (II) : Setting Buttons option to "3" (==) : Emulate3Buttons, Emulate3Timeout: 50 (**) : ZAxisMapping: buttons 4 and 5 (**) : Buttons: 9 (**) Option "CoreKeyboard" (**) : always reports core events (II) : Opened device "/dev/kbd" (--) : Keyboard type: USB (6) (--) : Keyboard layout: 28 (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xorg" (**) : XkbRules: "xorg" There are no more 'base' rules. How can I change the default layout, since there are no more alternatives? Yes, the problem is an X problem: On the command line login everything is perfectly well Swiss-German as always. Uwe -- This message posted from opensolaris.org ___ opensolaris-help mailing list opensolaris-help@opensolaris.org
[osol-help] up nv106-nv107 breaks keyboard layout to US
Another, minor, item here. I wonder what is the proper way to resolve this? The keyboard is sg (swiss-german) and all earlier updates left it there, now it is invariably at 'us'. I have already tried kbd -s, but it won't do anything and stays at 'us': # kbd -s USB keyboard [...] 16. Greek 38. Swiss-German 17. Icelandic 39. Traditional-Chinese 18. Italian 40. TurkishQ 19. Japanese-type641. TurkishF 20. Japanese 42. UK-English 21. Korean43. US-English 22. Latin-American To select the keyboard layout, enter a number [default 43]:38 # qwerty I might as well put it into xorg, but I don't think that is what it is intended for. The Gnome Preferences for Keyboard have no more settings for the layout. And Gnome Preferences Input Methods die with: X Vendor: Sun Microsystems, Inc. X Vendor Release: 10503000 Selinux: No Accessibility: Disabled GTK+ Theme: nimbus Icon Theme: nimbus Memory status: size: 82653184 vsize: 82653184 resident: 19976192 share: 1691648 rss: 19976192 rss_rlim: 0 CPU usage: start_time: 1233813766 rtime: 28 utime: 234469 stime: 53833 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/iiim-properties' 2136: iiim-properties fef01937 waitid (0, 859, 8044e3c, 3) feeb2da5 waitpid (859, 8044ef8, 0, feb98bfd) + 65 feb99004 g_spawn_sync (0, 85e0c40, 0, 4, 0, 0) + 418 feb99404 g_spawn_command_line_sync (830d6d8, 0, 0, 0, 8045018) + 5c fa2d1791 __1cNrun_bug_buddy6Fpkclp0_b_ (8079ae8, 858, 0, 858) + 71 fa2d1a19 __1cMcheck_if_gdb6F_v_ (feed8125, fef8f000, 8045198, feefcd9f, b, 0) + 145 fa2d1458 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 804524c) + 64 feefcd9f __sighndlr (b, 0, 804524c, fa2d13f4) + f feef010f call_user_handler (b) + 2af feef033f sigacthandler (b, 0, 804524c) + df --- called from signal handler with signal 11 (SIGSEGV) --- fee73ffb strlen (80669c4, 80467ac, 8046250, 0) + b feec310d vsnprintf (804628f, 1, 80669c4, 80467ac) + 65 feb6ba04 g_printf_string_upper_bound (80669c4) + 24 feb97f86 g_vasprintf (80462dc, 80669c4, 80467ac, feb811b0) + 26 feb811ce g_strdup_vprintf (80669c4, 80467ac, 804634c, feb6a6b1) + 2a feb6aa6a g_logv (0, 20, 80669c4, 80467ac) + 3ca feb6ab9d g_log(0, 20, 80669c4, 3e9) + 25 08060893 cf_initialize (808b600, f9ce3260, f9ce3224, f9ce3258) + 2f3 0805cfbf init_setup (80f2048) + 23 080578e1 main (1, 804709c, 80470a4, feffb7e4) + 85 080577cd _start (1, 80471cc, 0, 80471dc, 8047206, 8047249) + 7d Uwe -- This message posted from opensolaris.org ___ opensolaris-help mailing list opensolaris-help@opensolaris.org
