OpenSUSE Install :: Install Some Wireless Drivers - Don't Have A /lib/modules/<kernel>/build Directory
Dec 14, 2009
I'm trying to install some wireless drivers, but apparently I don't have a /lib/modules/<kernel>/build directory, which is causing the Makefile to throw an error. Is there a specific place I should point the Makefile at?
I've downloaded a linux driver for my wireless card (Realtek 8191SE), and whenever I try to make it it gives me the following error:make: *** /lib/modules/126.96.36.199-0.1-desktop/build: No such file or directory. Stop. make: *** [all] Error 2I have installed make, pattern devel_basis devel_C_C++, kernel-source, linux-kernel-headers, gcc43, etc.I also tried linking them:# ln -s /usr/src/kernel-headers-188.8.131.52-0.1-desktop /lib/modules/184.108.40.206-0.1-desktop/buildln: creating symbolic link `./build': File existslinux-ynct:/lib/modules # ls220.127.116.11-0.1-debug 18.104.22.168-0.1-desktop 22.214.171.124-0.1-desktop126.96.36.199-0.1-default 188.8.131.52-0.1-xen
I am trying to install an application. But when I do a make it gives me this error . I tried to resolve it by installing kernel-sorce, kernel-devel packages But still cant seem to get rid of the error.
I am having some issues compiling kernel modules against the pre-built OpenSUSE kernel. Whenever I compile a module and try to load it, I get something like:
Code: insmod fs/smbfs/smbfs.ko insmod: error inserting 'fs/smbfs/smbfs.ko': -1 Invalid module format It doesn't actually matter what the module is, they all do the same thing. I have tried the above mentioned smbfs, I've also tried:vmware kernel module
I want to remotely install OpenSUSE on one of my servers. I followed the instructions given at SDB:Remote installation - openSUSE, but it didn't work. (My server reverted back to the already installed system.) I think this has to do with a special kernel module (megaraid_sas) that is necessary for the raid controller. Without this module, the kernel cannot find any disk. Of course, the module is not included in the initrd provided by OpenSUSE. I know how to add files to the initrd, but I have no idea where I have to put the required kernel module and which config file inside the initrd must be modified to make the kernel load the module.
When I build the kernel 2.6.30 source, the rpm package is very big and needed or root filesystem 800-900 Mb. I use "make rpm" as described in Configure, Build and Install a Custom Linux Kernel - openSUSE.
Which configuration options would I need to select to build the correct drivers/modules for my usb mouse and ps/2 keyboard? The mouse is a Microsoft 1.1A Optical (Compatible with USB or PS/2 but plugged into usb port) and the keyboard is just a no name chinese one. BTW i am running Gentoo and linux 2.6.32-gentoo-rc7
I then went agead to download ethernet realtek ethernet gigabyte card driver for my version of linux. I untar the file and i got the directory r8168-x.x.xxx.xx, a README file so i read the README file and it asked me to run ./autorun.sh which i did but i got the following error:
Check old driver and unload it. Build the module and install make: *** /lib/modules/2.6.32-71.el6.x86_64/build: No such file or directory. Stop.
Since new kernel 3.0 update I cannot rebuild vmware modules
sudo vmware-modconfig --console --install-all Unable to initialize kernel module configuration
how to do that. Where do I insert the "CONFIG_LOCALVERSION" line.
Same here. This seems to be due to the kernel version being "3.0" instead of "3.0.0". Recompiling the Kernel (and all modules based on it, e.g. nvidia) with CONFIG_LOCALVERSION=".0-ARCH" allows me to compile the modules and run VMware.
I was trying to install VirtualBox through the YaST > Software Management but it is not working, someone in the forum told me that I have to download the OSE version and do it manual way. Finally I am able to start up VB but not able to use the network connection. Thus I am trying to do this:
/etc/init.d/vboxdrv setup. I get this error:
When I type dmesg, it shows me a bunch of info which I don't know what should look for. When I type modprobe vboxnetflt, I get the error: FATAL: Error inserting vboxnetflt (/lib/modules/184.108.40.206-1.2-default/updates/vboxnetflt.ko): Invalid module format. what should I do in order to get my VB to be able to connect to the internet?
Ok I am a total linux noob, and I was looking through threads and couldn't easily find what I am looking for. I am using a HP Mini 1010nr with broadcom bcm4312 wireless card. I went online and downloaded the drivers onto a USB drive from the broadcom website. All I need to know is what are the commands or the programs I use to install the 32 bit drivers I downloaded?? Sorry I know the answer is in here somewhere but I don't understand what the command is on how to install my drivers from my thumb drive.
ubuntu could delay kernel module installation until device is inserted?Take my usb ath9271 wifi adapter as an example: when kernel boot up, no ath modules are installed until usb wifi apdapter is inserted, ath related modules are insmod.Could anybody how to achieve this? udev or something else?
0 down vote favorite share [fb] share [tw] This is the problem I run lspci -v which checks all drivers on my system and more. It says kernel driver in use is nouveau. Then under that it says kernel modules: nvidia recent, nvidia-96, nouveau, nvidiafb. So what it looks like I have 3-4 drivers for my video card loaded and one, nouveau, being used. I think they conflict with each other.
I'm trying to add drivers other then nouveau, because the mouse freezes with it. At this point I can't seem to get rid of nouveau, I go to terminal and type: sudo apt-get --purge remove xserver-xorg-video-nouveau And it says that it's not loaded so I can't dump it. lspci-v says nouveau is the driver being used and trying to dump it. It says it isn't installed. I'm confused. I want to dump nouveau, what should I do? I also go into Synaptic package manager and it isn't listed as being installed.
I love KDE4 now, but I still want KDE3, so I I want to build KDE3.5.10 and install it to my home directory, sort of like konstruct does, but the current version. I've built almost an entire KDE3 before, so I'm pretty sure it's doable, but what do I do different to point the installer at ~. If the answer is in the man page for make I couldn't see it.
I have, for days, been trying to get a Fedora 15 server to send audio output to the system monitor, an ASUS VH242H, via HDMI. The video portion works perfectly, allowing me to appreciate GNOME 3 for the first time. Sound, on the other hand, is non-existent.
From many, many threads on this problem, I have at least been able to provide some info which might help resolve this. Unfortunately, I have now read too much and followed too many suggestions to be able to find my way through the morass. So, once again, I built a completely new system to ensure a clean start.
Note also that to simplify things, I disabled the on-board audio in BIOS so only Nvidia has any sound output capability. Initially, 'alsamixer -V all' identifies the card and the chip as being PulseAudio. That would change if I used the <F6> option but I have not done so to keep things 'clean' at this point. The 'Master' is full on (100<>100), so muting is not a problem. Next, I searched for the device from the output of /proc/asound/card0 which would match the monitor.
The one device associated with the monitor_name is eld#3.0:
monitor_present 1 eld_valid 1 monitor_name ASUS VH242H
Both the kernel driver and the kernel modules are not what I think I should have. The kernel driver should be HDA NVidia for starters, no? Running modprobe -l and looking for nvidia returns:
'kernel/drivers /video/nvidia/nvidiafb.ko'and 'extra/nvidia/nvidia.ko' But I have not attempted anything beyond this point because I am just too confused as to what needs to be done and who or what manages these values effectively.
I'm trying to install Sun VirtualBox Additions into Fedora 12 which is installed in VirtualBox running on top of Windows 7. As the Fedora install was originally a live distro which was then installed to the HD, it may be missing some essential files for compiling.
My attempt to install the VBoxLinux additions is incomplete and I can't get the full range of video displays. The largest is This is the error message: "Your system does not seem to be set up to build kernel modules".
Should I update Fedora to install all the updates available? I did find one webpage which gave an accurate list of files to install for this purpose but can't find it now.
This is from Centos 5.5 so I apologize to anyone who may be offended.I installed my system and it came with kernel 2.6.18-194.el5. I installed the src.rpm of this kernel with rpm, patched, and built it. Then I did a yum -y install kernel.i686 which installed kernel-2.6.18-194.32.1.el5.centos.plus.src.rpm. Since this was a yum install, why doesn't this new kernel version show in the BUILD and SPEC directory?
Just spent three whole days barking up the wrong tree, solving Fedora 11 and Fedora 12 boot failures because the correct hypothesis was illogical: installation did not update/modify the initrd.
The first couple of times I installed Fedora 11 on the HighPoint Technologies RocketRaid 2640x4, the installation inserted my "custom" driver module (rr26xx) into the initrd, permanently, so that the system booted off the controller card for which the custom driver was inserted. (I yelled about this success in this thread: [url]
My most recent installs of BOTH F11 and F12 on the RocketRaid failed to properly set up the boot. It turns out that the "rr2640" module I "slipstreamed" into the installation process was *NOT* permanently added to the initrd by anaconda. (F12 gave me "no root device found boot has failed, sleeping forever", on boot; F11 hung also, without such error, I presume, during the init script execution). Because of limited resources and time, I only know for sure the module was missing from the F11 initrd, and am ASSUMING the same was the case with F12.
The only difference between the successful installs and the ones with failed boot is that the successful installs were made on a single-drive (JBOD) mode on the controller; whereas, the failed ones were placed on RAID 5. But, AFAIK, the created logical device for the card is "/dev/sda", in both cases, and the kernel can not distinguish between the two cases (or can it?). Thus, the inconsistency cost me a lot of time, and is still inexplicable to me.
Question: What is the best way to deal with custom drivers, today? There are custom spins, and many tools, like isomaster. Stupid question: Is there a way to modify the initrd inside an installer ISO -- be it for CD/DVD/USBboot drive -- beefing the init RAM disk with whatever modules you'd like, for the boot process (using, say, isomaster)?
And what makes anaconda understand that a module must be added to the initrd ? How can one force anaconda to do so?
How does moving to dracut as the initrd tool affect any/all of the above?