SEO

Following the instructions I've reached the point of
http://www.gentoo.org/doc/en/handbook
handbook-x86.xml?style=printable&full=1#kernel_modules (section 22)

I do this,

Code Listing*22: /etc/modules.autoload.d/kernel-2.4 or kernel-2.6

3c59x
Now run modules-update to commit your changes to the /etc/modules.conf file:

Code Listing*23: Running modules-update

# modules-update

When I enter modules-update it fails and tells me;
Warning: could not generate /etc/modprobe.conf!

I have followed instructions, I am doing the 2.6 kernel so I DO take notice
to follow directions for kernel 2.6.5

I've been all over google and the gentoo forums and can't find anyone else
having this same problem..

Help! Please!! I'm a gentoo newbie....

Thanks!!

On Mon, 03 May 2004 07:49:10 +0000, Dave wrote:

> Following the instructions I've reached the point of
> http://www.gentoo.org/doc/en/handbook
> handbook-x86.xml?style=printable&full=1#kernel_modules (section 22)
>
> I do this,
>
> Code Listing*22: /etc/modules.autoload.d/kernel-2.4 or kernel-2.6
>
> 3c59x
> Now run modules-update to commit your changes to the /etc/modules.conf file:
>
> Code Listing*23: Running modules-update
>
> # modules-update
>
> When I enter modules-update it fails and tells me;
> Warning: could not generate /etc/modprobe.conf!
>
> I have followed instructions, I am doing the 2.6 kernel so I DO take notice
> to follow directions for kernel 2.6.5
>
> I've been all over google and the gentoo forums and can't find anyone else
> having this same problem..
>
> Help! Please!! I'm a gentoo newbie....
>

Dont't worry - just do this step after reboot. AFAIK it's because the:
mount -t proc proc /mnt/gentoo/proc
sometimes is and sometimes isn't in the handbook - which (the handbook) is
quite unstabel

PiotrAF wrote:

> On Mon, 03 May 2004 07:49:10 +0000, Dave wrote:
>
>> Following the instructions I've reached the point of
>> http://www.gentoo.org/doc/en/handbook
>> handbook-x86.xml?style=printable&full=1#kernel_modules (section 22)
>>
>> I do this,
>>
>> Code Listing*22: /etc/modules.autoload.d/kernel-2.4 or kernel-2.6
>>
>> 3c59x
>> Now run modules-update to commit your changes to the /etc/modules.conf
>> file:
>>
>> Code Listing*23: Running modules-update
>>
>> # modules-update
>>
>> When I enter modules-update it fails and tells me;
>> Warning: could not generate /etc/modprobe.conf!
>>
>> I have followed instructions, I am doing the 2.6 kernel so I DO take
>> notice to follow directions for kernel 2.6.5
>>
>> I've been all over google and the gentoo forums and can't find anyone
>> else having this same problem..
>>
>> Help! Please!! I'm a gentoo newbie....
>>
>
> Dont't worry - just do this step after reboot. AFAIK it's because the:
> mount -t proc proc /mnt/gentoo/proc
> sometimes is and sometimes isn't in the handbook - which (the handbook) is
> quite unstabel

Pardon my ignorance but I still don't understand.

I typed "mount -t proc proc /mnt/gentoo/proc"
and it tells me, "mount: mount point /mnt/gentoo/proc does not exist"
I must still be missing some steps somehow..
Is there a guide on how to install using only the 2.6 kernel?
I notice that the installation manual is rather murky when it comes to the
2.6 kernel and leaves you to GUESSING some steps and instructions.

I'm far, far away from being an expert at this...

Thanks!

On Mon, 03 May 2004 19:29:11 +0000, Dave wrote:


> Pardon my ignorance but I still don't understand.
>
> I typed "mount -t proc proc /mnt/gentoo/proc"
> and it tells me, "mount: mount point /mnt/gentoo/proc does not exist"

Maybe - mkdir /mnt/gentoo/proc - helps you.

--
Laik

