openthinclient.org

Hi Johan,

i sure the tg3 was recently updated by Martin. Try to use an experimentel 
version of OTC.

http://openthinclient.org/Packages#Activate_experimental_repository

Experimental means experimental. Be carefull!

Regards, Jörn

On 29.08.2012 09:36, Johan.Sturve@... wrote:
> Hi Everyone,
>
>
> The HP t5745 stops with a kernel panic when it tries to load NIC drivers.
> It uses the Broadcom BCM57780 chip. If i check the tg3 module i see that
> vendor & device ID(14e4, 1692) is missing for this chip.
> Is there any way to get this working other than waiting for OTC to move to
> newer kernel?
>
>
> Med vänlig hälsning / Best regards
>
> Johan Sturve
>
>
> This body part will be downloaded on demand.
>
>
>
> This body part will be downloaded on demand.
>

Hi,

in contrast to thinStation the openthinclient system is based on NFS-mounted filesystems, so the cause of this very slow booting could be a low bandwidth connection to the otc server or a congested network. Even with a perfect network connection it coud take a few minutes to boot a 400Mhz Geode based device to the login screen. The long wait for the desktop may be due to low ram. I've experienced similar behaviour with very old PCs - until I upgraded ram. Have a look at the output of 'top' on the otc clients console. Perhaps this will give you some insight what's going on.

Regards
Christoph

From: Markus Frenzel [mailto:Markus.Frenzel@...]
Sent: Thursday, August 16, 2012 1:13 PM
To: 'openthinclient-user@...'
Subject: [openthinclient-user] Boot delay: Building TCOS base config

Hello!

I’m new to openthinclient… I’ve played around with thinstation for about a couple of months and ended up frustrated with some weird problems. Then I’ve discovered openthinclient… and I’m deeply impressed about all the build-in things and the GUI. Good job!

But also I’ve got a few problems and now I’m going to ask you if this a minor problems which can be solved with the help of the community.

Technical Background: we’ve got 50+ winterms (Wyse 3150SE) which are old but they are still running so we try to get them up and running again with openthinclient. 128MB RAM and 256MB flash drive (build-in) aren’t tech specs I like to have… but this is my equipment.

First problem: The winterm boots up… shows the openthinclient boot splash… screen switches to black… then some messages are displayed. Last line says: Building TCOS base config… and this is the point where I’m able to grab a cup of coffee… This message is displayed nearly forever. :-)

Second problem: After a couple of minutes (> 5 min.) the Login Screen shows up… I authenticate via the user account I’ve created in the openthinclient Manager… and go to grab another cup of coffee… and another one… and another one… 20 minutes later the Desktop is displayed.

What we intend to do is: give our users the possibility to start the citrix pnagent to connect to our Xenapp 6.5 Serverfarm where the applications for our users are published. There is no need of any browser or desktop-session…

Looking forward for your replies. Any help would be appreciated.

Regards

Markus Frenzel



Private Universität Witten/Herdecke gGmbH
Alfred-Herrhausen-Straße 50
D - 58448 Witten

Homepage: http://www.uni-wh.de
Twitter: http://twitter.com/UniWH
Facebook: http://www.facebook.com/UniWH

Geschäftsführung: Dipl.-Ök. Michael Anders (Kanzler), Prof. Dr. med. Martin Butzlaff (Präsident)

Sitz der Gesellschaft: Witten
Handelsregister des Amtsgerichts Bochum Nr. HRB 8671

"man linux" :-)

A PXE needs to load the module inside the initrd - this is by design.

Unlike this, a localboot loads the module from:
/lib/modules/`uname -r`/kernel/drivers/net/ethernet/some-module

The module inside the initrd is just a copy from the other one, copied by 
mkinitramfs or mkinitrd (depends on your system).

Read the docs/man according to initramfs, depmod, modprobe, lsmod an so on.

Regards, Jörn

--
Jörn Frenzel

   Development and Support

mailto:j.frenzel@...

