|00:14||matttttt has joined #ltsp|
|00:23||erieslabnx has joined #ltsp|
Guys I try really hard not to just come here when I have a problem but... I have a big one...
3 of my thin clients' screens are both inverted and reversed
I can't figure out why
has anyone seen this before?
wait, not reversed... They are flipped horizontally, bottom of back ground is at top, and text is reading not only upside down, but is also inverted so applications reads as snoitacilppA
|00:26||japerry has joined #ltsp|
erieslabnx, try putting screen resolution for those clients in lts.conf
what format would that go in as for 1024 x 768?
do you know off hand?
lol wait bigger question... where is lts.conf?
cyberorg: "docs" is For the most current documentation, see http://wiki.ltsp.org/twiki/bin/view/Ltsp/LtspDocumentationUpstream
erieslabnx, ^^ :)
thank you :)
so in theory the screens could be flipped like this because the user accounts were initially setup and configured using my brand new HP monitor, and when they were plugged into these ancient bricks, this is the result?
or could it be because the monitor they are currently plugged into is not capable of the color/resolution settings as the monitor they were plugged into 3 hours ago?
hmmm I can not find my lts.conf file, perhaps that is the problem?
found it ;)
|01:02||Ahmuck has joined #ltsp|
|01:03||japerry_cat has joined #ltsp|
|01:05||japerry has quit IRC|
|01:39||japerry_cat has quit IRC|
|01:51||nubae1 has joined #ltsp|
|01:51||nubae has quit IRC|
|03:14||Subhodip has joined #ltsp|
|03:40||Remaille has joined #ltsp|
|03:48||yoshi__ has joined #ltsp|
|03:55||Subhodip has quit IRC|
|04:22||Egyptian[Home]1 has quit IRC|
|04:36||Egyptian[Home] has joined #ltsp|
|04:45||ogra has quit IRC|
|04:46||ogra has joined #ltsp|
|05:43||intelliant has quit IRC|
|06:06||hanthana has joined #ltsp|
|06:11||intelliant has joined #ltsp|
|06:12||yoshi__ has quit IRC|
|06:12||intelliant_ has joined #ltsp|
|06:26||Patina_ has joined #ltsp|
|06:30||intelliant has quit IRC|
|06:31||Patina_ has quit IRC|
|06:34||Patina_ has joined #ltsp|
|06:40||Patina has quit IRC|
|06:46||Patina has joined #ltsp|
|06:56||mikkel has joined #ltsp|
|07:02||barbosa has quit IRC|
|07:02||Patina_ has quit IRC|
|07:20||barbosa has joined #ltsp|
|07:40||yoshi__ has joined #ltsp|
|07:48||yoshi___ has joined #ltsp|
|07:49||yoshi__ has quit IRC|
|07:54||Ahmuck has quit IRC|
|07:54||Ahmuck has joined #ltsp|
|08:08||intelliant_ has quit IRC|
|09:20||matttttt has quit IRC|
|09:23||MichalPenka has joined #ltsp|
Hello community! I'm playing with LTSP (Ubuntu standalone ltsp server) few days and I've decided to install the server into VirtualBox with bridged networking (physical eth0 is bridged to virtual eth0)...The question is - will I be able to boot ltsp physical clients? Thanks!
|09:37||MichalPenka1 has joined #ltsp|
|09:37||MichalPenka has quit IRC|
to be more precise...my virtual eth0 has 192.168.0.1/24, my physical eth0 gets 192.168.0.20/24 from virtualized ltsp server
I'm not expert in networking
but I thought bridged network should make the IPs the same
|09:53||nubae1 has quit IRC|
|09:54||nubae has joined #ltsp|
|09:57||yoshi__ has joined #ltsp|
|10:09||yoshi___ has quit IRC|
am I online?
Směrovací tabulka v jádru pro IP
Adresát Brána Maska Přízn MSS Okno irtt Rozhraní
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
192.168.200.0 * 255.255.255.0 U 0 0 0 wlan0
link-local * 255.255.0.0 U 0 0 0 wlan0
default ltsp-server.loc 0.0.0.0 UG 0 0 0 eth0
|10:20||intelliant has joined #ltsp|
|10:24||achandra has joined #ltsp|
|10:25||gate_keeper_ has joined #ltsp|
anyone around to answer fl_teacher installation on k12linux? -- I have 64bit OS installed hosting 32 bit clients. Am I required to install it in chroot /opt/ltsp/i386 or is the install done on the x86_64 bit side ?
|10:26||subhodip has joined #ltsp|
|10:36||MichalPenka1 has quit IRC|
|10:38||yoshi__ has quit IRC|
|10:38||barbosa has quit IRC|
|10:40||barbosa has joined #ltsp|
|10:45||vvinet has joined #ltsp|
|11:05||vvinet has quit IRC|
|11:05||Patina_ has joined #ltsp|
|11:05||intelliant has quit IRC|
|11:15||Patina has quit IRC|
|11:21||achandra has quit IRC|
|11:23||yoshi__ has joined #ltsp|
|11:31||yoshi___ has joined #ltsp|
|11:33||yoshi____ has joined #ltsp|
|11:49||yoshi__ has quit IRC|
|11:50||yoshi___ has quit IRC|
|11:53||yoshi____ has quit IRC|
|12:15||intelliant has joined #ltsp|
|12:20||yoshi__ has joined #ltsp|
|12:29||F-GT has quit IRC|
|12:30||otavio has joined #ltsp|
|12:31||F-GT has joined #ltsp|
|12:48||japerry has joined #ltsp|
|12:53||gate_keeper_ has quit IRC|
|13:06||dmc has quit IRC|
|13:06||dmc has joined #ltsp|
|13:07||dmc has left #ltsp|
|13:07||dmc has joined #ltsp|
|13:32||yoshi__ has quit IRC|
|13:49||hanthana has quit IRC|
|14:15||Remaille has quit IRC|
|14:17||Ahmuck has quit IRC|
|14:19||subhodip has quit IRC|
|14:20||intelliant has quit IRC|
|14:58||vagrantc has joined #ltsp|
|15:11||matttttt has joined #ltsp|
|15:27||pmatulis has joined #ltsp|
|15:59||nubae has quit IRC|
|16:33||nubae has joined #ltsp|
"vagrantc" pasted "very minor tweak to getltscfg-cluster" (13 lines) at http://pastebot.ltsp.org/381
stgraber: does that look ok to you? ^^
i'm not sure if it should be egrep '/rofs.*nbd' or egrep 'nbd.*/rofs'
|16:53||nubae has quit IRC|
|16:53||nubae has joined #ltsp|
|17:07||Ahmuck has joined #ltsp|
|17:17||vagrantc has quit IRC|
|18:19||vagrantc has joined #ltsp|
vagrantc: got my mail ?
stgraber: worth committing?
i also made another commit changing the way the ntpdate/hwclock stuff is called
though it assumes the thin-client hardware clock will be utc, which is maybe flawed.
|18:43||pmatulis_ has joined #ltsp|
vagrantc: what's the different in behavior vs not having --utc ?
stgraber: using --noadjfile requires using --utc or --local, as least according to the manpage.
|18:47||pmatulis has quit IRC|
was needed to not have /etc/adjtime tweaked, which doesn't really make sense on a thin client which gets a different /etc/adjtime every boot.
|18:47||pmatulis has joined #ltsp|
but i guess it stores the LOCALTIME vs. UTC in there, too ... guess we could parse it to find the appropriate behavior...
well, I don't think we copy it or generate it with ltsp-build-client so whatever is its default should be fine
|19:58||mikkel has quit IRC|
|20:10||ahven has joined #ltsp|
hello, got a problem that google doesn't answer quite fully - got a very fresh install of LTSP on my debian and both virtualbox and my IBM T23 won't recognize my keyboard and mouse
the login screen comes up and no input possiblity
how does the thin client know where to download the ltsp image?
pmatulis, dhcpd tells it
covered in the most basic setup manuals
under debian that file is located in /etc/ltsp/dhcpd.conf which is included from the main dhcpd configuration
ahven: i know all that
so...what seems to be the problem then? :)
in dhcpd.conf there is the root-path parameter. but that does not give the image location, it gives the path of the root filesystem from which the image is built
my image is at /opt/ltsp/images/i386.img
root-path shows /opt/ltsp/i386
ahven: do you understand my question?
i think that pxelinux.0 must have the intelligence to find the image location from the root-path value
it's handled in initramfs that's downloaded via pxelinux
oh, no ... it actually is passed on the pxelinux.cfg/default commandline
nbdserver/nbdport and all that
vagrantc: thanks, will check
vagrantc: is it possible to have multiple images? like direct image1 for client1 and image2 for client2?
from the above, that means "can we have different pxelinux configs for different clients
pmatulis: definitely possible.
well, sort of trivial.
what's the crux of it?
etherboot seems a more better solution imho
when multiple images are involved
yeah, you can specify a different pxelinux.cfg/ ... when it boots, you should see all the files it tries ... tries a mac based on, and then an ip address based one, and then hashed versions of pieces of the ip address.
and when it doesn't find any of those, it tries pxelinux.cfg/default
read up in the syslinux documentation for how it works
it sounds trivial, why you say not trivial?
vagrantc, can you perhaps shed some light on my problem as well? :)
ahven: i dont' recall having issues with keyboard ever ... so not much.
textmode works just fine, ldm doesn't spit out any error to remote-syslog neither
there are people with quite similar problems but no real answer has been given to most of them
currently seems that ltsp is having a hard time creating a workable xorg.conf
|22:22||Egyptian[Home] has quit IRC|
|22:23||pmatulis has quit IRC|
|22:39||Egyptian[Home] has joined #ltsp|
|22:47||intelliant has joined #ltsp|
|22:54||vagrantc has quit IRC|
|23:22||PhilGlass has quit IRC|
|23:23||Lockeian has joined #ltsp|
|23:27||michael1 has joined #ltsp|
|23:34||michael1 has quit IRC|
|23:37||chupacabra has quit IRC|
|23:38||chupacabra has joined #ltsp|