User:MartinDengler: Difference between revisions
Jump to navigation
Jump to search
m (fix pre-formatted text in journal2 section) |
No edit summary |
||
Line 1: | Line 1: | ||
{{Latest Releases | firmware = inline | devel = inline | extra = inline}} |
|||
== About Me == |
|||
I program for a living. I got an XO to support the OLPC project and have a laptop for daily use. |
|||
I work with python and use Fedora a lot. |
|||
See also [http://wiki.sugarlabs.org/go/User:MartinDengler My SugarLabs page] |
|||
== journal2 playing == |
|||
m_stone's instructions as to how to get journal2 running: |
|||
<pre> |
|||
18:21 < m_stone> mtd: yum install git, git clone git://dev.laptop.org/users/mstone/journal2 |
|||
18:22 < m_stone> then yum install pinot, then wget http://teach.laptop.org/~mstone/pinot.rpm then rpm -Uvh --force pinot.rpm |
|||
18:22 < m_stone> you need to tell pinot to start indexing useful things like your home-dir. |
|||
18:23 < m_stone> to do that, just follow the instructions at pinot.berlios.de -- i.e. run 'pinot' and edit its preferences to start indexing. |
|||
18:23 < m_stone> mtd: then wait a while for indexing. :) |
|||
18:23 < m_stone> mtd: it gets a lot faster once that's done. |
|||
18:22 < m_stone> then cd journal2; python gui.py |
|||
</pre> |
|||
TODO: |
|||
<pre> |
|||
18:19 < m_stone> mtd: you should play with scott's journal2 work. it's easy to get running on 767 and it could use some love. |
|||
18:19 < mtd> m_stone: what type of love? |
|||
18:20 < m_stone> mtd: well, it's currently a cute little desktop search gui, but it doesn't really know how to talk to launch anything. |
|||
18:20 < m_stone> so that would be good first step. |
|||
18:20 < m_stone> it could use a nice detail view for its search results |
|||
18:24 < m_stone> mtd: I think the other thing that would really help would be drawing in the results background with a 'no results' symbol or text when no results are available |
|||
18:25 < m_stone> mtd: and getting it to display results incrementally as they come it. |
|||
18:25 < m_stone> mtd: scott took care when designing his dbus api to let you pick out ranges of results on demand. |
|||
18:25 < m_stone> but the gui batches up the graphical updates all at once. |
|||
</pre> |
|||
== frame clock == |
|||
This should add a [http://www.xades.com/proj/clock_frame_767_screenshot.png digital clock] to the frame with the format MM/DD HH:MM. Requires build 767 (current stable and G1G1 2008 build): |
|||
1. Launch Terminal and become root by typing 'su -' (without the quotes) |
|||
2. Type EXACTLY, ALL ON ONE LINE (mind your spaces and minuses and capitals!) |
|||
wget -O - http://www.xades.com/proj/clock_device_767.tar.gz | tar xvzf - -C /usr/share/sugar/shell |
|||
...and it may be useful to recall that "copy" in Browse is Ctrl-C, and "paste" in Terminal is Shift-Ctrl-V. |
|||
3. Restart Sugar by pressing Ctrl-Alt-Backspace (you will lose all your open programs and data, so be sure to save anything you want first) |
|||
== Bugs I'm interested in == |
|||
[http://dev.laptop.org/query?status=assigned&status=new&status=reopened&cc=~mtd&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component Cced] |
|||
[http://dev.laptop.org/query my own] |
|||
== rebuilding the kernel with tuxonice support == |
|||
I'm working on [[ TuxOnIce]] support, so I'm editing the [[MTDKernelRebuild|kernel rebuild instructions]]. |
|||
== kernel module building for compcache == |
|||
To build a kernel module on a joyride XO, ensure you have make and gcc (yum -y install make gcc should do it) and then try: |
|||
<pre> |
|||
#get joyride kernel-devel rpm |
|||
wget http://dev.laptop.org/~dilinger/{stable,testing}/kernel-devel-`uname -r`.i586.rpm |
|||
sudo rpm -ivh kernel-devel-`uname -r`.i586.rpm |
|||
sudo cp -af /boot/* /versions/boot/current/boot/ |
|||
#get compcache |
|||
wget http://compcache.googlecode.com/files/compcache-0.3.tar.gz |
|||
tar xzf compcache-0.3.tar.gz |
|||
cd compcache-0.3 |
|||
make |
|||
#use it |
|||
sudo ./use_compcache.sh |
|||
</pre> |
|||
== XO/OLPC mini-projects == |
|||
I'm interested in helping with: |
|||
* {{Trac|2954|Implementing ebook mode}} |
|||
* {{Trac|4646|Sugar grabs too many shortcut keys}} |
|||
* and anything else that looks interesting |
|||
== Ambient temperature tracking == |
|||
<pre> |
|||
bash-3.2$ cat /ofw/openprom/model ; echo |
|||
CL1 Q2D13 Q2D |
|||
bash-3.2$ cat /boot/olpc_build |
|||
update.1 691 |
|||
bash-3.2$ for f in /sys/class/power_supply/olpc-battery/temp* ; do (echo -e $f\\t ; cat $f) | paste - - ; done |
|||
/sys/class/power_supply/olpc-battery/temp 2783 |
|||
/sys/class/power_supply/olpc-battery/temp_ambient 3900 |
|||
</pre> |
|||
bemasc explained things on #olpc [I edited out background chatter]: |
|||
<pre> |
|||
bemasc: "ambient" means "ambient in the case" |
|||
bemasc: battery means in the battery compartment |
|||
bemasc: the "ambient" thermometer is on the motherboard |
|||
bemasc: not sure which chip |
|||
bemasc: they were trying to place in the antenna |
|||
bemasc: so that it would be far from the heat sources |
|||
mtd: bemasc: so I guess if I want to know the temperature outside the case, the lower of the two numbers is closer to that (though still quite inaccurate) |
|||
bemasc: the battery temp is closest, yeah |
|||
bemasc: if you have another thermometer, you might consider trying to work out the offset and correct for it |
|||
bemasc: it'll be different depending on whether the battery is charging or discharging, and how fast |
|||
bemasc: and it'll take at least a few minutes to stabilize |
|||
bemasc: so it's not easy, but it's also not impossible |
|||
</pre> |
|||
== Misc snippets to remember == |
|||
Backlight and blurring switched off, makes some pdfs more readable: |
|||
<pre> |
|||
su -c "echo 1 > /sys/devices/platform/dcon/output" |
|||
</pre> |
|||
== How to explicitly forget/add a WPA wireless network == |
|||
If you want to forget/add a WPA wireless network explicitly, stop NetworkManager (/etc/init.d/NetworkManader stop) and edit |
|||
<pre> |
|||
/home/olpc/.sugar/default/nm/networks.cfg |
|||
</pre> |
|||
== Screen battery status hint == |
|||
<pre> |
|||
Date: Sat, 5 Jan 2008 18:09:19 +0000 |
|||
From: Martin Dengler <martin@martindengler.com> |
|||
Subject: Battery capacity in screen hardstatus line hint |
|||
To: devel@lists.laptop.org |
|||
[-- PGP output follows (current time: Sat 05 Jan 2008 06:23:51 PM GMT) --] |
|||
gpg: Signature made Sat 05 Jan 2008 06:09:19 PM GMT using DSA key ID 75C7D2F8 |
|||
[GNUPG:] SIG_ID AwM6Me4nlHAq/mT0qRJbz79n4sk 2008-01-05 1199556559 |
|||
[GNUPG:] GOODSIG 81B444DD75C7D2F8 martin@martindengler.com |
|||
gpg: Good signature from "martin@martindengler.com" |
|||
[GNUPG:] VALIDSIG 565C8F33ABF72DAA33DEB9CB81B444DD75C7D2F8 2008-01-05 1199556559 0 3 0 17 2 01 565C8F33ABF72DAA33DEB9CB81B444DD75C7D2F8 |
|||
[GNUPG:] TRUST_ULTIMATE |
|||
[-- End of PGP output --] |
|||
[-- The following data is signed --] |
|||
Hi, |
|||
In case this is of use to anyone, I've put the battery capacity in my |
|||
xo screen instance's hardstatus line with this tiny script & screenrc |
|||
change: |
|||
---------- /home/olpc/bin/olpc_screen_status.sh |
|||
#!/bin/bash |
|||
# Author: Martin Dengler <martin@martindengler.com> |
|||
# idea from http://www.mail-archive.com/screen-users@gnu.org/msg00322.html |
|||
# based on battery info from olpc-logbat |
|||
# |
|||
B_INFO=/sys/class/power_supply/olpc-battery |
|||
while true |
|||
do |
|||
CAP=`cat $B_INFO/capacity` |
|||
echo b:$CAP% |
|||
sleep 60 |
|||
done |
|||
---------- |
|||
....screenrc change: |
|||
---------- /home/olpc/bin/.screenrc |
|||
# run command forever and assign most recent output to string escape %1` |
|||
backtick 1 0 0 /home/olpc/bin/olpc_screen_status.sh |
|||
# the ...%1`... part at the end is the important part |
|||
hardstatus alwayslastline "%{.bW}%-w%{.rW}%n %t%{-}%+w %=%{..G} %H %{..Y} %m/%d %C%a %1` " |
|||
---------- |
|||
</pre> |
|||
I'd be interested to know how to get at the ambient temperature sensor |
|||
mentioned in section 2.4.1 of the CL1 hardware design specification |
|||
PDF. I've had a look around /sys/class but nothing's jumped out at |
|||
me. |
|||
== Other useful OLPC hints == |
|||
http://www.catmoran.com/olpc |
|||
== Activity Installation fu == |
|||
<pre> |
|||
From: Gary C Martin <gary@garycmartin.com> |
|||
Subject: Re: Playing w/ Activity packs in build 702 |
|||
> Can anyone tell me how to install TamTam from scratch? |
|||
Not sure if this is the official way â but hidden in the update- |
|||
activities.py script from Bert Freudenberg is a very useful link to a |
|||
whole bunch of .xo builds, not all of which are available on the wiki |
|||
activities page (I'm not sure why). You can find .xo bundles for the |
|||
TamTam** activities here: |
|||
http://mock.laptop.org/repos/local.update1/XOS/index.html |
|||
** I believe the original TamTam activity is now considered old, |
|||
unsupported code, and has been split out into individual activities |
|||
called TamTamEdit, TamTamJam, TamTamMini, and TamTamSynthLab. |
|||
Once activities are installed, the new xo_get.py script (which |
|||
includes Bert's update-activities.py code), is very useful for keeping |
|||
all installed activities upgraded to the latest versions available. |
|||
You can download the xo-get.py file from: |
|||
http://wiki.laptop.org/go/Xo-get |
|||
</pre> |