openthinclient gmbh, Heilbronner Straße 150, 70191 Stuttgart
Amtsgericht Stuttgart: HRB 245 177; USt-ID: DE216017092
Geschäftsführer: Alexander Stecher, Martin Kreiner
http://openthinclient.com

On 14.08.2012 14:42, Klammer Ludwig wrote:
> That’s the strange part about it:
>
> If i boot via PXE there’s no problem. Just if i use localboot and try to
> boot from local disc it keeps writing me that line…
>
> Maybe if i extract the initrd of pxe boot and load this into my localboot
> image?
>
> Best regards,
>
> Mit freundlichen Grüßen,
>
> Ludwig Klammer
>
> Systemadministrator
>
>
>
> This body part will be downloaded on demand.
>
>
>
> This body part will be downloaded on demand.
>

Hi Ludwig,

yes, it looks like you're missing the driver for the network card. The 
driver must reside in the initrd. Unpack the initrd and add your driver 
(you need to build it according to the otc-kernel).

See: http://wiki.openvz.org/Modifying_initrd_image

Once this is done, you'll be able to boot via PXE, but you'll may notice 
problems with the nic again once you're using localboot. To fix this, the 
driver needs to be added to the base too.

Please also consider to ask us for the implemetation.

Regards, Jörn

-- 
Jörn Frenzel

   Development and Support

mailto:j.frenzel@...

openthinclient gmbh, Heilbronner Straße 150, 70191 Stuttgart
Amtsgericht Stuttgart: HRB 245 177; USt-ID: DE216017092
Geschäftsführer: Alexander Stecher, Martin Kreiner
http://openthinclient.com

On 13.08.2012 08:35, Klammer Ludwig wrote:
> Good Morning,
>
> after i kept hanging in boot-proccess at the line
>
> „IP-config: eth0 hardware address [MAC ADDRESS] mtu 1500 DHCP RARP“
>
> I was searching for reasons or a way to pass this and read that this is
> caused by missing network drivers.
>
> Is that true? And is it possibe to manually include drivers?
>
> Thanky you for your replies!
>
> Best regards,
>
> Mit freundlichen Grüßen
>
> Ludwig Klammer
>

Hi 

What I don't understand. Why does it work using PXE boot, but give that
trouble on localboot? 

Jörn do you have different drivers in localboot and pxe boot version?



Mit freundlichem Gruß

Julian Ohm

------------------------------------------
Ohm & Meyer Immobilien e. K.
Inh. Gabor Sarkany
Schiffbrücke 66
24939 Flensburg

Tel.: 0461 / 840 31 0
Fax.: 0461 / 840 31 11

HRA 2190 FL

Haftungsbeschränkungen/Disclaimer

Diese Nachricht enthält vertrauliche Informationen und ist ausschließlich 
für den Adressaten bestimmt. Der Gebrauch durch Dritte ist verboten. Das 
Unternehmen ist nicht verantwortlich für die ordnungsgemäße, vollständige 
oder verzögerungsfreie Übertragung dieser Nachricht. Diese Hinweise gelten 
auch für zukünftige Nachrichten.
This message may contain confidential information and is intended solely 
for the use by the addressee. Use of this communication by others is 
prohibited. The Company is neither liable for the proper and complete 
transmission of the message nor for the delay in its receipt.


-----Ursprüngliche Nachricht-----
Von: Jörn Frenzel [mailto:j.frenzel@...] 
Gesendet: Montag, 13. August 2012 09:23
An: openthinclient-user@...
Betreff: Re: [openthinclient-user] How to implement/install additional
drivers?

Hi Ludwig,

yes, it looks like you're missing the driver for the network card. The
driver must reside in the initrd. Unpack the initrd and add your driver (you
need to build it according to the otc-kernel).

See: http://wiki.openvz.org/Modifying_initrd_image

Once this is done, you'll be able to boot via PXE, but you'll may notice
problems with the nic again once you're using localboot. To fix this, the
driver needs to be added to the base too.

