Openmoko - User contributions [en]

Qi

2008-12-10T06:11:53Z

Laen:

Qi is a boot manager. It is designed to replace [[Uboot|uBoot]]. But Qi will be simpler and faster.

==Concept==
Qi's concept is it leaves everything possible to Linux, that includes even the video init. Therefore Qi does NOT provide a boot menu. The usual NOR uBoot menu you use to flash your Neo (Aux first, power second, wait for menu) of course works fine, but if you try the usual procedure to fire up NAND uBoot (Power first, aux second, wait for menu) you get no response. (not even the 'backlighted black screen')

==Partitions==
Qi will boot from any kernel named uImage-GTA0[123...].bin in the /boot folder in the root of an ext2 or ext3
partition on the uSD card.
* Qi looks for a kernel in the first, second and third partition, silently ignoring FAT partitions.
* Qi expects the / (root) filesystem to be on the same partition as /boot.
* If both uImage-GTA02 and uImage-GTA03 files are present, Qi loads the right one for the machine.

Failing to find a kernel in the SD card, Qi will boot from the kernel in NAND (if the kernel works of course, see below). Failing to find a valid kernel, Qi perform a memory test. It means that one can either move kernels out of the way to get the memory test, or make an SD Card just with normal Qi on it and no kernels to get a memory test.
* Up to Nov. 28th, Qi would blink the blue Power LED a fraction of a second every 10 secs or so to say ''nothing valid to boot''.

== Download and installation ==
The daily download is a ''qi-s3cXXXX-andy_somenumber.udfu'' file at http://people.openmoko.org/andy/ .
(look at your dmesg output for the CPU to pick the right s3c* version.)

The installation should be flashing like;
# dfu-util -a u-boot -R -D qi-s3c6410-andy_8589b40295653557.udfu

===Source code===
git://git.openmoko.org/git/qi.git , http://git.openmoko.org/?p=qi.git;a=summary .
One can also just use strings(1) on the .udfu file to get an idea of where Qi currently looks for files.

==Enabling console messages==
[http://lists.openmoko.org/pipermail/openmoko-kernel/2008-November/006812.html]
If it's SD Card boot, just create a text file, e.g., for a [[GTA02]] use
/boot/append-GTA02
on the rootfs in question, put in there
console=tty0 loglevel=8
and you'll see the messages on boot. If it's NAND right now you need to edit the default commandline in Qi for gta02.

==SD Initialisation==
If you don't specify loglevel=8 in append-GTAXX, and booting fails with a "VFS: Cannot open root device "mmcblk0p1" or unknown-block(2,0)", the SD card needs a little bit more time to initialise.

Put a "rootdelay=" in append-GTAXX like so:
rootdelay=1

== Testing speed improvements ==

Stopwatch results on Qi (error is approx ±1/2 second):

Booting SHR image with uBoot:
* 0:00 power button held down
* 0:07 splash screen appears
* 0:15 drops to console showing kernel messages scrolling by for ~1 minute
* 1:18 Openmoko 'please wait' splash
* 1:31 desktop animated splash
* 2:38 finished booting

Booting identical setup with Qi flashed over uBoot:
* 0:00 power button held down
* 0:06 backlit black
* 0:13 please wait booting... (only this text on console for next 38 seconds)
* 0:51 Angstrom console message (at the end of kernel output with uBoot, but ONLY text display to appear throughout this stage with Qi)
* 0:54 Openmoko 'please wait' splash
* 1:05 desktop animated splash
* 1:54 finished booting

So for this particular configuration, it reduced time-to-desktop by about 28%, about 44 seconds. Surprisingly, the later segments of booting (desktop) were also noticeably faster than with uBoot - One would have expected just the fist stages up until init (kernel finished establishing itself) to be faster.

== Bugs ==

* Qi won't boot the 'first try' after power restored - the tester didn't count that first 10 seconds for Qi to be fair to its booting speed, not penalize it for what appears to be a bug that bears no relation to actual boot speed).
* The current (Oct. 12, 2008) 2.6.27 kernel does not boot from the build-in flash NAND. It only works from the uSD boot on ext3. If one tries to boot it from the flash, then AUX red LED blinks ~4/sec. This means kernel panic... It's panicking because it has no rootfs because it can't mount the jffs2 because of the CRC errors because there is a bug that the mtd are not done properly.
* Qi often doesn't want to resume after suspend.
* Qi is able to load kernels larger than 2MB correctly, uBoot has a bug.

