[Peeweelinux] lilo.conf hangs
correy
[email protected]
Fri, 18 Jul 2003 12:06:24 +1000
--------------090001040005010207000400
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Hi there
Thanks for the information it is always good to know what is going on.
From what I gather the lilo.conf file is only in PWL for fun just
incase you use it later cause the one I originally had said stuff like
disk=/dev/sda which could never have worked since I have /dev/hdc so I
had to modify it but as from my first post I didn't modify it well
enough so now I have changed it from this -
__________________________
disk=/dev/hdc
bios=0x80
heads=4
sectors=32
cylinders=490
boot=/dev/hdc
map=/mnt/cf1/map
install=/mnt/cf1/boot.b
compact
prompt
timeout=20
default=linux
image=/mnt/cf1/vmlinuz
label=linux
initrd=/mnt/cf1/initrd
read-only
root=/dev/hdc2
vga=0x317
--------------------------------------------------
To This
________________________________
boot=/dev/hdc
disk=/dev/hdc
bios=0x80
linear
map=/mnt/cf1/map
install=/mnt/cf1/boot.b
prompt
timeout=50
initrd=/mnt/cf1/initrd
default=vmlinuz
image=/mnt/cf1/vmlinuz
label=vmlinuz
root=/dev/hdc2
# ramdisk=9312
read-only
image=/mnt/cf1/bzImage
label=bzImage
root=/dev/hdc2
read-only
--------------------------------------------
The important things are that I added initrd and got rid of a lot of
stuff that was causing grief I now have added another image.
I am having problem with the eepro100 drivers for my ethernet intel
82559ER and alsa drivers and so I am now compiling a 2.4.9 kernel
instead of the 2.2.17 kernel so that they can all be
satisfied......finergers crossed.
Correy
Barry Gershenfeld wrote:
>>I have been playing with lilo.conf to try another kernel image. I tried
>>the other image I made but it didn't work and then I tried to restore
>>the original one but it doesn't work so I am assuming it is a problem
>>with my lilo.conf file.
>>
>>
>
>It used to work? Did you install lilo this way when you got
>it to work? I am not familiar with installing from a chroot
>environment, nor do I use a CF disk, so while I would usually
>question entries in your lilo.conf file, they are probably
>right, if it used to work.
>
>So, which line(s) did you change?
>Or, what are you doing different?
>
>
>
>>I then run lilo and it says
>>Added linux *
>>
>>
>
>So lilo doesn't think you have any errors.
>
>
>
>>However after rebooting all I get is LI and the system hangs.
>>
>>
>
>This means that you did not get to load the kernel. That
>means you don't have to worry about
> -append arguments to the kernel
> -initrd
> -init
> -startup scripts
> -mounted drives
>because none of this will have happened yet.
>
>
>
>>also I don't really understand about
>>initrd and what script causes it to load into ram2?
>>
>>
>
>The kernel, after it is running, after it has detected processor
>and hardware, wants to mount a root file
>system to work from. This can be a ramdisk. From watching it
>boot, it is apparent the code for mounting a ramdisk and even
>the copying-to-it part are in the kernel.
>
>Up until this point the kernel is a single piece of code doing
>its thing. Once a root disk is mounted it (tries to) start init
>and from there inittab and all the other scripts start running
>and other processes can be created.
>
>
>More specifically, when you see "LI", code in the boot sector
>has executed, read what it thinks is the map file, loaded what
>it thinks is the kernel loader, and tried to jump to it.
>
>The most common problem is "geometry mismatch", which in a few
>words means that lilo (when you install it) has to be able
>to predict exactly what to feed the BIOS on boot up such
>that it will read the same device/sectors it found during
>the install.
>
>Well, you said "any help" :)
>
>Barry
>
>
>
>_______________________________________________
>Peeweelinux mailing list
>[email protected]
>http://mail.adis.on.ca/lists/listinfo/peeweelinux
>
>
>
>
--------------090001040005010207000400
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title></title>
</head>
<body>
Hi there<br>
Thanks for the information it is always good to know what is going on. From
what I gather the lilo.conf file is only in PWL for fun just incase you use
it later cause the one I originally had said stuff like disk=/dev/sda which
could never have worked since I have /dev/hdc so I had to modify it but as
from my first post I didn't modify it well enough so now I have changed it
from this - <br>
__________________________<br>
disk=/dev/hdc <br>
bios=0x80 <br>
heads=4 <br>
sectors=32 <br>
cylinders=490 <br>
<br>
boot=/dev/hdc <br>
map=/mnt/cf1/map <br>
install=/mnt/cf1/boot.b <br>
compact <br>
prompt <br>
timeout=20 <br>
default=linux <br>
<br>
image=/mnt/cf1/vmlinuz <br>
label=linux <br>
initrd=/mnt/cf1/initrd <br>
read-only <br>
root=/dev/hdc2 <br>
vga=0x317 <br>
--------------------------------------------------<br>
To This<br>
________________________________<br>
boot=/dev/hdc<br>
disk=/dev/hdc<br>
bios=0x80<br>
<br>
linear<br>
map=/mnt/cf1/map<br>
install=/mnt/cf1/boot.b<br>
prompt<br>
timeout=50<br>
initrd=/mnt/cf1/initrd<br>
default=vmlinuz<br>
<br>
image=/mnt/cf1/vmlinuz<br>
label=vmlinuz<br>
root=/dev/hdc2<br>
# ramdisk=9312<br>
read-only<br>
image=/mnt/cf1/bzImage<br>
label=bzImage<br>
root=/dev/hdc2<br>
read-only<br>
--------------------------------------------<br>
The important things are that I added initrd and got rid of a lot of stuff
that was causing grief I now have added another image.<br>
I am having problem with the eepro100 drivers for my ethernet intel 82559ER
and alsa drivers and so I am now compiling a 2.4.9 kernel instead of the
2.2.17 kernel so that they can all be satisfied......finergers crossed.<br>
<br>
Correy<br>
<br>
<br>
Barry Gershenfeld wrote:<br>
<blockquote type="cite"
cite="[email protected]">
<blockquote type="cite">
<pre wrap="">I have been playing with lilo.conf to try another kernel image. I tried
the other image I made but it didn't work and then I tried to restore
the original one but it doesn't work so I am assuming it is a problem
with my lilo.conf file.
</pre>
</blockquote>
<pre wrap=""><!---->
It used to work? Did you install lilo this way when you got
it to work? I am not familiar with installing from a chroot
environment, nor do I use a CF disk, so while I would usually
question entries in your lilo.conf file, they are probably
right, if it used to work.
So, which line(s) did you change?
Or, what are you doing different?
</pre>
<blockquote type="cite">
<pre wrap="">I then run lilo and it says
Added linux *
</pre>
</blockquote>
<pre wrap=""><!---->
So lilo doesn't think you have any errors.
</pre>
<blockquote type="cite">
<pre wrap="">However after rebooting all I get is LI and the system hangs.
</pre>
</blockquote>
<pre wrap=""><!---->
This means that you did not get to load the kernel. That
means you don't have to worry about
-append arguments to the kernel
-initrd
-init
-startup scripts
-mounted drives
because none of this will have happened yet.
</pre>
<blockquote type="cite">
<pre wrap="">also I don't really understand about
initrd and what script causes it to load into ram2?
</pre>
</blockquote>
<pre wrap=""><!---->
The kernel, after it is running, after it has detected processor
and hardware, wants to mount a root file
system to work from. This can be a ramdisk. From watching it
boot, it is apparent the code for mounting a ramdisk and even
the copying-to-it part are in the kernel.
Up until this point the kernel is a single piece of code doing
its thing. Once a root disk is mounted it (tries to) start init
and from there inittab and all the other scripts start running
and other processes can be created.
More specifically, when you see "LI", code in the boot sector
has executed, read what it thinks is the map file, loaded what
it thinks is the kernel loader, and tried to jump to it.
The most common problem is "geometry mismatch", which in a few
words means that lilo (when you install it) has to be able
to predict exactly what to feed the BIOS on boot up such
that it will read the same device/sectors it found during
the install.
Well, you said "any help" :)
Barry
_______________________________________________
Peeweelinux mailing list
<a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a>
<a class="moz-txt-link-freetext" href="http://mail.adis.on.ca/lists/listinfo/peeweelinux">http://mail.adis.on.ca/lists/listinfo/peeweelinux</a>
</pre>
</blockquote>
<br>
</body>
</html>
--------------090001040005010207000400--