At 15:08:31 on Friday Friday 19 March 2010, Joachim Schrod <jschrod@acm.org> wrote:
Stan Goodman wrote:
At 02:55:20 on Friday Friday 19 March 2010, Joachim Schrod
<jschrod@acm.org> wrote:
Stan Goodman wrote:
At 13:36:05 on Wednesday Wednesday 17 March 2010, Stan Goodman
<stan.goodman@hashkedim.com> 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/v >boxvfs .ko > > ./lib/modules/2.6.27.45-0.1-trace/weak-updates/updates/v >boxadd .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-default/updates/vboxadd.ko #
In fact, the directory /lib/modules/2.6.27.42-0.1-default/ doesn't exist.
Yes, that was established several posts ago. Please read my post again, with careful attention to the directory names that I used.
I directed you to a different directory, namely to the ...trace/ directory, not to the ...default/ directory. That's where I suspect that the real files are. If yes, that's where the symlinks should point to. *Then*, one can call "depmod -a" and try to load them.
That went right over my head before; sorry. I waited several days for correction, to be sure I understood, and then proceeded. Reviewing the history, I see that you did speak of the trace directory, and I didn't notice the change. I apologize. Yes, the files in the trace directory are real, not symlinks: /lib/modules/2.6.27.42-0.1-trace/updates> dir total 168 -rw-r--r-- 1 root root 77448 2010-01-26 21:50 vboxadd.ko -rw-r--r-- 1 root root 83424 2010-01-26 21:50 vboxvfs.ko 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. I have read the man page for depmod, and don't feel that I understand it wekk enough to compose a command with it.
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