* 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
chr
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 0xf00
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:
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, e
ilto:[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
-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 output
* 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'
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 sy
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
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 - wha
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 01 01 01..." Any clues what the problem
-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
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 n
"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 kerne
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 oth
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
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 DO
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,
[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 Windows
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 #
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 star
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
regards
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 help
line in my
> config file.
>
> Good 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:
> 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?
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,
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
timeou
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 ker
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
You were referring to System.map for the error messages, not the /boot/map
file used to load the system.
* 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
> 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 n
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.
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
> > 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
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
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
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
http://members.tripod
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.
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
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:
>
On Wed, Jan 27, 1999 at 12:03:40PM -0600, Harrison, Shawn wrote:
>
> /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
/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 obvious
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.
>
> w
> --
> 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.
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:
>
47 matches
Mail list logo
