LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-11-2011, 06:19 PM   #16
DragonWisard
Member
 
Registered: Sep 2004
Location: MD, USA (D.C. Suburbs)
Distribution: Slackware
Posts: 95

Rep: Reputation: 53

Same for me. After upgrading to 13.37rc1 started seeing the following message when I tired to launch WinXP in VBox.

Code:
Mar 11 09:40:25 blackflag kernel: [37790.799348] VirtualBox[5916]: segfault at fffffff4 ip b41bf45f sp fffffff4 error 4 in VBoxSharedClipboard.so[b41b8000+b000]
I'm sure which package change is the root cause of the problem, but it was definitely something in the 13.37rc1 update.

Edit: I was able to recompile and load vboxdrv and company just fine. It's just the segfault in VBoxSharedClipboard.so that is causing me problems, but disabling Shared Clipboard for the VM works for now (it will become annoying if the shared clipboard doesn't get fixed).

Last edited by DragonWisard; 03-11-2011 at 06:22 PM.
 
Old 03-11-2011, 09:41 PM   #17
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 959

Rep: Reputation: 376Reputation: 376Reputation: 376Reputation: 376
I am not having this problem with Shared Clipboard.

I am using Slackware64-current, updated to latest update. Of course AlienBOB's multilib is installed. VirtualBox 4.0.4r70112 w/extension pack installed.
 
Old 03-11-2011, 10:20 PM   #18
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,824

Original Poster
Blog Entries: 1

Rep: Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225
OK, I was trying to figure this out and according to the VB docs the following are required to install the VB module:
qt4.40, or higher,
sdl-1.2.7, or higher,
and
DKMS (dynamic kernel module support).
Installed on my system are, qt-4.7.0-7abde40, sdl-1.2.14, but I can't find anything called DKMS. Is that part of another package?
Thanks.

Last edited by cwizardone; 03-11-2011 at 10:40 PM.
 
Old 03-11-2011, 10:40 PM   #19
anti_user
Member
 
Registered: May 2008
Location: Russia, Ural
Distribution: Slackware Current
Posts: 69

Rep: Reputation: 4
Quote:
Originally Posted by DragonWisard View Post
Same for me. After upgrading to 13.37rc1 started seeing the following message when I tired to launch WinXP in VBox.

Code:
Mar 11 09:40:25 blackflag kernel: [37790.799348] VirtualBox[5916]: segfault at fffffff4 ip b41bf45f sp fffffff4 error 4 in VBoxSharedClipboard.so[b41b8000+b000]
I'm sure which package change is the root cause of the problem, but it was definitely something in the 13.37rc1 update.

Edit: I was able to recompile and load vboxdrv and company just fine. It's just the segfault in VBoxSharedClipboard.so that is causing me problems, but disabling Shared Clipboard for the VM works for now (it will become annoying if the shared clipboard doesn't get fixed).
+1, i have this error on slackware current. It could be fixing by removing Oracle VBOX additional from WinXP Safe Mode. It will be worked without Oracle Guest Additional.
 
Old 03-12-2011, 02:10 AM   #20
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,824

Original Poster
Blog Entries: 1

Rep: Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225
OK. While this has never been a problem in the past, apparently, with the new kernel, DKMS has to be installed.
I couldn't find DKMS on OSU in Slackware64 'current' or Slackware64 13.1, but googled around and found it on an Australian site.
I installed the package, re-installed VB, re-booted, and, voilą, VB now works. Well, everything, but the principal reason I run Xp in VB, my HP scanner. I'll have to re-install the software and see if that fixes the problem. However, the HP printer does work, so who knows.
Thanks to everyone for their replies and suggestions.

Last edited by cwizardone; 03-12-2011 at 10:22 AM.
 
Old 03-12-2011, 04:06 AM   #21
lonestar_italy
Member
 
Registered: Nov 2010
Location: Italy
Distribution: Slackware64-current
Posts: 103

Rep: Reputation: 27
Quote:
Originally Posted by DragonWisard View Post
Same for me. After upgrading to 13.37rc1 started seeing the following message when I tired to launch WinXP in VBox.