== LED codes summary ==

* One Blue shine every ~10 second: did not found any valid kernel to boot
* About four RED shines per second: kernel panic.

[[Category:System Developers]]

Qi

2008-12-10T06:05:33Z

Laen: /* Bugs */

Qi is a boot manager. It is designed to replace [[Uboot|uBoot]]. But Qi will be simpler and faster.

==Concept==
Qi's concept is it leaves everything possible to Linux, that includes even the video init. Therefore Qi does NOT provide a boot menu. The usual NOR uBoot menu you use to flash your Neo (Aux first, power second, wait for menu) of course works fine, but if you try the usual procedure to fire up NAND uBoot (Power first, aux second, wait for menu) you get no response. (not even the 'backlighted black screen')

==Partitions==
Qi will boot from any kernel named uImage-GTA0[123...].bin in the /boot folder in the root of an ext2 or ext3
partition on the uSD card.
* Qi looks for a kernel in the first, second and third partition, silently ignoring FAT partitions.
* Qi expects the / (root) filesystem to be on the same partition as /boot.
* If both uImage-GTA02 and uImage-GTA03 files are present, Qi loads the right one for the machine.

Failing to find a kernel in the SD card, Qi will boot from the kernel in NAND (if the kernel works of course, see below). Failing to find a valid kernel, Qi perform a memory test. It means that one can either move kernels out of the way to get the memory test, or make an SD Card just with normal Qi on it and no kernels to get a memory test.
* Up to Nov. 28th, Qi would blink the blue Power LED a fraction of a second every 10 secs or so to say ''nothing valid to boot''.

== Download and installation ==
The daily download is a ''qi-s3cXXXX-andy_somenumber.udfu'' file at http://people.openmoko.org/andy/ .
(look at your dmesg output for the CPU to pick the right s3c* version.)

The installation should be flashing like;
# dfu-util -a u-boot -R -D qi-s3c6410-andy_8589b40295653557.udfu

===Source code===
git://git.openmoko.org/git/qi.git , http://git.openmoko.org/?p=qi.git;a=summary .
One can also just use strings(1) on the .udfu file to get an idea of where Qi currently looks for files.

==Enabling console messages==
[http://lists.openmoko.org/pipermail/openmoko-kernel/2008-November/006812.html]
If it's SD Card boot, just create a text file, e.g., for a [[GTA02]] use
/boot/append-GTA02
on the rootfs in question, put in there
console=tty0 loglevel=8
and you'll see the messages on boot. If it's NAND right now you need to edit the default commandline in Qi for gta02.

== Testing speed improvements ==

Stopwatch results on Qi (error is approx ±1/2 second):

Booting SHR image with uBoot:
* 0:00 power button held down
* 0:07 splash screen appears
* 0:15 drops to console showing kernel messages scrolling by for ~1 minute
* 1:18 Openmoko 'please wait' splash
* 1:31 desktop animated splash
* 2:38 finished booting

Booting identical setup with Qi flashed over uBoot:
* 0:00 power button held down
* 0:06 backlit black
* 0:13 please wait booting... (only this text on console for next 38 seconds)
* 0:51 Angstrom console message (at the end of kernel output with uBoot, but ONLY text display to appear throughout this stage with Qi)
* 0:54 Openmoko 'please wait' splash
* 1:05 desktop animated splash
* 1:54 finished booting

So for this particular configuration, it reduced time-to-desktop by about 28%, about 44 seconds. Surprisingly, the later segments of booting (desktop) were also noticeably faster than with uBoot - One would have expected just the fist stages up until init (kernel finished establishing itself) to be faster.

== Bugs ==

* Qi won't boot the 'first try' after power restored - the tester didn't count that first 10 seconds for Qi to be fair to its booting speed, not penalize it for what appears to be a bug that bears no relation to actual boot speed).
* The current (Oct. 12, 2008) 2.6.27 kernel does not boot from the build-in flash NAND. It only works from the uSD boot on ext3. If one tries to boot it from the flash, then AUX red LED blinks ~4/sec. This means kernel panic... It's panicking because it has no rootfs because it can't mount the jffs2 because of the CRC errors because there is a bug that the mtd are not done properly.
* Qi often doesn't want to resume after suspend.
* Qi is able to load kernels larger than 2MB correctly, uBoot has a bug.

