When I try to update the f-cam drivers from this post http://talk.maemo.org/showpost.php?p...postcount=5028 via the app manager I get an error. Uninstalling the fcam apps and fcam drivers and trying to install the driver from the post doesn't help.

Try

sudo gainroot
apt-get update
apt-get upgrade

I installed the .deb posted here and then I did that. Works like a charm on power43,44,and 45.

And question: Why is Titan updating the Kernel so much? Don't fix it unless it is broken, what was wrong with it? I have been running at 1150MHz for over 4 months and I have been doing just fine. What has changed? I am sure there is some reason (besides the addition of uBoot)

rofl, that amde my day, no offence

I know!!

he,he,he

I'm a NOOB!

Thanks a lot --- that is helping.

Clemens.

should i overclock to 250-1150 or 500-1150, and is there a difference when i play games between the two

the power kernel is not only for overclocking, many features & patches were added & needed for other programs to work, e.g USB host mode

it will be best if you want to update the power kernel you should read the changelogs https://garage.maemo.org/news/?group_id=1528 and follow threads that discuss the power kernel

if you think you don't need the changes in the latest power kernel & doing fine with your current kernel, then stick with it...

First: Titan's questions:
WAS stock pr1.3 kernel, no other patches or SOs or boot loaders running. I was highly interested in the usb host mode, not the OC part. So, no OC.

Here is my experience with power kernel so far:
Whenever I restart(not turn off and then on, restart) it doesn't. It looks like will reboot, but when it will boot, the light dims and no boot. Then, I have to turn it on in the "old fashioned way" (by holding the turn on button, the blue led lightning on and etc).

It broke my maemo-pc-connectivity. It doesn't work, even by reinstalling. And I really need it in order to get internet TO the fone FROM the pc(NOT tethering), via _USB_ (I have never been able to do it through bluetooth). My main interest was to get internet to the device via USB without the neet to maintain the PC on, but, no luck even to USB sticks.

I tried to get a Cyberpower CPH420MP(old-not manufactured anymore) self powered hub AND another self powered hub to connect something to it, and no luck. Then I tried to see if there was any readings in the energy coming fro the USB: No energy - zero volts.

I'll uninstall or reflash the pr1.3 back. I hope you guys be able to figure it out.

Thank you for your effort!

There won't be a difference because the cpu will run at max speed the most time.
Your phone will just be a bit snappier (and drains a bit more battery) if you use 500-1550Mhz instead of 250-1150.

I like to use uboot (or multiboot) to start Meego from my sd card.

Now i have installed the latest power kerner 45..

I have installed the raw image on the N900 itself:

Nokia-N900:~# dd if=/home/user/MyDocs/meego-core-armv7l-n900-1.1.80.4.20101102.1-mmcblk0p.raw of=/dev/mmcblk1

that does result in these partitions:

Nokia-N900:~# sfdisk -l

Disk /dev/mmcblk1: 979328 cylinders, 4 heads, 16 sectors/track
Warning: The partition table looks like it was made
for C/H/S=*/4/32 (instead of 979328/4/16).
For this listing I'll assume that geometry.
Units = cylinders of 65536 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/mmcblk1p1 0+ 24414- 24415- 1562500 83 Linux
/dev/mmcblk1p2 24416 28319 3904 249856 83 Linux
/dev/mmcblk1p3 0 - 0 0 0 Empty
/dev/mmcblk1p4 0 - 0 0 0 Empty

Disk /dev/mmcblk0: 977024 cylinders, 4 heads, 16 sectors/track
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/mmcblk0p1 1 884864 884864 28315648 c W95 FAT32 (LBA)
/dev/mmcblk0p2 884865 950400 65536 2097152 83 Linux
/dev/mmcblk0p3 950401 974976 24576 786432 82 Linux swap / Solaris
/dev/mmcblk0p4 0 - 0 0 0 Empty

but when i reboot and i try for example:

run mmcboot

i get wrong image format for bootm command..

anybody know what that can be?


if i just let it boot i get something like

unable to read "boot.scr" from mmc 0:1
invalid partition #3

but what is that partition #3? i only have 2 partitions on it...