Messages

16

Angstrom & OpenZaurus / Selecting A Zimage File

« on: July 23, 2005, 12:46:28 am »

Slightly OT, but it seemed like a good place to ask this:

What is your experience using 64-0?  I do remove my SD card from time to time. . . will this lock up the Z every time I do so?  At the moment, it seems like it makes a habit of locking up every time its expecting a card and doesn't have one; it also has a habit of not ejecting the card when I ask it to.

On the other hand, I'm getting ready to install pocketworkstation, and could probably use the extra RAM.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=89133\"][{POST_SNAPBACK}][/a][/div]

If you aren't running apps off your SD you should be able to unmount and remove it - no problems...  I've done this lots.

RAM disk is only helpful as long as the Z doesn't crash or lockup.  As soon as you have to reset / reboot it anything on the RAM disk is toast  (it is not non-volitile or NVRAM storage you see on some PDAs) ...  this really limits the usefulness of it in my opinion.  So I run 64-0.

17

Angstrom & OpenZaurus / Sdio - Only Waiting To Be Ported?

« on: July 03, 2005, 02:00:20 am »

Acordding to this a SDIO stack is allready available for linux.

I'm sure if it were that simple people would have ported it to the collies/poodles...
But AFAIK they run undocumented SD chips, which are only able to work with Sharp's SD/MMC driver which is largely why collies/poodles are stuck at the 2.4.18 kernel.

It's a shame, but Sharp will not or cannot release the necessary specs or source code.

18

Angstrom & OpenZaurus / Why The Hell Did I Try To Upgrade Ipkg?

« on: June 25, 2005, 01:40:46 am »

the prgram closed unexpectly, and I had to reset via the rear button.
now I can run the program manager

em......             HELP!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=85734\"][{POST_SNAPBACK}][/a][/div]

Reflashing is the easiest way to recover from disaster...

19

5x00 Hardware / Cradle -> Serial Cable Conversion

« on: June 25, 2005, 01:31:32 am »

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...

 [ Invalid Attachment ]

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...