Please also consider to ask us for the implemetation.

Regards, Jörn

--
Jörn Frenzel

   Development and Support

mailto:j.frenzel@...

openthinclient gmbh, Heilbronner Straße 150, 70191 Stuttgart Amtsgericht
Stuttgart: HRB 245 177; USt-ID: DE216017092
Geschäftsführer: Alexander Stecher, Martin Kreiner http://openthinclient.com

On 13.08.2012 08:35, Klammer Ludwig wrote:
> Good Morning,
>
> after i kept hanging in boot-proccess at the line
>
> „IP-config: eth0 hardware address [MAC ADDRESS] mtu 1500 DHCP RARP“
>
> I was searching for reasons or a way to pass this and read that this 
> is caused by missing network drivers.
>
> Is that true? And is it possibe to manually include drivers?
>
> Thanky you for your replies!
>
> Best regards,
>
> Mit freundlichen Grüßen
>
> Ludwig Klammer
>

----------------------------------------------------------------------------
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat
landscape has changed and how IT managers can respond. Discussions will
include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
The Open Source Thin Client Solution http://openthinclient.org
openthinclient-user@...
https://lists.sourceforge.net/lists/listinfo/openthinclient-user

Think not. Would make way more sense to create some sort of live CD than 
with autoboot of the terminal client and hardcoding of the terminal 
server. Changing this product to do this sounds like overkill.

BC


On 08/10/12 21:30, José Román Bilbao Castro wrote:
> Hi,
>
> This is my first post to the list. I am coming from thinstation and 
> would like to know if it is possible to make this work without the 
> server part. I mean, just generating a USB/CD with client IP, the 
> destination Terminal Server IP, local printer, etc... and make this 
> client work standalone.
>
> Just a yes or no will suffice ;-). I will do the rest ...
>
> Thanks in advance.
>
> Jose.
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
> _______________________________________________
> The Open Source Thin Client Solution http://openthinclient.org
> openthinclient-user@...
> https://lists.sourceforge.net/lists/listinfo/openthinclient-user

Hi Jose,

yes, you can do this. But you need to setup the server part once. Then you 
can use the localboot feature to flash to system with all its settings to 
USB, flash, DOM - whatever.

Localboot clients can run without connection to the server. The benefit you 
have is that you can configure all your settings in the otc-manager. If one 
client is already flashed to local disc, just reconnect it to the server 
and reboot to commit updates or setting changes incrementally.

See also: http://openthinclient.org/tiki-index.php?page=localboot

Regards, Jörn

-- 
Jörn Frenzel

   Development and Support

mailto:j.frenzel@...

openthinclient gmbh, Heilbronner Straße 150, 70191 Stuttgart
Amtsgericht Stuttgart: HRB 245 177; USt-ID: DE216017092
Geschäftsführer: Alexander Stecher, Martin Kreiner
http://openthinclient.com

On 10.08.2012 21:30, José Román Bilbao Castro wrote:
> Hi,
>
> This is my first post to the list. I am coming from thinstation and would
> like to know if it is possible to make this work without the server part. I
> mean, just generating a USB/CD with client IP, the destination Terminal
> Server IP, local printer, etc... and make this client work standalone.
>
> Just a yes or no will suffice ;-). I will do the rest ...
>
> Thanks in advance.
>
> Jose.
>
>
>
>
> This body part will be downloaded on demand.
>
>
>
> This body part will be downloaded on demand.
>

Ok, update,

i have to be honest, maybe you know that picture of a dog in a scientists coat, sitting infront of some chemicals and written into the picture with big fat letters "I have no idea what i'm doing"? That's exactly how i feel right now ;)

Some oft he problems could be solved or at least located. The problems with the slow screen refresh rate is caused by limitations of the RDP protocol, so we have to live with that. Despite that we want our clients to boot independent and even if our internet connection is down.

