Hi, you mentioned virtualbox and vmware.
Does virtualbox work or does it crash, too? If virtualbox isn't working too it seems to be a problem with some other piece of software. I'm using virtualbox with the radeon driver for month without any issues. Regards, Felix On 21. January 2011 - 11:00, Mark Knecht wrote: > Date: Fri, 21 Jan 2011 11:00:18 -0800 > From: Mark Knecht <[email protected]> > To: Michel Dänzer <[email protected]> > Cc: [email protected] > Subject: Re: Any known problems with vmplayer and git driver? > > 2011/1/20 Michel Dänzer <[email protected]>: > > On Don, 2011-01-20 at 12:55 -0800, Mark Knecht wrote: > >> Hi, > >> I switched to the git version of xf86-video-ati this morning and I > >> immediately noticed some improvements with things like KDE menus and > >> such. However almost immediately I started having problems with > >> VMWare's vmplayer app. Appliances that I have run for months now won't > >> run at all. Lock files are left in the appliance directories and the > >> player won't play them. > >> > >> There have been a few other changes to this machine over the last > >> few days so I want to be careful about debugging what the root cause > >> is but they were certainly working this morning before I tried the new > >> driver. > >> > >> At this point I'm unable to run my most important appliances. > >> > >> I have not yet downgraded back to the normal release. I'll be doing > >> that soon. > >> > >> Thanks in advance for any info. > > > > I'm afraid it's you who needs to provide us with more information about > > the problem... I assume the lock files are just leftovers from the > > original problem. > > > > > > -- > > Earthling Michel Dänzer | http://www.vmware.com > > Libre software enthusiast | Debian, X and DRI developer > > > > OK, back again and as far as I can tell the problem is real. If I open > any VM in vmplayer after having upgraded to xf86-video-ati from git > then the VM hangs and there's no good way to get back out gracefully. > I do agree that the lock files are likely just a by-product of not > closing the machine normally. emerging vmware-workstation and doing a > reconfigure seems to clear that problem up. > > Here's what I did to test: > > 1) First, running the older xf86-video-6.13.2 I upgraded to mesa-7.10 > & mesa-progs-0.8 > > 2) Rebooted and tested glxgears. Rendering was disabled in Xorg.0.log > and FPS was about 200. glxgears -info showed I was using mesa-7.10. > > 3) Ran both a Virtualbox and VMware VM. Both worked fine. > > 4) Updated to xf86-video-ati-9999 which comes from git. > > 5) For safety ran module-rebuild -X rebuild which rebuilds all the > stuff I normally build after creating a new kernel. > > 6) Rebooted and tested glxgears. Rendering was now enabled which is > good. FPS was still at 200 which was no improvement. > > 7) I then ran a VMware VM which hung immediately.If you're familiar > with running VMs there's a first step where it looks like a BIOS boot > screen and then you see VMware and a bar which gets bigger to the > right over time. With the new driver installed this bar never appears > and the VM is hung. > > 8) Rebooted and emerged vmware-workstation again. Ran modules-rebuild > -X rebuild again. For safety rebooted. > > 9) Tried running the player again but it's still unable to show the > first portion of the boot screen. > > From my perspective the problem is real and it's the new driver from > git that kicks it off. > > There's certainly a possibility that it's another piece of software > that's involved. xorg-server is a little old. I could update to > 1.9.3.901. There is a newer version of vmware-workstation but I cannot > get it to even install yet. > > With VMware back to working as of right now this is what's on the system: > > c2stable ~ # uname -a > Linux c2stable 2.6.36-gentoo-r6 #28 SMP PREEMPT Thu Jan 20 12:03:50 > PST 2011 x86_64 Intel(R) Core(TM) i7 CPU X 980 @ 3.33GHz GenuineIntel > GNU/Linux > c2stable ~ # > > [ebuild R ] x11-libs/libdrm-2.4.23 USE="libkms -static-libs" > VIDEO_CARDS="radeon vmware -intel -nouveau" 0 kB [0] > > [ebuild R ] app-emulation/vmware-modules-1.0.0.28-r1 0 kB [1] > > [ebuild R ] x11-base/xorg-server-1.9.2 USE="nptl udev xorg -dmx > -doc -ipv6 -kdrive -minimal -static-libs -tslib" 0 kB [0] > > [ebuild R ] x11-drivers/xf86-video-ati-6.13.2 0 kB [0] > > [ebuild R ] x11-drivers/xf86-video-fbdev-0.4.2 0 kB [0] > > [ebuild R ] x11-drivers/xf86-video-vmware-11.0.3 0 kB [0] > > [ebuild R ] x11-drivers/xf86-video-vesa-2.3.0 USE="-debug" 0 kB [0] > > [ebuild R ] x11-base/xorg-drivers-1.9 INPUT_DEVICES="evdev > keyboard mouse -acecad -aiptek -elographics -fpit -joystick -penmount > -synaptics -tslib -virtualbox -vmmouse -void -wacom" > VIDEO_CARDS="fbdev radeon vesa vmware -apm -ark -ast -chips -cirrus > -dummy -epson -fglrx (-geode) -glint -i128 (-i740) (-impact) -intel > -mach64 -mga -neomagic (-newport) -nouveau -nv -nvidia -r128 > -rendition -s3 -s3virge -savage -siliconmotion -sis -sisusb (-sunbw2) > (-suncg14) (-suncg3) (-suncg6) (-sunffb) (-sunleo) (-suntcx) -tdfx > -tga -trident -tseng -v4l -via -virtualbox (-voodoo) (-xgi)" 0 kB [0] > > > If you need more info let me know. If I should be filing a bug report > somewhere please let me know that also. > > Thanks, > Mark > _______________________________________________ > xorg-driver-ati mailing list > [email protected] > http://lists.x.org/mailman/listinfo/xorg-driver-ati ---end quoted text--- _______________________________________________ xorg-driver-ati mailing list [email protected] http://lists.x.org/mailman/listinfo/xorg-driver-ati
