Rebuild the vboxdrv Module Problem [SOLVED]

I'm running Arch 64bit and recently updated to kernel 2.6.33.2-1
Running the usual vbox module update results in the following error.
[root@Arch2009p2 jeff]# vbox_build_module
Building vboxdrv for Linux 2.6.33-ARCH
make[1]: Entering directory `/opt/VirtualBox/src/vboxdrv'
for f in . linux r0drv r0drv/generic r0drv/linux VBox common/err common/string common/log generic math/gcc; \
do rm -f $f/*.o $f/.*.cmd $f/.*.flags; done
rm -rf .vboxdrv* .tmp_ver* vboxdrv.* Module.symvers Modules.symvers modules.order
make[1]: Leaving directory `/opt/VirtualBox/src/vboxdrv'
make[1]: Entering directory `/opt/VirtualBox/src/vboxnetflt'
for f in . linux r0drv r0drv/linux VBox common/err common/string common/log generic math/gcc; \
do rm -f $f/*.o $f/.*.cmd $f/.*.flags; done
rm -rf .vboxnetflt* .tmp_ver* vboxnetflt.* Modules.symvers modules.order
make[1]: Leaving directory `/opt/VirtualBox/src/vboxnetflt'
make[1]: Entering directory `/opt/VirtualBox/src/vboxnetadp'
for f in . linux r0drv r0drv/linux VBox common/err common/string common/log generic math/gcc; \
do rm -f $f/*.o $f/.*.cmd $f/.*.flags; done
rm -rf .vboxnetadp* .tmp_ver* vboxnetadp.* Modules.symvers modules.order
make[1]: Leaving directory `/opt/VirtualBox/src/vboxnetadp'
rm -f vboxdrv.ko vboxnetflt.ko vboxnetadp.ko
*** Building 'vboxdrv' module ***
make[1]: Entering directory `/opt/VirtualBox/src/vboxdrv'
make KBUILD_VERBOSE= -C /lib/modules/2.6.33-ARCH/build SUBDIRS=/opt/VirtualBox/src/vboxdrv SRCROOT=/opt/VirtualBox/src/vboxdrv modules
make[2]: Entering directory `/usr/src/linux-2.6.33-ARCH'
CC [M] /opt/VirtualBox/src/vboxdrv/linux/SUPDrv-linux.o
In file included from /opt/VirtualBox/src/vboxdrv/include/VBox/types.h:34,
from /opt/VirtualBox/src/vboxdrv/linux/../SUPDrvInternal.h:39,
from /opt/VirtualBox/src/vboxdrv/linux/SUPDrv-linux.c:37:
/opt/VirtualBox/src/vboxdrv/include/iprt/types.h:100:30: error: linux/autoconf.h: No such file or directory
make[3]: *** [/opt/VirtualBox/src/vboxdrv/linux/SUPDrv-linux.o] Error 1
make[2]: *** [_module_/opt/VirtualBox/src/vboxdrv] Error 2
make[2]: Leaving directory `/usr/src/linux-2.6.33-ARCH'
make[1]: *** [vboxdrv] Error 2
make[1]: Leaving directory `/opt/VirtualBox/src/vboxdrv'
make: *** [all] Error 2
Last edited by jeff story (2010-04-18 23:18:00)

Thanks wonder, that did it.
My Arch install has been running so smooth and maintenance free, (or my old age),
I actually had to refer to my notes for this!!!
HMmmm... A good refresher exercise though.

Similar Messages

Unable to rebuild the VMware modules

