Karsten Merker (2014-10-01):
> Vagrant is right, the script fragment added in V2 for conditionally
> setting the console parameter is the wrong way round. I am very
> much in a hurry now to catch a train and don't want to risk
> breaking anything by rushing an untested last-minute change into
> t
Cyril Brulebois (2014-10-01):
> Karsten Merker (2014-10-01):
> > On Mon, Sep 22, 2014 at 12:17:23AM +0200, Karsten Merker wrote:
> >
> > > I have started working on implementing hd-media support for the
> > > armhf platform in debian-installer.
> > [snip]
> > > I have run some tests with the res
On 2014-09-30 15:47:13 -0700, Karsten Merker wrote:
> * Add the "console=" parameter to bootargs only if ${console}
> is set.
...
> diff --git a/build/boot/arm/bootscr.mainline_common
> b/build/boot/arm/bootscr.mainline_common
...
> +if test -z "${console}"; then
> + setenv bootargs "${boot
Karsten Merker (2014-10-01):
> On Mon, Sep 22, 2014 at 12:17:23AM +0200, Karsten Merker wrote:
>
> > I have started working on implementing hd-media support for the
> > armhf platform in debian-installer.
> [snip]
> > I have run some tests with the resulting tarball contents and a
> > Jesse CD1 i
Thanks Martin, thanks Arnaud,
That's very helpful!
Best regards,
pepesz
On Tue, Sep 30, 2014 at 4:03 PM, Arnaud Patard
wrote:
> Martin Michlmayr writes:
>
> > * pepesz [2014-09-30 13:34]:
> >> That helped, initrd is now 2260857 instead of 7844605.
> >> How can I see which modules comes into
Martin Michlmayr writes:
> * pepesz [2014-09-30 13:34]:
>> That helped, initrd is now 2260857 instead of 7844605.
>> How can I see which modules comes into initrd.
>
> You could unpack it:
>
> cd /tmp/foo
> zcat /boot/initrd.img-... | cpio -i
iirc, there's also a lsinitramfs command.
Arnaud
* pepesz [2014-09-30 13:34]:
> That helped, initrd is now 2260857 instead of 7844605.
> How can I see which modules comes into initrd.
You could unpack it:
cd /tmp/foo
zcat /boot/initrd.img-... | cpio -i
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to debian-arm-requ
On Tue, 2014-09-30 at 08:19 +0100, Ian Campbell wrote:
> On Fri, 2014-09-26 at 00:08 +0100, Ben Hutchings wrote:
> > However, at the moment initramfs-tools won't include PHY drivers even in
> > that configuration.
>
> I spent some time last week hunting for a sysfs link between a device
> and the
Thanks Ian,
That helped, initrd is now 2260857 instead of 7844605.
How can I see which modules comes into initrd.
I have another nslu2 where the upgrade went smoothly with "most" (size only
2884191)
Thanks again,
pepesz
On Tue, Sep 30, 2014 at 11:05 AM, Ian Campbell wrote:
> On Tue, 2014-09-30
On Tue, 2014-09-30 at 09:43 +0200, pepesz wrote:
> Dear All,
>
>
> Up to yesterday I was using debian squeeze on my nslu2.
> Then I decided to upgrade to debian wheezy - changed apt sources and
> did apt-get dist-upgrade.
>
> All the packages were updated but looks like the created image is too
Dear All,
Up to yesterday I was using debian squeeze on my nslu2.
Then I decided to upgrade to debian wheezy - changed apt sources and did
apt-get dist-upgrade.
All the packages were updated but looks like the created image is too big
:( (see below).
Any advice?
Best regards,
pepesz
Setting
On Fri, 2014-09-26 at 00:08 +0100, Ben Hutchings wrote:
> However, at the moment initramfs-tools won't include PHY drivers even in
> that configuration.
I spent some time last week hunting for a sysfs link between a device
and the phys which it is using, without success. Do you have any ideas?
Ia
12 matches
Mail list logo
