On Tue, 2002-02-19 at 12:45, Jorge A. Pichardo wrote:
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
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
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
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
Hello All,
How are you doing today? Good I hope.
I have an interesting problem with my Lilo that I hope someone might have a
solution for.
I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have an
UltraDMA 66 drive installed and is accessible as well. Currently my Mandrake 7.2
I'm wondering if you might have to do some drive mapping. My windows install
is on hdb, so to get it to boot, I do:
other=/dev/hdb1
label=windows
table=/dev/hdb
map-drive=0x80
to=0x81
map-drive=0x81
to=0x80
This is just a guess, but maybe
On Mon, 13 Aug 2001, Lonnie Cumberland wrote:
Hello All,
How are you doing today? Good I hope.
I have an interesting problem with my Lilo that I hope someone might have a
solution for.
I have Mandrake 7.2 booting from my /dev/sda SCSI drive and also have an
UltraDMA 66 drive installed
Hello,
I can select the proper image to boot in the LILO selections, but the problem is
that the incorrect vmlinuz is being booted. The vmlinuz pointed to on the
SCSI /dev/sda5 is being booted instead of the vmlinuz pointed to on the
/dev/hde6 UltraDMA 66 controller.
The correct root filesystem
Ok, you have /boot/vmlinuz as the image for both kernels. You should
have the two different images listed separately.
Try putting a different image e.g.
image=/boot/vmlinuz-new
in your /etc/lilo.conf file
where /boot/vmlinuz-new is a link to your new kernel image.
-sen
On Mon, 13 Aug
--- Lonnie Cumberland [EMAIL PROTECTED] wrote:
lilo.conf
---
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
vga=normal
default=linux
keytable=/boot/us.klt
lba32
prompt
timeout=50
message=/boot/message
[EMAIL PROTECTED] wrote:
I just istalled LM7.2 on my new drive (20GB). It's got a 13GB Win98
partition and the rest for LM7.2. The install goes fine, but LILO doesn't
install. I tried with every distro I own and the same thing happens, LILO
refuses to install. In order to get the thing to
I just istalled LM7.2 on my new drive (20GB). It's got a 13GB Win98
partition and the rest for LM7.2. The install goes fine, but LILO doesn't
install. I tried with every distro I own and the same thing happens, LILO
refuses to install. In order to get the thing to boot, I installed FreeBSD
4.0,
I believe Windows likes to be the first partition on
the drive, and then you have to set LILO to the MBR
(master boot record). I think FreeBSD defaults it's
loader to the master boot record as well.
--- [EMAIL PROTECTED] wrote:
I just istalled LM7.2 on my new drive (20GB). It's
got a 13GB
hi !
my lilo does not work anymore
how do i restore the fd0 to the lilo ?
is there a short way to do that ?
please help !!
I'm only guessing what you are asking here . . .
If you mean that your LILO on the hard disk went away,
but you can still boot from floppy, then . . .
Just boot from floppy, the log in as root, and run lilo, by typing
lilo
.
If you mean somthihng else, please ask the question more
On Mon, 17 Apr 2000, Kirk McElhearn wrote:
I just tried something - I have a Mandrake boot floppy, and I figured
that maybe I could just copy it and change some config in the floppy to
get the other distro to boot. But when trying to access the floppy, I
get a message Could not list
On 16/04/00 23:11, Andrew George [EMAIL PROTECTED] is reported to
have said:
/boot/vmlinuz is a symlink to the real kernel file, I noticed both your linux
distributons in LILO.conf pointed to it so I was wondering if the symlink had
been removed somehow so lilo didn't know where to find the
I'm really getting fed up with this problem. So many people said it was
so easy to use a big HD and boot more than one distribution, I wish there
were some way to figure out why it won't work for me
I just tried something - I have a Mandrake boot floppy, and I figured
that maybe I could
Kirk McElhearn wrote:
I'm really getting fed up with this problem. So many people said it was
so easy to use a big HD and boot more than one distribution, I wish there
were some way to figure out why it won't work for me
I just tried something - I have a Mandrake boot floppy, and I
Kirk McElhearn wrote:
On 16/04/00 23:11, Andrew George [EMAIL PROTECTED] is reported to
have said:
/boot/vmlinuz is a symlink to the real kernel file, I noticed both your linux
distributons in LILO.conf pointed to it so I was wondering if the symlink had
been removed somehow so lilo didn't
Marcos Dione wrote:
On Fri, 14 Apr 2000, Mike Corbeil wrote:
Lastly, this is truly a newbie question and should be asked in the newbie
mailing list.
don't mean to start a flamewar here... but don't try to
discriminate... I mean, I don't think he's a newbie if he's trying to boot
On 15/04/00 0:28, Marcos Dione [EMAIL PROTECTED] is reported to
have said:
Lastly, this is truly a newbie question and should be asked in the newbie
mailing list.
don't mean to start a flamewar here... but don't try to
discriminate... I mean, I don't think he's a newbie if he's trying
On 14/04/00 19:45, Stephen F. Bosch [EMAIL PROTECTED] is reported to
have said:
OK, I have finally managed to get two distributions installed, and to get
lilo to work. But when I try to tweek the lilo.conf, I get a message
that each of my choices is added, but then it says No images have
Kirk McElhearn wrote:
Actually, I figured this question would not get many answers on the
newbie list...
You may be correct, but it would be useful to other newbies, because many or
all newbies will need deal with that kind of question. On the other hand,
asking in the expert mailing list
Kirk McElhearn wrote:
On 14/04/00 19:45, Stephen F. Bosch [EMAIL PROTECTED] is reported to
have said:
OK, I have finally managed to get two distributions installed, and to get
lilo to work. But when I try to tweek the lilo.conf, I get a message
that each of my choices is added, but
On 15/04/00 19:54, Mike Corbeil [EMAIL PROTECTED] is reported to
have said:
Show us your /etc/lilo.conf, man.
boot = /dev/fd0
If you want your changes to go to the mbr, then the above line must be
changed
to /dev/hda, which is where the mbr is located.
The way you have it, it'ld used
On Sun, 16 Apr 2000, Kirk McElhearn wrote:
On 14/04/00 19:45, Stephen F. Bosch [EMAIL PROTECTED] is reported to
have said:
OK, I have finally managed to get two distributions installed, and to get
lilo to work. But when I try to tweek the lilo.conf, I get a message
that each of my
OK, I have finally managed to get two distributions installed, and to get
lilo to work. But when I try to tweek the lilo.conf, I get a message
that each of my choices is added, but then it says No images have been
defined. It does not update my changes in the mbr. What could I be
doing
Kirk McElhearn wrote:
OK, I have finally managed to get two distributions installed, and to get
lilo to work. But when I try to tweek the lilo.conf, I get a message
that each of my choices is added, but then it says No images have been
defined. It does not update my changes in the mbr.
Kirk McElhearn wrote:
OK, I have finally managed to get two distributions installed, and to get
lilo to work. But when I try to tweek the lilo.conf, I get a message
that each of my choices is added, but then it says No images have been
defined. It does not update my changes in the mbr.
On Fri, 14 Apr 2000, Mike Corbeil wrote:
Lastly, this is truly a newbie question and should be asked in the newbie
mailing list.
don't mean to start a flamewar here... but don't try to
discriminate... I mean, I don't think he's a newbie if he's trying to boot
another kernel. I think a
Tom Berkley wrote:
Larry
Suspect a lilo.conf line length limitation. Try using the \ character at
the end of a line
and continue the append command on the following line. Make absolute
certain that no spaces follow the \ character or is will not escape the
newline character.
Tom
Sorry
Hello,
As my linux won't recognize my 128M RAM
I'm trying to put append="mem=128M" in my
lilo.conf. But when I type lilo to update the config
I get the following message:
Added li
Added win
Added floppy
No images have been defined.
HERE IS MY LILO.CONF
boot=/dev/hde
map=/boot/map
Fabrice SERVANT wrote:
Hello,
As my linux won't recognize my 128M RAM
I'm trying to put append="mem=128M" in my
lilo.conf. But when I type lilo to update the config
I get the following message:
Added li
Added win
Added floppy
No images have been defined.
HERE IS MY LILO.CONF
Fabrice SERVANT wrote:
Hello,
As my linux won't recognize my 128M RAM
I'm trying to put append="mem=128M" in my
lilo.conf. But when I type lilo to update the config
I get the following message:
Added li
Added win
Added floppy
No images have been defined.
HERE IS MY LILO.CONF
win instead of windows
That was my mistake
Thanks
Fabrice
U allways need someone to look after you, so do I
__
Get Your Private, Free Email at http://www.hotmail.com
Fabrice SERVANT wrote:
Hello,
As my linux won't recognize my 128M RAM
I'm trying to put append="mem=128M" in my
lilo.conf. But when I type lilo to update the config
I get the following message:
Added li
Added win
Added floppy
No images have been defined.
HERE IS MY LILO.CONF
In append major items are separated with spaces and minor (within an
option) items are separated with commas. Not sure if this is a
convention for viewing or if lilo actually pays attention to this. But
it works, notheless.
Tom
Larry Sword wrote:
Fabrice SERVANT wrote:
Hello,
As my
On Sun, 09 Apr 2000, you wrote:
Hello,
As my linux won't recognize my 128M RAM
I'm trying to put append="mem=128M" in my
lilo.conf. But when I type lilo to update the config
I get the following message:
HmmFirst of all, does that first image (/boot/vmlinuz-2.2.14-15mdk) exist
in the
Tom Berkley wrote:
In append major items are separated with spaces and minor (within an
option) items are separated with commas. Not sure if this is a
convention for viewing or if lilo actually pays attention to this. But
it works, notheless.
Tom
Speaking of the append statement. I've run
Larry
Suspect a lilo.conf line length limitation. Try using the \ character at
the end of a line
and continue the append command on the following line. Make absolute
certain that no spaces follow the \ character or is will not escape the
newline character.
Tom
Larry Sword wrote:
Tom Berkley
Just to let everyone know...
I downloaded and built the lilo SRPM. It seems that on dual processor
systems that lilo can hang the kernel because it ends up overwriting
some of it's memory space. Lilo therefore needs to be compiled with
the LARGE_EDBA option.
Just thought that this
On Thu, 10 Jun 1999, Sheldon Lee Wen wrote:
It seems that on dual processor
systems that lilo can hang the kernel because it ends up overwriting
some of it's memory space. Lilo therefore needs to be compiled with
the LARGE_EDBA option.
Thanks - I've put a new lilo in the updates directory.
Hi,
I recompiled and installed my kernel. After rebooting lilo comes up as
normal. However, after I type in
linux I get the starting linux message and it hangs. I thought it may be my
kernel so I reinstalled the
rpm's for the old one and rebooted. Same problem. I can boot off of a boot
44 matches
Mail list logo
