Re: Kernel.org kernel woes

From: Jacob Heider (lord-jacob_at_comcast.net)
Date: 01/16/04

  • Next message: Rhys: "Symbolic link to java problem"
    Date: Fri, 16 Jan 2004 08:26:08 GMT
    
    

    On Fri, 16 Jan 2004 02:15:55 -0500, Gwen Morse wrote:

    >
    > I wanted to try installing the "vanilla" kernel from kernel.org. I
    > downloaded 2.6.0 and armed myself with the Redhat Linux 9 Bible (by Negus)
    > and followed the directions on pages 964-966. The kernel _seemed_ to build
    > fine, although, I was not able to build an inetrd image.
    >
    > The book said this was for controlling SCSI devices, so, I left it
    > unbuilt (I have no SCSI devices).
    >
    > I then added the boot information to my grub.conf file, where it appears
    > as thus:
    > title Red Hat Linux (2.6.0)
    > root (hd0,4)
    > kernel /bz-2.6.0 ro root=/dev/hda5 hdb=ide-scsi init 3
    >
    > However, I could not boot into Xwindows (I later added 'init 3' to the end
    > of the kernel line just so I could boot into terminal mode -- it wasn't in
    > my original config). Even terminal mode doesn't work.
    >
    > I get the following error messages (hand-typed as best as I'm able):
    >
    > EXT2-fs warning (dev hda5): ext2_fill_super mounting ext3 filesystem as
    > ext2
    > VFS: mounted root (ext2 filesystem) readonly
    > Freeing unused kernel memory
    > Warning: unable to open an initial console
    > Kernel Panic: no init found. Try passing init=option to kernel
    >
    > Do I need to go back and build an inetrd image? Is there some other issue?
    > Any help would be appreciated. My book doesn't cover this situation at
    > all.
    >
    > Gwen

    You have the ext3 file system on your root device, IINM. Either compile
    ext3 support into your kernel, or run:

    mkinitrd 2.6.0 /boot/initrd-2.6.0.img

    and add the appropriate initrd line to your grub.conf file. HOWEVER, there
    are other changes that need to be made to various utilities and
    initialization files to use a 2.6 kernel. There are documents on migrating
    to the 2.6 kernels on the web, but as you're a newbie, my suggestion would
    be to try the newest 2.4 kernel (2.4.24?) currently available, and wait
    for FC2 (looks like april) for an integrated 2.6 kernel. Just a thought.

    GL
    Jacob


  • Next message: Rhys: "Symbolic link to java problem"

    Relevant Pages

    • Re: CD writing in future Linux (stirring up a hornets nest)
      ... >> Linux kernel, or to avoid integrating a particular device into a unique SCSI ... By not treating ATAPI the same as all other SCSI devices. ... that are on the local network. ...
      (Linux-Kernel)
    • ahc driver now borked in -current?
      ... Running a -current kernel from May 1st, the box works just fine albeit ... than the "Waiting 2 seconds for SCSI devices to settle" message you see ... da2: Attempt to query device size failed: NOT READY, Medium not present ... Opened disk da2 -> 6 ...
      (freebsd-current)
    • Re: CD writing in future Linux (stirring up a hornets nest)
      ... On Linux, the user-space API is to address ... > Linux kernel, or to avoid integrating a particular device into a unique SCSI ... > for network interfaces that are PPP connections via a modem vs. network ... pretty similar to the addressing of SCSI devices on Linux, ...
      (Linux-Kernel)
    • Re: PATCH: cdrecord: avoiding scsi device numbering for ide devices
      ... I have more than 20 years of experiences in Kernel and Application ... primarily SCSI devices and therefore they need to have instance numbers within ... Bugs with unclear reasons that are most likely caused by incorrect timeouts ... You just need to admit that the Linux kernel is _not_ related to the ...
      (Linux-Kernel)
    • Re: Sandisk Cruzer USB flash drive -- gaah!
      ... Gaah! ... > the kernel tries to talk to it twice before giving up. ... This is on my laptop, no other scsi devices, so if you ... Debian GNU/Linux ...
      (Debian-User)