Wyse VX0: Linux 





As you would expect from this standard hardware set up I have had no problems running various flavours of linux. For example Tiny Core 3.3 worked perfectly back then as does Tiny Core 10.1 now.

As noted under the Firmware tab above, it looks like it is a bit hit-and-miss if it will boot from your USB pen drive. I originally wrote that you needed to select the boot option USB-ZIP and ensure your pen drive (a) has a partition table at the start, and (b) that the boot partition is <=1GB. My July 2019 experience showed that (b) was no longer correct.

Lawrence Yau emailed:

"I also have a couple of the Wyse V90Ls and have successfully installed Debian Linux onto the stock 512mb DOM with room to spare, though I compiled my own stripped down kernel to save space.

I installed just a base Debian install which takes up around 250mb IIRC. Got rid of a few packages and compiled my own kernel as well as installing FFmpeg and its dependencies and it's still under 200mb. Can easily install X and other applications in the remaining space."

[Update: February 2017]

Revisiting the VX0 to add the pci listings I booted and ran Tiny Core 7.2 from a 1GB USB pen drive. This had been created using LiLi without bothering to do anything with the geometry of the drive. It looks like, similar to the Igel D200, USB-ZIP format just means the pen drive has to have a partition table at the start.

WARNING: One quirk I discovered was to do with booting. My USB boot menu is set so that the default boot option is the second in the list - Tiny Core GUI with a 'waitusb=5' for slow devices. This is what was highlighted when the boot screen appeared. As noted on the Firmware tab, on the V30L and the V30LE my USB keyboard was 'dead' at this point and so I had to wait for things to time out before the system auto booted. Despite what was highlighted on the screen the system booted the first entry with no 'waitusb' in the command line. This resulted in my ending up at a command prompt rather than with a desktop.

After going round in circles for about five minutes (yes I do have 'waitusb=5' as a kernel parameter) I typed:

tc@box~$ dmesg | grep command
Kernel lcommand line: loglevel=3 kmap=qwerty/uk tce initrd=/boot/core.gz BOOT_IMAGE=/boot/vmlinuz

..and saw it was missing from the command line passed to the kernel. I then edited syslinux.cfg to add waitusb=1 to the first menu entry, rebooted and then ended up the graphical desktop. Looking at the log file again showed the kernel command line now included waitusb=1 showing that it was the first entry being booted when things timed out - not the second (highlighted) entry that I expected.

<Duh> I subsequently noted that in my syslinux.cfg the fourth line is: ONTIMEOUT tc.

i.e. There is a separate entry for what it boots on timeout - it doesn't just take the default.</Duh>


Any comments? email me. Added May 2011    Last update July 2019