Re: [expert] System freeze on kernel compilation

2002-02-04 Thread Steve Kieu


> 5. Run 'make modules_install && make install'.

I nerver did that, I just 'make modules_install' and
manually copy the bzImage file from arch/i386/boot to
/boot and manually modify lilo.conf. always work :-)


> 
> This process used to work perfectly, but now the
> process freezes my whole
> computer whenever I get to the /sbin/installkernel
> phase (part of 'make
> install'), and specifically when it gets to running
> mkinitrd. On a quick glance
> of the 'make install' process, I noticed a reference
> to zImage. This is strange
> because I used 'make bzImage', not 'make zImage'.
> After a hard reboot, the
> kernel looked as if it was mostly installed: there
> were modules in /lib/modules/
> and various files in /boot. The only file missing in
> /boot was an initrd image.
> As an experiment, I configured the new kernel in
> /etc/lilo.conf, but I got a
> "Kernel [name] is too big!" error whenever I tried
> to run LILO (as if I had used
> 'make zImage' instead of 'make bzImage').
> 
> -- 
> Sridhar Dhanapalan
> 
> "I feel that open, competitive markets, free thought
> and democracy all flourish
> only when we defend the medium itself as being
> independent. That may mean
> constraints that carriers cannot also supply
> software, that suppliers of generic
> software should be constrained from competing in
> markets which that software
> gives access to." -- Tim Berners-Lee, founder of the
> World Wide Web
> 
> > Want to buy your Pack or Services from
MandrakeSoft?
> 
> Go to http://www.mandrakestore.com
>  

=
S.KIEU

http://greetings.yahoo.com.au - Yahoo! Greetings
- Send your Valentines love online.



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [expert] System freeze on kernel compilation

2002-02-04 Thread Nguyen Hung Vu

Have you checked MUO site?


We have to reconfigure system:

http://www.mandrakeuser.org/docs/install/kupgrade3.html#conf

as well as  lilo or grub

http://www.mandrakeuser.org/docs/install/kupgrade3.html#lilo

good luck

Hung vu

>>This process used to work perfectly, but now the
>>process freezes my whole
>>computer whenever I get to the /sbin/installkernel
>>phase (part of 'make
>>install'), and specifically when it gets to running
>>mkinitrd. On a quick glance
>>of the 'make install' process, I noticed a reference
>>to zImage. This is strange
>>because I used 'make bzImage', not 'make zImage'.
>>After a hard reboot, the
>>kernel looked as if it was mostly installed: there
>>were modules in /lib/modules/
>>and various files in /boot. The only file missing in
>>/boot was an initrd image.
>>As an experiment, I configured the new kernel in
>>/etc/lilo.conf, but I got a
>>"Kernel [name] is too big!" error whenever I tried
>>to run LILO (as if I had used
>>'make zImage' instead of 'make bzImage').
>>
>>-- 
>>






Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [expert] System freeze on kernel compilation

2002-02-06 Thread Sridhar Dhanapalan

Thanks, that worked very well. I still have no idea why mkinitrd freezes my
computer, but it doesn't matter since I don't need an initrd image anyway :)

On Tue, 5 Feb 2002 15:18:18 +1100 (EST), Steve Kieu <[EMAIL PROTECTED]> wrote:
> 
> > 5. Run 'make modules_install && make install'.
> 
> I nerver did that, I just 'make modules_install' and
> manually copy the bzImage file from arch/i386/boot to
> /boot and manually modify lilo.conf. always work :-)
> 
> 
> > 
> > This process used to work perfectly, but now the
> > process freezes my whole
> > computer whenever I get to the /sbin/installkernel
> > phase (part of 'make
> > install'), and specifically when it gets to running
> > mkinitrd. On a quick glance
> > of the 'make install' process, I noticed a reference
> > to zImage. This is strange
> > because I used 'make bzImage', not 'make zImage'.
> > After a hard reboot, the
> > kernel looked as if it was mostly installed: there
> > were modules in /lib/modules/
> > and various files in /boot. The only file missing in
> > /boot was an initrd image.
> > As an experiment, I configured the new kernel in
> > /etc/lilo.conf, but I got a
> > "Kernel [name] is too big!" error whenever I tried
> > to run LILO (as if I had used
> > 'make zImage' instead of 'make bzImage').


-- 
Sridhar Dhanapalan

"Maybe somebody should tell gcc maintainers about programmers
that know more than the compiler again."
  -- Linus Torvalds



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [expert] System freeze on kernel compilation

2002-02-06 Thread Praedor Tempus

I may give that a shot myself (used to do it that way). 
I noticed that devfs seems to be REALLY broken now rather than just 
experimental and buggy.  I built the 2.4.17 kernel and created an initrd for 
it - and it works ONLY if I do the 'append= "devfs nomount"' deal in lilo.  
Change it to "devfs mount" and all hell breaks loose - well, nothing breaks 
loose, which is the problem.  Upon bootup there is a kernel panic and an 
inability to load the root filesystem, yadda, yadda.  Change it back to 
"devfs=nomount" and all is well again.  I'm wondering if flushing the 
initrd.img down the toilet and simply booting the kernel proper would allow 
it to bootup with devfs activated?  

I was trying this as one of many desperate means to get Alsa/sound working 
with my laptop.  It was a flimsy longshot but I was trying it and found the 
absolute impossibility of bootup at all with devfs activated (yes, it was 
selected in xconfig so the kernel "supports" it).

praedor

On Wednesday 06 February 2002 07:19 am, Sridhar Dhanapalan wrote:
> Thanks, that worked very well. I still have no idea why mkinitrd freezes my
> computer, but it doesn't matter since I don't need an initrd image anyway
> :)
>
> On Tue, 5 Feb 2002 15:18:18 +1100 (EST), Steve Kieu <[EMAIL PROTECTED]> 
wrote:
> > > 5. Run 'make modules_install && make install'.
> >
> > I nerver did that, I just 'make modules_install' and
> > manually copy the bzImage file from arch/i386/boot to
> > /boot and manually modify lilo.conf. always work :-)
> >
[...]



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [expert] System freeze on kernel compilation

