John Doe wrote:
Frank Thommen wrote:
To modify the initrd.img, I took the original CentOS 5.2 image, unpacked
with cpio/gunzip and replaced modules/2.6.18-92.el5/x86_64/e1000e.ko
with a current version. This driver module had been created on a
freshly installed CentOS 5.2 host with kernel
Tru Huynh wrote:
On Thu, Mar 26, 2009 at 05:27:10PM +0100, Frank Thommen wrote:
What cpio options did you use to re-create modules/modules.cgz and then
the initrd.img?
I used `cpio -ovF file` and `cpio -ov -H crc -F file` (I found the
latter on http://sial.org/howto/linux/initrd/). However
On Fri, Mar 27, 2009 at 04:04:40PM +0100, Frank Thommen wrote:
This give a slightly different error message:
[...]
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device NULL or unknown-block(253,3)
Please append a correct root= boot option
Tru Huynh wrote:
On Fri, Mar 27, 2009 at 04:04:40PM +0100, Frank Thommen wrote:
This give a slightly different error message:
[...]
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device NULL or unknown-block(253,3)
Please append a correct root=
Hi,
to install current PC models (with new Intel NICs) via Kickstart/PXE, I
wanted to add the newest e1000e-Treiber to initrd.img. With this
modified image, the Kickstart kernel crashes with the following error
messages:
[...]
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun
Frank Thommen wrote:
To modify the initrd.img, I took the original CentOS 5.2 image, unpacked
with cpio/gunzip and replaced modules/2.6.18-92.el5/x86_64/e1000e.ko
with a current version. This driver module had been created on a
freshly installed CentOS 5.2 host with kernel 2.6.18-92.el5
Frank Thommen wrote:
Hi,
to install current PC models (with new Intel NICs) via Kickstart/PXE, I
wanted to add the newest e1000e-Treiber to initrd.img. With this
modified image, the Kickstart kernel crashes with the following error
messages:
Maybe you need to increase the memory allocated
Frank Thommen wrote:
To modify the initrd.img, I took the original CentOS 5.2 image, unpacked
with cpio/gunzip and replaced modules/2.6.18-92.el5/x86_64/e1000e.ko
with a current version. This driver module had been created on a
freshly installed CentOS 5.2 host with kernel
What cpio options did you use to re-create modules/modules.cgz and then
the initrd.img?
I used `cpio -ovF file` and `cpio -ov -H crc -F file` (I found the
latter on http://sial.org/howto/linux/initrd/). However I could not
find any officially looking information about how the
to install current PC models (with new Intel NICs) via Kickstart/PXE, I
wanted to add the newest e1000e-Treiber to initrd.img. With this
modified image, the Kickstart kernel crashes with the following error
messages:
Maybe you need to increase the memory allocated to ramdisk? by
default I
On Thu, Mar 26, 2009 at 05:27:10PM +0100, Frank Thommen wrote:
What cpio options did you use to re-create modules/modules.cgz and then
the initrd.img?
I used `cpio -ovF file` and `cpio -ov -H crc -F file` (I found the
latter on http://sial.org/howto/linux/initrd/). However I could not
John Doe wrote:
Frank Thommen wrote:
[...]
The new image is considerably bigger than the old one (12 MB vs. 5.7 MB)
which puzzles me, as the driver file itself is 2.8 MB (compared to the
old e1000e.ko with ca 170 KB) [...]
Just wondering... can you safely strip modules like you would
On Thu, 2009-03-26 at 17:49 +0100, Frank Thommen wrote:
John Doe wrote:
Frank Thommen wrote:
[...]
The new image is considerably bigger than the old one (12 MB vs. 5.7 MB)
which puzzles me, as the driver file itself is 2.8 MB (compared to the
old e1000e.ko with ca 170 KB) [...]
On Thu, 2009-03-26 at 14:56 -0400, William L. Maltby wrote:
snip
It's been a long time since I dinked with this stuff, but...
IIRC, there's several levels of strip. One strips everything, save for
s/save/safe/ # RATS!
standalone binaries (not dependent on run-time linking with a
14 matches
Mail list logo
