General :: Insmod: Getting "KIlled" Message While Inserting Kernel Module?
May 18, 2010
i created a sample module and while trying to insert it i am getting the message "Killed". But when I did lsmod my module was listed out there and was 'Used by' 1. Maybe because it is in use I cannot do a rmmod on my module. How to overcome this, that is do a rmmod while it is still in use?
I'm new to openSUSE and as a matter of fact, to linux too. I've got a Linksys WUSB600N wireless adapter which used to work fine with some live versions of linux that I was testing out before moving onto suse... Each time, upon booting using live CDs, I used to copy the driver I had downloaded from:
Then 'make' and get into the driver's os/linux directory to load the driver using 'insmod rt2870sta.ko' Now, upon doing a 'make' and 'make install', followed by the 'insmod rt2870sta.ko', I get the error saying:
insmod: error inserting 'rt2870sta.ko': -1 Invalid module format
I tried doing 'modprobe -rv rt2870sta' and didn't get any error messages. But while doing 'modprobe -v', this error shows up: insmod /lib/modules/2.6.27.7-9-default/kernel/drivers/net/wireless/rt2870sta.ko FATAL: Error inserting rt2870sta (/lib/modules/2.6.27.7-9-default/kernel/drivers/net/wireless/rt2870sta.ko): Invalid module format
insmod: error inserting 'kernel.ko': -1 Invalid parametersI am getting this error when i am try to insert kernel.ko into kernelMy systemfedora 12 with gcc 4.4.2insmod kernel.koinsmod: error inserting 'kernel.ko': -1 Invalid parametersmy program
I have some problems with CentOS 5.4 and standard kernel 2.6.32.7, which I need for realtime extensions.With the solution in this thread: [URL] I could boot the new standard kernel , There are still two error messages during the boot process:
module loads successfully; another is using (CC) and then creating the module by "make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules", this module gives the error message when it is inserted, .........
I successfully built the sources for 64 bit linux drivers from [URL].... on the 64 bit F14 machine: Linux localhost.localdomain 2.6.35.6-45.fc14.x86_64 #1 SMP Mon Oct 18 23:57:44 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux and got wl.ko:
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?
After a reboot, my PC just hang. It says "insmod : error inserting '/lib/raid456.ko : -1 File exists ..." then followed by a kernel panic. I have tried to boot using rescue mode but it couldn't find any Linux partition, thus no /mnt/sysimage was mounted. It left me at a shell and I'm stuck there.
i installed SLES 11 sp1 as guest on openSUSE 11.3 host, then change the adapter network from 'NAT' to 'Bridged Adapter', but when i hit start i got this error message: Failed to open a session for the virtual machine sles. Failed to open/create the internal network 'HostInterfaceNetworking-wlan0' (VERR_SUPDRV_COMPONENT_NOT_FOUND). Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND). One of the kernel modules was not successfully loaded. Make sure that no kernel modules from an older version of VirtualBox exist. Then try to recompile and reload the kernel modules by executing '/etc/init.d/vboxdrv setup' as root (VERR_SUPDRV_COMPONENT_NOT_FOUND). but when run: sudo /etc/init.d/vboxdrv setup
I have a problem with loading the powersaving kernel module p4-clockmod.ko. When I try inserting the module (via modprobe or insmod) I get FATAL: Error inserting p4_clockmod (/lib/modules/2.6.31.8-mediaserver/extra/p4-clockmod.ko): Invalid module format The module has been compiled together with the kernel. Other modules load with no problem at all. I've tried recompiling the kernel (after re-installing the sources, make xconfig from scratch) - no avail. There's only one kernel source package installed. Searching the forum and google didn't yield a helping answer.
I'm having some troubles with nfsd in slackware-current. When I start the service, I get the following error messages: Quote:
WARNING: Error inserting sunrpc (/lib/modules/2.6.33-smp/kernel/net/sunrpc/sunrpc.ko): Invalid module format WARNING: Error inserting auth_rpcgss (/lib/modules/2.6.33-smp/kernel/net/sunrpc/auth_gss/auth_rpcgss.ko): Invalid module format WARNING: Error inserting lockd (/lib/modules/2.6.33-smp/kernel/fs/lockd/lockd.ko): Invalid module format FATAL: Error inserting nfsd (/lib/modules/2.6.33-smp/kernel/fs/nfsd/nfsd.ko): Invalid module format
The mount fails from the clients with the error message: Quote: mount.nfs: access denied by server while mounting jupiter:/media/Backup A look at syslog from the server side gives: Quote: exportfs: exports duplicate symbol exportfs_decode_fh (owned by kernel) mountd[28198]: getfh failed: No such device kernel: exportfs: exports duplicate symbol exportfs_decode_fh (owned by kernel)
I need to use a pendrive with the Slackware 13.0 and I've tried a lot of things I've found at the internet but unfortunately they didn't work. It's not possible to use graphical interface because some reasons. So the problem need to be solved by command line.
When I use "lsusb" command, I can see the pendrive.
However, when I try these:
I got the following message: "Module usb-ohci not found" and "Module usbcore not found"
How can I deal with these problem? Because I guess without these module loaded it's not possible to mount the pendrive. Is it right?
When opening gedit as a user I get the following message
Gkt-message: Failed to load module "'pk-gtk-module"
If I try to open gedit as root I get the same message but with other messages. These are shown in the attached file. gtk.txt
This is on an upgraded machine using the preupgrade method. The same has happened on two machines upgraded from F14 to F15 the same way. 64 bit systems.
How to clean this up so the messages do no appear?
I have a Samsung phone GT-B3210. For some time I was unable to find working Windows drivers for it. I eventually gave up looking. Then one time I was charging phone over its USB port and booted Ubuntu and was pleasantly surprised when I saw phone's μSD card reader on my desktop. I now need to switch to Gento and would like to be able to work with phone there too. Lsusb tells me it's detected as Bus 007 Device 006: ID 04e8:663f Samsung Electronics Co., Ltd SGH-E720/SGH-E840but lsmod wasn't very helpful. On the list of loaded modules, I wasn't able to find one which looks like it's related to the phone.
I updated the latest kernel and other new maintenance tonight and started getting this error at boot...doesn't appear to be hindering anything. My encrypted partitions (luks, ext4) still open and are accessible.
modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.29.5-191.fc11.i586/kernel/drivers/crypto/padlock-sha.ko): No such device
See similar errors reported on ubuntu forums... with various recommended workarounds... update/add an alias, blacklist a module, fresh install
I'd like openSUSE to automatically load a kernel module (e.g. libsas) at boot time even no device requires it. In Ubuntu, you would add the module name to the file /etc/modules. Is this the correct place for openSUSE as well?
I wish to recompile serial_core module to make a change in the way ioctl works. I don't wish to rebuild the whole kernel package. Can someone point me to the proper method?? I know I will need to download the kernel headers etc. But I would like to avoid the unneeded compiles of things I don't need to recompile.
I update my last kernl to 2.6.38-rc7 but when I launch VirtualBox, on stdout.The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (2.6.38-rc7) or it failed to load. Please recompile the kernel module and install it by sudo /etc/init.d/vboxdrv setup.
Recently I was trying to look into vmware pvscsi modules for newly announced linux kernel 2.6.35-rc2. I compiled the kernel with option: make oldconfig where it asked me for various interactive options and all I did is Kept pressing the Enter ENTER key(Donno if that is the correct way to slect default ).The Kernel Compilation anyway went fine and I can see new kernel at grub screen, booted and it went fine.Now when I explored I found that nor the vmware_balloon and vmw_pvscsi modules are present which means I need to install these modules.I came to know that recently a new version of the vmware memory drivers being included through this page:
[URL]
where you can see an entry like:
Code:
MODULE_AUTHOR("VMware, Inc."); MODULE_DESCRIPTION("VMware Memory Control (Balloon) Driver"); -MODULE_VERSION("1.2.1.0-K"); +MODULE_VERSION("1.2.1.1-k");
Doesn't it mean that the new kernel has new driver version inboxed?Also, I tried to install modules through modprobe and insmod(seems that this doesnt work) but couldnt do that.
I am experiencing the "slow internet" problem (mentioned multiple times in these forums) but it started exactly when I ran an online update, which switched my boot image from vmlinuz-2.6.31.12-0.1 to vmlinuz-2.6.31.12-0.2. Perhaps a setting somewhere got overridden? When the update occurred, grub couldn't find the OS because it had the wrong version #, and I manually edited it (via a livedisk) and that fixed it; it also switched my vga resolution in the grub conf. OpenSUSE is *acting* like ipv6 is enabled again, but ifconfig doesn't report that, and my MTU is close to 1500.
A quick note for other frustrated Ubuntu users out there. I have a D-Link DWA-510 PCI wireless card (RT61) that just stopped working. After wasting hours searching posts and asking for help, I've determined that there's a problem in the latest Kernel to be rolled out.
I have now installed StartUp-Manager, and used it to boot into the old 2.6.31-22 kernel still on the machine and, hey presto, wireless is working again. It seems like the simplest fix by far.
A kernel update just killed my ATI graphics driver.
Trying to install proprietary graphics driver fails and points at /var/log/jockey.log
This ends with
Code:
If I can't sort this out I'll have to try rebooting into the old kernel to get the graphics driver back. The dreadfully slow scrolling in the browser is starting.