The real problem is that your lilo.conf file makes reference
to an /initrd.img file which may not exist. The warning can
be skipped and means that your kernel was compiled with DEVFS_FS
support and you are not using it.
--
Andrés Roldán [EMAIL PROTECTED]
GPG Key-ID: 0xB29396EB
I'm having some probs with lilo:
# dpkg -i kernel-image-2.6.4_cobalamin.1.0_i386.deb# install of a custom kernel
===
{SNIP}
You already have a LILO configuration in /etc/lilo.conf
Install a boot block using the existing /etc/lilo.conf? [Yes] yes
Testing
Michael Bonert wrote:
I'm having some probs with lilo:
# dpkg -i kernel-image-2.6.4_cobalamin.1.0_i386.deb# install of a custom kernel
===
{SNIP}
You already have a LILO configuration in /etc/lilo.conf
Install a boot block using the existing /etc/lilo.conf?
Roscoe Joao [EMAIL PROTECTED] writes:
There's a catch, anyway: knoppix gives you a complete RAM based
working environment, so you must to sure that you're working in the
real HD filesytem (find the right partition, mount it read/write, and
maybe, chroot to it) to make all this work.
Mount it
I know this isn't a knoppix list, but it's debian based, and I'm not having much luck
at other places. Hope you can help :)
I made a new computer (yay), and proceeded install the Fedora Core. After playing with
it for a little while, I thought No, I don't think so, and did a hard disk install
On Tue, Feb 03, 2004 at 10:00:31AM +, [EMAIL PROTECTED] wrote:
I also tried uninstalling grub using dselect. I assume that the grub that I
uninstalled was a debian grub, not the one that is booting my system.
Hi, Paul.
The bootstrappers are managed unlike the rest of the system. Simple
I'm still kind of newbie, so, please, be careful about by tips, but
maybe this will help:
Grub and lilo are alike in the sense that both (can) install code to the
Master Boot Record to (be loaded by the bios at startup and) automate
the boot process. Such boot code would not be affected by
Hi all.I haven't had problems before on other machines with make-kpkg.
Just used it to upgrade the kernel to 2.4.22 on a machine at work, and have
had a horrible time.
I get the message: fsck ext3 No such file or directory while trying to
open /dev/hdb2 which is my root directory. Then
Subject:
LILO problems, no boot, can I use Knoppix rescue to fix?
Repost with modifications, first few tries did make
it to the debian user list. Maybe an overzealous
spam filter again:
I did an aptitude and did an update,
and a few g keystrokes to download and install.
Aptitude said something
FIxed.
I pressed the ALT key to go
to boot from linux.old selection in the lilo
boot menu. Then went in and downloaded
a new kernel (for Athlon K7) and matching modules.
Sorry, if you see my original posting several times,
it is taking a full day to see my posting show up??
--
To UNSUBSCRIBE,
J F wrote:
Repost with modifications, first one did make
it to the list:
I did an aptitude and did an update,
and a few g keystrokes to download and install.
Aptitude said something like:
Warning, it was deleting modules for old
version of kernel.
Now the system won't reboot.
THe screen says:
On Tue, Sep 23, 2003 at 11:02:02PM -0400, J F wrote:
Any way, I can reboot using the Knoppix CD
as a rescue disk
and then edit /mnt/hda1/etc/lilo.conf .
But when I run lilo, it
says:
# sudo su
# lilo -C /mnt/hda1/etc/lilo.conf
Fatal. Sorry, don't know how to handle device 0xf000
How
I am doing this from memory, so I stand to be
corrected. But...
You must chroot to the root directory that has the
problem and the /etc with lilo.conf.
Lilo does that with the -r option: so try
lilo -r /mnt/hda1
Regards,
Hugo
__
Do you Yahoo!?
The New Yahoo!
* J F [EMAIL PROTECTED] [030924 21:53]:
But when I run lilo, it
says:
# sudo su
# lilo -C /mnt/hda1/etc/lilo.conf
Fatal. Sorry, don't know how to handle device 0xf000
How can I use Knoppix to fix LILO boot?
I don't know, if this will fix your problem, but you might try to use
chroot
Repost with modifications, first one did make
it to the list:
I did an aptitude and did an update,
and a few g keystrokes to download and install.
Aptitude said something like:
Warning, it was deleting modules for old
version of kernel.
Now the system won't reboot.
THe screen says:
LILO
Repost with modifications, first few tries did make
it to the debian user list. Maybe an overzealous
spam filter again:
I did an aptitude and did an update,
and a few g keystrokes to download and install.
Aptitude said something like:
Warning, it was deleting modules for old
version of kernel.
I did an aptitude and did an update,
and a few g keystrokes to download and install.
It said: warning, it was deleted modules for old
version of kernel.
Now the system won't reboot.
This is from a Knoppix CD install.
Any way, I can reboot using the Knoppix CD
and edit /mnt/hda1/etc/lilo.conf .
I've installed a new server (woody 3.0r1 + proposed updates + security
updates) on a system that is running with root on sda3. Lilo seems to be
having problems as on boot it outputs and L followed by 01 01 01 and on
and on. i.e. L 01 01 01 01... Any clues what the problem is? I'm able
to get in
On Wednesday 06 August 2003 19:23, Jefferson Cowart wrote:
I've installed a new server (woody 3.0r1 + proposed updates + security
updates) on a system that is running with root on sda3. Lilo seems to be
having problems as on boot it outputs and L followed by 01 01 01 and on
and on. i.e. L 01
Thanks for the help everyone. I ended up getting the answer from the
LILO developer. His answer is below. The problem stems from the fact
that the version of LILO in stable can't handle the bios booting from a
disk other than the first one, without telling lilo what the bios boot
order is. In my
* Paul Johnson ([EMAIL PROTECTED]) [030806 02:48]:
On Wed, Aug 06, 2003 at 12:23:24AM -0700, Jefferson Cowart wrote:
Please CC me on any responses as I'm not subscribed to this list.
http://www.cs.tut.fi/~jkorpela/usenet/mail-responses.html
Either set Mail-Followup-To: yourself or don't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Aug 06, 2003 at 12:23:24AM -0700, Jefferson Cowart wrote:
I've installed a new server (woody 3.0r1 + proposed updates + security
updates) on a system that is running with root on sda3. Lilo seems to be
having problems as on boot it outputs
West [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 06, 2003 05:19
To: Jefferson Cowart
Cc: [EMAIL PROTECTED]
Subject: Re: Lilo Problems
Jefferson Cowart wrote:
I've installed a new server (woody 3.0r1 + proposed updates
+ security
updates) on a system that is running with root
In linux.debian.user, you wrote:
Sorry I mis-typed the rescue line. My root is /dev/sda3 and I type
rescure root=/dev/sda3. Below is my lilo.conf file with comments
removed. In addition I've included my /etc/fstab file and the output of
df -h to show my /boot partition is small and at the
On Wed, August 06 at 2:46 AM EDT
Paul Johnson [EMAIL PROTECTED] wrote:
Please CC me on any responses as I'm not subscribed to this list.
http://www.cs.tut.fi/~jkorpela/usenet/mail-responses.html
Either set Mail-Followup-To: yourself or don't request it.
Paul - for future reference - what if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Aug 06, 2003 at 09:11:31AM -0400, Shawn Lamson wrote:
Paul - for future reference - what if one requests CC's because it
sometimes takes hours (12 or more) for one to see posts on the lists due
to listserv (or whatever handles this) being
AM
Subject: Re: Help! Lilo Problems with NT and Debian Linux
Am Montag, 3. Juni 2002 17:50 schrieb Sebastian Canagaratna:
Any suggestion for safely recovering so that I can boot up into
WIndows, and also chose linux from the menu rather than always
use a floppy to boot into linux
Am Dienstag, 4. Juni 2002 19:13 schrieb prover:
I'M NOT MEMER OF YOUR MAILING LISTS.
WHY THIS MAILS COME TO ME?
EVERY DAY COME TO ME 200 MAILS FROM YOUR MAILING LISTS.
CAN YOU DO SOMETHING WITH IT?
THANK YOU.
Hi Thomas,
Didn't you read the Answer to an earlier message of you?
You
Hi:
I am running sid and kernel 2.4.8. I had copied /bootsect.lnx
into c:\ so that I would be given a choice to boot into NT or linux.
After I installed kernel 2.4.8 and I chose linux, I would get LI
and the machine would hang up. So whenever I used to linux I had to
boot from a floppy
Am Montag, 3. Juni 2002 17:50 schrieb Sebastian Canagaratna:
Any suggestion for safely recovering so that I can boot up into
WIndows, and also chose linux from the menu rather than always
use a floppy to boot into linux?
Hello,
I think you can use M$ fdisk /mbr to reinstall the
As a new debian User ie 48 hours I am having trouble with the
configuration of lilo.
I installed a 2.2r3 version of debian and imediately down loaded the
2.4.16
binary.
The configuration tool said I am going to add a new block for your to
lilo but you will have to add initrd=/initrd to lilo.conf
On Sat, 2002-02-16 at 14:51, Peter McConnell wrote:
As a new debian User ie 48 hours I am having trouble with the
configuration of lilo.
I installed a 2.2r3 version of debian and imediately down loaded the
2.4.16
binary.
You can't run that kernel without significant upgrades to some other
Greg C. Madden wrote:
On Sat, 2002-02-16 at 14:51, Peter McConnell wrote:
As a new debian User ie 48 hours I am having trouble with the
configuration of lilo.
I installed a 2.2r3 version of debian and imediately down loaded the
2.4.16
binary.
You can't run that kernel without
On Sat, Feb 16, 2002 at 06:51:23PM -0500, Peter McConnell wrote:
As a new debian User ie 48 hours I am having trouble with the
configuration of lilo.
I installed a 2.2r3 version of debian and imediately down loaded the
2.4.16
binary.
The configuration tool said I am going to add a new
I'm trying to configure LILO to allow me to boot from my FAT partition
(Windows 98) and my Linux partition, but for some reason the only thing it'll
boot from is Linux. If I try to run a boot loader from DOS to configure it,
the only partition it'll find is the Windows one.
Does anyone know
Put an entry like this:
# Boot Win98
other=/dev/sda2
label=dos(2)
alias=2
You also need entries for prompt, and delay (and I'd suggest timeout and
single-key).
prompt # Needed so you can choose what to boot.
single-key # Allows you to use number aliases without hitting enter.
delay=100 #
[EMAIL PROTECTED] wrote:
I'm trying to configure LILO to allow me to boot from my FAT partition
(Windows 98) and my Linux partition, but for some reason the only thing it'll
boot from is Linux. If I try to run a boot loader from DOS to configure it,
the only partition it'll find is the
On Mon, Jul 30, 2001 at 05:03:59PM -0400, [EMAIL PROTECTED] wrote:
I'm trying to configure LILO to allow me to boot from my FAT partition
(Windows 98) and my Linux partition, but for some reason the only thing it'll
boot from is Linux. If I try to run a boot loader from DOS to configure it,
Sam Varghese wrote:
On Mon, Jul 30, 2001 at 05:03:59PM -0400, [EMAIL PROTECTED] wrote:
I'm trying to configure LILO to allow me to boot from my FAT partition
(Windows 98) and my Linux partition, but for some reason the only thing it'll
boot from is Linux. If I try to run a boot loader from
Kent West wrote:
Sam Varghese wrote:
On Mon, Jul 30, 2001 at 05:03:59PM -0400, [EMAIL PROTECTED] wrote:
I'm trying to configure LILO to allow me to boot from my FAT
partition (Windows 98) and my Linux partition, but for some reason
the only thing it'll boot from is Linux. If I try to run a
hi,
are you sure that lilo is installed? lilo.conf is in /etc
dpkg -l | grep lilo.
on my system this is the output.
ii lilo 21.7.5-5 LInux LOader - The Classic OS loader can loa
if you don't get anything similar the run apt-get install lilo.
hope that helps
Dan Ryan wrote:
I am completely new to debian and linux for that matter and I was just
installing it on one of my other computers. Now I want to make it a dual
boot system. The only problem is I can't use X because I dont have a
supported video card. So... how do I edit lilo.conf from the
I am completely new to debian and linux for that matter and I was just installing it on one of my other computers. Now I want to make it a dual boot system. The only problem isI can't use X because I dont have a supported video card. So... how do I edit lilo.conf from the starting command prompt?
On Sat Feb 24 00:06:54 2001 David Raeker-Jordan wrote...
This seems to have been done by the installer. I booted from the
floppy, looked
at /etc/lilo.conf (which had all teh correct setings for my confg as
dar as I
can tell), and ran lilo just on general principles.
On Fri Feb 23 23:48:07 2001 Lute Mullenix wrote...
On Fri, Feb 23, 2001 at 09:34:24PM -0500, Stan Brown wrote:
This seems to have been done by the installer. I booted from the
floppy, looked
at /etc/lilo.conf (which had all the correct settings for my config as
dar as I
On Fri Feb 23 22:33:51 2001 ktb wrote...
If I try to boot from the hard didk, I get the following:
L 40 40 40 40 40 40 40 40 40 and it continures till i hit the
power
swithc.
More sugestions?
Post the output of -
# rdev
and your /etc/lilo.conf
Any error messages
On Fri Feb 23 22:33:51 2001 ktb wrote...
If I try to boot from the hard didk, I get the following:
L 40 40 40 40 40 40 40 40 40 and it continures till i hit the
power
swithc.
More sugestions?
Post the output of -
# rdev
and your /etc/lilo.conf
Any error messages
On Fri Feb 23 22:33:51 2001 ktb wrote...
Post the output of -
# rdev
and your /etc/lilo.conf
Any error messages when you run /sbin/lilo?
kent
On Sat, Feb 24, 2001 at 10:00:36AM -0500, Stan Brown wrote:
Script started on Sat Feb 24 05:58:00 2001
debian_test:~# rdev
/dev/hda3 /
On Sat Feb 24 11:53:25 2001 ktb wrote...
OK I don't know if this will work but lets clean this up a bit and try a
couple things. First comment out the lines for the image=/vmlinuz.old
section and comment out lba32 and run /sbin/lilo, post any error
messages. Have you tried upgrading your bios
(quoting modified for readability)
On Sat, 24 Feb 2001 12:59:52 EST, Stan Brown writes:
Now on to the good new. I made the changes to /etc/lilo.conf you
sugested, and reran /sbin/lilo (no errors). Then I rebooted. I
now ger LI and the system hangs there. I have tried this both
with LBA on, and off
On Sat, Feb 24, 2001 at 12:59:52PM -0500, Stan Brown wrote:
On Sat Feb 24 11:53:25 2001 ktb wrote...
OK I don't know if this will work but lets clean this up a bit and try a
couple things. First comment out the lines for the image=/vmlinuz.old
section and comment out lba32 and run
On Sat Feb 24 13:11:40 2001 Robert Waldner wrote...
(quoting modified for readability)
On Sat, 24 Feb 2001 12:59:52 EST, Stan Brown writes:
Now on to the good new. I made the changes to /etc/lilo.conf you
sugested, and reran /sbin/lilo (no errors). Then I rebooted. I
now ger LI and the system
I am trying to install stable On an HP Vectra P200, with a 20G IDE disk.
All of the install goes well, untill I reboot. Then, I get a continuois stream
of
40 ;s streaming across teh screen while the hard disk ling _and_ the floppy
light
flash!
I can boot from the boot floppy OK.
I set up a
On Fri, Feb 23, 2001 at 05:42:13PM -0500, Stan Brown wrote:
I am trying to install stable On an HP Vectra P200, with a 20G IDE disk.
All of the install goes well, untill I reboot. Then, I get a continuois
stream of
40 ;s streaming across teh screen while the hard disk ling _and_ the floppy
I am trying to install stable On an HP Vectra P200, with
a 20G IDE disk.
snip
BTW, the BIOS thinks this is onl an 8G disk, which may
be part of the problem?
You might be able to upgrade your bios in order to see all 20G's.
And if there's no BIOS upgrade available, I *think* you can
On Fri Feb 23 18:57:36 2001 ktb wrote...
On Fri, Feb 23, 2001 at 05:42:13PM -0500, Stan Brown wrote:
I am trying to install stable On an HP Vectra P200, with a 20G IDE disk.
All of the install goes well, untill I reboot. Then, I get a continuois
stream of
40 ;s streaming across teh screen
On Fri, Feb 23, 2001 at 09:34:24PM -0500, Stan Brown wrote:
On Fri Feb 23 18:57:36 2001 ktb wrote...
On Fri, Feb 23, 2001 at 05:42:13PM -0500, Stan Brown wrote:
I am trying to install stable On an HP Vectra P200, with a 20G IDE disk.
All of the install goes well, untill I reboot. Then,
On Fri, Feb 23, 2001 at 09:34:24PM -0500, Stan Brown wrote:
This seems to have been done by the installer. I booted from the
floppy, looked
at /etc/lilo.conf (which had all the correct settings for my config as
dar as I
can tell), and ran lilo just on general principles.
This seems to have been done by the installer. I booted from the
floppy, looked
at /etc/lilo.conf (which had all teh correct setings for my confg as
dar as I
can tell), and ran lilo just on general principles.
I alos watched the boot messages, and went back and
luck
Hall
- Original Message -
From: Rogelio E. Castillo Haro,,, [EMAIL PROTECTED]
To: Hall Stevenson [EMAIL PROTECTED]
Sent: Wednesday, February 07, 2001 1:49 PM
Subject: Re: Lilo problems after a debian installation...
I have not the PC on network, but I think that the matter
I thought it was odd that you had Windows on the secondary controller. I
didn't think it would work that way, but assumed it was already. I
thought you made some changes to lilo and then it stopped working...
Oh well, it's working now so that's all that matters !
Hall
thanks lot for your
Hi,
I've two disks
Primary master (hda) with Debian, just installed las weekend
Secondary master (hdc) with Win98 already installed and working...(sic)
Well I install Debian on my primary disk and tell lilo to install at the
MBR (unsafe I know)
Now when I select to boot win98 it appears:
Primary master (hda) with Debian, just installed las weekend
Secondary master (hdc) with Win98 already installed and
working...(sic)
Well I install Debian on my primary disk and tell lilo to install at
the
MBR (unsafe I know)
Now when I select to boot win98 it appears:
Loading win
L?
And
I upgraded to sid a month or so ago, and i
remember it asked me something about lilo, and replacing it with the debian boot
loader, i said yes, but now after i compiled a new kernel, and ran lilo i get :
LI
i know that means a geometry missmatch etc... but
what i wanna know is which
On Mon, Aug 28, 2000 at 08:18:43PM -0500, luke b wrote:
I am having problems with lilo. When my computer boots, I have no
opportunity to type my other kernel labels. It just says LILO, and I am
unable to type anything. Lilo is in my MBR. Please help . . .
Does it say
prompt
timeout=20
i got it working. i just had to turn on the welcome message and an alias,
and it started working like i'm used to . . .
luke
From: Dean [EMAIL PROTECTED]
To: luke b [EMAIL PROTECTED], debian-user@lists.debian.org
Subject: Re: LILO problems . . .
Date: Mon, 28 Aug 2000 22:55:14 -0500
Hi
I am having problems with lilo. When my computer boots, I have no
opportunity to type my other kernel labels. It just says LILO, and I am
unable to type anything. Lilo is in my MBR. Please help . . .
_
Get Your Private,
You need to edit /etc/lilo.conf the default file has really good comments just
read them and do the right thing.
-- Original Message --
From: luke b [EMAIL PROTECTED]
Date: Mon, 28 Aug 2000 20:18:43 CDT
I am having problems with lilo. When my computer
-Originating-IP: [206.146.40.218]
From: luke b [EMAIL PROTECTED]
To: debian-user@lists.debian.org
Subject: LILO problems . . .
Date: Mon, 28 Aug 2000 20:18:43 CDT
X-OriginalArrivalTime: 29 Aug 2000 01:18:43.0370 (UTC)
FILETIME=[125410A0:01C01157]
Resent-Message-ID: [EMAIL PROTECTED]
Resent-From
Hi Luke:
You did try to hit the shift key as soon as you saw
lilo? That should pause lilo, then you can hit tab
and that will show all choices loaded in lilo.conf
hth Dean
luke b wrote:
I am having problems with lilo. When my computer boots, I have no
opportunity to type my other
* Jon Keating [EMAIL PROTECTED] writes:
with that. Can a system boot up without a map file? It seems like it can.
Yes, you experienced it :-)
But like your problem, I always thought you needed the map file. I know my
Only if you want more informative error messages in case of a kernel
You were referring to System.map for the error messages, not the /boot/map
file used to load the system.
Hello,
I've recently discovered problems with the drive that had the /boot and
/home partitions of my Debian box, so I decided to go out and get a new HD
in transferring the files, I simply copied /boot/* and /home/* to the new
drive, and ran lilo on it. It gave me the message that lilo
Subject: LILO problems with new HD
Date: Sun, Jul 25, 1999 at 09:48:08PM -0700
In reply to:Lev Lvovsky
Quoting Lev Lvovsky([EMAIL PROTECTED]):
Hello,
I've recently discovered problems with the drive that had the /boot and
/home partitions of my Debian box, so I decided
I've recently discovered problems with the drive that had the /boot and
/home partitions of my Debian box, so I decided to go out and get a new
HD
in transferring the files, I simply copied /boot/* and /home/* to the new
drive, and ran lilo on it. It gave me the message that lilo
I don't know if we have similiar problems or not. With my system it can't
find the map file, but it still boots up, so I'm not sure what the deal is
with that. Can a system boot up without a map file? It seems like it can.
But like your problem, I always thought you needed the map file. I know
Subject: Re: LILO problems with new HD
Date: Mon, Jul 26, 1999 at 01:21:46AM -0700
In reply to:Lev Lvovsky
Quoting Lev Lvovsky([EMAIL PROTECTED]):
hehe, sorry, I post under the assumption that ppl's balls are in working
order ;-D.
/boot is hda1...there are three partitions
Ok I guess I have to spend more time to ask specific questions..
sigh
You said
I simply copied /boot/* and /home/* to the new drive, and ran lilo on
it.
You didn't say if you updated the /etc/fstab file.
yes, /boot, /home, and the swap partition are updated to reside on the new
tf wrote:
hey all
I just expanded the 2.2.6 kernal into /usr/src. I have only the base system
installed, but am getting debs and
throwing them into a windows directory. among them was make. so I got to
the make menuconfig step and I got
an error (sorry can't remember
hey all
I just expanded the 2.2.6 kernal into /usr/src. I have only the base system
installed, but am getting debs and
throwing them into a windows directory. among them was make. so I got to
the make menuconfig step and I got
an error (sorry can't remember which one). I thought I'd find
I've had debian 2.0 running on my machine for a while now, but I finally
decided it
was time to load up windows so I could play some games. :) I went out
and bought
a new hard drive, and I want to boot windows off of it.
I've tried several lilo configurations, but I can't seem to make my
On Sun, Feb 21, 1999 at 02:06:50PM -0500, Christopher Fury wrote:
I've had debian 2.0 running on my machine for a while now, but I finally
decided it
was time to load up windows so I could play some games. :) I went out
and bought
a new hard drive, and I want to boot windows off of it.
If 2 drives are swaped, /etc/fstab will also need to be changed to
reflect
changes in system.
Andrew
---
Andrei S. Ivanov
[EMAIL PROTECTED]
UIN 12402354
On Thu, Aug 21, 1997 at 10:44:08PM -0700, Mike Schmitz wrote:
make the boot line in /etc/lilo.conf read
boot=/dev/hda - or sda for SCSI
and run lilo
Urgh. That's the wrong solution. It is unnecessary in 95% of cases to put
LILO in the MBR, and it just makes things more confusing later if
On Aug 22, Paul Lange wrote
Joy. I've installed Debian 1.3.1 fresh on a 486/66 with ~4 megs of ram.
This machine is to be a router for home, but right after the install when I'm
to reboot and see how my system goes, I get this as an error message when LILO
won't load:
3FA:
Yup.
ext
/dev/sda1 == New SCSI Disk, Linux filesystem, bootable
/dev/hda1 == Old 9GB Disk, hda1 currently holds old copy of filesystem.
/dev/hda2 == Windoze partition on old disk, bootable.
I included my lilo.conf below. I'm sure that I'm either doing something
dumb, or just not considering an
On Wed, Jan 27, 1999 at 12:03:40PM -0600, Harrison, Shawn wrote:
ext
/dev/sda1 == New SCSI Disk, Linux filesystem, bootable
/dev/hda1 == Old 9GB Disk, hda1 currently holds old copy of filesystem.
/dev/hda2 == Windoze partition on old disk, bootable.
I included my lilo.conf below. I'm sure
Hi all,
I recently switched my filesystem over to a SCSI Hard Drive, and
now I want to use my old 9GB Drive for storage and for holding a small
Windows partition. After I set this up in lilo.conf and tried to boot to
Windows, my machine hung right at the message Loading Windows. I have
I have compiled a new kernel, I run make zdisk to make a boot-disk
and that works just fine. But I can't make my hard-drive boot-able.
When init is about to start I get an oops, 'unable to handle kernel
paging request...'. I have also tried make-kpkg but I get the same
error.
lilo.conf points to
--
interzone:/etc# /sbin/lilo
Warning: /dev/hdd is not on the first disk
Warning: BIOS drive 0x82 may not be accessible
Warning: BIOS drive 0x82 may not be accessible
Warning: BIOS drive 0x82 may not be accessible
I struggled thru this myself recently. I finally had lilo booting NT. My
On Mon, Nov 17, 1997 at 11:23:19AM -0700, Robert Goodwin wrote:
I'm having a bit of a problem getting my OS loader to boot Linux using
LILO. I downloaded some instructions from www.windows-nt.com/multiboot on
this but they aren't working correctly although it seems like they should.
what
Hi there,
I'm having a bit of a problem getting my OS loader to boot Linux using
LILO. I downloaded some instructions from www.windows-nt.com/multiboot on
this but they aren't working correctly although it seems like they should.
what I've done is first installed LILO in the superblock of my
Joy. I've installed Debian 1.3.1 fresh on a 486/66 with ~4 megs of ram.
This machine is to be a router for home, but right after the install when I'm
to reboot and see how my system goes, I get this as an error message when LILO
won't load:
3FA:
Yup. That's it. That on a line.
On Aug 22, Paul Lange wrote
Joy. I've installed Debian 1.3.1 fresh on a 486/66 with ~4 megs of ram.
This machine is to be a router for home, but right after the install when I'm
to reboot and see how my system goes, I get this as an error message when LILO
won't load:
3FA:
Yup.
94 matches
Mail list logo
