search for: kver

Package: blktap-dkms Version: 2.0.91-1 Severity: important User: debian-qa at lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean

Hi, Everything compiled correctly for the ocfs2 package, but so far the modules will not load with the "well known" module symbol error. FATAL: Error inserting ocfs2 (/lib/modules/2.6.16.27-0.6-smp/kernel/fs/ocfs2/ocfs2.ko): Unknown symbol in module, or unknown parameter (see dmesg) Okay not sure what is up here, any suggestions? BTW, this is the correct module location and I

Has anyone successfully built Asterisk with linux 2.6.9 kernel? It fails in my zaptel build trying to find a Makefile in the /lib/modules/2.6.9/build directory - thanks.

Hi all, I am wanting to use an option from the ./configure script with zaptel to compile zaptel for a different kernel than the running kernel. How do I do that exactly. Example: Current kernel is 2.6.18-8.1.4.el5 and I want to compile zaptel for 2.6.18-53.1.4.el5 I am using centos 5.1 or RHEL 5.1 So when I reboot zaptel is ready to go. How do I do that? Thanks, Jerry

...10 08:35 permissive -rw------- 1 root root 0 Nov 10 08:35 quirks --w------- 1 root root 4096 Nov 10 09:55 remove_id --w------- 1 root root 4096 Nov 10 09:55 remove_slot -r-------- 1 root root 4096 Nov 10 09:55 slots --w------- 1 root root 4096 Nov 10 09:55 unbind # Script do create the initrds KVER="2.6.18-164.6.1.el5xen" mkinitrd -f --omit-scsi-modules --omit-raid-modules \ --with=e1000e --with=xennet --with=xenblk \ --preload=xenblk /boot/initrd-$KVER-domU.img $KVER mkinitrd -f --preload=pciback /boot/initrd-$KVER.img $KVER # cat /etc/modprobe.conf alias eth0 e1000e options ne...

...0 May 16 04:37 usr/lib/modules/3.10.0-514.16.1.el7.x86_64/kernel/drivers/scsi/mpt3sas -rw-r--r-- 1 root root 379021 Apr 12 08:51 usr/lib/modules/3.10.0-514.16.1.el7.x86_64/kernel/drivers/scsi/mpt3sas/mpt2sas.ko So I added it: $ sudo dracut --force --add-drivers mpt3sas --kver=4.9.25-27.el7.x86_64 $ sudo lsinitrd -k 4.9.25-27.el7.x86_64 | grep mpt Arguments: --force --add-drivers 'mpt3sas' --kver '4.9.25-27.el7.x86_64' -rw-r--r-- 1 root root 0 May 16 12:57 etc/fstab.empty -rw-r--r-- 1 root root 22 Nov 5 2016 usr/lib/kbd/...

Hello, I''ve this strange problem. When Xen kernel start and it try to start eth devices, network doesn''t work. It seems to be a problem with NICs firmware. Anyone had this problem? Do you know where I can download firmware upgrade? (on DELL''s site I''ve just searched...) Thanks, Carlo No virus found in this outgoing message. Checked by AVG Free Edition.

...ile DAHDI for an AMD Geode system on my development system which is Intel Atom. Building the kernel is easy - been doing that for years, but DAHDI is just hard and does the wrong thing. So I start by hardwiring HOTPLUG to no because my target device doesn't support nor need it. Then setting KVERS to be the correct thing, and this is picked up by the Makefile, but I really want -march=geode and the only way I've found to get this is to edit Kbuild directly. (And comment out all the modules I really don't want to build like torisa, xpp, etc. Even then it still barfed on the VPMAD...

...let convert (g : G.guestfs) inspect source_disks output rcaps _ = run_update_initramfs_command () ) + else if family = `ALT_family then ( + (* ALT utilities to work with initrd does not support adding modules + * to an existing initrd + *) + let kver = kernel.ki_version in + let kmodpath = kernel.ki_modpath in + + (* find module files *) + let files = g#find kmodpath |> Array.to_list in + let test f = + let r m = sprintf ".*/%s\\.ko$" m |> Str.regexp in + let rmodules = List.map r mo...

Hello Looking to build CentOS based micro EC2 instance bootable from Amazon EBS. Want that the image be minimal, so that I can add only the rpms I want. Despite looking could not find a way to import a CentOS image from scratch or an existing minimal CentOS image that is bootable from EBS. My server must must persist, as I cannot handle issues with a dynamic server, so I want to use a server

...s.org/QaWiki/Xen4) kernel: CentOS release 6.4 (Final) 3.4.61-9.el6.centos.alt.x86_64 I had to modify the Makefile's a little to get to pass the validation since it was referring to kernel 3.0 and 3.5 but not 3.4. But after doing this I still had the following problem: # make make -C bnx2/src KVER=3.4.61-9.el6.centos.alt.x86_64 PREFIX= make[1]: Entering directory `/tmp/Server/Linux/Driver/netxtreme2-7.6.62/bnx2-2.78.11/src' make -C /lib/modules/3.4.61-9.el6.centos.alt.x86_64/build SUBDIRS=/tmp/Server/Linux/Driver/netxtreme2-7.6.62/bnx2-2.78.11/src modules make[2]: Entering directory `/us...