So anyway, it was like, 21:29 CEST May 03 2004, you know? Oh, and, yeah,
Dave was all like, "Dude,

> I typed "mount -t proc proc /mnt/gentoo/proc" and it tells me,
> "mount: mount point /mnt/gentoo/proc does not exist" I must still be
> missing some steps somehow..

The most likely reason for the message is that you indeed lack a
mount point. The solution is to create one, 'mkdir /mnt/gentoo/proc',
assuming that your chroot is /mnt/gentoo.

(I think that's 'mount -t proc none /mnt/gentoo/proc', btw, but I
may be incorrect there.)

> Is there a guide on how to install using only the 2.6 kernel?

It's not a big difference from the 2.4 kernel, really. The big
difference is that you don't emerge alsa-drivers since they're already
in the kernel.

Just merge 'development-sources' instead of 'vanilla-sources' or
'gentoo-dev-sources' instead of 'gentoo-sources'.

> I notice that the installation manual is rather murky when it
> comes to the 2.6 kernel and leaves you to GUESSING some steps and
> instructions.

What steps are missing? Posting a bug report at http://bugs.gentoo.org
might save future users from having the same difficulties as you are
having, especially if you've figured out the missing parts already.

> I'm far, far away from being an expert at this...

I've failed at installing source distributions before I found gentoo,
and I must say that it's got, by far, the best documentation there is.
It's just a matter of finding the right page, most of the time.

--
Time flies like an arrow, fruit flies like a banana. Perth ---> *
22:07:23 up 21 days, 2:41, 4 users, load average: 0.15, 0.07, 0.01
$ cat /dev/bollocks Registered Linux user #261729
deliver open-source models

Johan Lindquist enlightened us with:
> (I think that's 'mount -t proc none /mnt/gentoo/proc', btw, but I may
> be incorrect there.)

You can use that too, but as the manual page states:

The proc file system is not associated with a special device, and when
mounting it, an arbitrary keyword, such as proc can be used instead
of a device specification. (The customary choice none is less
fortunate: the error message `none busy' from umount can be
confusing.)

Sybren
--
The problem with the world is stupidity. Not saying there should be a
capital punishment for stupidity, but why don't we just take the
safety labels off of everything and let the problem solve itself?

So anyway, it was like, 22:22 CEST May 03 2004, you know? Oh, and, yeah,
Sybren Stuvel was all like, "Dude,
> Johan Lindquist enlightened us with:

>> (I think that's 'mount -t proc none /mnt/gentoo/proc', btw, but I
>> may be incorrect there.)

> mounting it, an arbitrary keyword, such as proc can be used instead

I thought 'none' had some significance, indicating that it wasn't a
real device, so that was news to me. (RTFM? How quaint. ) Thanks.

--
Time flies like an arrow, fruit flies like a banana. Perth ---> *
22:51:41 up 21 days, 3:25, 4 users, load average: 0.05, 0.08, 0.05
$ cat /dev/bollocks Registered Linux user #261729
leverage vertical portals

Dave wrote:

> PiotrAF wrote:
>
>> On Mon, 03 May 2004 07:49:10 +0000, Dave wrote:
>>
>>> Following the instructions I've reached the point of
>>> http://www.gentoo.org/doc/en/handbook
>>> handbook-x86.xml?style=printable&full=1#kernel_modules (section 22)
>>>
>>> I do this,
>>>
>>> Code Listing*22: /etc/modules.autoload.d/kernel-2.4 or kernel-2.6
>>>
>>> 3c59x
>>> Now run modules-update to commit your changes to the /etc/modules.conf
>>> file:
>>>
>>> Code Listing*23: Running modules-update
>>>
>>> # modules-update
>>>
>>> When I enter modules-update it fails and tells me;
>>> Warning: could not generate /etc/modprobe.conf!
>>>
>>> I have followed instructions, I am doing the 2.6 kernel so I DO take
>>> notice to follow directions for kernel 2.6.5
>>>
>>> I've been all over google and the gentoo forums and can't find anyone
>>> else having this same problem..
>>>
>>> Help! Please!! I'm a gentoo newbie....
>>>
>>
>> Dont't worry - just do this step after reboot. AFAIK it's because the:
>> mount -t proc proc /mnt/gentoo/proc
>> sometimes is and sometimes isn't in the handbook - which (the handbook)
>> is quite unstabel
>
> Pardon my ignorance but I still don't understand.
>
> I typed "mount -t proc proc /mnt/gentoo/proc"
> and it tells me, "mount: mount point /mnt/gentoo/proc does not exist"
> I must still be missing some steps somehow..
> Is there a guide on how to install using only the 2.6 kernel?
> I notice that the installation manual is rather murky when it comes to the
> 2.6 kernel and leaves you to GUESSING some steps and instructions.
>
> I'm far, far away from being an expert at this...
>
> Thanks!



Oh yeah, I don't know if this matters but I wonder if I misssed something
else, my prompt is this,

livecd linux #

I wonder if I even have the permissions to do these things.
At this point I'm thoroughly confused...

Johan Lindquist wrote:

> So anyway, it was like, 22:22 CEST May 03 2004, you know? Oh, and, yeah,
> Sybren Stuvel was all like, "Dude,
>> Johan Lindquist enlightened us with:
>
>>> (I think that's 'mount -t proc none /mnt/gentoo/proc', btw, but I
>>> may be incorrect there.)
>
>> mounting it, an arbitrary keyword, such as proc can be used instead
>
> I thought 'none' had some significance, indicating that it wasn't a
> real device, so that was news to me. (RTFM? How quaint. ) Thanks.
>


At this point I've discovered that /mnt/gentoo did not exist, so I created
it. Then I mounted /dev/sda3/ to /mnt/gentoo

When I did an ls of /mnt/gentoo I can see a lot of directories in there,
bin, boot, dev, etc, home, lib, mnt, opt, proc, root, sbin, sys, tmp, usr
and var.

I then did a 'mount -t proc none /mnt/gentoo/proc' and it returned me to my
prompt without error. I then tried to run modules-update and I still get
the original error message.

I think that I've skipped more than one step somewhere. Is there any
salvage or should I just reformat and start over from page one??

Thanks!

So anyway, it was like, 23:45 CEST May 03 2004, you know? Oh, and, yeah,
Dave was all like, "Dude,
> Johan Lindquist wrote:
>>> Johan Lindquist enlightened us with:

>>>> (I think that's 'mount -t proc none /mnt/gentoo/proc', btw, but I
>>>> may be incorrect there.)

> At this point I've discovered that /mnt/gentoo did not exist, so I
> created it. Then I mounted /dev/sda3/ to /mnt/gentoo

I'm guessing you did this from /within/ your chroot? The idea is to
prepare the root fs before you actually chroot into it by mounting all
the special devices you'll need while inside. Until you reboot the
new system for the first time, the chrooted environment is a slave to
the one you've initially booted (be it a livecd or an already running
system), so you shouldn't be doing much else besides installing
packages and configuring.

All this is detailed in the installation docs, including the order in
which to do it.

> I think that I've skipped more than one step somewhere. Is there any
> salvage or should I just reformat and start over from page one??

I suggest you start over. You seem to have confused some of the steps,
skipped some and added some. Before you do anything else, read
through the installation handbook and make sure you understand each
step and the reason behind it, /then/ start installing your system,
following the handbook. If something is unclear, ask questions before
you proceed. You'll be happier for it once you're finished, knowing
exactly what you have done to get there.

I think the old "measure twice, cut once" adage applies to computers
as well, if somewhat modified; "Read twice, do once".

--
Time flies like an arrow, fruit flies like a banana. Perth ---> *
09:50:55 up 21 days, 14:24, 5 users, load average: 0.01, 0.01, 0.00
$ cat /dev/bollocks Registered Linux user #261729
target virtual networks