Code:
Mar 11 09:40:25 blackflag kernel: [37790.799348] VirtualBox[5916]: segfault at fffffff4 ip b41bf45f sp fffffff4 error 4 in VBoxSharedClipboard.so[b41b8000+b000]
I'm sure which package change is the root cause of the problem, but it was definitely something in the 13.37rc1 update.
Code:
lonestar@vaio64:/opt/VirtualBox$ ldd VBoxSharedClipboard.so 
        linux-vdso.so.1 =>  (0x00007fff1130b000)
        VBoxVMM.so => /opt/VirtualBox/VBoxVMM.so (0x00007f388f9a5000)
        VBoxRT.so => /opt/VirtualBox/VBoxRT.so (0x00007f388f52d000)
        libXt.so.6 => /usr/lib64/libXt.so.6 (0x00007f388f298000)
        libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f388ef59000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f388ed3a000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f388eb36000)
        libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f388e832000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f388e48b000)
        VBoxREM.so => /opt/VirtualBox/VBoxREM.so (0x00007f388e28b000)
        libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007f388e076000)
        libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f388de3c000)
        libz.so.1 => /usr/lib64/libz.so.1 (0x00007f388dc26000)
        librt.so.1 => /lib64/librt.so.1 (0x00007f388da1d000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f388d797000)
        libSM.so.6 => /usr/lib64/libSM.so.6 (0x00007f388d590000)
        libICE.so.6 => /usr/lib64/libICE.so.6 (0x00007f388d375000)
        libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f388d158000)
        libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f388cf55000)
        libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007f388cd50000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f388fd5a000)
        libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f388cb4c000)
It could have been the libXt upgrade, being this the only dependency library that's been upgrades in 13.37. Probably Vbox would just need to be recompiled, if we had the sources =D
 
Old 03-12-2011, 06:17 AM   #22
kite
Member
 
Registered: Aug 2003
Location: Shenzhen, China
Distribution: Slackware
Posts: 303

Rep: Reputation: 47
It should be libXt that caused this problem. After libXt upgrade, this problem has been solved here. It has nothing to do with the kernel, because I am still using 2.6.35.7-smp
 
Old 03-12-2011, 07:50 AM   #23
DragonWisard
Member
 
Registered: Sep 2004
Location: MD, USA (D.C. Suburbs)
Distribution: Slackware
Posts: 95

Rep: Reputation: 53
Quote:
Originally Posted by chrisretusn View Post
I am not having this problem with Shared Clipboard.

I am using Slackware64-current, updated to latest update. Of course AlienBOB's multilib is installed. VirtualBox 4.0.4r70112 w/extension pack installed.
It may only affect Slackware-current/13.37rc1 not Slackware64. I haven't upgraded my Slackware64 system yet to test it.
 
Old 03-12-2011, 08:11 AM   #24
DragonWisard
Member
 
Registered: Sep 2004
Location: MD, USA (D.C. Suburbs)
Distribution: Slackware
Posts: 95

Rep: Reputation: 53
Quote:
Originally Posted by kite View Post
It should be libXt that caused this problem. After libXt upgrade, this problem has been solved here. It has nothing to do with the kernel, because I am still using 2.6.35.7-smp
I can confirm this, fixed it for me too.
 
Old 03-13-2011, 04:56 AM   #25
lonestar_italy
Member
 
Registered: Nov 2010
Location: Italy
Distribution: Slackware64-current
Posts: 103

Rep: Reputation: 27
Quote:
Originally Posted by DragonWisard View Post
I can confirm this, fixed it for me too.
what exactly did fix it? libXt downgrade?
 
Old 03-13-2011, 08:58 AM   #26
hughszg
LQ Newbie
 
Registered: Apr 2007
Location: China
Distribution: fedora, debian, ubuntu
Posts: 9

Rep: Reputation: 0
libXt upgraded again, to an even higher version...

Fri Mar 11 06:34:03 UTC 2011
x/libXt-1.1.1-i486-1.txz: Upgraded

Quote:
Originally Posted by lonestar_italy View Post
what exactly did fix it? libXt downgrade?
 
Old 03-13-2011, 11:08 AM   #27
DragonWisard
Member
 
Registered: Sep 2004
Location: MD, USA (D.C. Suburbs)
Distribution: Slackware
Posts: 95

Rep: Reputation: 53
Yes, the libXt upgrade on Friday fixed the problem for me. Sorry if I wasn't clear about that.
 
Old 03-13-2011, 11:15 AM   #28
BroX
Member
 
Registered: Oct 2003
Location: Sweden
Distribution: Slackware64-current, SlackwareARM-current
Posts: 787

