|02:37||vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)|
|04:09||||cw2 has left IRC (||cw2!~chrisw@unaffiliated/cw/x-1182934, Ping timeout: 268 seconds)|
|04:10||||cw has joined IRC (||cw!~chrisw@unaffiliated/cw/x-1182934)|
|07:44||jp_ has joined IRC (jp_!7aab73eb@gateway/web/freenode/ip.184.108.40.206)|
Hi. I have installed LTSP on a normal desktop (Intel Core2 / 4GB ram) running 64bit Kubuntu 16.04.3LTS. And I want to connect to it using a RaspberryPi-3.
I followed the steps as in : http://wiki.ltsp.org/wiki/Ltsp-manager/Installation
And, post this I ran the steps as in : https://help.ubuntu.com/community/UbuntuLTSP/RaspberryPi
I want to install only the thin client.
When I run the step : ltsp-build-client --arch armhf --config /etc/ltsp/ltsp-build-client-raspi2.conf
I get an error message :
Selecting previously unselected package linux-image-raspi2. Preparing to unpack .../linux-image-raspi2_220.127.116.116.17_armhf.deb ... Unpacking linux-image-raspi2 (18.104.22.1686.17) ... Processing triggers for man-db (2.7.5-1) ... Setting up linux-image-4.10.0-1016-raspi2 (4.10.0-1016.19) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/posti
pastebin: try !paste
paste: the LTSP pastebin is at http://ltsp.pastebin.com. Please paste all text longer than a line or two to the pastebin, as it helps to reduce traffic in the channel. Don't forget to paste the URL of the text here.
The error message that I get is : https://pastebin.com/iNLAM5zi
There's a bug in ltsp-update-sshkeys, you need to apply this patch on the server to fix it: https://git.launchpad.net/ltsp/commit/?id=b1030c40f40930928f2f114f96419edbeddb5e17
|08:22||ricotz has joined IRC (ricotz!~ricotz@p5B2A809F.dip0.t-ipconnect.de)|
|08:22||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
Thanks for the moment Alkis. I am now rerunning the ltsp-build-client after lstsp-update-sshkeys patch. Will let you know how it all goes.
|08:43||Statler|Home has joined IRC (Statler|Home!~Georg@p5B30E0E2.dip0.t-ipconnect.de)|
|09:34||quinox1 has left IRC (email@example.com, *.net *.split)|
|09:34||dragon788 has left IRC (dragon788!sid158229@gateway/web/irccloud.com/x-rowydmluvjxwdtfh, *.net *.split)|
|09:34||spectra has left IRC (spectra!~spectra@debian/developer/spectra, *.net *.split)|
|09:34||tarzeau has left IRC (firstname.lastname@example.org, *.net *.split)|
|09:36||quinox1 has joined IRC (email@example.com)|
|09:36||dragon788 has joined IRC (dragon788!sid158229@gateway/web/irccloud.com/x-rowydmluvjxwdtfh)|
|09:36||spectra has joined IRC (spectra!~spectra@debian/developer/spectra)|
|09:36||tarzeau has joined IRC (firstname.lastname@example.org)|
|10:12||highvoltage has left IRC (highvoltage!~highvolta@ubuntu/member/highvoltage, Ping timeout: 276 seconds)|
|10:13||highvoltage has joined IRC (highvoltage!~highvolta@ubuntu/member/highvoltage)|
|10:39||GodFather has left IRC (GodFatheremail@example.com, Read error: Connection reset by peer)|
|10:39||GodFather has joined IRC (GodFatherfirstname.lastname@example.org)|
|12:28||jp_ has left IRC (jp_!7aab73eb@gateway/web/freenode/ip.22.214.171.124)|
|13:01||Natureshadow has left IRC (Natureshadow!~Naturesha@commu.teckids.org, Ping timeout: 276 seconds)|
|13:16||lee_ is now known as lee|
|13:24||Natureshadow has joined IRC (Natureshadow!~Naturesha@commu.teckids.org)|
|14:02||jp_ has joined IRC (jp_!7aab73eb@gateway/web/freenode/ip.126.96.36.199)|
I have done all the steps related to the thin client for RaspberryPi-3 (which are basically the RaspberryPi-2 steps itself) in the RaspberryPi help page (https://help.ubuntu.com/community/UbuntuLTSP/RaspberryPi)
I have made the SD image also as listed in it.
Now when I boot up my Raspberry, I get an error : "Gave up waiting for root device. Common problems:" ....
And then : "ALERT! /dev/nbd0 does not exist. Dropping to a shell!"
And a little before that, I had also got an error message :
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Setting up nbd-client ... [ <some number> nbd: registered device at major 43
Negotiation: ..Error: Read failed: End of file
Could anyone please help me understand what is going wrong ?
|15:08||lucascastro has joined IRC (email@example.com)|
nbd-client: To try mounting the NBD image from the client initramfs: nbd-client 192.168.67.1 -N /opt/ltsp/i386 /dev/nbd0
jp_: try that ^ while putting the correct server ip, from the raspberry initramfs shell
ok, let me try that ...
i guess, instead of /opt/ltsp/i386 I will need to use /opt/ltsp/armhf
Btw, I do not find nbd-server.allow file either in "/etc/ltsp/nbd-server.allow"
Could that also be an issue ?
Or, is it that I need to create this file myself ?
No, that file should not exist
After running nbd-client <server-ip> -N /opt/ltsp/armhf /dev/nbd0 I get an error :
Negotiation: ..Error: Read failed: End of file
And does it work with your i386 or amd64 configuration?
i.e. -N /opt/ltsp/amd64
I have only 2 directories under /opt/ltsp : "armhf", and, "images"
And what's inside images?
|15:55||markit has joined IRC (firstname.lastname@example.org)|
"amd64.img", and, "armhf.img"
|15:55||nehemiah has joined IRC (email@example.com)|
ok, try nbd-client -N /opt/ltsp/amd64
Still the same error
And yet an amd64 client can boot?
We're coming to a point where everything seems to be working really well. I wanted to thank everybody for there advise and input! We are getting into the stage of making an automated installation the can easily replicate the setup.
@alkisg : How do I test that ?
There's just a couple more questions. Can I, for thin clients, downgrade the amount of colors displayed to make up a little for the network latency? Like you can with x2go?
jp_: have you booted any clients with this ltsp setup?
I am directly trying through my RaspberryPi-3
OK, this means that there may be more issues to be addressed server-side than just nbd-server
Unfortunately I don't have much time currently, I'll be available again a few hours, or tomorrow...
lts.conf: (#1) http://manpages.ubuntu.com/lts.conf, or (#2) lts.conf manpage is available in the ltsp-docs package
nehemiah: check X_COLOR_DEPTH there, you can set it to 16
Is there any way to check if my Raspberry client is able to connect to my Kubunto server and access /opt/ltsp/*
jp_: ehi, I use kubuntu too :) (not with raspberry though... I'm surprised it can work with it... any special fine tuning to reduce the I/O?)
markit: I have still not been able to get it working even for once.
I have a desktop (Intel Core2 ; 4GB ram, running 64bit Kubuntu 16.04.3LTS) with a single NIC. I have my LTSP Server installed on this. And, I am trying to get a RaspberryPi-3 (want to use it as a dumb terminal, like in the earlier days, but with a running GUI).
So, just want to be able to work on my Desktop through the RaspberryPi-3
Is there any way I can test (maybe from within initramfs) that there is no access issue from RPi to the LTSP Server ? Something similar to a ping / ssh ?
Through a normal Rasbian SD on my RPi, I am able to ssh to my Kubuntu without any issue, though.
|16:40||lucascastro has left IRC (firstname.lastname@example.org, Remote host closed the connection)|
|16:44||lucascastro has joined IRC (email@example.com)|
jp_: I have 3-4 minutes until some meeting, if you're here currently we can try this:
vnc-edide: To share your screen with me, open Epoptes → Help menu → Remote support → Host: srv1-dide.ioa.sch.gr, and click the Connect button
|17:16||adrianor1 has joined IRC (firstname.lastname@example.org)|
|17:19||adrianorg has left IRC (email@example.com, Ping timeout: 252 seconds)|
alkisg: Oops, missed to catch you it seems ...
|18:45||jp_ has left IRC (jp_!7aab73eb@gateway/web/freenode/ip.188.8.131.52)|
|19:11||adrianor1 is now known as adrianorg|
|19:13||markit has left IRC (firstname.lastname@example.org, )|
|20:56||nehemiah has left IRC (email@example.com)|
|21:24||Statler|Home has left IRC (Statler|Home!~Georg@p5B30E0E2.dip0.t-ipconnect.de, Remote host closed the connection)|
|21:26||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|