** Also affects: dkms
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/600517
Title:
dkms is not processing vboxdrv, must do manually
To manage
** Summary changed:
- dkms is not processing vboxdrv must do manually
+ dkms is not processing vboxdrv, must do manually
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/600517
Title:
dkms is not
Works for me now since the new kernel 3.5.0-28-generic
#48~precise1-Ubuntu
Can please somebody confirm this or are i'm the only one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/600517
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dkms (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/600517
Title:
dkms
Bug still active in Precise!
Every time i install a new kernel, this problem comes up and i have to
do an manual setup by:
sudo /etc/init.d/vboxdrv setup
* Stopping VirtualBox kernel modules
hum I just had to do that with the update to the next kernnel in 12.10
sudo /etc/init.d/vboxdrv setup
I can almost type it in my sleep now that I have done it so many times now
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
As can be read here:
http://ubuntuforums.org/showthread.php?t=1530691page=4
I am not the only one with this issue.
Out of frustration I've removed all the headers and images for any older
kernels on my system.
Including the 2.6.32-22 generic that dkms was holding on to.
I also tried the
a...@tabbycat:~$ sudo /usr/lib/dkms/dkms_autoinstaller start `uname -r`
[sudo] password for kat:
* Running DKMS auto installation service for kernel 2.6.32-24-generic
* bcmwl (5.60.48.36+bdcom)... [ OK ]
* fglrx (8.723.1)...
Here is more of what I've tried:
1608 sudo chmod a-rwx 3.2.4
1609 ls -l
1610 cd ../vboxnetadp/
1611 sudo chmod a-rwx 3.2.4
1612 cd ../vboxnetflt/
1613 sudo chmod a-rwx 3.2.4
1614 dkms status
=== result ===
bcmwl, 5.60.48.36+bdcom, 2.6.32-24-generic, x86_64: installed
fglrx,
So I worked around the bug the old fashioned way.
Purged dkms completely from my system, then removed the folder /var/lib/dkms
then reinstalled my videocard and wireless network adapter drivers
Then reconfigured virutalbox
1640 sudo aptitude purge dkms
1641 cd ~
1642 sudo rm -r
After a reboot, it still fails.
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or
there is a permission problem with /dev/vboxdrv. Please reinstall the
kernel module by executing
'/etc/init.d/vboxdrv setup'
(/dev/vboxdrv) does not exist.
--
dkms is not processing vboxdrv
This still works as a workaround. :(
k...@tabbycat:~$ sudo modprobe vboxdrv
k...@tabbycat:~$ sudo modprobe vboxnetflt
k...@tabbycat:~$ sudo modprobe vboxnetadp
--
dkms is not processing vboxdrv must do manually
https://bugs.launchpad.net/bugs/600517
You received this bug notification because
I noticed I had this package installed
virtualbox-ose-dkms
I removed the package but am still getting the error:
It looks like DKMS is building for the wrong kernel.
k...@tabbycat:~$ dkms status
bcmwl, 5.60.48.36+bdcom, 2.6.32-24-generic, x86_64: installed
fglrx, 8.723.1, 2.6.32-22-generic,
Daniel:
I am running Lucid x86_64.
And have reproduced this bug this on 3 different machines.
But good to hear that the i386 version is working as expected.
--
dkms is not processing vboxdrv must do manually
https://bugs.launchpad.net/bugs/600517
You received this bug notification because you
With some experimentation
I was able to start Virutal Box today without recompiling by doing the
following:
k...@tabbycat:~$ sudo modprobe vboxdrv
k...@tabbycat:~$ sudo modprobe vboxnetadp
k...@tabbycat:~$ sudo modprobe vboxnetflt
Can anyone enlighten me as to why these three are not being
does `dkms status` report them as installed?
--
dkms is not processing vboxdrv must do manually
https://bugs.launchpad.net/bugs/600517
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Here is the result of dkms status... As you can see from my earlier
attachment of the dkms.conf file... the file is correct, and the fields
it's complaining about are filled.
k...@tabbycat:~$ dkms status
bcmwl, 5.60.48.36+bdcom, 2.6.32-21-generic, x86_64: installed
bcmwl, 5.60.48.36+bdcom,
Jeff:
This should be addressed by the module packages themselves. They have the
option to build for all kernels or just the kernel in question, so I would
recommend directing bugs there if you think this is a big deal.
On Wed, Jul 14, 2010 at 11:04, Jeff Epstein
600...@bugs.launchpad.netwrote:
The problem is that the module has to be rebuilt at every reboot of the system.
The system does not remember the same module of the same kernel.
Real World situation:
Every day that I go to work I need to run a virtual machine on my laptop.
Every day when I start up the laptop I have to rebuild
Plus that whole 10 seconds boot time is lost, when you spend another 15
minutes configuring your system just so you can start to work with it.
--
dkms is not processing vboxdrv must do manually
https://bugs.launchpad.net/bugs/600517
You received this bug notification because you are a member of
hey Kat, that shouldn't happen, and hasn't been the issue discussed thus
far. Once the module is built with dkms, it shouldn't need to be built
again.
--
dkms is not processing vboxdrv must do manually
https://bugs.launchpad.net/bugs/600517
You received this bug notification because you are a
Having to rerun the build multiple times Is certainly a different bug. I
would say that is important to fix.
Do we have an understanding for what is happening there? When you run
modinfo on the next boot is the module not there? Is something deleting it?
If we were to add an init script or
Mario,
Per your suggestion to address this issue to the individual modules. So
far as I can tell, all dkms-using modules in the repositories only
contain install scripts to build for the current kernel, and therefore
they all suffer this problem. Would you suggest creating a separate bug
report
Yes, the problem is that dkms has to be re-run every day. The module is
not remembered across a reboot.
If you re-read the original bug report I stated:
every day I have to run /etc/init.d/vboxdrv setup because the ubuntu
DKMS package is not doing it's job.
What really happens:
The dkms package
Jeff:
Your bug is similar but is confusing the issue slightly.
From what I experience the kernel module has to be rebuilt at every
reboot no matter which kernel I do it in or when I install the package.
Try to reboot into the same kernel twice and see if you can start nvdia and
vboxdrv
I did a modprobe -l vboxdrv after a fresh reboot
and started virtualbox and made a screenshot
This is what I am experiencing.
as you can see the module is there... but it's not loaded.
so this is what I meant by Ubuntu not remembering the module.
** Attachment added: screenshot showing vboxdrv
Here is the virutal box install log. There are many DKMS errors in it.
May be a help in solving the bug.
** Attachment added: Virtual Box install log
http://launchpadlibrarian.net/52000664/vbox-install.log
--
dkms is not processing vboxdrv must do manually
I investigated the logging and discovered the dkms.conf file.
It contains everything that the logging is complaining that it doesn't have:
--log error --
dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified.
dkms.conf: Error! No 'PACKAGE_NAME' directive specified.
dkms.conf: Error! No
fwiw, I installed vbox from the oracle website, and dkms seems to be
working as expected, in that the modules build and are available after a
reboot.
I'm still experiencing the issue where the vbox modules are only built
for the running kernel. Shall I mark my bug un-duped?
--
dkms is not
oops, forgot to say that I'm running i386 lucid
--
dkms is not processing vboxdrv must do manually
https://bugs.launchpad.net/bugs/600517
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
As I recall, under Jaunty, there was a dkms service in /etc/init.d that
would automatically recompile kernel modules if you were booting a new
kernel. That service is no longer there. Is that a design decision or an
oversight as a result of the switch to upstart or a bug? Is it possible
to
Jeff:
That's a design decision. Kernel modules will be built by kernel
postinstall scripts and module package post install scripts.
On Wed, Jul 14, 2010 at 09:48, Jeff Epstein
600...@bugs.launchpad.netwrote:
As I recall, under Jaunty, there was a dkms service in /etc/init.d that
would
Mario,
Thanks for replying. So, one consequence of this design decision is that
if you select a different kernel from the GRUB boot menu, dkms modules
will fail to build for that kernel and subsequently won't load. This
creates a negative user experience, if the user (like me) expects to be
able
Jeff:
The modules should have been previously built for that kernel. Why is
that not the case for you?
This decision was made in the preference of boot speed. Having a shell
script in every boot to check kernel modules slowed it down. You can
create your own upstart script to do this (or
Mario,
The kernel modules in question (virtualbox and nvidia) weren't already
built for me because I installed them after I upgraded to the new
kernel. Other users in a similar situation will have the same problem.
Yes, running the following command worked. Thanks.
sudo
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/51223568/Dependencies.txt
--
dkms is not processing vboxdrv must do manually
https://bugs.launchpad.net/bugs/600517
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
36 matches
Mail list logo
