Mentalist Traceur | # 231 | 2011-01-11, 00:17 | Report

No. No it magically stopped needing to use the custom kernel sometime between now and the last time someone asked just a couple pages ago.

Rule of thumb: If someone bothers including an entire custom kernel image, chances are, you need that kernel image.

It's basically power kernel v46, with one module compiled and added in that the modified driver needs to work. If you're using it with multiboot, everything you need is included.

If you're using uboot, I can provide you with either the instructions on how to use the image lxp provides with dd and mkimage to combine it with a uboot image, or with a flashable kernel image already prepended with uboot (I'm assuming you already have the sources and files anyway, so presumably providing you with the same image attached to a uboot binary would just save you effort/time, and not violate anything).

IsaacDFP | # 232 | 2011-01-11, 00:54 | Report

Is there a fix for the camera "operation failed" issue? I do not have the "osso" installed and never did.

kulas | # 233 | 2011-01-11, 01:20 | Report

have you install F-cam api drivers?

Mentalist Traceur | # 234 | 2011-01-11, 01:25 | Report

Uninstall all the FCam stuff (BlessN900, FCamera, that one low-light picture taking program - everything that uses FCam drivers). Then reboot. Then reinstall all the FCam stuff. Reboot. The fix has been around for months. It happens when the kernel updates to a newer version, but doesn't update the drivers with it, or something along those lines gets screwed up. Reinstalling the drivers tends to fix it. If it doesn't, something else is wrong.

As for the osso stuff, if you have the N900, you have "osso". Osso - I'm not sure what it stands for though - is a prefix for a bunch of the stuff that's installed on the N900 by default. Some of it, like the thing lxp's patch fixes, is necessary for the system to work. For instance, half of the applications that are installed by default have osso in their name (I don't remember which ones do. You can always open up x-term and type osso and press tab twice. It should show a bunch of commands that start with osso in the name).

Anyway, the point is, this osso package fixes a bug in the stock osso-wifi-thingy. The problem is it makes apt-get complain about dependencies being wrong. If you don't install it, you don't lose too much - you just might have to occasionally restart your wifi driver to make it work right if the bug kicks in.

Haider | # 235 | 2011-01-11, 01:37 | Report

Is the downloading file really 141 mb or am I downloading a wrong file? Because I dont have much space left in my applications?

Mentalist Traceur | # 236 | 2011-01-11, 01:50 | Report

Yeah it's pretty big, but a lot of that is the source code, kernel headers, and other stuff.

The sources are just there to comply with GPL. They don't actually do anything, so they can be kept in the MyDocs partition or moved off-device. The kernel will override your current kernel, so it's not like it adds much if anything to the space used. The kernel headers don't need to be installed, so that's a lot of space aside from the source code saved. Then there's the multiboot-compatible package, so you don't need to install that unless you're using multiboot, and again, it probably won't take much space.

Also, you can keep the driver modules on the MyDocs partition, so long as you rewrite/edit the load/unload scripts to use absolute paths or the appropriate relative paths.

In other words, you're not actually using that much application space at all.

damion | # 237 | 2011-01-11, 03:38 | Report

Ah, that is excellent news. I'll look at what is needed in later kernels config/command-wise to actually enable AP mode having only read about the potential until now. Is it possible this already works due to the backport?

stlpaul | # 238 | 2011-01-11, 05:41 | Report

OSSO - Open Source Software Operations

IsaacDFP | # 239 | 2011-01-11, 07:32 | Report

Thank you very much. It's my first time playing around with power kernel so I wasn't aware of this. I also had a few other applications that failed to launch but reinstalling them also fixed it. As per the newly modified osso wifi driver, i'd rather manually restart it the rare times i get out of range than not be able to receive future ota updates. But thanks again

Tigerite | # 240 | 2011-01-11, 11:30 | Report

The feature modified wasn't the wifi driver, but osso-wlan, i.e. wlancond - which is simply a daemon ensuring wl1251-cal gets run, amongst other things. The driver is modified within the kernel module and does not prevent future OTA updates.