recent kernels won't boot

[Evan Martin]

Could you give me some pointers on how this is done?  The last time I
fought with kernels was in the 2.4 days.
For example, can I unpack the existing initrd and add the module to
it?  If so, how do I unpack it?  It's a gzipped <something> but that
something isn't ext2 or cramfs according to mount, and that's what all
pages I can dig up on Google say.

On 10/4/05, MAIN Thomas D <thomas.main at us.labinal.com> wrote:
> I experienced this as well, in my case all the needed modules were not
> included in the initrd.  I'm using jfs for a filesystem, and upon
> booting / could not be loaded and the system dropped into busybox
> complaining that /sbin/init could not be found.  I rebooted into the
> 2.6.10-5 kernel, created a new initrd for the 2.6.12-9, making sure I
> had the jfs module included and everything appears to be fine.
>
> Tom Main
> 940-270-5645
> tom.main at us.labinal.com
>
>
>
> > -----Original Message-----
> > From: ubuntu-users-bounces at lists.ubuntu.com
> > [mailto:ubuntu-users-bounces at lists.ubuntu.com] On Behalf Of
> > Evan Martin
> > Sent: Tuesday, October 04, 2005 12:51 PM
> > To: Art Alexion
> > Cc: Ubuntu Help and User Discussions
> > Subject: Re: recent kernels won't boot
> >
> >
> > On 10/4/05, Art Alexion <art.alexion at verizon.net> wrote:
> > > Kernel updates execute the update-grub process.  The
> > /boot/grub/menu.lst
> > > file works with single (#) and double (##) comments.  when
> > booting grub
> > > ignores text following both single and double comments, but
> > update-grub
> > > only ignores double comments.  It updates your grub menu to reflect
> > > kernel updates using the lines following single comments.
> > >
> > > If you added or removed drives or partitions, your /boot
> > directory which
> > > used to reside on /dev/hda2, may now reside elsewhere, but
> > the single
> > > commented defaults in menu.lst still point to /dev/hda2.
> > >
> > > I suggest you have a look and if this is your problem, make
> > the changes
> > > to the defaults manually, and then run update-grub.
> >
> > Thanks for the suggestion!  But I haven't changed any hardware.
> > I have both the working and nonworking kernels installed, too, so
> > update-grub hasn't been involved.  It's as simple as: if I pick
> > 2.6.10-5-686-smp from the boot menu it boots fine, but if I pick
> > 2.6.12-6-686-smp from the boot menu it fails.
> >
> > --
> > ubuntu-users mailing list
> > ubuntu-users at lists.ubuntu.com
> > http://lists.ubuntu.com/mailman/listinfo/ubuntu-users
> >
>
>
> ***********************************************************************
> This e-mail and any attachments may contain confidential and
> privileged information. If you are not the intended recipient,
> please notify the sender immediately by return e-mail, delete this
> e-mail and destroy any copies. Any dissemination or use of this
> information by a person other than the intended recipient is
> unauthorized and may be illegal.
> ***********************************************************************
>