For people following this thread on debian-arm@, discussion should move
to Debian #621137.
On Wed, Apr 06, 2011, Joey Hess wrote:
> Awesome. I just recovered my nslu2 by flashing firmware from an
> installation of stable.
Now that you recovered your system, you could probably install stable's
Loïc Minier wrote:
> Arnaud Patard looked a bit into this today; we both reproduce in QEMU.
Awesome. I just recovered my nslu2 by flashing firmware from an
installation of stable. Not ideal, but at least my internet gateway
in the cabin is back to using 3 watts rather than the temporary laptop
I
Hey
Arnaud Patard looked a bit into this today; we both reproduce in QEMU.
It seems to be an issue with busybox or the toolchain; replacing
/bin/sh in the initrd with bash works fine. Starting from your initrd
and a bash binary for armel do:
mkdir tmp
cd tmp
gunzip -c
Hi Barry
On Thu, Mar 31, 2011 at 02:28, Barry Tennison wrote:
> I too am having no success at getting sid to boot on nslu2 with (debian
> stock) kernels 2.6.37 and beyond. I know/believe that a number of things
> happened between 2.6.32 and 2.6.37 including:
> - some kind of change around sda
I too am having no success at getting sid to boot on nslu2 with (debian stock)
kernels 2.6.37 and beyond. I know/believe that a number of things happened
between 2.6.32 and 2.6.37 including:
- some kind of change around sda devices, making UUID= or LABEL= parameters
even more advisable in fstab
Gordon Farquharson wrote:
> Hi Joey
>
> On Wed, Mar 23, 2011 at 08:52, Joey Hess wrote:
>
> > I did upgrade busybox, too. Seems likely that the new version
> > (1:1.18.3-1) is miscompiled on armel, then.
>
> So, does this mean you know how to fix the problem? Is there anything
> more I should d
Hi Joey
On Wed, Mar 23, 2011 at 08:52, Joey Hess wrote:
> I did upgrade busybox, too. Seems likely that the new version
> (1:1.18.3-1) is miscompiled on armel, then.
So, does this mean you know how to fix the problem? Is there anything
more I should do?
Gordon
--
Gordon Farquharson
GnuPG Key
On Wed, Mar 23, 2011 at 04:08, Loïc Minier wrote:
> In the bug you pointed at, Dave martin has an useful recipe to start
> debugging issues in the initrd like this one:
> https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/683683/comments/30
The recipe was going so well until:
/ # /mnt/usr/b
Gordon Farquharson wrote:
> I did an upgrade from squeeze to unstable on my test NSLU2. During the
> upgrade, the kernel was upgraded to 2.6.38-1-ixp4xx (Debian 2.6.38-1)
> (did you specially hold the kernel version back at 2.6.32-5-ixp4xx?).
> Booting fails with the following messages:
I don't re
On Tue, Mar 22, 2011, Gordon Farquharson wrote:
> The only thing I can find on the web that seems related is
> https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/683683
The klibc parts of this bug were related to klibc and building in ARM
mode or Thumb mode. The Ubuntu toolchain in maverick a
Hi Joey
On Tue, Mar 22, 2011 at 11:04, Joey Hess wrote:
> Upgraded my nslu2 to unstable and it no longer boots. I don't have the
> cable here to see console, so all I can tell is the kernel seems to
> boot, initramfs may try to mount root (flashes briefly), and all leds
> then remain off forever.
Upgraded my nslu2 to unstable and it no longer boots. I don't have the
cable here to see console, so all I can tell is the kernel seems to
boot, initramfs may try to mount root (flashes briefly), and all leds
then remain off forever.
This upgrade did not change the kernel which remains at 2.6.32-5
12 matches
Mail list logo
