Re: Kernel 2.4, 8 megs of ram and kernel panic

2002-02-17 Thread dman
On Sat, Feb 16, 2002 at 10:12:48PM -0600, Adam Majer wrote:
| On Sat, Feb 16, 2002 at 11:14:36PM +0100, Gr?gory Kar?kinian wrote:
| > Hello,
| > 
| > Thank you guys, that's exactly the answer i needed :). I can't compile a
| > kernel on this machine (it's a 486 @ 66 mhz.. Slow even to untar :p).
| > I'll keep my 2.2 for now.
| 
| You _can_ build it - it takes about 2-4h depending on options you choose. :)

or build it on a faster machine and copy the binary over.

-D

-- 

"Don't use C;  In my opinion,  C is a library programming language
 not an app programming language."  - Owen Taylor (GTK+ developer)



Re: Kernel 2.4, 8 megs of ram and kernel panic

2002-02-16 Thread Adam Majer
On Sat, Feb 16, 2002 at 11:14:36PM +0100, Gr?gory Kar?kinian wrote:
> Hello,
> 
> Thank you guys, that's exactly the answer i needed :). I can't compile a
> kernel on this machine (it's a 486 @ 66 mhz.. Slow even to untar :p).
> I'll keep my 2.2 for now.

You _can_ build it - it takes about 2-4h depending on options you choose. :)

- Adam



Re: Kernel 2.4, 8 megs of ram and kernel panic

2002-02-16 Thread Wayne Topa
Grégory Karékinian([EMAIL PROTECTED]) is reported to have said:
> Hi,
> 
> I've been searching on google but found no way to boot a 2.4 kernel
> without initrd. I indeed don't have any scsi hdd, so i don't think i
> need it.
What?

I have been booting 2.4.x kernels for months now, without initrd, on 3
boxen with IDE drives.
> 
> Any help appreciated, thanks in advance.

I used a stock kernel from kernel.org.  Running 2.4.17 curently.  No
different than the way 2.2.x kernels were made.  Don't make the ext2/3
filesystems as modules, which you 'could' do 'if' you were using
initrd.

I must have missed something in this thread or don't really understand
your problem.
-- 
Computers are like air-conditioners: both stop working, if you open
windows.
___



RE: Kernel 2.4, 8 megs of ram and kernel panic

2002-02-16 Thread Grégory Karékinian
Hello,

