Start X?

[Onktebong]

Hi, I'm new here.
I'm trying to run the latest TCL on a 1/1 (1 GHz CPU/1 GB RAM) laptop.
It lets me select a window manager, then boots to command line.
How do I start a WM from there?
Executing startx and initx from command line doesn't work.
Thank you!

[neonix]

If you want simple answer, type tce, press s, and type jwm.

Code: [Select]

  1. jwm.tcz
  2. Xfbdev-jwm-desktop.tcz
  3. Xorg-jwm-desktop.tcz
  4. Xvesa-jwm-desktop.tcz
chose 4
press q
press i
and then startx

If you use 64-bit TC version for x86 then Xvesa-jwm-desktop.tcz will be not available.

If you want long answer, then tell us what window manager you choose in TinyCorePlus.iso?

[Onktebong]

Thank you, Neonix!

I did all this (after plugging the laptop into the Ethernet) and the reply was:
failed in waitforX
... and then the system prompt.

At startup from the large menu I chose:
Boot Core Plus with FLWM topside.

PS: I've also tried to install Slitaz and had the same problem of not being able to get the GUI to start. Other Linuces such as DamnSmallLinux, Debian or Antix are starting OK though.

[Onktebong]

I also get the message:
xc:corrupted data
after selecting the OS from the list.

Despite this, I managed to launch the GUI by selecting:
Boot Core with X/GUI (TinyCore) + Wifi + Firmware

BTW, what does "+ Firmware" mean in this context?
Thank you.

[Onktebong]

  I took a hint from the obscure
xc:corrupted data
message flashing across the boot screen and did another Live-USB stick installation, this time using BalenaEtcher (with just one installation on it) rather than Ventoy.
Again chosing the default
Boot Core Plus with FLWM topside.
from the menu.
And this time, the GUI all started nicely! Yay!
I suspect a dodgy USB stick, although I checked it for errors and none were found. Or something wrong with the Ventoy.
Thanks for your help! 

[Rich]

Hi Onktebong

... BTW, what does "+ Firmware" mean in this context?

Firmware is basically a small program that a driver loads into a device, wifi
in this instance. It is supplied by the manufacturer and unique to each device.
It can enable certain features on a device and in some cases is needed just
to make the device functional.

[Onktebong]

Thank you. So it's basically a collection of proprietary Wifi drivers?

[Rich]

Hi Onktebong
For all practical purposes, yes. The driver is the open source part
that connects the device to the kernel. The firmware is the closed
source part containing the vendors "secrets" they don't want to share.

[Onktebong]

Thank you! 

[Rich]

Hi Onktebong
You are welcome.

[Onktebong]

I found this out: The problem was that I was using Ventoy to create the bootable USB stick. With Ventoy it only booted to command line.
With Balena Etcher I could actually start the desktop environment.

[gadget42]

re: ventoy

see: https://forum.tinycorelinux.net/index.php/topic,27208.0.html

as well as other forum search results as desired/necessary/required/etc

[youxiaojie]

If you want simple answer, type tce, press s, and type jwm.

Code: [Select]

  1. jwm.tcz
  2. Xfbdev-jwm-desktop.tcz
  3. Xorg-jwm-desktop.tcz
  4. Xvesa-jwm-desktop.tcz
chose 4
press q
press i
and then startx

If you use 64-bit TC version for x86 then Xvesa-jwm-desktop.tcz will be not available.

If you want long answer, then tell us what window manager you choose in TinyCorePlus.iso?

what's the difference of xfbdev xvesa and xorg7.7? in my guess xfbdev is based frambuffer and xvesa based vesa2.0 and xorg 7.7 is the authentic x server. which one is the fastest and lightweight?

[Rich]

Hi youxiaojie
xfbdev  and  xvesa  are both lightweight.  xfbdev  might be a little faster.