SEO

Hi genkernel fails on make modules. i deleted the entire source
directory and emergerd it again, but it still fails.

GenKernel v3.0.1_beta4-3
* ARCH: x86
* KERNEL VER: 2.4.22-gentoo-r5
* kernel: configuring source
* kernel: running mrproper
* kernel: using config from /usr/share/genkernel/x86/kernel-config-2.4
* kernel: running oldconfig
* kernel: running clean
* kernel: Making dependencies for linux 2.4.22-gentoo-r5
* kernel: Starting compile of linux 2.4.22-gentoo-r5 bzImage
* kernel: Starting compile of linux 2.4.22-gentoo-r5 modules
* gen_die(): compile of modules failed

Any help appriciated

-V-

I had the same problem, with the same kernel, switch to a different
kernel and it worked.

Venkat Venkataraju wrote:
> Hi genkernel fails on make modules. i deleted the entire source
> directory and emergerd it again, but it still fails.
>
> GenKernel v3.0.1_beta4-3
> * ARCH: x86
> * KERNEL VER: 2.4.22-gentoo-r5
> * kernel: configuring source
> * kernel: running mrproper
> * kernel: using config from /usr/share/genkernel/x86/kernel-config-2.4
> * kernel: running oldconfig
> * kernel: running clean
> * kernel: Making dependencies for linux 2.4.22-gentoo-r5
> * kernel: Starting compile of linux 2.4.22-gentoo-r5 bzImage
> * kernel: Starting compile of linux 2.4.22-gentoo-r5 modules
> * gen_die(): compile of modules failed
>
> Any help appriciated
>
> -V-
>

Captains log; stardate Sunday 18 January 2004 04:02 pm, Lieutenant Michael R. reported that.......

> I had the same problem, with the same kernel, switch to a different
> kernel and it worked.
>
> Venkat Venkataraju wrote:
>> Hi genkernel fails on make modules. i deleted the entire source
>> directory and emergerd it again, but it still fails.
>>
>> GenKernel v3.0.1_beta4-3
>> * ARCH: x86
>> * KERNEL VER: 2.4.22-gentoo-r5
>> * kernel: configuring source
>> * kernel: running mrproper
>> * kernel: using config from /usr/share/genkernel/x86/kernel-config-2.4
>> * kernel: running oldconfig
>> * kernel: running clean
>> * kernel: Making dependencies for linux 2.4.22-gentoo-r5
>> * kernel: Starting compile of linux 2.4.22-gentoo-r5 bzImage
>> * kernel: Starting compile of linux 2.4.22-gentoo-r5 modules
>> * gen_die(): compile of modules failed
>>
>> Any help appriciated
>>
>> -V-
>>

Or you can build your kernel manually, its not that difficult, especially if you use
--makemenuconfig or whatever the option is in genkernel to get a list of options to enabled /
disable / modulize in the kernel. All it does after that is the equiv of "make dep && make bzImage
modules modules_install". I've seen quite a few of these kinds of posts (both in newsgroups and
forums) by people using genkernel, and whenever I / we get them to build the kernel manually, they
never have any problems, nor do they have to switch what sources their using.

Genkernel is wothless when you really get down to it. All it does is take away you having to type
one line of commands, and give you the impression that its saving you time.

My first install of Gentoo I used genkernel and immediately didn't like the way it worked. As soon
as the station was up and running I rm -rf'd the .config file inside /usr/src/linux and did
everything by hand. After that, my kernel was a great deal faster, and nearly half the size of the
one by genkernel (ALL of my hardware was working, unlike most done by genkernel).

--
Shan Destromp
---
Sent: Mon, Jan 19, 2004 @ 13.53.10 EST
----
OS: GNU/Linux 2.4.22-gentoo-r5
Processor: AuthenticAMD i686

On Mon, 19 Jan 2004 18:58:36 +0000, Shan Destromp wrote:

> Genkernel is wothless when you really get down to it. All it does is take away you having to type
> one line of commands, and give you the impression that its saving you time.

You must be talking about the -old- genkernel...

================
# genkernel --menuconfig all

*** End of Linux kernel configuration.

