PanzerSajt | # 271 | 2012-06-20, 20:00 | Report

I was investigating during the day and found the output of the Amnient Light Sensor and the Accelerometer.

I have atteched the scripts which are showing the outputs of these two sensors. Hope it will help someone.

Just rename the two files to accel.sh and ambient.sh and sudo chmod +x them. They just give you raw data from the sensors

Attached Files

	accel.sh.txt (105 Bytes, 113 views)
	ambient.sh.txt (118 Bytes, 113 views)

caveman | # 272 | 2012-06-20, 20:31 | Report

ok, I have checked that I have this one installed :-)

I totally agree

Indeed, I re-ran the installation without selecting the upgrade. While I have seem the same upstart error while installing acpid, the installation script has not stopped at that point and completed fine. My first impression is that upstart failed to start inside the qemu vm.

Thanks for your help ;-)

Now let's try to boot this beast :-P

caveman | # 273 | 2012-06-21, 11:14 | Report

I had to make a small manual adjustment in the uSD after the install.sh script completed. My first partition was of type 83 instead of 0C, although it did contain a vfat filesystem, so I had to fix it by hand.

PanzerSajt | # 274 | 2012-06-21, 11:39 | Report

Can you provide me some inscructions on fixing SD-card since I have the same problem as you and the partitions also overlap each other.

caveman | # 275 | 2012-06-21, 11:40 | Report

I tried booting ubuntu with u-boot-menu from http://talk.maemo.org/showthread.php?t=81613.

Three tries were made:

1. run sdboot
2. boot from vfat partition
3. boot from ext4 partition

sdboot run sdboot from u-boot console. It complains about invalid uImage format, but loads the kernel. The kernel fails with
'mmc0: error -110 whilst initializing SD card'
mmc1 is recognized (internal MMC)

boot from vfat partition I used the following item file:
It says: 'Wrong Ramdisk Image format' and goes to u-boot console.
Kernel and uImage MD5:
boot from ext4 partition I used the following item file:
Kernel and uImage MD5:
Similar to the 'run sdboot' case. The kernel is loaded and fails with -110 on uSD.

This is the only uSD I have available, so I can not rule out a card problem.

Those are with the custom kernel. Is it worth trying with another kernel?

caveman | # 276 | 2012-06-21, 11:46 | Report

I placed the uSD inside the SD adapter and edited the partition table on the PC with cfdisk, where I have changed its type.

If your partitions overlap it becomes trickier. If you know the correct start locations, you can delete the partition and recreate with the correct type, the same start location and correct size. But that will work only if the filesystem has the correct size inside the partition.

unknown.obvious | # 277 | 2012-06-21, 16:43 | Report

uhm, I assume you do have u-boot combined with stock kernel. If you'd use kernel power you shouldn't get -110 errors while trying to load a kernel from sd.

Explanation: some sdcards need the dto=14 patch enabled in kernel. stock kernel doesn't have it. so if stock kernel u-boot combi access sdcard you get -110 error. kernel-power, as far as I know, does have that patch enabled.

---

Last edited by unknown.obvious; 2012-06-21 at 16:51.

caveman | # 278 | 2012-06-21, 17:32 | Report

Sorry, but I am not sure I followed. My N900 runs u-boot-menu with KP50, and I am trying to boot ubuntu from the uSD (from u-boot-menu) using your custom kernel. The kernel does load, but the boot fails with the -110 error when trying to mount the root partition on the uSD. You mean I should try to boot ubuntu with KP50?

unknown.obvious | # 279 | 2012-06-21, 17:39 | Report

If you flashed KP50 u-boot combi and still get a -110 error then either there is a bug in pali's u-boot or your sdcard is broken.

freemangordon | # 280 | 2012-06-21, 19:32 | Report

what u-boot is that?