<?xml version="1.0" encoding="utf-8"?>

<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
<title type="text">Journal of Martin Michlmayr</title>
<subtitle type="html"><![CDATA[
Martin Michlmayr's journal
]]></subtitle>
<id>http://www.cyrius.com/journal/index.atom</id>
<link rel="alternate" type="text/html" href="http://www.cyrius.com/journal" />
<link rel="self" type="text/xml" href="http://www.cyrius.com/journal/index.atom" />

<author>
<name>Martin Michlmayr</name>
<uri>http://www.cyrius.com/journal/index.atom</uri>
<email>tbm@cyrius.com</email>
</author>
<rights>Copyright 2003-2006 Martin Michlmayr</rights>
<generator uri="http://pyblosxom.sourceforge.net/" version="1.3.2 2/13/2006">
PyBlosxom http://pyblosxom.sourceforge.net/ 1.3.2 2/13/2006
</generator>

<updated>2010-03-17T17:24:47Z</updated>
<!-- icon?  logo?  -->

<entry>
<title type="html">Using the installer to flash the kernel again</title>
<category term="/debian" />
<id>http://www.cyrius.com/journal/2010/03/17/#installer-flash-kernel</id>
<updated>2010-03-17T17:24:47Z</updated>
<published>2010-03-17T17:24:47Z</published>
<link rel="alternate" type="text/html" href="http://www.cyrius.com/journal/debian/installer-flash-kernel" />
<content type="html">
<p>

Every once in a while someone asks how they can use the Debian installer
to access their system on disk to run commands, for example to write
the kernel and ramdisk to flash again.  This is particularly useful on
headless NAS devices.  So here's how to do it:

</p>

<ol>

<li>Start the Debian installer.</li>

<li>Remove the SSH key from <tt>~/.known_hosts</tt> because the installer
will always generate a new key.</li>

<li>Connect to the installer with SSH: <tt>ssh installer@...</tt></li>

<li>Follow the installer until you reach the partitioner, then choose "go
back".</li>

<li>Open a shell (look for <tt>Execute a shell</tt> towards the end of the
menu).</li>

