upgraded from v47 to v48 a couple of weeks back . using backup menu and multiboot . everything worked perfect straight away and no problems at all...

Same problem in qemu - After installing settings package black Xorg screen. (Without settings package + manually compiled qemu kflges module - all ok)

But there is no error, no warning in dmesg or serial console...

Problem in qemu was found. But I do not understand why it works in upgrade v47-->v48 and setting11-->settings12 and not with v48+setting12.

In /etc/default/mount-opts is KERNEL-POWER-HOOK line which run script /etc/kernel-power/pre-mount (if exists). But if this script does not exists it hangs too (WHY?) And why it does work after upgrade?

I should correct myself. MobileHotspot does work with power48. I originally did not have the repository containing "wireless-tools" enabled in App-Manager. After enabling the repository, (Fremantle Tools), all is well...

So far, power48 is working well, though the vibration from touching the touchscreen is somewhat prolonged occasionally. This could be my core-voltage settings, though.

Cheers!

Perhaps something to do with an updated version of ash in busybox power?

it is in qemu with clean pr 1.3

but something new I have. Problem (in qemu and I'm sure same on real n900) is that /home and /opt was not mounted, so hildon-desktop cannot be started (black Xorg screen). But why /home is not mounted? /etc/event.d/rcS-late is responsible for mounting. So I enabled console output from this script (then double called sync), but then no error and qmeu normally bootmed me.

So I again created clean qemu image, installed kernel v47 and shutdown. All ok. Started again installed setting12, enabled debug output from rcS-late, double sync, shutdown. Started again, no errors in rcS-late, home mounted and all is OK.

I do not understand why it works if I enabled debug output (changed 'console none' to 'console output' and added some echo...). I ony called $ sync and $ sync.

Finally problem with kernel-power-settings was found and fixed.

Problem:
I'm using madde for compiling and creating deb packages. Madde has its own dpkg tools (own tool for low-level creating deb package) which ignore file permitions (or change it or use its own??). And it still change permitions of /etc/kernel-power/pre-mount from 755 to 644. And upstart failed in /etc/default/mount-opts (which started pre-mount script).

Solution:
Changed generating file /etc/default/mount-opts which execute script from method 'if test -x FILE && ./FILE' to 'sh FILE || true'. In qemu now all works.

Why it worked with update? Config file /etc/kernel-power/pre-mount was not changed, so dpkg does not replaced it when update from 11 to 12. (and permitions was kept).

When I debugged it I also chmod +x permitions, so I was unable to debug it...

New fixed version is on same place.

Curiosity, it could be possible to generate a power kernel with Android support ?

I don't know what patches are applied by Android/Nitdroid's team to kernel but I have wish to try to run Nitdroid on a chroot enviroment (like SuperJumbo for BeagleBoard).

To do so we need a kernel which can boot Maemo and Nitdroid (full boot)

Dear Pali and kernel-dev team

All the work you're doing is great. It's amazing that you're able to maintain the momentum and keep us informed of what's happening. My question is - when the version nudges on to .49 or .48 becomes stable enough to start developing addons, please would you start a new thread for each addon/update e.g "kernel development: abc for v.XY"?

I ask this for a few reasons:
- kernel development extends across so many features thus questions and discussions will be equally diverse. Therefore, they [dicussions] can appear disjointed, which makes finding answers a bit difficult and will in turn result in a lot of people repeating the same question.
- Reading through over a thousand posts to get up to speed on testing things to watch out for is beyond most of us!
- The thread title doesn't accurately reflect its content: it started by pulling together the v0.46 patches, it goes right through all the v0.47 work and now we're discussing pre-extras-devel 0.48.

Consiolidation and evolution are good but but it's quite confusing, especially with the number of sub-topics.

On a completely different note, have you had any news about updating the package interface. I see Titan is still the sole maintainer for a few of the associated packages - might that be something to do with it? A work-around, which would be a pain to start withe because it would break the auto updates would be to upload a package with a new name, say "power-kernel", instead of "kernel-power"? If you did this it might be an idea to make a member of the council a silent 2nd maintainer so it can "change hands" easily in case you can't/dont't want to continue?

I would also like to reiterate that both the code and efforts to update the docs are amazing and really help us all to make the most of this device. I have noticed the irony of this now slightly verbose, multi-themed post so, over-and-out!

After discusion on #maemo with DocScrutinizer and ShadowJK we decided to disable one i2c patch which break API and can damage n900 (patch was added in v45). When this patch is disabled - bme is broken when bq modules is loaded.

So autoloading bq module is disabled too and now is not possible to have both bme and bq. (bq module is still installed so after stopping bme is possible to manually load it).

Now I recompiling v48 and publish new version as soon as.