Hi,
First of all, this thread has wandered off the subject a bit - perhaps I
should start a new thread? For instance, this is no longer about the
stable 2007 branch.
Alessandro Pellizzari wrote:
I have a Zaurus SL-C860 and iPAQ hx4700, and have been using Narcissus
for a few months now. After some problems getting the images working, I
think I've just about sorted it. I got 'Unable to open an initial
console' on the Zaurus, so I added a few device nodes and it was okay.
Would you mind writing something about it?
Sure. After downloading the Narcissus .tar.bz2, I unpacked that into
the root of the SD card, then:
cd dev
mknod console c 5 1
mknod zero c 1 5
mknod full c 1 7
mknod null c 1 3
mknod tty c 5 0
Some of those devices will already be present, or will be added by udev.
I'm using a CF card, so I needed to create some devices for the
partitions (it has four):
mknod hda b 3 0
mknod hda1 b 3 1
mknod hda2 b 3 2
mknod hda3 b 3 3
mknod hda4 b 3 4
I checked the files in /boot. I currently have:
zImage (symlink to zImage-2.6.21-hh20)
zImage-2.6.21-hh20 (kernel)
In the root dir is a 'linuxrc' symlink to /bin/busybox.
That's all that was necessary for my hx4700, though I found that the
contents of /boot varied a bit - on my Zaurus (SL-C860), there's a
kernel-cmdline file.
I just tried yesterday to generate some narcissus images for spitz, and
all of them were non-working.
They started the image, began installing packages and then got stuck
with no login, no X and no error messages. I even don't know if it
finished installing packages, as the last message was something like
"configuring package XYZ" (I don't remember what packages, it was
different for every image tried).
I had something similar on my SL-C860. For every package installed,
opkg would output a large amount of configuration messages. I think
that it was adding symlinks. I interrupted the package installation and
did it manually. Some of the packages had dependences to others that
were not available. I found it easier to configure Narcissus to make a
small image and add the packages on the installed system. I only had
this symlink thing on the Zaurus - it didn't occur on the hx4700.
Besides, I had a very hard time understanding how to install them. The
Angstrom website has (apparently) no link to narcissus, but even no link
to a kexecboot kernel and installkit. I had to find one on the Omegamoon
blog.
Arghh, I know - the documentation system is messy - not that there are
many docs. The introduction even appears to tell new Angstrom users off
for not reading the Wiki, which is incomplete anyway and has broken
links going off all over the place. I found that I needed a lot of
patience (and coffee).
And then I had to bunzip2 the nascissus images and gzip2 them again
because the updater.sh doesn't recognize bz2.
That's probably because the resources available to the updater
environment are very limited (I think it's just a small ramdisk) and
there wouldn't be space for bzip2.
I ended up leaving kexecboot kernel and reinstalling a 2007 system on a
SD card (and then copying it to the internal microdrive manually).
I think I'm going to be seeing something similar to this when/if I
install Angstrom on my SL-C3100 (forgot the dog name - Borzoi?).
Cheers,
Lex.
_______________________________________________
Angstrom-distro-users mailing list
Angstrom-distro-users@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
