Trying to install from the following directions hasn't worked so far.

http://www.angstrom-distribution.org/zaurus-c7x0-c8x0

I don't recall the errors. If I find time, I'll post them here, but ideally they'll be working soon. The following link is where I downloaded the images from.

http://www.angstrom-distribution.org/unsta.../tosa/20070401/

Trying to find a way to boot angstrom led me to the following page, which was simultaneously amusing, and frustrating, since as of yet, this issue is not resolved.

http://lists.linuxtogo.org/pipermail/angst...rch/000089.html

I'm assuming that we're currently working somewhere along the lines of this thread:

http://lists.linuxtogo.org/pipermail/angst...ril/000137.html


As of yet, I still haven't gotten Angstrom to boot. Any help would be appreciated.

See my message here: http://lists.linuxtogo.org/pipermail/angst...ril/000156.html

Not entirely encouraging, but I still think this is a good way to go.

Try today's build and report/update bugs in the OE bugtracker

will do tonight or tomorrow. I've got a ton of work to do just now

EDIT:

Posted some pusillanimous "stream of conciousness" stuff here, which might make me look stupid, so here's the reader's digest version:

Make sure to flash OZ/Angstrom from a FAT formatted card, or you will end up with errors. That was pretty much the source of my problems with getting angstrom to flash.

The x11 image flashed without error when a FAT formatted card was used to flash. However, I'll state again, that GPE in it's current state is not really suitable for my current needs from my zaurus.

Angstrom Apr 14 build test image

console image: boots fine (thanks for getting rid of the OE splash screen)

upon resume: mixed text from dmesg output, previous console input/output, and maybe some output from the suspend/resume scripts, then
...
power.c: device-level power management is not supported yet
power: requesting system suspend ...
power: requesting system suspend ...
usbcore: deregistering driver prism2_usb
_(underscore sign blinking here)

after pressing enter, device frozen (has to reset).

x11 image: boots fine
suspend/resume worked for the first time, then suspend stops working (see attached suspend.txt)
shutdown -r now has no effect or froze the device

btw: tested with: 4G SD, 512M CF in hda (socket 1), 8G Microdrive (partitioned as 4G vfat + 4G ext2) in hdc (socket 0). Seems all work fine.

The OE bugtracker is at http://bugs.openembedded.org, not here

Agreed, this thread is not a bugtracker. Rather, it is a forum to do more than list bugs.

Would you prefer that no one discuss issues with the angstrom distro outside of the bugtracker and/or wiki?

I did not have time to submit these bugs last night. I will do it tonight. Just wanted to give a heads up in the forum because looks like only few 6k user are subscribed to the OE mailing list or bugtracker.

I would prefer that people would at least

a) report issues to the bugtracker
discuss issues at the mailinglists

if you want to summarize things at this forum after that, fine, but there are more *developers* following the bugtrackers and mailinglists than this forum.

bug report submitted: http://bugs.openembedded.org/show_bug.cgi?id=2134
a general report sent to the Angstrom-dev mailing list.
Will test the new image soon.

just a quick heads-up for people not on the OE mailing/bug list. Right now, the single one stumbling block of Tosa Angstrom is the broken suspend/resume.

Has anyone tried the latest images for Tosa? My battery should be arriving sometime early next week and I'm interested in flashing.

If not, I'll try and post my general results on the mailing lists, bug tracker, and here.

No, but I'd love to hear how it works. Is Angstrom anywhere near approaching stable?

Nowhere near stable. No major issue (suspend/resume bug, corrupted screen etc) was resolved in the recent months. Tosa also becomes unsupported in Angstrom. I've also heard people in the mailing list complain about unusable altboot and corrupted keymap in the recent images. I don't have any time to test though.

What does this mean? Is it useless to try testing unless one is a dev?

It means nobody is working on fixing tosa bugs - I've switched back to openzaurus. As far as tosa goes, Angstrom is unusable crap and apparently always will be.

BTW- don't get on the angstrom mailing list - the unsubscribe doesn't work and I keep getting spammed with angstrom mail.

Hmm a shame the support for the SL-6000 has dropped.
Well then I have to try OpenZaurus also or pdaXrom...

/me wishes people would actually read the news on http://www.angstrom-distribution.org/ instead of believing the FUD on this ph0rum

It sais:



It will be done but slow. Ok...

I read the news there, which is why I know tosa isn't being worked on. It says "no developer is working on them".

The last image I tried was ridden with show-stopping bugs (can't suspend/resume, for example). going to bugs.openembedded.org and searching for "tosa" shows a screen full of bugs that have been "NEW" for at least a year.

OpenZaurus is history. PdaXrom hasn't updated 6000 images in a long time (beta1, I think) though what is there works.
Honestly I'd think about going with a tetsu kernel on sharprom and running pdaXqt.

We can assign them all to you if you think "NEW" is so offensive.

Is there still any value to your team for folks to test the Tosa images and report the bugs? Or would it be better to wait for a dev to be assigned?

That's what we encourage people to do, provided that 'reporting bugs' means putting them in the bugtracker.

Done.

First bug (reported first at the bugtracker) is the updater.sh.tosa script is not downloadable.

OK...files have changed, thus the instructions have changed. I have updated the tosa install wiki to reflect this.

I installed Angstrom on my tosa and it seemed to work fine. However, none of the ipks I downloaded unstable/armv5te/base/ works for me. I used package manager and it just popped up an error message saying:

I have no clue what went wrong and where to check message log.
In the system info -> log display -> System Log, I got:

Is syslog running? You could try starting it manually and try again.

Not sure if it's the same with Angstrom, but as far back as OZ, the package manager had problems. I'd recommend trying to install via command line using ipkg.

Example:


<location> might be something like sd, cf, flash, whatever. <package> is exactly that...if you've got an ipk downloaded, you can use that name.

You'll get a better idea what's going on if you do installs that way. If the install works via command line, but not via the package installer, then the bug might be with the installer itself. Check to see if there's a bug in the bugtracker.

Installing packages to external media is broken, I've tried.

it's not normally possible, but there's a third party ikpg-link program; however, it's very easy to break your system if used wrongly, and the angstrom rulers had it expunged, but it's out there on a few personal pages.

unplug: the Angstrom feed is under overhaul recently. I'm not following this topic closely either. But as far as I can tell, the unstable is empty/cleaned up now. The ipk built from the stable branch is under 2007, while ipk built from the dev branch is under 2008. (don't mix these two, as tool chain is changed from 2007 to 2008). So s/unstable/2007/g in your pkg conf to point to the right place.

ipkg-link is deprecated and unsupported in Anstrom. I was against this in the beginning but now realizes that it makes sense. The best way to install/use Angstrom on Tosa right now is to install altboot-console-image first, then unpack the rootfs to SD/CF.

I will prepare an instruction soon with the recent opie-images for testing over the weekend.

I have been looking around and thus far have not been able to find the tosa install wiki. Could you please direct me to where that may be? I have checked the wiki off of www.angrstom-distribution.org and haven't found it there unless it is buried under a couple of different levels.

Thanks!

Try here:

http://linuxtogo.org/gowiki/TosaInstall?hi...7C%28install%29

I've moved the latest Angstrom 2007.12-r8 to the unstable/image/tosa folder.