At 12:20:15 on Monday Monday 22 March 2010, Joachim Schrod <jschrod@acm.org> wrote:
Stan Goodman wrote:
I intend to run: ln -sf vboxvfs.ko /lib/modules/2.6.27.42-0.1-trace/updates/vboxvfs.co ln -sf vboxadd.ko /lib/modules/2.6.27.42-0.1-trace/updates/vboxadd.ko from the directory where the incorrect symlinks are located.
Almost. 1) The arguments must be the other way round; first the real files, then the place where the symlinks shall be created. 2) There's a typo in the first command, there ".co" must be ".ko".
The exact commands are, as root:
cd /lib/modules/`uname -r`/weak-updates/updates ln -sf /lib/modules/2.6.27.42-0.1-trace/updates/vbox*.ko . depmod -a
# cd /lib/modules/2.6.27.45-0.1-default/weak-updates # ln -sf /lib/modules/2.6.27.42-0.1-trace/updates/vbox*.ko # depmod -a WARNING: Can't read module /lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxvfs.ko: No such file or directory WARNING: Can't read module /lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxadd.ko: No such file or directory poblano:/lib/modules/2.6.27.45-0.1-default/weak-updates # ln -sf /lib/modules/2.6.27.42-0.1-trace/updates/vbox*.ko # There was no complaint about the formation of the symlinks, but depmod failed.
Then, run
modprobe vboxvfs
and see if error messages are output to console or to /var/log/messages. If not, the kernel module problem has probably been resolved.
Joachim
-- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany
-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org