Messages

1

Angstrom & OpenZaurus / Kernel panic after flashing OZ 3.5.1 on C760

« on: November 09, 2004, 03:31:10 pm »

OpenZaurus only works with the default partitioning. If you used Cacko to repartition your flash, OZ won't work.

and what is the default partitioning?

2

Angstrom & OpenZaurus / Kernel panic after flashing OZ 3.5.1 on C760

« on: November 09, 2004, 10:41:42 am »

as you can see in the last line of my original post, I did try zImage.bin as well, with the same result..

I had Cacko ROM 1.21 on it before (and also now, afterwards, as I could not make OpenZaurus work)

3

Angstrom & OpenZaurus / Kernel panic after flashing OZ 3.5.1 on C760

« on: November 09, 2004, 09:58:33 am »

I just tried to flash OpenZaurus 3.5.1 to my SL-C760. I dowloaded the following files:

opie-image.rootfs.img
updater.sh
zImage.bin.forHusky

from http://www.openzaurus.org/official/unstable/3.5.1/c7x0,c8x0/ and also checked for their MD5 sums to be OK. I copied them to my CF card, with renaming them in the following manner:

opie-image.rootfs.img   -> initrd.bin
updater.sh                    -> updater.sh
zImage.bin.forHusky     -> zImage

and then go for the reflash procedure. All seems to go well, and the Zaurus reboots. but, when booting, there are a lot of error messages, like:

Inode #XXX was a directory with children - removing those too..

and

Cannot remove child "pan.png" ino #XXX because it doesn't exist


and after a while, I get the following message:

Kernel panic: No init found. Try passing init= option to kernel

and the whole thing hangs.

now, what am I doing wrong? I tried to use the bootstrap-image.rootfs.img file instead of the opie-image.rootfs.img. Also tried to rename zImage to zImage.bin, but to no avail...

4

Linux Issues / syncing with Evolution, or what else?

« on: May 08, 2004, 06:33:50 am »

OK, now I have a better picture. Say, I\'d use Ko/Pi on the Zaurus, then I\'d need an application on my desktop that is capable of syncing to/from .ics files. What applications are there that support this feature?

KO/Pi itself does the actual syncing with the other ics file.
You need an application, that stores its data in an ics file.

You can compile KO/Pi for your Linux desktop.
It does not need anything from KDE.
It just needs the Qt-lib.
And it has more features, less bugs and better usebility than the KDE Desktop KO.
z.

I tried, but could not compile it. I downloaded korganizerPi.150.source.tar.gz from http://korganizer.kde.org/korganizer/download.html , unpacked it. Unfortunately there is no configure script, nor an INSTALL file in the tarball. I saw a Makefile, which references tmake. So I installed tmake as well, but it just doesn\'t work:

Code: [Select]

$ cd korgenizerPi.150

$ tmake

Usage:

    tmake [options] project-files

Options:

    -e expr    Evaluate expression, ignore template file

    -nodepend  Don\'t generate dependency information

    -o file    Write output to file

    -t file    Specify a template file

    -unix      Create output for Unix (auto detects)

    -v         Verbose/debug mode

    -win32     Create output for Win32 (auto detects)

$ make

for i in libical/src/libical libical/src/libicalss qtcompat microkde libkcal libkdepim korganizer kalarmd; do mkdir -p $i/obj/; done

cd qtcompat; tmake qtcompat.pro -o Makefile

tmake error: Template file tmake.conf not found

make: *** [qtcompat/Makefile] Error 1

I also tried replacing references to tmake in Makefile with make. But that fails as well, as it ties to do a make in libical/src/libical, but there\'s no Makefile in that directory:

Code: [Select]

$ make

for i in libical/src/libical libical/src/libicalss qtcompat microkde libkcal libkdepim korganizer kalarmd; do mkdir -p $i/obj/; done

cd qtcompat; make qtcompat.pro -o Makefile

make[1]: Entering directory `/usr/local/src/zaurus/pim/KoPi/korgenizerPi.150/qtcompat\'

make[1]: Nothing to be done for `qtcompat.pro\'.

make[1]: Leaving directory `/usr/local/src/zaurus/pim/KoPi/korgenizerPi.150/qtcompat\'

cd microkde; make microkdeE.pro -o Makefile

make[1]: Entering directory `/usr/local/src/zaurus/pim/KoPi/korgenizerPi.150/microkde\'

