Messages

1

5x00 Hardware / Cf Cards That Will Flash 5500...

« on: April 04, 2006, 04:15:37 pm »

DaneElec 128 is ok, too.

2

OpenZaurus/Opie/Qtopia / Using Gcc Directly On The Z

« on: March 29, 2006, 05:45:36 pm »

I tried again on the new 3.5.4 release. Loads of packages to install, but at least it looks better (*-symlinks.ipk is the way...).

Still, I can't compile the simplest C program on Earth. Well, actually I can't link it. The linker told me that

Code: [Select]

root@collie:~# gcc -o hello hello.c
/usr/lib/gcc/arm-linux/3.4.4/../../../../arm-linux/bin/ld: cannot find /lib/libc.so.6 inside /usr/bin/../../usr
collect2: ld returned 1 exit status
Would anyone have an idea?

3

Angstrom & OpenZaurus / Openzaurus 3.5.4 Released

« on: March 19, 2006, 06:47:30 am »

I flashed my Collie yesterday with the OPIE image. Worked like a charm. I had a brief (and not so good) experience with altboot on the previous RC (when it wasn't integrated), but now it's very easy to use it. The only thing that could be, IMHO, improved is the way previous configuration is remembered : altboot uses the previous choice (Normal, No GUI, SD or CF) by default, but it still asks for the rootfs image to use when several are available on - say - the SD card. Since it's easy to rename the unwanted images, it is not really blocking, though.

The feed is much easier to browse now, and I need no more "-force-depends" to install QT-based packages. I'm also glad to see updated things like mplayer.

Suspending/resuming works much better, now, and the only way I managed to freeze the Z was to keep the On/Off key pressed for more than ten seconds in a row.

Synchronisation between KDE and OPIE works nice, too.

All in one, this is by far the best OZ release, both in features and quality, I ever used. I'm more and more eager to test the SDK and contribute... Thanks for all, OZ devs!

4

5x00 Hardware / Sd Card Fails On Insert

« on: March 19, 2006, 06:35:35 am »

I'm using a Kingston 1GB SD card without any problem on my Collie. I kept the original partition layout (one big VFAT partition).

5

OpenZaurus/Opie/Qtopia / Using Gcc Directly On The Z

« on: March 08, 2006, 03:34:08 pm »

Actually, my /usr/lib/libc.so looks more like this:

Code: [Select]

/* GNU ld script
   Use the shared library, but some functions are only in
   the static library, so try that secondarily.  */
*** BUG in libc/scripts/output-format.sed *** elf32-bigarm,elf32-littlearm
GROUP ( /lib/libc.so.6 /usr/lib/libc_nonshared.a )
I guess the BUG line can explain a lot of things, but I can't see how to work around this.

6

OpenZaurus/Opie/Qtopia / Using Gcc Directly On The Z

« on: March 04, 2006, 06:52:23 am »

I'm trying to compile some world-hailing test program on my zaurus. I installed gcc and, as far as I know, everything needed. But when I'm trying to

Code: [Select]

arm-linux-gcc hello.c  -o hello
I got an ugly

Code: [Select]

/usr/lib/gcc/arm-linux/3.4.3/../../../../arm-linux/bin/ld:/usr/lib/gcc/arm-linux/3.4.3/../../../libc.so: file format not recognized; treating as linker script
/usr/lib/gcc/arm-linux/3.4.3/../../../../arm-linux/bin/ld:/usr/lib/gcc/arm-linux/3.4.3/../../../libc.so:4: syntax error
collect2: ld returned 1 exit status
Would anyone understand this? And, better, explain me why?

Thanks alot.

7

OpenZaurus/Opie/Qtopia / Failing To Set-up A Build Environment...

« on: January 27, 2006, 05:07:56 pm »

Does adding 'INHERIT += patcher' in your local.conf help?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=112672\"][{POST_SNAPBACK}][/a][/div]

I don't think so:

Code: [Select]

ERROR: function do_stage failed
ERROR: log data follows (/goinfre/openembedded-oz3.5.3/tmp/work/patcher-native-20040913-r1/temp/log.do_stage.25375)
| install: cannot stat `patcher.py': No such file or directory
What Bitbake version should I be using, btw? Thanks

8

OpenZaurus/Opie/Qtopia / Failing To Set-up A Build Environment...

« on: January 27, 2006, 08:56:55 am »

I downloaded the OZ SDK from the 3.5.3/sdk directory, and uncompressed it. I followed the OE GettingStarted page. The only thing I'm not so sure about it is the version of Bitbake. I'm using 1.3.2, which may be a little too new for our "old" OE tree. Anyway...

I modified local.conf accordingly, setting my MACHINE as "collie" and my DISTRO as "openzaurus". I also set temp and cache dirs to something that makes sense.

I then export BBPATH to the root of my "sdk", and try to run a simple "bitbake nano". Sadly, I got the following output:

Code: [Select]

NOTE: Using cache in '/goinfre/openembedded-oz3.5.3/cache'
NOTE: Parsing finished. 2216 cached, 0 parsed, 47 skipped, 0 masked.
NOTE: build 200601271454: started

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

NOTE: package quilt-native-0.39: started
NOTE: package quilt-native-0.39-r0: task do_fetch: started
NOTE: package quilt-native-0.39-r0: task do_fetch: completed
NOTE: package quilt-native-0.39-r0: task do_unpack: started
NOTE: Unpacking /goinfre/openembedded-oz3.5.3/sources/quilt_savannah.nongnu.org_VER_0_39_.tar.gz to /goinfre/openembedded-oz3.5.3/tmp/work/quilt-native-0.39-r0/
tar: /goinfre/openembedded-oz3.5.3/sources/quilt_savannah.nongnu.org_VER_0_39_.tar.gz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error exit delayed from previous errors
NOTE: Task failed:
NOTE: package quilt-native-0.39-r0: task do_unpack: failed
ERROR: TaskFailed event exception, aborting
NOTE: package quilt-native-0.39: failed
ERROR: Build of nano failed
If anybody has an idea on what went wrong, or maybe knows which version of Bitbake I should use? Thanks alot.

9

5x00 Hardware / "check Backup Battery" In Dmesg

« on: January 26, 2006, 12:20:16 pm »

I bought a refurbished Collie a couple of months ago, and it mostly works like a charm. But whenever I remove the battery or switch the battery lock, the whole RAM is cleared. I realized it isn't normal when I read a "check backup battery" kernel message in my dmesg.

This is not a big problem since I have my root on an SD card, but I'd like to know if there is a way to change the aforementionned battery, where I can buy a new one, maybe some schematics on how to access the old on on my Zaurus... all this.

If anyone already performed the trick, any advice would be welcomed. Thanks alot.

10

Angstrom & OpenZaurus / Oz 3.5.4 Rc Bug & Work-around List

« on: November 07, 2005, 05:45:56 am »

2. ntpdate... invalid protocol
[div align=\"right\"][a href=\"index.php?act=findpost&pid=102627\"][{POST_SNAPBACK}][/a][/div]

Try to desactivate the ipv6 module (remove the "ipv6" file from /etc/modutils, run update-modules and then reboot, IIRC). It worked for me.

11

Angstrom & OpenZaurus / Oz 3.5.4 Rc Bug & Work-around List

« on: November 06, 2005, 04:26:47 pm »

I just flashed my collie with the opie image, and moved root fs to an SD card. Works nice, so far, especially the suspend-by-cancel thing. I had the need to reset a few times, dunno why, it got stuck. I didn't manage to isolate it yet.

The only thing I saw that is annoying and (probably) easy to fix is with ntpdate: I had to disable the ipv6 kernel module for it to work. It was complaining about an IPV6_V6ONLY (IIRC) error.

Not that I need V6 on my Z, but having a working ntpdate by default would be nice.

12

Angstrom & OpenZaurus / Usb Networking

« on: November 03, 2005, 04:42:53 am »

Since I'm using an internal network for our wirelss network, can I just bridge wlan0 and usb0 together? or will that not work? would the 'route' command on the host machine(not my Z) allow me to do the same thing larrycow was talking about?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=101955\"][{POST_SNAPBACK}][/a][/div]

Bridging wlan0 and usb0 should work, though I'm not used to bridging and I don't know at all whether it's an easy process or not.

Using the 'route' command on your laptop is almost useless, for what I understand: the usb0 interface being bought up, a route to it is automagically definied (you can check that easily, you should have a 192.168.129.0 route to usb0). And the problem is not to route packets from your host to your Z, but to route packets from all other hosts to your Z (through your own host). So you must either, unless I'm wrong: set up a route to your laptop on every single host in the world, or set it on the main router of your network.

If you can't do that (e.g. if you don't have the rights), you will need to use NAT (or bridging, probably). But I found it quite easy: no need to use iptables on your host (in fact, no other "special thing" than ip forwarding), no new interface to manage (like when bridging). Anyway, I'm not even sure my method won't raise new problems later...

13

Angstrom & OpenZaurus / Usb Networking

« on: November 02, 2005, 12:20:28 pm »

No, this is my laptop, which just connects to our wireless router. I don't know anything about NAT, is there an easier way?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=101727\"][{POST_SNAPBACK}][/a][/div]

There is an easy way, at least it worked for me.

Either way, you will need your laptop to do IP forward, in order to transfer packets between your own network (let's call it 192.168.0.0) and your USB network (192.168.129.0). You can do this by the following command (as root, and must be redone each boot, unless you configure your linux to do otherwise):

Code: [Select]

echo 1 > /proc/sys/net/ipv4/ip_forward
Once done, you need another tweak in order to make your two networks connected: you can now send packets from your Z to the outer world, but the outer world can't reply, because it misses a route. The simpler way to do this, if you can, is to set up a new route on your wireless router. This way, any equipment in the 192.168.0.0 network will be able to talk to your Z (through your laptop), and answers to the Z's queries won't be lost anymore.

Depending on your router's model, the process will be different, but the idea is to setup a route on it for the 192.168.129.0/24 network using gateway 192.168.0.X (replace by your laptop's own IP adress).

On mine (Linksys WRT), it's in the "Advanced router" section, IIRC.

14

Angstrom & OpenZaurus / Oz 3.5.4 Release Date?

« on: October 18, 2005, 01:50:34 pm »

The RC build is underway atm. I'll upload images during the next 48 hours. Any preferences of machine/image combination?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=99822\"][{POST_SNAPBACK}][/a][/div]

I'd vote for collie/opie. Thanks anyway

15

Angstrom & OpenZaurus / Syncing - Effort To Create A Definitive Doc

« on: October 09, 2005, 05:47:04 pm »

Handheld:

* Zaurus SL5500
* OZ 3.5.3
* OPIE 1.2
* Standard OPIE PIM (no Kopi/Kapi)
* Connected through USB craddle, IP is 192.168.129.201

Desktop:

* Gentoo Linux
* KDE 3.4
* usb0's IP is 192.168.129.1

Results:

* TCP/IP communication is OK between hosts (ssh to and from the zaurus, ...).

* I can sync with QtopiaDesktop 1.7.0.

* Badly, I can't get to do it with Kontact/KDE. I configure it as stated in another post of this thread, and MultiSynk tells me that it managed to read local data (both addressbook's and calendar's, but that's nothing too impressive), and that it managed to get connected, and then nothing more. Obviously, no data has changed, neither on the Z nor on the PC.

Any idea, someone?

Edit: At last, I managed to synchronize with Kontact. Only that it doesn't want my root password, but some weird synchronization-specific password (Qtopia + random chars). I wasn't aware of this until I monitored qtopiadesktop's traffic with ethereal.