== LED codes summary ==

* One Blue shine every ~10 second: did not found any valid kernel to boot
* About four RED shines per second: kernel panic.

[[Category:System Developers]]

Talk:Qi

2008-12-10T06:03:51Z

Laen: /* Qi Kernel */

Qi

2008-12-09T19:50:22Z

Laen: /* Bugs */

Qi is a boot manager. It is designed to replace [[Uboot|uBoot]]. But Qi will be simpler and faster.

==Concept==
Qi's concept is it leaves everything possible to Linux, that includes even the video init. Therefore Qi does NOT provide a boot menu. The usual NOR uBoot menu you use to flash your Neo (Aux first, power second, wait for menu) of course works fine, but if you try the usual procedure to fire up NAND uBoot (Power first, aux second, wait for menu) you get no response. (not even the 'backlighted black screen')

==Partitions==
Qi will boot from any kernel named uImage-GTA0[123...].bin in the /boot folder in the root of an ext2 or ext3
partition on the uSD card.
* Qi looks for a kernel in the first, second and third partition, silently ignoring FAT partitions.
* Qi expects the / (root) filesystem to be on the same partition as /boot.
* If both uImage-GTA02 and uImage-GTA03 files are present, Qi loads the right one for the machine.

Failing to find a kernel in the SD card, Qi will boot from the kernel in NAND (if the kernel works of course, see below). Failing to find a valid kernel, Qi perform a memory test. It means that one can either move kernels out of the way to get the memory test, or make an SD Card just with normal Qi on it and no kernels to get a memory test.
* Up to Nov. 28th, Qi would blink the blue Power LED a fraction of a second every 10 secs or so to say ''nothing valid to boot''.

== Download and installation ==
The daily download is a ''qi-s3cXXXX-andy_somenumber.udfu'' file at http://people.openmoko.org/andy/ .
(look at your dmesg output for the CPU to pick the right s3c* version.)

The installation should be flashing like;
# dfu-util -a u-boot -R -D qi-s3c6410-andy_8589b40295653557.udfu

===Source code===
git://git.openmoko.org/git/qi.git , http://git.openmoko.org/?p=qi.git;a=summary .
One can also just use strings(1) on the .udfu file to get an idea of where Qi currently looks for files.

