The answer is to recompile the source tarball with a patch which appeared
at:
https://communities.vmware.com/message/2686431?tstart=0#2686431
generously provided by https://communities.vmware.com/people/dariusd .
Tried it and it works swimmingly.
___
>Build error "Failed to build vmnet. Failed to execute the build
command."
>when trying to compile vmnet.Not one other shred of data in the logs
>telling me WHY it failed to build.
>I have rolled back to the last 514 kernel to use vmware but I
>don't want to recompile vmware because of the
Build error "Failed to build vmnet. Failed to execute the build command."
when trying to compile vmnet.Not one other shred of data in the logs
telling me WHY it failed to build.
I have rolled back to the last 514 kernel to use vmware but I
don't want to recompile vmware because of the liability
Well, the boxen with Intel i915 chips scramble the video after a period of
time somehow relating to the amount of graphic activity with log entries:
Dec 26 21:05:04 blade17 kernel: [521008.703090] [drm] stuck on render ring
Dec 26 21:05:04 blade17 kernel: [521008.708996] [drm] GPU HANG: ecode
On two blades both with Atom Processors but different Graphics chips (a
Matrox WPCM450 on one, Intel 82945Gon the other). One machine had distorted
video and required logging out of KDE and then back again. The other one
had no video and required ssh from another box to restart X remotely (which
I
On Tue, Oct 13, 2015 at 2:48 PM, pro alias <proa...@gmail.com> wrote:
> None of my Centos 5 boxen can show flash since the update this morning.
> Am I alone or do other people have this issue ??
> Centos 7 boxes work properly. I haven't looked at RHEL 6 boxes yet.
>
> Althou
None of my Centos 5 boxen can show flash since the update this morning.
Am I alone or do other people have this issue ??
Centos 7 boxes work properly. I haven't looked at RHEL 6 boxes yet.
Although I miss using flash on these boxes, it IS a great security
upgrade
I writ:
The latest kernel kernel-3.10.0.229.1.2.el7.x86_64 appears not to like
our Supermicro X9SBAA-F board. It fails on boot with the last message
before panic being apic_timer_interupt snipped rest
It turned out that only one X9SBAA box was affected.
Deleting and reinstalling the kernel
The latest kernel kernel-3.10.0.229.1.2.el7.x86_64 appears not to like
our Supermicro X9SBAA-F board. It fails on boot with the last message
before panic being apic_timer_interupt . Previous kernels load very well.
We erased and reinstalled the kernel, it verifies good as does everything
else
9 matches
Mail list logo
