Tiny Core Base > Release Candidate Testing
Core v7.0beta1
andyj:
The mouse doesn't work in a VMware VM when booting from the ISO image. This appears to be an issue with the Xvesa extension. I can verify that it is available to the system by 'cat'ing /dev/input/event2 in the console, but specifiying the path using startx -- -mouse doesn't have any effect. I have tested this with VMware versions 9 with Nvidia host graphics and version 12 with ATI host graphics. I can't tell if the keyboard works while Xvesa is running, but it does work in the console. There is no X log to give any hints. I ran tc-install.sh from the command line and after rebooting ran tce-load -iw Xorg-7.7-3d to get to a working system so this confirms that the mouse does work with the Xorg extension in the same VM.
Juanito:
--- Quote from: Lee on January 08, 2016, 09:18:13 PM ---qemu-common.tcz.dep references libcap-ng.tcz which is not present
--- End quote ---
libcap-ng copied to tc-7.x repo - thanks.
--- Quote ---SDL.tcs.dep references libmad.tcz which is not present.
--- End quote ---
Maybe I'm missing something, but libmad looks to be present in the tc-7.x repo to me?
--- Quote ---Looks like xautolock-2.2 from the 4.x repo works in 7.x. I suppose it would work in 5.x and 6.x, too.
--- End quote ---
xautolock-2.2 copied to tc-5.x, 6.x and 7.x repos - thanks
Juanito:
--- Quote from: andyj on January 09, 2016, 10:23:35 PM ---The mouse doesn't work in a VMware VM when booting from the ISO image. This appears to be an issue with the Xvesa extension.
--- End quote ---
Is vmware meant to work with Xvesa?
Does vmware work with Xvesa in tc-6.x?
andyj:
Since I don't recall having this same problem with TC 6.4.1, I'll say yes it worked. But now I have another problem. Open-vm-tools won't compile with gcc 5. Something about the new C++ ABI. I've tried setting the "old behavior" macros without success. In the process of building extensions for this new version, did this problem come up and was it successfully resolved?
Juanito:
gcc was compiled to support the old and new libstdc++ abi - I suppose the default is to compile for the new abi, but I haven't compiled any extensions yet where this came up...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version