Arch Linux

sant527

Member

Registered: 2009-06-21

Posts: 273

[SOLVED] older kernel modules being used rather than newer one

My system is little old.

I am having problem with linux kernel versions (installed vs being used)

bash$ pacman -Qs linux

local/linux 3.7.10-1 (base)
    The linux kernel and modules
local/linux-api-headers 3.7.4-1
    Kernel headers sanitized for use in userspace

bash$ ls /usr/lib/modules
3.5.4-1-ARCH  3.7.10-1-ARCH  extramodules-3.5-ARCH

bash$ uname -a
Linux 3.5.4-1-ARCH #1 SMP PREEMPT Sat Sep 15 13:04:04 UTC 2012 i686 GNU/Linux

[root@gauranga simha]# lsinitcpio /boot/initramfs-linux.img (only partial output shown regarding modules used from 3.5.4-1)
./usr/lib/modules
./usr/lib/modules/3.5.4-1-ARCH
./usr/lib/modules/3.5.4-1-ARCH/modules.devname
./usr/lib/modules/3.5.4-1-ARCH/modules.builtin.bin
./usr/lib/modules/3.5.4-1-ARCH/modules.symbols.bin
./usr/lib/modules/3.5.4-1-ARCH/modules.alias.bin
./usr/lib/modules/3.5.4-1-ARCH/modules.dep.bin
./usr/lib/modules/3.5.4-1-ARCH/kernel
./usr/lib/modules/3.5.4-1-ARCH/kernel/ehci-hcd.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/crc16.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/i915.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/firewire-core.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/mbcache.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/libata.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/crc-itu-t.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/mmc_core.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/button.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/firewire-sbp2.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/uhci-hcd.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/usbhid.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/ext4.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/drm_kms_helper.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/mmc_block.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/i2c-core.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/intel-gtt.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/libahci.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/i2c-algo-bit.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/ahci.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/usbcore.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/hid.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/video.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/drm.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/jbd2.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/usb-common.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/usb-storage.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/sd_mod.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/cdrom.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/firewire-ohci.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/sdhci-pci.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/scsi_mod.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/sdhci.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/intel-agp.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/sr_mod.ko
./usr/lib/modules/3.5.4-1-ARCH/kernel/agpgart.ko

bash# mkinitcpio -p linux
==> Building image from preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.5.4-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.5.4-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful

bash# cat /etc/mkinitcpio.conf
MODULES="i915"
BINARIES=""
FILES=""
HOOKS="base udev autodetect modconf block resume filesystems keyboard fsck"

Even though i intalled 3.7.10,
uname still shows 3.5.4
/boot/initramfs-linux.img shows modules used from 3.5.4,
mkinitcpio command still uses 3.5.4 even though the mkinitcpio.conf does not specify.
/usr/lib/modules still contains 3.5.4 version  folder.

can any tell me how this is happening. I am using grub2. HOw to get back to the 3.7.10 version

Last edited by sant527 (2013-07-25 07:21:25)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: [SOLVED] older kernel modules being used rather than newer one

Tell us more about your bootloader setup. EFI or BIOS? Separate boot partition? What is the bootloader config actually loading?

Allan

Pacman

From: Brisbane, AU

Registered: 2007-06-09

Posts: 11,672

Website

Re: [SOLVED] older kernel modules being used rather than newer one

I'd check if anything owns the files in 3.5.4-1-ARCH and if not, just delete the folder.

---

PGP Key: F99FFE0FEAE999BD | I develop pacman - buy me a drink!

sant527

Member

Registered: 2009-06-21

Posts: 273

Re: [SOLVED] older kernel modules being used rather than newer one

I have only one partition (root partition - everything stays there, boot, home).

I USE BIOS.

I am using grub2 boot loader.

pasting text about the bootloader config from /boot/grub/grub.cfg

echo    'Loading Linux core repo kernel ...'
    linux    /boot/vmlinuz-linux root=UUID=de9c1526-30ec-4261-a7fe-c21f74aefba0 ro bahci.ignore_sss=1 quiet
    echo    'Loading initial ramdisk ...'
    initrd    /boot/initramfs-linux.img

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,426

Website

Re: [SOLVED] older kernel modules being used rather than newer one

Please use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Fo … s_and_Code

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

sant527

Member

Registered: 2009-06-21

Posts: 273

Re: [SOLVED] older kernel modules being used rather than newer one

I'd check if anything owns the files in 3.5.4-1-ARCH and if not, just delete the folder.

