Find the answer to your Linux question:
Page 2 of 2 FirstFirst 1 2
Results 11 to 14 of 14
Originally Posted by Rubberman What was your previous kernel before you tried to build/install 2.6.39? And is this 32-bit or 64-bit? I also assume (possibly incorrectly) that you are running ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #11
    Just Joined!
    Join Date
    Apr 2011
    Posts
    12

    Quote Originally Posted by Rubberman View Post
    What was your previous kernel before you tried to build/install 2.6.39? And is this 32-bit or 64-bit? I also assume (possibly incorrectly) that you are running an Intel processor?
    2.6.35-22-generic on 32 bit Intel platform

  2. #12
    Linux Newbie
    Join Date
    Dec 2010
    Posts
    146
    Quote Originally Posted by scuzzy View Post
    The kernel image vmlinuz is being created there. The only problem is with initrd.img.
    On what basis are you configuring the kernel?

    There's NOTHING on the screen? You should see kernel messages at least... if you don't, probably you've not selected the FB device or these modules are not present in the initrd. As a test see if alt+printscreen (or sysrq)+c or alt+printscreen (or sysrq)+b results in a kernel crash (blinking scroll and caps lock).

    Place the contents of /boot with ls -l.

  3. #13
    Just Joined!
    Join Date
    Apr 2011
    Posts
    12
    Quote Originally Posted by dE_logics View Post
    On what basis are you configuring the kernel?

    There's NOTHING on the screen? You should see kernel messages at least... if you don't, probably you've not selected the FB device or these modules are not present in the initrd. As a test see if alt+printscreen (or sysrq)+c or alt+printscreen (or sysrq)+b results in a kernel crash (blinking scroll and caps lock).

    Place the contents of /boot with ls -l.
    As a matter of fact, the caps lock is blinking WITHOUT even pressing those keys... I apologize for not having mention that before.

    Here's the contents of /boot:
    Code:
    $ls -l /boot
    total 23744
    -rw-r--r-- 1 root root   705737 2010-09-20 07:28 abi-2.6.35-22-generic
    -rw-r--r-- 1 root root   128592 2010-09-20 07:28 config-2.6.35-22-generic
    -rw-r--r-- 1 root root    76464 2011-06-09 17:30 config-2.6.39
    drwxr-xr-x 3 root root    12288 2011-06-09 17:45 grub/
    -rw-r--r-- 1 root root 10765192 2011-04-07 18:08 initrd.img-2.6.35-22-generic
    -rw-r--r-- 1 root root   165084 2010-09-24 22:44 memtest86+.bin
    -rw-r--r-- 1 root root   167264 2010-09-24 22:44 memtest86+_multiboot.bin
    -rw-r--r-- 1 root root  1830681 2010-09-20 07:28 System.map-2.6.35-22-generic
    -rw-r--r-- 1 root root  1954458 2011-06-09 17:30 System.map-2.6.39
    -rw-r--r-- 1 root root     1192 2010-09-20 07:31 vmcoreinfo-2.6.35-22-generic
    -rw-r--r-- 1 root root  4289584 2011-04-07 20:32 vmlinuz-2.6.35-22-generic
    -rw-r--r-- 1 root root  4191120 2011-06-09 17:30 vmlinuz-2.6.39
    I have deleted the initrd.img which I created using mkinitramfs which didn't do me any good because I could only boot using recovery mode and with the strange shell prompt I mention in previous posts. The main concern for me is why the initrd.img was not created automatically by make install? I think that might be the main problem...

  4. #14
    Linux Newbie
    Join Date
    Dec 2010
    Posts
    146
    You're having a kernel panic on Boot, and that's cause there's no initramfs. Generate one after booting your old kernel using -

    mkinitramfs -v -k 2.6.39 -o initrd.img-2.6.39

    Also post it's output.

    Post contents of /lib/modules

    Finally update-grub.

Page 2 of 2 FirstFirst 1 2

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •