OESF Portal | OESF Forum | OESF Wiki | LinuxPDA | #planetgemini chat on matrix.org | #gemini-pda chat on Freenode | #zaurus and #alarmz chat on Freenode | ELSI (coming soon) | Ibiblio


Welcome Guest ( Log In | Register )

Personal Photo
Personal Statement
ironstorm doesn't have a personal statement currently.
Personal Info
Age Unknown
Gender Not Set
Location Unknown
Birthday Unknown
No Information
Joined: 10-August 03
Profile Views: 647*
Last Seen: 29th July 2006 - 12:35 PM
Local Time: Jun 24 2018, 10:58 AM
86 posts (0 per day)
Contact Information
AIM No Information
Yahoo No Information
ICQ No Information
MSN No Information
Contact Private
* Profile views updated each hour



My Content
5 Dec 2005
OE Builder VMware image is a Ubuntu VMware disk image preconfigured to build OE distributions. It is intended to drastically simplify the compiling of OE distros to running 2 shell scripts and waiting for the build to complete.

Start the VM, login as oe/oe, run ~/oe-configure.sh and then ~/start-opie-image-build.sh to build an opie-image.

This release is designed to run on the free [beer] VMware Player (http://www.vmware.com/products/player/), requires 256MB dedicated to the VM, and about 10GB of disk space to complete a build of opie-image. Building is time consuming (8+hrs on a fast PC) and should be checked on from time to time...

The set-up assumes it will be running on a Windows host, however with QEMU installed (for QEMU-img tool used to create vmdk) it should be easy enough to get it started under a Linux host.

Image Logon/Password is oe/oe

http://ewi546.ewi.utwente.nl/OE/vmware-image/ See the release fixes section!


Attached Image
Attached Image

Release Fixes:
* Unzip the file Attached File  oebuilder_scripts_20051209.tar.gz ( 8.53K ) Number of downloads: 100
in your oe home directory, this will update the scripts to fix the partition detection problem and also the problem with stale OE.db data (bug #498)

* Some packages didn't get installed, this fixes that problem when oe-configure runs... you need to give the bold answers
Checking for required Debian Packages ...
Password: oe
Reading package lists... Done


Score is 47

Accept this solution? [Y/n/q/?] n


Score is -1089

Accept this solution? [Y/n/q/?] y


Need to get 20.3MB of archives. After unpacking 54.0MB will be used.
Do you want to continue? [Y/n/?] y
30 Nov 2005
In June, I put out a QEMU image for building OE ( https://www.oesf.org/forums/index.php?showtopic=13311 ).

The idea being that one could unzip the image, install the emulator, fire it up and start a build of OE/OZ by invoking 3 or so quick shell scripts.

The June image has been obsolete since July or so when the devs finally switched over to monotone.

Recently, I picked up on this again and started updating it... got things going with monotone and ported the set-up to run under VMware Player to try to boost speed.

Last night I managed to complete a build for Collie on this set-up, it still needs some polish.

I'm wondering if there is general interest in this type of roll-your-own set-up... If so I'll put the effort into cleaning it up for consumption.


19 Nov 2005
I'm running OZ 3.5.4RC...

I've been trying to employ my Z5500 as a shoutcast reciever to pump sound into my stereo.

Unfortunately, the state of shoutcast in OZ is somewhat weak... That is to say neither XMMS (doesn't recognize streams at all) nor Opie-Player2 (crashes right away) can handle shoutcast streams.

This has forced me to fall back to the console, making use of mpg321... And while mpg321 recognizes streams and plays them back, it also skips during playback... I suspect either the Z is too slow or it suffers from the bug described here -> http://angerman.net/articles/jukebox/#mpg321 ...

Are there any other alternatives known to support shoutcast streams?

While we are at it is there any way to script volume changes?

I used to use aumix in the old days, however trying it now just gives an error (SOUND_MIXER_READ_RECSRC) ... I thought about trying to script the volume applet, but there is no documentation anywhere for it's support or lack of support for QCOP calls.


24 Jun 2005
I took apart (rather roughly) my cradle to extract the sharp I/O connector for the Z...

I'm now at a loss as to what my next steps are in terms of disassemble...

Attached Image

Above is what the back side (opposite side of the sync button) looks like, below are the labels and some of my guesses about what is going on...

    (6543210987654321)?      Back Shot
_____||||||||||||||||____   (Sync Button is on the other side)
/ CH1 /(-?)       (+?)\ 1  \
|  16 ||||||||||||||||     |  () indicate are guesses
|R                         |
|L                         |
|/\  [||||||||||||||||||]  |
|Y                         |
|M   CH5                   |
|X                         |
||                         |
|C                         |
|3                         |

The pin out from the board into the plug at the top has 16 pins...
The pin out to the middle socket appears to have 18 lines...
I'm guessing that it is the 16 pins for the Z +2 for power?

Does anyone know for sure?
Should I be creating a new ribbon to run to the middle socket?
Should I take the top plug off and wire what directly to my serial port plug?

I'm trying to working off this: https://www.oesf.org/index.php?title=Serial...-to-Sharp_cable


17 Jun 2005
This image is a working OE build environment inside a QEMU disk image.

Thanks to offroadgeek for hosting:

- QEMU pc emulator For Windows For Linux
- A PC that can spare 256MB RAM to run the guest image
- A Disk that can spare 6GB+ space
- A day or so to build a Zaurus opie-image
- An SSH client is highly recommended (i.e. PuTTY)

To set-up:
On windows:
- Unzip into the QEMU directory (i.e. C:\Program Files\QEMU)
- start-oe-bitbake-QEMU.bat
- once "login: " appears you can SSH as user/pass: oe/oe
- read the login message / readme file (same file)

Other notes:
I recommend you replace the oe-configure.sh script with the one attached to this posting (i.e. use FileZilla to SFTP it to localhost), but it is not essential if you don't mind setting up the compile output partition yourself.

Compiled Z image output ends up in a deploy subdirectory of oe-build/build... (do a find ~/oe-build | grep deploy for exact path)

It's slow the first time through (i.e. ~18-24hrs to build everything for opie-image) but at least you can watch it doing it's thing and once built only new/unbuilt packages need to be rebuilt the next run. I'd be curious to know how fast someone can bitbake opie-image on a Linux host with KQEMU accelerator installed.



PS: thanks to those in IRC who help with answers to my silly questions and especially to offroadgeek for hosting. smile.gif
Attached File(s)
Attached File  oe_configure.sh.txt ( 3.43K ) Number of downloads: 56
Last Visitors
ironstorm has no visitors to display.

Other users have left no comments for ironstorm.

There are no friends to display.
RSS Lo-Fi Version Time is now: 24th June 2018 - 10:58 AM