The problem while booting after localboot installation ([numbers] usb 2-1: USB disconnect, address 3...) seems tob e solved, i just deleted the localboot application and created+configured it new. Now it seems like I could get a few steps  further but my target is still not reached:

After running my "new" localboot installation my client starts but stops after a while, showing this as last line:
IP-Config:eth0 hardware address bl:ah:bl:ah:bl:ah mtu 1500 DHCP RARP

I tried to solve this by unplugging it from network and reconnect it to search for DHCP again, but it only results in two lines:

[numbers] r8169: eth0: link down
[other numbers] r8169: eth0: link down

Yes, twice "link down".

Any ideas?
Thanks!

Best regards,
Ludwig

Hi Ludwig,

I am not sure about what you will make working?
Localboot = Booting without PXE
Localboot = OTCOS is installed on local Drive

Normaly you want this only if your networkconnection is very slow (<10 
MB) to speedup booting
Localboot does not support the same networkdrivers like PXE one... i think

Does the "PXE Booting" working correct..
What networkadapter has your Lenovo?

....


  Am 08.08.2012 13:34, schrieb Klammer Ludwig:
>
> Hello,
>
> (i missclicked and unfortunatly sent my mail before finishing it, so 
> here it is again.)
>
> First i have to say that i usually speak german and my english lessons 
> in school are already a few years in the past, please be patient and 
> ask if something is incomprehensible. Google Translate will be my 
> friend ;) What i have to say too ist hat my Linux experience is not 
> very well so i ask you to describe me solutions step by step please. 
> And last but not least: I have no idea how this mailinglist is 
> working, i hope i will ever find my post again! ;)
>
> We are currently testing the OTCL System in our company and are having 
> some troubles with or on the clients:
>
> It all began with some IGEL Thinclients, low-level hardware but 
> delivered with a management suite and so on. Just invented ald set up 
> at some desktops users already began to complain about performance 
> problems. While viewing and scrolling through .pdf files the screen 
> refresh rate was that low that the shown file appeared block by block 
> and line by line. Unacceptable while working with documents containig 
> a few hundred pages. These problems didn't apear on normal PCs in the 
> same office, just these Thinclients. So we decided to take a look at 
> some other systems.
>
> Open Thinclient appears tob e a nice alternative and so we ordered a 
> blanc Thinclient, without any OS. A lenovo IdeaCentre Q180 with built 
> in 2,13GHz Dualcore, 2GB Memory, 320GB HDD (i know, unneccesary -.-), 
> and an ati Radeon 6450 graphics card. Quite a nice equipment for oure 
> requirements.
>
> After i managed the first hurdle (never used PXE network boot before) 
> the same problem again:
>
> "...shown file appeared block by block and line by line..."
>
> Well, maybe there's an option to install that OS on the client. I 
> searched and could find the localboot application. I set up the 
> application, pushed it to my client and began installing it to the 
> built in disk. All done, no obvious errors -> reboot.
>
> Boot form disk without any problems, but now i have a few problems:
>
> I'm hanging in a loop of text lines counting up:
>
> ...
>
> ...
>
> ...
>
> [numbers] usb 2-1: USB disconnect, address 3
>
> [numbers] usb 2-1: new low speed USB device using uhsi_hcd and address 5
>
> [numbers] usb 2-1: configuration #1 chosen from 1 choice
>
> [numbers] input: Microsoft   Microsoft Basic Optical Mouse v2.0 as 
> /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/input/input8
>
> [numbers] generic-usb 0003:045E:00CB.0004: input,hidraw0: USB HID 
> v1.11 Mouse [Microsoft   Microsoft Basic Optical Mouse v2.0] on 
> usb-0000:00:1d.0-1/input7
>
> [numbers] usb 2-1: USB disconnect, address 4
>
> [numbers] usb 2-1: new low speed USB device using uhsi_hcd and address 5
>
> [numbers] usb 2-1: configuration #1 chosen from 1 choice
>
> [numbers] input: Microsoft   Microsoft Basic Optical Mouse v2.0 as 
> /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/input/input9
>
> [numbers] generic-usb 0003:045E:00CB.0004: input,hidraw0: USB HID 
> v1.11 Mouse [Microsoft   Microsoft Basic Optical Mouse v2.0] on 
> usb-0000:00:1d.0-1/input8
>
> [numbers] usb 2-1: USB disconnect, address 5
>
> [numbers] usb 2-1: new low speed USB device using uhsi_hcd and address 5
>
> [numbers] usb 2-1: configuration #1 chosen from 1 choice
>
> [numbers] input: Microsoft   Microsoft Basic Optical Mouse v2.0 as 
> /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/input/input10
>
> [numbers] generic-usb 0003:045E:00CB.0004: input,hidraw0: USB HID 
> v1.11 Mouse [Microsoft   Microsoft Basic Optical Mouse v2.0] on 
> usb-0000:00:1d.0-1/input9
>
> ...
>
> ...
>
> ...
>
> If i unplug the mouse it only stops at this line:
>
> "IP-Config: eth0 hardware address 50:af:73:1d:f6:85 mtu 1500 DHCP RARP"
>
> I first thought it is because of a missing or wrong graphics-driver, 
> but when i add a graphic-card-device containing ati drivers it just 
> shows an error message:
>
> "Failed to start x-server", so I removed the device (in management suite).
>
> Please help me, I'm glad about every single hint..!
>
> Mit freundlichen Grüßen
>
>  Best regards,
>
> Ludwig Klammer
>
> Systemadministrator
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
> _______________________________________________
> The Open Source Thin Client Solution http://openthinclient.org
> openthinclient-user@...
> https://lists.sourceforge.net/lists/listinfo/openthinclient-user

