Wyse cx0 установка linux

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Install Linux on a Wyse Thin Client

KlenschLucas/wyse-linux-install

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Sign In Required

Please sign in to use Codespaces.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

I managed to get my hands on a wyse thin client pc for realively cheap, but it came with an unusable Window 7 Embedded OS.
This wil be a tutorial to get Debian up and running on the 4GB System.

Step 1 — Debian Installation

Download net install for Debian, and create a bootable drive with it.
To boot from the drive, enter the bios by hitting the Del key and entering in Fireport .
Move your USB drive to the top of the boot list.
Install Debain normally from there.

Since the system comes with only 4GB Storage and 2GB of that is used by swap, we going to have diable swap.

• Login your account and go root, su and enter the root password.
• Run /sbin/swapoff -a to disable all swap devices.
• Remove the swap entry in fsab, vi /ect/fstab
• Check that swap was disabled, free -h

Step 3 — Add Swap To System

• Start fdisk, /sbin/fdisk /dev/sda
• List all partition with p
• Delete all the partitions on sda with d and input number
• Create a new partition with n and use default settings
• Run /sbin/resize2fs /dev/sda1 to register the new partition.

Step 4 (optional) — Add Sudo

apt install sudo to install sudo
/sbin/usermod -aG sudo to add user to sudo users

Step 5 (optional) — Install xcfe4

apt install xcfe4 for XCFE Desktop
apt install xcfe4-goodies for additional XCFE Plugins

About

Install Linux on a Wyse Thin Client

Источник

XTL :: blog

I decided to try Tiny Core Linux on one of the Wyse thin clients I have and picked the middle ground with a Cx0.

Install Tiny Core

I downloaded CorePlus-7.1 ISO and put it on the same spare USB key I used to install Debian on the Igel. Booting the Wyse while tapping del, I used BIOS password Fireport and hiked the USB key up in the boot list. TCL booted right up and I spent some time looking around and getting used to thing.

I used dd to dump the drive over sshfs so I’d have a backup image and something to poke around in case I want to. I have a few whole spare units anyway. I would try to make this one to boot TCL directly.

I ran the frugal install as instructed and rebooted. The image fits quite well in the 128 MB nominal flash drive. There are less boot options than on the CorePlus image. I left in the firmware packages and some other stuff in as options, but eventually decided to remove anything I didn’t think I’d immediately need. The installed size went from some 120 MB down to 40 or so, IIRC. Well enough free space to install some applications or little data.

Using Tiny Core

Everything runs very swiftly and seems to work.

I changed .Xdefaults for aterm to turn off transparency and set a bg colour instead. I also changed the keymap and some other boot options. I was hunting a font problem for a while before noticing that it’s just Busybox that rejects certain characters, while even vi in the same terminal displays everything fine. I think I can live with that. Setting a timezone or other locale bits didn’t seem to be worth the effort yet.

One annoying thing is, naturally, web browsing. Dillo works very very quickly, but has fairly limited abilities and behaves very oddly with some CSS sites. I tried Fifth as well, and it seems very slow despite the promises. Installing Chromium or Firefox would take up almost all the remaining space, and I don’t expect them to work much smoother. Opera is surprisingly small and functional, but I still consider it to be evil. Uzbl and surf. aren’t available, but could probably easily be pulled in from somewhere or built to a small executable.

Hardware tests and thoughts

Basically the box works, booting and shutting down (not by button though).

Graphics at 1920x1200x16, sound output, GbE networking, internal and USB storage. Cpufreq also seems to be happily switching between the two choices of 400 MHz and 1000 MHz with ondemand governor. There are messages about a crypto accelerator in dmesg , but I have no idea if that’s doing anything.

# Check temperature tc@box:~$ cat /sys/class/thermal/thermal_zone0/temp 59000 # After some time streaming audio and browsing docs: tc@box:~$ cat /sys/class/thermal/thermal_zone0/temp 70000 # Pretty hot tc@box:~$ df -h /mnt/sda1/ Filesystem Size Used Available Use% Mounted on /dev/sda1 109.9M 68.2M 39.4M 63% /mnt/sda1 tc@box:~$ cpufreq-info -s -m 1000 MHz:40.25%, 400 MHz:59.75% (46440) 

I might test a wifi dongle at some point. There’s also an available USB port and a few more could be freed by switching to (or using adapters in) PS/2 ports.

And there’s the serial port as well. Actually, the kernel detects four. No picocom package, though.

I’m not exactly running out of RAM, but the two buster HP terminals would have 1 GB modules that I could swap in. The 2 GB PATA flash boards should also just drop in (after imaging).

I decided to drop in the bigger RAM chip. BIOS showed it fine. Changing the slice allocated to the display would probably allow me to free even more RAM. Linux is happy with the 750 MB or so that remains, though.

Compilers

tc@box:~$ cat hello.c #include int main(void) < printf("Hello tiny core wyse!\n"); return 0; >tc@box:~$ tcc hello.c tc@box:~$ ./a.out Hello tiny core wyse! tc@box:~$ ldd a.out linux-gate.so.1 (0xb7752000) libc.so.6 => /lib/libc.so.6 (0xb7635000) /lib/ld-linux.so.2 (0x80016000) tc@box:~$ tcc -run hello.c Hello tiny core wyse! 

