Hi Quadir,
Make sure you compiled in support (not modules) for your hard disks and
the file system you're using on your root device. Also, what does the
entry in your boot loader configuration file look like?
Cheers,
Matthew James
Kareemullah Quadir wrote:
hi all,
i am a newbie at linux kern
hi all,
i am a newbie at linux kernel compilation. i have a hp pavilion
zt1135 laptop and recently i installed redhat 8 and downloaded the latest
kernel 2.4.20, compiled and installed it. after i reboot to the new
kernel, i get the following message and the system hangs:
VFS: cannot open root de
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 11 Feb 2003 13:12:24 +, Neil Bird wrote:
> Around about 10/02/2003 13:36, Robert P. J. Day typed ...
> > if you want to use the "root=LABEL=/" label notation, then you need
> > to use the initrd, or build ext3 support right into the kernel
>What *is* the LABEL notation all about? I've only ever come across
> /dev/xxx ...
The Label puts a name for the partition which is the same regardless of
weather or not the hard drive stays in the same position, i.e move
drive from hda to hdb grub will still find the partitions.
--
D
Around about 10/02/2003 13:36, Robert P. J. Day typed ...
if you want to use the "root=LABEL=/" label notation, then you need
to use the initrd, or build ext3 support right into the kernel.
if you're happy with the /dev notation, you're fine without it.
What *is* the LABEL notation all about?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 10 February 2003 07:45 am, Jesse Keating wrote:
> On Monday 10 February 2003 05:36, Robert P. J. Day uttered:
> > if you want to use the "root=LABEL=/" label notation, then you
need
> > to use the initrd, or build ext3 support right into the
On Monday 10 February 2003 05:36, Robert P. J. Day uttered:
> if you want to use the "root=LABEL=/" label notation, then you need
> to use the initrd, or build ext3 support right into the kernel.
> if you're happy with the /dev notation, you're fine without it.
>
> once upon a time, i knew why this
On Mon, 10 Feb 2003, Mark Hoover wrote:
> Jesse,
>
> Thanks for the help. I tried this over the weekend and amazingly enough
> it works great. I was seriously expecting some kind of boot error by leaving
> that initrd line out.
>
> I will note however, RH7.x used a root=/dev/ notation for it's
perfectly.
--
Mark Hoover
District Network Engineer
Norfolk Public Schools
628-3810 x3045
>>> [EMAIL PROTECTED] 02/07/03 02:52PM >>>
Message: 5
From: Jesse Keating <[EMAIL PROTECTED]>
Organization: j2Solutions
To: [EMAIL PROTECTED]
Subject: Re: Kernel Comp
On Friday 07 February 2003 09:58, Mark Hoover wrote:
> I recently installed RH8 on a 486 system that I want to use as a
> gateway/router machine. When I compile the 2.4.20 kernel, I for some
> reason end up with a initrd-2.4.20.img file. I specifically told
> menuconfig that I did *not* want to u
Greetings everyone..
I have a question that seems to be a bit of a mystery.
I recently installed RH8 on a 486 system that I want to use as a gateway/router
machine. When I compile the 2.4.20 kernel, I for some reason end up with a
initrd-2.4.20.img file. I specifically told menuconfig
I'll try that. I have been able to not do a mrproper in the past when I
wanted to just change one item of a configuration.
Thanks
Steve
On Mon, 2002-11-04 at 16:19, Jesse Keating wrote:
> On 04 Nov 2002 16:06:20 -0800
> Steve White <[EMAIL PROTECTED]> wrote:
>
> # make xconfig
> # make dep
> #
On 04 Nov 2002 16:06:20 -0800
Steve White <[EMAIL PROTECTED]> wrote:
# make xconfig
# make dep
# make bzImage
# Error 2
you forgot make mrproper.
--
Jesse Keating
j2Solutions.net
Mondo DevTeam (www.mondorescue.org)
Was I helpful? Let others know:
http://svcs.affero.net/rm.php?r=jkeating
make xconfig
make dep
make bzImage
Error 2
Steve
On Mon, 2002-11-04 at 15:47, Rinaldi J. Montessi wrote:
> Steve White wrote:
> >
> > here is the error output when the make bzImage fails:
> >
> > make[3]: *** No rule to make target
> > `/usr/src/linux-2.4.18-17.8.0/drivers/pci/devlist.h', neede
Steve White wrote:
>
> here is the error output when the make bzImage fails:
>
> make[3]: *** No rule to make target
> `/usr/src/linux-2.4.18-17.8.0/drivers/pci/devlist.h', needed by
> `names.o'. Stop.
> make[3]: Leaving directory `/usr/src/linux-2.4.18-17.8.0/drivers/pci'
> make[2]: *** [first_
here is the error output when the make bzImage fails:
make[3]: *** No rule to make target
`/usr/src/linux-2.4.18-17.8.0/drivers/pci/devlist.h', needed by
`names.o'. Stop.
make[3]: Leaving directory `/usr/src/linux-2.4.18-17.8.0/drivers/pci'
make[2]: *** [first_rule] Error 2
make[2]: Leaving direc
Greetings.
I have been unable to compile a kernel on red hat 8.0. I need to
include NTFS read support to back up an unbootable NT partition. I have
tried to compile on several occasions and get an error 2 during the make
modules routine.
Is there something broken in the Gcc libraries as
On Mon, 2002-10-14 at 02:05, Jack Bowling wrote:
> > Iirc RH selects the proper System.map automagically at boot depending on
> > the kernel it used so no need to do the rm -f ... & ln -s ...
>
> Ah. Didn't know that. This is the case for 2.5.x devel branch so RH likely
> backported it.
The /etc/
** Reply to message from Patrick <[EMAIL PROTECTED]> on Mon, 14 Oct 2002
07:28:20 +0200
> On Mon, 2002-10-14 at 03:42, Jack Bowling wrote:
> > cp /usr/src/linux-2.4.19/System.map /boot/System.map-2.4.19
> > rm -f /boot/System.map
> > ln -s System.map-2.4.19 System.map
>
> Iirc RH selects the pro
Either I found something, or it just works for me.
My procedure is as follows:
make mrproper
make distclean
make xconfig& (to keep the shell open)
make dep bzImage modules modules_install
make install
lilo
Then I do a dd of the boot sector which is alias in my bash like this:
alias ddlilo='dd if
On Mon, 2002-10-14 at 01:28, Patrick wrote:
> On Mon, 2002-10-14 at 03:42, Jack Bowling wrote:
> > cp /usr/src/linux-2.4.19/System.map /boot/System.map-2.4.19
> > rm -f /boot/System.map
> > ln -s System.map-2.4.19 System.map
>
> Iirc RH selects the proper System.map automagically at boot depending
On Mon, 2002-10-14 at 03:42, Jack Bowling wrote:
> cp /usr/src/linux-2.4.19/System.map /boot/System.map-2.4.19
> rm -f /boot/System.map
> ln -s System.map-2.4.19 System.map
Iirc RH selects the proper System.map automagically at boot depending on
the kernel it used so no need to do the rm -f ... &
Thanks for all the quick replies! I just did the mkinitrd routine,
everything loads fine now. Thanks!
However, the reason I went about getting a new kernel on my system is
I'm trying to get my Lexmark X83 USB working. Other people on the
[EMAIL PROTECTED] have reported (in RH 7.3, Mandra
** Reply to message from Brandon Dorman <[EMAIL PROTECTED]> on Sun, 13 Oct
2002 17:51:02 -0700
> Hello,
>
> I recently compiled the 2.4.19 kernel with the following commands: (i
> just changed the numbers to .19 instead of .17)
>
> tar jxvf linux-2.4.17.tar.bz2
> mv linux linux-2.4.17
>
On Sun, 2002-10-13 at 20:51, Brandon Dorman wrote:
> tar jxvf linux-2.4.17.tar.bz2
> mv linux linux-2.4.17
This should be more like "ln -s linux-2.4.17 linux", no?
> make menuconfig
> make dep
> make clean
> make bzImage
> make modules
> make modules_install
> cp arch/i386/boot/bzImage /
On Sun, 2002-10-13 at 20:51, Brandon Dorman wrote:
> Hello,
>
> I recently compiled the 2.4.19 kernel with the following commands: (i
> just changed the numbers to .19 instead of .17)
>
> tar jxvf linux-2.4.17.tar.bz2
> mv linux linux-2.4.17
> make menuconfig
> make dep
> make clean
> make
On Sun, 2002-10-13 at 20:51, Brandon Dorman wrote:
> Hello,
>
> I recently compiled the 2.4.19 kernel with the following commands: (i
> just changed the numbers to .19 instead of .17)
>
> tar jxvf linux-2.4.17.tar.bz2
> mv linux linux-2.4.17
> make menuconfig
> make dep
> make clean
> make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 13 October 2002 08:51 pm, Brandon Dorman wrote:
> Hello,
>
> I recently compiled the 2.4.19 kernel with the following commands: (i
> just changed the numbers to .19 instead of .17)
>
> tar jxvf linux-2.4.17.tar.bz2
> mv linux linux-2.4.
Hello,
I recently compiled the 2.4.19 kernel with the following commands: (i
just changed the numbers to .19 instead of .17)
tar jxvf linux-2.4.17.tar.bz2
mv linux linux-2.4.17
make menuconfig
make dep
make clean
make bzImage
make modules
make modules_install
cp arch/i386/boot/bzImage /v
29 matches
Mail list logo
