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


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

00:13
<bac__>
How is the Wiki going?
00:16Da-Geek has joined IRC (Da-Geek!~Da-Geek@11.74.155.90.in-addr.arpa)
00:19Da-Geek has left IRC (Da-Geek!~Da-Geek@11.74.155.90.in-addr.arpa, Client Quit)
00:39Steve_the_Pirate has joined IRC (Steve_the_Pirate!~Gary@cpc16-haye17-2-0-cust169.haye.cable.virginmedia.com)
00:45Steve_the_Pirate has left IRC (Steve_the_Pirate!~Gary@cpc16-haye17-2-0-cust169.haye.cable.virginmedia.com, Ping timeout: 260 seconds)
01:24andygraybeals has joined IRC (andygraybeals!~andy@h64.71.213.151.dynamic.ip.windstream.net)
01:38mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, Remote host closed the connection)
02:11alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
02:37Parker955_Away is now known as Parker955
03:44andygraybeals has left IRC (andygraybeals!~andy@h64.71.213.151.dynamic.ip.windstream.net, Ping timeout: 248 seconds)
05:13Parker955 is now known as Parker955_Away
08:20map7 has left IRC (map7!~map7@ppp118-209-74-113.lns20.mel4.internode.on.net, Ping timeout: 244 seconds)
08:41
<Hyperbyte>
bac__, hm?
09:09kusznir has left IRC (kusznir!~kusznir@casas-net.ailab.wsu.edu, Ping timeout: 240 seconds)
09:11alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
09:12kusznir has joined IRC (kusznir!~kusznir@casas-net.ailab.wsu.edu)
10:10bac__ has left IRC (bac__!~admin@64.223.214.150, Quit: bac__)
10:10alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
10:33nubae has joined IRC (nubae!~sysadmin@opensuse/member/nubae)
10:34
<nubae>
!seen alkisg
10:34
<ltsp>
nubae: alkisg was last seen in #ltsp 16 hours, 1 minute, and 0 seconds ago: * alkisg is trying to put ssl support in epoptes :(
10:34
<nubae>
!seen hyperbyte
10:34
<ltsp>
nubae: hyperbyte was last seen in #ltsp 1 hour, 53 minutes, and 2 seconds ago: <Hyperbyte> bac__, hm?
10:35
<nubae>
Hyperbyte, ah u are there.... :-)
10:35
maybe u can help me with a question... I want all my fat clients to have non-priveledged access to their hds
10:35
easy way to do that?
10:51map7 has joined IRC (map7!~map7@ppp118-209-74-113.lns20.mel4.internode.on.net)
11:07Must`see1 has joined IRC (Must`see1!backess@78-61-170-109.static.zebra.lt)
11:08Must`see1 has left IRC (Must`see1!backess@78-61-170-109.static.zebra.lt)
11:27leio has left IRC (leio!~leio@gentoo/developer/leio, Read error: Operation timed out)
11:29leio has joined IRC (leio!~leio@gentoo/developer/leio)
11:33nubae has left IRC (nubae!~sysadmin@opensuse/member/nubae, Quit: Ex-Chat)
12:55laurei has joined IRC (laurei!3a069039@gateway/web/freenode/ip.58.6.144.57)
12:55
<laurei>
hello ltspers
12:56
i have a problem installing graphics card in the chroot because i believe it's trying to probe for it, what should I do?
13:09
<Hyperbyte>
laurei, install the kernel module manually
13:09andygraybeals has joined IRC (andygraybeals!~andy@h64.71.213.151.dynamic.ip.windstream.net)
13:28MrDoh2 has joined IRC (MrDoh2!~mrdoh@r74-192-178-144.htvlcmta01.hnvitx.tl.dh.suddenlink.net)
13:30MrDoh has left IRC (MrDoh!~mrdoh@r74-192-178-144.htvlcmta01.hnvitx.tl.dh.suddenlink.net, Read error: Connection reset by peer)
13:59alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
14:01
<alkisg>
laurei: which graphics card? nvidia?
14:06ogra_ has left IRC (ogra_!~ogra@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 256 seconds)
14:36komunista has joined IRC (komunista!~slavko@adsl-195-168-248-132.dynamic.nextra.sk)
14:39map7 has left IRC (map7!~map7@ppp118-209-74-113.lns20.mel4.internode.on.net, Ping timeout: 260 seconds)
14:42laurei has left IRC (laurei!3a069039@gateway/web/freenode/ip.58.6.144.57, Quit: Page closed)
15:14toscalix has joined IRC (toscalix!~toscalix@188.87.95.79)
15:40Parker955_Away is now known as Parker955
15:40bac__ has joined IRC (bac__!~admin@64.223.214.150)
15:58bac__ has left IRC (bac__!~admin@64.223.214.150, Quit: bac__)
15:59loather has joined IRC (loather!~khudson@wsip-98-175-250-115.sd.sd.cox.net)
16:42komunista has left IRC (komunista!~slavko@adsl-195-168-248-132.dynamic.nextra.sk, Ping timeout: 276 seconds)
16:56alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Read error: Connection reset by peer)
16:57alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
17:06matrix30001 has joined IRC (matrix30001!~Eric@rrcs-70-61-255-227.central.biz.rr.com)
17:28alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
17:41toscalix has left IRC (toscalix!~toscalix@188.87.95.79, Read error: Connection reset by peer)
17:53lifeboy has joined IRC (lifeboy!~lifeboy@196.215.143.190)
17:56sviesusisalus has joined IRC (sviesusisalus!~sviesusis@46.251.62.244)
17:57vmlintu has joined IRC (vmlintu!~vmlintu@nblzone-240-143.nblnetworks.fi)
18:02sviesusisalus has left IRC (sviesusisalus!~sviesusis@46.251.62.244, Ping timeout: 240 seconds)
18:08sviesusisalus has joined IRC (sviesusisalus!~sviesusis@46.251.62.244)
18:16komunista has joined IRC (komunista!~slavko@adsl-195-168-248-132.dynamic.nextra.sk)
18:19
<lifeboy>
Hi all
18:19
I get "Error: failed to connect to NBD Server 172.16.0.1:2000"
18:20
but I have read almost all reports of this condition and nothing I can find applies
18:20
Server: Ubuntu Server 10:10 64bit
18:20
Client: Vortex86MX 1GHz, 1GB RAM.
18:21
On the server nbd-server listens in port 2000 and there is actually a connection from the client!
18:21
# netstat -tunap | grep 2000
18:22
tcp 0 0 0.0.0.0:2000 0.0.0.0:* LISTEN 5949/inetd
18:22
tcp 0 0 172.16.0.1:2000 172.16.0.24:48051 ESTABLISHED 12839/sh
18:22
Anyone that can help trace this problem?
18:23
Please? ;-)
18:29drdata has left IRC (drdata!~drdata@pool-173-57-189-158.dllstx.fios.verizon.net)
18:32Steve_the_Pirate has joined IRC (Steve_the_Pirate!~Gary@cpc16-haye17-2-0-cust169.haye.cable.virginmedia.com)
18:36sviesusisalus has left IRC (sviesusisalus!~sviesusis@46.251.62.244, Ping timeout: 258 seconds)
18:47laurei has joined IRC (laurei!3a069039@gateway/web/freenode/ip.58.6.144.57)
18:49
<laurei>
i am trying to install fglrx for an ATI radeon 5450
18:50
but the card is installed on a fat client, not the server, so the installation fails
18:51cliebow has joined IRC (cliebow!~cliebow@66.63.66.218)
18:56
<NeonLicht>
Have you installed it into the chroot?
19:01
<Hyperbyte>
lifeboy, try telnetting to port 2000 from a machine in the same network as your client, see if you can get a connection.
19:04
<laurei>
yeah ive installed in the chroot but it wants to modprobe and it fails
19:24Parker955 is now known as Parker955_Away
19:24
<laurei>
thanks, i got it working installing the repo driver instead of the website driver
19:32
<lifeboy>
Hyperbyte, yes, connection in fine
19:32
is fine, I mean
19:33andygraybeals has left IRC (andygraybeals!~andy@h64.71.213.151.dynamic.ip.windstream.net, Ping timeout: 258 seconds)
19:34
<lifeboy>
Here's what syslog says on the server:
19:34
Oct 30 19:57:56 Ashton nbdrootd[12839]: connect from 172.16.0.24 (172.16.0.24)
19:34
Oct 30 19:57:56 Ashton nbd_server[12840]: connect from 172.16.0.24, assigned file is /opt/ltsp/images/i386.img
19:34
Oct 30 19:57:56 Ashton nbd_server[12840]: Size of exported file/device is 916684800
19:34
But shortly after that, the client gives the error message
19:35
I also tried the nbd commands from busybox, but something is wrong, although I don't know what
19:36
Here are the commands (I looked in ltsp_nbd script)
19:36
nbd-proxy 172.16.0.1 2000 2000
19:36
Response: Hangup
19:36
then I do
19:37
nbd-client 127.0.0.1 2000 /dev/nbd0
19:37
and I get back:
19:38
Error: Cannot open NBD: No such file or directory
19:38
Please ensure the 'nbd' module is loaded
19:38
'modprobe -l | grep nbd' returns nothing
19:39
<Hyperbyte>
!disable-nbd-proxy
19:39
<ltsp>
Hyperbyte: disable-nbd-proxy: To disable nbd-proxy on Ubuntu Lucid (10.04) and Maverick (10.10), follow the instructions in comment #13 in this link: https://bugs.launchpad.net/ltsp/+bug/589034
19:40
<Hyperbyte>
Probably not related, but do that anyways.
19:42
<lifeboy>
Hmmm... I'll go do that, but is that standard? I used ltsp-make-client to create a 32bit Lucid client.
19:43
<Hyperbyte>
ltsp-build-client you mean?
19:43
nbd-proxy is enabled by default on 10.04 and 10.11, but it's causing lots of problems. Disabled again by default as of 11.04
19:44
Try disabling it first, to make sure it's not causing this problem as well.
19:45
<lifeboy>
Ah, yes, I'm reading that thread now. I have a fast switch (HP ProCurve) and a "slower" client, although not an Atom. Let's see
19:46laurei has left IRC (laurei!3a069039@gateway/web/freenode/ip.58.6.144.57, Quit: Page closed)
20:01
<lifeboy>
Hyperbyte, yes, I meant ltsp-build-client. However, disabling the proxy and loading the never version of ltsp_nbd script, only results in multiple retries on the nbd connect.
20:02Steve_the_Pirate has left IRC (Steve_the_Pirate!~Gary@cpc16-haye17-2-0-cust169.haye.cable.virginmedia.com, Quit: Leaving)
20:02
<lifeboy>
I still get repeated similar errors as before
20:04
Should I be worried that there is no kernel module 'nbd' on the thin client OS's busybox?
20:05
Or is that just busybox's way or guessing what a problem could be?
20:10vagrantc has joined IRC (vagrantc!~vagrant@209-6-46-132.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com)
20:17
<vagrantc>
yay: http://packages.qa.debian.org/libp/libpam-sshauth/news/20111030T130225Z.html
20:33sviesusisalus has joined IRC (sviesusisalus!~sviesusis@46.251.62.244)
20:43tuboil has joined IRC (tuboil!~local-adm@46-126-143-167.dynamic.hispeed.ch)
20:49lifeboy has left IRC (lifeboy!~lifeboy@196.215.143.190, Remote host closed the connection)
21:00lifeboy has joined IRC (lifeboy!~lifeboy@196.215.143.190)
21:01
<lifeboy>
I have restarted the server for good measure, just incase I missed some service and to see what would happen. Now I don't see nbd-server messages in syslog anymore, but if I telnet to the service it's ready:
21:01
telnet 172.16.0.1 2001
21:01
Trying 172.16.0.1...
21:01
Connected to 172.16.0.1.
21:01
Escape character is '^]'.
21:01
NBDMAGICB��S6��^]
21:01
telnet> quit
21:01
Connection closed.
21:01
roland@Ashton:~$
21:02
And the client says: Failed to connect to NBD server 172.16.0.1:2001
21:03
as a results of the previously mentioned:
21:03
"Error: Cannot open NBD: No such file or directory
21:03
Please ensure the 'nbd' module is loaded"
21:06sviesusisalus has left IRC (sviesusisalus!~sviesusis@46.251.62.244, Quit: Leaving)
21:13cliebow has left IRC (cliebow!~cliebow@66.63.66.218, Read error: Connection reset by peer)
21:13cliebow has joined IRC (cliebow!~cliebow@66.63.66.218)
21:17
<lifeboy>
What else can I check? nbd-server (nbdrootd) is running on port 2001, nbd-proxy is disabled, network is up, all seems well, except it isnt'! :-(
21:18
<vagrantc>
can a client on that network actually get to the ip address? is there a firewall on the server?
21:18cliebow has left IRC (cliebow!~cliebow@66.63.66.218, Read error: Connection reset by peer)
21:18cliebow__ has joined IRC (cliebow__!~cliebow@66.63.66.218)
21:23
<lifeboy>
vagrantc, yes, the client actually boots fine, get's a DHCP address and connects to the server on nbd port 2001. I can also boot my notebook with a standard i386 client image. The modified image for the vortex86 chip just has the network card (r6040), sound and video added in.
21:23
There's not firewall at the moment. Just one server and one client I'm using to set this up.
21:24
All my other LTSP servers are running Maverick 10.10 without problems... out of the box with similar clients (eBox 4300), although they have VIA processors rather than Vortex86's
21:26
I don't want to go to other releases at this stage. All on 10.10 is better from a support perspective. I was running 10.04, but some applications forced me to upgrade a while ago to 10.10.
21:26
<vagrantc>
lifeboy: so it's a specific machine that's not working, but others on the same network work fine?
21:32komunista has left IRC (komunista!~slavko@adsl-195-168-248-132.dynamic.nextra.sk, Quit: Leaving.)
21:36cliebow__ has left IRC (cliebow__!~cliebow@66.63.66.218, Ping timeout: 240 seconds)
21:49Parker955_Away is now known as Parker955
22:02khildin has joined IRC (khildin!~khildin@ip-80-236-227-20.dsl.scarlet.be)
22:18alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
22:20khildin has left IRC (khildin!~khildin@ip-80-236-227-20.dsl.scarlet.be, Quit: I'm gone, bye bye)
22:22lifeboy has left IRC (lifeboy!~lifeboy@196.215.143.190, Ping timeout: 255 seconds)
22:35Damianos has joined IRC (Damianos!~Damianos@adsl-070-145-074-043.sip.cha.bellsouth.net)
22:42lifeboy has joined IRC (lifeboy!~lifeboy@196.215.143.190)
22:44
<lifeboy>
Well, these Vortex86 machines require a customised boot image, so when I boot a standard image with it, I get an error that says I should use a kernel without cmov support. On the other hand when I try to boot my laptop, which boot fines with a standard lucid i386 image, I get a kernel panic since the vortex86 image doesn't boot a standard pentium class machine.
22:46
<vagrantc>
didn't ubuntu completely drop support for pre i686 kernels?
22:47
<lifeboy>
So in a way, it's only these clients, yes, but I have a whole lot of them that I need to deploy. I have a flashcard image that runs fine locally, but cannot find any documentation on how to integrate LTSP client-script into an image like that, except for one very high-level document on it.
22:47
Only after Lucid. Maverick was the first release that dropped it.
22:47
<vagrantc>
ah
22:47
try a debian -486 kernel?
22:48
<lifeboy>
Which is why I'm booting the client with 10.04
22:48Damianos has left IRC (Damianos!~Damianos@adsl-070-145-074-043.sip.cha.bellsouth.net)
22:49
<lifeboy>
I could, although it will prove a major mission, since I can't find any documentation on how to load another client with Ubuntu (or ltsp for that matter). Do you have something that I don't know of / can't find?
22:49
<vagrantc>
you mean how to load specific clients with a different kernel?
22:50
<lifeboy>
no, all my clients going forward will be the same
22:50
oh, yes, I mistunderstood that
22:50
<alkisg>
lifeboy: so you built a customized initrd? Maybe you forgot to force loading of the nbd module?
22:51
Try it from the initramfs> prompt, to modprobe nbd
22:51
<vagrantc>
alkisg: working on epoptes hoping to upload to experimental soonish
22:51
<alkisg>
vagrantc: cool, I just made a first successful attempt of integrading openssl, I'll have it ready in a couple of days
22:51
<lifeboy>
Nope, as far as I can tell it's there in the config, but it's not on client when I check it with modprobe. Which is why I asked earlier about that.
22:51
<alkisg>
You home already?
22:52
<vagrantc>
alkisg: no, in boston for a night
22:52
<alkisg>
Ah. We lost our flight and are still in WC :
22:52
:(
22:52
<vagrantc>
alkisg: i figured i'd get it uploaded to experimental, and then it'll be easier when ssl support is ready
22:52
<alkisg>
We'll arrive in orlando about ... 11pm
22:52
Yup, having it in experimental would be awesome ;)
22:53
<vagrantc>
you're still in the WC?
22:53
<alkisg>
Yes, all 3 of us, and the plane is delayed 2 hours etc....
22:53
lifeboy: so if you manually run modprobe, does it succeed then?
22:54
<vagrantc>
alkisg: so, i went ahead and switched to dh --with python2, instead of pycentral, as ftp-master might not accept pycentral for something new (since it's deprecated)
22:54
<alkisg>
Also, ok, you need a custom kernel, but why a custom initramfs?
22:54
The code there needs to be recompiled for non-686?
22:54
<vagrantc>
lifeboy: does your initramfs have different kernel modules than the running version of the kernel?
22:54
<alkisg>
vagrantc: np, we'll use that in 12.04 anyway which contains python2
22:55
<vagrantc>
alkisg: i've pushed my own branch to alioth so i can hack on it and maybe merge with yours later
22:56
<alkisg>
vagrantc: OK, I'll check later on if launchpad would accept a recipy with remote branches - otherwise I'll just copy your debian/
22:56
<vagrantc>
alkisg: you can also have launchpad mirror my branch (once it's actually published ... it may take a bit)
22:57
<lifeboy>
vagrantc: I have /opt/ltsp/i386/usr/share/initramfs-tools/scripts/local-top/nbd on the server. And also
22:57
/opt/ltsp/i386/usr/share/initramfs-tools/hooks/nbd
22:57
. /usr/share/initramfs-tools/hook-functions
22:57
<alkisg>
vagrantc: nice, I didn't know that
22:57
<lifeboy>
force_load nbd
22:57
auto_add_modules net
22:57
copy_exec /sbin/nbd-client /sbin
22:58
<alkisg>
lifeboy: so if you do it manually from the prompt, does it work?
22:58
modprobe nbd, and then run nbd-client server port /dev/nbd0
22:58
<lifeboy>
no, it doesn't.
22:59
modprobe nbd returns nothing
22:59
<alkisg>
Is nbd there?
22:59
in /lib/modules etc
22:59
<vagrantc>
uname -r and /lib/modules/$(uname -r) present?
22:59
<lifeboy>
Ah, wait, if it says nothing, it means that it's ok, it had loaded?
23:00
eh, has loaded
23:00
<vagrantc>
not necessarily
23:01Parker955 is now known as Parker955_Away
23:01
<alkisg>
lsmod would tell you
23:01
or ls /dev/nbd*
23:02
You can also use insmod once you locate the nbd module path
23:02
<lifeboy>
When I do nbd-client 172.16.0.1 2001 /dev/nbd0 I get the error:
23:02
Error: Cannot open NBD: No such file or directory
23:02
Please nsure the 'nbd' module is loaded
23:02
<alkisg>
Try the modprobing thing first
23:02
If you see that your nbd module isn't there, you'll know your problem
23:04
<lifeboy>
nbd is not there, that I know, but I wasn't shure that it was needed (as a module)
23:04
<alkisg>
It is
23:04
You should see it in /lib/modules/kernelver/kernel/drivers/block/nbd.ko
23:05
If it's not there, that's the problem
23:05
<vagrantc>
is it a custom kernel?
23:06
<lifeboy>
No, standard lucid
23:06
32 bt
23:07
On the server that is what I can find:
23:07
# find / -name "nbd.*"
23:07
/opt/ltsp/i386/usr/include/linux/nbd.h
23:07
/opt/ltsp/i386/usr/src/linux-headers-2.6.32-34/include/linux/nbd.h
23:07
/opt/ltsp/i386/usr/src/linux-headers-2.6.32-34-generic/include/linux/nbd.h
23:07
/opt/ltsp/i386/usr/src/linux-headers-2.6.32-34-generic/include/config/blk/dev/nbd.h
23:07
/opt/ltsp/i386/lib/modules/2.6.32-34-generic/kernel/drivers/block/nbd.ko
23:08
<vagrantc>
from the booted initramfs, do you have the nbd.ko file?
23:09
alkisg: i'm working on building some virtual machines to test with ... if those ever finish, i'll test epoptes and upload
23:09
<alkisg>
vagrantc: you can also use xnest and fool epoptes that you're using a standalone machine
23:10
Using VMs or LTSP isn't strictly necessary...
23:10
<vagrantc>
no, but i'd like to keep it isolated
23:10
<alkisg>
But sure VMs is the easiest way :)
23:10
<lifeboy>
Is that the one that Ubuntu's 'ltsp-build-client --dist=lucid --arch=i386' should have installed?
23:11
I have /opt/ltsp/i386/lib/modules/2.6.32-34-generic/kernel/drivers/block/nbd.ko
23:11
<alkisg>
lifeboy: the problem is that you don't copy the module to the initramfs. One of your initramfs hooks isn't working
23:11
Check if you're missing one of the ltsp files there under initramfs-tools/
23:11
<vagrantc>
does ubuntu have lsinitramfs?
23:11
<lifeboy>
yes
23:12
<alkisg>
I don't see it in my lucid...
23:13
<lifeboy>
My server runs Maverick
23:13
64bit
23:14
<alkisg>
ok
23:14
<lifeboy>
vagrantc: which ltsp files/scripts should be under initramfs-tools?
23:15* vagrantc was trying to determine if the booted kernel and initramfs are the same version ...
23:16
<vagrantc>
so it doesn't matter what's on the server, like alkisg keeps saying, check in the booted initramfs
23:16
<lifeboy>
You mean, on the client in busybox?
23:17
<vagrantc>
yes!
23:17
troubleshoot the problem where the problem is occurring :)
23:19
<lifeboy>
Ok I only have hid/ net/ staging/ usb/ and video/ in the kernel/drivers dir on the client
23:20
no block/
23:20
<vagrantc>
what's the output of: uname -r
23:20
<lifeboy>
2.6.34.1-vortex86-sg
23:21
<vagrantc>
and is there /lib/modules/2.6.34.1-vortex86-sg ?
23:21andygraybeals has joined IRC (andygraybeals!~andy@h64.71.213.151.dynamic.ip.windstream.net)
23:21
<lifeboy>
yes
23:21
<vagrantc>
this is a standard ubuntu kernel?
23:22
<lifeboy>
yes, but norhtec provides a .deb that patched the ethernet, sound and video drivers into the kernel (as they put it)
23:23
<vagrantc>
it seems like they built a non-standard kernel
23:24
grep NBD /opt/ltsp/i386/boot/config-*
23:25
<lifeboy>
# CONFIG_BLK_DEV_NBD is not set
23:25
<vagrantc>
there's your problem
23:25
no NBD support in your kernel
23:26
this doesn't sound like a standard ubuntu kernel at all
23:26
lifeboy: so the kernel shipped with ubuntu didn't work?
23:27miks has joined IRC (miks!~chatzilla@50-39-205-135.bvtn.or.frontiernet.net)
23:27
<miks>
Alright guys, I've finally got my lab up and running for the time being, but it took rolling back to Ubuntu 9.10 to do it :-(
23:28
<lifeboy>
Hmm... This is weird. Let me look at the contents of their patch deb file again. It's all pretty new to me, I've never dug in these things before.
23:28
<vagrantc>
miks: that was with the wrong video port problem?
23:28
<lifeboy>
The kernel needs the Realtec r6040 ethernet driver to boot, which is why sent me the .deb to install
23:28
<miks>
Yeah
23:28
Never got those machines working under anything latet than 9.10
23:29
<Hyperbyte>
miks, I had the same problem with my thin clients on Ubuntu 11.04. It's easily fixed with some lts.conf/xorg.conf options.
23:29
<miks>
So I've got 9.10 running now, with an intention to upgrade later this year to something recent, and deal with those machines then
23:29
I had to just get things running, so the students could get in there tomorrow. I've had the lab closed too long already
23:29
Over winter vacation I'll do some more 11.04 testing when my blood pressure is back down :-)
23:30
The one thing I can't get working in 9.10 though, is shutting down the thin-clients automatically with CRON
23:30
I set it all up according to documentation, but the time for the cron job comes and goes and nothing happens
23:31
<lifeboy>
vagrantc: The kernel that shipped with Ubuntu Lucid panics as soon as the network driver is not found.
23:31
<alkisg>
lifeboy: just put the network driver there
23:31
It was a bug in the initramfs-tools, it was fixed in later versions
23:31
!adding-modules
23:31
<ltsp>
alkisg: adding-modules: If your clients won't boot with messages like 'eth0: link not ready', maybe you're missing an initramfs-module: https://help.ubuntu.com/community/UbuntuLTSP/AddingModules
23:31
<miks>
Any ideas where to look to see what's going wrong? Or alternatively, making it so you can actually use the "Shut Down" button with thin clients (with autologin, Shut Down results in a login loop)
23:31
<vagrantc>
miks: the CRON support may be broken in the version you're running
23:32
<miks>
Doh :-(
23:32
<lifeboy>
I started with this 3 days and know a great deal more by now that I did then. Maybe I should do a clean client install and add the drivers by hand
23:32
<alkisg>
lifeboy: which network driver is that?
23:32
atl1c?
23:32
<vagrantc>
miks: use guestlogin and timedlogin instead of autologin
23:32
<miks>
Oooh
23:32
I'm not familiar with those
23:33
Will that make it so that the "Shut Down" option in Ubuntu actually shuts down the thin client?
23:33
<vagrantc>
miks: check the lts.conf manpage ...
23:33
!lts.conf
23:33
<ltsp>
vagrantc: lts.conf: http://manpages.ubuntu.com/lts.conf
23:33
<lifeboy>
no, r6040
23:33
<miks>
I'll check it out right now
23:34
<vagrantc>
miks: it will prevent the login loop, but you need to do more to get the shutdown button to actually work as expected
23:34
<miks>
Vagrant: I'm hoping to pick up some more machines and keyboards from Nate this week, so I hope to replace the 3 troublemaking computers with those
23:34
<vagrantc>
the shutdown button works properly with LXDE in debian testing :)
23:35
<alkisg>
lifeboy: ah, I think I remember someone having a problem with that driver, but we helped him solve it. Check the logs in the /topic.
23:36
<miks>
Throwing in LXDE at this point might panic teachers and students. Anything I can do to get the shutdown button working properly in Gnome on 9.10?
23:36
<vagrantc>
not sure what version ubuntu introduced the shutdown features
23:36
and not sure if it's automatic
23:37
<miks>
Ah
23:37
<alkisg>
miks: you mean the shutdown menu inside the gnome session?
23:37
<vagrantc>
it feels like a long time ago ... but since i don't use ubuntu i don't know what versions are even possible to suppotr
23:37
<miks>
Yes
23:37
<lifeboy>
So will the mkinitramfs command automagically make all the kernel modules that are placed in /opt/ltsp/i386/lib/modules/2.6.32-34-generic/kernel/drivers/block/nbd.ko (in the case of the kernel I'm using here) available to the client in booting? Or do these have to be compiled "in" to be supported?
23:37
<miks>
The gnome shutdown. If there's some way to make a shortcut that does it, I could put that on desktops even
23:38
<alkisg>
miks: I've a ppa with a patched gnome-session for that, it works in 10.04 and maybe in 9.10, I don't remember. I'd suggest you used 10.04 instead, and just use xrandr for the problematic clients.
23:38
The desktops part is easier
23:38
<vagrantc>
lifeboy: if you're using a properly packaged kernel, initramfs-tools will include all the right modules in most cases ...
23:39
<miks>
Well I can easily make a shortcut and lock it on everyone's desktop, if I can figure out how to make it work
23:39
<alkisg>
miks: There's a shutdown.desktop example somewhere in the ltsp package
23:40
./localapps/doc/examples/ltsp-shutdown.desktop
23:40
./localapps/doc/examples/ltsp-restart.desktop
23:40
!ltsp-source
23:40
<ltsp>
alkisg: ltsp-source: at http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/files
23:41
<alkisg>
miks: so, download the examples from: http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/files/head:/localapps/doc/examples/
23:42
<miks>
Got it. So I just save this as a .desktop file on the thin client, and then running the file should shut it down?
23:42
<lifeboy>
vagrantc: I principle I understand that, but I just "add the r0604 network module" and the kernel doesn't know it, will it work? (by just adding the module I mean adding it to /opt/ltsp/i386/etc/initramfs-tools/modules)
23:42
<vagrantc>
i think that depends on features introduced later
23:43
<alkisg>
miks: just, if you put them on the menus or on the user desktops, clicking on those files would shutdown the client
23:43
<vagrantc>
lifeboy: i think you'll need to add it to a hook to actually include it
23:44
<miks>
alkisg: Awesome. I'll give this some testing later tonight when I'm back in the lab
23:44
<alkisg>
lifeboy: I added a hook for the inclusion process in the wiki page I pasted above
23:44
<lifeboy>
https://help.ubuntu.com/community/UbuntuLTSP/AddingModules Yes, just reading that now
23:44
Thanks
23:45
<vagrantc>
miks: that feature depends on code that was added two months after 9.10 was released...
23:45
<miks>
Oh snap!
23:46
:-(
23:46
<vagrantc>
though you could manually add a few more files and it should work...
23:46
<miks>
What files would I need?
23:47
<alkisg>
vagrantc: what part? xprop etc? it should work in 9.10 afaik...
23:48
<vagrantc>
alkisg: the ltsp-logout-action code was first introduced in 12/2009
23:48
(well, at first it was ldm-logout-action)
23:48
<alkisg>
Hm. I remember using that with 9.10, but maybe I was using my ppa...
23:49
<vagrantc>
using xatoms/xprop ... there might have been an earlier implementation that should work
23:49
miks: it's a little tricky to support something so old
23:49
<miks>
I know
23:49
<Hyperbyte>
miks, not to rub it in - but a few days ago I told you solving this problem with proper xrandr config for the machines would be easiest.
23:49
<miks>
Hyperbyte - I know, but I didn't get anywhere with it
23:50
<Hyperbyte>
(I guess I am kinda rubbing it in, a little) :)
23:50
<miks>
I've spent a TON of hours in this lab over the last few weeks, and am burning out fast
23:50
<alkisg>
miks: if you put another monitor, did you get a visible screen?
23:50
<miks>
Yeah
23:50
<alkisg>
And you tried xrandr --output xxx --off --output yyy --auto, and it didn't work?
23:50
<miks>
Correct
23:50
I never got the maine screen working
23:51
The external screen shut off, but the main one never turned on
23:51
<alkisg>
Not even with the gnome monitor settings dialog?
23:51
<miks>
Correct. Not even in gnome
23:52
<alkisg>
OK, you probably needed a module parameter then. Which graphics card is this? Intel?
23:53
<miks>
Yeah, they are Gateway Profile 4 machines, which I believe use Integrated Intel
23:53cliebow has joined IRC (cliebow!~cliebow@66.63.66.218)
23:54
<alkisg>
video:lvds-1:d
23:55
<miks>
I have to run and pick up my son now, but I'll be back on later. Thank you all for your help! I'm hoping I can get some replacement machines from FreeGeek this week, and upgrade everything to 11.10 so I'm up to date
23:55
alkisg: How do i implement that?
23:55
<alkisg>
It's something like this, if you ever put 10.04 or a newer version back, tell me to look at my notes
23:56
You put that in pxelinux.cfg/default, or you use a modprobe.conf snippet, I think Hyperbyte has one
23:57miks has left IRC (miks!~chatzilla@50-39-205-135.bvtn.or.frontiernet.net, Quit: ChatZilla 0.9.87 [Firefox 7.0.1/20110928134238])
23:57
<alkisg>
Let's tackle it after the upgrade
23:57* alkisg is at the airport... :-/
23:58cliebow has left IRC (cliebow!~cliebow@66.63.66.218, Ping timeout: 244 seconds)