SEO

My computer won't boot now. I was messing around with kernels and adding
modules such as the e100 and nvdidia. Now my computer won't boot. I used
genkernel to compile a new kernel and when I bot my computer it stops with
this message.

"RAMDISK: Compressed image found at block 0"

I was just going to reload every thing from scratch but I figure I would try
asking for some help first.

Matt

Matthew Martin wrote:

> My computer won't boot now. I was messing around with kernels and
> adding modules such as the e100 and nvdidia. Now my computer won't
> boot. I used genkernel to compile a new kernel and when I bot my
> computer it stops with this message.
>
> "RAMDISK: Compressed image found at block 0"
>
> I was just going to reload every thing from scratch but I figure I
> would try asking for some help first.

Sounds like another genkernel screwup ... I say drop it and do the make
menuconfig yourself. Avoiding the use of an initrd eliminates one point
of failure. If you have no working bootable configuration, just boot
the LiveCD and chroot.

--
PeKaJe

Life is a POPULARITY CONTEST! I'm REFRESHINGLY CANDID!!

I forgot to let you know I'm a newbie. Could you translate that a little.
I know about chroot. but dropping the kernel I assume you talking about.
Your help is appreciated
"Peter Jensen" <usenet@pekajemaps.homeip.net> wrote in message
news:4131f9af$0$234$edfadb0f@dread12.news.tele.dk. ..
> Matthew Martin wrote:
>
> > My computer won't boot now. I was messing around with kernels and
> > adding modules such as the e100 and nvdidia. Now my computer won't
> > boot. I used genkernel to compile a new kernel and when I bot my
> > computer it stops with this message.
> >
> > "RAMDISK: Compressed image found at block 0"
> >
> > I was just going to reload every thing from scratch but I figure I
> > would try asking for some help first.
>
> Sounds like another genkernel screwup ... I say drop it and do the make
> menuconfig yourself. Avoiding the use of an initrd eliminates one point
> of failure. If you have no working bootable configuration, just boot
> the LiveCD and chroot.
>
> --
> PeKaJe
>
> Life is a POPULARITY CONTEST! I'm REFRESHINGLY CANDID!!

Matthew Martin enlightened us with:
> I forgot to let you know I'm a newbie.

In that case: please don't top-post. Remove the quoted text that you
do not directly refer to, and post your reaction below that, just as I
did now.

> Could you translate that a little. I know about chroot. but
> dropping the kernel I assume you talking about.

No, he said:

>> Sounds like another genkernel screwup ... I say drop it

Which means dropping genkernel.

>> and do the make menuconfig yourself. Avoiding the use of an initrd
>> eliminates one point

Which means do the kernel configuration & building yourself. Easy
enough, and a 2.6 kernel (gentoo-dev-sources) is even easier than a
2.4 (gentoo-sources) kernel.

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?

"Sybren Stuvel" <sybrenUSE@YOURthirdtower.imagination.com> wrote in message
news:slrncj418f.kk0.sybrenUSE@sybren.thirdtower.co m...
> Matthew Martin enlightened us with:
> > I forgot to let you know I'm a newbie.
>
> In that case: please don't top-post. Remove the quoted text that you
> do not directly refer to, and post your reaction below that, just as I
> did now.
>
> > Could you translate that a little. I know about chroot. but
> > dropping the kernel I assume you talking about.
>
> No, he said:
>
> >> Sounds like another genkernel screwup ... I say drop it
>
> Which means dropping genkernel.
>
> >> and do the make menuconfig yourself. Avoiding the use of an initrd
> >> eliminates one point
>
> Which means do the kernel configuration & building yourself. Easy
> enough, and a 2.6 kernel (gentoo-dev-sources) is even easier than a
> 2.4 (gentoo-sources) kernel.
>

OK I chose to do the 2.6 Kernel Manualy. What is the diference between *
built-in and M module


> 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?

Sybren Stuvel wrote:
> Matthew Martin enlightened us with:
>
>>>Sounds like another genkernel screwup ... I say drop it
>
>
> Which means dropping genkernel.

I've used genkernel since forever, and always Gentoo-testing, never-ever
had any problem. genkernel rocks!

>
>
>>>and do the make menuconfig yourself. Avoiding the use of an initrd
>>>eliminates one point

It is my humble opinion that you should check the ramdisk support.
(Device Drivers -> Block Devices -> RAM disk support + Initial RAM disk
(initrd) support)

/Hazze

Matthew Martin wrote:

>
> OK I chose to do the 2.6 Kernel Manualy. What is the diference between *
> built-in and M module
>

Module = loaded from disk when needed.
built-in = usable from beginning of boot.
(not really true, but anyway...)
Choose RAM disk support built-in, running genkernel ... :-)

/Hazze

Matthew Martin wrote:

> OK I chose to do the 2.6 Kernel Manualy. What is the diference
> between * built-in and M module

Well, one is hard-coded into the kernel, while the other can be loaded
(and unloaded, if so configured) at run-time. Things like the file
systems you use to boot from should be compiled in, while the ALSA
drivers all seem to work smoother when compiled as modules.

If you check the install docs on gentoo.org, you'll find what basic
options *must* be compiled in to make the kernel work with Gentoo.

--
PeKaJe
Sit back and watch the messages. This is actually more important than one
might think as there is a bug in GNU Mach whereby hitting a key during the
boot process causes the kernel to panic -- GNU Hurd Installation Guide

Well I manualy configed linux-2.6.8-gentoo-r2 and still stoped at:

RAMDISK: Compressed image found at block 0

Any ideas I'm going to try this again but I'm going to remove any thing to
do with the gentoo-sources kernel from my system.

Matthew Martin enlightened us with:
> OK I chose to do the 2.6 Kernel Manualy. What is the diference
> between * built-in and M module

Modules are parts of the kernel that are stored in files that live in
/lib/modules/<kernel version>/. They can be loaded on demand, and thus
prevent your kernel from taking up more memory than you need. It's
also easier to pass them options, etc.

You need some modules compiled into your kernel (*) instead of as an
external module. Think of this: if your harddisk has the XFS
filesystem, but you compiled XFS support as a module, your kernel
wouldn't be able to find the module in the first place to load XFS
support. See the problem? You also need to compile in support for your
IDE chipset, and some other things, for the same reason.

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?