Menu
▾
▴
Re: [Ltsp-discuss] Keyboard and mouse not working.
|
From: Michael P. <mi...@dt...> - 2013-10-29 22:49:58
|
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Jay,<br>
<br>
On 30/10/13 06:57, Rodney Jay Fluharty wrote:<br>
</div>
<blockquote cite="mid:527...@gm..." type="cite">
<pre wrap="">I've installed LTSP onto my shiny new Debian 64-bit server. I'm running
current stable Wheezy. LTSP is from apt repository version 5.4.2-6.
I built client ltsp-build-client --arch i386 to create i386 compatible
client.
Client PXE boots, comes up to LTSP login (ldm?) At that point, neither
the mouse or keyboard work, leaving me dead in the water. I've tried
this with both USB and ps2 devices.
Read an old post somehere saying HAL needed to be installed in chroot.
Tried it. Nothing. Remote syslog server shows nothing.
Can I boot strictly into terminal so I can maybe debug this? Anyone
else seen this? I also tried upgrading server and chroot environment up
through the testing and unstable distros hoping there was just a bug in
older version. No Luck.
Tried googling this for two days. Nothing useful.
Thanks in advance for help.
</pre>
</blockquote>
You could look at the lts.conf file it has many options for
different keyboards also you can set the screens to drop your client
directly into a terminal.<br>
<br>
Ref:
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="http://manpages.ubuntu.com/manpages/lucid/man5/lts.conf.5.html">http://manpages.ubuntu.com/manpages/lucid/man5/lts.conf.5.html</a><br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<h4 id="contenttoc11" style="margin: 0px; padding: 0px; border: 0px;
font-weight: normal; font-style: normal; font-size: 12px;
line-height: 16px; font-family: Ubuntu, 'DejaVu Sans', 'Bitstream
Vera Sans', Tahoma, sans-serif; text-align: left; vertical-align:
baseline; color: rgb(51, 51, 51); font-variant: normal;
letter-spacing: normal; orphans: auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px;"><b>LTS.CONF</b><span
class="Apple-converted-space"> </span><b>OPTIONS</b><span
class="Apple-converted-space"> </span><b>-</b><span
class="Apple-converted-space"> </span><b>SCREEN</b><span
class="Apple-converted-space"> </span><b>SCRIPTS</b></h4>
<pre style="margin: 0px; padding: 0px; border: 0px; font-weight: normal; font-style: normal; font-size: 12px; line-height: 16px; font-family: inherit; text-align: left; vertical-align: baseline; color: rgb(51, 51, 51); font-variant: normal; letter-spacing: normal; orphans: auto; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"> <u>SCREEN_01...SCREEN_12</u>
string, default <u>ldm</u>
Up to 12 screen scripts can be specified for a thin client. This
will give you up to 12 sessions on the thin client, each accessible
by pressing the Ctrl-Alt-F1 through Ctrl-Alt-F12 keys.
Currently, possible values include: rdesktop, xdmcp, shell, ldm,
startx (depreciated), and telnet
Look in the $CHROOT/usr/share/ltsp/screen.d directory for more
scripts, or write your own, and put them there.
Are you able to boot a livecd or live USB distro on the thin client and test the same keyboard and mouse?
Does it happen with all thin clients or just one?
Have you tried configuring Virtualbox or KVM on the host and setup a diskless virtual image which boots off the network, this way you could test a thin client without hardware and see if it's a hardware or software issue?
from
Michael
</pre>
</body>
</html>
|