bash$ ls -al /usr/lib/modules/3.5.4-1-ARCH/
total 3168
drwxr-xr-x  4 root root   4096 Mar 10 15:54 .
drwxr-xr-x  5 root root   4096 Mar  9 13:00 ..
lrwxrwxrwx  1 root root     24 Sep 15  2012 extramodules -> ../extramodules-3.5-ARCH
drwxr-xr-x 12 root root   4096 Sep 15  2012 kernel
drwxr-xr-x  2 root root   4096 Sep 21  2012 misc
-rw-r--r--  1 root root 729653 Mar  9 13:00 modules.alias
-rw-r--r--  1 root root 710461 Mar  9 13:00 modules.alias.bin
-rw-r--r--  1 root root   2799 Sep 15  2012 modules.builtin
-rw-r--r--  1 root root   3649 Mar  9 13:00 modules.builtin.bin
-rw-r--r--  1 root root 398446 Mar  9 13:00 modules.dep
-rw-r--r--  1 root root 539587 Mar  9 13:00 modules.dep.bin
-rw-r--r--  1 root root    353 Mar  9 13:00 modules.devname
-rw-r--r--  1 root root 120747 Sep 15  2012 modules.order
-rw-r--r--  1 root root    131 Mar  9 13:00 modules.softdep
-rw-r--r--  1 root root 309921 Mar  9 13:00 modules.symbols
-rw-r--r--  1 root root 388007 Mar  9 13:00 modules.symbols.bin
bash$ 

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,690

Re: [SOLVED] older kernel modules being used rather than newer one

You showed us which kernel is installed, but you did not show us which kernel is actually running.  I do not believe that a 3.7 kernel will load 3.5 modules. 

What is the output of uname -a   ??  I'll wager one beer that it is a 3.5 kernel.  If so, the question is:  Why does your bootloader not know about the 3.7 kernel???   There are several possible reasons.

Edit:  I was wrong, you did tell us:

bash$ uname -a
Linux 3.5.4-1-ARCH #1 SMP PREEMPT Sat Sep 15 13:04:04 UTC 2012 i686 GNU/Linux

And I was right

Let's take the easy tack first.  What is the output of mount  ??   If boot partition was not mounted on /boot when you updated your kernel, then the new kernel cannot be written to the boot partition.  It usually just ends up in the /boot mount point off of /.

Last edited by ewaller (2013-07-25 06:35:45)

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

sant527

Member

Registered: 2009-06-21

Posts: 273

Re: [SOLVED] older kernel modules being used rather than newer one

bash$ ls -al /boot
total 19648
drwxr-xr-x  4 root root     4096 Jul 24 10:14 .
drwxr-xr-x 22 root root   102400 Jul 25 10:29 ..
drwxr-xr-x  6 root root     4096 Jul 25 11:45 grub
-rw-r--r--  1 root root 13298268 Jul 25 10:44 initramfs-linux-fallback.img
-rw-r--r--  1 root root  3424883 Jul 25 10:44 initramfs-linux.img
drwxr-xr-x  2 root root     4096 Jul 24 10:14 syslinux
-rw-r--r--  1 root root  3273616 Sep 15  2012 vmlinuz-linux


bash$ pacman -Qi linux
Name           : linux
Version        : 3.7.10-1
URL            : http://www.kernel.org/
Licenses       : GPL2
Groups         : base
Provides       : kernel26=3.7.10
Depends On     : coreutils  linux-firmware  kmod  mkinitcpio>=0.7
Optional Deps  : crda: to set the correct wireless channels of your country
Required By    : None
Conflicts With : kernel26
Replaces       : kernel26
Installed Size : 62660.00 KiB
Packager       : Tobias Powalowski <tpowa@archlinux.org>
Architecture   : i686
Build Date     : Thu 28 Feb 2013 02:32:30 PM IST
Install Date   : Sat 09 Mar 2013 12:01:07 AM IST
Install Reason : Explicitly installed
Install Script : Yes
Description    : The linux kernel and modules

bash$ pacman -Qo /boot/vmlinuz-linux 
/boot/vmlinuz-linux is owned by linux 3.7.10-1

if you observe the date of vmlinux-linux is sep-15,2012 same as uname output date.

but the installation of new linux kernel is mar 9, 2013. and vmlinux-linux is owned by linux 3.7.10

how is this possible.

Before i installing linux 3.7.10, i have virtualbox installed in my computer. Its modules are still show in old kernel.

bash$ ls -al /usr/lib/modules/3.5.4-1-ARCH/misc
[simha@gauranga boot]$  ls -al /usr/lib/modules/3.5.4-1-ARCH/misc
total 424
drwxr-xr-x 2 root root   4096 Sep 21  2012 .
drwxr-xr-x 4 root root   4096 Mar 10 15:54 ..
-rw-rw-r-- 1 root root 345234 Sep 21  2012 vboxdrv.ko
-rw-rw-r-- 1 root root  12799 Sep 21  2012 vboxnetadp.ko
-rw-rw-r-- 1 root root  29719 Sep 21  2012 vboxnetflt.ko
-rw-rw-r-- 1 root root  28449 Sep 21  2012 vboxpci.ko

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,690

