Wyse 3630LE: Development 





As one might expect things are very similar to the EvoT20 and my first check was that the kernel/initrd ran without problems on a T20. (My current workhorse of Tinycore 2.7 and kernel

However, in my preliminary tests, I found I ended up with a running system but no screen display! The GX1/CS5530A does include additional functionality that can be used when it is used directly with a CRT display or LED panel rather than just routing the video output to a VGA socket. It is currently my guess that it is this that is giving me grief and needs to be investigated.

On booting the kernel the screen does clear, but then remains blank forever. Probing further I found that to enable support for the panel display features you have to add a boot parameter. The HOWTO was a little bit confusing with a reference to the option video= not being supported V2.0 kernels. I ended up working through the kernel sources to discover that it is the correct way of doing I guess it means v2.0.x.x ???.

The syntax we need is: video=gx1fb:crt:0,panel=1024x768. I also tried video=gx1fb:crt:0,panel=1280x1024. In neither case did I end up with a working display - although there were some interesting screen effects along the way!

Verifying something is working

This is actually quite simple. Having booted Linux on the WT3630LE it is a matter of checking the "attached devices" screen on my Netgear router. After a while a new device appears which confirms that the ethernet interface on the WT3630LE is up and running.

The initrd I'm using has been configured to start the dropbear SSH server, but you do need to have a user account set up to allow you to logon remotely. (You can't do this using the default root and tc accounts). Although the display isn't working, you actually have an active console. If you (blindly!) type:

sudo adduser hen
you'll create a user account with a userid/password of hen/speckled and can then log in remotely as 'hen'.

Rather defeats the point of having an integral display if you run "headless", but it does let you confirm the kernel loads and runs!

After a while I found it easier to construct a new tinycore.gz file with the user already set up.


Any comments? email me.    Last update June 2010