Florian Ernst wrote:
MicheleM wrote:
all worked fine untill I rebooted the machine and...ooops! The boot
loader LILO failed with the LI code error.
[...]
But what did it happen? I think there is a bug somewhere.
lilo should have detected it needed to be re-run and should have
prompted
This topic may be a few days old, but this is apparently exactly what
happened to a server I admin remotely. When I upgraded to the new
stable packages, I saw nothing that affected the kernel, therefore
rerunning LILO didn't occur to me as something that needed to be done.
Hopefully someone
This topic may be a few days old, but this is apparently exactly what
happened to a server I admin remotely. When I upgraded to the new
stable packages, I saw nothing that affected the kernel, therefore
rerunning LILO didn't occur to me as something that needed to be done.
Hopefully someone
This topic may be a few days old, but this is apparently exactly what
happened to a server I admin remotely. When I upgraded to the new
stable packages, I saw nothing that affected the kernel, therefore
rerunning LILO didn't occur to me as something that needed to be done.
Hopefully someone
Hello again,
On Thu, Jun 09, 2005 at 02:54:32PM -0700, MicheleM wrote:
this is the output:
anjuna:~# grep -A5 'lilo/runme' /var/cache/debconf/config.dat
Name: lilo/runme
Template: lilo/runme
Owners: lilo
[...]
no more.
Hm, strange, to me it looks like this question was never asked. I
Hi there,
yesterday I tried to upgrade my Woody production server to Sarge after
reading and following step by step the relase notes under:
http://www.debian.org/releases/sarge/i386/release-notes/ch-upgrading.en.html
all worked fine untill I rebooted the machine and...ooops! The boot
loader LILO
Hello *,
On Thu, Jun 09, 2005 at 08:23:39AM -0700, MicheleM wrote:
yesterday I tried to upgrade my Woody production server to Sarge after
reading and following step by step the relase notes under:
http://www.debian.org/releases/sarge/i386/release-notes/ch-upgrading.en.html
all worked fine
On Thu, Jun 09, 2005 at 08:08:08PM +0200, Florian Ernst wrote:
Hello *,
all worked fine untill I rebooted the machine and...ooops! The boot
loader LILO failed with the LI code error.
No way to boot the machine. I solved the problem with a knoppix live
cd, I mounted the root
Hello *,
On Thu, Jun 09, 2005 at 04:46:32PM -0400, Roberto C. Sanchez wrote:
Why do people insist on using LILO? Just install grub, [...]
Advocacy is one thing, trying to find out why a bug has occurred
another. Let's try not to mix things up.
Cheers,
Flo
signature.asc
Description: Digital
Hi Flo,
this is the output:
anjuna:~# grep -A5 'lilo/runme' /var/cache/debconf/config.dat
Name: lilo/runme
Template: lilo/runme
Owners: lilo
Name: lilo/upgrade
Template: lilo/upgrade
Owners: lilo
I grep the upgrade's typescript searching for the lilo prompt but this
is what I found:
anjuna:~#
I partitioned my hard drive in such a way that i can
install 2 OS. The partition goes like this:
/dev/hda1 - Linux (ext3)- Bootable
/dev/hda5 - Linux Swap
/dev/hda3 - Linux (reiserfs)
/dev/hda1 has Knoppix3.3 (LiveOIO) and /dev/hda3 has
Knoppix 3.6. I configured /dev/hda3's lilo.conf by
I partitioned my hard drive in such a way that i can
install 2 OS. The partition goes like this:
/dev/hda1 - Linux (ext3)- Bootable
/dev/hda5 - Linux Swap
/dev/hda3 - Linux (reiserfs)
/dev/hda1 has Knoppix3.3 (LiveOIO) and /dev/hda3 has
Knoppix 3.6. I configured /dev/hda3's lilo.conf by
putting
hi
i've been running sid and after an apt-get -f upgrade yesterday morning, i
found that my lilo hangs. the letters LIL.. come up and it simply
freezes. i read through several man-pages and lists and figured that the
lilo may be pointing to incorrect map or something simply wrong with the
MBR.
[EMAIL PROTECTED] wrote:
hi
i've been running sid and after an apt-get -f upgrade yesterday morning, i
found that my lilo hangs. the letters LIL.. come up and it simply
freezes. i read through several man-pages and lists and figured that the
lilo may be pointing to incorrect map or something
On Wed, Jun 30, 2004 at 01:12:14PM -0400, Patrick Ouellette wrote:
[EMAIL PROTECTED] wrote:
hi
i've been running sid and after an apt-get -f upgrade yesterday morning, i
found that my lilo hangs. the letters LIL.. come up and it simply
freezes. i read through several man-pages and lists
Try placing the root= in your mkinitrd.conf.
# If this is set to probe mkinitrd will try to figure out what's needed to
# mount the root file system. This is equivalent to the old PROBE=on setting.
ROOT=/dev/hdb1 ext3
substitute your file system, ext2, etc. Quotes are necessary for correct
I am trying to get a Debian system 3.0 to use a 2.4.16-k7 kernel
I have added the kernel to lilo.conf entered the command lilo but get a
error (I do not get the error if I try using the 2.2.20-idepci kernel) the
error is:-
request_module[block-major-3]: Root fs not mounted
VFS: Cannot open root
Hello, Denis,
On Sun, May 16, 2004 at 07:02:27PM +0100, Denis Croombs wrote:
I am trying to get a Debian system 3.0 to use a 2.4.16-k7 kernel
I have added the kernel to lilo.conf entered the command lilo but get a
error (I do not get the error if I try using the 2.2.20-idepci kernel) the
On Sun, May 16, 2004 at 07:17:23PM +0100, Denis Croombs wrote:
I am using ext2 I have tried with and without initrd !
Is ext2 compiled into your kernel? If it is a module, you might need to
add it to your initrd.
If you have a serial console, a full boot output would help. Is it a
standard
in lilo.conf , enter line
root=/dev/*d**
for example root=/dev/hda1
cheers,
http://www.axeltabs.com/
__
axel
--- Denis Croombs [EMAIL PROTECTED] wrote:
I am trying to get a Debian system 3.0 to use a
2.4.16-k7 kernel
I have added the kernel to lilo.conf entered the
command lilo but get a
Hallo,
ich möchte ein Debian mit Hilfe eines debootstrap installieren.
dazu stecke ich die Platte auf die das neue Debian soll
(kann alternativ auch einfach ein zweites System auf einer anderen
Partition sein). in den Rechner, mache mit cfdisk die Partitionen
die ich will und mit mkfs.ext3 das
Hi Leute
Ich habe hier auf meiner debian-Kiste den Kernel 2.6.3 kompiliert/installiert.
Jetzt habe ich allerdings probleme mit lilo:
# lilo
Warning: '/proc/partitions' does not match '/dev' directory structure.
Name change: '/dev/nbd0' - '/tmp/dev.0'
Warning: '/dev' directory structure is
Hi Leute
Ich habe hier auf meiner debian-Kiste den Kernel 2.6.3 kompiliert/installiert.
Jetzt habe ich allerdings probleme mit lilo:
# lilo
Warning: '/proc/partitions' does not match '/dev' directory structure.
Name change: '/dev/nbd0' - '/tmp/dev.0'
Warning: '/dev' directory structure is
Hello
I need to install lilo on a HD on a machine that see it as /dev/sdc
and use it to boot linux (root=/dev/sdc1) on a machine that see it as
/dev/hdc (root=/dev/hdc1). My problem is that second machine realy is
not a PC, so I must create disk on a PC.
Can you give me a clue???
Thank
Guten Abend zusammen,
auf hoffnung bessere Hardware unterstützung zu bekommen natürlich mal
an dem wirklichen Schrauben des Systems zu drehen, habe ich mich dran
gemach (mit anweisungen auf
http://www.stud.uni-karlsruhe.de/~usge/kernel-compile.html)
den 2.4.22Kernel zu installieren. Es läut
Hi,
Es läut alles so lange gut,
bis das System lilo ausführen muss. Dann heist es, das Fehler
aufgetreten sind und ich die lilo.conf evtl. editieren soll und
lilo ausführen soll. Zu editiren gibt es meiner meinung nach
nichts.
Wie sieht sie denn aus, die lilo.conf?
Als führe ich lilo aus
Moin moin,
Am Friday 07 November 2003 19:43 schrieb M.Kiberu:
[...]
http://www.stud.uni-karlsruhe.de/~usge/kernel-compile.html)
den 2.4.22Kernel zu installieren. Es läut alles so lange gut, bis
das System lilo ausführen muss. Dann heist es, das Fehler
aufgetreten sind und ich die lilo.conf
Hello!
I have entries in my lilo.conf like these:
image=/boot/linux-2.4.22
label=D-Woody
read-only
other=/dev/hda5
label=D-Sarge
other=/dev/hda6
label=Red-Hat 9
When I run the 'lilo' command it says:
Fatal: First sector of /dev/hda6 doesn't have a valid boot signature
Ok, but
LeVA wrote:
When I run the 'lilo' command it says:
Fatal: First sector of /dev/hda6 doesn't have a valid boot signature
Ok, but what should I do now? How can I make a valid boot signature to
that partition? I have installed RH9 on it, and it seems it didn't create
that onto that partition.
How
[EMAIL PROTECTED] wrote:
Thanks for the help everyone, especially Michael. With your help I
managed to get it working :)
On Wed, 2003-09-17 at 15:03, Michael Bellears wrote:
Ensure that /vmlinuz exists.
It does on /dev/hdc8
Please show the output of mount.
Cool, now that
In linux.debian.user, you wrote:
Hi,
I have installed debain (woody) next to my current dist (mandrake 9.1).
I added entries to mandrakes lilo.conf so that I could boot both debian
and mandrake, I am sick of mandrake and want to completely switch to
debian.
I get the following error
Thanks for the help everyone, especially Michael. With your help I
managed to get it working :)
On Wed, 2003-09-17 at 15:03, Michael Bellears wrote:
Ensure that /vmlinuz exists.
It does on /dev/hdc8
Please show the output of mount.
MB
--
To UNSUBSCRIBE, email to [EMAIL
Hi,
I have installed debain (woody) next to my current dist (mandrake 9.1).
I added entries to mandrakes lilo.conf so that I could boot both debian
and mandrake, I am sick of mandrake and want to completely switch to
debian.
I get the following error message when running lilo (on mandrake):
Fatal: open /vmlinuz: No such file or directory
image=/vmlinuz
^^
label=Debian
root=/dev/hdc8
boot=/dev/hdc8
install=/boot/boot.b
map=/boot/map
read-only
What should I do?
Pretty self explanatory:
Ensure that /vmlinuz exists.
It does on /dev/hdc8
I imagine that /vmlinuz exists on all debian installs.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Ensure that /vmlinuz exists.
It does on /dev/hdc8
Please show the output of mount.
MB
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Wed, 2003-09-17 at 15:03, Michael Bellears wrote:
Ensure that /vmlinuz exists.
It does on /dev/hdc8
Please show the output of mount.
No output. It mounts without any problems, I am currently chrooted into
it. Thanks for trying to find a solution :)
--
To UNSUBSCRIBE, email to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 16 September 2003 07:07 pm,
[EMAIL PROTECTED] wrote:
On Wed, 2003-09-17 at 15:03, Michael Bellears wrote:
Ensure that /vmlinuz exists.
It does on /dev/hdc8
Please show the output of mount.
No output. It mounts without any
Thanks,
It's work for me.
Regards,
Victor,
- Original Message -
From: Andrés Roldán [EMAIL PROTECTED]
To: Victory [EMAIL PROTECTED]
Cc: Debian-User [EMAIL PROTECTED]
Sent: Monday, September 08, 2003 7:55 PM
Subject: Re: LILO problem
Change boot=/dev/sda1 for boot=/dev/sda and rerun
I use Noton Ghost 2003 to create disk to CD images then
restored from CD Image to another disk, After done I the reboot
to new disk and after MBR it support to start LILO 22.2 but it
show all 01 number all over the screen, I think my MBR LILO is screw-up,
search and found that Symantec say boot to
Change boot=/dev/sda1 for boot=/dev/sda and rerun /sbin/lilo
Victory [EMAIL PROTECTED] writes:
I use Noton Ghost 2003 to create disk to CD images then
restored from CD Image to another disk, After done I the reboot
to new disk and after MBR it support to start LILO 22.2 but it
show all 01
alles wieder in ordnung
man sollte seinem default kernel auch den namen geben den er hat!!
--
Haeufig gestellte Fragen und Antworten (FAQ):
http://www.de.debian.org/debian-user-german-FAQ/
Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an
Hi all,
I copied a working debian installation from one hard disk to another, except
i had to make a new kernel and install it.
I copied the new bzImage into /boot, and updated lilo.conf. /boot contains
the new kernel and nothing else.
When i run lilo, it gives an error message:
Fatal: open
Russell wrote:
Hi all,
I copied a working debian installation from one hard disk to another,
except
i had to make a new kernel and install it.
I copied the new bzImage into /boot, and updated lilo.conf. /boot contains
the new kernel and nothing else.
When i run lilo, it gives an error
On Sun, 17 Nov 2002, Elimar Riesebieter wrote:
On Sun, 17 Nov 2002 the mental interface of
Jan Krupa told:
Thanks for answer.
On Sun, 17 Nov 2002, Elimar Riesebieter wrote:
Hi Jan,
On Sun, 17 Nov 2002 the mental interface of
Jan Krupa told:
[...]
#
I have Pentium IV, HD 40 GB.
First Windows2000 professional was installed on first 30 GB of the HD
(on hda1).
Then on hda3 (10GB ) I installed Debian3.0 (current stable)
using compact floppies and then via ftp.
I chose (in the end of the installation process) to use
menu version of LILO and
Hi Jan,
On Sun, 17 Nov 2002 the mental interface of
Jan Krupa told:
[...]
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# --- `install-mbr(8)', `/usr/share/doc/lilo/',
# and `/usr/share/doc/mbr/'.
#
On Sun, 17 Nov 2002 the mental interface of
Jan Krupa told:
Thanks for answer.
On Sun, 17 Nov 2002, Elimar Riesebieter wrote:
Hi Jan,
On Sun, 17 Nov 2002 the mental interface of
Jan Krupa told:
[...]
# Boot up Linux by default.
#
On Thu, Jun 06, 2002 at 10:40:31PM +0200, Joachim Fahnenmueller wrote:
Hi,
there is only _one_ boot sector for the whole harddisk (e. g. hda).
So you have the following options:
1. Install lilo in the harddisk's MBR. It can boot windoze as well, as
Paul explained.
Uh, you *can*
Hi, All,
Here is my problem:
I am installing the testing version of debian. during the installation of
LILO, I choose to install it in the boot sector of hda2, which is my Linux
root partition (hda1 is windows 98). after that, it asks me whether I want
to install a new boot manager in the MBR, I
Ming Feng Gu wrote:
Hi, All,
Here is my problem:
I am installing the testing version of debian. during the installation of
LILO, I choose to install it in the boot sector of hda2, which is my Linux
root partition (hda1 is windows 98). after that, it asks me whether I want
to install a new boot
On Thu, Jun 06, 2002 at 11:12:48AM -0400, Ming Feng Gu wrote:
( ... )
I am installing the testing version of debian. during the installation of
LILO, I choose to install it in the boot sector of hda2, which is my Linux
root partition (hda1 is windows 98).
Hi,
there is only _one_ boot sector
Hello,
I got sid working! *jump*
Thanks to Alvin!
--
Rudy Gevaert - [EMAIL PROTECTED] - http://www.webworm.org
- keyserverID=24DC49C6 - http://www.zeus.rug.ac.be
Private mail with incorrect quoting behavior will remain unanswered
The backbone of surprise is fusing speed
- Original Message -
From: Rudy Gevaert [EMAIL PROTECTED]
To: Alvin Oga [EMAIL PROTECTED]
Cc: Rudy Gevaert [EMAIL PROTECTED]; debian-user@lists.debian.org
Sent: Friday, February 22, 2002 3:47 PM
Subject: Re: lilo problem
Wel, I removed the initrd line from lilo.conf, and redhat boots
On Fri, Feb 22, 2002 at 06:07:58PM -0800, Alvin Oga wrote:
cut
Thanks for the tips, I'll try it Mondag asap! (I'm now home and dont
have acces to my computer at uni)
--
Rudy Gevaert - [EMAIL PROTECTED] - http://www.webworm.org
- keyserverID=24DC49C6 - http://www.zeus.rug.ac.be
hi ya
I thought you had install Sid (and its kernel) on its own partition. So the
Sid kernel surely isn't in the /boot directory of your Red Hat !
just many ways to skinn the cat...
while booted on say /dev/hda1...( deb )
put all your kernels in /boot of the distro you wanna
Hello,
Due to some workload I've only had the time to look at this now.
On Thu, Feb 21, 2002 at 05:12:12AM -0800, Alvin Oga wrote:
hi ya
if it hands on ramdisk... remove that initrd line...
and/or make sure the file exists as typed
Wel, I removed the initrd line from lilo.conf, and
I'm just coming into the thread, but if you had your initrd=
in the main section of lilo.conf, try putting it
in the image section of your Sid kernel. That way,
no other kernel will try to use it.
Bob
On Fri, Feb 22, 2002 at 03:47:53PM +0100, Rudy Gevaert wrote:
Hello,
Due to some workload
On Fri, Feb 22, 2002 at 12:48:05PM -0500, Bob Thibodeau wrote:
I'm just coming into the thread, but if you had your initrd=
in the main section of lilo.conf, try putting it
in the image section of your Sid kernel. That way,
no other kernel will try to use it.
Where should I put the init
hi ya rudy
if you use a precompiled kernel... you have to tell
it where / is on the new machine... otherwise you do get
those kernel panics and no init found
- i always make a kernel on the target... and copy it around
but if you copy that kernel to flippy...
that floppy should boot
hi ya rudy
- first test that the sid kernel boots and oyu have sid running...
by putting it onto floppy...and boot off floppy
- sometimes it might not boot till you rdev the boot floppy
( the part i am wondering about for your kernel system
- once you know sid boots and
Hello,
I just installed a new hd (hdc), and put Sid on it. Because I have some bad
experiences with lilo (always my mistake), I boot now from floppy to get
to my Sid.
This is what I have on hdc:
/dev/hdc6 /
/dev/hdc1 /boot
/dev/hdc7 swap
/dev/hdc2 /usr
/dev/hdc3 /home
/dev/hdc5
jo ua to get sid running ...
for simplicity, just add these lines to lilo.conf on hda ( redhat's lilo )
#
# boot sid instead
# copy hdc:/boot/vmlinuz-2.4.xx to hda:/boot
#
image=/boot/vmlinuz-2.4.xxx
label=DebianSid
initrd=/boot/initrd-2.2.14-5.0.img
On Thu, Feb 21, 2002 at 04:08:43AM -0800, Alvin Oga wrote:
jo ua to get sid running ...
for simplicity, just add these lines to lilo.conf on hda ( redhat's lilo )
#
# boot sid instead
#copy hdc:/boot/vmlinuz-2.4.xx to hda:/boot
#
image=/boot/vmlinuz-2.4.xxx
hi ya
if it hands on ramdisk... remove that initrd line...
and/or make sure the file exists as typed
initrd is not needed if your kernel has all the hardware
drivers needed to boot...
i dont think a new kernel in sid ( hdc ) will solve anything
for redhat stuff in hda...
if you're referring
Recently I have been receiving a number of bug reports of LILO upgrades
unexpectedly resulting in a non-bootable system.
I have just received the following message which purports to explain it.
If your system matches the below description (2.4.10 kernel with first
partition
being Ext2 and
Better not downgrade to 2.4.9, as it is also vulnerable. See below.
Regards,
Stefan
Quoting Russell Coker [EMAIL PROTECTED] [23 Oct-01 19:08]:
On Tue, 23 Oct 2001 15:23, you wrote:
Quoting Russell Coker [EMAIL PROTECTED] [23 Oct-01 15:08]:
2) Prepare an upgrade to 2.4.12 or a downgrade
I see from the archives that there have been problems
with LILO and Woody. Have they been resolved?
I took my (text only) 2.2r3 + 2.4.5 upgrade system which
worked quite happily and tried to upgrade to Woody.
Using dselect failed (template parse errors) but using
apt-get upgrade and then apt-get
hello!
i'm a fourth-yr comp. sci. student from the university
of the phils. manila. i've just installed debian
gnu/linux a month ago, and i'm very satisfied not to
see another BSOD from windows again. After tinkering
the pc, here are some of the stumbling blocks i
encountered:
1.)i just upgraded
hi,
1.)i just upgraded (force-overwrite) libc6-2.1.3 and
libdb2 that comes with the debian 2.2r3 with the
testing packages of libc6-2.2.3 and libdb2-2.7.
after that i recompiled kernel 2.4.7pre3. when i ran
lilo, it flashed out a message open /vmlinuz - no
such file or directory when i
On Sun, Jul 22, 2001 at 01:31:20AM -0700, Fallen Lord wrote:
1.)i just upgraded (force-overwrite) libc6-2.1.3 and
libdb2 that comes with the debian 2.2r3 with the
testing packages of libc6-2.2.3 and libdb2-2.7.
Be very careful with any of the --force options to dpkg, they're not
supposed to be
Fallen Lord wrote:
3.)Do i need to upgrade pppd if i use kernel 2.4.x?
wvdial won't connect - something like invalid
argument reflects in the /var/logs/message file. what
do i need to do? is there a better way to connect via
dial-up than wvdial? if so, how?
Check out the Debian Website.
Hello all,
I recently upgraded all packages necessary to install a 2.4.x kernel on my
Debian 2.2 laptop. After downloading, compiling, and installing the 2.4.5
kernel I rebooted and was greeted with a screen reading only LIL-.
I have a boot floppy made when I originally installed and was able to
On Mon, Jun 11, 2001 at 04:54:04PM +, Anthony Fairchild wrote:
| Hello all,
|
| I recently upgraded all packages necessary to install a 2.4.x kernel on my
| Debian 2.2 laptop. After downloading, compiling, and installing the 2.4.5
| kernel I rebooted and was greeted with a screen reading only
On Mon, Jun 11, 2001 at 04:54:04PM +, Anthony Fairchild wrote:
Hello all,
I recently upgraded all packages necessary to install a 2.4.x kernel on my
Debian 2.2 laptop. After downloading, compiling, and installing the 2.4.5
kernel I rebooted and was greeted with a screen reading only
On Mon, Jun 11, 2001 at 08:04:16PM -0500, ktb wrote:
On Mon, Jun 11, 2001 at 04:54:04PM +, Anthony Fairchild wrote:
Hello all,
I recently upgraded all packages necessary to install a 2.4.x kernel on my
Debian 2.2 laptop. After downloading, compiling, and installing the 2.4.5
kernel
i have encountered an odd lilo problem.
i have a scsi HD (linux) and an IDE HD (win2k).
i configure lilo, run lilo, and it reports no errors.
reboot, and lilo hangs.
unplug IDE drive, run lilo again, and it reports no errors.
plug IDE drive back in, and lilo boots linux normally. in fact, i
On Thu, May 24, 2001 at 03:15:08AM -0400, [EMAIL PROTECTED] wrote:
i have encountered an odd lilo problem.
i have a scsi HD (linux) and an IDE HD (win2k).
i configure lilo, run lilo, and it reports no errors.
reboot, and lilo hangs.
unplug IDE drive, run lilo again, and it reports
Can you mail your /etc/lilo.conf?
Once upon a time, [EMAIL PROTECTED] [EMAIL PROTECTED] found a keyboard. And
typed:
i have encountered an odd lilo problem.
i have a scsi HD (linux) and an IDE HD (win2k).
i configure lilo, run lilo, and it reports no errors.
reboot, and lilo hangs.
unplug
Hey all...
I recompiled my kernel 2.4.2, and did all of the System.map,
vmlinuz copying, then ran LILO (which seemed quite happy).
However, when I boot the computer, I get the following prompt,
after which it freezes:
LIL-
Any ideas about this? I have more than one kernel on the system,
so it
On Thu, Apr 26, 2001 at 03:14:16AM -0700, Tiarnan O'Corrain wrote:
Hey all...
I recompiled my kernel 2.4.2, and did all of the System.map,
vmlinuz copying, then ran LILO (which seemed quite happy).
However, when I boot the computer, I get the following prompt,
after which it freezes:
Tiarnan O'Corrain wrote:
Hey all...
I recompiled my kernel 2.4.2, and did all of the System.map,
vmlinuz copying, then ran LILO (which seemed quite happy).
However, when I boot the computer, I get the following prompt,
after which it freezes:
LIL-
I had a similar problem. Mine was due
On Thursday 26 April 2001 15:37, Andrew D Dixon wrote:
Tiarnan O'Corrain wrote:
Hey all...
I recompiled my kernel 2.4.2, and did all of the System.map,
vmlinuz copying, then ran LILO (which seemed quite happy).
However, when I boot the computer, I get the following prompt,
after which
On Thursday 26 April 2001 12:14, Tiarnan O'Corrain wrote:
I recompiled my kernel 2.4.2, and did all of the System.map,
vmlinuz copying, then ran LILO (which seemed quite happy).
However, when I boot the computer, I get the following prompt,
after which it freezes:
LIL-
Any ideas about
Thanks to all who replied. Here's what I did in the end
(not having a rescue disk and being too ashamed to admit it)...
Downloaded Tom's Root and Boot disk
http://www.toms.net/rb/
Booted using tomsrtbt and since I had no concrete idea what
the partition table looked like (head once more bowed
On Thu, Apr 26, 2001 at 07:59:15AM -0700, Tiarnan O'Corrain wrote:
Thanks to all who replied. Here's what I did in the end
(not having a rescue disk and being too ashamed to admit it)...
You do not need rescue disk made during installation for this. If you
have boot floppy for installation or
hi
i have installed linux many times but there is just
one problem that i am facing, that is writing lilo to
the mbr. every time the installation is successful the
lio prompt does not show up when the pc reboots , but
it only comes up with the boot floppy. how can i
write lilo to the mbr as i
On Wed, 24 Jan 2001, Omar Shuja Siddiqui wrote:
hi
i have installed linux many times but there is just
one problem that i am facing, that is writing lilo to
the mbr. every time the installation is successful the
lio prompt does not show up when the pc reboots , but
it only comes up with
On Wed, Jan 24, 2001 at 02:13:22PM -0800, Omar Shuja Siddiqui wrote:
hi
i have installed linux many times but there is just
one problem that i am facing, that is writing lilo to
the mbr. every time the installation is successful the
lio prompt does not show up when the pc reboots , but
it
Hi,
I just updated my debian woody (testing) installation with dselect and
when it tries to install the new lilo-version, I get the following
errors:
Configuring packages ... /var/lib/debconf//config.1295:
/usr/sbin/lilo_find_mbr: No such file or directory
lilo failed to configure, with
On Thu, Jan 11, 2001 at 07:57:58PM -0800, Dale Morris wrote:
Big learning curve here.
Actually, it's not as bad it seems. :-)
I just checked and it is on the secondary controller. What now?
Good. Moving the drive should be fairly straightforward. Excuse me if it
is a bit longish. Easier to
Bob Billson wrote:
On Fri, Jan 12, 2001 at 08:05:13AM +0700, Oki DZ wrote:
well actually two questions. First, is it easy to pass parameters to the
kernel like with lilo.conf's 'append='?
Yes, just press c when grub's menu shows (spending time for the
defined delay).
Sorry, guess I
On Fri, Jan 12, 2001 at 04:05:49PM +0700, Oki DZ wrote:
Sorry, guess I didn't make myself clear. I should have said does grub
have the equivalent of lilo's /etc/lilo.conf where an equivalent 'append='
line goes? That avoids have to press 'c' and entry to info.
Yes, it's the
To quote Dale Morris [EMAIL PROTECTED],
# I'm having a problem with LILO. I have windows installed in the first
# partition on my hd but somehow have wiped out the mbr. I've also tried
to
# compile the new 2.4 kernel, but am getting the following error:
# cat bzImage /vmlinuz
# cp
duh.. I forgot to attach the lilo.conf file. I'll try again. When I try to
boot from the hard drive, all that happens is I get a screenfull of zeros.
here's how my hd is partitioned:
hdc1=windows
hdc3=/
hdc5=/home
hdc6=/usr
hdc4=swap
thanks for replying.
David B. Harris [EMAIL PROTECTED] wrote:
On Thu, Jan 11, 2001 at 07:15:37AM -0800, Dale Morris wrote:
here's how my hd is partitioned:
hdc1=windows
hdc3=/
hdc5=/home
hdc6=/usr
hdc4=swap
Assuming you didn't make a typo and meant hdc not hda, what is on hda (master
drive, primary controller)? My brother looking over my shoulder
Hi Bob,
When I change hdc to hda and run /sbin/lilo I get the following message:
lymond:/# /sbin/lilo
Fatal: open /dev/hda1: Device not configured
I am not sure now why these are listed as hdc, this install comes from
libranet 1.8.2 (althought I don't know why that would make any difference).
I'm
On Thu, Jan 11, 2001 at 07:55:56AM -0800, Dale Morris wrote:
Hi Dale... I forgot to ask how many drives are in your machine?
Partition check:
hdc: hdc1 hdc2 hdc5 hdc6 hdc3 hdc4
This it the only drive the kernel finds when booting? Seems like it. The
kernel should report all
On Thu, Jan 11, 2001 at 10:44:20AM -0500, Bob Billson wrote:
| Linux maps drives like this:
|MSDOSLinux
|~~
| C: hda(master, primary controller)
| D: hdb(secondary, primary controller)
| E: hdc(master, secondary
On Thu, 11 Jan 2001 12:44:18 EST, D-Man writes:
C: hda1
D: hda2
E: hdb1
F: hdb2
DOS values primary partitions higher than everything else, so that
would be:
C: hda1
D: hdb1
E: hda2
F: hdb2
eg when you have 3 partitions per drive:
C: hda1
D: hdb1
E: hda2
F:
1 - 100 of 169 matches
Mail list logo