Rep: Reputation: 70
Wouldn't it be good to modify the thread title since DKMS (which I thought was a Debian thing) is not required to run virtualbox in Slackware?

Just my 2 cents.
 
Old 03-13-2011, 06:58 PM   #29
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,824

Original Poster
Blog Entries: 1

Rep: Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225
Quote:
Originally Posted by BroX View Post
Wouldn't it be good to modify the thread title since DKMS (which I thought was a Debian thing) is not required to run virtualbox in Slackware?

Just my 2 cents.
It is, apparently, not required to run VB in Slackware, but it is required to install the VB kernel module.
Here, per the VB docs, pages 29-30:

Quote:
2.3.2 The VirtualBox kernel module
VirtualBox uses a special kernel module to perform physical memory allocation and to gain
control of the processor for guest system execution. Without this kernel module, you will still
be able to work with virtual machines in the configuration interface, but you will not be able to
start any virtual machines.
The VirtualBox kernel module is automatically installed on your system when you install
VirtualBox. To maintain it with future kernel updates, for recent Linux distributions – for ex-
ample Fedora Core 5 and later, Ubuntu 7.10 (Gutsy) and later and Mandriva 2007.1 and later –,
generally we recommend installing Dynamic Kernel Module Support (DKMS)1 . This framework
helps to build kernel modules and to deal with kernel upgrades.
If DKMS is not already installed, execute one of the following:
• On an Ubuntu system:
sudo apt-get install dkms
• On a Fedora system:

1 See http://en.wikipedia.org/wiki/Dynamic...Module_Support
for an introduction.

(Page 30)
yum install dkms
• On a Mandriva system:
urpmi dkms
If DKMS is available and installed, the VirtualBox kernel module should always work automat-
ically, and it will be automatically rebuilt if your host kernel is updated.
Otherwise, there are only two situations in which you will need to worry about the kernel
module:
1. The original installation fails. This probably means that your Linux system is not prepared
for building external kernel modules.
Most Linux distributions can be set up simply by installing the right packages - normally,
these will be the GNU compiler (GCC), GNU Make (make) and packages containing header
files for your kernel - and making sure that all system updates are installed and that the
system is running the most up-to-date kernel included in the distribution. The version
numbers of the header file packages must be the same as that of the kernel you are using.
• With Debian and Ubuntu releases, you must install the right version of the
linux-headers and if it exists the linux-kbuild package. Current Ubuntu releases
should have the right packages installed by default.
• In even older Debian and Ubuntu releases, you must install the right version of the
kernel-headers package.
• On Fedora and Redhat systems, the package is kernel-devel.
• On SUSE and openSUSE Linux, you must install the right versions of the
kernel-source and kernel-syms packages.
• Alternatively, if you have built your own kernel, /usr/src/linux should point to your
kernel sources. If you have not removed the files created during the build process,
then your system will already be set up correctly.
2. The kernel of your Linux host got updated. In that case, the kernel module will need to be
reinstalled by executing (as root):
/etc/init.d/vboxdrv setup

Last edited by cwizardone; 03-13-2011 at 07:01 PM.
 
Old 03-13-2011, 09:26 PM   #30
octoberblu3
Member
 
Registered: Oct 2005
Distribution: Slackware64-current
Posts: 67

Rep: Reputation: 22
Quote:
Originally Posted by cwizardone View Post
It is, apparently, not required to run VB in Slackware, but it is required to install the VB kernel module.
It's just recommended, not required. All it does is recompile the kernel modules whenever you install a new kernel version automatically (fitting in with the philosophy of Ubuntu and Fedora of helping out the normal user and doing things behind your back). All you need to do is run as root '/etc/rc.d/rc.vboxdrv setup' when you have booted up the new kernel. It will compile and load the new modules just fine, and you can run VirtualBox as before.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
VirtualBox 3.1.6 kernel @ SlackBuild error - kernel include dir dc_eros Slackware 4 05-31-2010 11:24 PM
Mdv-2010 & Virtualbox FredGSanford Mandriva 4 09-25-2009 02:21 PM
Virtualbox kernel modules won't load after updating kernel in openSUSE 11.0 JamesHall SUSE / openSUSE 6 02-03-2009 04:36 PM
virtualbox & DHCP paul_mat Linux - Server 1 05-24-2008 07:23 PM
Virtualbox, Mandriva & Windows 98 dolphans1 Mandriva 15 04-21-2008 01:25 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:19 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration