Fedora :: Module Development Version Different With Current Kernel
Sep 21, 2010
I want to do some modules development in fedora 11, by the command uname -r, I get the current kernel running in my system.
Code:
$ uname -r
2.6.30.10-105.2.23.fc11.i686.PAE
But when I run the following command
Code:
# yum install kernel-devel
the package what I installed is kernel-devel-2.6.30.10-105.2.23.fc11.i586 and kernel
development directory is /usr/src/kernels/2.6.30.10-105.2.23.fc11.i586
So,the modules I developed can't insert to current running kernel because current is i686 and the compile environment is i586. Is that a bug of fedora 11?
It is bad enough that the kernel gods have basically required that the whole kernel source tree be installed and configured to compile even a simple module but they have made it so a module compiled on one kernel will not work on any other.
To make the situation worse much of the configuration needed to successfully compile a module has been left out of open suse11.3. If you want to replicate the problems may I suggest you attempt to compile the usb-skeleton.c driver example code that is included with each kernel. If it is the intent of the linux community to limit driver development to the professionals then congratulations.
Which is the current stable version of kernel in fedora 10 and how can I installed because right now I have unstable kernel: uname -a Linux blind 2.6.29.3-60.fc10.x86_64 #1 SMP Sat May 9 04:18:14 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
I just want to get back to latest stable kernel of fedora 10. I'm not able from the grub to choose an older because there are only kernels for fedora 9. The problem was that previously I used fedora 9 however I upgrade it but it was still with kernel of fedora 9 so I pick it the unstable of fedora 10 and I installed it. Right now I just want to get back to current version of kernel in fedora 10 so I can upgrade it to fedora 11.
Where are the kernel headers for the current kernel of F12KDE? I am trying to configure VMWare player on my machine, and on initial startup I got an error message.
I'm trying to set up a netbook I purchased that has a lot of more recent hardware, and so I'm having to compile some kernel modules on my own. I've installed Debian on this particular system, and so the version of gcc that was used to compile the kernel is older than the one currently in the repos. Now, I've installed the version I need, but can't remember how to specify building the modules in question with said version.
I've done this in the past, and recall temporarily changing some variable to use the different version, but it's been a while and I just can't remember. Is there an easier way to do this on the fly for any compilation? Or is changing a variable necessary? If there is no way to explicitly specify gcc version used prior to a compilation, could someone remind me of the variable I need to change to use x.x.x version?
I just ran "yum update" to download the latest kernel from the repository, and noticed that it's 2.6.18-164.11.1 while the latest on www.kernel.org is 2.6.32.4.Out of curiosity, why is there such a discripency between the two? Lack of resources to test and build binaries?
I have installed the fedora 14, but there is no kernel source tree.I read the doc "building a custom kernel".But I don't want to rebuild a new kernel.I just want to install the source tree of current kernel.Could someone tell me the way?
I have a fedora 11 with kernel package: kernel-PAE-2.6.29.6-217.2.3.fc11.i686
I would like to install the devel package for this kernel version, but I can't find it, because in the fedora repo there is only the original kernel (2.6.29.4....) and in the updates repo there is only the newest kernel package (2.6.30....)
Where can I find the packages which are between the fedora and update repos' versions?
I upgraded from 8.04 to 10.04 without issue. Today I was trying to set up the development version of GRASS7, which required changes to Python 2.6. instead of reinstalling,I managed to select remove for all python except minimal for all versions. Ubuntu of course now boots in low graphics mode. Is there a way I can restore it to the default without reinstalling from scratch?
I want to keep my current Kernel (I wanted to keep the last one but read on... lol) Why? Fedora is stable as a rock right now and so is GNOME
Now: 2 updates ago I thought I was cool and I did this: nano /etc/yum.conf and I added.... this: exclude=kernel* nvidia*
But right after the next update.... all hell broke loose.... X errors and more... no need for details since I used tty2 to uncomment the "exclude" in yum.conf... updated and ALL is well and VERY stable (good job to Fedora.... it wasn't your fault... I just know I didn't exclude enough )
"What do I need to exclude in yum.conf if I want to keep the current Kernel as well as Nvidia driver while keeping everything updated besides "kernel* and besides "nvidia* packages"? I know I missed a dependency and that upgrade broke the "old"
I need to install module u32 into the netfilter module for kernel 2.6.27.
I did not see the source code in the kernel version I have. where can I find the code for U32 module.
I have checked "netfilter.org" and looks like POM is discontinued. Is the u32 module committed to kernel version 2.6.27 or need to patch it. If yes, where can I find the patch?
The problem I'm facing is that I can't use my headphone. Sound works, but not the headphone. See my ealier thread. It was suggested to edit the module options, but I don't quite know which buttons to push.
Sound disappears as soon as I try to use an application e.g. News Video Fox, CNN, BBC or playing a video disk or cd disk, and a kernel module crash is reported (listed below from logs) After this happens no sound, and the desktop freezes (X11 only Linux is fine). Restarting X obviously do not solve the problem.
It seems that Fedora 12 has sever problems with Intel Sound cards.
I guess it is not really a Kernel developers problem but more the authors for the sound module causing the crash. I already reported it through the popup to "kernel-oops" by clicking on the "black screen" popup reporting the crash on FC12.
Here follows the logs containing the crash info.
WARNING: at sound/pci/hda/hda_intel.c:565 azx_send_cmd+0x36/0x1df [snd_hda_intel]() (Tainted: G W ) Hardware name: Macmini2,1 BUG?
getting KVM Kernel modules installed under Fedora 14? I'm trying to do a post-installation setup of KVM. I'm getting the "No package kmod-kvm available." error, when doing "yum install kmod-kvm".
My VMWare Player was working fine After updating the kernel it is throwing the error "Unable to build kernel module" my kernel is 2.6.40-4.fc15.x86_64 what to do?
I have a macbook, but I am very much interested in writing device drivers in linux. Currently, I have a debian os installed. I dual booted my mac book. Is there any way, I can work on linux source code in mac book and do the needed development.
I had the 180.xxx nvidia drivers on my FC10 setup.I installed the 185.xxx and am running into issues. It gives me the fatal server error: no screens found message. Before that it says that the nvidia kernel module is 180.xxx and the driver component has 185.xxx. I can't seem to figure out how to uninstall the previous module to make this work. I removed the yum kmod nvidia. I'm running this using sh nvidia.185xxx.xxxx.run . The weird thing is that it sometimes would work but then I would restart and it would break again. Thanks in advance,
im trying to install the driver for my nvidia GeForce 7300 GS.i have Fedora 12 installed in an Intel duo core 2 processor 64 bits.kernel installed is 2.6.31.5-127.fc12.x86_64...i followed leigh's guide i did the 4 steps but after reboot screen goes blanck and X dont work.the log says:
-> Kernel module load error: insmod inserting './usr/src/nv/nvidia.ko' -1 no such device
I have downloaded latest version of sun vm virtual box foe Fedora 13 x64. After installing and creating a VM when I want to start vm I got this error. And when I enter this command on terminal : /etc/init.d/vboxdrv setup
I get this error: Code: [root@localhost arash]# /etc/init.d/vboxdrv setup Stopping VirtualBox kernel module [ OK ] Recompiling VirtualBox kernel module [FAILED] (Look at /var/log/vbox-install.log to find out what went wrong) Log file:
Code: [root@localhost arash]# cat /var/log/vbox-install.log Makefile:159: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop. [root@localhost arash]#
since the release of the 2.6.32.14-127 kernel a couple of days ago I can't use my wireless adapter (rt2870 based) since there isn't a kmod-rt2870 package released for this kernel.Normaly I found that the kmod package was available the same day as the kernel. Does anyone know why there is such a delay this time? Or if there is a workaround
I am new to fedora core and needs desperate help.Now what i can notice is the kernel files doesnot match. will this makes a difference..what do you think ? How can i make the VirtualBox kernel module status [OK] ?
I searched around and found out the kernel accepts only GPL modules, which is pretty dumb. People recommended using rpmfusion's akmods, but that's what I'm using to begin with.
How can I fix this without having to recompile the kernel?
I can not for the work get Virtual Box's Additions to install in my FC12 guest. The error log (/var/log/vboxadd-install.log) shows: Makefile:23: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.. Stop.
I have tried: # KERN_DIR=/usr/src/kernels # KERN_DIR=/usr/src/kernels/2.6.31.12-174.2.22.fc12.i686 # KERN_DIR=/usr/src/kernels/2.6.31.12-174.2.22.fc12.i686/kernel
I think I know quite well what my problem is. However, I'm still too much of a newbie to know how to solve it.My problem: I no longer get a login screen on my server after I ran a yum update which updated my kernel (thank god, vnc server still works).Cause: During startup Fedora complains that it can't load the module nvidia.ko. Reason: The module doesn't match the current kernel.
For a diskfull node (the OS installed in a disk), I can use the 'insmod' command to insert a kernel module into the kernel. And after the reboot, the module is still in the kernel. I have a question here: how, when and which kernel module will be loaded in the boot up process for a diskfull node?And for the diskless node, can I use the chroot or some other ways to install the kernel modules into ramdisk, so that kernel module can work when the diskless node boot up? I think it needs certain mechanism to load the kernel like the boot up of diskfull node.