Patch supplied by Mikhail Gordeev, posting for review. I have compile tested it and checked the code and it looks all fine to me, so ACK from my point of view. I did not actually run it because I don't have an ALT Linux install, but it doesn't seem as if it would affect any other distro. Rich.

Hello, # rpm -qa | grep kernel kernel-headers-2.6.18-274.18.1.el5 kernel-PAE-2.6.18-128.el5 kernel-devel-2.6.18-274.18.1.el5 kernel-PAE-devel-2.6.18-274.18.1.el5 [root at localhost ~]# uname -i i386 Trying to install dahdi-linux-complete-2.3.0.1+2.3.0 on CentOS but get below error. Can you please assist in this? [root at localhost dahdi-linux-complete-2.3.0.1+2.3.0]# make make -C linux all

...-4GB-SMP.spec config.status: creating vendor/unitedlinux/ocfs-2.4.19-4GB.spec config.status: creating vendor/unitedlinux/ocfs-2.4.21-107.spec config.status: creating vendor/unitedlinux/ocfs-2.4.21-111.spec config.status: creating vendor/unitedlinux/ocfs-2.4.21-138.spec [root@RAC1 ocfs-1.0.11]# make KVER=up make -C ocfs2 make[1]: Entering directory `/tmp/ocfs/ocfs-compile/ocfs-1.0.11/ocfs2' gcc -nostdinc -fno-strict-aliasing -fno-common -fomit-frame-pointer -include /usr/src/linux-2.4.9-e.38/linux/include/linux/modversions.h -DMODVERSIONS -Wall -Wstrict-prototypes -Wno-format -Wmissing-prototy...

...es/3.10.0-514.16.1.el7.x86_64/kernel/drivers/scsi/mpt3sas > -rw-r--r-- 1 root root 379021 Apr 12 08:51 > usr/lib/modules/3.10.0-514.16.1.el7.x86_64/kernel/drivers/scsi/mpt3sas/mpt2sas.ko > > > So I added it: > > > $ sudo dracut --force --add-drivers mpt3sas --kver=4.9.25-27.el7.x86_64 > $ sudo lsinitrd -k 4.9.25-27.el7.x86_64 | grep mpt > Arguments: --force --add-drivers 'mpt3sas' --kver '4.9.25-27.el7.x86_64' > -rw-r--r-- 1 root root 0 May 16 12:57 etc/fstab.empty > -rw-r--r-- 1 root root 22 Nov...

hi guys, I came across Gerd Hoffmann's repo at http://kraxel.fedorapeople.org/el5/ which seems to have a much newer KVM for EL5 - has anyone managed to get that working ? Even trying with the kver he used ( 2.6.18-53.el5 ) does not seem to satisfy all required symbols. - KB

Updated the kernel on a fc3 box from 2.6.9-1.667 to 2.6.12-1.1372_FC3 today. Now the cvs-head for zaptel won't compile (libpri and asterisk does). The problem seems to be a symlink issue with the zaptel/Makefile looking for: KSRC:=/lib/modules/$(KVERS)/build and it doesn't exist. The kernel source for 2.6.12 was applied succesfully (supposedly) but a find on "build" does not indicate its existance for the 2.6.12 kernel. (The build directory does exist for the old kernel yet.) A google search produced lots of "install the ke...

...th 'make install' - basically the command installed the files in /lib/modules/2.6.13-15-default instead of /lib/modules.2.6.13-15.8-default. If I run the command 'uname -r' I am shown '2.6.13-15.8-default' and I see the Makefile in /usr/src/zaptel has the following line: KVERS:=$(shell uname -r) I then see in the install section lower down the following lines: for x in $(MODULESO); do \ install -D -m 644 $$x $(INSTALL_PREFIX)/lib/modules/$(KVERS)/misc/$$x ; \ done I take from this that it should be placing them in /lib/modules/2.6.13-15.8-default/misc, but as men...

This may be more a Linux issue but maybe someone can help. I need to know how to compile zaptel for a kernel version different from the one I am running at the moment. Basically I need to do this because I run into trouble when the customer updates the Linux kernel and the next time they restart they do not have the zaptel modules installed. What do I need to do to be able to compile zaptel for

Hi, If I have multiple kernel sources in /usr/src, e.g. linux-headers-2.6.26-1-686 linux-headers-2.6.26.custom.1 how does the Zaptel Makefile(?) know which one to pick? Is it a good approach to compile the kernel first and then compile Zaptel "manually" afterwards? Or should I rather put zaptel in /usr/src/modules and use fakeroot make-kpkg ... modules_image in the kernel