2002-02-06 Thread Sridhar Dhanapalan

On Wed, 6 Feb 2002 08:12:05 -0700, Praedor Tempus <[EMAIL PROTECTED]> wrote:
> I may give that a shot myself (used to do it that way). 
> I noticed that devfs seems to be REALLY broken now rather than just 
> experimental and buggy.  I built the 2.4.17 kernel and created an initrd for 
> it - and it works ONLY if I do the 'append= "devfs nomount"' deal in lilo.  
> Change it to "devfs mount" and all hell breaks loose - well, nothing breaks 
> loose, which is the problem.  Upon bootup there is a kernel panic and an 
> inability to load the root filesystem, yadda, yadda.  Change it back to 
> "devfs=nomount" and all is well again.  I'm wondering if flushing the 
> initrd.img down the toilet and simply booting the kernel proper would allow 
> it to bootup with devfs activated?  

I have no devfs problems at all with my compiled 2.4.17-mjc3 kernel, so it may
help not using your initrd file. You can usually disable it loading in your boot
manager's config file (e.g. /etc/lilo.conf for LILO).

> I was trying this as one of many desperate means to get Alsa/sound working 
> with my laptop.  It was a flimsy longshot but I was trying it and found the 
> absolute impossibility of bootup at all with devfs activated (yes, it was 
> selected in xconfig so the kernel "supports" it).

It doesn't hurt to try...

> praedor
> 
> On Wednesday 06 February 2002 07:19 am, Sridhar Dhanapalan wrote:
> > Thanks, that worked very well. I still have no idea why mkinitrd freezes my
> > computer, but it doesn't matter since I don't need an initrd image anyway
> > :)
> >
> > On Tue, 5 Feb 2002 15:18:18 +1100 (EST), Steve Kieu <[EMAIL PROTECTED]> 
> wrote:
> > > > 5. Run 'make modules_install && make install'.
> > >
> > > I nerver did that, I just 'make modules_install' and
> > > manually copy the bzImage file from arch/i386/boot to
> > > /boot and manually modify lilo.conf. always work :-)
> > >
> [...]

-- 
Sridhar Dhanapalan

Windows - 32 bit extensions and a graphical shell
for a 16 bit patch to an 8 bit operating system
originally coded for a 4 bit microprocessor,
written by a 2 bit company
that can't stand 1 bit of competition!



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com