So, picocom! It compiles out of the box after setting CC to tcc. It won’t open my serial ports, though 🙁

tc@box:~/code/picocom-2.1$ ./picocom /dev/ttyS0 . FATAL: failed to add device /dev/ttyS0: Filedes is not a tty tc@box:~$ cat /dev/ttyS0 cat: read error: Input/output error 

Edit: Actually, I’ve gotten these confused somehow. This model does not have any external serial or parallel ports. Oops. It’s also not the middle one, but probably the newest Wyse I have.

Conclusions

It’s quite usable as it is for any kind of computing except multimedia rich web browsing. A fast network interface gives it some interesting terminal potential.

I was planning, at one point, to make some kind of box that would have an attached Launchpad or something, logic analyzer, any other instruments I had at hand, and some software just to do data logging and graphing.

I finally grabbed a backup image that I should be able to use for cloning into other boxes if I want. At least one clone I’d probably like to do onto a bigger drive. The image should also Just Work on other hardware types as there’s hardly any specific configuration done here.

Parts of this post were typed on the box in question over SSH.

Links

Источник

Wyse Cx0: Linux

First time around I had no problems booting and running Tiny Core 5.4 from a 1GB or a 8GB USB pen drive. However note that the BIOS does treat these devices differently. My usual 1GB pen drive appears in the BIOS under USB KEY:. The 8GB Lexar pen drive I tried appears as USB HDD:.

FYI: As many older thin clients will not boot from pen drives that are larger than ~1GB I decided to check what a more modern one would do when presented with an 8GB pen drive.

On my latest visit I have been running Tiny Core 7.2

Wireless

As the latest C90LEWs I had picked up were fitted with WLAN cards I thought I’d see how easy it was to set then up to run wirelessly . In the event it is fairly straight forward but actually took me a while due to lack of information. Maybe I typed the wrong words into Google when trying to find out the right approach?

I don’t know how many variants of WLAN card that Wyse ship the C90LEW with, but the words below reflect that the WLAN adapter that I had is based on the Ralink RA2770 chip. Yours might be different.

I started with Tiny Core 7.2 and the usual few apps — kmap, pci-utils and usb-utils which I set up with a wired connection.

We know from the lsusb command that the WLAN card uses the Ralink RT2770 chip set. In order to be able to use this we have to use the App Browser to download and install the file firmware-ralinkwifi.tcz. I also picked on wifi.tcz to bring in the necessary WiFi software. An alternative is wicd.tcz which brings in a lot more baggage and also managed to disable my wired connection at one stage. The simplicity of wifi.tcz suited me.

At this point I disconnected the ethernet lead and clicked on the wireless icon to run wifi.sh. It scanned for wireless networks, found the usual ones I see here, and prompted me to select one. Having selected my network and entered the password it went ahead and connected me.

That just left the job of making things happen automatically when the system boots. When the wifi app started it created a file wifi.db in the tc home directory recording my choice of network and password to connect. We also need to add:

/usr/local/bin/wifi.sh -a > /tmp/wifi.log 2>&1

to the bootlocal.sh file.

Finally run filetool.sh -b to ensure that the files are backed up so that the changes persist.

Any comments? email me. Added November 2014 Last update February 2017

Источник

Установка Linux на Wyse Cx0: требуется минимальная система [дубликат]

Я хочу использовать их для целей RDP. Первоначальный план состоял в том, чтобы установить на них Tinycore и использовать Rdesktop для rdp на сервер, но последняя версия rdesktop (1.7) на Tinycore не поддерживает Windows Server 2008 R2 (были некоторые проблемы с моим указательным устройством, не отображавшимся на экране).

Теперь я ищу дистрибутив Linux, который использует менее 128 МБ флэш-памяти и менее 512 МБ ОЗУ. ОС должна поддерживать запуск rdesktop 1.8.3.

1 ответ

Просто измените внутреннюю флэш-память. Можно изменить его до 8 ГБ, чем получают ddr2 RAM от ноутбука и заменяют его, чтобы иметь поршень на 1 ГГц 2 ГБ и 8 ГБ внутренней памяти. Затем можно увеличиться до Win 8, 32-разрядного, если Вам нравится. Я двойная шахта начальной загрузки с Ubuntu 18.04 и Win 7 черный выпуск.

Другие вопросы по тегам:

Похожие вопросы:

• Ubuntu 16.04 и 17.10 не работают хорошо для меня. Что я должен установить вместо этого? [dубликат] — 27 March 2018 18:28
• Каковы системные требования для каждого варианта Ubuntu Desktop? — 16 December 2017 18:43
• Ubuntu на ПК с Windows ME — 24 July 2013 23:51
• Какой дистрибутив я должен использовать на IBM ThinkPad T41 для скорости? [закрыто] — 14 March 2012 22:26
• Есть ли дистрибутив, в котором compiz используется в качестве оконного менеджера по умолчанию? [закрыто] — 1 November 2013 07:52
• Предложение Ubuntu для двойной загрузки с Windows на легком ПК — 9 August 2012 14:36
• В чем разница между версией сервера и версией для ПК? — 22 November 2012 01:35

Источник