On 04/23/2012 08:48 AM, Ed Greshko wrote: > On 04/23/2012 01:26 PM, Ed Greshko wrote: >> As it is only a minor irritant, I've put my low priority stack. > > Maybe it was low on my priority...but it bugged me so I worked on it and "resolved" > the issue at least when it comes to the Guest Addons. > > The "problem" was that even if you had dkms installed, when you ran > VBoxLinuxAdditions.run it didn't set things up for updates by dkms. So, here is what > I did..... > > First I had the 3.3.2-1.fc17 kernel installed..... > > 1. Install dkms and rename the binary > 2. Installed the Guest Additions by running VBoxLinuxAdditions.run > 3. Rebooted and checked that all works well. > 4. Looked in /var/lib/dkms/ and found there was no vboxguest directory. > 5. Run /etc/init.d/vboxadd setup > 7. /var/lib/dkms/vboxguest directory now created with a > kernel-3.3.2-1.fc17.i686-i686 symlink > 8. Run "yum update" and the 3.3.2-8 kernel was install. > 9. /var/lib/dkms/vboxguest directory now contains a kernel-3.3.2-8.fc17.i686-i686 > symlink > 10. Reboot and all the new modules were loaded as expected. Hi Ed, using the same steps you described, I can confirm this: I downgraded from kernel-3.2.2-8 to kernel-3.3.2-1, rebooted to 3.3.2-1, run "/etc/init.d/vboxdrv setup", removed kernel-3.3.2-8 and reinstalled kernel-3.3.2-8. After this procedure the vbox modules for kernel-3.3.2-8 were correctly installed. This is really a hint that the problem mostly lies in the kernel update and not in dkms. > > I feel that subsequent kernel updates work now work correctly. > I guess too. Thank you for your cooperation. Kind regards Joachim Backes <joachim.backes@xxxxxxxxxxxxxx> http://www.rhrk.uni-kl.de/~backes
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
