At 02:55:20 on Friday Friday 19 March 2010, Joachim Schrod wrote:

Stan Goodman wrote:

...

At 13:36:05 on Wednesday Wednesday 17 March 2010, Stan Goodman

wrote:

...

At 21:19:58 on Tuesday Tuesday 16 March 2010, Joachim Schrod

...

...

WARNING: Can't read module

/lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxvf s.ko: No such file or directory WARNING: Can't read module

/lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxad d.ko: No such file or directory

# find -name "vbox*.ko" ./lib/modules/2.6.27.45-0.1-default/misc/vboxnetadp.ko ./lib/modules/2.6.27.45-0.1-default/misc/vboxnetflt.ko ./lib/modules/2.6.27.45-0.1-default/misc/vboxdrv.ko

./lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxv fs.ko ./lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxa dd.ko ./lib/modules/2.6.27.39-0.2-default/misc/vboxnetadp.ko ./lib/modules/2.6.27.39-0.2-default/misc/vboxnetflt.ko ./lib/modules/2.6.27.39-0.2-default/misc/vboxdrv.ko ./lib/modules/2.6.27.39-0.2-trace/misc/vboxnetadp.ko ./lib/modules/2.6.27.39-0.2-trace/misc/vboxnetflt.ko ./lib/modules/2.6.27.39-0.2-trace/misc/vboxdrv.ko ./lib/modules/2.6.27.39-0.2-debug/misc/vboxnetadp.ko ./lib/modules/2.6.27.39-0.2-debug/misc/vboxnetflt.ko ./lib/modules/2.6.27.39-0.2-debug/misc/vboxdrv.ko

./lib/modules/2.6.27.45-0.1-trace/weak-updates/updates/vboxvfs .ko ./lib/modules/2.6.27.45-0.1-trace/weak-updates/updates/vboxadd .ko ./lib/modules/2.6.27.42-0.1-trace/updates/vboxvfs.ko ./lib/modules/2.6.27.42-0.1-trace/updates/vboxadd.ko

In a nutshell, the problem has been reduced to redirecting the two symlinks to kernel modules of the proper version. At present, they are as follows: vboxvfs.ko -> /lib/modules/2.6.27.42-0.1-default/updates/vboxvfs.ko vboxadd.ko -> /lib/modules/2.6.27.42-0.1-default/updates/vboxadd.ko

whereas they should be instead ~vboxvfs.ko -> /lib/modules/2.6.27.45-0.1-default/updates/vboxvfs.ko ~vboxadd.ko -> /lib/modules/2.6.27.45-0.1-default/updates/vboxadd.ko

No. The symlink in weak-updates/ should point to existing files in the updates/ subdirectory of an older kernel.

One must not have the same kernel modules in weak-updates/ and in updates/ of one kernel release, that'll cause havoc. (A symlink to an existing file is the same as having that file there.)

...

and I should do (from the directory containing the links: ln -sf vboxvfs /lib/modules/2.6.27.45-0.1-default/updates/vboxvfs.ko ln -sf vboxadd /lib/modules/2.6.27.45-0.1-default/updates/vboxadd

No. Check that the files really exist in /lib/modules/2.6.27.42-0.1-trace/updates/, and that there are no symlinks.

They don't, as I discovered yesterday after I wrote. Here is the search: # find -name "vboxadd.ko" ./lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxadd.ko ./lib/modules/2.6.27.45-0.1-trace/weak-updates/updates/vboxadd.ko ./lib/modules/2.6.27.42-0.1-trace/updates/vboxadd.ko # find -name "vboxvfs.ko" ./lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxvfs.ko ./lib/modules/2.6.27.45-0.1-trace/weak-updates/updates/vboxvfs.ko ./lib/modules/2.6.27.42-0.1-trace/updates/vboxvfs.ko # In fact, the directory /lib/modules/2.6.27.42-0.1-default/ doesn't exist.

Then do

cd /lib/modules/`uname -r`/weak-updates ln -sf /lib/modules/2.6.27.42-0.1-trace/updates/vbox*.ko . depmod -a

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. If yes, somebody knowledgable about VirtualBox must help you to check what went wrong with your installation.

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