Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Capn_Fish

Pages: 1 [2] 3 4 ... 157
16
Mer / Fluxbox Install How-to
« on: July 23, 2009, 10:29:04 am »
Here's my simple how-to for installing Fluxbox on an N810 with Mer. N800 users may want to stay away, as this disables the built-in keyboard.

1. Install and remove some packages:

Code: [Select]
sudo apt-get remove osso-xterm
sudo apt-get install fluxbox xterm

2. Make Fluxbox start up instead of Hildon stuff:

Code: [Select]
sudo rm /etc/alternatives/x-session-manager
sudo cp /usr/bin/startfluxbox /etc/alternatives/x-session-manager

3. Edit some files for usability:

Code: [Select]
#~/.fluxbox/keys

#Fullscreen button on top and window-switch button on face
F16 :NextWindow
Shift F6 :FullScreen

# fullscreen button, -, and + (in that order); chenges mouse buttons
F6 :exec xmodmap -e "pointer = 1 2 3";xsetroot -cursor_name left_ptr
F8 :exec xmodmap -e "pointer = 3 2 1";xsetroot -cursor_name right_ptr
F7 :exec xmodmap -e "pointer = 2 1 3";xsetroot -cursor_name hand2

#Requires chmodding, not necessary if you don't FUBAR / uninstall all of the Hildon stuff
Shift F7 :exec echo  0 > /sys/class/leds/keyboard/brightness
Shift F8 :exec echo 30 > /sys/class/leds/keyboard/brightness

Control Mod1 Left :PrevWorkspace
Control Mod1 Right :NextWorkspace

# click on the desktop to get menus
#Very nice to not have to change mouse buttons
OnDesktop Mouse1 :HideMenus
OnDesktop Double Mouse1 :RootMenu

#whatever else you want to stick here

Code: [Select]
! ~/.Xmodmap
! A little strange, but more usable than the default

clear Mod1
clear Mod2
clear Mod3
clear Mod4
clear Mod5

! Top row
keycode 24 = q Q 1 F1
keycode 25 = w W 2 F2
keycode 26 = e E 3 F3
keycode 27 = r R 4 F4
keycode 28 = t T 5 F5
keycode 29 = y Y 6 F6
keycode 30 = u U 7 F7
keycode 31 = i I 8 F8
keycode 32 = o O 9 F9
keycode 33 = p P 0 F10

! Middle row
keycode 38 = a A exclam exclam
keycode 39 = s S quotedbl quotedbl
keycode 40 = d D  at at
keycode 41 = f F numbersign numbersign
keycode 42 = g G backslash backslash
keycode 43 = h H slash slash
keycode 44 = j J parenleft parenleft
keycode 45 = k K parenright parenright
keycode 46 = l L asterisk asterisk
keycode 48 = slash apostrophe question question

! Bottom row
keycode 52 = z Z grave grave
keycode 53 = x X asciicircum asciicircum
keycode 54 = c C asciitilde asciitilde
keycode 55 = v V percent percent
keycode 56 = b B ampersand ampersand
keycode 57 = n N dollar dollar
keycode 58 = m M bar bar
keycode 47 = semicolon colon
keycode 20 = minus quotedbl underscore underscore
keycode 21 = plus numbersign equal equal

! Others (backspace, return, etc.)
keycode 22 = BackSpace
keycode 36 = Return
keycode 50 = Shift_L
keycode 105 = Control_L
keycode 60 = period greater bracketright braceright
keycode 59 = comma less bracketleft braceleft
keycode 65 = space
keycode 135 = Alt_L
keycode 108 = Mode_switch

! Keypad, menu, and screen keys
keycode 70 = Tab
keycode 104 = Return
keycode 111 = Up Prior
keycode 114 = Right End
keycode 116 = Down Next
keycode 113 = Left Home
keycode 71 = F16
keycode 9 = Escape


add mod1 = Alt_L
add mod2 = Mode_switch

Code: [Select]
# ~/.fluxbox/startup

#!/bin/sh
#
# fluxbox startup-script:
#
# Lines starting with a '#' are ignored.

# Change your keymap:
xmodmap ~/.Xmodmap

gksudo nm-applet &
xterm &

#Left and down don't autorepeat by default
xset r 116 &
xset r 113 &
#gksudo /etc/init.d/ssh start &

# And last but not least we start fluxbox.
# Because it is the last app you have to run it with ''exec'' before it.

exec fluxbox

4. Reboot

Code: [Select]
sudo reboot
You should boot into Fluxbox after that.

EDIT: Added N810 package (eg, compiled with N810 CFLAGS)

EDIT2: Corrected the path for x-session-manager

17
Zaurus - pdaXrom / Fluxbox 1.0.0 Ipk Released
« on: July 21, 2009, 04:07:39 pm »
Yeah, I've been using Fluxbox on my N810, and right/middle clicking is a breeze. I should probably give EvilWM a go on it, but the keyboard is crummy enough that I don't really want to.

Fixing things is the easy part. I do it when things annoy me, and sharing how to do it is trivial.

18
Ubuntu / Very Quick Keyboard
« on: July 21, 2009, 04:00:46 pm »
run 'xev' from a terminal, then press the button you want the code of. It will show up in the terminal.

19
Zaurus - pdaXrom / Fluxbox 1.0.0 Ipk Released
« on: July 18, 2009, 08:50:57 pm »
For clarification, it shouldn't matter which kernel is being run. Issues arise with different glibc versions, which also changed between beta3 and beta4/r1xx.

20
Ubuntu / Very Quick Keyboard
« on: July 13, 2009, 08:24:07 pm »
You should be able to use 'xset' to change repeat rate.

As for mapping, it's likely one of:

/etc/keymap.map (or something similar)
/etc/X11/Xmodmap
~/.Xmodmap

21
Ubuntu / Mplayer Question
« on: July 05, 2009, 05:35:07 pm »
Well, yes and no. The pdaXrom ipks are tarballs, but Angstrom ipks are ar archives.

22
Ubuntu / Mplayer Question
« on: July 03, 2009, 10:23:45 am »
I'm not sure which is more optimized, the Angstrom MPlayer or this one:

http://www.tyrannozaurus.com/feed/beta3/fe...-1_armv5tel.ipk

Feel free to try both.

Yes, the install method is "download and extract the ipk to /, install deps (from Ubuntu repos) as necessary."

Extracting (as root):

Code: [Select]
cd /
tar -xf /path/to/mplayer_whatever_armv5te.ipk
tar -xpvf data.tar.gz
rm data.tar.gz debian-binary control.tar.gz

23
Debian / Right Click
« on: June 29, 2009, 11:44:45 am »
I might as well throw my latest in here as well...

My current setup just uses Fluxbox's event grabber to run "xmodmap -e 'pointer = 3 2 1'" or similar commands. I also have it change the cursor so I can visually check what button will be pressed at any given time.

