I have no idea what I'm doing when I can't use apt-get for updates. I see you have a script that says extract to the kernel folder...where is that? Do I download all 3 files on http://www.powerdeveloper.org/platforms/efikamx/kernel ?

You only need the binaries (boot- and modules-) and once you got them to the Efika (use an SD card or USB stick) you just extract them as normal;
When you reboot it will be using the new kernel. You may also want to edit /etc/fstab to add the line to it, to make it easier for next time by automounting the partition (they don't ship this way because trashing the boot partition is hard to fix :)

_________________
Matt Sealey

I got this error.. a bit of extra info that might be useful too. I starred out my username, as it has details of my real name.
*******@efikamx:~/stuff$ sudo mount /dev/sda1 /boot
*******@efikamx:~/stuff$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 3676352 1889656 1599944 55% /
none 257880 96 257784 1% /dev
none 257880 0 257880 0% /dev/shm
none 257880 84 257796 1% /var/run
none 257880 0 257880 0% /var/lock
none 257880 0 257880 0% /lib/init/rw
/dev/mmcblk0p1 1920704 5088 1915616 1% /home/*******/stuff
/dev/sda1 32018 2436 29582 8% /boot
*******@efikamx:~/stuff$ udo tar --lzma -xf boot-2.6.31.9-ER1-efikamx.tar.lzma -C /
-bash: udo: command not found
*******@efikamx:~/stuff$ sudo tar --lzma -xf boot-2.6.31.9-ER1-efikamx.tar.lzma -C /
tar: boot/type_id.bin: Cannot change ownership to uid 1000, gid 100: Operation not permitted
tar: boot/uImage: Cannot change ownership to uid 1000, gid 100: Operation not permitted
tar: Exiting with failure status due to previous errors

EDIT: A fellow efika owner(much more skilled than I with linux...and a former gentoo user.) told me not to worry about that error. Also, it worked! thanks!

Indeed the error is COMPLETELY harmless, just a side effect of it being a FAT formatted partition :)

I'm glad it worked. Do you have a display?

We are working on proper packaging for the kernel so it can be updated automatically, but there is a lot of finesse required, and it would also rely on the flash MTD driver working (right now, it is obfuscated so that it does not lock up on boot) so that we can edit boot arguments and do proper bootloader support.

_________________
Matt Sealey

Yes. I'm using it now. though the native resolution of my screen is 1330x768(or near that) and it is displaying at 1280x720, so it's a little fuzzy and unpleasant to look at. Further errors are the very edges of the screen being off the screen. Enough that knowing what the Desktop Environment looks like to be necessary to use it, but not enough to have to guess where things are.

Could you post the output of "dmesg" here?

It'd really help to work this out. There is a current limit on the pixel clock to 133MHz (HDMI spec is a lofty 165MHz) which we are hoping to work out if we can safely boost. On top of that, there seem to be some problems with clocks being slightly off, and maybe a couple driver bugs which are affecting the way the framebuffer drives the display.. some monitors state that their maximum resolution is just a hair over 165MHz though after overheads, which means.. well, they can't be driven by anything with an HDMI port :)

We will get through them though, apart from this, we got 2D acceleration working a little while ago, and once we get enough people with working displays we will ship the driver :)

_________________
Matt Sealey