* kernel: running clean
* kernel: skipping make dep for non 2.4 kernels
* kernel: Starting compile of linux 2.6.1-rc2-gentoo make
* kernel: Starting compile of linux 2.6.1-rc2-gentoo modules
* Dietlibc: Found bincache at /usr/share/genkernel/pkg/x86/dietlibc-0.24-x86.tar.bz2
* Busybox: Found bincache at /usr/share/genkernel/pkg/x86/busybox-1.00-pre3-patched-x86.bz2
* module-init-tools: configure
* extracting dietlibc bincache
* module-init-tools: make all
* cleaning up dietlibc bincache
* module-init-tools: copying to bincache
* module-init-tools: cleaning up
* devfsd: Found bincache at /usr/share/genkernel/pkg/x86/devfsd-1.3.25-dietlibc-kernel25-x86.bz2 and /usr/share/genkernel/pkg/x86/devfsd-conf-0.24-x86.bz2
* initrd: creating base system
* initrd: copying modules
* initrd: copying auxilary files
* initrd: calculating initrd size
* initrd: calculated size 900 + 100k slop for fs overhead
* initrd: real size 1000
* initrd: creating loopback filesystem
* initrd: moving initrd fs to loopback
* initrd: cleaning up and compressing initrd
* initrd: copying bootsplash
* DONE
==================================

--
-Joseph-
Newbies, we all say & do stupid things sometimes. But, googling is powerful.
http://users.netwit.net.au/~pursang/l-faq.pdf
http://www.gentoo.org/doc/en/index.xml

I used to compile my kernels manually. But genkernel creates initrd
which i dont know how to make one manually.

i tried to compile 2.4.22-r4 and it worked without any probelm.

/V


Joseph wrote:
> On Mon, 19 Jan 2004 18:58:36 +0000, Shan Destromp wrote:
>
>
>>Genkernel is wothless when you really get down to it. All it does is take away you having to type
>>one line of commands, and give you the impression that its saving you time.
>
>
> You must be talking about the -old- genkernel...
>
> ================
> # genkernel --menuconfig all
>
> *** End of Linux kernel configuration.
>
> * kernel: running clean
> * kernel: skipping make dep for non 2.4 kernels
> * kernel: Starting compile of linux 2.6.1-rc2-gentoo make
> * kernel: Starting compile of linux 2.6.1-rc2-gentoo modules
> * Dietlibc: Found bincache at /usr/share/genkernel/pkg/x86/dietlibc-0.24-x86.tar.bz2
> * Busybox: Found bincache at /usr/share/genkernel/pkg/x86/busybox-1.00-pre3-patched-x86.bz2
> * module-init-tools: configure
> * extracting dietlibc bincache
> * module-init-tools: make all
> * cleaning up dietlibc bincache
> * module-init-tools: copying to bincache
> * module-init-tools: cleaning up
> * devfsd: Found bincache at /usr/share/genkernel/pkg/x86/devfsd-1.3.25-dietlibc-kernel25-x86.bz2 and /usr/share/genkernel/pkg/x86/devfsd-conf-0.24-x86.bz2
> * initrd: creating base system
> * initrd: copying modules
> * initrd: copying auxilary files
> * initrd: calculating initrd size
> * initrd: calculated size 900 + 100k slop for fs overhead
> * initrd: real size 1000
> * initrd: creating loopback filesystem
> * initrd: moving initrd fs to loopback
> * initrd: cleaning up and compressing initrd
> * initrd: copying bootsplash
> * DONE
> ==================================
>

Captains log; stardate Monday 19 January 2004 05:04 pm, Lieutenant Joseph reported
that.......

> On Mon, 19 Jan 2004 18:58:36 +0000, Shan Destromp wrote:
>
>> Genkernel is wothless when you really get down to it. All it does is take away
>> you having to type one line of commands, and give you the impression that its
>> saving you time.
>
> You must be talking about the -old- genkernel...
>
<snip>

I fail to see what the big deal about it is. So it can now pre-select your hardware
and such, whoopty doo. Maybe I don't WANT all of my hardware installed (as is the
case with a built in modem and sound), or I don't agree with some of the default
options it pre-selects for me.