Re: [SOLVED] older kernel modules being used rather than newer one

sant527 you and and I posted at the same time.  Note that your observations support mine.  The time of your kernel in /boot is ancient.  Reinstall the kernel and see if it updates.  Also, is there any chance you are booting from a different boot partition?

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

sant527

Member

Registered: 2009-06-21

Posts: 273

Re: [SOLVED] older kernel modules being used rather than newer one

You showed us which kernel is installed, but you did not show us which kernel is actually running.  I do not believe that a 3.7 kernel will load 3.5 modules. 

What is the output of uname -a   ??  I'll wager one beer that it is a 3.5 kernel.  If so, the question is:  Why does your bootloader not know about the 3.7 kernel???   There are several possible reasons.

bash$ uname -a
Linux gauranga 3.5.4-1-ARCH #1 SMP PREEMPT Sat Sep 15 13:04:04 UTC 2012 i686 GNU/Linux

please see my first post i mentioned uname -a output. But again i am sending.

Also see mkinitcpio -p linux comand uses 3.5.4 kernel modules. By which the boot loader kernel img are made.

and mkinitcpio command uses /boot/vmlinux-linux as the input.

there is some problem with vmlinux-linux which corresponds to 3.5.4 rather than 3.7.10.

why vmlinux-linux didnot got updated while installing kernel 3.7.10

sant527

Member

Registered: 2009-06-21

Posts: 273

Re: [SOLVED] older kernel modules being used rather than newer one

Let's take the easy tack first.  What is the output of mount  ??   If boot partition was not mounted on /boot when you updated your kernel, then the new kernel cannot be written to the boot partition.  It usually just ends up in the /boot mount point off of /.

[root@gauranga boot]# mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=1484368k,nr_inodes=217034,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sda5 on / type ext4 (rw,relatime,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=27,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/sda2 on /media/GAUR type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)

bash# fdisk -l

Disk /dev/sda: 320.1 GB, 320072933376 bytes, 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xb8f7fca6

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048    21585919    10791936   27  Hidden NTFS WinRE
/dev/sda2        21585920   522739703   250576892    7  HPFS/NTFS/exFAT
/dev/sda3       545053320   625137344    40042012+   5  Extended
/dev/sda5   *   545053383   623177414    39062016   83  Linux
/dev/sda6       623177478   625137344      979933+  82  Linux swap / Solaris

bash# lsblk 
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 298.1G  0 disk 
├─sda1   8:1    0  10.3G  0 part 
├─sda2   8:2    0   239G  0 part /media/GAUR
├─sda3   8:3    0     1K  0 part 
├─sda5   8:5    0  37.3G  0 part /
└─sda6   8:6    0   957M  0 part [SWAP]
sr0     11:0    1  1024M  0 rom  

As i mentioned i have not created separate boot partition. I only have root (ext4) and swap

I am also sending the output of reinstalling kernel.

root# pacman -S linux
warning: linux-3.7.10-1 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...

Targets (1): linux-3.7.10-1

Total Installed Size:   61.19 MiB
Net Upgrade Size:       0.00 MiB

Proceed with installation? [Y/n] 
(1/1) checking package integrity                                                              [#######################################################] 100%
(1/1) loading package files                                                                   [#######################################################] 100%
(1/1) checking for file conflicts                                                             [#######################################################] 100%
(1/1) checking available disk space                                                           [#######################################################] 100%
(1/1) upgrading linux                                                                         [#######################################################] 100%
>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio.  Please wait...
==> Building image from preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.7.10-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.7.10-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful

bash# uname -a
Linux gauranga 3.5.4-1-ARCH #1 SMP PREEMPT Sat Sep 15 13:04:04 UTC 2012 i686 GNU/Linux

sant527

Member

Registered: 2009-06-21

Posts: 273

Re: [SOLVED] older kernel modules being used rather than newer one

After reinstalling the vmlinuz-linux file got updated in /boot to date feb 28. After reboot the the uname changed to 3.7.10

I dont know how this happened but.

Max-P

Member

Registered: 2011-06-11

Posts: 164

Re: [SOLVED] older kernel modules being used rather than newer one

After reinstalling the vmlinuz-linux file got updated in /boot to date feb 28. After reboot the the uname changed to 3.7.10

I dont know how this happened but.

Did you reboot after installing the new kernel? Because it is very normal than running uname -a right after updating the package still shows the old kernel, because you are still running the old kernel. Only a reboot can update the kernel (or ksplice, but if you use this kind of tool you know what you are doing anyway).

Also, is there a reason why you install such an old kernel? Current [core] kernel is at 3.9.9, and you are using pacman -S, which suggest your cache or mirror are really out of sync...