Yes, you do, but I've found that doesn't always work, so I always resort to a complete reintallation of Vmware. Still got the oops though. There's nothing about it on the Vmware website.
I think you have to run one of the vmware configure scripts so it redoes the required modules. Not sure of the name or location of the required scripts, look around. I had this problem some time ago. Good Luck Terry
Derek Fountain wrote:
I upgraded my kernel to (a handrolled) 2.2.14 last night from 2.2.13. Seemed OK until I ran vmware, which caused an oops. Vmware is 1.1.2 and is fine under 2.2.13.
Anyone else seen this? I'm back on 2.2.13 for the time being...
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/