OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio


Welcome Guest ( Log In | Register )

Personal Photo
Personal Statement
Varti doesn't have a personal statement currently.
Personal Info
Age Unknown
Gender Not Set
Trieste/Trst, Italy
Birthday Unknown
No Information
Joined: 30-April 08
Profile Views: 5,356*
Last Seen: Today, 07:45 AM
Local Time: Jan 18 2017, 07:01 AM
119 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
11 Jan 2017
It's a 7 inch laptop, using an Intel Atom x7-Z8700 Cherry Trail processor, with support for Windows 10 or Ubuntu 16.04 Linux. Unlike the GPD Win, Linux support might be then officially supported for this device.


"The system is said to be slightly larger than the GPD Win, and it has an aluminum chassis. (..) According to ton-chi-ki, GPD plans to launch an Indiegogo crowdfunding campaign for the GPD Pocket in February."

11 Jan 2017
Lineo Solutions, Inc. has joined the Yocto Project, an open source collaboration project for embedded Linux development.


"(...) it is a pleasant reencounter with the 'OpenZaurus' in the history of the Yocto Project, as we were involved in the development of Linux Zaurus in the past." said Akira Kobayashi, Representative Director of Lineo. Lineo was engaged in Linux development for Sharp Zaurus from its first model to the last model, and Akira Kobayashi led the development team.

25 Dec 2016
Hi everyone,

I think it is time to update all of you on what's happening behind the scenes, regarding this forum's administration. I have some good news for you to share: Speculatrix and me have finally gained access to the OESF's shell account on ibiblio. This means that we can now remove all the malware that has gathering here during the last years. I have done a preliminary search and cleanup, unfortunately there are still files though which can be only removed by the host's admins, I'll get in touch with them once I'll complete the list of all the malicious files. We have now a complete backup of both the forum's files and the database, I'm doing manual backups for now but I'll see if I can set an automatic rsync setup. Also, Speculatrix and me have been thinking of upgrading the Invision Power Board software to the latest version (we are using the 2.3.1 version, which was in September 2007; the current version is, in order to make it more secure to all the latest malware floating around, more about this later.

We can now put back online the Wiki, too; there's already a great replacement Wiki that has been recently setup by koan (thanks!), we can decide to keep it there or move it on this server. For now, in place of the old Wiki pages I have put a redirection link to the forum itself, so that it can be accessed by just typing oesf.org.
Regarding elsix, all the files are unfortunately stored on a different account on ibiblio, and for now we still don't have access to it. I'll keep hunting for the account details, also there are a couple of ex-maintainers which we can get in touch with.

That's it for now. What I'd really like for this forum is to continue to be a reference for both all the information regarding the Zaurus (and I believe it's the only remaining English forum devoted to it), and any other present and future device which shares the same philosophy as the Z.

Warm greetings and best wishes for Christmas and the New Year!

16 Dec 2016

I have opened this thread to document my attempts to run Alarmz on my Akita (SL-C1000). As you probably already know, Alarmz is currently declared as not tested on that Zaurus. Yesterday night I have finally found some free time to test it, and I'd like to write down everything I'm trying to do so that I won't forget anything in case I'll have to postpone any further testing due to lack of time, and in case these info could be useful for other C1000 users here. Please feel free to comment and/or point to any error in my post.

The first blocking step is alarmz's own kexecboot, which doesn't run on the Akita since it lacks specific code for that model. Luckily the official kexecboot does support the Akita, there's a specific build for it. I have tried two versions of it: the old one based on the 2.6.2x kernel, and the latest one (released last May) based on 4.4.8. Both can be found here:


The 2.6 kexec works as expected, though it doesn't support ext4 partitions, which the 4.4.8 one does. Alarmz on an ext4 partition should run faster than on an ext3 one, but if at the end I'll not manage to boot the latest kexec, I'll try the 2.6/ext3 setup.

I have not been able to run the 4.4.8 kexec so far. At first I thought that the problem might be the modified partition table on my NAND: I had previously resized the root partition from 58 MB to 32, in order to install Cacko on NAND. I had a conversation on IRC with Ant (Kexecboot's Zaurus maintainer), he has told me that the latest kexec supports only root partitions with a default size of 58 MB, unlike older kexec versions. I have therefore done a NAND restore using Trisoft's backup, but I still had the same problems, as I will explain below.

At the first boot, a screen with the Open Embedded logo is displayed. The boot seem to remain stuck to that image, I have waited for a couple of minutes but nothing happened. After a switch off/on cycle, the screen went black, then the kexec menu was briefly shown for a fraction of second, then the screen turned black again. After unplugging the charger and the battery, waiting for 5 seconds then plugging them back, nothing is displayed anymore. The charger LED is turned off for a second, turned on and turned back off again after a second. I have tried to reflash kexec to no avail, the Open Embedded screen still isn't shown anymore, so I'll have to do the NAND restore again in order to go back one step and try to do something else when the OE logo is shown. This is what I'll try next:

- do the NAND restore again; when the OE logo is shown, leave the Zaurus untouched for a longer time and see if it makes any difference
- (thanks Ant for the hint!) the original Sharp's ROM has the rootfs and second rootfs formatted as JFFSv1 which seems that cannot be mounted by newer kexecboot with kernel >= 2.6. Try to flash again kexec with updater.sh, but this time flash the rootfs and 2nd rootfs too with an JFFSv2 image, i.e.:
1) zImage for kernel
2) initrd.bin for rootfs in mtd2
3) home.bin for second rootfs in mtd3 (optional)
as described here: http://cgit.openembedded.org/meta-handheld...n/README.zaurus . Use two copies of the following file, named as initrd.bin and home.bin:
- have an ext4 SD with Alarmz on it inserted. If the menu can be seen again, see if it's possible to navigate in the menu and select the Alarmz partition before the screen turns black again
- report the issues on #kexecboot. In case a dmesg log is generated and stored anywhere in the NAND, consider doing a NAND dump via the maintenance menu and see if the dmesg log can be extracted from there.
- try the kexec 2.6/ext3 partition solution

15 Dec 2016
This is unfair, I don't understand how a PDA on a plane could be dangerous biggrin.gif

P.s.: no, that's not me in the photo, this is a random photo I found while browsing.

Attached File(s)
Attached File  73961753.jpg ( 136.06K ) Number of downloads: 17
Last Visitors

2 Dec 2016 - 6:02

21 Nov 2016 - 0:21

10 Nov 2016 - 16:38

29 Oct 2016 - 6:40

1 Oct 2016 - 7:56

Other users have left no comments for Varti.

There are no friends to display.
RSS Lo-Fi Version Time is now: 17th January 2017 - 10:01 PM