Code: [Select]

    (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

Cheers,

-G

20

Angstrom & OpenZaurus / Just Got My Zaurus Faq

« on: June 23, 2005, 12:27:35 am »

The main thing that ext2 gives you over FAT is the ability to use "protection" on the files by assigning read write execute (rwx) priviledges to user, group or world.  (Yes I know it gives other benefits, but that's the jist of it).  [div align=\"right\"][a href=\"index.php?act=findpost&pid=85416\"][{POST_SNAPBACK}][/a][/div]

The other most important benefit ext2 provides is the ability to create symbolic links, which is essential if you want to install packages onto it...

21

Angstrom & OpenZaurus / Oz3.5.3 (collie) On/off Button Problem

« on: June 21, 2005, 10:38:08 pm »

I'm sorry, but I don't think that will change anything. At the moment, we don't have any developers left to look into the suspend/resume issues. I'm afraid that someone outside the core team will have to look into this bug.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=85138\"][{POST_SNAPBACK}][/a][/div]

What is surprising is why this bug should creep in to OZ in the first place.
....
 
Its unlikely that this could be a kernel bug, as i am assuming that no one has done any changes to the ancient kernel 2.4.18-rmk etc which is in use on collie for a long time. So if we use the same kernel that is used for a previous OZ release (3.5.2) we should be able to see if the bug occurs in it too. [div align=\"right\"][a href=\"index.php?act=findpost&pid=85169\"][{POST_SNAPBACK}][/a][/div]

@Mickeyl: what's cookin' (3xxx series?, nokia 770?)?  Know anyone in Toronto with a Z serial cable I could borrow?  

@weasel123:
While I shared your surprise about it creeping in, I don't agree that it's probably not the kernel...   I think there's quite a bit of patching that goes on to the baseline kernel to get support into it for everything required to run an 5xxx series Z...

It also probably wouldn't do you any good to flash an older kernel against OZ3.5.3 unless your are able to repack the FS with the kernel modules that go with it, you're best bet would be to see if you can dig up OZ 3.5.2 somewhere and just continue to run off that (or try the Qtopia 2.1 series ROMs)...

As far as solving it goes, it will probably be a bitch to trace what is happening on the Z without a serial cable to watch the kernel messages as it suspends.   (Any record of what happen disappears with a hard reset.)

22

Angstrom & OpenZaurus / Oz3.5.3 (collie) On/off Button Problem

« on: June 19, 2005, 06:08:51 pm »

My poodle has yet to fail to come back after suspending from the menu, whereas opie itself seems to lock up quite often when it suspends by itself (apm?).

Hmm...  I wonder what the difference in how suspend begins is... maybe we can use the menu's suspend method on an idle timer instead of apm...

23

Angstrom & OpenZaurus / Qemu Bitbake Image - Jun 17, 2005

« on: June 19, 2005, 03:57:44 am »

To speed things up folks probably want to install hdparm:

sudo apt-get install hdparm; sudo hdparm -d1 -c3 -u1 /dev/hda; sudo hdparm -d1 -c3 -u1 /dev/hdb

24

Angstrom & OpenZaurus / Oz3.5.3 (collie) On/off Button Problem

« on: June 17, 2005, 11:20:03 pm »

As an additional note, if the Collie is suspended with the suspend menu things appear to work.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=84748\"][{POST_SNAPBACK}][/a][/div]

Sounds anecdotal to me... how many times have you done it successfully in a row?

25

Angstrom & OpenZaurus / Qemu Bitbake Image - Jun 17, 2005

« on: June 17, 2005, 05:45:47 pm »

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

Thanks to offroadgeek for hosting:
https://www.oesf.org/howto/downloads/OE-Bit...MU-20050617.zip

Requirements:
- 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.

Cheers,

-Ironstorm

PS: thanks to those in IRC who help with answers to my silly questions and especially to offroadgeek for hosting.

26

OpenZaurus/Opie/Qtopia / Sd Card Mount Problem + Workaround

« on: June 16, 2005, 08:12:46 am »

Do you know that posting bugfixes to forum does not gwarant that it will be in next OZ releases? We have bugtracker for distro bugs.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=84479\"][{POST_SNAPBACK}][/a][/div]

Yes, however this bugfix should not be in the next OZ release...  It's not the right level to be addressing the problem as there are other areas of the distro that may depend on the kernel's behaviour being non-buggy.

27

OpenZaurus/Opie/Qtopia / Sd Card Mount Problem + Workaround

« on: June 16, 2005, 01:52:48 am »

I just did a build of OZ the other night:
Linux collie 2.4.18-rmk7-pxa3-embedix #1 Tue, 14 Jun 2005 03:05:30 +0000 armv4l unknown

And when I do a cat /proc/partitions I get:

major minor  #blocks  name

  60     0     999424 mmcda
  60     1     999392 mmcda1
  60     0     999424 mmcda
  60     1     999392 mmcda1
  60     0     999424 mmcda
.....

Into infinity...  this is a kernel bug...  

I'm not a kernel developer so I hacked a fix into the /etc/sdcontrol script instead....

At line 104 of /etc/sdcontrol edit as follows:

Code: [Select]

       # Read available partitions from /proc/partitions.
        PROC_PARTITIONS=`cat /proc/partitions | head -$(expr $(cat /proc/partitions | head -10 | grep -n " 0 " | head -2 | tail -1 |  cut -d: -f1) - 1)`
        # OK_PARTS="`cat /proc/partitions |awk '{print $4}'| grep mmcd`"
        OK_PARTS="`echo $PROC_PARTITIONS |awk '{print $4}'| grep mmcd`"

        echo $PROC_PARTITIONS |awk '{print $4}'| grep mmcd > "$LOGFILE-part"
Cheers,

-G

28

Angstrom & OpenZaurus / Oz3.5.3 (collie) On/off Button Problem

« on: June 15, 2005, 01:30:24 am »

Is this a related problem?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=84271\"][{POST_SNAPBACK}][/a][/div]

Yes, the suspend/resume issues are all releated to broken APM/Kernel interactions and there is no reliable fix for the issue(s) other then to use something other then OZ3.5.3.

Edit: I should say this only effects collies (5000d/5500) AFAIK.

29

OpenZaurus/Opie/Qtopia / Kernel Compile Can't Find Arm-linux-gcc-2.95

« on: June 03, 2005, 05:42:43 pm »

Not sure why the kernel compile can't find arm-linux-gcc-2.95... it's there...
Have I misconfigured my local.conf?
Could it be that the build directory is too large a pathname or something?

Help

-Ironstorm

Code: [Select]

bitbake@debian-bitbake:~/bb/build$ bitbake openzaurus-sa
NOTE: Using cache in '/home/bitbake/bb/build/tmp/cache'
NOTE: Parsing finished. 2338 cached, 0 parsed, 48 skipped, 0 masked.
NOTE: build 200506030547: started

OE Build Configuration:
TARGET_ARCH   = "arm"
TARGET_OS     = "linux"
MACHINE       = "collie"
DISTRO        = "openzaurus"
TARGET_FPU    = "soft"

NOTE: package openzaurus-sa-2.4.18-rmk7-pxa3-embedix: started
NOTE: package openzaurus-sa-2.4.18-rmk7-pxa3-embedix-r19: task do_fetch: started
NOTE: package openzaurus-sa-2.4.18-rmk7-pxa3-embedix-r19: task do_fetch: completed
NOTE: package openzaurus-sa-2.4.18-rmk7-pxa3-embedix-r19: task do_compile: started
ERROR: function do_compile failed
ERROR: log data follows (/home/bitbake/bb/build/tmp/work/openzaurus-sa-2.4.18-rmk7-pxa3-embedix-r19/temp/log.do_compile.4348)
| NOTE: make EMBEDIXRELEASE=- include/linux/version.h CC=ccache arm-linux-gcc-2.95 LD=arm-linux-ld-2.11.2
| make: `include/linux/version.h' is up to date.
| NOTE: make EMBEDIXRELEASE=- dep CC=ccache arm-linux-gcc-2.95 LD=arm-linux-ld-2.11.2
| rm -f include/asm-arm/arch include/asm-arm/proc
| (cd include/asm-arm; ln -sf arch-sa1100 arch; ln -sf proc-armv proc)
| make[1]: Entering directory `/home/bitbake/bb/build/tmp/work/openzaurus-sa-2.4.18-rmk7-pxa3-embedix-r19/linux/arch/arm/tools'
| /home/bitbake/bb/build/tmp/work/openzaurus-sa-2.4.18-rmk7-pxa3-embedix-r19/linux/scripts/mkdep -D__KERNEL__ -I/home/bitbake/bb/build/tmp/work/openzaurus-sa-2.4.18-rmk7-pxa3-embedix-r19/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -Os -mapcs -fno-strict-aliasing -fno-common -fno-common -pipe -mapcs-32 -march=armv4 -mtune=strongarm1100 -mshort-load-bytes -msoft-float  -- getconstants.c |\
|  sed s,getconstants.o,constants.h, > .depend
| make all
| make[2]: Entering directory `/home/bitbake/bb/build/tmp/work/openzaurus-sa-2.4.18-rmk7-pxa3-embedix-r19/linux/arch/arm/tools'
| ccache arm-linux-gcc-2.95 -D__KERNEL__ -I/home/bitbake/bb/build/tmp/work/openzaurus-sa-2.4.18-rmk7-pxa3-embedix-r19/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -Os -mapcs -fno-strict-aliasing -fno-common -fno-common -pipe -mapcs-32 -march=armv4 -mtune=strongarm1100 -mshort-load-bytes -msoft-float -S -o constants.h.tmp.1 getconstants.c
| arm-linux-gcc-2.95: No such file or directory
| make[2]: *** [constants.h] Error 1
| make[2]: Leaving directory `/home/bitbake/bb/build/tmp/work/openzaurus-sa-2.4.18-rmk7-pxa3-embedix-r19/linux/arch/arm/tools'
| make[1]: *** [dep] Error 2
| make[1]: Leaving directory `/home/bitbake/bb/build/tmp/work/openzaurus-sa-2.4.18-rmk7-pxa3-embedix-r19/linux/arch/arm/tools'
| make: *** [archdep] Error 2
| FATAL: oe_runmake failed
NOTE: Task failed:
NOTE: package openzaurus-sa-2.4.18-rmk7-pxa3-embedix-r19: task do_compile: failed
ERROR: TaskFailed event exception, aborting
NOTE: package openzaurus-sa-2.4.18-rmk7-pxa3-embedix: failed
ERROR: Build of openzaurus-sa failed

Code: [Select]

bitbake@debian-bitbake:~/bb/build$ which arm-linux-gcc-2.95
/usr/local/arm/2.95.3/bin/arm-linux-gcc-2.95
bitbake@debian-bitbake:~/bb/build$ export
declare -x BBPATH="/home/bitbake/bb/build:/home/bitbake/bb/openembedded:/usr/local/arm/2.95.3/bin"
declare -x HOME="/home/bitbake"
declare -x LANG="en_CA"
declare -x LANGUAGE="en_CA:en_US:en_GB:en"
declare -x LOGNAME="bitbake"
declare -x LS_COLORS="no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.avi=01;35:*.fli=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.ogg=01;35:*.mp3=01;35:*.wav=01;35:"
declare -x MAIL="/var/mail/bitbake"
declare -x OLDPWD="/home/bitbake/bb"
declare -x PATH="/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:~/bk_client-1.1:/usr/local/arm/2.95.3/bin"
declare -x PWD="/home/bitbake/bb/build"
declare -x SHELL="/bin/bash"
declare -x SHLVL="1"
declare -x SSH_CLIENT="192.168.0.101 1038 22"
declare -x SSH_CONNECTION="192.168.0.101 1038 10.0.2.15 22"
declare -x SSH_TTY="/dev/pts/0"
declare -x TERM="xterm"
declare -x USER="bitbake"
bitbake@debian-bitbake:~/bb/build$

30

Angstrom & OpenZaurus / Bitbake Scripts...

« on: June 03, 2005, 02:25:30 pm »

There is a problem with the compiler path I can't resolve (says it can't find arm-linux-gcc-2.95, but it is in the path)...

Are you sure that you remembered to rename the arm-linux-gcc file to arm-linux-gcc-2.95 ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=82641\"][{POST_SNAPBACK}][/a][/div]

Yes, it's gets mv'd in the bitbake_install.txt commands...  And /usr/local/arm/2.95.3/bin
is exported both BBPATH and PATH...

At first I had it symlinked but then I realized that might not work from ZaurusKernels where Mickeyl said that ln might leave it still in the path (it could conflict w/ 3.3 or 3.4 or whatever is used to compile the non-kernel packages, I guess)...

I'm wondering if maybe the directory path is too long or something (the kernel compile like 6 directories below /home/bitbake/bb/build vs. /stuff/build which is used in the OE docs)...

It also seems to work executing the "ccache arm-linux-gcc-2.95 ..." command from the command line in the directory it supposedly died in...

-Ironstorm