[Peeweelinux] kernel 2.4, panic on boot
[email protected]
[email protected]
Thu, 6 Jun 2002 09:36:51 +1000
I'll second that motion.. :)
Tom Genereaux
<entropy@sunflower To: [email protected]
.com> cc:
Sent by: Subject: Re: [Peeweelinux] kernel 2.4, panic on boot
peeweelinux-admin@
adis.on.ca Project:
05/06/2002 11:42
PM
Please respond to
peeweelinux
I for one am interested in such a how-to.
Tom
On Wed, 2002-06-05 at 18:22, Troy Engel wrote:
> FYI only -- building the 2.4 kernel with no modules (all internal) did
> the trick, my ext3 partition mounts, emlog loads, ppp/eth0 still work
> and everything.
>
> I had to build a whole bunch of stuff in a neato way for a 2.4 kernel
> that was uber easy to integrate -- if anyone is interested, gimme a
> holler and I'll cobble together a basic HowTo.
>
> -te
>
> Mark Meade wrote:
> > Hi Troy,
> >
> > Thanks for the embedded Java (Wonka) link.
> >
> > I've had 2.4.18 working with Peewee and a DiskOnChip Millennium,
although I
> > didn't use modprobe. I found it much easier to build everything I
needed
> > into the kernel, instead of using modules and/or initrd.
> >
> > Mark
> >
> > On Tuesday 04 June 2002 07:24 pm, Troy Engel wrote:
> >
> >>Has anyone gotten a 2.4 kernel to boot with peewee? I've built all
> >>sorts of custom packages with the new kernel (modutils, etc), but on
> >>boot I am getting an inability to mount the root partition:
> >
> >
> > _______________________________________________
> > Peeweelinux mailing list
> > [email protected]
> > http://mail.adis.on.ca/lists/listinfo/peeweelinux
>
>
> --
> Troy Engel, Systems Engineer
> Hockey. Kinda like Figure Skating in a War Zone.
>
> _______________________________________________
> Peeweelinux mailing list
> [email protected]
> http://mail.adis.on.ca/lists/listinfo/peeweelinux
>
_______________________________________________
Peeweelinux mailing list
[email protected]
http://mail.adis.on.ca/lists/listinfo/peeweelinux
*********************************************************************
This email message (and attachments) may contain information
that is confidential to Jupiters Technology. If you are not the
intended recipient you cannot use, distribute or copy the message
or attachments. In such a case, please notify the sender by return
email immediately and erase all copies of the message and
attachments. Opinions, conclusions and other information in this
message and attachments that do not relate to the official business
of Jupiters Technology are neither given nor endorsed by it.
*********************************************************************