make[1]: Nothing to be done for `microkdeE.pro\'.

make[1]: Leaving directory `/usr/local/src/zaurus/pim/KoPi/korgenizerPi.150/microkde\'

cd libkcal; make libkcalE.pro -o Makefile

make[1]: Entering directory `/usr/local/src/zaurus/pim/KoPi/korgenizerPi.150/libkcal\'

make[1]: Nothing to be done for `libkcalE.pro\'.

make[1]: Leaving directory `/usr/local/src/zaurus/pim/KoPi/korgenizerPi.150/libkcal\'

cd libkdepim; make libkdepimE.pro -o Makefile

make[1]: Entering directory `/usr/local/src/zaurus/pim/KoPi/korgenizerPi.150/libkdepim\'

make[1]: Nothing to be done for `libkdepimE.pro\'.

make[1]: Leaving directory `/usr/local/src/zaurus/pim/KoPi/korgenizerPi.150/libkdepim\'

cd korganizer; make korganizerE.pro -o Makefile

make[1]: Entering directory `/usr/local/src/zaurus/pim/KoPi/korgenizerPi.150/korganizer\'

make[1]: Nothing to be done for `korganizerE.pro\'.

make[1]: Leaving directory `/usr/local/src/zaurus/pim/KoPi/korgenizerPi.150/korganizer\'

cd kalarmd; make kalarmdE.pro -o Makefile

make[1]: Entering directory `/usr/local/src/zaurus/pim/KoPi/korgenizerPi.150/kalarmd\'

make[1]: Nothing to be done for `kalarmdE.pro\'.

make[1]: Leaving directory `/usr/local/src/zaurus/pim/KoPi/korgenizerPi.150/kalarmd\'

cd libical/src/libical; make libicalE.pro -o Makefile

make[1]: Entering directory `/usr/local/src/zaurus/pim/KoPi/korgenizerPi.150/libical/src/libical\'

make[1]: Nothing to be done for `libicalE.pro\'.

make[1]: Leaving directory `/usr/local/src/zaurus/pim/KoPi/korgenizerPi.150/libical/src/libical\'

cd libical/src/libicalss; make libicalssE.pro -o Makefile

make[1]: Entering directory `/usr/local/src/zaurus/pim/KoPi/korgenizerPi.150/libical/src/libicalss\'

make[1]: Nothing to be done for `libicalssE.pro\'.

make[1]: Leaving directory `/usr/local/src/zaurus/pim/KoPi/korgenizerPi.150/libical/src/libicalss\'

for i in libical/src/libical libical/src/libicalss qtcompat microkde libkcal libkdepim korganizer kalarmd; do pushd $i;

          make -f Makefile || exit 1; popd;

          done

/usr/local/src/zaurus/pim/KoPi/korgenizerPi.150/libical/src/libical /usr/local/src/zaurus/pim/KoPi/korgenizerPi.150

make[1]: Entering directory `/usr/local/src/zaurus/pim/KoPi/korgenizerPi.150/libical/src/libical\'

make[1]: Makefile: No such file or directory

make[1]: *** No rule to make target `Makefile\'.  Stop.

