When you say reboots, do you mean running the reboot command, or selecting reboot from the power key menu? Or do you mean powering off and then using the power key to power on? If it is the former, please try to power off and then power on, instead of reboot, and see if it helps.
About the subject of the thread - power kernel comes with u-boot since its maintainer, titan, chose so. Since it is free software you have a few options if you are unhappy with his choice, even without giving up the benefits of the power kernel:
You can create you own power 45 kernel image without u-boot, as Fabry did.
You can change the source package to generate a u-boot-less image, and distribute the package (with name changed) for users who feel like you.
You can change the source package to generate two images, one with and one without u-boot (it is easy) and offer this change to titan so that two kernel image packages will be created, and users will have a choice of which package to install. I don't know if titan will accept such a patch, but it has a better chance than merely asking for not including u-boot.
I don't see anything wrong with the concept of saying this feature sucks and asking the developer to get rid of it. There are many very responsive developers here who respond to the requests of the users.
I think that uboot is pretty dramatic and that there is a reasonable argument for making it separate from this wildly popular alternate kernel.
Personally, I love uboot so far and welcome it as part of the kernel.
But I don't see anything wrong about users who disagree making their case.
I think that u-boot is a great thing. I tested yesterday MeeGo. Because implemented u-boot in titan's kernel, it was very simple task, I just copied MeeGo's image on memory card. I hope that we will see soon similar image file for Nitdroid.
see, i do not have an issue with people finding bugs. i do not have an issue with people who expect the stable packages to work.
i do have an issue with folks that miss the devel point. who use broken stuff and demand it to be not broken. this is not only with meamo the case: you have something labled: stable/working and instead of that they take the things labled unstable/devel/experimental and then complain it realy is unstable.
i have an issue with that, because this behavior leads to a situation in which the devs have to do their experiments and theit developement behind closed doors and only make finished, fully functional, tested stuff public. i have an issue with that for i do like to see the work of others even though it is not finished because that might help me to solve a similar problem or save me the trouble of doing the same work already done by others again. and i want to see the work in the open for there might be someone out there with a brilliant idea to a problem.
i also have an issue with that because you need a bootloader for all kind of projects. it's good if all the projects try to get it in so that they will work smoothly together and not break each others stuff. and again if that happens behind closed doors you can not try to make things work smoothly together for you don't know what the others do or already have done. so i realy like to have the devel stuff in the open. and ask those who use that stuff to respect that it is such: under construction.
if devel stops being devel - that is being inherently broken - you can close it down alltogether and only have a stable branch. that is what i have a real issue with. and i also have an issue with measuring devel stuff,things under construction, based on the number of bugs and unactivated features instead of the potential they have and what it will be. the possibility to resolve issues.
you just don't go to a construction site and and demand to stop the construction for there are no carpets on the floor and no glass in the windows - and on top reason that with: "look, others also found that this house has no carpets it realy has no carpets".
well... never mind ..
If you first make sure nothing (charger, computer, etc.) is connected to the usb port of the N900. Then power off by selecting power off from the power key menu. Make sure the device does really turn off and does not reboot immediately (as might happen if you used host mode). Then you turn it on in the usual way by pressing the power key.
Does it happen that the audio does not work after such a sequence?
If you first make sure nothing (charger, computer, etc.) is connected to the usb port of the N900. Then power off by selecting power off from the power key menu. Make sure the device does really turn off and does not reboot immediately (as might happen if you used host mode). Then you turn it on in the usual way by pressing the power key.
Does it happen that the audio does not work after such a sequence?
If if does please run the command
dmesg > out.file
and upload the out.file somewhere I can see it.
hey there
i dont have a charger or anything else on the device.
now i shut down the n900 wait a min. and boot it.
no sound.
I have had same kind of audio and also video problems as Erazor. After some boot times (now it took 5) audio & video stop working. Rebooting (power key & battery removal) do not help. When problems occurs, then boot-up video is not showed, no audio, no video playback possible.
Here is dmesg files from OK and Not OK boot-ups. dmesg.zip
This v45 test was my 4th trial and only thing which has helped is reinstall of kernel-power. v42 is OK
I have had same same kind of audio and also video problems as Erazor. After some boot times (now it took 5) audio & video stop working. Rebooting (power key & battery removal) do not help. When problems occurs, then boot-up video is not showed, no audio, no video playback possible.
Here is dmesg files from OK and Not OK boot-ups. dmesg.zip
This v45 test was my 4th trial and only thing which has helped is reinstall of kernel-power. v42 is OK