==Enabling console messages==
[http://lists.openmoko.org/pipermail/openmoko-kernel/2008-November/006812.html]
If it's SD Card boot, just create a text file, e.g., for a [[GTA02]] use
/boot/append-GTA02
on the rootfs in question, put in there
console=tty0 loglevel=8
and you'll see the messages on boot. If it's NAND right now you need to edit the default commandline in Qi for gta02.

== Testing speed improvements ==

Stopwatch results on Qi (error is approx ±1/2 second):

Booting SHR image with uBoot:
* 0:00 power button held down
* 0:07 splash screen appears
* 0:15 drops to console showing kernel messages scrolling by for ~1 minute
* 1:18 Openmoko 'please wait' splash
* 1:31 desktop animated splash
* 2:38 finished booting

Booting identical setup with Qi flashed over uBoot:
* 0:00 power button held down
* 0:06 backlit black
* 0:13 please wait booting... (only this text on console for next 38 seconds)
* 0:51 Angstrom console message (at the end of kernel output with uBoot, but ONLY text display to appear throughout this stage with Qi)
* 0:54 Openmoko 'please wait' splash
* 1:05 desktop animated splash
* 1:54 finished booting

So for this particular configuration, it reduced time-to-desktop by about 28%, about 44 seconds. Surprisingly, the later segments of booting (desktop) were also noticeably faster than with uBoot - One would have expected just the fist stages up until init (kernel finished establishing itself) to be faster.

== Bugs ==

* Qi won't boot the 'first try' after power restored - the tester didn't count that first 10 seconds for Qi to be fair to its booting speed, not penalize it for what appears to be a bug that bears no relation to actual boot speed).
* The current (Oct. 12, 2008) 2.6.27 kernel does not boot from the build-in flash NAND. It only works from the uSD boot on ext3. If one tries to boot it from the flash, then AUX red LED blinks ~4/sec. This means kernel panic... It's panicking because it has no rootfs because it can't mount the jffs2 because of the CRC errors because there is a bug that the mtd are not done properly.
* Qi often doesn't want to resume after suspend.
* Qi is able to load kernels larger than 2MB correctly, uBoot has a bug.
* Without "console=tty0 loglevel=8" in append-GTA02, and especially the loglevel variable, Qi fails to boot the SD, claiming it has an unknown root device (2,0).

== LED codes summary ==

* One Blue shine every ~10 second: did not found any valid kernel to boot
* About four RED shines per second: kernel panic.

[[Category:System Developers]]

Talk:Qi

2008-12-09T01:52:49Z

Laen: /* Qi Kernel */

will it boot jffs2 on flash ?
--kd8ikt

== dmesg output ==

With ''`uname -a`'' = ''"Linux om-gta02 2.6.24 #1 PREEMPT Tue Dec 2 15:02:59 CST 2008 armv4tl unknown"'', dmesg outputs '''s3c2440''' on GTA02 Revision: 0360.
'''qi-s3c2442-master''' works fine on it.

== Qi Kernel ==

The page isn't telling anything about the Qi kernel (uImage-moredrivers-GTA02_andy-tracking_49cff03d0e867b06.bin). Is that a requirement, good idea, or not nessecairy at all?
--[[User:Laen|Laen]] 01:51, 9 December 2008 (UTC)

Talk:Qi

2008-12-09T01:51:45Z

Laen:

will it boot jffs2 on flash ?
--kd8ikt

== dmesg output ==

With ''`uname -a`'' = ''"Linux om-gta02 2.6.24 #1 PREEMPT Tue Dec 2 15:02:59 CST 2008 armv4tl unknown"'', dmesg outputs '''s3c2440''' on GTA02 Revision: 0360.
'''qi-s3c2442-master''' works fine on it.

== Qi Kernel ==

The page isn't telling anything about the Qi kernel. Is that a requirement, good idea, or not nessecairy at all?
--[[User:Laen|Laen]] 01:51, 9 December 2008 (UTC)

Openmoko Local Groups: Netherlands

2008-11-13T21:59:10Z

Laen: /* Possible Participants */