<li>Run the commands below (the example assumes that <tt>/boot</tt> is
<tt>/dev/sda1</tt> and <tt>/</tt> is <tt>/dev/sda2</tt>.</li>

</ol>

<div class="code">
<pre>
mkdir -p /target
mount /dev/sda2 /target
mount /dev/sda1 /target/boot
mount --bind /dev /target/dev
mount -t proc none /target/proc
mount -t sysfs none /target/sys
chroot /target /bin/sh
# the prompt will change
# make modifications to the system and regenerate the initramfs
update-initramfs -u
exit
# the prompt will change again as you're leaving the chroot
umount /target/sys
umount /target/proc
umount /target/dev
umount /target/boot
umount /target
reboot
</pre>
</div>

<!-- time: 2010-03-17 17:24:47 +0000 -->

</content>
</entry>

<entry>
<title type="html">Debian Installer 6.0 Alpha1 available</title>
<category term="/debian/kirkwood" />
<id>http://www.cyrius.com/journal/2010/02/21/#squeeze-alpha1</id>
<updated>2010-02-21T19:36:14Z</updated>
<published>2010-02-21T19:36:14Z</published>
<link rel="alternate" type="text/html" href="http://www.cyrius.com/journal/debian/kirkwood/squeeze-alpha1" />
<content type="html">
<p>

The Debian installer team today announced the alpha1 version of the
installer for Debian squeeze (6.0).  This release adds a lot of new
features but I just wanted to highlight the ARM related enhancements.  With
this release, Marvell's Kirkwood platform is supported.  Specifically, the
installer supports the following devices: QNAP <a href =
"http://www.cyrius.com/debian/kirkwood/qnap/ts-119/">TS-110 and TS-119</a>,
QNAP <a href = "http://www.cyrius.com/debian/kirkwood/qnap/ts-219/">TS-210,
TS-219 and TS-219P</a>, <a href =
"http://www.cyrius.com/debian/kirkwood/sheevaplug/">SheevaPlug</a> and
OpenRD.  In addition to Kirkwood support, Wouter Verhelst added support for
the Intel Storage System SS4000-E.

</p>

<!-- time: 2010-02-21 19:36:14 +0000 -->
</content>
</entry>

<entry>
<title type="html">Project management lessons from the FreeDOS Project</title>
<category term="/fossbazaar" />
<id>http://www.cyrius.com/journal/2009/11/10/#lessons-from-freedos</id>
<updated>2009-11-10T17:12:18Z</updated>
<published>2009-11-10T17:12:18Z</published>
<link rel="alternate" type="text/html" href="http://www.cyrius.com/journal/fossbazaar/lessons-from-freedos" />
<content type="html">
<p>

A lot of people seem to think that open source is a magic solution to
project management and that open source projects will automatically
attract a large and healthy community of contributors and users who will
improve the software.  This, of course, is not the case.  In fact,
creating a successful open source project is a really major and
difficult effort.  You have to deliver an initial promise that people
find interesting, attract other people, then facilitate and lead the
community, etc.  You just have to look at all the failed projects on
SourceForge that never delivered any code to see that "open source" is
not a guarantee for success.

</p>

<p>

Even though project management is a key element of every open source
project, there are only few resources about this topic.  That's why I
always enjoy reading about the experience from open source project
leaders.  Jim Hall, the founder of the FreeDOS project, recently posted
a series of four articles which I find particularly interesting.

</p>

<p>

Here are links to the articles along with a quick summary:

</p>

<ul>

<li><a href =
"http://scienceblogs.com/collectiveimagination/2009/10/james_hall_on_free_and_open_so.php">Free
and Open Source Software</a>: the first article just describes what free
software and open source are all about.  It also looks at Raymond's
model and compares the cathedral and the bazaar style of
development.</li>

<li><a href =
"http://scienceblogs.com/collectiveimagination/2009/10/james_hall_open_source_softwar.php">Open
source software in the real world</a>: this article summarizes a number
of key lessons learned: every project needs a clear purpose (i.e. you
have to solve an actual problem); initial users of the software should
be recruited as developers; releases are important; and every project
needs an active coordinator or maintainer.</li>

<li><a href =
"http://scienceblogs.com/collectiveimagination/2009/10/cultivating_open_source_softwa.php">Cultivating
Open Source Software</a>: you need a web site; making the source code
availability in an easy way is important; documentation is often hard to
write but is vital; you need a bug tracking system and responding to bug
reports is important to attract good feedback.</li>

<li><a href =
"http://scienceblogs.com/collectiveimagination/2009/11/jim_hall_transitions_in_an_ope.php">Transitions
in an open source software project</a>: finally, when you need to hand
over the project, make sure to communicate openly, arrange for your
replacement and stick around to ensure a successful hand over.</li>

</ul>

<p>

I really like these articles from Jim Hall since they contain a lot of
great insights that apply to other projects, so I suggest you check them
out!

</p>

<p>

(Originally published on <a href = "https://fossbazaar.org/">FOSSBazaar</a>)

</p>

<!-- time: 2009-11-10 17:12:18 +0000 -->

</content>
</entry>

<entry>
<title type="html">Marvell publishes roadmap of its ARM series called Armada</title>
<category term="/debian/kirkwood" />
<id>http://www.cyrius.com/journal/2009/11/07/#marvell-armada-roadmap</id>
<updated>2009-11-07T10:49:27Z</updated>
<published>2009-11-07T10:49:27Z</published>
<link rel="alternate" type="text/html" href="http://www.cyrius.com/journal/debian/kirkwood/marvell-armada-roadmap" />
<content type="html">
<p>

For those who haven't seen it yet, LinuxDevices published an article
recently looking at the <a href =
"http://www.linuxfordevices.com/c/a/News/Marvell-Armada-100-500-600-and-1000/">roadmap
of Marvell's ARM line</a>.  The new line is called Armada and for Debian
the Armada 510 (known as Dove) is of particular interest.  To me, it
essentially looks like a Kirkwood (the current platform) but with ARMv6/v7
(instead of ARMv5), integrated VGA and some other features.  According to
the article, the Armada 510 is aimed at "high-end smartbooks and tablets".

</p>

<p>

I'm happy to see the integration of VGA because I'd like to see more ARM
based smartbooks, tablets and thin clients.  At the same time, I'm worried
that the VGA will be some proprietary chip without proper open source
drivers and I'm surprised that the new chip only offers 1.2 GHz.  After
all, the current Kirkwood chip clocks 1.2 GHz already, so I'd have
expected an increase to 2.0 GHz for the next generation.

</p>

<!-- time: 2009-11-07 10:49:27 +0000 -->

</content>
</entry>

<entry>
<title type="html">New devices from QNAP: TS-110, TS-210 and TS-410</title>
<category term="/debian/kirkwood/qnap" />
<id>http://www.cyrius.com/journal/2009/11/05/#ts-x10</id>
<updated>2009-11-05T21:07:04Z</updated>
<published>2009-11-05T21:07:04Z</published>
<link rel="alternate" type="text/html" href="http://www.cyrius.com/journal/debian/kirkwood/qnap/ts-x10" />
<content type="html">
<p>

When I visited Taiwan last week to talk about Debian at a conference on
smartbooks, I used the opportunity to meet up with the folks from QNAP.  It
was really nice to meet many of my contacts at QNAP in person.  We talked
about their roadmap and existing products and I found out that they had
just released a number of new devices that may be of interest to Debian
users.

</p>

<p>

I really like the hardware from QNAP but one downside of their high quality
is also that the devices are fairly expensive.  Last week they introduced a
number of lower cost alternatives: in addition to the TS-119 and TS-219,
you now have the TS-110 and TS-210.  They feature a 800 MHz CPU (instead of
1.2 GHz on the TS-119/TS-219), 256 MB (instead of 512 MB) and have a
plastic case (as a result of which, the TS-110 now has a fan unlike the
TS-119).  Similarly, in addition to the TS-419 and TS-419U, you now have a
TS-410 and TS-410U.

</p>

<p>

Since the TS-110/TS-210 and TS-119/TS-219 are compatible, the Debian
installer will work out of the box.

</p>

<!-- time: 2009-11-05 21:07:04 +0000 -->

</content>
</entry>

<entry>
<title type="html">New Debian on NSLU2 documentation available</title>
<category term="/debian/nslu2" />
<id>http://www.cyrius.com/journal/2009/11/02/#new-docs</id>
<updated>2009-11-02T22:32:08Z</updated>
<published>2009-11-02T22:32:08Z</published>
<link rel="alternate" type="text/html" href="http://www.cyrius.com/journal/debian/nslu2/new-docs" />
<content type="html">
<p>

I wrote several new guides about Debian on the Linksys NSLU2 this
weekend.  The new guides cover the following topics:

</p>

<ul>

<li>Troubleshooting: common problems and their solutions</li>

<li>Internals about the boot process of Debian on the NSLU2</li>

<li>Modifying a NSLU2 firmware image</li>

<li>Cloning a NSLU2</li>

<li>Migration guide: how to move your Debian installation from your NSLU2
to a SheevaPlug.</li>

</ul>

<p>

You can find this documentation at my <a href =
"http://www.cyrius.com/debian/nslu2/">Debian on NSLU2</a> site.

</p>

<!-- time: 2009-11-02 22:32:08 +0000 -->

</content>
</entry>

<entry>
<title type="html">Debian installer for SheevaPlug available</title>
<category term="/debian/kirkwood/sheevaplug" />
<id>http://www.cyrius.com/journal/2009/10/12/#sheevaplug-installer-available</id>
<updated>2009-10-12T18:55:27Z</updated>
<published>2009-10-12T18:55:27Z</published>
<link rel="alternate" type="text/html" href="http://www.cyrius.com/journal/debian/kirkwood/sheevaplug/sheevaplug-installer-available" />
<content type="html">
<p>

You can now use the Debian installer to install Debian on the Marvell
SheevaPlug.  This routine will install Debian testing (squeeze), which
is currently under development.  The installer itself is also under
development, so there may be problems from time to time but it should
generally work pretty well.  The Debian installer doesn't support
installations to flash, but you can use it to install to a USB stick or
disk as well as to an SD card.  Here are <a href =
"http://www.cyrius.com/debian/kirkwood/sheevaplug/">installation
instructions</a>.

</p>

<!-- time: 2009-10-12 18:55:27 +0100 -->

</content>
</entry>

<entry>
<title type="html">Upgrading SheevaPlug&apos;s U-Boot to version 3.4.19</title>
<category term="/debian/kirkwood/sheevaplug" />
<id>http://www.cyrius.com/journal/2009/10/11/#upgrade-uboot</id>
<updated>2009-10-11T11:25:52Z</updated>
<published>2009-10-11T11:25:52Z</published>
<link rel="alternate" type="text/html" href="http://www.cyrius.com/journal/debian/kirkwood/sheevaplug/upgrade-uboot" />
<content type="html">
<p>

Marvell made a new version of U-Boot for the SheevaPlug available last
month.  This version, 3.4.19, integrates SD card support and improves
support for FAT32 USB partitions (although USB support in general is
still a bit flaky).  This page describes how to install this new
version of U-Boot on your SheevaPlug.

</p>

<p>

First of all, download the <a href =
"http://plugcomputer.org/index.php/us/resources/downloads?func=fileinfo&amp;id=54">SheevaPlug
U-Boot 3.4.19</a>.  Unpack the zip file and copy the file
<tt>u-boot-3.4.19/u-boot-rd88f6281Sheevaplug_400db_nand.bin</tt> to your
TFTP server.  I suggest you call the file <tt>u-boot.bin</tt>.

</p>

<p>

Then start your SheevaPlug and type the following:

</p>

<div class="code">
<pre>
setenv serverip 192.168.1.2 # IP of your TFTP server
setenv ipaddr 192.168.1.200
bubt u-boot.bin
</pre>
</div>

<p>

The upgrade process will ask whether you want to change the environment:

</p>

<div class="code">
<pre>
**Warning**
If U-Boot Endiannes is going to change (LE->BE or BE->LE),
Then Env parameters should be overridden..
Override Env parameters? (y/n) <span class="input">n</span>
</pre>
</div>

<p>

Make sure to answer "n" here.

</p>

<p>

We also need to make a small change to the u-boot configuration because
this version of u-boot no longer accepts the <tt>console</tt> parameter
we have been using.  Thanks to Tom Rinehart for pointing this out.
Instead of <tt>console</tt>, we'll therefore add a new
<tt>bootargs_console</tt> and update <tt>bootcmd</tt> to make use of it:

</p>

<div class="code">
<pre>
setenv bootargs_console console=ttyS0,115200
printenv bootcmd
</pre>
</div>

<p>

You'll see that bootcmd contains <tt>$(console)</tt>.  You have to
set a new <tt>bootcmd</tt> and change the console parameter to
<tt>$(bootargs_console)</tt>.  In my case, I'd type:

</p>

<div class="code">
<pre>
setenv bootcmd 'setenv bootargs $(bootargs_console); run bootcmd_usb; bootm 0x400000 0x0800000; reset'
</pre>
</div>

<p>

Make sure you don't forget the quotes!

</p>

<p>

Finally, save the environment and restart your machine:

</p>

<div class="code">
<pre>
saveenv
reset
</pre>
</div>

<!-- time: 2009-10-11 11:25:52 +0100 -->

</content>
</entry>

<entry>
<title type="html">Debian installer for QNAP TS-119, TS-219 and TS-219P available</title>
<category term="/debian/kirkwood/qnap" />
<id>http://www.cyrius.com/journal/2009/10/10/#ts-219-installer-available</id>
<updated>2009-10-10T23:11:13Z</updated>
<published>2009-10-10T23:11:13Z</published>
<link rel="alternate" type="text/html" href="http://www.cyrius.com/journal/debian/kirkwood/qnap/ts-219-installer-available" />
<content type="html">
<p>

The Debian installer for QNAP TS-119, TS-219 and TS-219P devices (based
on Marvell's 1.2 GHz Kirkwood chip) is now available, together with <a
href = "http://www.cyrius.com/debian/kirkwood/qnap/ts-219/">installation
instructions</a>.  The installer is still under development and it will
install Debian testing, which is also under development.  However, I
think it's working pretty well.  If you try the installer, please send
me feedback.

</p>

<!-- time: 2009-10-10 23:11:13 +0100 -->

</content>
</entry>

<entry>
<title type="html">Fan control on the D-Link DNS-323</title>
<category term="/debian/orion/d-link/dns-323" />
<id>http://www.cyrius.com/journal/2009/06/06/#dns-323-fan-control</id>
<updated>2009-06-06T14:52:14Z</updated>
<published>2009-06-06T14:52:14Z</published>
<link rel="alternate" type="text/html" href="http://www.cyrius.com/journal/debian/orion/d-link/dns-323/dns-323-fan-control" />
<content type="html">
<p>

The kernel in Debian doesn't have support for the fan control chip on
the D-Link DNS-323.  Since some people said that their device runs quite
hot after installing Debian, I've prepared a 2.6.29 based kernel that
includes the fan driver.

</p>

<p>

If you want to install this kernel, edit the file
<tt>/etc/apt/sources.list</tt> and add the following line:

</p>

<div class="code">
<pre>
deb http://people.debian.org/~tbm/orion lenny main
</pre>
</div>

<p>

Now you can install the new kernel:

</p>

<div class="code">
<pre>
apt-get update
apt-get install linux-image-orion5x
</pre>
</div>

<p>

After a reboot, you can control the fan this way:

</p>

<div class="code">
<pre>
echo   0 &gt; /sys/class/hwmon/hwmon?/device/pwm1  # turn it off
echo 255 &gt; /sys/class/hwmon/hwmon?/device/pwm1  # turn it to full speed
</pre>
</div>

<p>

Any values between 0 and 255 will work.

</p>

<p>

According to Anselmo Luginbuhl, you should also be able to use the
<tt>lm-sensors</tt> package to automatically control the fan:

</p>

<p>

"Execute pwmconfig, it will make some tests and generate the fancontrol
config file.  At the end of the procedure it will ask you to "Select fan
output to configure, or other action:", just be sure to pass through
choice "1" or it would not fill in the configuration file, save the
configuration and start the daemon /etc/init.d/fancontrol.

</p>

<p>

Probably the only thing that needs some attention to get an optimal
result is to choose the right parameters for max and min temperature at
which the fan should start or stop to minimize the °C and the noise."

</p>

<p>

Finally, this kernel also includes some performance patches from
Marvell, so you might see some performance increases too.

</p>

<!-- time: 2009-06-06 14:52:14 +0200 -->

</content>
</entry>

<entry>
<title type="html">Corporate participation in open source communities</title>
<category term="/fossbazaar" />
<id>http://www.cyrius.com/journal/2009/06/05/#corporate-community-participation</id>
<updated>2009-06-05T11:10:58Z</updated>
<published>2009-06-05T11:10:58Z</published>
<link rel="alternate" type="text/html" href="http://www.cyrius.com/journal/fossbazaar/corporate-community-participation" />
<content type="html">
<p>

Someone recently asked me a few question about corporate participation
in open source communities and I thought I'd share my thoughts on this
topic here.

</p>

<p>

<em>Are there differences between an open source project done for a
corporation and one done for personal reasons?</em>

</p>

<p>

There are many different ways to run an open source project, led by a
corporation or by someone else.  Some projects that are run by
corporations have few outside contributors.  This is often the case with
projects that require copyright assignment (i.e. contributors have to
assign their copyright to the corporation).  These projects may not gain
all the benefits of a true open source community, such as outside
contributions or high levels of peer review.  However, they may still be
very successful projects and may have high levels of quality.

</p>

<p>

Projects done by a corporation may have better planning and may have
more resources than other projects.  When a corporation, especially a
large one, starts or becomes involves in a project it can also give
credibility to the project and attract a lot of interest to the project.
This means that projects done by corporations may have a bigger impact
and might also be more visible in terms of publicity.

</p>

<p>

<em>How do corporations successfully utilize an open source
community?</em>

</p>

<p>

Corporations can benefit from an open source community in many ways.
For example, they can often find people who will review their code or
make code contributions.  If people become excited about what the
corporation does, they might also spread the word and create viral
marketing for the corporation.  Establishing a community around one's
project is often also a good way to identify people to hire since you
already have experience working with them and know their capabilities.

</p>

<p>

<em>How do open source communities successfully utilize their corporate
relationships?</em>

</p>

<p>

Corporations can make several unique contributions.  For example, large
corporations can use their name to attract attention to a project and
give it credibility.  Furthermore, corporations have some capabilities
that personal contributors often don't have access.  They may have
special testing equipment (such as servers with thousands of CPUs or
hard drives) or access to a testing lab where a professional usability
test can be done.  Finally, corporations can sponsor developer
conferences, which are typically very effective means for the community
to come together and work on activities together.

</p>

<p>

It is important for projects to remember that corporations are not
charities and that they will invest in an open source project for a
reason.  Therefore, they have to ensure that the corporation will get
tangible outcomes from their involvement or sponsorship, otherwise they
may not stay involved in the long run.

</p>

<p>

<em>What are the risks for a corporation when working with an open
source community?</em>

</p>

<p>

One risk is that the code (or other form of contribution) is not
accepted.  However, this is a risk any contributor to a project faces.
Before making any sort of contribution, it is therefore important to
become familiar with the project and its culture.  Every project has
their own "do's" and "don'ts" that have to be followed.

</p>

<p>

Another risk is that a corporation will invest in a community project
that later on is abandoned by the community.  However, in this case, the
corporation could take the lead and continue to maintain the project.

</p>

<p>

<em>What are the risks for an open source community when working with a
corporation?</em>

</p>

<p>

One potential risk is that the corporation will assert too much control
over the project.  It's important for projects to ensure that the
community as a whole has influence over the direction of a project
rather than one particular player.

</p>

<p>

<em>Are certain certifications needed in order for someone
to participate in open source projects for a corporation?</em>

</p>

<p>

Certifications are not needed to get involved in or start a project.
However, it is important to become familiar with the open source
community and the project one wants to contribute to.  A good first step
is to read the book Producing Open Source Software by Karl Fogel which
is <a href = "http://producingoss.com/">available online</a>.  As a next
step, the community in which someone wants to get involved in should be
studied, for example by reading the mailing list archives.  This will
help to become familiar with the culture of a project as well as the
mechanisms to contribute to the project.

</p>

<p>

<em>How do open source communities communicate and collaborate with
corporations?</em>

</p>

<p>

In the best case, employees from corporations would interact in the
project like any other contributor.  That is, they should use the
existing communication channels, such as mailing lists, IRC or developer
gatherings.  Many companies are good at working "with the community" but
the ideal scenario is for a company to be part of the community and to
work "in the community", just like other contributors.  This is the most
effective way for them to make changes to the code and project.

</p>

<p>

Of course, not every corporation will get involved in a project
directly.  That's why it makes sense for projects to collaborate with
corporations in other ways.  For example, projects can talk directly to
companies to get samples of their hardware in order to add support for
them in their software.  Projects can also work directly with
corporations to find out how their project can better meet the needs of
enterprise users.

</p>

<!-- time: 2009-06-05 11:10:58 +0200 -->

</content>
</entry>

<entry>
<title type="html">Initial thoughts on the new QNAP TS-219P</title>
<category term="/debian/kirkwood/qnap" />
<id>http://www.cyrius.com/journal/2009/05/31/#ts-219p-initial-thoughts</id>
<updated>2009-05-31T22:22:22Z</updated>
<published>2009-05-31T22:22:22Z</published>
<link rel="alternate" type="text/html" href="http://www.cyrius.com/journal/debian/kirkwood/qnap/ts-219p-initial-thoughts" />
<content type="html">
<p>

<img src="http://www.cyrius.com/debian/kirkwood/qnap/ts-219/images/r_ts219p.jpg"
 alt="QNAP TS-219P" class="right" width="148" height="188" />

QNAP has announced a new device earlier this month, the QNAP TS-219P.  The
specs are very similar to the TS-219 (1.2 GHz Kirkwood CPU, 512 MB RAM and
16 MB flash) but the device is smaller and has some other advantages.

</p>

<p>

What I like about the new TS-219P:

</p>

<ul>
<li>The device is more compact and looks really nice.</li>

<li>The fan is less noisy than the one in the TS-209 and TS-219.</li>

<li>There are two eSATA ports.</li>

</ul>

<p>

What I don't like so much:

</p>

<ul>

<li>The device only has one Ethernet.  I'd really like to see two Ethernet
ports.</li>

<li>The serial connector cannot easily be accessed through the SATA slot,
something that was possible with the TS-209.</li>

</ul>

<p>

Since the TS-219 and TS-219P are quite similar, Debian and the installer
will work without any problems.  I updated <a href =
"http://www.cyrius.com/debian/kirkwood/qnap/ts-219/">my QNAP page to
document the QNAP TS-219P</a>, including some pictures of the new device.

</p>

<!-- time: 2009-05-31 22:22:22 +0200 -->

</content>
</entry>

<entry>
<title type="html">SheevaPlug lenny tar ball and SD cards</title>
<category term="/debian/kirkwood/sheevaplug" />
<id>http://www.cyrius.com/journal/2009/05/19/#tar-ball-sd-card</id>
<updated>2009-05-19T22:15:08Z</updated>
<published>2009-05-19T22:15:08Z</published>
<link rel="alternate" type="text/html" href="http://www.cyrius.com/journal/debian/kirkwood/sheevaplug/tar-ball-sd-card" />
<content type="html">
<p>

I updated my <a href =
"http://www.cyrius.com/debian/kirkwood/sheevaplug/">SheevaPlug installation
instructions</a> today to document how to boot from an SD card.  The u-boot
boot loader shipped with the SheevaPlug doesn't have SD/MMC card support,
but <a href = "http://openplug.org/plugforum/">PlugComputer forum</a> user
<tt>kwonsk</tt> created one that does (and which works pretty well, except
for not working with some SD cards).

</p>

<!-- time: 2009-05-19 22:15:08 +0200 -->

</content>
</entry>

<entry>
<title type="html">First successful installation on QNAP TS-219</title>
<category term="/debian/kirkwood/qnap" />
<id>http://www.cyrius.com/journal/2009/05/19/#ts-219-successful-install</id>
<updated>2009-05-19T22:08:26Z</updated>
<published>2009-05-19T22:08:26Z</published>
<link rel="alternate" type="text/html" href="http://www.cyrius.com/journal/debian/kirkwood/qnap/ts-219-successful-install" />
<content type="html">
<p>

I performed the first successful installation of Debian on the QNAP
TS-219 using the Debian installer today.   Everything is in place now
but the Linux 2.6.29 kernel has to move to testing so installations will
work.

</p>

<!-- time: 2009-05-19 22:08:26 +0200 -->

</content>
</entry>

<entry>
<title type="html">Automatic power on QNAP Turbo Station devices</title>
<category term="/debian/orion/qnap" />
<id>http://www.cyrius.com/journal/2009/05/16/#automatic-power-on</id>
<updated>2009-05-16T11:01:53Z</updated>
<published>2009-05-16T11:01:53Z</published>
<link rel="alternate" type="text/html" href="http://www.cyrius.com/journal/debian/orion/qnap/automatic-power-on" />
<content type="html">
<p>

All ARM based QNAP machines can turn on automatically when power is
applied if the device was not powered down correctly.  This is helpful
when your power goes down.  Follow the instructions below if you want to
turn automatic power on using Debian on a QNAP TS-109, TS-119, TS-209,
TS-219, TS-409 or TS-409U.

</p>

<p>

Edit the file <tt>/etc/apt/sources.list</tt> and add the following line:

</p>

<div class="code">
<pre>
deb http://people.debian.org/~tbm/orion lenny main
</pre>
</div>

<p>

Now install a new version of qcontrol:

</p>

<div class="code">
<pre>
apt-get update
apt-get install qcontrol
</pre>
</div>

<p>

Finally, turn the automatic power feature on:

</p>

<div class="code">
<pre>
qcontrol -d &amp;
qcontrol autopower on
kill %1
rm /var/run/qcontrol.sock
</pre>
</div>

<!-- time: 2009-05-16 11:01:53 +0200 -->

</content>
</entry>

<entry>
<title type="html">Update on QNAP TS-119/TS-219 kernel support</title>
<category term="/debian/kirkwood/qnap" />
<id>http://www.cyrius.com/journal/2009/05/13/#ts-219-kernel-support2</id>
<updated>2009-05-13T19:44:10Z</updated>
<published>2009-05-13T19:44:10Z</published>
<link rel="alternate" type="text/html" href="http://www.cyrius.com/journal/debian/kirkwood/qnap/ts-219-kernel-support2" />
<content type="html">
<p>

I mentioned a few weeks ago that initial kernel support for the QNAP
TS-119 and TS-219 Turbo NAS got accepted for 2.6.30 but that there were
<a href =
"http://www.cyrius.com/journal/debian/kirkwood/qnap/ts-219-kernel-support">some
issues left</a>.  Here's an update:

</p>

<ul>

<li>SATA: Kirkwood uses a different SATA PHY and the Orion settings
weren't quite right, leading to the timeouts I saw.  As it turns out,
Saeed Bishara from Marvell had a patch for this already and it will be
in 2.6.30-rc6.</li>

<li>Flash: writing to flash is now possible thanks to a patch from Peter
Horton that has been merged into 2.6.30-rc5.</li>

<li>Parsing the MAC address: Thomas Reitmayr created a patch to parse
the MAC address from flash but the kernel people thought this should be
done in userspace.  I haven't looked into this yet... maybe the best
solution is to document that the MAC address will change.</li>

<li>SATA lights: Thomas Reitmayr created a patch to fix this issue.</li>

</ul>

<p>

The SATA and flash fixes are already in our 2.6.29 kernel.

</p>

<!-- time: 2009-05-13 19:44:10 +0200 -->

</content>
</entry>

<entry>
<title type="html">Debian 5.0 (lenny) tar ball for QNAP TS-119 and TS-219</title>
<category term="/debian/kirkwood/qnap" />
<id>http://www.cyrius.com/journal/2009/05/07/#debian-lenny-tar-ball</id>
<updated>2009-05-07T22:22:22Z</updated>
<published>2009-05-07T22:22:22Z</published>
<link rel="alternate" type="text/html" href="http://www.cyrius.com/journal/debian/kirkwood/qnap/debian-lenny-tar-ball" />
<content type="html">
<p>

Since the installer isn't quite ready yet, I created a tar ball containing
Debian lenny for the QNAP TS-119 and TS-219 along with some <a href =
"http://www.cyrius.com/debian/kirkwood/qnap/ts-219/unpack.html">installation
instructions</a>.  The QNAP firmware is used to partition the hard drive
and unpack the tar ball, so Debian can be installed without having to put
the hard drive into another machine.

</p>

<!-- time: 2009-05-07 22:22:22 +0200 -->

</content>
</entry>

<entry>
<title type="html">Debian 5.0 (lenny) tar ball for the SheevaPlug</title>
<category term="/debian/kirkwood/sheevaplug" />
<id>http://www.cyrius.com/journal/2009/05/04/#debian-lenny-tar-ball</id>
<updated>2009-05-04T20:17:43Z</updated>
<published>2009-05-04T20:17:43Z</published>
<link rel="alternate" type="text/html" href="http://www.cyrius.com/journal/debian/kirkwood/sheevaplug/debian-lenny-tar-ball" />
<content type="html">
<p>

It took me a while because of travel and other projects, but I finally
released a tar ball containing Debian lenny for the SheevaPlug along with
some <a href =
"http://www.cyrius.com/debian/kirkwood/sheevaplug/unpack.html">installation
instructions</a>.  It should be really easy to install Debian this way, but
I'll also make sure that SheevaPlug support will be in the Debian installer
for the next release of Debian.  For now, check out the tar ball I
prepared!

</p>

<!-- time: 2009-05-04 20:17:43 +0200 -->

</content>
</entry>

<entry>
<title type="html">Adventures with the Qstarz BT-Q1000X GPS logger and receiver</title>
<category term="/gps" />
<id>http://www.cyrius.com/journal/2009/05/01/#adventures-bt-q1000x</id>
<updated>2009-05-01T19:21:22Z</updated>
<published>2009-05-01T19:21:22Z</published>
<link rel="alternate" type="text/html" href="http://www.cyrius.com/journal/gps/adventures-bt-q1000x" />
<content type="html">
<p>

<img src="http://www.cyrius.com/images/bt-q1000x.jpg"
 alt="Qstarz BT-Q1000X GPS in my hand" class="right" width="250" height="230" />

Spring has arrived in Europe and I'm looking forward to spending more
time outdoors.  While I was pondering some plans, I thought it would be
nice to have a GPS.  I've never used a GPS before but it seems it will
allow me to combine outdoors activities such as walking and hiking with
geek things.  In particular, I'm interested in tracking where I'm going
(what route, what distance, what speed, etc), geotagging photos and
possibly contributing to OpenStreetMap.  Since last week, I have a
Qstarz BT-Q1000X (Travel Recorder X), a GPS logger and receiver, and
I've been playing around with it a bit.  This device uses the new MTK II
chip, which gives good accuracy and long battery time.

</p>

<p>

I've created a new <tt>gps</tt> category in which I'll share my
experience using a GPS in general and specifically the Qstarz BT-Q1000X.
I've also created a <a href =
"http://www.cyrius.com/debian/gps/bt-q1000x/">Qstarz BT-Q1000X and
Debian</a> page to describe how to use this GPS device on Linux and I'll
add more information to the page as I try out different applications.

</p>

<!-- time: 2009-05-01 19:21:22 +0200 -->

</content>
</entry>

<entry>
<title type="html">OSI signs an MOU with the Korea Software Copyright Committee</title>
<category term="/fossbazaar" />
<id>http://www.cyrius.com/journal/2009/04/22/#mou-osi-socop</id>
<updated>2009-04-22T15:12:51Z</updated>
<published>2009-04-22T15:12:51Z</published>
<link rel="alternate" type="text/html" href="http://www.cyrius.com/journal/fossbazaar/mou-osi-socop" />
<content type="html">
<p>

I visited Seoul last week to represent the Open Source Initiative (OSI) at
an open source conference and to sign a Memorandum of Understanding (MOU)
with the <a href = "http://www.socop.or.kr/english/main/main.jsp">Korea
Software Copyright Committee</a> (SOCOP).  SOCOP organized a conference
with the title "Free Open Source Software License Insight Conference", and
the international speakers included Brett Smith of the FSF, Brendan Scott
of Open Source Law, Michael Coté of RedMonk and myself.  From the questions
we received, it seems that there is a lot of interest in legal questions
related to open source.  There were a number of folks from hardware
companies that asked specific questions what they could do and couldn't do
(e.g. related to including sources for GPL code and properly giving credit
for BSD code).

</p>

<p>

I think the conference was a great success.  The talks were of high
value and we got good questions.  The audience was quite mixed, ranging
from managers to developers.  Even though they had simultaneous
translation of the talks, the majority of the people listened in
English... this gives me hope that some of these folks will end up
becoming involved in the international open source community.

</p>

<p>

<img src="http://www.cyrius.com/images/mou-socop-osi.jpg"
 alt="Mr Koo and Dr Michlmayr signing MOU" class="right" width="400" height="266" />

SOCOP is working on a number of activities related to open source,
including:

</p>

<ul>
<li>An information portal called OLIS.</li>
<li>The translation of all OSI approved licenses to Korean.</li>
<li>The verification of open source code to identify which code uses which license.</li>
<li>More promotional activities, including workshops and conferences.</li>
</ul>

<p>

The day after the conference, I went to the SOCOP office to sign the MOU
between SOCOP and OSI with Mr Yung Bo Koo, the chairman of SOCOP.  The
MOU says that we'll share knowledge and expertise, help with promotional
activities and support each other's activities in other ways.  I was
delighted to sign the MOU between SOCOP and OSI, and I look forward to a
fruitful cooperation between our organizations in the future.  It's
great to see so much interest and so many activities around open source
in the Republic of Korea.

</p>

<!-- time: 2009-04-22 15:12:51 +0200 -->

</content>
</entry>
</feed>
