On Mon, Feb 25, 2008 at 10:13:48AM -0500, Douglas A. Tutty wrote:
> On Sun, Feb 24, 2008 at 10:14:54PM +, Richard Lyons wrote:
[..]
> >
> > As I said, I am at home with fdisk and parted. And can boot from
> > knoppix and copy a whole partition off when I need to, whereas knoppix
> > doesn't
On Sun, Feb 24, 2008 at 10:14:54PM +, Richard Lyons wrote:
> On Sun, Feb 24, 2008 at 04:25:02PM -0500, Douglas A. Tutty wrote:
> >
> > What warnings did you get about LVM? It is rather nice to be able to
> > resize partitions, but also migrate partitions of of failing drives. On
> > all my o
On Sun, Feb 24, 2008 at 04:25:02PM -0500, Douglas A. Tutty wrote:
>
> What warnings did you get about LVM? It is rather nice to be able to
> resize partitions, but also migrate partitions of of failing drives. On
> all my old boxes (that are still new enough to run Debian), drive
> failures sta
On Sun, Feb 24, 2008 at 07:14:02PM +, Richard Lyons wrote:
> On Sun, Feb 24, 2008 at 12:22:59PM -0500, Douglas A. Tutty wrote:
> > On Sun, Feb 24, 2008 at 12:16:34PM +, Richard Lyons wrote:
> > I hope you kept backups and if not, make a full set before you do
> > anything else. That is,
On Sun, Feb 24, 2008 at 12:22:59PM -0500, Douglas A. Tutty wrote:
> On Sun, Feb 24, 2008 at 12:16:34PM +, Richard Lyons wrote:
> > Silly situation: I have been wanting to release my etch install from
> > the LVM so as to be able to adjust the partitioning. The arrangement
[...]
> > Problem
On Sun, Feb 24, 2008 at 12:16:34PM +, Richard Lyons wrote:
> Silly situation: I have been wanting to release my etch install from
> the LVM so as to be able to adjust the partitioning. The arrangement
> was:
[snip: old LVM setup] See my note at the bottom.
> /usr used also to be in the LVM
Hi all.
Silly situation: I have been wanting to release my etch install from
the LVM so as to be able to adjust the partitioning. The arrangement
was:
/dev/mapper/Debian-root on / type ext3 (rw,errors=remount-ro)
/dev/hda1 on /boot type ext3 (rw)
/dev/mapper/Debian-home on /home type ext3 (rw)
/
for me (TM)
But on resume the user interface module must be present in an initrd
image in order to show up.
So I am trying to create an initrd image with just 3 things in it that I
have entered into /etc/mkinitrd/modules:
suspend2ui_fbsplash
suspend2ui_text
suspend2ui_usplash
and those I
On Thu, 2006-11-02 at 07:13 -0600, Hugo Vanwoerkom wrote:
> Hi,
>
> FATAL: Module suspend2ui_fbsplash not found.
> FATAL: Module suspend2ui_text not found.
> FATAL: Module suspend2ui_usplash not found.
>
> Question:
>
> These are "user built" modules and not kernel built modules, they don't
>
resume the user interface module must be present in an initrd
image in order to show up.
So I am trying to create an initrd image with just 3 things in it that I
have entered into /etc/mkinitrd/modules:
suspend2ui_fbsplash
suspend2ui_text
suspend2ui_usplash
and those I have place in directory
Hi All,
I am trying to create a ramdisk image using mkinitrd command. But i
get the following problem.
I will be thankful for any help in this regard.
[EMAIL PROTECTED]:/boot$ sudo mkinitrd -o /initrd.img-2.6.16 2.6.16
find: warning: you have specified the -mindepth option after a
non-option
some help
>
> modules below that the script complains of are compiled into the
> kernel.
>
> uname -a
> Linux fai-amd64 2.6.15modules #1 Tue Mar 7 16:19:18 EST 2006 x86_64
> GNU/Linux
>
>
> # mkinitrd -o ./initrd-2.6.15modules.img 2>&1 | tee log
> /usr/sb
ins of are compiled into the
kernel.
uname -a
Linux fai-amd64 2.6.15modules #1 Tue Mar 7 16:19:18 EST 2006 x86_64
GNU/Linux
# mkinitrd -o ./initrd-2.6.15modules.img 2>&1 | tee log
/usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed
FATAL: Module sg not found.
FATAL: Module mptspi
ins of are compiled into the
kernel.
uname -a
Linux fai-amd64 2.6.15modules #1 Tue Mar 7 16:19:18 EST 2006 x86_64
GNU/Linux
# mkinitrd -o ./initrd-2.6.15modules.img 2>&1 | tee log
/usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed
FATAL: Module sg not found.
FATAL: Module mptspi
Hi all,
I write this e-mail a bit upset after spending three days trying to install
a new kernel with bootsplash and suspend2. And I write this to avoid anybody
else to spend the same. I do not know who must solve this, but I think that
there is a problem with bootsplash or mkinitrd. I can
On Fri, Jul 01, 2005 at 01:54:55PM +0200, Tom Larard wrote:
> Hi,
>
> I'd like to mount my root partition on /dev/evms/hda1. Currently it is
> mounted on /dev/hda1. (The reason for wanting to do this is so I can
> use hda[2-10] with evms)
>
> Mkinitrd correctly probe
Hi,
I'd like to mount my root partition on /dev/evms/hda1. Currently it is
mounted on /dev/hda1. (The reason for wanting to do this is so I can
use hda[2-10] with evms)
Mkinitrd correctly probes my root device (as it is now), and notices
that it is not an evms volume, and hence exclude
On 2005-05-25, Ibrahim Mubarak <[EMAIL PROTECTED]> wrote:
> OK. So I went ahead and downloaded the latest kernel off of kernel.org,
> compiled it and installed it. Still mkinitrd doesn't output the image.
I don't know much about this, but perhaps it's as simple as
&q
fter
> > > compiling the modules using "make modules." There is a more
> > > fundamental
> > > issue here, however, regarding custom kernels in a debian system,
> > > which I
> > > address below.
> > >
> > > >
> > > >
Ibrahim Mubarak wrote:
Well, I am not bypassing anything. I am using make-kpkg. I use this
guide http://newbiedoc.sourceforge.net/system/kernel-pkg.html.en
| Sorry. Your mention of grabbing a kernel off of kernel.org is what
threw me off. I had thought you had to use the debian-patched k
a more
> > fundamental
> > issue here, however, regarding custom kernels in a debian system,
> > which I
> > address below.
> >
> > >
> > > OK. So I went ahead and downloaded the latest kernel off of
> > kernel.org,
> > > compiled it and
k to the debien kernel-source package and did the whole thing again
(configure / clean / compile / install) using make-kpkg and making sure
the initrd option is turned on, but I still got the same results : no
initrd image created at installation time, and no initrd image created
using mkinitrd manu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ibrahim Mubarak said:
> OK. So I went ahead and downloaded the latest kernel off of kernel.org,
> compiled it and installed it. Still mkinitrd doesn't output the image.
> So I tried to mkinitrd of the running kernel. Still nothing. I am
Ibrahim Mubarak wrote:
Well, I am not bypassing anything. I am using make-kpkg. I use this
guide http://newbiedoc.sourceforge.net/system/kernel-pkg.html.en
Sorry. Your mention of grabbing a kernel off of kernel.org is what
threw me off. I had thought you had to use the debian-patched kernel
Charles Hallenbeck wrote:
On Wed, 25 May 2005, Marty wrote:
apt-get install make-kpkg;man make-kpkg
I tried to fetch that package, with this result:
hhs48:~# apt-get install make-kpkg
Reading Package Lists... Done
Building Dependency Tree... Done
E: Couldn't find package make-kpkg
I am tra
On Wed, 25 May 2005, Marty wrote:
apt-get install make-kpkg;man make-kpkg
I tried to fetch that package, with this result:
hhs48:~# apt-get install make-kpkg
Reading Package Lists... Done
Building Dependency Tree... Done
E: Couldn't find package make-kpkg
I am tracking unstable through mirr
debian system,
> which I
> address below.
>
> >
> > OK. So I went ahead and downloaded the latest kernel off of
> kernel.org,
> > compiled it and installed it. Still mkinitrd doesn't output the
> image.
>
> I don't know anything about initrd since I always
below.
but
I wanted to see what happens. And still, my initrd image won't show
up.
mkinitrd did not come back with an error this time, not even saying
that it did not create it. Did an updatedb and then a locate and
nothing comes up. Checked both / and /boot and still no image.
I checked th
t;
> error. So, I went and created it manually. I know I shouldn't have,
> but
> I wanted to see what happens. And still, my initrd image won't show
> up.
> mkinitrd did not come back with an error this time, not even saying
> that it did not create it. Did an updatedb an
. And still, my initrd image won't show up.
mkinitrd did not come back with an error this time, not even saying
that it did not create it. Did an updatedb and then a locate and
nothing comes up. Checked both / and /boot and still no image.
I checked the bugs on initrd-tools, but nothing about
If "the debian way" isn't your preferred cup of tea (so you can also use
it for future systems which may not be debian..)
I have always used what was in the original email [mkinitrd -k -o
/boot/initrd-2.6.9_custom.img -r /dev/hda4 2.6.9custom]
And I compile the root fs (actually, I
On Tue, Dec 28, 2004 at 12:43:10PM -0500, Paul Tsai wrote:
> Andrew,
> I believe if you compile the kernel "the debian way" as they like to
> say on this list. your job is a lot easier.
>
> after configuring your kernel instead of make bzimage, do
> make-kpg --initrd -rev 1 kernel_image
Typo sh
..
dpkg -i
this will install the kernel for you and add appropriate entries in lilo
or grub.
Paul
Andrew Konosky wrote:
I am trying to compile a vanilla 2.6.9 kernel and I have configured it
and compiled it, but the mkinitrd syntax is different from the one I
am used to in Fedora. My kernel modu
I am trying to compile a vanilla 2.6.9 kernel and I have configured it
and compiled it, but the mkinitrd syntax is different from the one I am
used to in Fedora. My kernel modules are in /lib/modules/2.6.9custom and
I want to create an initrd image in /boot/initrd-2.6.9_custom.img.
I ran this
Andrea Tasso wrote:
> I am installing a sarge with uml; everything works well until kernel
> installation, then it tries to start mkinitrd.
> I get something like: uml device is not a valid block device.
> I wanted to bypass the problem commenting out some lines of mkinitrd
> scrip
Hi all,
I am installing a sarge with uml; everything works well until kernel
installation, then it tries to start mkinitrd.
I get something like: uml device is not a valid block device.
I wanted to bypass the problem commenting out some lines of mkinitrd
script, but I cannot find it in the ram
with the amd64 Kernel. This results in a mkinitrd failure,
when installing or upgrading a 32 bit kernel.
The solution is rather simple: Don't upgrade the 32bit Kernel out of an
amd64 Kernel environment. If this has already happened, boot the system
with a 32bit only kernel (for example the non-opti
Michael Spang wrote:
Benedict Verheyen wrote:
Hugo Vanwoerkom wrote:
Good point. So what's the reason that debian kernel images come with
an initrd? An example I can think of is vesafb: in order for that to
be used it must be either builtin or in initrd. Right?
H.
The kernels Debian provides n
Benedict Verheyen wrote:
Hugo Vanwoerkom wrote:
Good point. So what's the reason that debian kernel images come with
an initrd? An example I can think of is vesafb: in order for that to
be used it must be either builtin or in initrd. Right?
H.
The kernels Debian provides need to run on a broad
Hugo Vanwoerkom wrote:
Good point. So what's the reason that debian kernel images come with
an initrd? An example I can think of is vesafb: in order for that to
be used it must be either builtin or in initrd. Right?
H.
The kernels Debian provides need to run on a broad number of machines
hence
Michael Spang wrote:
Shawn McCuan wrote:
This is what i get - but - ive already used make for the modules - -
metion:/home/metiosarius/src/linux-2.6.9# mkinitrd -o
/boot/initrd-2.6.9.img 2.6.9
/usr/sbin/mkinitrd: /lib/modules/2.6.9: Not a directory
/usr/sbin/mkinitrd: MODULES needs to be set to
Shawn McCuan wrote:
This is what i get - but - ive already used make for the modules - -
metion:/home/metiosarius/src/linux-2.6.9# mkinitrd -o
/boot/initrd-2.6.9.img 2.6.9
/usr/sbin/mkinitrd: /lib/modules/2.6.9: Not a directory
/usr/sbin/mkinitrd: MODULES needs to be set to none?
metion:/home
Shawn McCuan wrote:
Ive downloaded, configured, compiled and installed kernel 2.6.9 BUT- .
the only thing I have left to do is "mkinitrd" Im not sure what commands
I should be putting in... im trying:
metion:/home/metiosarius/src/linux-2.6.9# mkinitrd
/boot/initrd-2.6.9.img
Ive downloaded, configured, compiled and installed kernel 2.6.9 BUT- .
the only thing I have left to do is "mkinitrd" Im not sure what
commands I should be putting in... im trying:
metion:/home/metiosarius/src/linux-2.6.9# mkinitrd
/boot/initrd-2.6.9.img 2.6.9
$Id: mkinitrd,v 1.2
t the initrd is the problem and tried making my own initrd:
mkinitrd -o /boot/initrd.img-2.6.8.10sep2004 2.6.8.10sep2004
This returns with an error:
/usr/sbin/mkinitrd: /dev/mapper/main-lv_swap: Kernel does not support LVM
Weird because the standard 2.6.7 kernel in debian does support
I'm having problems creating an mkinitrd image where I want the /
directory to be lvm2.
Setup:
o Using stock 2.6.7-k7-smp w/ udev
o Volume group named "vg" created from /dev/md1
o Logical volume "root" on "vg"
=> result: a lvm2 device called "/d
On Thursday 22 July 2004 15:57, Alec Berryman wrote:
> I'm trying to do software raid on a fresh install of Woody with a
> 2.4.26 kernel. In order to load the software raid I need to make an
> initrd image, so I installed initrd-tools. However, when I run
> mkinitrd, I get the
#x27;m trying to do software raid on a fresh install of Woody with a
> 2.4.26 kernel. In order to load the software raid I need to make an
> initrd image, so I installed initrd-tools. However, when I run
> mkinitrd, I get the following message:
>
> # mkinitrd -o /boot/initrd.im
I'm trying to do software raid on a fresh install of Woody with a
2.4.26 kernel. In order to load the software raid I need to make an
initrd image, so I installed initrd-tools. However, when I run
mkinitrd, I get the following message:
# mkinitrd -o /boot/initrd.img-2.4.26 2.4.26
/usr
/modprobe.conf: No such file or directory
cpio: /lib/modules/modprobe.conf: No such file or directory
With the RAID support compiled in, the error, FATAL: Module raid1 not
found, sounds a bug to me. It was suppressed by changing, ROOT=probe,
to ROOT=, in /etc/mkinitrd/mkinitrd.conf.
My reason to
roblem: since I compiled raid support into my
kernel, it didn't have the raid modules and mkinitrd is being too smart,
trying to add the raid modules anyway.
Sounds like a bug to me.
But this is good news too, since root-on-raid now works with raid modules
and I can now use a stock kernel again. Pro
blem: my kernel didn't have the raid modules and
mkinitrd is being too smart, trying to add the raid modules anyway. Sounds
like a bug to me.
But this is good news too, since root-on-raid now works with raid modules
and I can now use a stock kernel again!
Thanks
Bob
"Justin Guerin"
w I get
>
> Setting up kernel-image-2.6.6-jn040531a (dizzy.1.0) ...
> /usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed
> FATAL: Module raid1 not found.
> Failed to create initrd image.
>
> My system is indeed running raid1, but raid1 support is compiled into the
> ker
Hi,
I'm attempting to upgrade from 2.6.2 to kernel 2.6.6, compiling from the
kernel-source package,
make-kpkg --initrd kernel_image modules_image
and trying to install with dpkg -i
This used to work fine, but now I get
Setting up kernel-image-2.6.6-jn040531a (dizzy.1.0) ...
/usr/sbin/mki
Googling around has suggested that 2.6.5 has changed the parsing of
> >> the "root= " boot argument.
> >
> > No, there is no change in root argument.
> > Of course you can define your partitions on different ways.
> >
> > Are you sure that your roo
Googling around has suggested that 2.6.5 has changed the parsing of
the "root= " boot argument.
No, there is no change in root argument.
Of course you can define your partitions on different ways.
Are you sure that your root device is hdb5 and maybe not hda5?
"Tux:~# /usr/sbin/mkin
Markus Kolb wrote:
> The initrds my installation builds with mkinitrd doesn't work on boot.
> It doesn't matter which kernel I use.
That sounds like a problem with mkinitrd.
> I alway see this message at boot:
> pivot_root: no such file or directory
> /sbin/init: 347
Googling around has suggested that 2.6.5 has changed the parsing of the
"root= " boot argument.
No, there is no change in root argument.
Of course you can define your partitions on different ways.
Are you sure that your root device is hdb5 and maybe not hda5?
"Tux:~# /usr/sbi
.8-bf2.4), which is missing its
modules dependency file (modules.dep), but now find
"Tux:~# /usr/sbin/mkinitrd -m /boot/initrd.img-2.6.5-1-686 -o
2.6.5custom
/usr/sbin/mkinitrd line 1: /boot/initrd.img-2.6.5-1-686: Permission
denied"
What am I missing here ?
Adam Bogacki,
[EMAIL PROTECTED]
Hello,
I have a big problem.
The initrds my installation builds with mkinitrd doesn't work on boot.
It doesn't matter which kernel I use.
I alway see this message at boot:
pivot_root: no such file or directory
/sbin/init: 347: cannot open dev/console : no such file
Kernel panic: Attempt
Yes. I'm using ext3 (only, besides swap) and it's compiled in, not as a
module. I didn't compile in SCSI support but I have no SCSI devices.
--Jeff
On Mon, 2004-04-05 at 17:11, [EMAIL PROTECTED] wrote:
> On Mon, Apr 05, 2004 at 03:30:22PM -0500, Jeff Mitchell wrote:
> > my kernel work just fin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 05 April 2004 12:30 pm, Jeff Mitchell wrote:
> Hello--
>
> For whatever reason I can't boot up a 2.6 kernel (on Sarge-testing)
> without using mkinitrd to generate an initrd file. No Debian 2.6
> HOWTO I've read ha
mkinitrd config not to create a cramfs initrd). The
cramfs initrd patch is shipped with Debian kernel sources.
When my first kernel 2.6.4 wouldn't boot (like yours) I went back to this doc
and added --initrd as it says, then everything worked fine.
> On Mon, Apr 05, 2004 at 03:30:22
I had the same error,
i had to compile ext3 and reiserfs and scsi into the kernel (not as a
module) to solve it
On Mon, 05 Apr 2004 15:30:22 -0500, Jeff Mitchell <[EMAIL PROTECTED]>
wrote:
Hello--
For whatever reason I can't boot up a 2.6 kernel (on Sarge-testing)
without using
On Mon, Apr 05, 2004 at 03:30:22PM -0500, Jeff Mitchell wrote:
> my kernel work just fine.
>
> Can anyone tell me why this is happening?
Did you compiled in support for your filesystem?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROT
Hello--
For whatever reason I can't boot up a 2.6 kernel (on Sarge-testing)
without using mkinitrd to generate an initrd file. No Debian 2.6 HOWTO
I've read has this step, and a friend who has build kernels on
Woody-testing has never had to do it.
If I don't have an initrd and a
I've just build my new 2.6.4 kernel from the kernel sources but I can't
build the initrd.img because
mkinitrd -o /boot/initrd-2.6.4.img /lib/modules/2.6.4
FATAL: Module ide_disk not found.
FATAL: Module ata_piix not found.
FATAL: Module sd_mod not found.
I've tried to look
Can anyone point me to some docs online discussion how to
setup an initrd kernel image with mkinitrd and getting it to work with
lilo?
Christopher J. Noyes
kernel compile to include all required modules.
I really wanted to use apt-get/dpkg to install kernel upgrades straight
from the official Debian binaries, so I spent some time and got Debian's
mkinitrd script working with root on LVM on RAID.
NOTE: This procedure does *NOT* require any modifica
On Fri, Oct 24, 2003 at 07:28:49PM +0200, W. Borgert wrote:
> the combination of raid1, reiserfs, and mkinitrd works sort of.
> An admin and me have still two problems:
>
> - a lot of modules are loaded unnecessarily
>
> - on boot (it seems) the devices are probed for diff
On Fri, Oct 24, 2003 at 07:28:49PM +0200, W. Borgert wrote:
> Hi,
>
> the combination of raid1, reiserfs, and mkinitrd works sort of.
> An admin and me have still two problems:
>
> - a lot of modules are loaded unnecessarily
>
> - on boot (it seems) the devices are p
Hi,
the combination of raid1, reiserfs, and mkinitrd works sort of.
An admin and me have still two problems:
- a lot of modules are loaded unnecessarily
- on boot (it seems) the devices are probed for different file systems
until reiserfs is found
We tried different things, like setting /etc
Ron Rademaker wrote:
Hello,
This 'll probably be a piece of cake for those of you who have any
experience using mkinitrd, I found a howto on how to get my raid system
to work. However I gotta make an image, the howto was written for RH and
the mkinitrd of Debian seems to be something els
Hello,
This 'll probably be a piece of cake for those of you who have any
experience using mkinitrd, I found a howto on how to get my raid system
to work. However I gotta make an image, the howto was written for RH and
the mkinitrd of Debian seems to be something else. If anyone could tel
On Fri, 30 May 2003 00:50:55 +0200 (MEST)
Axel Gerster <[EMAIL PROTECTED]> wrote:
> Well, I have a Highpoint HPT370A Raid Controller. Highpoint offers just an
> module (which works) but no kernel patch. Due the fact, that I want / to
> reside on the raid, I think the module should be in the initrd
> This question is not easy to answer without knowing more about what you have
> and what you're trying to do.
>
> Can you explain what kind of hardware you're trying to support, what
> distribution of Debian (and which kernel) you're running, and what you need
> to do? In particular, why do you th
> cp initrd.img initrd.gz
> gunzip initrd.gz
> mkdir mnt
> mount -o loop initrd mnt
> Now, copy whatever you want into mnt/...
> umount initrd
> gzip initrd
> cp initrd.gz initrdnew.img
Well, thx. But there are two more problems then. How to get the module
loaded and the error "disk full".
Yours
On Thu, 29 May 2003 17:50:10 +0200, Axel Gerster wrote:
>> > can someone please explain to me how to get an module into an existing
>> > initrd.img and get it loaded on bootup? Or does someone know a good
>> > howto?
>>
If you just want to add a module, and not recreate it from scratch, try
this:
On Thu, 29 May 2003 17:22:18 +0200 (MEST)
Axel Gerster <[EMAIL PROTECTED]> wrote:
> I only have the source code for a module. How to patch it into the kernel?
This question is not easy to answer without knowing more about what you have
and what you're trying to do.
Can you explain what kind of h
On Thursday 29 May 2003 11:22, Axel Gerster wrote:
> > Would it be easier for you to embed the module into the kernel?
>
> I only have the source code for a module. How to patch it into the kernel?
1) run make menuconfig
2) read "Legend" in Main Menu
--
Mike M.
--
To UNSUBSCRIBE, email to [EMA
> > can someone please explain to me how to get an module
> > into an existing initrd.img and get it loaded on bootup?
> > Or does someone know a good howto?
>
> Have you checked the Kernel HOWTO?
Yes, I have. But the Explanation there does not contain any things like:
Which files do I need. Which
On Wednesday 28 May 2003 16:22, Axel Gerster wrote:
> Hello,
>
> can someone please explain to me how to get an module
> into an existing initrd.img and get it loaded on bootup?
> Or does someone know a good howto?
Have you checked the Kernel HOWTO?
If you look back through the archives of this l
Hello,
can someone please explain to me how to get an module
into an existing initrd.img and get it loaded on bootup?
Or does someone know a good howto?
Thx.
Axel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
dule, and the default mkinitrd scripts ignore it.
I managed to get it working by doing the following (I think):
/etc/mkinitrd/modules:
isa-pnp
aha1542 aha1542=0x130
/etc/mkinitrd/mkinitrd.conf:
MODULES=most
/etc/mkinitrd/scripts/inst-pnp:
#!/bin/sh
mkdir $INITRDDIR/$MODULEDIR/kerne
source was obtained from
the kerne-source-2.4.20-5 package.
2. The format of /etc/mkinitrd/modules
According to the example for wd8003 in /etc/mkinitrd/modules and to
the mkinitrd man page,
You can also specify modules
to load by putting them in
, January 21, 2003 2:21 PM
To: '[EMAIL PROTECTED]'; [EMAIL PROTECTED]
Subject: RE: mkinitrd trouble
_I_AM_NO_EXPERT_
Did you compile the kernel with cramfs, also?
You didn't mention it.
-Original Message-
From: James Miller [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 21,
on Tue, Jan 21, 2003 at 12:49:13PM -0600, James Miller wrote about mkinitrd trouble:
> Hello all
>
> I am pulling my hair trying to get Debian Woody to boot with an initrd
> image. I have compiled the kernel 2.4.18 with Loopback device support, RAM
> disk support , 8192KB,
_I_AM_NO_EXPERT_
Did you compile the kernel with cramfs, also?
You didn't mention it.
-Original Message-
From: James Miller [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 21, 2003 2:01 PM
To: [EMAIL PROTECTED]
Subject: mkinitrd trouble
Hello all
I am pulling my hair trying t
On 21 Jan 2003, 12:49:13, James Miller wrote:
> Here is a snippet of lilo.conf
> default=Linux
>
> image=/vmlinuz
> label=Linux
> read-only
>
> image=/vmlinuz
> label=Linux-initrd
> initrd=/inird-2.4.18-12.img
don't you mean
initrd-2.4.18-12.img . . .
> a
Hello all
I am pulling my hair trying to get Debian Woody to boot with an initrd
image. I have compiled the kernel 2.4.18 with Loopback device support, RAM
disk support , 8192KB, and initrd (all compiled into the kernel). I am able
to run mkinird just fine 'mkinird 2.4.18-12 -o /initrd-2.4.18-12
Thanks a lot Colin and Herbert, after updating to the version 2.05b-5 it
works, great! :-)
Am Dienstag, 5. November 2002 15:55 schrieb Colin Watson:
> [Please send replies just to the list, not to my personal address as
> well]
>
> On Tue, Nov 05, 2002 at 03:33:25PM +0100, Pierre Burri wrote:
>
[Please send replies just to the list, not to my personal address as
well]
On Tue, Nov 05, 2002 at 03:33:25PM +0100, Pierre Burri wrote:
> yes, I do have the version 2.05b-4 which seems to be the latest version of
> unstable. where do I find the version 2.05b-5?
In unstable. :) Perhaps your mir
yes, I do have the version 2.05b-4 which seems to be the latest version of
unstable. where do I find the version 2.05b-5?
Am Dienstag, 5. November 2002 12:37 schrieb Colin Watson:
> On Tue, Nov 05, 2002 at 12:21:51PM +0100, Pierre Burri wrote:
> > Hi Herbert,
> > thanks for your answer.
> > I ha
On Tue, Nov 05, 2002 at 12:21:51PM +0100, Pierre Burri wrote:
> Hi Herbert,
> thanks for your answer.
> I had a mistake in fstab, /dev/hda11 was still /mnt/debian insthead of /.
> I corrected that, but there is still a problem with "ldd":
>
> sun:/# dpkg --configure kernel-image-2.4.19-686
> Setti
On Tue, Nov 05, 2002 at 12:21:51PM +0100, Pierre Burri wrote:
> thanks for your answer.
> I had a mistake in fstab, /dev/hda11 was still /mnt/debian insthead of /.
> I corrected that, but there is still a problem with "ldd":
>
> ldd: ./: No such file or directory
You need to install the latest bas
rked fine until
> > the kernel installation (apt-get -y installation
> > kernel-image-2.4.19-686). The problem is with "mkinitrd" that doesn't
> > find the root partition. I can reproduce the problem by invoking directly
> > mkinitrd.
> > I would greatly app
Pierre Burri <[EMAIL PROTECTED]> wrote:
>
> partition and a "mount -t proc proc /proc". Everything worked fine until the
> kernel installation (apt-get -y installation kernel-image-2.4.19-686). The
> problem is with "mkinitrd" that doesn't find the roo
I did a "chroot" to my free
partition and a "mount -t proc proc /proc". Everything worked fine until the
kernel installation (apt-get -y installation kernel-image-2.4.19-686). The
problem is with "mkinitrd" that doesn't find the root partition. I can
re
On Mon, Oct 14, 2002 at 07:14:34AM +0100, Alan Chandler wrote:
>
> My question is, why go to great trouble to store and then change
> real-root-dev. Why can't all of the meat of the action just happen in
> linuxrc and then pivot_root to the original root?
Because 2.4.19 broke automatic module
it.
My question is, why go to great trouble to store and then change
real-root-dev. Why can't all of the meat of the action just happen in
linuxrc and then pivot_root to the original root?
Alan Chandler
- -- Forwarded Message --
Subject: Bug#164498: mkinitrd doesn&#
1 - 100 of 126 matches
Mail list logo