Hello,

Thanks for your answer!

I have to be honest, maybe you know that picture of a dog in a scientists coat, sitting infront of some chemicals and written into the picture with big fat letters "I have no idea what i'm doing"? And in a few points that's exactly how i feel right now ;)

@Andreas Schneider
That's exactly what i want, a local OS installation. In case of a missing connection to the OTC Server we want the clients to be able to boot, and a faster boot would always be good ;) PXE boot process is working without any problems. How do i manage to find out wich networkadapter is built in?


Some of the problems could be solved or at least located. The problems with the slow screen refresh rate is caused by limitations of the RDP protocol, so we have to live with that. Despite that we want our clients to boot independent and even if our internet connection is down.

The problem while booting after localboot installation ([numbers] usb 2-1: USB disconnect, address 3...) seems to be solved, i just deleted the existing localboot application and created+configured it new. Now it seems like I could get a few steps  further but my target is still not reached:

After running my "new" localboot installation my client starts but stops after a while, showing this as last line:
IP-Config:eth0 hardware address bl:ah:bl:ah:bl:ah mtu 1500 DHCP RARP

I tried to solve this by unplugging it from network and reconnect it to search for DHCP again, but it only results in two lines:

[numbers]                         r8169: eth0: link down
[other numbers]             r8169: eth0: link down

Yes, twice "link down".

Any ideas?

Von: Andreas Schneider [mailto:as@...]
Gesendet: Mittwoch, 08. August 2012 17:12
An: openthinclient-user@...
Betreff: Re: [openthinclient-user] Localboot not working

Hi Ludwig,

I am not sure about what you will make working?
Localboot = Booting without PXE
Localboot = OTCOS is installed on local Drive

Normaly you want this only if your networkconnection is very slow (<10 MB) to speedup booting
Localboot does not support the same networkdrivers like PXE one... i think

Does the "PXE Booting" working correct..
What networkadapter has your Lenovo?

....


 Am 08.08.2012 13:34, schrieb Klammer Ludwig:
Hello,

(i missclicked and unfortunatly sent my mail before finishing it, so here it is again.)