make[1]: Leaving directory `/usr/local/src/zaurus/pim/KoPi/korgenizerPi.150/libical/src/libical\'

make: *** [all] Error 1

what am I doing wrong?

5

Linux Issues / syncing with Evolution, or what else?

« on: April 28, 2004, 02:50:09 am »

The Opie-PIMs have to be installed from the sharp-feed of Opie, they will be linked to the original sharp-PIM-icons. 

and where would I find this feed? I didn\'t find it on the Opie site

6

Linux Issues / syncing with Evolution, or what else?

« on: April 27, 2004, 05:46:00 am »

OK, now I have a better picture. Say, I\'d use Ko/Pi on the Zaurus, then I\'d need an application on my desktop that is capable of syncing to/from .ics files. What applications are there that support this feature?

From what I see, Ximian Evoltion doesn\'t do this. It can only import .ics files.

There\'s a project called MultiSync, but that only supports the old Sharp PIM formats and the Opie PIM, but not Ko/Pi, see here

What other such applications are there? Is the only viable solution KOrganizer as a sync partner to Ko/Pi?

7

Linux Issues / syncing with Evolution, or what else?

« on: April 27, 2004, 04:42:27 am »

does this mean that I have to replace the original PIM applications, and use Ko/Pi? that\'s the only way forward?

8

Linux Issues / syncing with Evolution, or what else?

« on: April 25, 2004, 04:42:26 pm »

I read in the FAQ that it\'s not possible to sync the Zaurus apps with Ximian Evoltion. There\'s a link there about some preliminary support though, but it\'s dead.

What do people use as PIM applications to sync the Zaurus with, on Linux?

9

Security and Networking / 1024 bit WEP WiFi does not work with Buffalo WiFi card, C760

« on: April 06, 2004, 12:39:13 pm »

thanks, changit it to open made it work!

10

Security and Networking / 1024 bit WEP WiFi does not work with Buffalo WiFi card, C760

« on: April 06, 2004, 11:06:27 am »

yes, 128bit encryption...

11

Security and Networking / 1024 bit WEP WiFi does not work with Buffalo WiFi card, C760

« on: April 06, 2004, 08:53:56 am »

I\'m trying to access a closed WiFi sport with my C760 via a Buffalo WLI2-CF-S11. I\'m using the Cacko QT ROM. The WiFi spot uses 1024bit encryption using Key2 for the encryption key.

I set up all in the network dialogs, but the WiFi card can\'t connect (it tries but it fails)

The same C760 with the same WiFi card works for public WiFi networks.

The same Buffalo WiFi card works fine for accessing the same closed WiFi sport from an other PDA (some PalmOS based device).

What could be wrong here?

12

Sharp ROMs / japanese input method with Cacko ROM on SL-C760?

« on: March 22, 2004, 06:58:24 am »

thanks, this was a very good link

but what I have problems with are the central european fonts. even though I installed the micro-unicodefonts-*.ipk packages, only ASCII characters appear in terms of latin characters.

13

Sharp ROMs / japanese input method with Cacko ROM on SL-C760?

« on: March 22, 2004, 04:39:11 am »

How could I get the japanese input method supplied with the C760 to work with the Cacko ROM? I just flashed it, but it only offers english input. The japanese input method (inlcuding the written interface) was very nice on the stock C760...

14

Angstrom & OpenZaurus / can\'t network, can\'t mount CF card with OZ 3.3.5 and 3.3.6

« on: March 21, 2004, 11:17:04 am »

more information: it seems that there is some problem with the modules supplied with this kernel:

Code: [Select]

# depmod -a

dempod: *** Unresolved symbols in /lib/modules/2.4.28-rmk7-pxa3-embedix/kernel/drivers/usb/storage/usb-storage.o

dempod: *** Unresolved symbols in /lib/modules/2.4.28-rmk7-pxa3-embedix/net/hostap.o

dempod: *** Unresolved symbols in /lib/modules/2.4.28-rmk7-pxa3-embedix/pcmcia/hostap_cs.o

15

Angstrom & OpenZaurus / can\'t network, can\'t mount CF card with OZ 3.3.5 and 3.3.6

« on: March 20, 2004, 02:13:05 pm »

I just flashed my CL-C760 with the OZ 3.3.6-pre1 images (husky). It reboots fine, but than I can\'t mount my CF card nor can I do networking.

For networking, I plug in the USB card, and the usbd0 net interface comes up. I can only ping the zaurus (192.168.129.201), but when trying to ping 192.168.129.1, the Zaurus simply freezes. The only way to get out of the situation is to remove power and the pattery, than restart.

As for the CF card, it desn\'t mount automatically. When trying manually with either

mount /mnt/cf
mount /dev/hda1 /mnt/cf

it simply says:

Code: [Select]

mount: /dev/hda1 is nat a valid block device

I tried to remedy the situation with trying:

cardctl eject; cardctl insert
/etc/init.d/pcmcia restart
/etc/init.d/mountall.sh

but to no avail. looking at scripts in /dev/init.d, I found a script called /dev/init.d/devices, in which the following line does not execute:

Code: [Select]

# mount -t ramfs ramfs /dev

mount: fs type ramfs not supported by kernel