General TC > Tiny Core on Virtual Machines
Can't start Xorg after installing open-vm-tools-desktop: "Illegal instruction"
denbkh:
Thank you for the VM link in pm message.
I have run it and got the same bug with "Illegal instruction at address 0xb4fc54a3" :(
Can you try to run it with the latest VMware 12.5.9?
In the VMware changelog they mention adding some "Spectre" (CVE-2017-5715) mitigation ... maybe this could be the source of the problem ...
p.s. I have tried to reply on your pm message twice, but it look like broken - can't see my reply in the "sent items" (http://forum.tinycorelinux.net/index.php?action=pm;f=sent)
Rich:
Hi denbkh
--- Quote from: denbkh on April 18, 2018, 04:51:58 PM --- ... p.s. I have tried to reply on your pm message twice, but it look like broken - can't see my reply in the "sent items" (http://forum.tinycorelinux.net/index.php?action=pm;f=sent)
--- End quote ---
When sending a PM there is a checkbox for saving a copy of your message.
andyj:
I upgraded my VM Player to 12.5.9 and the VM still works. Decreasing the CPU's to one didn't create the problem either. Neither did decreasing the amount of video memory. We both have Intel CPU's. There are two problems here. One is that when a VM is running on your system X doesn't detect DRM. The second is that software DRM fallback is crashing. When I disable 3D on my system DRM is not detected (DX: no) and software rendering works OK:
--- Code: ---[ 8.150] (II) vmware(0): Initialized VMWARE_CTRL extension version 0.2
[ 8.172] (WW) vmware(0): Failed to initialize Gallium3D Xa. No render acceleration available.
[ 8.172] (WW) vmware(0): Skipped initialization of direct rendering due to lack of render acceleration.
[ 8.172] (--) vmware(0): Render acceleration is disabled.
[ 8.172] (==) vmware(0): Rendercheck mode is disabled.
[ 8.172] (--) vmware(0): Direct rendering (3D) is disabled.
[ 8.172] (==) vmware(0): Backing store enabled
[ 8.172] (==) vmware(0): Silken mouse enabled
[ 8.174] (II) vmware(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 8.174] (==) vmware(0): DPMS enabled
[ 8.174] (II) vmware(0): No 3D acceleration. Not setting up textured video.
[ 8.174] (--) RandR disabled
[ 8.174] (II) AIGLX: Screen 0 is not DRI2 capable
[ 8.174] (EE) AIGLX: reverting to software rendering
[ 8.358] (II) IGLX: enabled GLX_MESA_copy_sub_buffer
[ 8.358] (II) IGLX: Loaded and initialized swrast
[ 8.358] (II) GLX: Initialized DRISWRAST GL provider for screen 0
--- End code ---
I cannot reproduce the problem. Maybe you have something else installed on your system which is interfering with VMware? Another hypervisor like VirtualBox also installed with services running in the background? Maybe check BIOS settings? Maybe update system BIOS?
denbkh:
--- Quote ---... Maybe you have something else installed on your system which is interfering with VMware? Another hypervisor like VirtualBox also installed with services running in the background? Maybe check BIOS settings? Maybe update system BIOS?
--- End quote ---
Hmm, I don't have VirtualBox on my PC.
The interesting thing is that open-vm-tools-desktop in my LUbuntu 17.10 x86 VM works without any problems with full 3d acceleration. Checked that with glxinfo and glmark2. So that I think the problem is not with my BIOS.
Any ideas how can I help you reproduce the bug?
andyj:
Those are good points. Did you upgrade VM Player from a previous version, or was it a clean install? When X crashes at startup does it fall back to a console prompt? If so, maybe you could use strace with startx to get some more info? How do you know that Ubuntu is using 3D and not software? Have you checked the Xorg.0.log?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version