I try to rebuild VMware modules but ...
[alifaan@dellalifaan ~]$ sudo vmware-modconfig --console --install-all
Password:
Stopping VMware services:
VMware Authentication Daemon done
VM communication interface socket family done
Virtual machine communication interface done
Virtual machine monitor done
Blocking file system done
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make -C /lib/modules/3.2.5-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-3.2.5-1-ARCH'
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/iommu.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-root/modules/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/apic.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/task.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/comport.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/hashFunc.o
CC [M] /tmp/vmware-root/modules/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-root/modules/vmmon-only/vmcore/moduleloop.o
/tmp/vmware-root/modules/vmmon-only/linux/iommu.c: In function ‘IOMMU_AdjustMappings’:
/tmp/vmware-root/modules/vmmon-only/linux/iommu.c:180:4: error: implicit declaration of function ‘iommu_found’ [-Werror=implicit-function-declaration]
/tmp/vmware-root/modules/vmmon-only/linux/iommu.c: In function ‘IOMMU_RegisterDevice’:
/tmp/vmware-root/modules/vmmon-only/linux/iommu.c:415:7: error: too few arguments to function ‘iommu_domain_alloc’
include/linux/iommu.h:68:29: note: declared here
cc1: some warnings being treated as errors
make[2]: *** [/tmp/vmware-root/modules/vmmon-only/linux/iommu.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [_module_/tmp/vmware-root/modules/vmmon-only] Error 2
make[1]: Leaving directory `/usr/src/linux-3.2.5-1-ARCH'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
Unable to install vmmon
uname -a
[alifaan@dellalifaan ~]$ uname -a
Linux dellalifaan 3.2.5-1-ARCH #1 SMP PREEMPT Tue Feb 7 08:34:36 CET 2012 x86_64 Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz GenuineIntel GNU/Linux
This line is confusing me Using 2.6.x kernel build system.
How can I resolve this error?

I fix the error and here is the solution https://bbs.archlinux.org/viewtopic.php … 4#p1055164

Has anyone got the screen flick problem solved?

as above thanks.
(i am starting to get irritated of the flicking screen)

finally got my computer back with more problems than I sent it in with I think. They put in a new logic board, battery, and super drive. I no longer can see my serial number in the about this mac window. also, the battery is loose and sometimes the meter reads 0% and sometimes it will not turn on. I dont know what the deal is. The people that fixed it are in the middle of selling the store so I dont feel like deeling with them for a while until they get all moved. I might just call applecare in the morning or something. I hate this, I am having the worst luck with all my electronics lately.

"Cannot Get Mail - The connection to the server failed" problem SOLVED

Hi All,
I had been getting a the dreaded "Cannot Get Mail - The connection to the
server failed" error on my first generation iPhone (firmware version 2.1) when syncing e-mail with an Exchange server. After many troubleshooting steps I found the problem was the size of the inbox (9K messages). After archiving older messages into folders the iPhone could again sync.
I hope the helps others.
BMc

A hidden fix for this is in active directory, under the persons 'advanced' security permissions. You must 'check' the "include inheritable permissions..." at the bottom of the window.
In Active Directory Users and Computers (be sure that View > Advanced Features is on) , you go into the user account that is having the problem (yours in this case), and right click, Properties.
Once you’re in the user account properties, click the Security tab, then the Advanced button. “Include inheritable permissions from this object’s parent” needs to be checked. This means top-level permissions from the Exchange server itself are able to propagate down to user account settings.
We found this out using the Exchange remote connectivity analyzer at https://www.testexchangeconnectivity.com which is a great site (owned by Microsoft) for troubleshooting all sorts of problems with remote Exchange access.

Who Said What That Got The "Cold Boot Problems Solved" Thread Deleted?

Hello, guys.
I logged in this morning and saw that Falipay??? had posted last in the thread I started called [something like] "Cold Boot Issues Solved And Temps Now Correct". I didn't get a chance to read it, but now that I've logged back in to see what he and others may have written since my last post, the thread is gone. Not edited...gone.
What happened since I last posted that got it deleted? It's not that important, but I was curious. Hope it wasn't something I did (I'm not showing any warnings).
Anyway, thanks.

Hey, Bas.
I see now that you reinstated my deleted thread. It should be apparent that my thread was not about me "telling people to buy Asus". Thanks for reconsidering your position.
And thanks Maxed Out for coming to my defense in the following thread (the "foul" language thing had me confused until I realized you guys were originally discussing something that happened before I ever joined the forum):
Re: Maxed Out's post dated 7-21-2004
From https://forum-en.msi.com/index.php?threadid=53961&sid=
Quote
bump due to yet more deleted threads.............
Link to mention of deleted thread......
https://forum-en.msi.com/index.php?threadid=55411&sid=
The thread that was deleted provided relevant user evidence of differences in MB's using the identical NF3-250 chipsets and baseline CPU, memory and power supply. With different results ....thus pointing to apparently correctable issues MSI needs to address.........there was absolutly no fol..(faoul foul fal?)...fowl language there, the users tests and opinions were presented unbiasedly and rationally (and had appropriate praise for MSI's strengths (spelling from BIOS)..........
Why shouldn't forum users be advised of this?
Later.

Virtualbox doesn't compiles "vboxdrv" module for 2.6.24 kernel

I installed Virtualbox, however I cannot launch any OS because the vboxdrv module doesn't exists for the latest kernel (I found another module for the 2.6.23 kernel); so the GUI says that I should execute this:
/etc/init.d/vboxdrv setup
However that file doesn't exists. I already tried to uninstall virtualbox and reinstalling from pacman, but still no luck.
What should I do? Is this a bug?
Thanks in advance.

I think that's where the confusion is. When I got the package from AUR it had:
-rw-r--r-- 1 ralvez users 217 2008-01-08 15:58 interfaces
-rw-r--r-- 1 ralvez users 3596 2008-01-20 11:38 PKGBUILD
-rwx------ 1 ralvez users 174 2007-12-30 04:23 vbox_build_module
-rw-r--r-- 1 ralvez users 2384 2007-12-30 07:39 vbox.install
-rw-r--r-- 1 ralvez users 2179 2007-12-30 07:31 vboxnet.patch
So the patch file is there (in bold text) ... and is not executable is a text file. That's why I'm asking if I have to do something with it to make the whole thing work.
Since it is just a plain text file if I try to use it as an upgrade patch it fails with error:
loading package data... error: error while reading package vboxnet.patch: Unrecognized archive format: Invalid or incomplete multibyte or wide character
error: failed to add target 'vboxnet.patch'
So, I'm stuck. I see no way to solve the problem.
R.
Edit: On re-reading your post I wonder what package from core are you referring to? I was under the impression that when we use AUR we are "fetching" files not from core but form the AUR source.
Am I wrong?
Last edited by ralvez (2008-02-13 22:50:31)

WiFi connection problem solved

My intel iMac and MBA had no problem but iPods 3g and 5g did. I had an old Netgear router connected and sitting next to my Airport Express. On a hunch I diconnected the Netgear and created a guest network to replace the one on the Netgear. PROBLEM SOLVED!
Evidently our iPods and boarder's iPhone had problems sorting out the signals and finding the right addresses. Moving the AE to a higher and slightly more central position also helped.
Jim

Same here on a Vodafone PocketWiFi 2.
Tried NetworkManager, wicd, wifi-menu but all have the same issue.
I recently installed Aptosid on another machine and it has the same problem... It also has kernel version 3.9.
All the live CDs I've tried work, even an Arch CD from May works, though a current install does not.
I have no problems connecting to another (wpa2 enterprise) network yet can't on this 3G modem.
I'm hoping this isn't a permanent issue and perhaps an update very soon will fix this.
It seems the only way to fix this for now is to use an old version of Linux. I'm currently running a virtual machine only for the purpose of Internet sharing, very annoying.

Printer Problem Solved!

I was happily printing valentines for my grandchildren when all of a sudden my Epson Stylus N11 would not go. The printer icon in the dock bobbled and the message said the printer did not recognize the ink cartridges! Very weird. So I turned the printer off and on and then when I tried to print the message said the computer was unable to communicate with the printer. Restarting my iMac did nothing.
That was very alarming. Did this mean the printer was malfunctioning? Would I need to go out and buy a new one?
Then I went to my preferences in my home folder and deleted everything that said printer or Epson. Restarted the computer. Problem solved! The symptoms seemed to indicate a problem with the printer itself, fortunately it was not. I thought this might be useful to share.

Hello Lars,
i agree with you that the v2.00 of the UFR2 driver works. I have been recommending it for a while now in this forum.
However, during my testing I found that it did not always work perfectly on 10.6 and it did not support all the models of Canon iR. So while it is currently working to your iRC4580, it may not be your final solution because it was not designed to work with 10.6 and I just wanted to make others who read your post aware of this.
Also, because the driver does not officially support 10.6, I was suggesting this as an explanation why Canon
Europe had not posted the same.
One final note. For the sake of other readers If the iRC4580 had an imagePASS-H1 print controller attached, rather than using the internal Canon board, then the UFR2 driver cannot be used.
Hope this clears things up. Like I said, I wasn't disagreeing with you. i was just trying to answer some of the items you raised.
Pahu

Vboxdrv module loading, no /dev/vboxdrv created?

I am freaking baffled now.
I've gone through the process of getting the options configured for my custom kernel to get vboxdrv built and loaded successfully, which it does.
However, despite vboxdrv loading, no /dev/vboxdrv node is created, and virtualbox gives the usual complaint that either the module isn't loaded (it is) or the device is missing (it is).
I've now tried both virtualbox/virtualbox-sources from the standard repository, and virtualbox-bin from AUR, and I get the same results: "modprobe vboxdrv" appears to successfully load the module, with no messages showing up in dmesg (at all - not even a "module loaded" or anything, but the module shows up in lsmod and can be removed with "modprobe -r").
I keep seeing references to a mysterious "/etc/init.d/vboxdrv" (or /etc/rc.d/vboxdrv on Arch) but have never actually seen any indication that this script actually exists.
What in the name of Apshai is going on here? How do I get the vboxdrv module to actually trigger creation of the missing device node?

I'm not sure, I'll have to try it and see. I really don't want to go to a "stock" kernel full-time though.
For reference - output of lsmod:
Module Size Used by
vboxpci 14960 0
vboxnetflt 16743 0
vboxnetadp 18387 0
vboxdrv 1791382 3 vboxnetadp,vboxnetflt,vboxpci
joydev 9908 0
arc4 1370 2
acpi_cpufreq 5893 1
mperf 1195 1 acpi_cpufreq
freq_table 2475 1 acpi_cpufreq
microcode 9337 0
iTCO_wdt 12781 0
processor 27000 1 acpi_cpufreq
ghash_clmulni_intel 4197 0
thermal 7951 0
ac 2336 0
serio_raw 4613 0
iwlwifi 312094 0
psmouse 70632 0
battery 6445 0
coretemp 5582 0
i2c_i801 8140 0
pcspkr 1859 0
mac80211 397055 1 iwlwifi
snd_hda_codec_hdmi 23640 1
iTCO_vendor_support 1889 1 iTCO_wdt
snd_hda_codec_realtek 60273 1
wmi 8435 0
evdev 10150 7
snd_hda_intel 23989 3
snd_hda_codec 94273 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
snd_pcm 74822 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_page_alloc 7145 2 snd_pcm,snd_hda_intel
snd_timer 18926 1 snd_pcm
snd_hwdep 6260 1 snd_hda_codec
snd 58773 13 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel
cfg80211 169793 2 iwlwifi,mac80211
crc32c_intel 1947 0
soundcore 5378 1 snd
nfs 275479 0
nfs_acl 2319 1 nfs
lockd 62646 1 nfs
auth_rpcgss 31668 1 nfs
sunrpc 184537 4 nfs,auth_rpcgss,lockd,nfs_acl
fscache 41179 1 nfs
ehci_hcd 41056 0
sr_mod 14791 0
sd_mod 34760 4
crc_t10dif 1292 1 sd_mod
usbcore 147481 2 ehci_hcd
usb_common 914 1 usbcore
none of the logs nor dmesg even mentions vbox* (except for /var/log/vbox-install.log, which doesn't show any apparent errors). I've tried loading these modules manually and via dkms and I get the same results either way.

Gaim-Skype ANooying problem- SOLVED

Hello Everybody,
I 've just migrated from debian to arch.
And i am impressed with the speed of arch.
Very very nice
I've solved much much greater problems than this curently(k3b,digikam+canon,my scaner, kernel recompile) but this one i cannot solve.
With debian when i closed the gaim or the skype window, the program won't be terminatedm instead it would be put with a nice icon next to the time in gnome-panel.
In arch, when i'm closing this programs.. they are terminated... And i have to keep them constantly runing in the "taskbar".
Is there any solution?
I've searched in the forum with no resault
:x

Well.. Sorry for the disturbence everybody
Problem solved!
I've just had to put add a new gnome panel tha shows the notifications icons..
The gaim and skype programs where not terminated.. there where runing in the background.. i just had no way of bringing them back
Sorry again,

[SOLVED] Can't build vboxdrv module

I can't build vboxdrv module with latest kernel 2.6.32.When I run vbox_build_module, I get
Makefile:152: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
make[1]: Leaving directory `/opt/VirtualBox/src/vboxdrv'
make: *** [all] Error 2
but, when I run
KERN_DIR=/usr/src/linux-2.6.32-ARCH vbox_build_module
I get this error
Makefile:179: *** Error: unable to find the include directory for your current Linux kernel. Specify KERN_INCL=<directory> and run Make again. Stop.
make[1]: Leaving directory `/opt/VirtualBox/src/vboxdrv'
make: *** [all] Error 2
What is the problem here?
Last edited by na12 (2009-12-31 09:26:34)

Also using Virtualbox here and was able to build the modules against the new kernel using this procedure:
Update kernel 31 --> 32
install kernel26-headers (seems to me you have the wrong kernel-headers package)
reboot
rebuild mkinitcpio (KMS)
reboot
rebuild vbox modules
modprobe them or reboot
Last edited by ulukai (2009-12-31 08:38:07)

Lightroom 4 crashes when trying to open the slideshow module. I spent over three hours with both Adobe and Apple tech support and we know it is a permission issue but have not been able to get it solved. It started with the last upgrade to 10.8

Lightroom 4 crashes when trying to open the slideshow module. I spent over three hours with both Adobe and Apple tech support and we know it is a permission issue but have not been able to get it solved. It started with the last upgrade to 10.8

Back up all data.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
Triple-click the following line to select it. Copy the selected text to the Clipboard (command-C):
{ sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -Rh $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2 (optional)
The first step should give you usable permissions in your home folder. This step will restore special attributes set by OS X on some user folders to protect them from unintended deletion or renaming. You can skip this step if you don't consider that protection to be necessary.
Boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open.
In the Terminal window, type this:
resetpassword
That's one word, all lower case, with no spaces. Then press return. A Reset Password window will open. You’re not going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

Update to PS CC 2014 all updated ok, opening image in camera raw if I use any sliders/panels it just freezes the raw module. Anyone with similar problem/solution?

Any solutions/fixes. Photoshop itself it's fully functional apart from the raw opening problem. I did have 8.5rc installed, raw does seem to have updated as I now have PS CC (non 2014 version) fully functional. I have already tried a new download and re install of 2014 to no avail. Also tried a download of the separate raw module, no fix either.
Win 8.1 system
Thanks in advance of any help, was trying to avoid a complete Adobe file wipe.

Ok, so this is actually a Wacom driver problem( I'm using Intuos 4). If I turn off windows ink in Wacom driver settings then my sliders in camera raw become responsive again, but I lose pressure sensitivity in PS. Just updated Wacom drivers, but no joy. Anybody have a work around/fix?

I am having a Startup problem. Someone comes on the screen with Open Firmware to Startup. How can I reset the PRAM myself to solve this problem?

I am having a Startup problem. Someone comes on the screen with Open Firmware to Startup. How can I reset the PRAM myself to solve this problem?

Read these.
http://support.apple.com/kb/HT1431
http://reviews.cnet.com/8301-13727_7-10330118-263.html

Unable to load the kernel module 'nvidia.ko' [SOLVED]

After my most recent kernel upgrade, I can't get my GUI to run. I've tried reinstalling the nvidia driver to no avail.
Any insight would be greatly appreciated. I'm using a GeForce 8400 GS
cat /var/log/nvidia-installer.log
ERROR: Unable to load the kernel module 'nvidia.ko'. This happens most
frequently when this kernel module was built against the wrong or
improperly configured kernel sources, with a version of gcc that differs
from the one used to build the target kernel, or if a driver such as
rivafb/nvidiafb is present and prevents the NVIDIA kernel module from
obtaining ownership of the NVIDIA graphics device(s), or NVIDIA GPU
installed in this system is not supported by this NVIDIA Linux graphics
driver release.
Please see the log entries 'Kernel module load error' and 'Kernel
messages' at the end of the file '/var/log/nvidia-installer.log' for
more information.
-> Kernel module load error: insmod: error inserting './usr/src/nv/nvidia.ko':
-1 No such device
-> Kernel messages:
NVRM: This can occur when a driver such as nouveau, rivafb,
NVRM: nvidiafb, or rivatv was loaded and obtained ownership of
NVRM: the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA graphics adapter probed!
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as nouveau, rivafb,
NVRM: nvidiafb, or rivatv was loaded and obtained ownership of
NVRM: the NVIDIA device(s).
NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
NVRM: No NVIDIA graphics adapter probed!
NVRM: The NVIDIA probe routine was not called for 1 device(s).
NVRM: This can occur when a driver such as rivafb, nvidiafb or
NVRM: rivatv was loaded and obtained ownership of the NVIDIA
NVRM: device(s).
NVRM: Try unloading the rivafb, nvidiafb or rivatv kernel module
NVRM: (and/or reconfigure your kernel without rivafb/nvidiafb
NVRM: support), then try loading the NVIDIA kernel module again.
NVRM: No NVIDIA graphics adapter probed!
ERROR: Installation has failed. Please see the file
'/var/log/nvidia-installer.log' for details. You may find suggestions
on fixing installation problems in the README available on the Linux
driver download page at www.nvidia.com.
Last edited by wsims (2010-06-22 15:06:04)

if you used the packages from repos, the blacklist is done automatically in nvidia,
$ pacman -Qo /etc/modprobe.d/nouveau_blacklist.conf
/etc/modprobe.d/nouveau_blacklist.conf is owned by nvidia 195.36.31-1
$ cat /etc/modprobe.d/nouveau_blacklist.conf
blacklist nouveau
but i guess you just want to mess your system by using unsupported and very bad ways and you are way smarter than the devs if you used that installer
Last edited by wonder (2010-06-22 14:10:01)

Rebuild the vboxdrv Module Problem [SOLVED]

Similar Messages

Maybe you are looking for