Yep. I updated the kernel through the Mandrake wizard and it burped
until the machine was booted. Anyway, thanks for the clues Braian and
BillK! It is up and running again! By the way when I run the boot CD and
going to the process of the expert mode choosing the update I got the
error "fsck failed with exit code 4 or signal 0" when it reaches the
security check. I tried to run a series of switches in the LILO in
rescue mode to rebuild the device and I didn't work telling me
"Fatal:open /boot/vmlinuz: no such file or directory". I looked into the
"/boot" and I had to rebuild the symbolic link pointing to the right
file for the vmlinuz file and that was it. It worked charmy.
Thanks folks
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of William Kenworthy
Sent: Monday, February 18, 2002 5:23 PM
To: Mandrake Expert
Subject: Re: [expert] LILO Problem - Loading Linux EBDA too big
To add a bit more: when you changed the kernel, lilo is trying to load
the kernel using the old boot info and what the obtuse error message is
saying is that it doesnt match what it thinks it should be loading. The
cure is to read "man lilo" and use the chroot option to to write the new
kernel information to the boot sector whilst mounted in rescue mode.
BillK
On Tue, 2002-02-19 at 09:04, Brian Parish wrote:
> Have you upgraded the kernel by any chance? This is usually the
> scenario that causes this. Anyway, the easiest way out is to boot
> from the install CD, choose expert mode, choose update, choose no
> packages to install, then just run through a standard install (very
> quickly). This should straighten on the chaos in your /boot and get
> you running again.
>
> If it was a kernel upgrade that caused it, note for the future that
> even though the kernel appears in the security updates list, it should
> NEVER be installed that way. Instead, download it and do "rpm -ivh
> kernel..." so that it gets installed alongside your existing kernel.
>
> HTH
> Brian
>
> On Tue, 2002-02-19 at 11:34, Jorge A. Pichardo wrote:
> > Hi all,
> >
> > I posted my problem in the newbies group and didn't get no answer
> > yet. So I posted it here. For some reason this morning appeared a
> > message in my linux box: "Loading Linux EBDA too big" and the system
> > halts. It is the same everytime I boot it.
> >
> > I tried to rescue it with the mandrake install CD and tried "chroot
> > /mnt" and all my directory structure seems ok (boot, dev, home,...)
> > now in "/" then I tried to mount /boot but I had this error "can't
> > find boot in /etc/fstab or /etc/mtab" I looked into those files and
> > I saw nothing about the "/boot" and I can't get it booted yet. I
> > read somewhere else that I need to remount the /boot and run "sync"
> > a couple of times followed by a lilo -v -v as commands. But I have
> > no luck yet.
> >
> > At this point I don't know how to proceed. Any thoughts,
> > recommendations
> >
> > Regards,
> > Jorge Pichardo
> >
> > Victoria - Vancouver British Columbia, Canada
> > Tel: +250-370-5250
> >
> >
> >
> >
> >
> >
> >
>
> > Want to buy your Pack or Services from MandrakeSoft?
> > Go to http://www.mandrakestore.com
>
>
>
>
>
> This message has been 'sanitized'. This means that potentially
> dangerous content has been rewritten or removed. The following log
> describes which actions were taken.
>
> Sanitizer (start="1014081124"):
> Part (pos="2727"):
> SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
> Match (rule="2"):
> Enforced policy: accept
>
> Part (pos="4603"):
> SanitizeFile (filename="message.footer", mimetype="text/plain"):
> Match (rule="default"):
> Enforced policy: defang
>
> Replaced mime type with: application/DEFANGED-8988
> Replaced file name with: message_footer.DEFANGED-8988
>
> Total modifications so far: 1
>
>
> Anomy 0.0.0 : Sanitizer.pm
> $Id: Sanitizer.pm,v 1.32 2001/10/11 19:27:15 bre Exp $
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
