Also remember that if you don't have fstab set up to mount /boot then
all you will see when you go to look at /boot is ... nothing.
try 'mount /boot' and check to see what is there again.
as for the errors at boot, are they occuring after the kernel goes to
load modules from your modules list? and are you seeing a whole lot of
"rc" or "tree" output?
My box did that after a emerge -U portage a few months back, turned
out there was some confusion in the environment so I just ran:
emerge --sync
emerge --update portage
then manually ran:
etc-update (don't ever,EVER,EVER! let it automatically update your
files, always do the file-by-file compare, this is where most new
gentoo people get "gotcha'd")
env-update
rm /etc/make.profile
ln -s /usr/portage/profiles/default-linux/x86/2004.2 /etc/make.profile
And everything went back to business as usual.
On Wed, 24 Nov 2004 21:09:13 -0700, Kevin Geiss <
kevin@desertsol.com> wrote:
> well, it looks like genkernel has set you up with an initial ram disk
> (initrd). I don't have any experience with that.
>
> the lilo.conf file will tell you where your kernel is that you're booting
> from though. (unless the lilo.conf file has been changed after you ran
> lilo to set the kernel and the boot-time options).
>
> look for /boot/kernel-2.4.26-gentoo-r9 and
> /boot/initrd-2.4.26-gentoo-r9. those should be your kernel and your
> inital ram disk.
>
>
>
> On Wed, Nov 24, 2004 at 04:58:22PM -0800, mike hoy wrote:
> > Something is amiss. BTW i can reboot and use
> > networking and login as a user or root, but there are
> > lots of errors during bootup and when I log in as a
> > normal user. I won't give all those very long errors
> > here. I did check in /boot and there is nothing but
> > lost+found. in lost+found there is nothing
> > i checked lilo *not grub for this install*
> >
> > lilo.conf
> > image=/boot/kernel-2.4.26-gentoo-r9
> > label=gentoo
> > read-only
> > root=/dev/ram0
> > append="init=/linuxrc ramdisk=8192
> > real_root=/dev/hda3
> > initrd=/boot/initrd-2.4.26-gentoo-r9
> >
> > I can't do a reboot now as I'm emerging apache.
> >
> > Just for clarification, I post re: gentoo and
> > slackware and fedora 3 the gentoo box is separate from
> > the slackware/fedora issues.
> >
> > mike h
> >
> >
> > however i can reboot w/out any problems at all. i have
> > to find out exactly where my kernel is
> > --- Kevin Geiss <kevin@desertsol.com> wrote:
> >
> > > this is kind of frightening...
> > >
> > > typically, /dev/hda1 is your /boot partition! so if
> > > you just created a new filesystem there, your
> > > computer won't boot up next time.
> > >
> > > take a look in /boot, see if there is anything in
> > > there. if not, try this:
> > >
> > > mount /boot
> > >
> > > then look in /boot again. :)
> > >
> > > you want to see a kernel image (either vmlin* or
> > > bzImage*) and a grub/ subdirectory
> > >
> > > if you don't see those, you will need to fix that
> > > partition before you reboot next time.
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss