OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: Bundabrg on September 13, 2004, 01:56:49 am
-
Hi All,
Just have some misc queries. My apologies if they are a FAQ or located somewhere, but with extensive googling I've been unable to find an answer to them yet.
Background
I have a C860, running pdaXrom Katherin RC3
90Mb Root partition, rest user
1Gb SD Card mounted /mnt/card
Till my wireless CF card arrives, I'm using the usb cable through my notebook (Debian Sid) running NAT iptables.
Questions
1. I notice that the silkscreen buttons are usable in RC3. How do I remap them to other commands?
2. I'm not sure if this is a problem with the ROM or something up with the USB network connection between the C860 and my notebook (Debian Sid). When I try to use ipkg (or even just wget) to get some ipk files (from the http://www.pdaxrom.org/feed2) (http://www.pdaxrom.org/feed2)), when its uncompressing the file, I get the following error:-
tar: Skipping to next header
gzip: stdin: invalid compressed data--crc error
gzip: stdin: invalid compressed data--length error
tar: Child returned status 1
tar: Error exit delayed from previous errors
If I wget the same file on my laptop, and scp it to the C860, it installs/untars fine. Performing a 'diff' of the two files shows that they are different (though both have the same size).
I know that pdaXrom has an older ipkg and that some ipk are 'ar' files. The files I'm testing are definately tgz. Just so you know I've symlinked /home/tmp to /mnt/card/tmp so its got the whole 1Gb of SD avail for use (and I've tried the same thing with a 512Mb CF I've got here as well). My df as well is:-
# df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/mtdblock/2 92160 48016 44144 52% /
none 12288 0 12288 0% /dev/shm
/dev/mtdblock/3 31744 1952 29792 6% /home
/dev/mmcd/disc0/part1 987720 1212 936336 0% /mnt/card
3. Is it worth upgrading ipkg to the newer one? If so, how? (This one I've been unable to find anywhere, just hints thats its possible by downgrading libc.so.6).
4. How do I access the F1-F10 keys.
5. Matchbox seems to allow right-clicks by simply holding a click on an item (like the old single button macs). However, this delay is sometimes really short (especially when using Xstroke as it cuts the letters in half). How do I change this delay?
Things I've noticed
a. RC3 definately has a slight screen flicker. It can be hard to see sometimes but at othertimes its quite noticable. (This has been reported many times. I'm just adding that I've seen it as well).
b. Sometimes auto-rotate doesn't work (Need to click it into the portrait/landscape mode twice for it to recognize the change).
c. Performing a 'dmesg' gives LOTS and LOTS of the following line: -
-W- Don't delete.
If I scroll back, the last lines from dmesg that are not like this are: -
devfs_register(part1): could not append to parent, err: -17
w100fb set 640x480 (VGA 90 degrees)
edit
d. When the screen blanks AND the pda is plugged into power, I can hear a high pitched noise, similar to the noise you hear if you put your monitor onto a frequency that is too high.
Final Word
Ok thats everything I can think of. Thanks to those who have helped so far and to those who have put all the work into these interesting devices. Its quite nifty to see my tetrinetx server run on a palm sized device .
Bundaberg
-
I give you an up. Interesting thread... and I'd like to know how to remap touch-buttons too!
hi
-
Things I've noticed
a. RC3 definately has a slight screen flicker. It can be hard to see sometimes but at othertimes its quite noticable. (This has been reported many times. I'm just adding that I've seen it as well).
Agreed. And I think those that don't see it just have poor eyes.
Seriously, it's hard to notice if you don't look closely. The whole image is shaky. Maybe it is specific to C860?
-
I see a slight flicker on the (left) side of my 700 ...
I also get a "buzz" on some headsets when the AC is plugged into the pda.
the buzz sounds like bad grounding... or something.
Scott
-
Seriously, it's hard to notice if you don't look closely. The whole image is shaky. Maybe it is specific to C860?
Same thing on C760.
-
no flicker here. Maybe I cannot see any flickering because of the poorness of my screenprotector.
-
no flicker here. Maybe I cannot see any flickering because of the poorness of my screenprotector.
Try increasing the brightness to the maximum -- then it flickers most.
-
A flickering C700 is a symptom for an overclocked kernel. Disable the fast sysclock and the higher cccr setting.
-
4) The F keys appear to be turned off by default, you can turn them on again by remoiving the exclamation marks from the file /etc/X11/kb/corgi.xmodmap where the F keys are defined.
Fn-1 Fn-2 etc then become F1 F2 etc.
-
XorA
Thanks for the tip. Will look at that file soon.
Rest
Interestingly the screen flickers more just when you turn it on (probably makes sense). It stabalises a bit after a while, but still flickers, though when I show it to some others they can't see it at all. Doesn't bother me that much, just something to note.
-
Ok finnally cracked it.
The important files are the following: -
- /etc/X11/kb/corgie.xmodmap
- /etc/xdg/openbox/rc.xml
The first obviously contains the keymap. This includes the silkscreen buttons, infact every button on the device including the screenswivel.
The second contains actions, ie the action XF86WWW (mapped in corgie.xmodmap to the web silkscreen button) is set to execute "dillo". Alsoo has stuff for how long a mouse being held down becomes a doubleclick. All I need now is to figure out how to map a key to a mouse button (i know, xkeymouse will probably be needed).
Here is my corgie.xmodmap (/etc/X11/xinit/.Xmodmap symlinks to this file). Its a modification of one provided by Foxdie. It maps the japanese keys to ctrl and alt.
---------------------------------
! 'Fn' key setup for c700
! Rewritten by Foxdie
! Modified by Bundaberg
! Added c860 keys
! Put in my own modifications
! Clear old modifiers
clear Mod1
clear Mod2
clear Mod3
clear Mod4
clear Mod5
remove Control = Control_L
! First row
! normal shift+key fn+key shift+fn+key
keycode 49 = 1 exclam F1 NoSymbol
keycode 50 = 2 quotedbl F2 NoSymbol
keycode 51 = 3 numbersign F3 NoSymbol
keycode 52 = 4 dollar F4 NoSymbol
keycode 53 = 5 percent F5 NoSymbol
keycode 54 = 6 ampersand F6 NoSymbol
keycode 55 = 7 apostrophe F7 NoSymbol
keycode 56 = 8 parenleft F8 NoSymbol
keycode 57 = 9 parenright F9 NoSymbol
keycode 58 = 0 asciitilde F10 NoSymbol
keycode 39 = BackSpace BackSpace KP_Delete KP_Delete
! Second row
! normal shift+key fn+key shift+fn+key
keycode 25 = q Q NoSymbol NoSymbol
keycode 31 = w W asciicircum NoSymbol
keycode 13 = e E equal NoSymbol
keycode 26 = r R plus NoSymbol
keycode 28 = t T bracketleft NoSymbol
keycode 33 = y Y bracketright NoSymbol
keycode 29 = u U braceleft NoSymbol
keycode 17 = i I braceright NoSymbol
keycode 23 = o O NoSymbol NoSymbol
keycode 24 = p P NoSymbol NoSymbol
! Third row
! normal shift+key fn+key shift+fn+key
keycode 73 = Tab Tab Caps_Lock Caps_Lock
keycode 9 = a A NoSymbol NoSymbol
keycode 27 = s S NoSymbol NoSymbol
keycode 12 = d D period period
keycode 14 = f F backslash backslash
keycode 15 = g G semicolon semicolon
keycode 16 = h H colon colon
keycode 18 = j J asterisk asterisk
keycode 19 = k K NoSymbol NoSymbol
keycode 20 = l L bar bar
! Fourth Row
! normal shift+key fn+key shift+fn+key
keycode 35 = Shift_L
keycode 34 = z Z NoSymbol NoSymbol
keycode 32 = x X XF86Cut NoSymbol
keycode 11 = c C XF86Copy NoSymbol
keycode 30 = v V XF86Paste NoSymbol
keycode 10 = b B underscore underscore
keycode 22 = n N NoSymbol NoSymbol
keycode 21 = m M NoSymbol NoSymbol
keycode 111 = Shift_R
keycode 36 = Return Return KP_Enter KP_Enter
! Fifth Row
! normal shift+key fn+key shift+fn+key
keycode 38 = Mode_switch
keycode 129 = Control_L
keycode 130 = Alt_L
keycode 66 = minus minus at at
keycode 100 = space space bar bar
keycode 71 = slash comma less less
keycode 72 = period question greater greater
keycode 44 = Up Up Prior Prior
! Sixth Row
! normal shift+key fn+key shift+fn+key
keycode 96 = NoSymbol
keycode 97 = NoSymbol
keycode 98 = NoSymbol
keycode 48 = XF86Start
keycode 42 = Escape
keycode 48 = Return
keycode 37 = XF86MenuKB
keycode 43 = Left Left KP_Home KP_Home
keycode 45 = Down Down Next Next
keycode 46 = Right Right KP_End KP_End
! Side buttons
keycode 117 = XF86PowerDown
keycode 134 = Down
keycode 133 = Up
keycode 131 = Return
keycode 132 = Escape
! Screen swivel sensor
keycode 110 = XF86RotateWindows
! Codes 118,119,120,121,122 correspond to the silkscreen keys
! on a C860 - not sure yet how to change these actions. I think
! it would be better to do this under xkeymap?
keycode 118 = XF86WWW
keycode 119 = XF86Favorites
keycode 120 = XF86Messenger
keycode 121 = XF86Book
keycode 122 = XF86Clear
! Remap locks
add Control = Control_L
! Modifiers
add mod1 = Alt_L Alt_L Alt_L
add mod2 = Mode_switch
!add mod3 = Control_L Control_L Control_L
-------------------------------------------------------------------
-
3. Is it worth upgrading ipkg to the newer one? If so, how? (This one I've been unable to find anywhere, just hints thats its possible by downgrading libc.so.6).
Are you talking about my posts?
In that case, it's certainly not downgrading libc. If you use the ipkg package from the OZ 3.3.5 feed it'll work with pdaXrom (otherwise you'd have to *upgrade* libc). I found it better to use as I don't use the graphical interface (though it should still work fine) and the default version requires that the command line parameters come in a certain order (not the one I use), also ipkg-link and ipkg package installation failures are graceful unlike with the default ipkg script.
To install it, take the data.tar.gz file from the ipkg*.ipk package from the feed and just extract it over the current components (cd / && tar -zxvf /path/to/data.tar.gz) should work.
Before you do this you should note that I'm not sure how the control file syntax on the pdaXrom packages is formulated (I've had some troubles trying to install pdaXrom packages on OZ - not sure why, but probably because OZ tends to be more picky about the control file), therefore you may be better installing the OZ components by hand (with a different name for example) so you can still use the pdaXrom version if things won't install.
Si