Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: nowhinjing on April 06, 2018, 08:19:55 AM
-
I hope someone can help.
I have Tiny Core 9.0 running in VMware Workstation 14, and am trying to get shared folders / cut and paste working.
I have carefully followed the instructions contained in the headers for open-vm-tools.tcz and open-vm-tools-desktop.tcz.
Installing open-vm-tools-desktop.tcz results with the following at boot (see attachment tcore1.png) followed by (see attachment tcore2.png),
X does not start.
Removing open-vm-tools-desktop.tcz from the onboot.lst means that at least I get the standard GUI showing up.
I have modified ~/.profile as specified to open-vm-tools.tcz (see attachment tcore3.png), but folder hgfs appear in /mnt.
However running this script (see attachment tcore4.png) creates the directory and makes the link to the required shared folder successfully.
What am I doing wrong ?
Any help much appreciated.
(http://)
-
When you get a failed in waitforx error, enter the first line of ~/.xsession to see the error - it should be something like this:
/usr/local/bin/Xorg -nolisten tcp
-
Hi, Jaunito
Thanks for the quick reply !
What I get is
/usr/local/bin/Xorg -nolisten tcp &&
export XPID=$!
waitforX || ! echo failed in waitforX || exit
much as you expected. What do I need to do now ?
With many thanks for your help and patience,
NWJ
-
I meant that you should execute just the first line of ~/.xsession from the console prompt. i.e.
$ /usr/local/bin/Xorg -nolisten tcp
-
There are two modifications you need to make: one to ~/.profile for open-vm-tools.tcz, and the other to ~/.xsession for open-vm-tools-desktop.tcz. The shared folder directory is created when open-vm-tools loads so I'm not sure why you needed to do this separately. As of right now open-vm-tools-desktop doesn't work right with the latest X extensions, but X should still start. I won't be back home to work on getting the extensions up to date until next week, so it will be broken until then. If you could post your onboot.lst it would help.
-
Hi, Jaunito and andyJ,
thanks again for your messages and help.
@Jaunito - Doh!, sorry to be so thick !
Output from running /usr/local/bin/Xorg -nolisten tcp
failed in waitforX
tc@box:"$ /usr/local/bin/Xorg —nolisten top
X.Org X Server 1.19.5
Release Date: 2017—10—12
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.8.17—tinycore i436
Current Operating System: Linux box 4.14.10—tinycore #876 SMP Mon Jan 1 15:00:32 UTC 2013 i686
Kernel command line: BOOT_IMAGE=/tce/boot/vmlinux quiet waitusb=5:UUID="0beffc71—999e—45cB—a213—fd5
fb53cb215" tce=UUID="0beffc71—999e—45cB—a213—fd5fb53cb215" initrd=/tce/boot/core.gz
Build Date: 15 October 2017 11:14:52AM
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you haue the latest version.
Markers: (——) probed, (**) from config file, (==) default setting,
(++) from eommand line, (!!) notiee, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr 7 11:15:33 2018
(==) Using system config direetory "/usr/local/share/X11/xorg.conf.d"
: CommandLine Error: Option 'static—func—full—module—prefix' registered more than once!
LLVM ERROR: inconsistency in registered CommandLine options
tc@box:"$
@andyJ - thanks very much but there is no real urgency to this as I can access the share albeit through a bodge method, but it would be nice if it all worked ...
Content of onboot.lst
GNU nano 2.2.6 File: onboot.lst
Xvesa.tcz
aterm.tcz
flwm_topside.tcz
wbar.tcz
flwm_topside.tcz
tc—install—GUI.tcz
ezremaster.tcz
kmaps.tcz
nano.tcz
nautilus.tcz
glib2.tcz
open—vm—tools.tcz
open—vm—tools—desktop.tcz
-
That's the output from Xorg.0.log, not the console, but anyway :P
What happens if both llvm-lib and llvm4-lib are loaded (check that you have the most recent version of llvm-lib)?
-
Delete Xvesa.tcz, flwm_topside.tcz is not needed twice so delete one of them. Open-vm-tools-desktop.tcz will load open-vm-tools.tcz so this is redundant. You should load open-vm-tools-desktop first as it will load X.org which is needed for some of the subsequent entries. In VMware you will find that aterm will have rendering problems so you will want to use rxvt instead.
-
Hi, both,
Thanks for your replies.
@Juanito, loading these 2 extentions, llvm-lib.tcz and llvm4-lib.tcz has made no difference.
@andyJ, current onboot.lst is
llvm-lib.tcz
llvm4-lig.tcz
glib2.tcz
open—vm—tools—desktop.tcz
urxvt.tcz
flwm_topside.tcz
wbar.tcz
tc—install—GUI.tcz
ezremaster.tcz
kmaps.tcz
nano.tcz
nautilus.tcz
open-vm-tools-desktop is not loading Xorg, so I get no GUI.
also replacing aterm with urxvt looses the (very handy) terminal shortcut from wbar. This means that every time I need the Terminal I have to drop out to the prompt, and then restart X, which is a bit of a pain
replacing open-vm-tools-desktop.tcz with open-vm-tools.tcz and adding Xorg-7.7.tcz gets me back to a different but working system.
Thanks for your help - anything else you need to help diagnose the problem, just let me know.
Gratefully,
NWJ
-
xf86-video-vmware updated to work with the latest llvm-lib
-
BTW, is this RPi, x86 or x86_64?
-
its standard coreplus x86 running as a guest in vmware workstation 14 under windows 10.
-
I guess I'm the only one with this problem - shame, it would have been nice to have it working properly ...
maybe one day ?
-
I've submitted updates for both 32-bit and 64-bit. All the features work on both architectures, but I have only tested them on a Linux host. I don't know when they'll be available to the general public though. As for rxvt, my up-to-date extension is available for 64-bit only.
For onboot.lst, this is the minimum you need. You shouldn't have to specify any X related extensions. I'll say it again: Make sure you have all the dependencies downloaded BEFORE you reboot if you want X to work. Please try this first before you add any additional extensions:
open-vm-tools-desktop.tcz
flwm_topside.tcz
aterm.tcz
wbar.tcz
Once you get an aterm window open, try
$ vmware-toolbox-cmd --version
You should get
10.2.5.3619 (build-8068406)
Also, dmesg should have something like this for DRM to work:
[drm] DX: yes.
[drm] Atomic: yes
checking generic (e8000000 400000) vs hw (e8000000 400000)
fb: switching to svgadrmfb from VESA VGA
Console: switching to colour dummy device 80x25
fbcon: svgadrmfb (fb0) is primary device
Console: switching to colour frame buffer device 128x48
[drm] Initialized vmwgfx 2.14.0 20170612 for 0000:00:0f.0 on minor 0
-
updated extensions posted - thanks
-
@andyj
thanks for this - I hope to try it out over the week-end, as family reasons will make it difficult to do before.
I will keep you informed.
-
as promised, a situation update.
Still not working for me, I'm afraid.
I started with a fresh install in VM from the TinyCore iso.
I then loaded open-vm-tools-desktop, and nano, updated the onboot.lst, listed the version (correct) and ran dmesg which shows DX : No.
I then saved the changes and rebooted.
The system seems to boot OK, and a GUI flashes up on the screen before all goes black.
On the basis that a picture is worth 1000 words, I have made a video of the process which is available here :
http://www.pughx2.com/assets/px2/files/tcl-open-vm.mp4
I also tried with CorePurex64, but I get "out of memory" at the end of the installation on open-vm-tools-desktop. I can make and post a video if you wish.
Sorry to be such a pain...
NWJ
-
If your onboot.lst doesn't look like this then it's probably wrong:
open-vm-tools-desktop.tcz
flwm_topside.tcz
aterm.tcz
wbar.tcz
nano.tcz
-
@andyj
it looks exactly like that .....
-
From what I saw in the video you misspelled flwm_topside. If DX is not yes in dmesg you should enable 3D under the display settings for the VM.
-
@andyj
many thanks for your help and patience...
OK, now we are getting somewhere ...
Enabled 3D graphics - solves the DX : No problem.
I also found out that I needed to load the following manually :
tce-load -wi flwm_topside.tcz
tce-load -wi aterm.tcz
tce-load -wi wbar.tcz
Saved changes and rebooted - got the GUI, hooray !
added the following line in .xsession
[ $(which vmware-checkvm) ] && [ vmware-checkvm ] && vmware-user &
saved and rebooted.
Now I can cut and paste from the VM, but /mnt/hgfs is still showing empty even though I have an enabled share in the VM.
Any ideas ?
-
Fixed it !
I forgot to add
[ $(which vmware-checkvm) ] && [ vmware-checkvm ] && [ -d /mnt/hgfs ] && vmhgfs-fuse /mnt/hgfs
to .profile.
all now seems to work, at least for x86.
Many thanks to those who have taken the time to help me through this.