I know its all a matter of personal preference, but I feel as though genkernel is
taking away a step Linux users (ESPECIALLY newbies) should have to (learn how to)
do. If you don't know how to build your kernel (and what the options mean) then you
don't know how to fix it when you need to, and so on and so forth ad nauseam,
infinity and what have you.

I dunno, maybe the install docs *shouldn't* have you run it by default, or should
alteast make you use --menuconfig to look around before you let it go on its way

--
Shan Destromp
---
Sent: Tue, Jan 20, 2004 @ 01.51.57 EST
----
OS: GNU/Linux 2.4.22-gentoo-r5
Processor: AuthenticAMD i686

Venkat Venkataraju wrote:
> I used to compile my kernels manually. But genkernel creates initrd
> which i dont know how to make one manually.

I had the same problem until someone explained to me that for the most
part you don't need an initrd. initrd "is a RAM disk that is initialized
(e.g. loaded) by the boot loader before the kernel is started." Unless
you're booting to a scsi drive then initrd isn't needed.

Genkernel 3.x is still new and has some problems. Once you manually
build a kernel (which is very simple) you'll never look back again.
Here's a simplified step by step guide:

Make sure /boot is mounted. running 'mount /boot' if it isn't.

cd /usr/src/linux
This of course drops you into your source directory.

make menuconfig
This will open the kernel configuration utility and select whatever
options you had selected previously. Go through the menus and see if you
want to make some changes. When done hit esc until you're asked if you
want to save your changes. Say yes.

make dep && make bzImage modules modules_install
The build begins.

cp arch/i386/boot/bzImage /boot/kernel-2.4.22-test
Insert your kernel version.

cp System.map /boot/System.map-2.4.22-test
Again, insert your kernel version.

cp .config /boot/config-2.4.22-test
Once again, your kernel version. This just backs up you kernel
configuration file (/usr/src/linux/.config).

modules-update
Updates /etc/modules.conf.

nano -w /boot/grub/grub.conf
Add the following:

title=Gentoo Linux 2.4.22-test
# Partition where the kernel image (or operating system) is located
root (hd0,0)
kernel (hd0,0)/kernel-2.4.22-test root=/dev/hda3

Notice the lack of an initrd? Unless you need a driver loaded _before_
the kernel, initrd isn't needed. Save and exit.

That's it. Reboot and enjoy. If your new kernel fails (because of the
options selected) just reboot, go back to the last working one and
change some options. The first one is the toughest but after a little
while you'll be building custom kernels for different things (like
gaming or video compression).

Good luck and please post your results to the tread.

On Wed, 04 Feb 2004 09:13:02 -0500, Mr. Root wrote:

> That's it. Reboot and enjoy.

Yes, so much easier than:

# genkernel all

....isn't it?

--
-Joseph- Thank God for the ability to PLONK people.
Watch out for people who have forgotten what it's like to be a nOOb.
Give them a good PLONK for 30 days or so. And, be greatful when people
say they are going to PLONK you; that is often a Godsend.

Mr. Root wrote:
> Venkat Venkataraju wrote:
>
>> I used to compile my kernels manually. But genkernel creates initrd
>> which i dont know how to make one manually.
>
>
> I had the same problem until someone explained to me that for the most
> part you don't need an initrd. initrd "is a RAM disk that is initialized
> (e.g. loaded) by the boot loader before the kernel is started." Unless
> you're booting to a scsi drive then initrd isn't needed.

Not quite for that last sentence... more in a bit. (initrd is the main
topic for my post here, just a little background.)

> Genkernel 3.x is still new and has some problems. Once you manually
> build a kernel (which is very simple) you'll never look back again.

Oh so true. Manually configuring your kernel gives you that extra bit of
control (and optimisation) of your system(s). You also learn more than
(just) 'genkernel'.

> Here's a simplified step by step guide:
>
> Make sure /boot is mounted. running 'mount /boot' if it isn't.
>
> cd /usr/src/linux
> This of course drops you into your source directory.
>
> make menuconfig
> This will open the kernel configuration utility and select whatever
> options you had selected previously. Go through the menus and see if you
> want to make some changes. When done hit esc until you're asked if you
> want to save your changes. Say yes.
>
> make dep && make bzImage modules modules_install

