I will be happy to post to bugtracker, but I need some help. I have
been flamed/ignored so often on this list that I want to do things
right, and I am NOT a Linux developer, so sometimes the terminology
throws me. In particular right now, I have no idea what you mean by
a "state file".
I have an Akita and have been having no end of problems getting
Angstrom to work on it. I use the Zaurus mostly for auditing Wi-Fi
installations, using kismet to detect rogue access points. That is
what I need the sound for, not playing music.
The base functionality I need consists of:
vim
kismet
nmap
curl
netcat
a simple web browser
a mail client, a little more than mutt, but not fancy
Each of the dozen or more times I have flashed Angstrom I have tried
the most recent version. I have used the NAND restore file from
Trisoft before flashing Angstrom, to ensure a consistent starting
point. Immediately after flashing, I copy over my /etc/network/
interfaces and /etc wpa_supplicant.conf so I have a network. (I've
gotten pretty good at that, and I even think I understand what's
going on!). Then I do ipkg update and start installing the software
in the order shown above, testing all of them after the last one is
installed. I usually get three or four packages installed before
things stop working. Thinking that nmap or curl might be the
culprit, I've tried them in different order, and even bypassing them
entirely, but each time, the symptom I see is that kismet acts as if
there is no network card, even through the card is working fine
otherwise. Of course I have tried a soft boot to see if that has any
effect.
(Tangential question: Does "shutdown -r now" do the same thing as
poking the reset button?)
I have tried ipkg upgrade at various times and various stages in the
process above - it gives many error messages referring to kernel
modules, and finally leaves my Zaurus with no networking and kismet
broken.
So, apart from not knowing what a "state file" is, or where it's
located, or what it represents, my question is how much of the above
types of information should I include in a bug report? From looking
at the reports in bugzilla, it seems to me that eh developers would
rather have solutions posted than problems, and certainly not from
blathering N00Bs like me :-)
Walt
P.S. - as I proofread this, it occurs to me, should I do something
like ipkg upgrade >/mnt/card/somefile and then post the file to
bugzilla? Or is that just being a pain in the a__ to the developers?
W
On Jul 20, 2007, at 10:58 AM, GROG! (Jeff Howie) wrote:
[SNIP]
> Has anyone had luck with akita?
Hi, I have an Akita, and I am using altboot to boot from SD.
I have nearly no problem with audio, just one: the volume is very low,
even if maximised, and I only hear something through headphones.
I made no configurations, just the standard angstrom installed
packages.
I am using xmms for the tests.
Make sure to post your info, problem & state file to the bugtracker:
http://bugs.openembedded.org/show_bug.cgi?id=2667
That's the only way it's gonna get fixed.
[SNIP]
_______________________________________________
Angstrom-distro-users mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
