Messages

31

Sharp PC-Z1 NetWalker / Iqnotes

« on: June 16, 2010, 02:59:00 am »

I think you forgot to send the attachment

32

Sharp PC-Z1 NetWalker / Netwalker's Kernel

« on: June 11, 2010, 05:13:11 pm »

Ok, there are also some positives of this digging. I found that LED currently controlled by WiFi driver can be reused for other tasks - I missed monitoring access to SD card or WiFi activity - this would be easy with slight kernel changes

I admire your efforts. I do not know almost anything about kernel programming but Im aware how complicated it is.
Is it very hard to make patch for blinking wifi led?

And another question: is it possible to get any sort of remote for netwalker (BT solution is known to me)? Zaurus has such solution (resistors in audio jack).

33

Sharp PC-Z1 NetWalker / Portabase

« on: June 07, 2010, 10:24:56 am »

Geeez Iqnotes!
I am willing to use one
kbasket is way too heavy.

If possible one IQnotes please.

34

Sharp PC-Z1 NetWalker / Which Window Manager Do You Use?

« on: June 06, 2010, 03:58:05 am »

I am using default gnome lxde.
Its pretty fast not much heavy.

Main advantage is easy setup of lots of panel goodies.
On zaurus I succesfully use matchbox.
It is nice there because fullscreen windows and very small resource usage.
Main pains is no panel gadgets and strange minimize behavior (window dissapears but process is still alive).

35

Off Topic forum / Xp On Sl C-1000

« on: June 06, 2010, 03:54:20 am »

So, can it not be done? I thought you could emulate an x86 processor with an ARM, just made it slower.

Its possible. Using qemu you can emulate lots of platforms, even x86. But it would be pretty slow.
I think you should ask your brother how it was done.

Possible scenarios:
-qemu (slow, not easy to set up)
-slideshow (just prepare coupe of slideshows)
-movie
-vnc/rdp to another computer.

36

Sharp PC-Z1 NetWalker / Working Hardware List: Ovation U727

« on: May 24, 2010, 04:38:03 am »

Usb - ethernet dongle based on pegasus II chipset - works fine no need for additional drivers.
usb bluetooth 1.2 dongles (pentagram and no name) works fine. Just plug and watch if led blinks.

Usb - ethernet dongle based on sr9600 chip - no success.
BT 2.0 (mini dongle from pentagram) - not working (but I did not tried too hard).

37

For Sale / Wanted / For Sale C1000

« on: May 12, 2010, 09:27:21 am »

I tried to find a good price but I can't find one on Ebay to compare.

I am also an c1000 owner. Currently I switched to netwalker.
C1000 is waiting for different usage. As far I can tell You will not get more than 100$ US for your device.
You will be lucky to get 50$.

For this reason I plan to make a web server from my c1000. It consumes very little power and can host apache+mysql+php very well.

Another way to ulilize c1000 is to embed it in home automation (temperature monitoring, simple automation - locking gates and so on). But that will require a bit of work.

38

Software / Eda - No Eagle For Arm But Kicad Is Quite Fine

« on: May 07, 2010, 04:03:38 am »

I do some electronic projects for fun.
Till now I was using Eagle to prepare pcb.
But there is no eagle for arm

So i started to use KiCAD. Main problem with it is a lack of element libraries.
I found a nice way to transfer eagle libraries to kicad format.
Just download eagle, install it on x86.
Then get ftp://ftp.cadsoft.de/eagle/userfiles/ulp/...2kicad-0.9b.ulp script, put it in eagledir/ulp
Run eagle, open desired library, there is a load of them, and click on "ULP" icon, select script (I renamed it to _eagle2kicad-0.9b.ulp to have it on first place), check Draw pin names and Draw pin numbers (that can be set in script), select place to put output files and run script.

Then, result files should be put in /usr/share/kicad/libraries and modules.

For now I have about 30 libraries exported. Did not test them much because i just started to learn kicad.

BTW.
Kicad is quite responsive on netwalker. Will try to check how it behaves on zaurus under zubuntu.

Any one know a nice tutorial on kicad?

Edited:
Just found nice bundle with all eagle libraries recoded:
http://library.oshec.org/
There is also a bundle with all of them pascked together...

39

Software / Qpdf3

« on: May 02, 2010, 05:14:50 am »

Hmmm the link goes to pdaxrom version. Is it correct version?
I did not found anything about cacko there.

