for three weeks i decided to install suse 11.2 with KDE 4.3.1 to try to realise a Terminalserver.
i followed the instruction of the Nomadsite (Nomad - openSUSE)
At a first glance it works probably fine, but like everything in life the devil is in the details.
What works:
-I can connect with a linux/ms client to the server
-I can choose whether i want the KDE gui or the failsafe terminal
-i can login with all known local users of the ts (except the root)
what didn’t work:
-I can’t login as a root despite that in the security-section in the sesman.ini the “AllowRootLogin” is set to 1
-when i’m logged in with a user i have a serious problem with the keyboard;
– the layout seems to be a qwerty keymap (although xrdp-sesman.log says “using keyboard layout: 0x407 (de)” O_o)
– just standard - alphabetical keys are functional.
– the numpad works partialy => i can youse the “arrows” but neither the numberkeys (with numlock) nor the mathoperators
– the numberkeys above the qwerty works also partially i can use the “1”,“4” and “5” and some additional characters (with shift)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type “ONE_LEVEL” has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
so i still have the same issues.
But i discovered a way to switch to the us keymap with this command in a bash:
setxkbmap -model pc105 -layout us -option “”
then it’s fully functional
the problem now is, i’am from germany and want to use the german layout. so if i try that command with “-layout de” the problems gets back with the previously explained issues.
i also tried to write the following into the xorg.conf:
Rather than responding to your problem, I have a question. (I haven’t used nomad myself but I would like to try).
When you change the xorg.conf file on the server, how does it affect different clients with different type of keyboards. Or, are you changing the local xorg.conf file on the client side?
here i am working with a windows machine and a linux thin-client as a tsclient… so it is almost impossible to change a xorg.conf on a win7 eh?
Nomad handles different session from clients local on its own machine. And it automaticly “detects” the client peripherals (keyboard, mouse, video etc.) and loads the maps and drivers for the client tty i guess.
Although my keyboard were detected, i think that no suitable driver provided by xorg will be found so it loads the evdev driver.
My thought is to force him to load a generic pc105 keyboard with a “de” keymap, what still not work at the current stadium.
DumpGuy wrote:
> i don’t know how exactly nomad works… if i would, i didn’t have the
> problem…
personally, i’d never heard of it before i saw your question…maybe
you are the Nomad expert here (being the only one who has ever used
it!)…i wouldn’t know where or how to find “competent authority” but
i think it is a Novell product/program/brainchild, so . . .
–
palladium
Ubuntu is an African word meaning “I can’t set up Debian.”
Yeah, you two are right, that it seems i’m the “expert”. But be sure, i’am anything else as that. I’m a Windowscrack, but linux is my weak spot.
well whatever…
regarding to kiwi-ltsp… yes i tried it with a colleague. it quite works (after a long time of trying - guessing -reinstalling), also difficult to configure in details but quite better documented.
The ts with Nomad is a testing project i got from my professor…
DumpGuy wrote:
> The ts with Nomad is a testing project i got from my professor…
i’d guess you could hook up with the developers or maybe a forum
somewhere that actually has some folks with some experience with
it…you might try again over in forums.novell.com or better yet
with a deftly worded google…how is your google-fu
–
palladium
Ubuntu is an African word meaning “I can’t use Google.”