This is just an aside but I usually
make dep && make clean bzImage modules modules_install
just for that extra clean feeling (okay, rogue modules get cleaned from
/lib/modules/, helps sometimes with modules-update errors).

> The build begins.
>
> cp arch/i386/boot/bzImage /boot/kernel-2.4.22-test
> Insert your kernel version.
>
> cp System.map /boot/System.map-2.4.22-test
> Again, insert your kernel version.
>
> cp .config /boot/config-2.4.22-test
> Once again, your kernel version. This just backs up you kernel
> configuration file (/usr/src/linux/.config).
>
> modules-update
> Updates /etc/modules.conf.
>
> nano -w /boot/grub/grub.conf
> Add the following:
>
> title=Gentoo Linux 2.4.22-test
> # Partition where the kernel image (or operating system) is located
> root (hd0,0)
> kernel (hd0,0)/kernel-2.4.22-test root=/dev/hda3
>
> Notice the lack of an initrd? Unless you need a driver loaded _before_
> the kernel, initrd isn't needed. Save and exit.

Here we are, about initrd. initrd is an initial ramdisk (compressed
image) that gets passed to the kernel before its boot-up sequence.
initrd decomresses the image and the kernel then loads it as the
(initial) root partition.

It is useful for storage/loading modules before the root partition (or
more precisely /lib/modules/) is available. So for example it is useful
for loading lvm or reiserfs if your root partition needs that. Or a raid
or scsi driver if it needs that.

Now I hear you ask, why not just compile those modules into the kernel?
Well, here is where initrd comes into its own. You can compile one
kernel for many machines with different hardware and just customise the
initial ramdisk image. This means that only the specific modules that a
machine needs to boot will be saved onto the /boot/ partition (most
useful when space is limited).

So in short, there isn't much advantage to an initrd *unless* you're
building a kernel for multiple computers. So as Mr Root wrote, you don't
really need to know how to make an initrd (just yet ).

> That's it. Reboot and enjoy. If your new kernel fails (because of the
> options selected) just reboot, go back to the last working one and
> change some options. The first one is the toughest but after a little
> while you'll be building custom kernels for different things (like
> gaming or video compression).
>
> Good luck and please post your results to the tread.

And GL from me. Enjoy!

--
Ben M.

----------------
What are Software Patents for?
To protect the small enterprise from bigger companies.

What do Software Patents do?
In its current form, they protect only companies with
big legal departments as they:
a.) Patent everything no matter how general
b.) Sue everybody. Even if the patent can be argued
invalid, small companies can ill-afford the
typical $500k cost of a law-suit (not to mention
years of harassment).

Don't let them take away your right to program
whatever you like. Make a stand on Software Patents
before its too late.

Read about the ongoing battle at http://swpat.ffii.org/
----------------

So anyway, it was like, 17:28 CET Feb 04 2004, you know? Oh, and, yeah,
Ben Measures was all like, "Dude,

> make dep && make clean bzImage modules modules_install just for
> that extra clean feeling (okay, rogue modules get cleaned from
> /lib/modules/, helps sometimes with modules-update errors).

I thought modules_install was responsible for wiping out /lib/modules
before installing stuff?

'make clean' only does its thing in /usr/src/linux (well, the current
dir, to be precise), afaik.

> So in short, there isn't much advantage to an initrd *unless* you're
> building a kernel for multiple computers. So as Mr Root wrote, you
> don't really need to know how to make an initrd (just yet ).

Personally, I've never used one. I've not booted off of lvm (because
I find it silly to put such a critical thing as / on a device that is
nothing else than software raid), but I've booted off some odd ide
cards, and I've currently got two boxen running on adaptec scsi cards.

--
Time flies like an arrow, fruit flies like a banana. Perth ---> *
19:11:40 up 11 days, 2:47, 2 users, load average: 2.07, 2.09, 2.08
$ cat /dev/bollocks Registered Linux user #261729
streamline open-source networks