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:
"insmod: error inserting /lib/dm-region-hash.ko -1 fikle exists"
and a problem with ip-tables "could not restore ip-tables line 20" or so
I've upgraded my raid array, and to make it boot I had to regenerate the initrd image (the root was on the raid drive)using
mkinitrd <img file> <kernel version>
after that at boot i always receive this error:
error inserting /lib/raid456.ko: -1 file exists
1)NOT USING MMCONFIG
2)insmod Error inserting `/lib/raid456.ko` -1 File Exist
Dell PowerEdge T110 with 4sata Controllers with Centos2.6.18-238.9.1.el5xen installed .
Code:
/boot on /dev/md0
/ on /dev/md1 Regards
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
__________________kernel.c________________________ ___________
#include <linux/module.h> /* Needed by all modules */
#include <linux/kernel.h> /* Needed for KERN_INFO */
[code].....
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:
SpeedShare - Download rt2870-kernel-2.6.24-nemesis.tar.bz2
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
If I try and paste text from the clipboard when using vim, it automatically inserts hash at the start of every line. This is driving me mad! How to I get rid of it? Ive deleted all my .vim files/directories in my home directory.
View 3 Replies View RelatedAfter 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.
View 3 Replies View Relatedi 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?
View 3 Replies View RelatedI got "Invalid Module format" error while using insmod command. Later i understand that the file is compiled in previous version of Linux. But, currently i don't have the source files to recompile in new version of Linux. I have tried with -f option. Still, It is not working. Is there any other way to solve this problem.
View 3 Replies View RelatedI'm a recently proud owner of a new Aspire AS3810T with Fedora 12 installed, when it boots up before entering the boot screen when it loads I see this error message:IOMMU: Mapping reserved region failedHow can i fix this error? It's quite frustrating
View 2 Replies View Related I was trying to compile and insert a module. The module compiles fine and creates tool.ko file(am compiling it from Desktop). Next when I try to use "insmod tool.ko" , it gives em this error: insmod: error inserting 'tool.ko': -1 Operation not permitted.I tried to use modprobe instead , thinking it might install the dependencies(if any) by itself: "modprobe -v tool.ko" but it gives me this error
FATAL: Module tool.ko not found
I went over some linux forum posts and tried to resolve it but no use.I copied all the files from Desktop to the /lib/modules/2.6.34.7-0.7-Desktop/build folder and then ran the commands but still face the same problem. Used this "/sbin/depmod -a " thinking it might update the modeprob.conf file, but no use !
when a remove a user from the system using the domain userdel guest the user gets removed but the /home/guest doesn't get removed so i remove it by command rm -rf /home/guest then i recreate the user by giving in the command useradd guest now it gives the error mailbox file already exists what does it mean when it says so though this command creates the user.
View 3 Replies View RelatedI 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:
[Code]...
I am still new to porting wifi drivers. I am currently porting Ralink RT5370 driver, no problem with the compilation but when I execute insmod operation I got a lot of errors regarding RTMP. This is a part of the error I got:
rt5370sta: Unknown symbol rausb_buffer_free
rt5370sta: Unknown symbol RtmpOsFreeSpinLock
rt5370sta: Unknown symbol RtmpOsPktHeadBufExtend
rt5370sta: Unknown symbol RtmpOSTaskNotifyToExit
rt5370sta: Unknown symbol RtmpOsGetNetDevName
rt5370sta: Unknown symbol RtmpOsHtonl
rt5370sta: Unknown symbol RtmpOsAtomicInterlockedExchange
rt5370sta: Unknown symbol RtmpUtilInit
rt5370sta: Unknown symbol RtmpOSTaskInit
rt5370sta: Unknown symbol RtmpOsAtomicInit
insmod: can't insert '/home/rt5370sta.ko': unknown symbol in module or invalid parameter
Based on the some forum that I've read, adding the MODULE_LICENSE("GPL") is one of the solution. I did add it inside usb_main_dev.c and recompile but I still get the same errors.
for some reason my first updating was interrupted and from then i cannot update. i get the following message:
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30974) from dbenv->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db3 - (-30974)
error: cannot open Packages database in /var/lib/rpm
CRITICAL:yum.main:
Error: rpmdb open failed
[root@laptop etc]# yum repolist
[Code]....
I've just install qemu-kvm from [URL]
I run modprobe kvm and modprobe kvm-intel to load the modules, but the second command won't work.
It gives the following error -
Code:
root@mika:/home/mika# modprobe kvm-intel
FATAL: Error inserting kvm_intel (/lib/modules/2.6.33.4/kernel/arch/x86/kvm/kvm-intel.ko): Operation not supported
I just downloaded CentOS-5.5-i386-bin-DVD.iso from a mirror and there is no check sum file or hash for
this ISO. The md5sum.txt file contains:
[Code]...
When I deleted uninstalling and installing some packages in Yast2 I got this output:
Deleting mc
Additional rpm output:
rpmdb: PANIC: Invalid argument
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) storing record "4.0-1" into Requireversion
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) setting "3.0.4-1" records from Requireversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) setting "" records from Requireversion index
and on and on for 3 pages for every package.
I have been getting a Hash Sum mismatch error on certain packages since Debian Squeeze became stable,
[Code]...
E: Some index files failed to download. They have been ignored, or old ones used instead.
I am getting an error from yum update and Kpackagekit:
[root@asus-m4n82 tylerm]# yum update
Loaded plugins: refresh-packagekit
Setting up Update Process
rpmdb: page 18816: illegal page type or format
[code]....
How do I "run recovery"? Edit: Ok so it looks like I had som bad ram in my system that caused this - I found a site that told me to do this:
rm -f /var/lib/rpm/__db*
rpm rebuilddb
yum clean all
I did this but now when I try something like yum install firefox it pulls in a ton of already installed packages.
I'm only partially new to Linux. I'm running Fedora 11. I've just set up two machines, I thought to be identical. Evidently I missed something. I had some problems getting the network started on the second machine, and I must have forgotten a name change somewhere. Anyway, after doing lot's of comparisons between the boxes, editing and renaming and re-linking the ifcfg-GigaStorey file, they are both functioning. The problem is that whenever I start or restart the network on box 2, it reports the following error:
Bringing up interface GigaStorey: RTNETLINK answers: File exists
Error adding address 192.168.1.6 for eth0.
[ OK ]
The file ifcfg-GigaStorey is linked in the following directories
/etc/sysconfig/network-scripts
/etc/sysconfig/networking/devices
code....
Like I said, it's not super critical, just annoying. The networking comes up ok, but the error is puzzling. I figure if I learn what this problem is I'll be one step closer to my Linux beanee.
Im trying to update the system packages list by doing "aptitude update", but I got a error like this:
W: Failed to fetch http://download.virtualbox.org/virtualb ... 4/Packages: Hash Sum mismatch
E: Some index files failed to download. They have been ignored, or old ones used instead.
E: Couldn't rebuild package cache
After searching the Web, I saw that many foruns seems to suggest to erase the reference list of packages using the command " rm -rf /var/lib/apt/lists/" and then run "aptitude update" again. I did that but the error still pops up.
My source.list:
### Debian Jessie
deb http://ftp.us.debian.org/debian/ jessie main contrib non-free
deb-src http://ftp.us.debian.org/debian/ jessie main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free
[Code] ....
Lately I have noticed when I am trying to install something I have been getting 'Hash Sum mismatch'
Here is an example when I tried to install Calibre:
root@V-debian:/etc/apt# apt install calibre
Reading package lists... Done
Building dependency tree
Reading state information... Done
[Code]....
I have tried installing skype through synaptic package manager, downloading from website through software centre and also manually using apt-get and dpkg. All I get is the same error - hash sum mismatch so file could not be retrieved. have tried the apt-get update and makes same error. not entirely certain what the --fix missing does or how to run it.
Get:1 [URL] [20.2MB]
Fetched 20.2MB in 6min 31s (51.5kB/s)
Failed to fetch [URL] Hash Sum mismatch
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? I just done successful install for Opera and Thunderbird. just this skype thing I can't seem to sort!
I am compiling the code has hash_map getting following error
Code:
typedef std::hash_map<uint32_t, CTM_ContextData> contexts_map_t;
Compilation Error:
/vobs/ims_hss1/ctm/inc/CTM_DidMemContextManager.h:77: error: ISO C++ forbids declaration of 'hash_map' with no type
/vobs/ims_hss1/ctm/inc/CTM_DidMemContextManager.h:77: error: typedef name may not be a nested-name-specifier
/vobs/ims_hss1/ctm/inc/CTM_DidMemContextManager.h:77: error: expected ';' before '<' token
/vobs/ims_hss1/ctm/inc/CTM_DidMemContextManager.h:78: error: 'contexts_map_t' was not declared in this scope
/vobs/ims_hss1/ctm/inc/CTM_DidMemContextManager.h:78: error: template argument 1 is invalid
/vobs/ims_hss1/ctm/inc/CTM_DidMemContextManager.h:78: error: template argument 2 is invalid
/vobs/ims_hss1/ctm/inc/CTM_DidMemContextManager.h:85: error: 'contexts_map_t' does not name a type
I am having a problem while inserting a particular module.
Following are some prints :-
I am using STLinux-2.4 Distribution, kernel 2.6
I have changed the access permissions on all the .ko as rwx. Still I am getting the problem.
I am running Red Hat with 2.6.18-194.8.1.el5PAE kernel version. I am trying to run encryptfs to encrypt a partition on my hard drive. One of the kernel modules necessary is the md5.ko. I noticed it wasn't loaded in when doing an lsmod. I tried running modprobe md5 and it fails to load:
[root@ ~]# /sbin/modprobe -v md5
insmod /lib/modules/2.6.18-194.8.1.el5PAE/kernel/crypto/md5.ko
FATAL: Error inserting md5 (/lib/modules/2.6.18-194.8.1.el5PAE/kernel/crypto/md5.ko): Invalid argument
I ran dmesg and grepped for md5, but I didn't see anything in there.
I am trying to install a third party driver and the provided makefile makes a call to insmod. Whenever I try to install this I run "su", so I am root and should have permissions. However, when I run "make install" I get the following output:
Code:
# make install
Unloading any instances of foo module
Loading new foo into running kernel
insmod: error inserting 'foo.ko': -1 Operation not permitted
make: *** [install] Error 1
Like I said before, I'm doing this as root, so I don't see how this is possible. Additionally, every time I try to do this it seems to cause a lot of damage to whatever kernel I'm currently booted in; USB and ethernet (and hence the Internet) stop working and I have to wipe the kernel and reinstall it.
After rebooting my centos server I no longer have a /dev/sda entry, nor any /dev/sd* entries. What could have gone wrong?
View 1 Replies View RelatedI 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