Compiled kernel module fails to install

Linpandro · 2012-10-04 02:49:34

A few moments ago finished compiling my own kernel, but still I can not boot with the new kernel.
When installing modules:

make modules_install

I get this:

Warning: you may need to install module-init-tools

The kernel was compiled in the traditional manner, and I get no error with mkinitcpio:

----> mkinitcpio -k 3.2.9 New -g /boot/initramfs-New.img
 
==> Starting build: 3.2.9
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [pata]
  -> Running build hook: [scsi]
  -> Running build hook: [sata]
  -> Running build hook: [filesystems]
  -> Running build hook: [usbinput]
  -> Running build hook: [fsck]
  -> Running build hook: [fglrx]
Building fglrx module for 3.2.9 kernel ...
Ok.
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-New.img
==> Image generation successful

I have the entry in grub and I can enter without problem, but there comes a point where you do not start:

Waiting 10 seconds for device /dev/sda4 ...
ERROR: Unable to find root device '/dev/sda4'.
You are being dropped to a recovery shell
       Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[rootfs /]#

And if my partition /root is /dev/sda4,I found a topic like this, but even I can not fix the problem:
https://bbs.archlinux.org/viewtopic.php?id=135851

Trilby · 2012-10-04 02:56:33

Why aren't you using one of the PKGBUILDs available? This makes the whole process a lot easier.

Also, if you are compiling your own kernel, do you still plan on using an initramfs? I thought eliminating this was one of the major benefits of compiling your own.

I don't know why you end with "if my partition...", don't you know? If you don't know your partitioning scheme, I'm not sure you should be mucking around with your kernel.

Last edited by Trilby (2012-10-04 02:57:44)

Linpandro · 2012-10-04 03:26:33

Sorry, English is not my language.

About initramfs I just search the wiki and what I found.
About the PKGBUILD do not know, I thought it would be simpler to compile my own kernel in the traditional way, this is the first time I compile a kernel in arch, and initramfs is one of the instructions are in the wiki.

* And my partition is / dev/sda4

Sorry for my English, as I said before is not my native language.

stefanwilkens · 2012-10-04 09:48:40

That's a fairly old kernel, is there a reason why you're compiling such an old version? The warning is likely because we switched to kmod, 3.2.9's makefile isn't aware and throws a (trivial) warning.

depmod is still run, you can check if this file exists:

/lib/modules/3.2.9-NewKernel/modules.dep

I built the same kernel from vanilla just now, system was able to boot properly (though X failed due to graphic modules, to be expected). I suspect your grub setup is incomplete.

could you show us:

sudo fdisk -l

ls -l /lib/modules/

ls -l /boot/

the contents of /boot/grub/grub.cfg, please use something like http://pastebin.com/ or http://pastie.org/ for this one

Last edited by stefanwilkens (2012-10-04 09:54:59)

Linpandro · 2012-10-04 14:04:25

I compiled the kernel old version that I have problems with the battery life on the newer versions.
The battery only lasts me one hour, but that is another problem.

fdisk:

Disk /dev/sda: 500.1 GB, 500107862016 bytes, 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Identificador del disco: 0x5d8c0991

Disposit. Inicio    Comienzo      Fin      Bloques  Id  Sistema
/dev/sda1   *        2048      409599      203776    7  HPFS/NTFS/exFAT
/dev/sda2          409600   147210239    73400320    7  HPFS/NTFS/exFAT
/dev/sda3       147219660   862304939   357542640    5  Extendida
/dev/sda4   *   862304940   976773167    57234114   83  Linux
/dev/sda5       147219723   859477499   356128888+   7  HPFS/NTFS/exFAT
/dev/sda6       859477563   862304939     1413688+  82  Linux swap / Solaris

/lib/modules:

drwxr-xr-x 4 root root 4096 oct  3 20:40 3.2.9
drwxr-xr-x 3 root root 4096 oct  3 08:55 3.5.4-1-ARCH
drwxr-xr-x 2 root root 4096 oct  3 08:55 extramodules-3.5-ARCH

