Re: Lilo warning about /dev/mapper/control

2004-11-09 Thread Rissland, Thorsten
Hello Possible failure is the "make clean, make dep" procedures cleaned not enough. So, here's my workaround. Save your .config and blow your complete kernel-source directory away. Unpack an new kernel-source tar and copy your saved .config in it. Now "make menuconfig" and save your settings by l

Lilo warning about /dev/mapper/control

2004-07-05 Thread Bill Moseley
I'm seeing this upon running lilo: laptop:/home/moseley# lilo /dev/mapper/control: open failed: No such device Is device-mapper driver missing from kernel? /dev/mapper/control: open failed: No such device Is device-mapper driver missing from kernel? Incompatible libdevmapper 1.00.17-ioctl (2004-04

Re: lilo warning

2004-06-08 Thread Alvin Oga
hi ya On Wed, 9 Jun 2004, Glenn Meehan wrote: > When I run lilo I get this warning message: > Warning: Partition 3 on /dev/hda is not marked Active. > What does it mean? means ... i wanna bother you today ... :-) > How can I make it go away? - pull the power to the disk - or - fdisk /dev/h

Re: lilo warning

2004-06-08 Thread Silvan
On Tuesday 08 June 2004 08:58 pm, Glenn Meehan wrote: > When I run lilo I get this warning message: > > Warning: Partition 3 on /dev/hda is not marked Active. > > What does it mean? > > How can I make it go away? Just a guess, but I think it means the "bootable" flag isn't set for the partition.

Re: lilo warning

2004-06-08 Thread Glenn Meehan
On Wed, 2004-06-09 at 10:58, Alvin Oga wrote: > means ... i wanna bother you today ... :-) > > > How can I make it go away? > > - pull the power to the disk - or - > > fdisk /dev/hda > fdisk> a > fdisk> 3 > fdisk> w > > "set the boot flag" on partition 3 Cheers dude, It went away! -- T

lilo warning

2004-06-08 Thread Glenn Meehan
When I run lilo I get this warning message: Warning: Partition 3 on /dev/hda is not marked Active. What does it mean? How can I make it go away? Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Help understanding lilo Warning message.

2003-10-07 Thread Andrés Roldán
I think I have seen it before, but now I'm concerned that > I really don't understand, and it may be important even tho > system is running fine to my untrained eye. > > message: > big:/home/pecondon# lilo > Warning: COMPACT may conflict with LBA32 on some systems >

Help understanding lilo Warning message.

2003-10-07 Thread Paul E Condon
big:/home/pecondon# lilo Warning: COMPACT may conflict with LBA32 on some systems Warning: '/proc/partitions' does not match '/dev' directory structure. Name change: '/dev/ide/host0/bus0/target0/lun0/disc' -> '/dev/hda' The kernel was compiled with

Re: Lilo warning causing problems

2003-01-22 Thread Felipe Martínez Hermo
El Tuesday 21 January 2003 13:19, Seneca escribió: > On Tue, Jan 21, 2003 at 12:44:41PM +0100, Felipe Mart?nez Hermo wrote: > > I have just installed a new Debain box and configured a new > > kernel. I run Lilo and it says: > > > > Warning: Int 0x13 function 8 and function 0x48 return d

Re: Lilo warning causing problems

2003-01-21 Thread Donald Spoon
Felipe Martínez Hermo wrote: Hi all! I have just installed a new Debain box and configured a new kernel. I run Lilo and it says: Warning: Int 0x13 function 8 and function 0x48 return different head/sector geometries for BIOS drive 0x80 (also for drive 0x81) This is usually caused by your

Re: Lilo warning causing problems

2003-01-21 Thread Felipe Martínez Hermo
El Tue, Jan 21, 2003 at 07:19:46AM -0500, Seneca escribió: > On Tue, Jan 21, 2003 at 12:44:41PM +0100, Felipe Mart?nez Hermo wrote: > > I have just installed a new Debain box and configured a new > > kernel. I run Lilo and it says: > > > > Warning: Int 0x13 function 8 and function 0x4

Re: Lilo warning causing problems

2003-01-21 Thread Seneca
On Tue, Jan 21, 2003 at 12:44:41PM +0100, Felipe Mart?nez Hermo wrote: > I have just installed a new Debain box and configured a new > kernel. I run Lilo and it says: > > Warning: Int 0x13 function 8 and function 0x48 return different > head/sector geometries for BIOS drive

Lilo warning causing problems

2003-01-21 Thread Felipe Martínez Hermo
Hi all! I have just installed a new Debain box and configured a new kernel. I run Lilo and it says: Warning: Int 0x13 function 8 and function 0x48 return different head/sector geometries for BIOS drive 0x80 (also for drive 0x81) It installs corre

Re: lilo warning

2002-01-02 Thread Jeff
L Vogtmann, 2002-Jan-01 22:40 -0800: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Tuesday 01 January 2002 09:06 pm, Jeff wrote: > > > Warning: Int 0x13 function 8 and function 0x48 return different > > > head/sector geometries for BIOS drive 0x80 > > > Added Linux > > > Added LinuxOLD

Re: lilo warning

