From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: boot error
Date: Tue, 24 Jul 2007 14:57:48 +0000 (UTC) [thread overview]
Message-ID: <loom.20070724T164456-697@post.gmane.org> (raw)
In-Reply-To: 20070724091351.5f294783@zaphod.digimed.co.uk
Neil Bothwick <neil <at> digimed.co.uk> writes:
> I use Google to search it "search string site:archives.gentoo.org/gentoo-user"
Very nice, never thought of using google to search a specific site....
> A stage 3 not only gives you the opportunity to build a kernel, it
> requires you to do so (unless you use the live CD kernel which defeats
> the object of using a customisable distro). Stage 3 only skips the
> bootstrap and emerge system steps that take so much time with a Stage 1
> install. I always do Stage 3 installs now, you can emerge -e system once
> the system is running to apply your USE and CFLAGS customisations.
OK, I went back to the handbook install process. I should have used a stage3
but I did not. Builing a kernel using menuconfig the Nvidia MCP51, which
was already preselected, I think that the issue of the a correct driver
is solved? Not really sure until I get the kernel to boot.
I used a stage 1 and got all the way to installing grub before
the install stalled.
Here's the grub error when (page 10 for amd64) I entered
'emerge grub'
rm: cannot remove '/var/tmp/portage/sys-boot/grub-0.97-r3/image/bin':
Funciont not implemented
then it repeats for .../image/lib .../image/usr and so no.
Maybe one of the partions is not rw? The other emerges along the
way ran fine. I did issue a
'etc-update' just before 'emerge grub'. Maybe that caused
the problem for the chrooted environment?
Any ideas?
Should I just trash the install and start over?
This is frustrating because except for using a stage 1 tarball
and issuing a questionable 'etc-update' I verbosely followed
the handbook installation process.
James
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-07-24 15:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 21:04 [gentoo-user] boot error James
2007-07-23 21:17 ` Joshua Doll
[not found] ` <loom.20070723T233436-220@post.gmane.org>
2007-07-23 21:56 ` [gentoo-user] " Joshua Doll
2007-07-23 21:22 ` [gentoo-user] " Neil Bothwick
2007-07-23 21:44 ` maxim wexler
2007-07-23 22:44 ` Neil Bothwick
2007-07-24 3:14 ` [gentoo-user] " James
2007-07-24 8:13 ` Neil Bothwick
2007-07-24 14:57 ` James [this message]
2007-07-24 15:54 ` Neil Bothwick
2007-07-24 16:04 ` Joshua Doll
2007-07-23 22:22 ` [gentoo-user] " Mike Williams
2007-07-24 1:52 ` [gentoo-user] " James
2007-07-24 13:51 ` Mike Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20070724T164456-697@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox