Thanks to Martin Michlmayr who solved my recent root mount problem. I
have one more problem. My NSLU2 has 64 MB (replaced memory chips, not
stacked), so I replaced Apex using the instructions at
http://www.nslu2-linux.org/wiki/Debian/FatSlug in order to get Apex to
detect it all: I used slugimage
Minus a compiled FUSE package I am curious if a compile using GCC in the NSLU2
(Lenny) of FUSE source would work. I was able to successfully compile it in my
NSLU2 but did not go beyond the "make" stage for fear it might be bogus.
Doug
--
To UNSUBSCRIBE, email to debian-arm-requ...@
I want to run OWFS which requires FUSE. Is there an apt-get package for
Lenny on the NSLU2 ?
Is anyone runing OWFS on the NSLU2 Debian Lenny ?
Doug
--
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.deb
Hi All,
I have been trying to boot my AT91SAM9263EK with Emdebian for a while now
but it keeps giving me errors. After mounting the filesystem, it keeps
giving error regarding ttyS2 - no file or directory.
I have used sudo emsandbox -a arm --create to create the tarball. Copied the
tarball to my
Martin Michlmayr wrote:
* David Given [2009-05-27 10:14]:
(Doesn't Linux have a system call to allow kernel chain-loading?
Would this allow a basic kernel to be loaded from flash that then
invokes a kernel read from a file system elsewhere?)
Yes, it's called kexec.
Alas, it doesn't seem t
* Steinar Midtskogen [2009-05-27 08:34]:
> I've just installed Debian/NSLU2 Stable 5.0.1 from
> http://www.slug-firmware.net/ on an NSLU2, but it wont boot. The
> problem seems to be that it tried to mount root before the disks are
> scanned and ready. I suppose a sleep in the boot scripts would
* David Given [2009-05-27 10:14]:
> (Doesn't Linux have a system call to allow kernel chain-loading?
> Would this allow a basic kernel to be loaded from flash that then
> invokes a kernel read from a file system elsewhere?)
Yes, it's called kexec.
--
Martin Michlmayr
http://www.cyrius.com/
-
Martin Michlmayr wrote:
[...]
If you look at bootcmd_usb you'll see something like "ext2load usb
0:1". 0:1 defines the device and partition.
Unfortunately, I don't know whether you can force any consistent
device naming in u-boot. I suppose you could run:
ext2load usb 0:1
ext2load usb 1
8 matches
Mail list logo