The other option (I haven't tried this yet) is to add
Code: [Select]
Option          "EmulateRightButton"    "1"to the "input" section of xorg.conf. That SHOULD enable press-and-hold right clicking.

Like I said, I haven't tried it, so YMMV.

Hope that helps somebody.

24
Angstrom & OpenZaurus / Create New Image For Zaurus
« on: June 13, 2009, 08:00:16 am »
Build your own here (without OpenEmbedded):

http://amethyst.openembedded.net/~koen/narcissus/

25
Off Topic forum / Zaurus Cluster How To With Distcc
« on: June 09, 2009, 07:14:07 pm »
OK, it turns out this is really easy. I'm going to do this from the prospective of two Zaurii running Zubuntu, so adapt it however necessary. This is a rough draft, so please don't expect everything to be absolutely correct the first time around.

Note that you COULD do this over traditional networks, but that the latency would slow things down to some extent (and it's pretty awesome to have a mini USB network cluster going).

A generic example can be found here.

0. Get USB networking between all of the involved devices going (not going in-depth on this, look it up):

Sample /etc/network/interfaces:
Code: [Select]
iface usb0 inet static
address 192.168.2.4
netmask 255.255.255.0
gateway 192.168.2.1

Then run:
Code: [Select]
ifup usb0
If all went well, you should be networked.

1. Install the necessary tools (both machines):
Code: [Select]
sudo apt-get install build-essential automake autoconf python2.5-dev
2. Download the latest distcc source (3.1 as of this writing, both machines unless you want to compile and transfer):
Code: [Select]
wget http://distcc.googlecode.com/files/distcc-3.1.tar.gz
3. Build distcc (both machines, once again, unless you want to compile and transfer):
Code: [Select]
tar -xf distcc-3.1.tar.gz
cd distcc-3.1
./configure --prefix=/usr --without-get --without-gnome --disable-Werror
make
sudo make install

4. Add a "distcc" user (both machines):
Code: [Select]
useradd distcc
5. Start the server (both machines, I believe):
Code: [Select]
distccd --daemon --allow "127.0.0.1 xxx.xxx.xxx.xxx"
6. On the machine "doing" the build, export the hosts:
Code: [Select]
export DISTCC_POTENTIAL_HOSTS='127.0.0.1 xxx.xxx.xxx.xxx'
7. Run the build ("host" machine only, NUMBER_OF_THREADS should probably be the number of machines available + 1, IIRC):
Code: [Select]
cd /to/source/dir/
pump make -jNUMBER_OF_THREADS CC=distcc

8. Check to make sure everything is working (on "host" machine only):
Code: [Select]
distccmon-text
If you see something like:
Code: [Select]
object_abc.o [0]: localhost
object_xyz.o [1]: 192.168.2.3

Sample speedups:
Building distcc using distcc (N810 and SL-C3100, using "pump make -j3 cc=distcc"):4 minutes, 49 seconds
Building distcc using only the N810: 4 minutes, 52 seconds

That's not really the speedup I was hoping for, but I'll try to build some other things and see how it pans out.

Anyway, I hope somebody finds this useful.

26
Ubuntu / Stupid Question But
« on: June 07, 2009, 09:03:48 pm »
Well, for MPlayer, you should use the optimized pdaX/Angstrom versions, but for others, the command should be:

Code: [Select]
apt-get source --build PACKAGENAME
Or so I gather.

27
Off Topic forum / Zaurus Cluster How To With Distcc
« on: June 07, 2009, 12:34:55 pm »
I can't remember if I've asked this before, but here goes: It it possible/feasable to USB network all of my ARM devices, running a common OS (Ubuntu/Debian, likely) and have a mini-cluster going to speed up native builds? It would seem that with 2 Zaurii and an N810 (and hopefully a Pandora soon), I could get things built 2-3x faster, which would be nice.

I suspect something with distcc could be done, but my impression is that that ignores the "host" CPU (eg, if I started the build on the N810, only the two Zaurii would actually do work), making it less than optimal. Is that correct?

Anyway, thoughts, how-tos, etc.?

EDIT: It looks completely possible. I guess this thread will likely turn into a how-to once I get around to it.

EDIT 2: Changed the thread title, see the next post for the tutorial.

28
Ubuntu / Stupid Question But
« on: June 07, 2009, 12:29:45 pm »
So are you talking about things that are in the Ubuntu repos, but not the Ubuntu-armel repos, or apps that Ubuntu doesn't have any packages for? The former is much easier to accomplish (eg, apt-get the_command_to_build_from_source_here and you're done).

29
Software / Slc1000 As A Wireless Print Server
« on: June 02, 2009, 06:12:47 pm »
I think your best bet is probably to use ZUbuntu (as everything you need works "out of the box," AFAIK). After you get that running, it should just be a matter of finding out how to configure CUPS. I can't help you with that, unfortunately.

30
User Request for Applications / Backtrack On An Sl-c1000
« on: June 02, 2009, 06:10:06 pm »
You can build your own images here:

http://amethyst.openembedded.net/~koen/narcissus/

It's easy to do and takes something like two minutes.

If you need to contact the Angstrom folks, use their mailing list. They don't check the forums much/at all.

Hope that helps.

Pages: 1 [2] 3 4 ... 157