=== Possible Participants ===
{|border=1
!Name
!Skills
!Level of Interest
!Ordered version
!Location
!Other
|-
|[[User:CathodioN|Geert Schuring]]
|Java EE, XML, UML
|Would like to develop Server components
|
|Ede, Gelderland
|willing to organize stuff i.e. meeting location/whatever.
|-
|[[User:Kero|Kero]]
|Ruby
|dbus and pim applications
|Base GTA01BV4
|Eindhoven
|
|-
|[[User:Ericsmith|Eric Smith]]
|Perl, Linux, VoIP
|
|
|Amsterdam
|Share Ideas, VoIP, GPS, SyncML
|-
|[[User:das_nl|Daniel Peptu]]
| C/C++, Java, .Net, Python
|
|Adv. kit GTA01BV4
|Den Haag
|
|-
|[[User:Boudewijn|Boudewijn]]
|general
|Looking for some participants in a group order
|
|Zwolle
|
|-
|[[User:tHe_IkkE|Walter Goossens]]
|(ARM)Kernel programming, OpenEmbedded, C/C++, Java, VHDL
|Would like to contribute to the kernel and other low-level stuff
|Adv. kit GTA01BV4
|Tilburg
|
|-
|[[User:Noud|Noud de Brouwer]]
|software development
|NetBSD on-top the Neo 1973
|qemu
|Goirle
|
|-
|[[User:Marnix.klooster|Marnix Klooster]]
|C/C++, Java, Python, Perl
|
|Neo FreeRunner
|Veenendaal
|
|-
|[[User:ChristW|Christ van Willegen]]
|C/C++
|OpenStreetMap stuff
|Neo FreeRunner
|Eindhoven
|Looking for group-order participants
|-
|[[User:KenSentMe|Jeroen van de Nieuwenhof]]
|Journalist
|Looking for group-order participants
|Neo FreeRunner
|Griendtsveen (LB)
|Interested in gps opportunities
|-
|[[User:Nicolas|Nico Veenkamp]]
|Projectmanagement
|Looking for group-order participants
|Neo FreeRunner
|Nijkerk (GLD)
|Interested in all kinds of usage for the freerunner

|-
|[[User:Charlesh65|Charles Hurenkamp]]
|ICT Consultancy
|Looking for group-order participants
|Neo FreeRunner
|Apeldoorn (GLD)
|Just interested ...
|-
|[[User:akrabbe|Albert Krabbe]]
|I&A Adviseur
|Looking for group-order participants
|Neo FreeRunner
|Haren (GN)
|Just interested ...

|-
|[[User:trickie|Nick Loeve]]
|Developer
|Linux kernel, bootloader, OpenEmbedded, C
|Neo FreeRunner
|Amsterdam
|Willing to help organise a meetup

|-
|[[User:Madjo|Marcel de Jong]]
|Software test engineer
|Testing applications, Open Streetmap
|Neo FreeRunner
|Bergen op Zoom
|
|-
|[[User:rutgerbazen|Rutger Bazen]]
|General
|Aiming to improve skill/knowledge.
|Neo FreeRunner
|Bodegraven
|

|-
|[[User:Laen|Marvin Vek]]
|Unix Consultant
|Planning to get Gentoo running on the FreeRunner
|Neo FreeRunner
|Heerlen

|
|}

[[Category:Openmoko Local Groups]]

User:Laen

2008-11-13T21:50:01Z

Laen: /* Hardware */

= Status =

== Hardware ==

* Openmoko Inc. GTA02 (S/N: 8A8906526) (P/N: 56-21175-00) (Date Code: 20080935) (FCC ID: EUNGTA02E)
* Shipped Transcend MicroSD 512MB (MM4GR512UACY-PA | 82710000 745)
* Shipped Pouch
* Shipped FIC GTA02 Standard Battery Pack (1200mAh Li-ion 3.7V) x 2
* Donated Nokia BL-5C Battery (1020mAh Li-ion 3.7V)
* Sandisk Mobile Ultra MicroSDHC 8GB Class 6 w/ reader (SDSDQY-81920E11M)

== Currently installed ==
* NAND: Qtextended
* MicroSD: Debian
* MicroSDHC: Unused

= Activity =

== Topics ==
* http://wiki.openmoko.org/wiki/Talk:Qi

User:Laen

2008-11-13T21:41:11Z

Laen:

= Status =

== Hardware ==

* Openmoko Inc. GTA02 (S/N: 8A8906526) (P/N: 56-21175-00) (Date Code: 20080935) (FCC ID: EUNGTA02E)
* Shipped Transcend MicroSD 512MB (MM4GR512UACY-PA | 82710000 745)
* Shipped Pouch
* Shipped FIC GTA02 Standard Battery Pack (1200mAh Li-ion 3.7V) x 2
* Donated Nokia BL-5C Battery (1020 mAh 3.7V)
* Sandisk Mobile Ultra MicroSDHC 8GB Class 6 w/ reader (SDSDQY-81920E11M)

== Currently installed ==
* NAND: Qtextended
* MicroSD: Debian
* MicroSDHC: Unused

= Activity =

== Topics ==
* http://wiki.openmoko.org/wiki/Talk:Qi