2002-01-02 Thread L Vogtmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 01 January 2002 09:06 pm, Jeff wrote: > > Warning: Int 0x13 function 8 and function 0x48 return different > > head/sector geometries for BIOS drive 0x80 > > Added Linux > > Added LinuxOLD > > Added Windows * > I have found that running lilo

Re: lilo warning

2002-01-01 Thread Jeff
Jeff, 2001-Dec-30 17:46 -0800: > I just did an upgrade on my woody machine using > > apt-get update && apt-get upgrade > > and after make a minor mod to my lilo.conf, and running lilo, I > get the follow error: > > Warning: Int 0x13 function 8 and function 0x48 return different > head/sector geo

lilo warning

2001-12-30 Thread Jeff
I just did an upgrade on my woody machine using apt-get update && apt-get upgrade and after make a minor mod to my lilo.conf, and running lilo, I get the follow error: Warning: Int 0x13 function 8 and function 0x48 return different head/sector geometries for BIOS drive 0x80 Added Linux Added Lin

Re: LILO: Warning: /dev/sda is not on the first disk

2000-09-09 Thread Noah L. Meyerhans
-BEGIN PGP SIGNED MESSAGE- On Sat, 9 Sep 2000, Nate Amsden wrote: > /dev/hda is the first disk. to boot off of /dev/sda you need to > probably reconfigure your BIOS or something to do it, or install LILO to > the MBR on /dev/hda. Yeah, I actually did that before I received this email, b

Re: LILO: Warning: /dev/sda is not on the first disk

2000-09-09 Thread brian moore
On Sat, Sep 09, 2000 at 02:48:02PM -0400, Noah L. Meyerhans wrote: > Can anybody shed some light on the error message above? I get it whenever > I run LILO now, and the system won't boot from the hard drive. The only > change to this system was a new network card (there are now 2) and the new > k

Re: LILO: Warning: /dev/sda is not on the first disk

2000-09-09 Thread Nate Amsden
"Noah L. Meyerhans" wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Can anybody shed some light on the error message above? I get it whenever > I run LILO now, and the system won't boot from the hard drive. The only > change to this system was a new network card (there are now 2) and the new

LILO: Warning: /dev/sda is not on the first disk

2000-09-09 Thread Noah L. Meyerhans
-BEGIN PGP SIGNED MESSAGE- Can anybody shed some light on the error message above? I get it whenever I run LILO now, and the system won't boot from the hard drive. The only change to this system was a new network card (there are now 2) and the new kernel. The kernel works fine, as I hav

Re: New drive--->lilo warning

1998-04-17 Thread Mark Phillips
> Re-arrange your drives like this and let me know if it fixes the situation: > > HDA - ok > HDC - Set as HDB > HDB - Set as HDC (Linux does not care where additional partitions are) I did almost this, except instead of swapping hdb and hdc, I simply detached hdb temporarily. Low and behold it

Re: New drive--->lilo warning

1998-04-16 Thread tko
Mark Phillips writes: [snip] > > Why have two "DOS" bootable drives? In my experience, "DOS" only likes to > > see > > one main bootable drive. [snip] One other item which I did not mention: The bootable "DOS" drive _must_ be the first one detectable by "DOS". > > This is the setup of my three

Re: New drive--->lilo warning

1998-04-16 Thread Marcus . Brinkmann
On Thu, Apr 16, 1998 at 11:01:34AM +0930, Mark Phillips wrote: > > > > I have just installed a third IDE hard drive (my board supports up > > > to 4). I have configured the BIOS. Now I want to use lilo to make it > > > possible to boot from it (it currently has DOS on it), but when I try, > > >

Re: New drive--->lilo warning

1998-04-16 Thread Mark Phillips
On Wed, 15 Apr 1998 [EMAIL PROTECTED] wrote: > Mark Phillips writes: > [snip] > > I tried booting anyway but it failed, complaining that it wasn't a system > > disk. However my Dad (whose disk it was before giving it to me) swears it > > was bootable. > > > > So what's wrong? On my father's com

Re: New drive--->lilo warning

1998-04-16 Thread tko
Mark Phillips writes: [snip] > I tried booting anyway but it failed, complaining that it wasn't a system > disk. However my Dad (whose disk it was before giving it to me) swears it > was bootable. > > So what's wrong? On my father's computer the disk was disk C: where as > now it is /dev/hdc (th

Re: New drive--->lilo warning

1998-04-16 Thread Mark Phillips
> > I have just installed a third IDE hard drive (my board supports up > > to 4). I have configured the BIOS. Now I want to use lilo to make it > > possible to boot from it (it currently has DOS on it), but when I try, > > it comes up with: > > > > # lilo > > Added linux * > > Added dos > > ide

Re: New drive--->lilo warning

1998-04-15 Thread tko
Mark Phillips writes: > > > Hi, > > I have just installed a third IDE hard drive (my board supports up to 4). > I have configured the BIOS. Now I want to use lilo to make it possible to > boot from it (it currently has DOS on it), but when I try, it comes up > with: > > # lilo > Added linux

New drive--->lilo warning

1998-04-15 Thread Mark Phillips
Hi, I have just installed a third IDE hard drive (my board supports up to 4). I have configured the BIOS. Now I want to use lilo to make it possible to boot from it (it currently has DOS on it), but when I try, it comes up with: # lilo Added linux * Added dos ide: probable bad entry for /dev/