Mumia W. wrote:
> On 08/06/2006 11:25 PM, ~David~ wrote:
>> [...] If possible, it would be nice
>> to not have an intitrd.img.
>>
>> I have compiled kernels before on this system and other systems for
>> different linux distros (gentoo, fedora, ubuntu and others) but
>> debains way of booting seems non-typical, and I want to stay as close
>> to the normal way (not "Debian way") as I can. What is there another
>> kernel option I need or something I need to do to get this kernel to
>> boot?
>> [...]
>
> You'll need to compile some things directly into the kernel, such as
> IDE/SATA support, filesystem support (ext2/3fs or reiserfs) and anything
> else needed for booting.
Everything needed (I think, based on previous experience) from filesystem to IDE
and CDROM to various other hardware in the systems is compiled in.

David
>
> [ Followups set to alt.os.linux.debian ]
>

On 08/07/2006 08:29 PM, ~David~ wrote:
> Mumia W. wrote:
>> You'll need to compile some things directly into the kernel, such as
>> IDE/SATA support, filesystem support (ext2/3fs or reiserfs) and anything
>> else needed for booting.
> Everything needed (I think, based on previous experience) from filesystem to IDE
> and CDROM to various other hardware in the systems is compiled in.
>

Compiled in how--as modules or /directly/ into the kernel?
Everything needed to boot must be compiled directly into the
kernel (use "Y", not "M" when selecting).

Boot into the default kernel (2.6.8 ?) and do an /sbin/lsmod
to list the modules loaded. That list might give you hints of
what else you need to have compiled into the kernel in order
to boot.

Also, make sure you're trying to boot the right device. Most
probably the current value (/dev/hda1) is correct, but check
anyway if you can.

The initrd utility for Sarge probably won't work with 2.6.17,
so, unless you want to create your own initrd from scratch
(hard), you don't want an initrd.

Mumia W. wrote:
> On 08/07/2006 08:29 PM, ~David~ wrote:
>> Mumia W. wrote:
>>> You'll need to compile some things directly into the kernel, such as
>>> IDE/SATA support, filesystem support (ext2/3fs or reiserfs) and
>>> anything else needed for booting.
>> Everything needed (I think, based on previous experience) from
>> filesystem to IDE and CDROM to various other hardware in the systems
>> is compiled in.
>>
>
> Compiled in how--as modules or /directly/ into the kernel? Everything
> needed to boot must be compiled directly into the kernel (use "Y", not
> "M" when selecting).

Compiled in directly - I try to use modules as little as possible.

> Boot into the default kernel (2.6.8 ?) and do an /sbin/lsmod to list the
> modules loaded. That list might give you hints of what else you need to
> have compiled into the kernel in order to boot.
Thanks for the tip, the standard deb kernel seems to have a lot of modules in it.

> Also, make sure you're trying to boot the right device. Most probably
> the current value (/dev/hda1) is correct, but check anyway if you can.
Checked that a million times... It's correct.

> The initrd utility for Sarge probably won't work with 2.6.17, so, unless
> you want to create your own initrd from scratch (hard), you don't want
> an initrd.
I used the command mkinitrd -o /boot/image_name.img which made an image file,
though how can I tell if it is linked to the correct kernel sources, 2.6.17.7,
instead of the default 2.6.8?

Thanks for the tips, I'll try compiling more options in that the default kernel
uses directly,
David

On 08/08/2006 09:36 AM, ~David~ wrote:
>
> Mumia W. wrote:
>> On 08/07/2006 08:29 PM, ~David~ wrote:
>>> Mumia W. wrote:
>>>> You'll need to compile some things directly into the kernel, such as
>>>> IDE/SATA support, filesystem support (ext2/3fs or reiserfs) and
>>>> anything else needed for booting.
>>> Everything needed (I think, based on previous experience) from
>>> filesystem to IDE and CDROM to various other hardware in the systems
>>> is compiled in.
>>>
>> Compiled in how--as modules or /directly/ into the kernel? Everything
>> needed to boot must be compiled directly into the kernel (use "Y", not
>> "M" when selecting).
>
> Compiled in directly - I try to use modules as little as possible.
>
>> Boot into the default kernel (2.6.8 ?) and do an /sbin/lsmod to list the
>> modules loaded. That list might give you hints of what else you need to
>> have compiled into the kernel in order to boot.
> Thanks for the tip, the standard deb kernel seems to have a lot of modules in it.
>
>> Also, make sure you're trying to boot the right device. Most probably
>> the current value (/dev/hda1) is correct, but check anyway if you can.
> Checked that a million times... It's correct.
>
>> The initrd utility for Sarge probably won't work with 2.6.17, so, unless
>> you want to create your own initrd from scratch (hard), you don't want
>> an initrd.
> I used the command mkinitrd -o /boot/image_name.img which made an image file,
> though how can I tell if it is linked to the correct kernel sources, 2.6.17.7,
> instead of the default 2.6.8?
>

I don't know for sure. I avoid using an initrd; however, the
man-page of mkinitrd says that by default, mkinitrd constructs
an image that uses the modules for your current kernel version.

For you, what this means is that /boot/image_name.img contains
modules for linux 2.6.8 rather than for 2.6.17; this would
certainly explain the boot failure.

I suspect you need to do this:

mkinitrd -o /boot/image_name.img 2.6.17.7

> Thanks for the tips, I'll try compiling more options in that the default kernel
> uses directly,
> David