vmware-config.pl errors out with various errors depending on kernel version >=2.6.6 (and possibly 2.6.5-mm & earlier)... I don't have my system handy at the moment, so I'm not sure whether vmware-config.pl references /usr/src/linux or headers. Downloading & extracting vmware-any-any-update**.tar.gz and running runme.pl will allow vmware-config.pl to run error-free 99% of the time. According to vmware mailing lists, vmware-any-any-update should always be the first step before vmware-config.pl on a new installation... new vmware-any-any-update**.tar.gz's come out quite regularly, where ** is a number (69 being the latest at time of this post). I'm not sure of the official mirror for this update, I've been using http://ftp.cvut.cz/vmware/. Reproducible: Always Steps to Reproduce: 1. kernel (possibly headers) >= 2.6.6 2. emerge vmware-workstation (4.5.x) 3. run vmware-config.pl Actual Results: vmware-config.pl errors out, different errors depending on kernel/headers version Expected Results: completed successfully again, not sure if vmware-config references kernel or headers... Portage 2.0.50-r8 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.4.20040605-r0, 2.6.6) ================================================================= System uname: 2.6.6 i686 AMD Athlon(tm) Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -O2 -pipe -mcpu=athlon-xp -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-xp -O2 -pipe -mcpu=athlon-xp -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://128.213.5.34/gentoo/ ftp://cudlug.cudenver.edu/pub/mirrors/distributions/gentoo/ http://mirror.datapipe.net/gentoo" MAKEOPTS="-j6" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage /usr/local/bmg-main" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow X aim alsa avi berkdb cddb cdr chroot clamav cups dillo dvd encode fbcon flac foomaticdb gif gphoto2 gtk gtk2 icq imagemagick imap imlib imlib2 ipv6 java jpeg libwww mad mmx motif mozdomi mozilla moznocompose moznoirc moznomail mozp3p mozsvg mozxmlterm mpeg msn ncurses nls nopsyco nptl oav offensive oggvorbis opengl operanom2 oscar pdflib pic png ppds quicktime readline samba sdl sse ssl tiff transcode truetype usb x86 xface xinerama xml xml2 xmms xv xvid yahoo zlib"
Fixed in CVS... thanks for the bug report
After applying the any-any-69 update to my love-sources-2.6.7-rc-love2 box, i still cant use vmware. After applying the patch, i can at least run vmware-config.pl without any errors. But after configuring it to use bridging, nat, host-only network and denying access to local partitions, i still cant start /etc/init.d/vmware successfully, it complains about vmnet0 and vmnet8 being unusable. Taking vmware out of the runlevel, reboot, configuring it, rebooting, starting vmware wasnt successful too.
After getting knowledge of the new -r1 ebuild for vmware-wokstation, I cant emerge it at all, since I'm getting this error: emperor /usr/portage/distfiles # ACCEPT_KEYWORDS="~x86" emerge vmware-workstation Calculating dependencies ...done! >>> emerge (1 of 1) app-emulation/vmware-workstation-4.5.1.7568-r1 to / >>> Downloading http://gentoo.oregonstate.edu/distfiles/vmware-any-any-update69.tar.gz --04:33:11-- http://gentoo.oregonstate.edu/distfiles/vmware-any-any-update69.tar.gz => `/usr/portage/distfiles/vmware-any-any-update69.tar.gz' Resolving gentoo.oregonstate.edu... 128.193.0.3 Connecting to gentoo.oregonstate.edu[128.193.0.3]:80... connected. HTTP request sent, awaiting response... 404 Not Found 04:33:11 ERROR 404: Not Found. >>> Downloading http://distro.ibiblio.org/pub/Linux/distributions/gentoo/distfiles/vmware-any-any-update69.tar.gz --04:33:11-- http://distro.ibiblio.org/pub/Linux/distributions/gentoo/distfiles/vmware-any-any-update69.tar.gz => `/usr/portage/distfiles/vmware-any-any-update69.tar.gz' Resolving distro.ibiblio.org... 152.2.210.109 Connecting to distro.ibiblio.org[152.2.210.109]:80... connected. HTTP request sent, awaiting response... 404 Not Found 04:33:11 ERROR 404: Not Found. >>> Downloading http://ftp.cvut.cz/vmware/vmware-any-any-update69.tar.gz --04:33:11-- http://ftp.cvut.cz/vmware/vmware-any-any-update69.tar.gz => `/usr/portage/distfiles/vmware-any-any-update69.tar.gz' Resolving ftp.cvut.cz... 147.32.160.19 Connecting to ftp.cvut.cz[147.32.160.19]:80... connected. HTTP request sent, awaiting response... 200 OK Length: 245,183 [application/x-tar] 100%[=========================================================================================================>] 245,183 7.30K/s ETA 00:00 04:33:44 (7.40 KB/s) - `/usr/portage/distfiles/vmware-any-any-update69.tar.gz' saved [245183/245183] >>> Resuming download... >>> Downloading http://knihovny.cvut.cz/ftp/pub/vmware/vmware-any-any-update69.tar.gz --04:33:44-- http://knihovny.cvut.cz/ftp/pub/vmware/vmware-any-any-update69.tar.gz => `/usr/portage/distfiles/vmware-any-any-update69.tar.gz' Resolving knihovny.cvut.cz... 147.32.240.81 Connecting to knihovny.cvut.cz[147.32.240.81]:80... connected. HTTP request sent, awaiting response... 416 Unknown The file is already fully retrieved; nothing to do. !!! Couldn't download vmware-any-any-update69.tar.gz. Aborting.
Same problem as comment 3. vmware-any-any-update69.tar.gz on the servers is only 245183 bytes and the digest seems to expect a 1198080 byte file, which just happens to be the un-gzipped file size (and the hash in the digest also matches the .tar). A temporary solution would be to delete /usr/portage/app-emulation/vmware-workstation/files/digest-vmware-workstation-4.5.1.7568-r1 and run 'ebuild /usr/portage/app-emulation/vmware-workstation/vmware-workstation-4.5.1.7568-r1 digest' After this, 'emerge vmware-workstation' should work as expected. I'm sure this will be fixed in cvs Real Soon Now...
Actually, it should already have been fixed... but if not, it is only because I forgot to commit it and will do so in the morning... As for love-sources, you're entirely on your own when you run a set of kernel sources made by a complete amateur who understands nothing about kernel internals and puts together patches that seem to work only because the patch applies cleanly without rejects. I would suggest switching to a kernel that is supported in Gentoo, as you will find that they work fine with VMware.
*** Bug 53482 has been marked as a duplicate of this bug. ***
Sorry about that... I fixed it this morning... when I originally did the digest I hadn't realized that my browser had already un-gzipped the tarball... anyway, it is fixed now.
*** Bug 53656 has been marked as a duplicate of this bug. ***
*** Bug 54073 has been marked as a duplicate of this bug. ***
