[opensuse] Re: Unlocking a locked file
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/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
# 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/vboxvfs.ko ./lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxadd.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. 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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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/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
On 03/19/2010 04:14 AM, Stan Goodman pecked at the keyboard and wrote: <snip>
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 that is not the installed/running kernel. uname -a will tell you the running kernel. And to rebuild the modules for Vbox run (as root) /etc/init.d/vboxdrv setup -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 14:06:06 on Friday Friday 19 March 2010, "Ken Schneider - openSUSE" <suse-list3@bout-tyme.net> wrote:
On 03/19/2010 04:14 AM, Stan Goodman pecked at the keyboard and wrote: <snip>
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 that is not the installed/running kernel. uname -a will tell you the running kernel. And to rebuild the modules for Vbox run (as root) /etc/init.d/vboxdrv setup
:~> uname -a Linux poblano 2.6.27.45-0.1-default #1 SMP 2010-02-22 16:49:47 +0100 x86_64 x86_64 x86_64 GNU/Linux :~> I think that's as it should be. The files that are missing are those that should be in those in the directory that is the target of the symlink, namely: ./lib/modules/2.6.27.42-0.1-default/updates/vboxadd.ko ./lib/modules/2.6.27.42-0.1-default/updates/vboxvfs.ko but even that directory is missing. Please correct me so we are on the same page, and (so I don't screw up more because of the confusion) tell me if you are suggesting that I rebuild the modules.
-- Ken Schneider SuSe since Version 5.2, June 1998
-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 19 March 2010 07:00:38 am Stan Goodman wrote: <snip>
On Friday 19 March 2010 06:06:06 am Ken Schneider - openSUSE wrote:
In fact, the directory /lib/modules/2.6.27.42-0.1-default/ doesn't exist.
Then that is not the installed/running kernel. uname -a will tell you the running kernel. And to rebuild the modules for Vbox run (as root) /etc/init.d/vboxdrv setup
:~> uname -a
Linux poblano 2.6.27.45-0.1-default #1 SMP 2010-02-22 16:49:47 +0100 x86_64 x86_64 x86_64 GNU/Linux
As Ken suggested, you appear to have kernel sources for 2.6.27.42-0.1-default, but you are running kernel 2.6.27.45-0.1-default - not the same version. You should update your kernel sources to match your running kernel before continuing. -- Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Don Raboud -
Joachim Schrod -
Ken Schneider - openSUSE -
Stan Goodman