Loading linux.EBDA too big
Jamey
setting up my desktop in gnome and then got tired and went to bed. When I
woke I up I saw this:
Loading linux.EBDA too big
LILO 21.7 boot:
My computer won't boot anymore and I can't even enter failsafe. There is
some info I would like to save but I am willing to start over if I have to.
I would just like to know what in the world could cause this error so it
doesn't happen again and if it is possible to recover from it. If it is
possible please explain this as you would a big huge n00b with know linux
lingo. You know like if you were telling your mom how to do it.
Thanks,
Jamey
Jamey
spi...@freenet.co.uk
1: WTF is a "noob"?
2: Get a boot disk (you DO have one, right?)
3: If not, then the other alternative is to use the CDROM to boot your
system, or, if that facility isn't available, go into rescue mode, mount the
root partition, and rerun lilo.
Tony Lawrence
>
> Jamey <ja...@eyeris.org> wrote:
> > Can anyone help me here or am I screwed. I am a linux n00b big time. I was
> > setting up my desktop in gnome and then got tired and went to bed. When I
> > woke I up I saw this:
>
> > Loading linux.EBDA too big
> > LILO 21.7 boot:
>
> > My computer won't boot anymore and I can't even enter failsafe. There is
> > some info I would like to save but I am willing to start over if I have to.
> > I would just like to know what in the world could cause this error so it
> > doesn't happen again and if it is possible to recover from it. If it is
> > possible please explain this as you would a big huge n00b with know linux
> > lingo. You know like if you were telling your mom how to do it.
>
> 1: WTF is a "noob"?
Newbie.
> 2: Get a boot disk (you DO have one, right?)
> 3: If not, then the other alternative is to use the CDROM to boot your
> system, or, if that facility isn't available, go into rescue mode, mount the
> root partition, and rerun lilo.
If it helps, I had to do this on my RH7.1 just yesterday. I booted with
the cd, and did "linux rescue". That automatically mounts all the file
systems under /mnt/sysimage. I then did:
lilo -r /mnt/sysimage
sync
sync
and unmounted each file system, working backward:
umount /mnt/sysimage/proc
umount/mnt/sysimage/var
etc. to
umount /mnt/sysimage
and finally exited the shell (' exit or ctrl-d) , removed the cd and
rebooted.
BTW, what did me in was adding a new scsi device and "not quite" getting
the cable seated corrected :-)
--
Tony Lawrence
SCO/Linux Support Tips, How-To's, Tests and more: http://pcunix.com
Jamey
getting is preventing me from booting. I see:
Loading linux.EBDA too big
..
LILO 21.7 boot:
I can useing the mandrake disk type rescue and get to a prompt. I can mount
/dev/hda5 /mnt/disk but I can not get the computer to boot. I was told that
I needed to rerun LILO but how do I do that without haveing my linux
partition as the / dir. When I try to run LILO I get /etc/lilo.conf not
there and so I copy it over and then it asks for another file and such. So
is there a way 1. to boot so that my linux partition is the root dir. 2. to
run lilo without it being in the /etc dir. 3. some other way to fix this
problem?
Thanks for any help you can give me this is very frustrating.
Tauno Voipio
"Jamey" <ja...@eyeris.org> wrote in message
news:doHv7.1881$iL5....@typhoon1.gnilink.net...
> Ok I posted before but I didn't get the help I need. This error I am
> getting is preventing me from booting. I see:
>
> Loading linux.EBDA too big
> ..
> LILO 21.7 boot:
>
> I can useing the mandrake disk type rescue and get to a prompt. I can
mount
> /dev/hda5 /mnt/disk but I can not get the computer to boot. I was told
that
> I needed to rerun LILO but how do I do that without haveing my linux
> partition as the / dir. When I try to run LILO I get /etc/lilo.conf not
> there and so I copy it over and then it asks for another file and such.
So
> is there a way
> 1. to boot so that my linux partition is the root dir.
Have you tried
linux root=/dev/hda5
for your rescue system?
> 2. to run lilo without it being in the /etc dir.
There is a switch to re-direct the configuration file. It needs to be
edited, though, to show the real location of the kernel to boot
> 3. some other way to fix this problem?
Copy your kernel from /boot to a floppy, set the master device using rdev.
For more information, get the Bootdisk-HOWTO from Linux Documentation
Project.
Tauno Voipio
tauno voipio @ iki fi
spi...@freenet.co.uk
>> 1: WTF is a "noob"?
> Newbie.
Yeh, it twigged a little later, but I refuse to speak in leet...
:)