Opened 7 years ago

Last modified 3 years ago

#1306 open enhancement

Need armv7 wrapper

Reported by: h4x Owned by:
Priority: minor Milestone: 0.9.33
Component: wrapper Version: 0.9.13
Keywords: debian arm Cc:
Parent Tickets: Sensitive: no


Problem: I got an error message on startup of i2p using the command "./i2prouter start".
Error: Failed to load the wrapper
Logs: no logs/events generated
Solution: Using the debian version from the i2p-repository (i2p-router 0.9.13-1~deb7u+1) the router starts.

Hardware: Cubietruck (ARM A20)
OS: Debian Wheezy (Linux debian 3.4.79-r0-s20-rm2+ #54 SMP)
Arch: armv7l
Java: Java™ SE Runtime Environment (build 1.8.0-b132)
i2p-Version: i2pinstall_0.9.13.jar (from i2p website)


Attachments (1)

error.txt (405 bytes) - added by h4x 7 years ago.

Download all attachments as: .zip

Change History (8)

Changed 7 years ago by h4x

Attachment: error.txt added

comment:2 Changed 7 years ago by zzz

Owner: set to killyourtv
Status: newassigned

Perhaps our compiled and distributed wrapper doesn't work on a Cubietruck, which I've never heard of.

We ship two ARM wrappers, v5 and v6. The v6 is hardfloat for Raspberry Pi. Our script installs the v5 wrapper on v7 systems.

http://i2p-projekt.i2p/en/misc/manual-wrapper has info on building your own wrapper.

Will have to research the cubietruck.

Assigning to kytv but I'll work on it too.

comment:3 Changed 6 years ago by str4d

Keywords: debian arm added
Milestone: 0.9.15

comment:4 Changed 5 years ago by zzz

Summary: **Failed to load the wrapper**Need armv7 wrapper
Type: defectenhancement

comment:5 Changed 5 years ago by zzz

Milestone: eventually
Owner: killyourtv deleted
Status: assignedopen

We need hardware for this.
I still don't know why the v5 wrapper doesn't load for the OP. We've updated the wrapper several times since the OP. Would be nice to hear from a tester.

comment:6 Changed 3 years ago by zzz

Milestone: eventually0.9.33

At line 41, we use the v5 wrapper for v7, with the note that the v6 wrapper didn't work on my Trimslice. That's only one data point, and the Trimslice was a strange platform.

From reading armhf should work for all modern 32-bit ARM. But we don't take the binary from tanuki, we build our own for RPi.

Still confused on why my old RPi is different from modern v7, or is it?

Seems like we should try our v6 wrapper on v7, not the v5 one.

Need somebody with a modern ARMv7 (not my ancient RPi) to help.

comment:7 Changed 3 years ago by zzz

Maybe we just take the armhf binary from the delta pack and use it for v7? Need to retest it on my v6 RPi also.

Note: See TracTickets for help on using tickets.