First i have to say that i usually speak german and my english lessons in school are already a few years in the past, please be patient and ask if something is incomprehensible. Google Translate will be my friend ;) What i have to say too ist hat my Linux experience is not very well so i ask you to describe me solutions step by step please. And last but not least: I have no idea how this mailinglist is working, i hope i will ever find my post again! ;)


We are currently testing the OTCL System in our company and are having some troubles with or on the clients:
It all began with some IGEL Thinclients, low-level hardware but delivered with a management suite and so on. Just invented ald set up at some desktops users already began to complain about performance problems. While viewing and scrolling through .pdf files the screen refresh rate was that low that the shown file appeared block by block and line by line. Unacceptable while working with documents containig a few hundred pages. These problems didn't apear on normal PCs in the same office, just these Thinclients. So we decided to take a look at some other systems.

Open Thinclient appears tob e a nice alternative and so we ordered a blanc Thinclient, without any OS. A lenovo IdeaCentre Q180 with built in 2,13GHz Dualcore, 2GB Memory, 320GB HDD (i know, unneccesary -.-), and an ati Radeon 6450 graphics card. Quite a nice equipment for oure requirements.

After i managed the first hurdle (never used PXE network boot before) the same problem again:

"...shown file appeared block by block and line by line..."

Well, maybe there's an option to install that OS on the client. I searched and could find the localboot application. I set up the application, pushed it to my client and began installing it to the built in disk. All done, no obvious errors -> reboot.

Boot form disk without any problems, but now i have a few problems:
I'm hanging in a loop of text lines counting up:

...
...
...
[numbers] usb 2-1: USB disconnect, address 3
[numbers] usb 2-1: new low speed USB device using uhsi_hcd and address 5
[numbers] usb 2-1: configuration #1 chosen from 1 choice
[numbers] input: Microsoft   Microsoft Basic Optical Mouse v2.0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/input/input8
[numbers] generic-usb 0003:045E:00CB.0004: input,hidraw0: USB HID v1.11 Mouse [Microsoft   Microsoft Basic Optical Mouse v2.0] on usb-0000:00:1d.0-1/input7
[numbers] usb 2-1: USB disconnect, address 4
[numbers] usb 2-1: new low speed USB device using uhsi_hcd and address 5
[numbers] usb 2-1: configuration #1 chosen from 1 choice
[numbers] input: Microsoft   Microsoft Basic Optical Mouse v2.0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/input/input9
[numbers] generic-usb 0003:045E:00CB.0004: input,hidraw0: USB HID v1.11 Mouse [Microsoft   Microsoft Basic Optical Mouse v2.0] on usb-0000:00:1d.0-1/input8
[numbers] usb 2-1: USB disconnect, address 5
[numbers] usb 2-1: new low speed USB device using uhsi_hcd and address 5
[numbers] usb 2-1: configuration #1 chosen from 1 choice
[numbers] input: Microsoft   Microsoft Basic Optical Mouse v2.0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/input/input10
[numbers] generic-usb 0003:045E:00CB.0004: input,hidraw0: USB HID v1.11 Mouse [Microsoft   Microsoft Basic Optical Mouse v2.0] on usb-0000:00:1d.0-1/input9
...
...
...

If i unplug the mouse it only stops at this line:
"IP-Config: eth0 hardware address 50:af:73:1d:f6:85 mtu 1500 DHCP RARP"


I first thought it is because of a missing or wrong graphics-driver, but when i add a graphic-card-device containing ati drivers it just shows an error message:
"Failed to start x-server", so I removed the device (in management suite).


Please help me, I'm glad about every single hint..!


Mit freundlichen Grüßen
 Best regards,

Ludwig Klammer

Systemadministrator




------------------------------------------------------------------------------

Live Security Virtual Conference

Exclusive live event will cover all the ways today's security and

threat landscape has changed and how IT managers can respond. Discussions

will include endpoint security, mobile security and the latest in malware

threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/




_______________________________________________

The Open Source Thin Client Solution http://openthinclient.org

openthinclient-user@...>

https://lists.sourceforge.net/lists/listinfo/openthinclient-user