[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] Ranomez:
You can add all the other OS later, for just CM9 and 2.2 stock (+root using custom kernel) you can just use this already setup kboot: https://copy.com/x8q1vlOqHzFMEgPQ (and yes I do know copy will close so I need to re-upload kboot if I want people to be able to download it also in the future but trying to find a permanent cloud service to do so). Just extract the archive on the PC, you will get a kboot folder, open it, inside you will see the files zImage and initramfs.cpio.gz and again a folder named kboot, what you do is copy the kboot folder to your internal memory (the one inside the other kboot folder, lol, this is confusing even for me, the one that contains 3 folders and no files, the folders being: conf, images, os) and then just flash the initramfs.cpio.gz and zImage from the SDE flash menu and then when you reboot you will be greeted with a boot menu with the following options:

Archos+root-this is to boot the stock 2.2 firmware and have root, it uses the RW root kernel by chrulri-BE EXTREMELY CAREFUL as it is the RW kernel you can make changes to the system and they are saved in the unionfs partition (about 35MB IIRC) so you can really break things and then won't be able to boot the Archos 2.2 Firmware from kboot anymore (or loose root as I did a few times), you can still boot it from recovery though as the system is actually a squashfs image so it's impossible to permanently modify it.

ICS-LZO-this is the CM9 with LZO kernel and will load the OpenAOS boot menu from where you choose CM9

ICS-SNAPPY-25-this will boot CM9 (again using the OpenAOS bootmenu) with the Snappy 25% kernel

ICS-SNAPPY-35-This will boot CM9 with the Snappy 35% kernel (again OpenAOS bootmenu first)

I included all the kernels for CM9 as I also have them all, you can test and see which of them behaves better.

Also if you do manage to brick the Archos+root entry it's quite easy to fix it, you have two options:

Either download the non-rw kernel made by chrulri from here: http://xdaforums.com/showthread.php?t=930197 (latest version) and then go on your internal memory (you will need to boot in the Archos 2.2 stock from recovery to do this, duh, or I think I remember there was an option in recovery to mount the internal memory in MSC) and then go in the kboot folder, in there go in the os folder and in there create a new folder (let's say Archos+root+non-RW) then in that folder just copy the initramfs.cpio.gz and zImage you got from that thread. Then reboot and boot the new entry (the new entry will have the name of the folder) and use a root explorer (for example root explorer or es file explorer) to go to /mnt/system/unionfs/system and undo your changes (delete files you added or undelete files you deleted), this folder will have the same structure as the /system folder but only contain the subfolders and files that have been modified. After this process you should be able to once again boot the Archos+Root entry.

Or an even simpler method: get either the OpenAOS 2.3 kernel or bizcuite's linaro kernel for OpenAOS (though I don't actually think some things on stock work with that, like wi-fi) and do the same procedure as I explained above with the chrulri's non-rw kernel to install it on the kboot boot menu then edit menu.lst to give the Archos boot option, just open it in Notepad++ and copy this line at the end of the file (on a newline): "Archos|ARCHOS|ARCHOS|/init|0" (without the quotes) then save (first look in the Edit tab under EOL Conversion that it is set to UNIX/OSX style and not Windows style, the grayed out option is the one selected). Now reboot the tablet and boot the new entry (whatever you called it, perhaps OpenAOS-kernel) and you will see the same boot menu as with ICS but now will have two entries (one being named Archos), DON'T select the Archos entry yet, first go to advanced and select "Enable rooted device" (should already be enabled, if you see Disable instead of Enable don't click it) and "Enable clear unionfs dir" then go back and select the Archos entry, now it will boot and be rooted and should have cleared all the changes you made to your unionfs and the Archos+root entry will once again boot, although you can also use the OpenAOS kernel to have root on stock I would still recommend using the other option just because technically the OpenAOS kernel is made to boot CM7 (and debian) so it's not optimized for 2.2.

Also if you do install the OpenAOS kernel and are still interested in booting Angstrom/Debian for it here are the templates for the entries you need to add:

"Debian||/debianlxdefinal.img|/sbin/init|1"

And here is an explanation to the things:

The first thing (Debian) before the first pipe sign "|" is the name, that is how the entry will appear in the OpenAOS bootmenu.

The second thing (nothing here, in the Archos entry it is Archos) is used ONLY and ONLY for booting the stock Archos firmware, for anything else leave it blank.

The third thing (/debianldefinal.img) is telling it where to boot from, this will be an img file on the internal memory.

The fourth thing (/sbin/init) is the location of init, for linux images it will be "/init" and for linux images "/sbin/init".

The fifth and last hing (1) is telling it if it is booting an android or linux OS, 1 being for linux and 0 for android.

That's pretty much all you need to know in order to install linux images and/or CM7, it's pretty easy to follow, just put pipes "|" between them and don't insert blank spaces, I don't think that will work. And do remember that although you will get the exact same boot menu when loading the ICS kernel (any of them) you CAN'T boot ANYTHING else with that kernel. Also I am pretty sure that the OpenAOS linaro kernel made by bizcuite does not work properly on stock or linux images so use the unmodified one, though if you do want to use CM7 also (android 2.3) I can really recommend the linaro kernel over the stock one.

I think except the location of the urukdroid kernel that is all you might ever want to know about this tablet, I find linux pretty useful on the tablet, but you need to have the knowledge necessary to use it without bricking it (changing the repos to the legacy ones, from time to time changing to the latest repos without letting it update anything else than you need and going back).

Also thank you very much, I really hope I don't manage to break the hardware of this nice thing, especially since I really love the 3D gaming.