User:Laen

2008-11-13T21:39:01Z

Laen:

Hardware:
* Openmoko Inc. GTA02 (S/N: 8A8906526) (P/N: 56-21175-00) (Date Code: 20080935) (FCC ID: EUNGTA02E)
* Shipped Transcend MicroSD 512MB (MM4GR512UACY-PA | 82710000 745)
* Shipped Pouch
* Shipped FIC GTA02 Standard Battery Pack (1200mAh Li-ion 3.7V) x 2
* Donated Nokia BL-5C Battery (1020 mAh 3.7V)
* Sandisk Mobile Ultra MicroSDHC 8GB Class 6 w/ reader (SDSDQY-81920E11M)

Currently installed:
* NAND: Qtextended
* MicroSD: Debian
* MicroSDHC: Unused.

Topics:
* http://wiki.openmoko.org/wiki/Talk:Qi

User:Laen

2008-11-13T21:38:07Z

Laen:

Hardware:
* Openmoko Inc. GTA02 (S/N: 8A8906526) (P/N: 56-21175-00) (Date Code: 20080935) (FCC ID: EUNGTA02E)
* Shipped Transcend MicroSD 512MB (MM4GR512UACY-PA | 82710000 745)
* Shipped Pouch
* Shipped FIC GTA02 Standard Battery Pack (1200mAh Li-ion 3.7V) x 2
* Donated Nokia BL-5C Battery (1020 mAh 3.7V)
* Sandisk Mobile Ultra MicroSDHC 8GB Class 6 w/ reader (SDSDQY-81920E11M)

Topics:
* http://wiki.openmoko.org/wiki/Talk:Qi

Currently installed:
* NAND: Qtextended
* MicroSD: Debian
* MicroSDHC: Unused.

User:Laen

2008-11-13T21:36:03Z

Laen:

User:Laen

2008-11-13T21:33:42Z

Laen:

User:Laen

2008-11-13T21:32:12Z

Laen:

Hardware:
* Openmoko Inc. GTA02 (S/N: 8A8906526) (P/N: 56-21175-00) (Date Code: 20080935)
* Shipped Transcend MicroSD 512MB (MM4GR512UACY-PA | 82710000 745)
* Shipped Pouch
* Shipped FIC GTA02 Standard Battery Pack (1200mAh Li-ion 3.7V) x 2
* Donated Nokia BL-5C Battery (1020 mAh 3.7V)

Topics:
* http://wiki.openmoko.org/wiki/Talk:Qi

User:Laen

2008-11-13T21:23:42Z

Laen: New page: O hai! * http://wiki.openmoko.org/wiki/Talk:Qi

O hai!

* http://wiki.openmoko.org/wiki/Talk:Qi

Talk:Qi

2008-11-13T21:21:46Z

Laen: New page: It could be me, but afai could see, the qi-s3c6410-andy_*.udfu is for the GTA03, even though that one flashed fine onto the GTA02. And it had sound. After all, i flashed it with the qi-s3c...

It could be me, but afai could see, the qi-s3c6410-andy_*.udfu is for the GTA03, even though that one flashed fine onto the GTA02. And it had sound. After all, i flashed it with the qi-s3c6410-andy_*.udfu, and that one gives me sound too. However, both tested with a Debian install on it.

The other thing that bugs me though, is that it still says "U-Boot 1.2.3-moko12 (May 9.." at the top of the menu. Does that have to do with the splash, or did my flash of Qi fail?

--[[User:Laen|Laen]] 21:21, 13 November 2008 (UTC)

Supported microSD cards

2008-11-04T11:44:23Z

Laen: /* Cards by Vendor */

{{todo|Maybe reformat table, see discussion page}}

There are a plethora of Transflash / microSD / SDHC (Secure Digital High Capacity) cards out there.

The Neo FreeRunner supports up to 8GB SDHC cards.