40

Sharp PC-Z1 NetWalker / Kexec On Netwalker

« on: May 02, 2010, 05:12:21 am »

I'm also interested in that matter but not as parto of the creation process. Rather as a consumer.
It would be nice to have a possibility to bot another OS version but for now ubuntu is good enough to not have to do this
I hope You will make it work

41

Ubuntu / Post Install Tweeks

« on: May 01, 2010, 05:14:39 am »

Here is my script:
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']#!/bin/sh
ONE=$(grep Spitzkbd /proc/interrupts|md5sum)
while true
do
    sleep 240
    PLAYING=$(mpc|grep "play"|wc -l)
    if [ "$PLAYING" = 0 ]; then
   TWO=$(grep "Spitzkbd\|ts" /proc/interrupts|md5sum)
   #echo $ONE $TWO
   if [ "$ONE" = "$TWO" ]; then
       apm -s
        fi
    fi
ONE=$TWO
done[/div]

File with interrupts (/proc/interrupts) looks like this:
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']           CPU0
  3:       1240          SC  ohci_hcd:usb1
  6:         12          SC  pxa_i2c-i2c.1
 11:          0          SC  pxa27x_udc
 16:          0          SC  SSP
 17:         34          SC  LCD
 18:       2214          SC  pxa_i2c-i2c.0
 23:     158689          SC  pxa2xx-mci
 25:      17071          SC  DMA
 26:     295976          SC  ost0
 73:          0        GPIO  MMC card detect
 75:         40        GPIO  ts
 76:         87        GPIO  Spitzkbd Sense
 77:          0        GPIO  Spitzkbd HP Type, sharpsl_rc
 80:          0        GPIO  Spitzkbd Sync
 81:         77        GPIO  Spitzkbd Sense
 85:          0        GPIO  Fatal Battery
 98:         56        GPIO  Spitzkbd Sense
100:         79        GPIO  Spitzkbd Sense
102:        158        GPIO  Spitzkbd Sense
103:        763        GPIO  Spitzkbd Sense
154:          0        GPIO  Battery Cover
155:         82        GPIO  Spitzkbd Sense
158:          0        GPIO  PCMCIA0 CD
159:         30        GPIO  Spitzkbd PwrOn
160:         23        GPIO  Spitzkbd SWB
161:          4        GPIO  Spitzkbd SWA
165:          0        GPIO  CO
169:      10693        GPIO  ide0
179:          0        GPIO  AC Input Detect
180:          0        GPIO  Spitzkbd HP
Err:          0
[/div]
I think ide0 contains number of interrupts for cf card and pxa2xx-mci contains number of interrupts for sd card.

If you want to check activity of network card just check output of ifconfig and look for eth0, ppp0 wifi activity represented by number of bytes,sent/received.

In my case it was not important how much keys was pressed i just needed to know if anything happened so i used md5sum to check that.

There is a lot of ways to achieve result which You need, just peek in /proc or /sys and with simple script monitor what is happening in those files while You are doodling with zaurus and then write script to use that information and react.
You can use beeping instead led flash. Or you can try aosd_cat as a OSD visualizer.


I have written a small utility to show vital signs of my zaurus. I connected it to a keypress using .xbindkeysrc:
Look at "#show" battery section. When you press FN and 0 (zero) then /bin/batt script is executed.
Also Fn+9 is mpd toggle and fn+8 and Fn+7 is next and prev song

