On 22 February 2011 11:27, Luca Niccoli lultimou...@gmail.com wrote:
Compressing my initrd with lzma instead of gzip reduces its size by
30%, so it could fit.
BEWARE though, there could be catches I'm not aware of (I haven't
actually tried booting in this configuration), maybe Martin could
* Jeffrey B. Green j...@kikisoso.org [2011-02-21 15:00]:
Yes. I do have lvm installed for the slug. So, that is a decent size hit...
Can you upload initrd.img-2.6.32-5-ixp4xx somewhere so I can have a
look at it?
Sent to you separately.
Thanks. I generated a ramdisk on my NSLU2 and it
* Luca Niccoli lultimou...@gmail.com [2011-02-22 11:27]:
Compressing my initrd with lzma instead of gzip reduces its size by
30%, so it could fit. BEWARE though, there could be catches I'm not
aware of (I haven't actually tried booting in this configuration),
maybe Martin could enlighten us?
* Björn Wetterbom bjohv...@gmail.com [2011-02-21 21:18]:
So what's the bottom line of this for the average user? Should I
take any precautionary measures before upgrading my slug to Squeeze
(I will of course follow the instructions in the release notes)? Is
it clear why Jeffrey's ramdisk
On 21 February 2011 21:00, Jeffrey B. Green j...@kikisoso.org wrote:
The 8 MB flash is divided into different partitions and the ramdisk
partition is only 6 MB; see http://cyrius.com/debian/nslu2/boot.html
Thanks for the info.
Compressing my initrd with lzma instead of gzip reduces its size
* Jeffrey B. Green j...@kikisoso.org [2011-02-18 13:53]:
# /etc/initramfs-tools/initramfs.conf
# replace most with dep
MODULES=dep
Anyone out there know of any pitfalls in this approach?? I.e. are all
the crucial modules included in the initrd?
Yeah, it should work fine.
Make sure to make
* Jeffrey B. Green j...@kikisoso.org [2011-02-18 11:22]:
One of my slugs is still in the process of upgrading but I noticed
that during the setting up of the 2.6.32-5 kernel that the flashing
failed due to (output message):
I believe some other people are running the 2.6.32-5 kernel on their
On 02/21/2011 11:18 AM, Martin Michlmayr wrote:
* Jeffrey B. Greenj...@kikisoso.org [2011-02-18 13:53]:
# /etc/initramfs-tools/initramfs.conf
# replace most with dep
MODULES=dep
Anyone out there know of any pitfalls in this approach?? I.e. are all
the crucial modules included in the initrd?
So what's the bottom line of this for the average user? Should I take any
precautionary measures before upgrading my slug to Squeeze (I will of course
follow the instructions in the release notes)? Is it clear why Jeffrey's
ramdisk didn't fit in the flash?
Regards
Björn
On Feb 21, 2011 8:39 PM,
On 02/21/2011 11:22 AM, Martin Michlmayr wrote:
* Jeffrey B. Greenj...@kikisoso.org [2011-02-18 11:22]:
One of my slugs is still in the process of upgrading but I noticed
that during the setting up of the 2.6.32-5 kernel that the flashing
failed due to (output message):
I believe some other
Hi everyone,
One of my slugs is still in the process of upgrading but I noticed that
during the setting up of the 2.6.32-5 kernel that the flashing failed
due to (output message):
Running update-initramfs.
update-initramfs: Generating /boot/initrd.img-2.6.32-5-ixp4xx
Running flash-kernel.
On 02/18/2011 11:22 AM, Jeffrey B. Green wrote:
Hi everyone,
[...snip prev msg...]
After unpacking the initrd in order to look where the space is going, I see:
du -sm *
2 bin
1 conf
1 etc
1 init
14 lib
2 sbin
1 scripts
And working my way down I get
On 02/18/2011 11:48 AM, Jeffrey B. Green wrote:
On 02/18/2011 11:22 AM, Jeffrey B. Green wrote:
Hi everyone,
[...snip prev msg...]
[...snip...]
Are all these drivers really necessary?
By configureing the initramfs system, the size can be reduced, e.g. edit
13 matches
Mail list logo