Some microSD cards appear to be too slow to work with the current default settings of the glamo driver, so some specific parameters must be set in uboot to use them (see https://docs.openmoko.org/trac/ticket/1743, and corresponding notes in the tables bellow).

There had been a [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=677 bug] in the SD device driver (s3cmci) which caused some trouble. Please make sure you use a post-september 4th kernel which applies our kernel patchset rev2832 or higher.

Booting from SDHC requires a u-boot from 2008-07-23 or later. '''But pay attention''' : there are problems with SDHC cards at suspend time. More details from [[Booting from SD#Booting_from_SDHC_.2F_suspend_problems|Booting from SD]]

Note that most vendors are using an irritating way of labeling the capacity of their cards (They are using the factor 1000 instead of 1024 for KB and MB). Therefore the real capacity of these cards will be about 5% less than the vendor's specification. For example, cards labelled ''6 GB'' will only have 5.7 GB of storage capacity.

If you use a card not listed here, please add to this table.

== Cards by Vendor ==
{| border=1 |
| Vendor || Model || Capacity || Speed || [[u-boot]] 1.1.6 || linux 2.6.17.14-fic5 || [[u-boot]] 1.2.0-moko8 svn1915 || [[u-boot]] 1.3.2-moko12 || linux 2.6.24+git75969 (2008.8 kernel as of Sept. 4, 2008) || OM2008.9's kernel
|-
| A-Data || microSDHC-8GB || 8GB (SDHC) || class 4 || ? || {{yes}} || ? || || ||
|-
| Corsair || CMFSDMICRO-512 || 512MB || || {{no}} || {{yes}} || || || ||
|-
| Dane-Elec || DA-SDMC-2048-R || 2GB || ? || ? || ? || ? || ? || {{yes}} ||
|-
| extreMemory || AE56-1280R || 128MB || || {{no}} || {{yes}} || {{yes}} || || ||
|-
| extreMemory || H256MS05 || 256MB || 60x || {{no}} || {{yes}} || {{yes}} || || ||
|-
| hama || 55371 || 256MB || || {{no}} || {{yes}} || {{yes}} || || ||
|-
| Intuix || IXMSDM128B60X || 128MB || 60x || {{no}} || {{yes}} || {{yes}} || || ||
|-
| Kingston || SD-C512 || 512MB || ? || {{no}} || {{yes}} || || || ||
|-
| Kingston || SD-C01G || 1GB || ? || {{yes}} || ? || || || ||
|-
| Kingston || [[Supported_microSD_cards/SD-C02G|SD-C02G]] || 2GB || ? || ? || {{yes}} || || {{yes}} || {{no}} || {{no}} (see [[Supported_microSD_cards/SD-C02G|SD-C02G]] )
|-
| Kingston || SDC4 (N0043-012.A00LF) || 4GB || ? || ? || FSO MS2 / Linux 2.6.24: I/O Errors while formatting [http://wiki.openmoko.org/wiki/Special:Emailuser/varacanero Contact me here] || || || ||
|-
| Patriot || PSF128MCSD-RC || 128MB || ? || {{no}} || ? || || || ||
|-
| Patriot || PSF8GMCSDHC4 || 8GB (SDHC)|| Class 4 || ? || ? || ? || {{yes}} || {{yes}} || {{yes}}
|-
| PNY || P-MICROSD512-BX || 512MB || || {{yes}} || {{yes}} || {{yes}} || || ||
|-
| PNY || P-MICROSD2GB-BX (card marked with MM8GR02GUACY) || 2GB || slow ? || ? || ? (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743] but apparently not enough) || ? || || ||
|-
| Pretec || || 128MB || ? || ? || {{yes}} || || || ||
|-
| SanDisk || SDSDQ-128 || 128MB || || {{yes}} || {{yes}} || {{yes}} || || ||
|-
| SanDisk || unknown || 256MB || || {{yes}} || {{yes}} || {{yes}} || || ||
|-
| SanDisk || unknown || 512MB || || {{yes}} || {{yes}} || || || ||
|-
| SanDisk || SDSDQ-1024-E10M || 1GB || || {{yes}} || {{yes}} || {{yes}} || || ||
|-
| SanDisk || SDSDQU-2048-E10M || 2GB || || {{yes}} || {{yes}} || {{yes}} || || ||
|-
| SanDisk || SDSDQ-2048-E11MK || 2GB || || || || || detects size incorrectly with U-Boot 1.3.2-moko12 (Aug 26 2008 - 08:24:58) : see http://docs.openmoko.org/trac/ticket/1815#comment:6 || ||
|-
| SanDisk || SDSDQ-4096-E11M || 4GB (SDHC) || || ? || {{yes}} || ? || {{yes}} || {{yes}} ||
|-
| SanDisk || SDSDQ-6144-E11M || 6GB (SDHC) || || ? || {{yes}} || {{no}} || || ||
|-
| SanDisk || SDSDQ-8192-E11M || 7GB (SDHC) || 4 || ? || {{yes}} || ? || || ||
|-
| SanDisk || [http://www.sandisk.com/Products/Item(2630)-SDSDQY-8192-A11M-SanDisk_Mobile_Ultra_microSDHC_8GBCard.aspx SDSDQY-8192-E11M/A11M] || 8GB (SDHC) || 6 || ? || {{yes}} || ? || || ||
|-
| SanDisk || SDSDQR-8192-E12M || 8GB (SDHC) || 4 || ? || {{yes}} || ? || || ||
|-
| SanDisk || SDSDQR-8192-???? || 8GB (SDHC) || 6 || ? || {{yes}} || {{yes}} || || ||
|-
| SanDisk || SDSDQ-008G-E11M || 8GB (SDHC) || 2 || || || || {{yes}} || {{yes}} ||
|-
| SanDisk || SDSDQ-008G-E11M || 8GB (SDHC) || 4 || ? || {{yes}} || || || ||
|-
| Silicon Power || SP004GBSTH006V10 || 4GB (SDHC) || 4 || ? || ? || ? || {{yes}} || {{yes}} || {{yes}}
|-
| Toshiba || SD-512R2W || 512MB || || {{no}} || {{yes}} || || || ||
|-
| Transcend || TS128MUSD || 128MB || || {{no}} || {{yes}} || || || ||
|-
| Transcend || TS256MUSD80 || 256MB || 80x || {{no}} || {{yes}} || {{yes}} || || ||
|-
| [http://www.transcendusa.com/ Transcend] || [http://www.transcendusa.com/Support/DLCenter/Datasheet/TSxxUSD.pdf TS512MUSD] '''(shipped with FreeRunner)''' || 512MB || || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}}
|-
| Transcend || MM4GRO1GUACY || 1GB || || ? || {{yes}} || ? || || ||
|-
| Transcend || TS1GUSDC || 1GB (SDC) || || ? || I/O errors while trying to install Om2008.8 rootfs.tar.gz, looks like [https://docs.openmoko.org/trac/ticket/1743 #1743] || ? || ? || ? ||
|-
| Transcend || TS4GUSDHC6 (card marked with MM8GR04GUACY) || 4GB (SDHC) || Class 6 || ? || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743]) || ? || || || {{no}}, see [http://docs.openmoko.org/trac/ticket/2025 bug #2025]
|-
| Transcend || TS8GUSDHC4 || 8GB (SDHC) || Class 4 || ? || ? || ? || {{yes}} || linux 2.6.24+git37+d744c88c14 (2007.2 kernel as of Aug 28, 2008) ||
|-
| Transcend || TS8GUSDHC4 || 8GB (SDHC) || Class 4 || ? || ? || ? || {{yes}} || {{yes}} since kernel of 30-Sep-2008 ||
|-
| Verbatim || 47225 || 1GB || || {{no}} || {{yes}} || {{yes}} || || ||
|-
| vox-fon || 1 GB || 1GB || || {{no}} || {{yes}} || || || ||
|-
| (Intenso) || ? || 4GB (SDHC) || || {{no}} || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743]) || ? || {{yes}} || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743])
|}

Note that cards with a "'''no'''" may still work at times, but that we just have found their behaviour too erratic to consider acceptable.
(Also note that this is a bug in our version of u-boot. The cards are probably fine.)