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
par
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
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 Deb
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
>
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 d
* Ross Boylan ([EMAIL PROTECTED]) [030629 00:24]:
> Here's the lilo.conf for debian that doesn't work for the RH sections.
How does it not work? Does lilo not run (i.e. refuses to install in
/dev/sda)? Do you get a LILO prompt? Does the kernel begin to load and
but fail to load the initrd?
goo
Aryan Ameri wrote:
> I don't have RedHat, so I can't verify that, but it seems we have the
> same problem.
>
> Any suggestions anyone?
It sounds like these distributions are using an initrd, and your lilo
setup is not passing the necessary parameters to the kernel to get it
mounted, maybe?
--
On Friday 27 June 2003 04:43 pm, Ross Boylan wrote:
> On Fri, 2003-06-27 at 13:39, Bijan Soleymani wrote:
> > On Fri, 2003-06-27 at 12:51, Ross Boylan wrote:
> > > To clarify: I mounted the red hat partitions under /red when running
> > > Debian. My understanding is the lilo's map, and so it's boo
On Fri, 27 Jun 2003 14:51:54 -0700
Ross Boylan <[EMAIL PROTECTED]> wrote:
> image=/red/boot/vmlinuz-2.4.20-18.9smp
> label=linux
> initrd=/red/boot/initrd-2.4.20-18.9smp.img
> read-only
> append="hdb=ide-scsi root=LABEL=/"
> root=/dev/sda2
What's "root=LABEL=/"?
I'd
On 26 Jun 2003 17:57:34 -0700
Ross Boylan <[EMAIL PROTECTED]> wrote:
> I got a system with Red Hat 9 preinstalled, booting with lilo. After
> making some space, I installed Debian (testing) on it. I thought it
> would be good to preserve the ability to boot into RH, so I mounted its
> partitions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Jun 27, 2003 at 02:51:54PM -0700, Ross Boylan wrote:
> image=/red/boot/vmlinuz-2.4.20-18.9smp
> label=linux
> initrd=/red/boot/initrd-2.4.20-18.9smp.img
> read-only
> append="hdb=ide-scsi root=LABEL=/"
> root=/dev/
Here's the lilo.conf for debian that doesn't work for the RH sections.
I've deleted 2 additional stanzas that are variations on the ones you see below:
prompt
timeout=50
#compact
default=debian
boot=/dev/sda
lba32
install=/boot/boot-menu.b
map=/boot/map
vga=0xa
image=/vmlinuz
label=debian
On Fri, 2003-06-27 at 13:39, Bijan Soleymani wrote:
> On Fri, 2003-06-27 at 12:51, Ross Boylan wrote:
> > To clarify: I mounted the red hat partitions under /red when running
> > Debian. My understanding is the lilo's map, and so it's boot process,
> > use absolute disk locations and so shouldn't
On Fri, 2003-06-27 at 12:51, Ross Boylan wrote:
> To clarify: I mounted the red hat partitions under /red when running
> Debian. My understanding is the lilo's map, and so it's boot process,
> use absolute disk locations and so shouldn't care how I get to the
> files. The lilo.conf under Debian r
On Thu, 2003-06-26 at 20:57, Ross Boylan wrote:
> I got a system with Red Hat 9 preinstalled, booting with lilo. After
> making some space, I installed Debian (testing) on it. I thought it
> would be good to preserve the ability to boot into RH, so I mounted its
> partitions under /red in linux
t
n to the kernel
> (it is already getting that option).
I have the same problem with booting Mandrake 9.1 using Debian Lilo. I
can boot other distros OK (like slack) but I get the same kernel panic
message when booting mandrake 9.1
I don't have RedHat, so I can't verify that, but it seem
On Fri, Jun 27, 2003 at 03:53:16AM -0400, Bijan Soleymani wrote:
> On Thu, 2003-06-26 at 20:57, Ross Boylan wrote:
> > I got a system with Red Hat 9 preinstalled, booting with lilo. After
> > making some space, I installed Debian (testing) on it. I thought it
> > would be good to preserve the abi
I got a system with Red Hat 9 preinstalled, booting with lilo. After
making some space, I installed Debian (testing) on it. I thought it
would be good to preserve the ability to boot into RH, so I mounted its
partitions under /red in linux, and modified its lilo.conf to use these
new paths. (Tha
Graeme Orton wrote:
>
>Hi i have my hard drive partisioned. One for Linux (debian) and the
>other for windows. I had lilo configured to load windows as default
>and to stop it i pressed 'shift' to boot debian. I recently >installed
>windows-xp professional and lilo load has dissapereard and >i c
> Windows rewrites the MBR on install and makes itself the default OS by
> setting it's own partition active.
>
> To fix this you can either:
>
> 1) Boot from a Linux boot disk (such as you hopefully made during the
> Debian install) and reinstall Lilo.
>
1.5) Boot from debian Rescue disk, (most
Windows rewrites the MBR on install and makes itself the default OS by
setting it's own partition active.
To fix this you can either:
1) Boot from a Linux boot disk (such as you hopefully made during the
Debian install) and reinstall Lilo.
2) Boot from a DOS/Win9XX boot disk and run fdisk to set
On Thu, 15 Nov 2001 13:41:02 +
"Graeme Orton" <[EMAIL PROTECTED]> wrote:
> Hi i have my hard drive partisioned. One for Linux (debian) and the other for
> windows. I had lilo configured to load windows as default and to stop it i
> pressed 'shift' to boot debian. I recently installed windo
windows installations tend to take over the boot partition, and windows
per se is unable to see anything but itself. if you've made a linux boot
disk, you can get in and hack lilo. otherwise, i think you need to get
hold of something like partition magic to restore the original mbr. i've
never used
Hi i have my hard drive partisioned. One for Linux (debian) and the other for windows. I had lilo configured to load windows as default and to stop it i pressed 'shift' to boot debian. I recently installed windows-xp professional and lilo load has dissapereard and i cant get in linux. Does windo
I installed Debian 2.2 (Potato) from CD. Hard Disk has
win 95(hda1)and linux (hda2)LiLo was installed in
MBR.Pl advise to configure to load Windows and LINUX.
Whithout losing contents on the HD.
__
Do You Yahoo!?
Get personalized email addresses from
o: Brian Morgan
> Subject: Re: trouble installing debian -LILO freezing
>
>
> On Wed, Jan 20, 1999 at 03:25:11PM -0600, Brian Morgan wrote:
> > An addendum to my 2 previous posts.
> >
> > I can go all the way through setup: partitioning OK, loading devices OK,
> > inst
An addendum to my 2 previous posts.
I can go all the way through setup: partitioning OK, loading devices OK,
installs and configures base system OK. I chose not to configure PCMCIA
support this time, and I've stopped getting the "problem extracting Base
System from /target/base2_1.tgz" error mess
27 matches
Mail list logo