/boot:
[

drwxr-xr-x 6 root root     4096 oct  3 06:20 grub
-rw-r--r-- 1 root root 12612222 oct  3 08:55 initramfs-linux-fallback.img
-rw-r--r-- 1 root root  3098536 oct  3 08:55 initramfs-linux.img
-rw-r--r-- 1 root root  2016551 oct  3 20:40 initramfs-New.img
-rw-r--r-- 1 root root  2081862 oct  3 19:37 System.map-New
-rw-r--r-- 1 root root  3444736 sep 15 00:15 vmlinuz-linux
-rw-r--r-- 1 root root  4434400 oct  3 19:35 vmlinuz-New

I install grub-legacy of AUR, but I have to change to syslinux.
For now this is my menu.lst:

# (0) Arch Linux
title  Arch Linux
root   (hd0,3)
kernel /boot/vmlinuz-linux root=/dev/sda4 nomodeset vga=773 ro
initrd /boot/initramfs-linux.img

# (0) Arch Linux
title  Arch Linux NK
root   (hd0,3)
kernel /boot/vmlinuz-New root=/dev/sda4 nomodeset ro
initrd /boot/initramfs-New.img

Trilby · 2012-10-04 14:48:17

?? is sda4 your root parition? What is your partitioning scheme?

Unless you have boot and root on the same partition (which is certainly possible, but not often in the recommended partitioning schemes) then your grub config is wrong.

EDIT: sorry for pursuing what turned out to be irrelevant. Having a shared boot and root is perfectly fine, I just don't see it that often so it seemed a potential suspect.

Last edited by Trilby (2012-10-04 19:28:40)

Linpandro · 2012-10-04 15:11:05

That's right, my root partition is sda4.
Never had a separate partition for / boot, that's not necessary and I have never had problems.

The GRUB configuration points to the root partition, which would sda4.

Obviously, the GRUB configuration is correct, because if I can start the system with the first kernel.

stefanwilkens · 2012-10-04 18:04:10

Your partitioning setup is fine, obviously the other kernel boots. The problem is likely in the kernel / module setup.

You're running this:

mkinitcpio -k 3.2.9 New -g /boot/initramfs-New.img

That isn't correct, that space should not be there. It should be this:

mkinitcpio -k FullKernelName -g /boot/initramfs-YourKernelName.img

FullKernelName should be 3.2.9-localversion, localversion being whatever you've set here during this step:
https://wiki.archlinux.org/index.php/Ke … al_version

YourKernelName should just be whatever you set as localversion.

Modules seem to be installed to /lib/modules/3.2.9/ but your other thread mentions that you've used "NewKernel" as your localversion. None of this is adding up The fact that /lib/modules/3.2.9/ exists tells me that you didn't set anything as localversion?

I suggest you remove what you've installed thus far and start over, carefully following the wiki. This isn't making sense.

To clarify, the kernel name is something that you have to configure in the kernel's config before you build it. Just giving the files another name isn't the proper way to do this.

Linpandro · 2012-10-04 18:23:43

But this way I can not generate the image with mkinitcpio.
I did not compile the kernel with the current configuration file, do the whole process with settings kernel sources that were downloaded.
Before NewKernel had created the image, but accidentally forget to add modules to the hard drive and got a kernel panic.
This time add support for my SATA hard drive and create the image called New, NewKernel was removed.

EDIT:ok I added a local version Compiled call, but still does not work, and I get the same error.

ls /lib/modules
3.2.9  3.2.9Compiled  3.5.4-1-ARCH  extramodules-3.5-ARCH

mkinitcpio -k 3.2.9Compiled -g /boot/initramfs-KCompiled.img

Waiting 10 seconds for device /dev/sda4 ...
ERROR: Unable to find root device '/dev/sda4'.
You are being dropped to a recovery shell
       Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[rootfs /]#

Now create the image called KCompiled,When the new kernel function, the remaining images will be removed.

Last edited by Linpandro (2012-10-04 18:42:33)

Linpandro · 2012-10-05 02:16:18

any idea?

stefanwilkens · 2012-10-05 10:21:55

Please do an fdisk -l while in the recovery shell

Linpandro · 2012-10-05 13:36:45

I can not use that command sheell recovery:
command not found

Linpandro · 2012-10-05 23:27:30

Any idea?
I don't know what else you can do.

Last edited by Linpandro (2012-10-05 23:27:58)

Linpandro · 2012-10-08 14:28:14

Any idea?
I don't know what else you can do.

Lone_Wolf · 2012-10-09 11:49:20

If the recovery shell doesn't have that command, try booting with a live CD/usb and run it from that.

Linpandro · 2012-10-09 13:41:56

Disk /dev/sda: 500.1 GB, 500107862016 bytes, 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Identificador del disco: 0x5d8c0991

Disposit. Inicio    Comienzo      Fin      Bloques  Id  Sistema
/dev/sda1   *        2048      409599      203776    7  HPFS/NTFS/exFAT
/dev/sda2          409600   147210239    73400320    7  HPFS/NTFS/exFAT
/dev/sda3       147219660   862304939   357542640    5  Extendida
/dev/sda4   *   862304940   976773167    57234114   83  Linux
/dev/sda5       147219723   859477499   356128888+   7  HPFS/NTFS/exFAT
/dev/sda6       859477563   862304939     1413688+  82  Linux swap / Solaris

Not the same result from my system to a live cd?

Lone_Wolf · 2012-10-10 10:35:19

Not entirely the same, as the partitions used by be live CD will be in the report also.

However, fdisk -l lists all partitions on all disks it sees .
it seems weird it only sees /dev/sda , which is a 500 Gb harddrive.

To verify what the live environment sees, i suggest you do

# cd /dev
# ls |grep sd
#ls |grep sr
# ls | grep hd

Linpandro · 2012-10-10 14:18:09

ls |grep sd
sda
sda1
sda2
sda3
sda4
sda5
sda6
ls |grep sr
sr0
ls | grep hd

The last command shows nothing.

Lone_Wolf · 2012-10-11 11:52:38

sr0 is an optical drive most likely, the grep HD part was just there incase you had some pata drives.

It does seem sda is the internal harddrive where you installed arch .
I'm not sure why stefan wilkens asked the fdisk- l list, but we have that data now.

Linpandro · 2012-10-11 14:47:47

So why do you think is the problem?
The modules for my SATA disk configurations were included in the kernel.

Lone_Wolf · 2012-10-12 12:02:38

Solving this problem may well be out of my expertise, but 1 thing that would be useful is your grub configuration.

If you're using grub2 , check the wiki where that is stored.
for grub legacy, post your /boot/grub/menu.lst .

Linpandro · 2012-10-12 14:04:25

This is my menu.lst:

title  Arch Linux
root   (hd0,3)
kernel /boot/vmlinuz-linux root=/dev/sda4 nomodeset vga=773 ro
initrd /boot/initramfs-linux.img


title  Arch Linux Other
root   (hd0,3)
kernel /boot/vmlinuz-New root=/dev/sda4 nomodeset vga=773 ro
initrd /boot/initramfs-New.img

archlinux other is the kernel compiled

Lone_Wolf · 2012-10-13 14:04:59

nomodeset is mostly used to prevent KMS from starting, but vga= has the same effect so using both is probably unneeded.
I doubt that will solve your problem though.

Linpandro · 2012-10-14 17:12:33

I'm using the proprietary driver for ATI card with the driver free the x will not start.
The nomodeset is to see my screen, if I add the screen is black.

Why do you say that I may not solve the problem?
If you help others, especially the more experienced, could solve the problem.

Lone_Wolf · 2012-10-14 18:44:21

I meant that removing nomodeset from the kernel line is unlikely to solve your boot problem with the selfcompiled kernel.

Arch Linux

#1 2012-10-04 02:49:34

Compiled kernel module fails to install

#2 2012-10-04 02:56:33

Re: Compiled kernel module fails to install

#3 2012-10-04 03:26:33

Re: Compiled kernel module fails to install

#4 2012-10-04 09:48:40

Re: Compiled kernel module fails to install

#5 2012-10-04 14:04:25

Re: Compiled kernel module fails to install

#6 2012-10-04 14:48:17

Re: Compiled kernel module fails to install

#7 2012-10-04 15:11:05

Re: Compiled kernel module fails to install

#8 2012-10-04 18:04:10

Re: Compiled kernel module fails to install

#9 2012-10-04 18:23:43

Re: Compiled kernel module fails to install

#10 2012-10-05 02:16:18

Re: Compiled kernel module fails to install

#11 2012-10-05 10:21:55

Re: Compiled kernel module fails to install

#12 2012-10-05 13:36:45

Re: Compiled kernel module fails to install

#13 2012-10-05 23:27:30

Re: Compiled kernel module fails to install

#14 2012-10-08 14:28:14

Re: Compiled kernel module fails to install

#15 2012-10-09 11:49:20

Re: Compiled kernel module fails to install

#16 2012-10-09 13:41:56

Re: Compiled kernel module fails to install

#17 2012-10-10 10:35:19

Re: Compiled kernel module fails to install

#18 2012-10-10 14:18:09

Re: Compiled kernel module fails to install

#19 2012-10-11 11:52:38

Re: Compiled kernel module fails to install

#20 2012-10-11 14:47:47

Re: Compiled kernel module fails to install

#21 2012-10-12 12:02:38

Re: Compiled kernel module fails to install

#22 2012-10-12 14:04:25

Re: Compiled kernel module fails to install

#23 2012-10-13 14:04:59

Re: Compiled kernel module fails to install

#24 2012-10-14 17:12:33

Re: Compiled kernel module fails to install

#25 2012-10-14 18:44:21

Re: Compiled kernel module fails to install

Board footer