Thank you guys, that's exactly the answer i needed :). I can't compile a
kernel on this machine (it's a 486 @ 66 mhz.. Slow even to untar :p).
I'll keep my 2.2 for now.

Later.


> -Original Message-
> From: Martin Wuertele [mailto:[EMAIL PROTECTED] 
> Sent: samedi 16 février 2002 22:03
> To: debian-user@lists.debian.org
> Subject: Re: Kernel 2.4, 8 megs of ram and kernel panic
> 
> [...]
> works just as with 2.2 or 2.0. configure the kernel without initrd
> support, compile it with make-kpkg, install it with dpkg, run lilo and
> reboot.
> [...]
> 
> yours martin

> -Original Message-
> From: D-Man [mailto:[EMAIL PROTECTED] On Behalf Of dman
> Sent: samedi 16 février 2002 21:54
> To: debian-user@lists.debian.org
> Subject: Re: Kernel 2.4, 8 megs of ram and kernel panic
> 
[...]
> Look at the config file for your kernel -- is CONFIG_BLK_DEV_INITRD
> set to 'y'?  If it is, then you need an initrd.  The debian-packaged
> kernels have this option set.  My kernel doesn't, so I don't need (in
> fact, can't use) an initrd.



Re: Kernel 2.4, 8 megs of ram and kernel panic

2002-02-16 Thread Martin Wuertele
Hi Grégory!

On Sat, 16 Feb 2002, Grégory Karékinian wrote:

> I've been searching on google but found no way to boot a 2.4 kernel
> without initrd. I indeed don't have any scsi hdd, so i don't think i
> need it.
 
works just as with 2.2 or 2.0. configure the kernel without initrd
support, compile it with make-kpkg, install it with dpkg, run lilo and
reboot.

i have 2.4.9-xfs on my portable and 2.4.17-lvm1.0.2 on my workstation
running without initrd.

yours martin
-- 
<[EMAIL PROTECTED]> -- NO HTML MAILS PLEASE
 PGP/GPG encrypted and signed messages preferred


pgp6GgNkn4nBU.pgp
Description: PGP signature


Re: Kernel 2.4, 8 megs of ram and kernel panic

2002-02-16 Thread dman
On Sat, Feb 16, 2002 at 09:23:30PM +0100, Grégory Karékinian wrote:
| Hi,
| 
| I've been searching on google but found no way to boot a 2.4 kernel
| without initrd.

This is a snippet of the kernel configuration documentation :

~
Initial RAM disk (initrd) support
CONFIG_BLK_DEV_INITRD
  The initial RAM disk is a RAM disk that is loaded by the boot loader
  (loadlin or lilo) and that is mounted as root before the normal boot
  procedure. It is typically used to load modules needed to mount the
  "real" root file system, etc. See 
  for details.
~

Look at the config file for your kernel -- is CONFIG_BLK_DEV_INITRD
set to 'y'?  If it is, then you need an initrd.  The debian-packaged
kernels have this option set.  My kernel doesn't, so I don't need (in
fact, can't use) an initrd.

-D

-- 

A wise servant will rule over a disgraceful son,
and will share the inheritance as one of the brothers.
Proverbs 17:2



RE: Kernel 2.4, 8 megs of ram and kernel panic

2002-02-16 Thread Grégory Karékinian
Hi,

I've been searching on google but found no way to boot a 2.4 kernel
without initrd. I indeed don't have any scsi hdd, so i don't think i
need it.

Any help appreciated, thanks in advance.

> -Original Message-
> From: Hans Ekbrand [mailto:[EMAIL PROTECTED] 
> Sent: samedi 16 février 2002 21:13
> To: debian-user@lists.debian.org
> Subject: Re: Kernel 2.4, 8 megs of ram and kernel panic
> 
> 
[...]
> 
> Do you really need to boot through initrd? A customized 2.4 
> kernel that
> does not depend on initrd, should have no problems at all 
> with 8 Mb, and
> if you will go through and customize, then why not to do it as simple
> as possible?
> 
> I might have missunderstood the uses of initrd, but I thought it was
> most useful for general setups where hardware is unknown and 
> other media
> is not (easily) accessible, e.g new installations or booting 
> over the network.
> 



Re: Kernel 2.4, 8 megs of ram and kernel panic

2002-02-16 Thread Hans Ekbrand
On Sat, Feb 16, 2002 at 07:40:53PM +1100, Herbert Xu wrote:
> Gr?gory Kar?kinian <[EMAIL PROTECTED]> wrote:
> 
> > I understand the reason of this error (only 8 megs of ram on this
> > computer, but is is possible to boot a 2.4 kernel with 8 megs ?
> > (Making a smaller ramdisk ? Been searching on google, found out it's 4
> > megs by defaut... That's a lot).
> 
> Yes, but you'll need to setup a custom initrd image.  Please refer to
> mkinitrd.conf(5) for details.

Do you really need to boot through initrd? A customized 2.4 kernel that
does not depend on initrd, should have no problems at all with 8 Mb, and
if you will go through and customize, then why not to do it as simple
as possible?

I might have missunderstood the uses of initrd, but I thought it was
most useful for general setups where hardware is unknown and other media
is not (easily) accessible, e.g new installations or booting over the network.


pgpT1xPoRDznV.pgp
Description: PGP signature


Re: Kernel 2.4, 8 megs of ram and kernel panic

2002-02-16 Thread Herbert Xu
Gr?gory Kar?kinian <[EMAIL PROTECTED]> wrote:

> I understand the reason of this error (only 8 megs of ram on this
> computer, but is is possible to boot a 2.4 kernel with 8 megs ?
> (Making a smaller ramdisk ? Been searching on google, found out it's 4
> megs by defaut... That's a lot).

Yes, but you'll need to setup a custom initrd image.  Please refer to
mkinitrd.conf(5) for details.
-- 
Debian GNU/Linux 2.2 is out! ( http://www.debian.org/ )
Email:  Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt



Kernel 2.4, 8 megs of ram and kernel panic

2002-02-15 Thread Grégory Karékinian
Hi,

I just installed a 2.4 kernel image on my woody box (binutils asked to
upgrade the kernel due to linking failure...), Everything went fine
until the beginning of the boot process (lilo well configured, of
course).
I get the following error :

RAMDISK: Loading 3204 blocks [1 disk] into ram disk... <0>Kernel panic:
Out of memory and no killable processes...


I understand the reason of this error (only 8 megs of ram on this
computer, but is is possible to boot a 2.4 kernel with 8 megs ?
(Making a smaller ramdisk ? Been searching on google, found out it's 4
megs by defaut... That's a lot).

Thanks in advance if you can help, else i'll just keep using 2.2... :)

Later.