Hi,
I have connected to the edubuntu server and I am receiving the screens correctly. But, how do I change the screen resolution? For my monitor (HDMI) I had to setup the config.txt file with the US, sound, DMT, and screen size. When I tried that with this image the screen never initialized. Any ideas what I am missing?
Nettekpi

Nettekpi wrote:I have connected to the edubuntu server and I am receiving the screens correctly. But, how do I change the screen resolution? For my monitor (HDMI) I had to setup the config.txt file with the US, sound, DMT, and screen size. When I tried that with this image the screen never initialized. Any ideas what I am missing?

Would expect it to work the same as with other images, as I think the config.txt part is handled by the closed source bootloader before the Linux kernel is started.
Have you copied the config.txt file from your working (Debian?) SD to your BerryTerminal SD, as opposed to typing in the parameters, to make sure they are exactly the same and there are no typos?

That would be pretty cool, the thinstation guys have got ICA, VDI and RDP working I think and its a tiny distro.

Problem is that Thinstation relies on closed source components, and that comes with some practical and legal issues.

To my knowledge the Citrix's ICA and VDI components used are not open source, so can only be compiled for the rPi by Citrix.
Any bugs can only be fixed by them, and they would need to authorize distribution.
Be aware that while the components can be downloaded for free from their site, that doesn't automatically grant you the right to bundle them with your own stuff.

Other companies did open source their client libraries, so they would be a more logical choice for inclusion in a future version of BerryTerminal.
Think of VMware view open client, RedHat's SPICE project and NX.

bindo wrote:we have an LTSP setup at work. Thin client boot from the ltsp server. Today I tried berryterminal and it has "seen" the ltsp server correctly.
Unfortunately there is an issue with login that fails.

I think the raspberry isn't using the correct protocol to authenticate, but I'm not finding the setup files.

Berryterminal uses SSH, which is the protocol for LTSP 5

Can you connect to the server IP with a normal SSH client (e.g. putty) using the same username and password you entered?

Can you share the command for boot BerryTerminal on qemu? I want to try your work but not with LTSP, I'm interested on trying it with TCOS http://www.tcosproject.org It's a very similar alternative to LTSP but more simple and graphically.

shawe wrote:
Can you share the command for boot BerryTerminal on qemu? I want to try your work but not with LTSP, I'm interested on trying it with TCOS http://www.tcosproject.org It's a very similar alternative to LTSP but more simple and graphically.

You will need to recompile the source, because I compiled later versions with the arm-bcm2708hardfp- compiler optimized for the rpi and qemu doesn't seem to understand some instructions it produces ("illegal instruction" errors when you start X).

shawe wrote:
Can you share the command for boot BerryTerminal on qemu? I want to try your work but not with LTSP, I'm interested on trying it with TCOS http://www.tcosproject.org It's a very similar alternative to LTSP but more simple and graphically.

You will need to recompile the source, because I compiled later versions with the arm-bcm2708hardfp- compiler optimized for the rpi and qemu doesn't seem to understand some instructions it produces ("illegal instruction" errors when you start X).

This sounds very interesting. I was involved with setting up an LTSP installation at a community centre in Exeter and at the moment the client machines are old P3 machines which are getting a little long in the tooth. If we can replace these long term with a few Pis that would take the power consumption down by a large amount

This gives me something to try with my Pi, just need to get LTSP running again on Virtual Box

Just come across something interesting while testing the berry terminal package and trying out abiword etc (ltsp servers running in virtualbox for now).

I've got one ltsp server running on ubuntu 10.04 and running abiword v 2.8.2 which works great as is very responsive (almost native speed). DE is gnome 2.8.x

Got another ltsp server running on xubuntu 12.04 and running abiword 2.9.2 and it exhibits the exact same problem (very sluggish at typing and refreshing the page) people have encountered running abiword on raspbian/wheezy (had the same issue myself). DE is lxde.

now I wouldn't have thought this problem would occur on a RPI running a LTSP session when the server is doing all the donkey work (firefox etc work find on both servers).

does anyone have clue why this is (is there that much difference between the 2 abiword versions, or did they break something in 2.9.2)?

I already had edubuntu installed and LTSP configured but never even thought of trying to run the Pi from ltsp. I am amazed at the performance, which is mostly of course server side.
I can actually use libreoffice with ease. This makes using the Pi a pleasure.