[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']###########################
# xbindkeys configuration #
###########################
#
# Version: 0.1.3
#
# If you edit this, do not forget to uncomment any lines that you change.
# The pound(#) symbol may be used anywhere for comments.
#
# A list of keys is in /usr/include/X11/keysym.h and in
# /usr/include/X11/keysymdef.h
# The XK_ is not needed.
#
# List of modifier (on my keyboard):
#   Control, Shift, Mod1 (Alt), Mod2 (NumLock),
#   Mod3 (CapsLock), Mod4, Mod5 (Scroll).
#
# Another way to specifie a key is to use 'xev' and set the
# keycode with c:nnn or the modifier with m:nnn where nnn is
# the keycode or the state returned by xev
#
# This file is created by xbindkey_config
# The structure is :
# # Remark
# "command"
# m:xxx + c:xxx
# Shift+...




#keystate_numlock = enable
#keystate_scrolllock = enable
#keystate_capslock = enable



#Brigtness Down
"display-brightness.sh down"
    m:0x40 + c:12
    Mod4 + 3

#Brightness Up
"display-brightness.sh up"
    m:0x40 + c:13
    Mod4 + 4

#Volume Down
"pcm down"
    m:0x40 + c:10
    Mod4 + 1
"pcm down"
    F19
   
#Volume Up
"pcm up"
    m:0x40 + c:11
    Mod4 + 2
"pcm up"
    F20
     
#show battery
"/bin/batt osd"
    m:0x40 + c:19
    Mod4 + 0

#toggle mpd
"mpc toggle"
    m:0x40 + c:18
    Mod4 + 9
"mpc toggle"
    F18
   
#prev mpd
"mpc prev"
    m:0x40 + c:16
    Mod4 + 7

#next mpd
"mpc next"
    m:0x40 + c:17
    Mod4 + 8


#Right Mouse Click
"xte 'mouseclick 3'"
   Control + b:1   (mouse)

#middle mouse click
"xte 'mouseclick 2'"
   Shift + b:1

#rotate
"/bin/rot"
   F10

"xte 'key Delete'"
    Mod4 + c:22
    #

#f1
#"xte 'key f1'"
#   Mod4 + 1

#rotate screen
"/bin/rot"
    m:0x40 + c:15

#fake alt-tab
"xte 'keydown Alt_L' 'key Tab' 'keyup Alt_L'"
    c:67
"xte 'keydown Alt_L' 'key Tab' 'keyup Alt_L'"
    F17
   
#fake alt-f4
"xte 'keydown Alt_L' 'key F4' 'keyup Alt_L'"
    c:96
   
#show desktop
"xte 'keydown Alt_L' 'key l' 'keyup Alt_L'"
    c:107
   
#
# End of xbindkeys configuration[/div]

It is helpful to use xev to check which codes are generated by X while pressing keyboard keys.

Here is a batt script:
It shows some nice information about Z

[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']#!/bin/sh

a=$(cat /sys/devices/platform/sharpsl-pm/battery_percentage)
f=$( free|grep Mem|awk '{ print $1 int($4/1024) }'|tail -n 3|tr "\n" " ")
l=$(top -b -n 1|grep "load average"|cut -d "," -f 3-6|cut -d ":" -f 2)
d=$(date)
s=$(amixer sget PCM|grep "\["|cut -d " " -f 4,6)


TEKST=$(echo -e "PCM\n$s\n$d\nbatt:$a \n$f \nload:$l")

echo -e "batt:$a $f load:$l"
if [ "$1" =  "osd" ]; then
aosd_cat -d 5000 -e 0 -F "Trebuchet 30" -s 3 -S 100 -r 1 -g 1 -b 0 -x 30 -y 30 -t "$TEKST"
fi
[/div]
And one more:
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']pcm script (used to change volume)

#!/bin/sh


STEP=3

if [ ! -n "$1" ]; then
    echo "max / current"
    amixer sget PCM
elif [ "$1" = "up" ]; then
    amixer sset PCM $STEP"%+"
elif [ "$1" = "down" ]; then
    amixer sset PCM $STEP"%-"
else
    echo -e "\nUsage:\n\t `basename $0` [up | down]\n"
fi[/div]

And if I remember correctly I have changed slightly standard zubuntu script to change display brightness.

[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']#!/bin/sh

# display-brightness.sh
# simple script to set display-brightness for zaurus clamshell
# author: patrick steiner <[EMAIL PROTECTED]>
# modified by: Ian Munsie <[EMAIL PROTECTED]>
# modified by: Paul M "speculatrix" - for Spitz/Zubuntu
# version: 1.02 | 15/12/2008 21:48 GMT

STEP=5
MAX_BRIGHTNESS=47
MIN_BRIGHTNESS=0

DRIVER="`ls /sys/class/backlight/|head -n 1`"
BRIGHTNESS_FILE="/sys/class/backlight/$DRIVER/brightness"
BRIGHTNESS=`cat /sys/class/backlight/$DRIVER/actual_brightness`
# this gives bad number - 15 is max, 16 is off!
#MAX_BRIGHTNESS=`cat /sys/class/backlight/$DRIVER/max_brightness`

POWER_FILE="/sys/class/backlight/$DRIVER/bl_power"
POWER_ON=0
#POWER_OFF=1


if [ ! -n "$1" ]; then
    echo "max / current"
    echo "$MAX_BRIGHTNESS / $BRIGHTNESS"
elif [ "$1" = "up" ]; then
    test -x /usr/bin/bl && bl on
    echo $POWER_ON >> $POWER_FILE
    if [ $BRIGHTNESS -lt $MAX_BRIGHTNESS ]; then
        let BRIGHTNESS=$BRIGHTNESS+$STEP
        if [ $BRIGHTNESS -ge $MAX_BRIGHTNESS ]; then
            let BRIGHTNESS=$MAX_BRIGHTNESS
        fi
        echo $BRIGHTNESS >> $BRIGHTNESS_FILE
    fi
elif [ "$1" = "down" ]; then
    test -x /usr/bin/bl && bl on
    echo $POWER_ON >> $POWER_FILE
    if [ $BRIGHTNESS -gt $MIN_BRIGHTNESS ]; then
        let BRIGHTNESS=$BRIGHTNESS-$STEP
        if [ $BRIGHTNESS -le $MIN_BRIGHTNESS ]; then
            let BRIGHTNESS=$MIN_BRIGHTNESS
        fi
        echo $BRIGHTNESS >> $BRIGHTNESS_FILE
    fi
elif [ "$1" = "off" ]; then
    if [ $BRIGHTNESS -ne 0 ];then
   echo "$BRIGHTNESS" >/tmp/backlight
   echo 0 > $BRIGHTNESS_FILE
    fi
elif [ "$1" = "on" ]; then
    cat /tmp/backlight > $BRIGHTNESS_FILE
    rm /tmp/backlight
else
    echo -e "\nUsage:\n\t `basename $0` [up | down]\n"
fi
[/div]

Combined together with .xbindkeyrc, those give quite nice result in usability of the zaurus. Dont forget ro run xbindkeys in your ./homedir/.xinitrc. the saver script is also executed there with background option (& ampersand at the end of a command)
BTW I use matchbox WM so there is not much to put in panel to monitor OS condition thats why i have those scripts.
Aosd_cat is quite slow to start but I use it rarely so it is not a problem.

42

Sharp PC-Z1 NetWalker / Netwalker Vs Zaurus (lets Say C1000)

« on: April 29, 2010, 08:38:46 am »

OK. After some time I can make a comparison.
I was using zaurus mainly for ebooking, games (cards and shisen like) and music. That was the 85% time spent with zaurus.
Rest of the time was abit of video, spreadsheet, notetaking and unix like activities.

I was using internet on zaurus only couple of times. Dangling cable for BT dongle was not convinient and WiFi is territory unknown to me.
My zaurus was equipped with 2GB CF and 2GB sd cards. Lots of space for emulator roms, books, images and so on.

The main pain of zaurus was RAM. That's why i tried to switch to next device. I considered eeepc but those are too big. I got oqo 01+ but it eats battery quite fast even in sleep mode. And hibernating takes about 30-40 seconds so it was unacceptable for notetaking.

Netwalker has only two disadvantages: it's not x86 compatible (i did not tried to emulate it under qemu but will try) and have no external buttons (available with lid closed).
I have no swap under netwalker and it is running smoothly.
Copying between one usb slot to other gives from 3,5MB/s to over 10MB/s (ram is acting as a buffer so 3,5MB is bottom for not loaded system - Tested on 2Gb files)
Most of the software is relatively quick to launch (planner, gimp, qcad, firefox about 20-40 seconds) and quite responsive.
PDF viewers are quick and shows documents very nicely. No corrupted graphics, no slowdowns, no lockups.
Video playback is acceptable.
Battery time gives me about 5-6h of normal work uptime and about 3h videoplayback (not measured just estimated).


I am happy with migration.

My advices for new owners:
Get small usb hub. Get mini usb cable for it.
Get BT dongle (I did not found BT with miniusb connector).
Get Big SD card (I got 8GB and it seems thats ok)
Get usb-ethernet dongle (but look for pegasus one, new ones have different chip and seems there is no module for it)


And finally one aesthetic problem: If lid is closed and sand gets between lid and battery lid and then lid is opened, sand will make ugly scratch on battery lid.  

43

C1000/3x00 Hardware / C1000 - Hw Pb With Touch Screen

« on: April 27, 2010, 02:07:26 pm »

From the command line, remove /etc/pointercal and run startx again.
or ts_calibrate should do the trick.

Late

Hi  InSearchOf,

Under PdaXRom, I've allready remove /etc/pointercal  and run startx again : the display stay "off-line".

The screen is rougly working in DEBUG-MODE but not with an OS ...?

Thanks.

The question is whether this test is showing good behavior of your TS.

Check if there is no sand/screen protector between screen and its bezel.
If something is there then it is constantly pressing touch screen and acting strangely.
Try to peek straight device for any data going from there when you touching TS. This will give you any idea if communication is working.

44

Ubuntu / Post Install Tweeks

« on: April 26, 2010, 06:30:33 am »

tweak a bit zaurus leds:
echo mmc0 > /sys/class/leds/spitz\:green\:mail/trigger
echo ide-disk > /sys/class/leds/spitz\:amber\:charge/trigger

if you like put it in /etc/init.d/zaurusd right after echo "starting zaurusd"
this gives you blinking leds while accessing cards.

This would seem to be wrong or at least outdated. If I add

Code: [Select]

echo "mmc0" > /sys/class/leds/spitz\:green\:hddacti/trigger
to zaurusd then the green led blinks whilst zubuntu boots then after its booted (ie after running the zaurusd daemon) the green LED only blinks when I access the SD card.

As far as I can tell you can only have one event / device (in this case mmc0 or ide-disk) assigned per LED trigger although under 2.4 based distros my green LED would flash when I accessed either the CF or SD interfaces.

Have I misunderstood or is there a workaround for this?

Well, I have only c1000 device so I cant tell how other devices behave. I confirm that there is possible to have only one device triggering LED. At least I did not try to echo something else than one trigger name.
Your code is correct and works as should to.
In c1000 there are two leds. And in my case I have two leds for cf and sd card blinking separately.

Additionally I can tell that amber led (charge) is acting problematically. Sometimes it works and sometimes it does not blink even when I am reading files on cf card.

I knew that I could use the amber led to monitor SD activity if I wanted to but I'd rather leave that as a charge indicator.

I can only presume that the Zaurus LED triggering worked differently under 2.4 kernels and you could assign multiple devices to trigger the same LED?

I have no idea. I think (but dont have any hard base on it) that in 2.4 kernel green led was used by some sort proprietary code to show any activity.

But just got an idea.
Try to look in /proc and /sys and search for interrupts information. I took numbers from /proc/interrupts or similar.
I did screensaver replacement for zubuntu on c1000 by looking number of interrupts generated by keyboard to put zaurus to sleep after some time without keypress (and touch screen taps) but only when mpd is stopped/paused.

I grepped file with interrups cuted number of them and compared with the same file after some sleep.

You can do the same to the led. Just grep interrupts or counters for cf, sd, network, put those in variable and sleep 1 sec.
If numbers change do a blink led.
It will be much less responsive but will act as you expect.

I will try to post my sleep script in a few days (im away from zaurus).

45

Ubuntu / Post Install Tweeks

« on: April 25, 2010, 03:15:51 pm »

tweak a bit zaurus leds:
echo mmc0 > /sys/class/leds/spitz\:green\:mail/trigger
echo ide-disk > /sys/class/leds/spitz\:amber\:charge/trigger

if you like put it in /etc/init.d/zaurusd right after echo "starting zaurusd"
this gives you blinking leds while accessing cards.

This would seem to be wrong or at least outdated. If I add

Code: [Select]

echo "mmc0" > /sys/class/leds/spitz\:green\:hddacti/trigger
to zaurusd then the green led blinks whilst zubuntu boots then after its booted (ie after running the zaurusd daemon) the green LED only blinks when I access the SD card.

As far as I can tell you can only have one event / device (in this case mmc0 or ide-disk) assigned per LED trigger although under 2.4 based distros my green LED would flash when I accessed either the CF or SD interfaces.

Have I misunderstood or is there a workaround for this?

Well, I have only c1000 device so I cant tell how other devices behave. I confirm that there is possible to have only one device triggering LED. At least I did not try to echo something else than one trigger name.
Your code is correct and works as should to.
In c1000 there are two leds. And in my case I have two leds for cf and sd card blinking separately.

Additionally I can tell that amber led (charge) is acting problematically. Sometimes it works and sometimes it does not blink even when I am reading files on cf card.