IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 30 March 2011   (all times are UTC)

00:04map7_ (~map7@115-64-152-217.static.tpgi.com.au) joined #ltsp.
00:14map7_ (~map7@115-64-152-217.static.tpgi.com.au) left irc: Ping timeout: 250 seconds
00:33cyberorg (~cyberorg@opensuse/member/Cyberorg) left irc: Ping timeout: 260 seconds
00:44dobber (~dobber@89.190.197.77) joined #ltsp.
00:49cyberorg (~cyberorg@opensuse/member/Cyberorg) joined #ltsp.
00:59cyberorg (~cyberorg@opensuse/member/Cyberorg) left irc: Remote host closed the connection
01:01hejhulak (~hejhulak@222-136-158-212.bluetone.cz) joined #ltsp.
01:03hejhulak (hejhulak@222-136-158-212.bluetone.cz) left #ltsp.
01:08cyberorg (~cyberorg@opensuse/member/Cyberorg) joined #ltsp.
01:22xavierb (~xavier@lns-bzn-24-82-64-156-238.adsl.proxad.net) joined #ltsp.
01:32spectra (~spectra@debian/developer/spectra) left irc: Read error: Operation timed out
01:33spectra (~spectra@debian/developer/spectra) joined #ltsp.
01:43din_os (~din_os@81.186.118.42) joined #ltsp.
01:59xavierb (~xavier@lns-bzn-24-82-64-156-238.adsl.proxad.net) left irc: Read error: Operation timed out
02:18mistik1 (mistik1@unaffiliated/mistik1) left irc: Read error: Connection reset by peer
02:19mistik1 (mistik1@unaffiliated/mistik1) joined #ltsp.
02:29alkisg_web (c23fefed@gateway/web/freenode/ip.194.63.239.237) joined #ltsp.
02:30xavierb (~xavier@lns-bzn-24-82-64-156-238.adsl.proxad.net) joined #ltsp.
02:32vmlintu (~vmlintu@nblzone-240-143.nblnetworks.fi) left irc: Ping timeout: 240 seconds
02:39xavier_brochard (~xavier@lns-bzn-39-82-255-58-34.adsl.proxad.net) joined #ltsp.
02:43xavierb (~xavier@lns-bzn-24-82-64-156-238.adsl.proxad.net) left irc: Ping timeout: 246 seconds
02:43
02:53Trixboxer (~Trixboxer@office.supportdepartment.net) joined #ltsp.
03:02alkisg_web (c23fefed@gateway/web/freenode/ip.194.63.239.237) left #ltsp.
03:02Da-Geek (~Da-Geek@80.235.229.178) joined #ltsp.
03:22Nick change: xavier_brochard -> xavierb
03:33alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
03:43vmlintu (~vmlintu@217.152.60.83) joined #ltsp.
03:56xavierb (~xavier@lns-bzn-39-82-255-58-34.adsl.proxad.net) left irc: Ping timeout: 260 seconds
04:09vmlintu (~vmlintu@217.152.60.83) left irc: Ping timeout: 260 seconds
04:15Nick change: zz_evil_root -> evil_root
04:21vmlintu (~vmlintu@217.152.60.83) joined #ltsp.
04:22xavierb (~xavier@lns-bzn-39-82-255-58-34.adsl.proxad.net) joined #ltsp.
05:04artista_frustrad (~artista_f@187.54.58.224) joined #ltsp.
05:05
<mgariepy>
good morning everyone
05:05bobby_C (~bobby@85-124-22-227.teleworker.xdsl-line.inode.at) joined #ltsp.
05:07
<vvinet>
good morning marc
05:09HeMan (jimmy@2a00:801:f5:40:10::19) left #ltsp.
05:22dgroos (~dgroos@205.215.177.151) joined #ltsp.
05:25vmlintu (~vmlintu@217.152.60.83) left irc: Ping timeout: 248 seconds
05:44xavierb (~xavier@lns-bzn-39-82-255-58-34.adsl.proxad.net) left irc: Ping timeout: 252 seconds
05:45xavierb (~xavier@lns-bzn-39-82-255-58-34.adsl.proxad.net) joined #ltsp.
05:50dgroos (dgroos@205.215.177.151) left #ltsp.
05:51vmlintu (~vmlintu@217.152.60.83) joined #ltsp.
06:00Gadi (~romm@ool-18bbe47a.static.optonline.net) joined #ltsp.
06:03rad4Christ (~anonymous@165.166.57.122) joined #ltsp.
06:05Adriannom (~adrian@cpc10-cwma7-2-0-cust15.7-3.cable.virginmedia.com) joined #ltsp.
06:10
<Adriannom>
hi. i'm running ubuntu 10.04 on an amd athlon 64bit 3500+, 2gb ram. i have the ltsp-server package installed from the repo. i'm using a wyse S50 thin client connected via 100mbit wire, which boots ubuntu straight away and everything just works. the only problem is the speed is incredibly slow, seems far worse than vnc especially when a browser is open. any ideas what might be wrong?
06:14
<Gadi>
Adriannom: try setting LDM_DIRECTX=True
06:20
<Adriannom>
ok gadi, thanks
06:25artista_frustrad (~artista_f@187.54.58.224) left irc: Quit: Leaving
06:27matrix3000 (~matrix@rrcs-70-61-255-226.central.biz.rr.com) joined #ltsp.
06:36xavierb (~xavier@lns-bzn-39-82-255-58-34.adsl.proxad.net) left irc: Ping timeout: 250 seconds
06:39xavierb (~xavier@lns-bzn-39-82-255-58-34.adsl.proxad.net) joined #ltsp.
06:45Kicer86 (~Kicer86@host-5db0eeee.sileman.net.pl) left irc: Quit: KVIrc Insomnia 4.0.2, revision: 4740, sources date: 20100627, built on: 2010-08-08 18:29:00 UTC http://www.kvirc.net/
06:51xavierb (~xavier@lns-bzn-39-82-255-58-34.adsl.proxad.net) left irc: Quit: Konversation terminated!
06:51xavier_brochard (~xavier@lns-bzn-39-82-255-58-34.adsl.proxad.net) joined #ltsp.
06:57
<Adriannom>
Gadi, looks exactly the same, everything is still crawling along. how can i confirm it worked? i created a file at /var/lib/tftpboot/ltsp/i386/lts.conf and put LDM_DIRECTX=True in it. is that right?
07:02rad4Christ (~anonymous@165.166.57.122) left irc: Read error: Connection reset by peer
07:02rad4Christ (~anonymous@165.166.57.122) joined #ltsp.
07:04Adriannom (~adrian@cpc10-cwma7-2-0-cust15.7-3.cable.virginmedia.com) left irc: Ping timeout: 240 seconds
07:17Adriannom (~adrian@cpc10-cwma7-2-0-cust15.7-3.cable.virginmedia.com) joined #ltsp.
07:18
<Gadi>
Adriannom: try:
07:18
[default]
07:18
LDM_DIRECTX=True
07:24matrix3000 (~matrix@rrcs-70-61-255-226.central.biz.rr.com) left irc: Ping timeout: 250 seconds
07:26xavier_brochard (~xavier@lns-bzn-39-82-255-58-34.adsl.proxad.net) left irc: Ping timeout: 276 seconds
07:27vmlintu (~vmlintu@217.152.60.83) left irc: Read error: Operation timed out
07:32xavier_brochard (~xavier@lns-bzn-39-82-255-58-34.adsl.proxad.net) joined #ltsp.
07:32
<Adriannom>
Gadi, yup, got it. looks better actually, thanks :) flash is still really slow but at least it's usable :p
07:40matrix3000 (~matrix@rrcs-70-61-255-226.central.biz.rr.com) joined #ltsp.
07:44Kicer86 (~Kicer86@host-5db0eeee.sileman.net.pl) joined #ltsp.
08:04Roasted (~jason@206.82.22.190) joined #ltsp.
08:10
<knipwim>
Gadi: when using LDM_DIRECTX=TRUE, the X connection happens on port 60XX right?
08:16
<Adriannom>
are there any other ways to speed things up? ideally i'd like flash to be fast enough to be able to use youtube. is that typically possible?
08:18
<knipwim>
Adriannom: i am not using ldm_directx atm, but i can use youtube (with some framedrop)
08:18
using fluxbox as my wm
08:18
<Adriannom>
i can play youtube videos but they are extremely choppy
08:18
sound is fine
08:19
<knipwim>
could you play it with ldm_directx=false?
08:19
<Adriannom>
nah, it was too slow to even work
08:19
<knipwim>
what window manager are you using?
08:20
<alkisg>
Adriannom: graphics card?
08:20
ltsp-localapps xterm
08:20
and there, lspci -nn -k | grep -A 2 VGA
08:20
<Adriannom>
gnome. i'm running ubuntu 10.04 on an amd athlon 64bit 3500+, 2gb ram. i have the ltsp-server package installed from the repo. i'm using a wyse S50 thin client connected via 100mbit wire. client spec: http://www.wyse.co.uk/products/hardware/thinclients/S50/index.asp
08:21
<abeehc>
hehe
08:21
still need to do the lspci
08:21
<Adriannom>
on the client?
08:21
<abeehc>
I think i have some of those machines at home
08:22
Yeah
08:22
<Adriannom>
brb, only have 1 monitor here ;)
08:22
actually, i'll vnc
08:25
<Roasted>
I have a dumb question. If LDM_DIRECTX speeds things up, why is it not there by default?
08:25staffencasa (~staffenca@128-193-150-224.oregonstate.edu) joined #ltsp.
08:25
<highvoltage>
Roasted: it's very insecure
08:25
<Roasted>
ah really?
08:25
like it poses potential security risks?
08:26
<abeehc>
http://manpages.ubuntu.com/manpages/karmic/man5/lts.conf.5.html
08:26
you should read about it
08:26
<highvoltage>
Roasted: not in the "I'm not good enough I'm worthless" kind of insecure, but in the sense that all your data (everything that's on the thin client screen and all keystrokes) are sent over the network unencrypted
08:26
Roasted: so someone who is able to listen in on the local network could steal passwords or do other nasty stuff
08:26
<Roasted>
ah, I gotcha
08:26
<highvoltage>
Roasted: which would make it a bad default :)
08:27
<Roasted>
so it should only be used... if needed
08:27
<abeehc>
then again if you turn it on to get flash going
08:27
<Roasted>
yeah
08:27
our flash was iffy but not "bad" without it
08:27
<abeehc>
hehe
08:27
<Roasted>
I think I turned it on for our lab here...
08:27
checking now..
08:27
<abeehc>
i run with true, barely tried without
08:28
<Roasted>
I don't think I have it on my middle school lab, but I can't think of a time they used flash there.
08:28
<Adriannom>
alkisg, 00:01.1 VGA compatible controlle [0300]: National Semiconductor Corporation Geocode GX2 Graphics Processor [100b:0030]
08:28
<Roasted>
And with it being a library lab, where things are hush hush quiet, I doubt they ever would.
08:28
<Adriannom>
kernel driver and module gxfb
08:28
<Roasted>
ah hah, yeah I did eanble it here
08:29
<highvoltage>
Roasted: I usually enable it if it's in an environment that doesn't require much security. if my users are going to pretty much run tuxpaint and gcompris then I care more about performance than security. as soon as people run web browsers from the application server and authenticate to any services then it becomes very important to keep the stuff that's going over the wire encrypted
08:31
<Roasted>
highvoltage, I hear ya. I'm not so sure our environments need to "beg" for higher security anyway. Especially compared to performance.
08:32
<abeehc>
Adriannom: i'm thinking that hardware's not fast enough to do flash in the best scenario
08:32
i'll be curious what the smarter people think though.. pretty sure i have a few of those at home and they look nice and compact
08:32
<Adriannom>
damnit :/
08:33
<abeehc>
again there's smarter people than me in here
08:34gnunux (~emmanuel@194.167.18.244) left irc: Quit: Ex-Chat
08:34
<alkisg>
I never had a geode machine so I'm not at all sure about this, but wasn't it almost unmaintained for some time, and it recently got 2 developers actively working on it? Maybe on some newer xorg it'll go faster...
08:35
<abeehc>
try running at a lower res; if your at 1280 anywawy
08:35
<highvoltage>
in the US, me stgraber and mgariepy drove past a place called "Crack A Geode". we took some picks there, but that's pretty much how we feel about them
08:35
<abeehc>
hehe
08:35
<Adriannom>
alkisg, interesting
08:36
abeehc, 1024, will try lower though
08:36
<abeehc>
haha
08:36
it'd be interesting to see if it goes slight faster
08:37
but of course below 1024 is not cool and hard to navigate
08:37
just a thought
08:38
<Adriannom>
yeah, was worth a try
08:38
monitor doesn't like lower
08:38
in fact it got stuck on 800x :p
08:39
oh, looks like maybe it crashed
08:39
<alkisg>
Try building a natty chroot with more recent x
08:39none (~none@81.144.250.190) joined #ltsp.
08:40
<Adriannom>
i don't really know enough to build from scratch i reckon
08:41
<alkisg>
I mean ltsp-build-client --dist=natty
08:41
...or something similar
08:41
or at least adding some xorg edgers ppa in the chroot, something to get you are more recent x version
08:41
bbl
08:41alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
08:42
<Adriannom>
oooh natty is 11.04, i see :)
08:44Da-Geek (~Da-Geek@80.235.229.178) left irc: Quit: Leaving
08:54wwx (~ww@raamat.polva.ee) left irc: Ping timeout: 240 seconds
08:55
<Adriannom>
thanks for the help guys, really appreciated
09:00xavier_brochard (~xavier@lns-bzn-39-82-255-58-34.adsl.proxad.net) left irc: Ping timeout: 246 seconds
09:01wwx (~ww@raamat.polva.ee) joined #ltsp.
09:09dgroos (~dgroos@s151-177.mpls.k12.mn.us) joined #ltsp.
09:14dobber (~dobber@89.190.197.77) left irc: Remote host closed the connection
09:19none (~none@81.144.250.190) left irc: Remote host closed the connection
09:26
<Roasted>
LDM_DIRECTX = It is set to True by default in Fedora. ------ Are other distros like Ubuntu false by default?
09:27wwx (~ww@raamat.polva.ee) left irc: Ping timeout: 240 seconds
09:28
<highvoltage>
Roasted: yep, it's set to false on all sane distros
09:28
<Roasted>
haha. "sane"
09:28wwx (~ww@raamat.polva.ee) joined #ltsp.
09:28xavier_brochard (~xavier@lns-bzn-39-82-255-58-34.adsl.proxad.net) joined #ltsp.
09:29
<highvoltage>
Roasted: LTSP Live has it set to true, since it's typically just used for demo purposes, but the installed systems don't
09:29
<Roasted>
gotcha
09:38vmlintu (~vmlintu@nblzone-240-143.nblnetworks.fi) joined #ltsp.
09:51
<knipwim>
gentoo is false by default :)
09:51
<dberkholz>
so don't let anyone tell you gentoo users are insane
09:54rad4Christ (~anonymous@165.166.57.122) left irc: Quit: rad4Christ
09:59xavier_brochard (~xavier@lns-bzn-39-82-255-58-34.adsl.proxad.net) left irc: Ping timeout: 250 seconds
10:01dptech (52f2df27@gateway/web/freenode/ip.82.242.223.39) joined #ltsp.
10:01
<dptech>
Hello Could you help me for installation LTSP cluster on Debian ?
10:24patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) left irc: Quit: Ex-Chat
10:27matrix3000 (~matrix@rrcs-70-61-255-226.central.biz.rr.com) left irc: Ping timeout: 246 seconds
10:34patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) joined #ltsp.
10:43matrix3000 (~matrix@rrcs-70-61-255-226.central.biz.rr.com) joined #ltsp.
10:46xavier_brochard (~xavier@lns-bzn-39-82-255-58-34.adsl.proxad.net) joined #ltsp.
10:57alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
11:03xavier_brochard (~xavier@lns-bzn-39-82-255-58-34.adsl.proxad.net) left irc: Ping timeout: 250 seconds
11:04
<Adriannom>
i'm trying to vnc to my ltsp server but it connects to the client instead. how do i differentiate between the client and server?
11:06
alkisg, thanks for the natty hint, it's way faster at booting and maybe slightly faster with graphics
11:06dptech (52f2df27@gateway/web/freenode/ip.82.242.223.39) left irc: Quit: Page closed
11:18bieb (~hbieber@gw1.johnmarshall.edu) joined #ltsp.
11:19patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) left irc: Quit: Ex-Chat
11:19patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) joined #ltsp.
11:19
<bieb>
I have a student that is getting the error "Keyring Default Password needed".. I am running Ubuntu 10.04 ltsp, Crossover is installed so the students can use MS Office. Any ideas what might cause this? or how to get rid of it? I only have 1 student with the issue.
11:24drdata (~drdata@tw2.udallas.edu) joined #ltsp.
11:29matrix3000 (matrix@rrcs-70-61-255-226.central.biz.rr.com) left #ltsp.
11:30
<Gadi>
bieb: that's the gnome keyring kicking in
11:30
bieb: the student can mange her keyrings with gnome-keyring-manager
11:30
<bieb>
Gadi: how do I kick it back?? :)
11:30
<Gadi>
you could remove the daemon from running in the session
11:30
a variety of choices
11:31
:)
11:31
<alkisg>
andygraybeal_: netstat -nap|egrep 'tcp.*vino' ==> you'll probably see more than 1 vnc server running
11:31
<bieb>
its odd.. because I dont have any other students with the issue
11:31
<Gadi>
maybe that student set a password
11:31
at some point
11:31
<alkisg>
Maybe he put a keyring password when prompted for the first time
11:31
<Gadi>
without knowing what she was doing
11:31
<alkisg>
ldm doesn't unlock the default keyring like gdm
11:31
<abeehc>
he or she did for sure
11:32
<bieb>
thats possible
11:32
<Gadi>
yeah, I guess this is one of those times PC encourages me to use "he"
11:32
:)
11:32
he definitely did
11:32
<bieb>
it is a "he" :D
11:32
<Gadi>
she never would have
11:33
<abeehc>
lol
11:33
<bieb>
is there a way to remove the keyring or the password it is looking for?
11:34
will removing the daemon be a good solution long term?
11:34
<abeehc>
looks like ~./gnome2/keyrings
11:35
<bieb>
abeehc: logged in as the student? or from the server?
11:35
when i say from the server.. I mean logged in as the admin user on the server
11:36
<alkisg>
You can manage keyrings from applications > accessories > keyrings or something
11:36
Or sure you can delete the whole keyring in the file system
11:36
<abeehc>
in the user's home folder you could do that
11:37
err find that folder and blow it away;
11:37
i'd be doing on while the user is logged off.. but there are probly betters olutions
11:37
<bieb>
maybe I will start with his home folder.. since no one else has had this issue in 2 years
11:37
<abeehc>
i've never gone as far as disabling the daemon
11:39
<bieb>
sounds good
11:44
<abeehc>
but i mess with profiles all the time
11:45
<Roasted>
I'm running a lab of fat clients on a gigabit network. Now and then 1 or 2 of them just magically freeze in mid use. No warning and no network outage from what I'm seeing. What are the common causes of this?
11:47
<Gadi>
Roasted: when they freeze to they stop responding to pings?
11:47
it could be that you have an IP conflict happening
11:48
<Roasted>
Gadi, I was thinking that, but I'm curious on how I could find the IP of a frozen system to try it.
11:48
<Gadi>
is the ltsp server the dhcp server?
11:48
<alkisg>
netstat and check for nbd
11:48
<Roasted>
No.
11:48
Windows is handling DHCP.
11:48
(for now)
11:49
<Gadi>
is it consistently the same machines?
11:49
<Roasted>
No.
11:49
Nor is it the same users.
11:49
It's happened a total of 3 times in 2 days across 30 systems.
11:49
So while it's very uncommon, it's still enough that raises an eyebrow.
11:51Kicer86 (~Kicer86@host-5db0eeee.sileman.net.pl) left irc: Quit: KVIrc Insomnia 4.0.2, revision: 4740, sources date: 20100627, built on: 2010-08-08 18:29:00 UTC http://www.kvirc.net/
11:51
<Gadi>
I suppose the arp table can tell you which client it can no longer find
11:51
and you can try to figure out what IP that was
11:51
<Roasted>
hmm
11:52
How long of keep alive time is there if a connection drops for whatever reason?
11:54
<Gadi>
you mean in the arp table?
11:54
<Roasted>
I mean if a client drops connection, it'll terminate the session with the server, right?
11:54
No re-establishing to "carry on" as if nothing ever happened.
11:54
I'm questioning if it's an instant drop = 100% termination or if it's only dropped for a few seconds if it will gain ti back.
11:54
<alkisg>
keepalive for nbd is 2h 11m
11:54
So you can use netstat until that point
11:55
<Gadi>
no, he's asking something else
11:55
I think
11:55
<Roasted>
yeah, a little different
11:55
check this...
11:55
if I'm on a client and I unplug the cat5e, am I toast?
11:55
<Gadi>
I think he is asking when does X give up
11:55
<Roasted>
or can I plug it back in and carry on
11:55
<alkisg>
OK - I suggested that for the conflicing IPs part
11:55
<Roasted>
ahh
11:55
gotcha
11:55
<alkisg>
keepalive is the opposite of what you're saying now
11:55
<Roasted>
oh?
11:56
<alkisg>
I.e. "send pings to see when the client has disconnected, so the server process can also die"
11:56
<Gadi>
actually, on the fat client, we should probably add some code to put all procs in stasis until nbd comes back
11:56
<alkisg>
nbd-proxy tries to do that
11:56
It tries to put the file system on hold - I don't remember the correct word
11:56
<Gadi>
nbd-proxy fails at lots of things, tho
11:56
<alkisg>
I don't think it succeeds
11:56
<Gadi>
:)
11:57
<alkisg>
nbd-client -persist was dropped, I wonder why
11:57
<Roasted>
so are what you guys saying is... if I unplug the ethernet, I'm toast?
11:57
No re-gaining the connection?
11:57
<alkisg>
Roasted: the ssh connection is surely lost
11:57
<Roasted>
I'm just trying to question if a quick network hiccup to those boxes could have results in them freezing.
11:57
<alkisg>
So no more remoteapps etc. But fat clients can continue if nbd-client is called with --persist
11:57
<Roasted>
Or if the connection would stay alive long enough for the network to bounce back from the hiccup
11:57
<Gadi>
Roasted: what happens is some procs that need to use the rootfs will start to get angry and fail in different ways
11:57
<alkisg>
I don't know why that was dropped though
11:58
<Gadi>
I would guess IP conflict before network hiccup
11:58
<Roasted>
I'm just trying to find out how I can work a solution into the mix, because if we have 30 systems taking a test and it just blam - 3 freeze...
11:58
it's just hard to say "oh it was just a hiccup, reboot it"
11:58
<Gadi>
or if you have tabs broken on your cables, I would guess that first
11:58
:)
11:58
<alkisg>
Roasted: which graphics cards?
11:58
<Roasted>
alkisg, uhhhh...
11:59
give me a second
11:59
I'm upstairs to where the clients are at the moment
11:59
<alkisg>
lspci -nn -k | grep -A 2 VGA
11:59
OK
11:59
<Gadi>
Roasted: can you ask windows to give them IP reservations?
11:59
it might be annoying, but you may be able to test the theory of IP conflict
11:59
<Roasted>
Gadi, wouldn't an IP conflict have started at the beginning though?
12:00GodFather (~rcc@adsl-68-248-78-158.dsl.sfldmi.ameritech.net) joined #ltsp.
12:00
<Roasted>
I mean these boxes were running for 3-4 hours before they locked up
12:00
<Gadi>
not necessarily
12:00
<alkisg>
What's the lease time in the windows dhcp server?
12:00
<Roasted>
alkisg, a lot of them appear to have nvidia 6200's, but I think the rest have Intel GMA of some sort.
12:00
<Gadi>
when the boxes refresh their lease, something else could have come in and snatched the IP
12:00
<alkisg>
Roasted: check one that froze
12:00
E.g. for intel 8xx you'd know that this is to blame
12:01
<Roasted>
alkisg, I gotta head downstairs quick to check something in the lab, so I'll be back in a few with an answer.
12:01
appreciate it, guys
12:05Trixboxer (~Trixboxer@office.supportdepartment.net) left irc: Quit: "Achievement is not the end, its the beginning of new journey !!!"
12:20xavier_brochard (~xavier@lns-bzn-39-82-255-58-34.adsl.proxad.net) joined #ltsp.
12:22
<Roasted>
Intel 82865G
12:22
alkisg, ^
12:22
<alkisg>
Roasted: https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes
12:22
And there's another one for maverick
12:23
<Roasted>
uh oh...
12:23
<alkisg>
Don't remember which one you have
12:23
<Roasted>
10.10
12:23
<alkisg>
It's a little better there
12:23
With lucid you'd be rebooting them every 10 minutes
12:23
<Roasted>
glad I took your advice with 10.10 then :P
12:23
I'm an LTS fanboy for environments like this.
12:23
<alkisg>
Did I really suggest 10.10?! I don't usually do that...
12:23
<Roasted>
Isn't this kind of kernel dependent though, largely?
12:24
<alkisg>
kernel + xorg
12:24
<Roasted>
Yeah, I was talking about Edubuntu.
12:24
I'm pretty sure it was you.
12:24
Someone here was really saying Edubuntu's support in 10.10 was a home run.
12:24
I guess in regard to LTSP it comes packaged with??
12:24
So I take it an 82865G is considered 8xx?
12:24
<alkisg>
I don't think it was me, I always suggest LTS unless there's unsupported hardware
12:25
https://wiki.ubuntu.com/X/Bugs/Mavericki8xxStatus
12:25
Not sure. I've tried with 845 and 855
12:25
Don't know how 865 fares, I think it's somewhat untested
12:25
<Roasted>
but when I see 8xx I think 3 digit gfx cards... not an 82865
12:25
oh
12:25
82865 = 865?
12:25
<alkisg>
82 is the same
12:25
<Roasted>
ah
12:25
k
12:25
<alkisg>
82855 etc yeah
12:26
<Roasted>
well hey as long as I know it's not something I personally did wrong
12:26
although...
12:26
my boss just bought an ASUS thin client box today to test... I wonder what that had...
12:27
<alkisg>
One of the major 8xx bugs: https://bugs.freedesktop.org/show_bug.cgi?id=27187
12:27
i830: untested i845: still fails the yes wtf > /tmp/wtf test i855: it possibly works i865: untested, might also work - anyone feeling brave?
12:27
<Roasted>
Intel GMA 3150
12:27
<alkisg>
i865 => untested
12:27
The wbinvd alone is known to be insufficient on i865G. If this patch works on i855 we need a guinea-pig to fry his i865G ... Please pass the word ;)
12:27
etc etc read the comments there
12:27
<Roasted>
trying to
12:27
it's oddly still loading
12:27
k, got it
12:28
<alkisg>
It's *big*. Hurt many people for a long time :)
12:28
<Roasted>
Seems like is till does, to a degree.
12:28
it still*
12:28
<alkisg>
In a school I had to install a maverick chroot on an lts server just to work around that bug
12:29
<Roasted>
Doesn't sound like it's entirely fixed in maverick, though.
12:29
Just more tolerable.
12:29
<alkisg>
(and now I'll probably install a hardy one for a school with nvidia/vanta :()
12:29
Right, and I"m not sure if the fix is in natty either
12:29
<Roasted>
oh wow.
12:29
That blows.
12:30
<alkisg>
Btw 8xx was working just fine up until 9.04
12:30
<Roasted>
lol
12:30
gotta love that
12:30
Would you install an old school chroot?
12:31
if you were me?
12:32
<alkisg>
No fat support in 9.04
12:32
<Roasted>
eh
12:32
even if the server is 10.10 and the chroot is old?
12:33
<alkisg>
Yes, the client doesn't know how to logon locally
12:33
You'd need to backport code
12:33
<Roasted>
gotcha
12:33
<alkisg>
I'd use vesa for a while to see if it solves the freezes
12:33
If it does, I'd try a very new kernel or something from xorg edgers etc
12:33
<Roasted>
pretty sure I'm on the newest kernel
12:34
Should I expect a degraded video quality with vesa?
12:34
<alkisg>
The newest kernel isn't on any ubuntu version :)
12:34
<Roasted>
well, yeah. I meant the newest that's easily accessible on ubuntu :P
12:34
<alkisg>
Yes, a lot worse video performance
12:35
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.39-rc1-natty/
12:35
Just for example, not suggesting you should install that
12:35
But I'd at least try a kernel that contains the fix to the bug above
12:36
<Roasted>
Do you know what kernel began support for the fix?
12:36
<alkisg>
No
12:36
It's in the bug + the kernel + ubuntu changelogs
12:36
<Roasted>
Do you know any other graphics cards that exhibit the same issues as this 865? (just to avoid it in case we buy any new hardware soon)
12:37
<alkisg>
8xx are old cards, I think more than 5 years old
12:37
<Roasted>
yeah
12:37
I guess their demand for support isn't at the top of the list.
12:37
<alkisg>
So I don't think you'd need to worry about them if you buy new equipment
12:37
<Roasted>
If we buy new equipment, it wouldn't be for that lab, though.
12:37
It would be to replace the other ncomputing lab.
12:37
our setup is night vs day in some areas
12:38
in some areas we have brand new systems with a ton of horsepower
12:38
other areas our systems are 7 years old and barely running
12:38
so this LTSP thing has been a blessing to pump life into that gear
12:39irule (~irule@189.254.201.226) joined #ltsp.
12:40
<Roasted>
are there no other problematic ones currently on the table to avoid?
12:41
<Gadi>
Roasted: maybe there are some video cards lying around you can pop into the problematic ones
12:41
<Roasted>
Gadi, that's very true.
12:42
I don't think we have 30 though.
12:42
But to grab a few PCI ones might be easy...
12:42
<Gadi>
sounds like you dont need 30
12:42
only a few
12:42
<Roasted>
it's a lab of 30, though.
12:42
There are systems that didn't freeze that have the same chip.
12:42
<Gadi>
right but not all 30 have probs, right?
12:42
<Roasted>
That I checked when I was downstairs.
12:42
Not right now.
12:42
But 3 in 2 days exhibited issues.
12:43
<Gadi>
are all 30 with same chip?
12:43
<Roasted>
My worry is that if we get new thin client gear, little self contained units without PCI slots for expansion, if we'll run into something else like this with the other gear.
12:43
Gadi, Well the lab is split with 2 models, but the 2 models are nearly identical. D530's and DC5000's by HP. The D530's have this 865 intel card that's causing issues. I'll have to check if the 5000's have the same chip.
12:43
If they don't, we're golden. But I thought I remember reading hte primary difference between the 2 boxes is the floppy drive.
12:43
I'll have to check on it though.
12:44
But worst case scenario, 30. Best case, ~15.
12:44xavier_brochard (~xavier@lns-bzn-39-82-255-58-34.adsl.proxad.net) left irc: Ping timeout: 248 seconds
12:44
<Roasted>
Either way I only have about 8 on my shelf here, and they're absolutely huge. Not suited for a SFF like the 530/5000's
12:46
That's why I was just curious if there were any other video chips worth mentioning that have issues, so if we spend our money on new thin client gear (without expansion slots to rectify any graphics issues) we can at least spend our moneyw isely.
12:46xavier_brochard (~xavier@lns-bzn-39-82-255-58-34.adsl.proxad.net) joined #ltsp.
12:47
<Gadi>
yeah - usually intel is a safe bet
12:47
this particular chipset notwithstanding
12:47
intel actually has a team that develops the Linux driver
12:48
so it isn't reverse engineered or divined from crystal balls
12:50
<Roasted>
Yeah, that's what I thought too. I thought Intel was a safe bet but you guys kinda scared me for a minute with this curve ball :P
12:50
Now I feel a little better about our 3150 Intel chipset in the new unit
12:52dgroos (~dgroos@s151-177.mpls.k12.mn.us) left irc: Ping timeout: 240 seconds
12:52dgroos (~dgroos@s151-177.mpls.k12.mn.us) joined #ltsp.
12:54
<Roasted>
with that said, I'm outa here. Thanks again for the info fellas.
12:57irule (~irule@189.254.201.226) left irc: Remote host closed the connection
12:59Roasted (~jason@206.82.22.190) left irc: Ping timeout: 246 seconds
13:02Nick change: evil_root -> zz_evil_root
13:04xavier_brochard (xavier@lns-bzn-39-82-255-58-34.adsl.proxad.net) left #ltsp ("Konversation terminated!").
13:15Gadi (romm@ool-18bbe47a.static.optonline.net) left #ltsp.
13:25irule (~irule@189.161.109.68) joined #ltsp.
13:27bieb (~hbieber@gw1.johnmarshall.edu) left irc: Quit: Leaving.
13:31evil_roou (~evil@host-98-127-40-50.bln-mt.client.bresnan.net) joined #ltsp.
13:32zz_evil_root (~evil@host-98-127-40-50.bln-mt.client.bresnan.net) left irc: Ping timeout: 246 seconds
13:32Nick change: evil_roou -> evil_root
13:33irule_ (~irule@189.161.254.178) joined #ltsp.
13:34irule (~irule@189.161.109.68) left irc: Ping timeout: 252 seconds
13:39irule_ (~irule@189.161.254.178) left irc: Read error: Connection reset by peer
14:01alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
14:03Nick change: evil_root -> zz_evil_root
14:03GodFather (~rcc@adsl-68-248-78-158.dsl.sfldmi.ameritech.net) left irc: Quit: Ex-Chat
14:10vagrantc (~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net) joined #ltsp.
14:51Nick change: zz_evil_root -> evil_root
14:51Nick change: evil_root -> zz_evil_root
15:03drdata (~drdata@tw2.udallas.edu) left irc: Ping timeout: 246 seconds
15:24garymc (~chatzilla@host86-145-43-73.range86-145.btcentralplus.com) joined #ltsp.
15:26dgroos (dgroos@s151-177.mpls.k12.mn.us) left #ltsp.
15:33loctrice (~loctrice@173-165-42-109-Illinois.hfc.comcastbusiness.net) joined #ltsp.
15:34
<loctrice>
can someone answer a tech question for me? I'm a newb with thin clients
15:35
I got everything setup, and I'm on a gigabit lan with my terminals. I can't watch hulu. Was wondering if that's normal
15:35
everything else seems to work fine. there's a delay when drawing windows from the server though
15:37
<HrdwrBoB>
that's not hugely surprising
15:37
it's not really built for video
15:37
<loctrice>
ah, so it's normal.
15:38
I was looking at switching to fat clients, but that sort of defeats my purpose
15:38
<HrdwrBoB>
fat clients will play hulu
15:38
if that's your requirement
15:38
but most thin client setups don't need to play videos :)
15:39
<loctrice>
we were going to set up another station in the living room to play our saved media, and things like hulu
15:39
doesn't look like it now unless I can find some performance tweeks or something
15:39
maybe a thin client running off a flash drive with shared filesystem.
15:40
I have my daughters thin client machine booting from flash now, and it seems to run just fine..... though that makes it 'not' a thin client I guess, heh
15:40garymc (~chatzilla@host86-145-43-73.range86-145.btcentralplus.com) left irc: Quit: ChatZilla 0.9.86.1 [Firefox 3.6.16/20110319135224]
15:40
<abeehc>
nice
15:40
<HrdwrBoB>
still a thin client
15:40
just a locally booted one
15:40
<abeehc>
LDM_DIRECTX=true in lts.conf if you haven't done that might help a bit
15:41
<loctrice>
I'll look for that. I"m still googling right now for performance stuff (I haven't even opened the .conf file)
15:41
I only started messing with this when i got my server put together monday.
15:44
It's still uber cool that I got it all set up :) I booted a random laptop off it just to see , it tickles me
15:54bobby_C (~bobby@85-124-22-227.teleworker.xdsl-line.inode.at) left irc: Ping timeout: 246 seconds
16:01
<abeehc>
lts.conf is your friend and that one directx thing is liek the first thing to try for perf
16:02
it has security remifications you should know about though
16:02
http://manpages.ubuntu.com/manpages/karmic/man5/lts.conf.5.html
16:02
<loctrice>
excellent i'll have to check it out
16:02
I have my network setup pretty tight. the home server segment is locked down
16:03
so I am free(ish) for settings
16:03
<abeehc>
cool then you are in good shape
16:03
i don't recall, hulu is browser based?
16:04
<loctrice>
yes, it is
16:05
<abeehc>
sow hen you say it's not working does youtube pretty well not work on the same machine?
16:05
and not work means laggy or?
16:05
<loctrice>
I shouldn't have said not working, I should have said choppy. it's tolerable for users if it's not fullscreened. Youtube works pretty well, but i haven't tried to full screen it
16:06
<abeehc>
gotcha
16:06
ther's a couple things there first that directx might help.. but ultimately as it is, the rendering is using the client gfx card, does it suck?
16:07
<loctrice>
it's an atom board, so I believe the onboard graphics sucks
16:07
<abeehc>
not bad though intel is the most recommended aroudn here
16:07
they suck but it should work well
16:07
<loctrice>
I got nothing against intel :) , I just didn't go all out on the clients
16:08
<abeehc>
i'd do directx in lts.conf and makre sure that doesn't immediately make it much more tolerable
16:08
and from there you might try it as a local app instead of going all the way to fat clients
16:08
<loctrice>
no rebooting required? I copied the /opt..../../ version to the tftp
16:08
<abeehc>
once you modify lts.conf rebooting client is needed
16:08
<loctrice>
alright
16:08
<abeehc>
which distro?
16:09
<loctrice>
ubuntu maverick
16:09
<abeehc>
word im not super familiar but the lts.conf should maybe exist in /var/lib/tftpboot/arch/lts.conf
16:09
<loctrice>
close, but it's not there by default. I copied it in as per instructions in the file though
16:10
<abeehc>
right on
16:10
i suspect that directive will just make it work very nicely
16:10
mind you HD hulu probly won't rock out on that machine ever
16:10
<loctrice>
lol, that's fine.
16:10
<abeehc>
i think you can just consider if the atom had windows, could it ever play hd
16:10
<loctrice>
hulu is pretty basic for my users though
16:10
<abeehc>
and as i recall, x264 anyway, its slow and can't do fullscreen hd
16:11
right on
16:11
maybe ltsp isnt the best for video.. but at the same time there's a dude around here using it for mythtv frontends
16:11
which i find awesome
16:12
<loctrice>
I'll figure it out eventually. the clients , if booted from flash, run amazing.
16:12
so there just has to be something in my config. the server is solid
16:13
<abeehc>
cool i'm sure you'll find it then
16:13
in my first deplyoment i went localapps for firefox and that made flash much much better
16:13
on crappier hardware than your atom
16:14
<loctrice>
it works better , but you can't full screen it
16:14
I don't have disks or roms in the thin clients
16:14
can I do it with flash drives?
16:14
<abeehc>
actually localapps doesn't require storage
16:14
<loctrice>
.... wonder if chrome would do better
16:15
<abeehc>
chrome might be more of an adventure than ff
16:15
<loctrice>
my answer to "I need a better computer" from my wife was "if you'd let me buy a server" lol. I'm a programmer and my machine was a mammoth when I bought it
16:15
<abeehc>
i wish you luck gotta run, smarter people than me watch this chan and will replay eventualy
16:15
lolllllll
16:15
<loctrice>
I got to google running local apps, thanks for the help
16:16
<abeehc>
ubuntu ltsp wiki is the place to be, also
16:16
they say only if your runnin ubuntu
16:16
https://help.ubuntu.com/community/UbuntuLTSP/
16:16
for me invaluable
16:16
<loctrice>
excellent , ty
16:16
<abeehc>
no worries good luck catch you later
16:21irule (~irule@189.161.175.12) joined #ltsp.
16:26irule (~irule@189.161.175.12) left irc: Read error: Connection reset by peer
16:26irule (~irule@187.139.3.186) joined #ltsp.
16:33Adriannom (~adrian@cpc10-cwma7-2-0-cust15.7-3.cable.virginmedia.com) left irc: Quit: Ex-Chat
16:34
<loctrice>
well, I'm pretty sure i broke it lol
16:38
my flash player on firefox is broken on the thin clients
16:40staffencasa (~staffenca@128-193-150-224.oregonstate.edu) left irc: Quit: Leaving
17:05sbalneav (~sbalneav@S01060018f8f3ce85.wp.shawcable.net) joined #ltsp.
17:05irule (~irule@187.139.3.186) left irc: Ping timeout: 240 seconds
17:12
<loctrice>
I can't get firefox working as a local app. I still have internet, but not with the browser
17:13
<HrdwrBoB>
loctrice: probably because your thin clients don't have internet access directly?
17:14
<loctrice>
I am guessing that is right. I went through the nat walkthrough again, I'm not sure if I'm doing the local app setup right
17:14
dns server is my second nic, and the search domain is myserver.local
17:38slakc (~slakc@c-98-244-160-87.hsd1.ga.comcast.net) joined #ltsp.
17:40vagrantc (~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net) left irc: Read error: Operation timed out
17:48
<loctrice>
I don't get it. I went through this thing and through this thing and still can't get the local app firefox to work
17:50
I did all the ubuntu walkthroughs, as far as I know it should work like a well oiled machine
18:04
I don't know where I went wrong with the nat thing. This is not working out so well, heh
18:13MorningSon (~MorningSo@cpe-70-114-21-95.satx.res.rr.com) left irc: Ping timeout: 240 seconds
18:24loctrice (~loctrice@173-165-42-109-Illinois.hfc.comcastbusiness.net) left irc: Quit: using sirc version 2.211+ssfe
18:25slakc (~slakc@c-98-244-160-87.hsd1.ga.comcast.net) left irc: Quit: Leaving
19:06cyberorg (~cyberorg@opensuse/member/Cyberorg) left irc: Ping timeout: 250 seconds
19:08nothingman (~joshua@32.138.40.159) joined #ltsp.
19:08
<nothingman>
hi, all
19:11
<sbalneav>
win 3
19:11sbalneav (~sbalneav@S01060018f8f3ce85.wp.shawcable.net) left irc: Quit: leaving
19:27cyberorg (~cyberorg@opensuse/member/Cyberorg) joined #ltsp.
19:43nothingman (~joshua@32.138.40.159) left irc: Ping timeout: 240 seconds
20:09drdata (~drdata@pool-173-57-189-158.dllstx.fios.verizon.net) joined #ltsp.
20:28loathing (~khudson@internal-nat.djnetworks.net) left irc: Ping timeout: 250 seconds
20:35Nick change: zz_evil_root -> evil_root
20:37Nick change: evil_root -> zz_evil_root
20:52Nick change: zz_evil_root -> evil_root
20:53Nick change: evil_root -> zz_evil_root
21:06alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
21:35alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
21:45Kicer86 (~Kicer86@host-5db0eeee.sileman.net.pl) joined #ltsp.
22:11Kicer86 (~Kicer86@host-5db0eeee.sileman.net.pl) left irc: Quit: KVIrc Insomnia 4.0.2, revision: 4740, sources date: 20100627, built on: 2010-08-08 18:29:00 UTC http://www.kvirc.net/
22:42alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
22:47wwx (~ww@raamat.polva.ee) left irc: Ping timeout: 240 seconds
22:59wwx (~ww@raamat.polva.ee) joined #ltsp.
23:15Kicer86 (~Kicer86@host-5db0eeee.sileman.net.pl) joined #ltsp.
23:53Kicer86 (~Kicer86@host-5db0eeee.sileman.net.pl) left irc: Read error: No route to host
23:57Kicer86 (~Kicer86@host-5db0eeee.sileman.net.pl) joined #ltsp.
23:58alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
00:00--- Thu Mar 31 2011