maemo.org - Talk
Page 14 of 75 « First 41213 14 151624 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Maemo 5 / Fremantle (https://talk.maemo.org/forumdisplay.php?f=40)
-   -   [Announce] kernel-power stable v49 in Extras-Testing (https://talk.maemo.org/showthread.php?t=71879)

petur 2011-05-11 11:40
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by N900@900MHz (Post 1004047)
just tested GPS with Sygic no problems here.:)
I have power kernel v47 and CSSU (latest)
Strangely enough, when I tested now it looked OK as well, but only when outside with plenty of sky visible.
So maybe it isn't A-GPS but cell tower location (since indoors I get no location updates)....

Estel 2011-05-11 12:26
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by MastaG (Post 1004090)
Since Pali joined the CSSU team and freemangordon is providing DSP patches for the kernel and userland to support 720p record/playback.
Does this mean we'll eventually see a CSSU that supports everything?
720p playback/record, USB OTG, overclocking, recovery console etc..?
Probably one day, but not with just CSSU update. CSSU is meant to provide patches/fixes/new features that can't be easily added by packages in extras, for example. so as for hostmode (i personally don't like "USB on the go" name, it's just marketing chitter), there is HEN project, and i think it will be keep that way. Also, power kernel is not going to be merged into CSSU.

I also hope that feemangordon work will allow us to watch/record 720p video - i hope that he won't get on ambition and will not stop working on it, he seems very upset that pali don't wanted to include his packages in way that break video watching.

Anyway, I'm with pali on this - i also can't imagine including package that will ''break'' userland media playing - should be included in parallel with userland updates available in extras devel at least. When i just think about massive outcry and 300+ pages of bug reporting about broken videos here, i feel cold ;P If just temperature/10 thing spammed this topic so much, how we will look with "upgraded" thing that make videos unplayable, and we can only reply by "it lacks userland application by now, sta tuned..."? Brrrr....

so, i hope that no one will get to high in ambition (sorry if i interpreted that posts totally wrong, what also may be the case here), and continue hard work, cause i can't imagine someone other to deliver such patches as freemangordon's - sorry if someone else is able to do it, but i haven't heard about such a person ;) Yea, we REALLY appreciate your work freeman, and hope for more!

petur 2011-05-11 12:35
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by Estel (Post 1004124)
<snip>... so as for hostmode (i personally don't like "USB on the go" name, it's just marketing chitter)...<snip>
It's even more... USB host and USB-on-the-go are two different things. Hostmode is what it says (being USB host or master), but USB OTG is actually the protocol that allows host and client to negotiate who is master, or to even swap roles.

vi_ 2011-05-11 13:09
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by Estel (Post 1004124)
Probably one day, but not with just CSSU update. CSSU is meant to provide patches/fixes/new features that can't be easily added by packages in extras, for example. so as for hostmode (i personally don't like "USB on the go" name, it's just marketing chitter), there is HEN project, and i think it will be keep that way. Also, power kernel is not going to be merged into CSSU.

I also hope that feemangordon work will allow us to watch/record 720p video - i hope that he won't get on ambition and will not stop working on it, he seems very upset that pali don't wanted to include his packages in way that break video watching.

Anyway, I'm with pali on this - i also can't imagine including package that will ''break'' userland media playing - should be included in parallel with userland updates available in extras devel at least. When i just think about massive outcry and 300+ pages of bug reporting about broken videos here, i feel cold ;P If just temperature/10 thing spammed this topic so much, how we will look with "upgraded" thing that make videos unplayable, and we can only reply by "it lacks userland application by now, sta tuned..."? Brrrr....

so, i hope that no one will get to high in ambition (sorry if i interpreted that posts totally wrong, what also may be the case here), and continue hard work, cause i can't imagine someone other to deliver such patches as freemangordon's - sorry if someone else is able to do it, but i haven't heard about such a person ;) Yea, we REALLY appreciate your work freeman, and hope for more!
Oh, somthing that could potentially break some functions of your device in the development repositorys? who would suggest something so reckless?

Everyone knows that 'good' software just works without any testing whatsoever and that the development repos is just where we hide stuff because we feel nubes are not good enough to use it.

So im totally with you, lets keep all of these stupid development packages OUT of the development repos just to keep the dumbasses happy.

misiak 2011-05-11 13:37
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by vi_ (Post 1004142)
Oh, somthing that could potentially break some functions of your device in the development repositorys? who would suggest something so reckless?

Everyone knows that 'good' software just works without any testing whatsoever and that the development repos is just where we hide stuff because we feel nubes are not good enough to use it.

So im totally with you, lets keep all of these stupid development packages OUT of the development repos just to keep the dumbasses happy.
Man I love your writing style :P Back on topic: the perfect situation (in my oppinion) would be freemangordon also joining CSSU team preparing packages to be compatible with both old kernel and kernel with his dsp pathes (it has to be possible, it just has... even via some external config file read at startup of every broken deamons and system services) and, when this update is pushed, further work on implementing 720 hd video playback in kernel (and obviously making this new kernel-power package depend on CSSU, but only when CSSU release reaches 'stable' state). This way 720 playback would be possible with some new power kernel release and with stock kernel (or older power kernels) media would still work as previously. That's my oppinion on topic, but there's not much sense writing it here, because neither I nor you reading this thread are to decide ;) (unless someone in charge of CSSU and powerful enough to make such decision reads this words)

freemangordon 2011-05-11 13:39
Re: [Announce] kernel-power v47
 
@ estel ... looks like you have missed my post with patch that do not break anything. No problem, could happen to everyone :) this thread is so bloated these days. http://talk.maemo.org/showpost.php?p...&postcount=452

handaxe 2011-05-11 19:07
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by Pillum (Post 1003909)
since 47, someplayer and symfonie isnt working more anymore...the sound is scrambled
Sounds issues as above are due to gstreamer0.10-av (now updated so fixed(????)). For most, that package was pulled in by a changed dependency for ogg-support between versions 1.5 and 1.7.

Both power47 and CSSU have been blamed for gstreamer0.10-av's sins.

misiak 2011-05-11 19:14
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by handaxe (Post 1004368)
Sounds issues as above are due to gstreamer0.10-av (now updated so fixed(????)). For most, that package was pulled in by a changed dependency for ogg-support between versions 1.5 and 1.7.

Both power47 and CSSU have been blamed for gstreamer0.10-av's sins.
We should hang the developer for very bad timing :P He unfortunately released buggy package in the same time as some cssu update and kernel update... Releasing it few days later would save a few posts from both threads. As well as people complaining thay cannot boot while they manually made some changes and made typos in filenames (at least two people from this thread).

colin.stephane 2011-05-11 19:26
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by pali (Post 983578)

New version v47 of kernel-power released!


News:
* Compiled more usb host modules
* Backported bq27x00_battery module (battery status)
* Some patches from garage projects
* Multiboot support
* Fixed problem with JoikuSpot_Bouncer

Update:
Use Hildon Application Manager or via apt-get

Step 1 Installation:
In Hildon Application Manager install package: Linux Kernel for power user
Or via apt-get package: kernel-power-flasher

Step 2 Multiboot support:
First see step 1.
Then in Hildon Application Manager install package: Linux Kernel for power user (boot image)
Or via apt-get package: kernel-power-bootimg

All work is in my power-kernel git repository (fork of garage project):
git clone http://atrey.karlin.mff.cuni.cz/~pali/kernel-power.git
Hi pali,

The new driver bq27x00_battery does not report properly parameters :

Here is output from the new driver :

Code:
-bash-2.05b# lshal -u /org/freedesktop/Hal/devices/computer_power_supply_battery_bq27200_0
udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_bq27200_0'
  battery.charge_level.current = 0  (0x0)  (int)
  battery.charge_level.design = 2056  (0x808)  (int)
  battery.charge_level.last_full = 1531  (0x5fb)  (int)
  battery.charge_level.percentage = 0  (0x0)  (int)
  battery.charge_level.rate = 161  (0xa1)  (int)
  battery.is_rechargeable = true  (bool)
  battery.present = true  (bool)
  battery.rechargeable.is_charging = false  (bool)
  battery.rechargeable.is_discharging = true  (bool)
  battery.reporting.current = 0  (0x0)  (int)
  battery.reporting.design = 2056  (0x808)  (int)
  battery.reporting.last_full = 1531  (0x5fb)  (int)
  battery.reporting.rate = 161  (0xa1)  (int)
  battery.reporting.technology = 'Li-ion'  (string)
  battery.reporting.unit = 'mAh'  (string)
  battery.technology = 'lithium-ion'  (string)
  battery.type = 'primary'  (string)
  battery.voltage.current = 3757  (0xead)  (int)
  info.capabilities = {'battery'} (string list)
  info.category = 'battery'  (string)
  info.parent = '/org/freedesktop/Hal/devices/computer'  (string)
  info.product = 'Generic Battery Device'  (string)
  info.subsystem = 'power_supply'  (string)
  info.udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_bq27200_0'  (string)
  linux.hotplug_type = 2  (0x2)  (int)
  linux.subsystem = 'power_supply'  (string)
  linux.sysfs_path = '/sys/class/power_supply/bq27200-0'  (string)
And here is output from bme :

Code:
-bash-2.05b# lshal -u /org/freedesktop/Hal/devices/bme
udi = '/org/freedesktop/Hal/devices/bme'
  battery.charge_level.capacity_state = 'ok'  (string)
  battery.charge_level.current = 3  (0x3)  (int)
  battery.charge_level.design = 8  (0x8)  (int)
  battery.charge_level.last_full = 0  (0x0)  (int)
  battery.charge_level.percentage = 25  (0x19)  (int)
  battery.charge_level.unit = 'bars'  (string)
  battery.is_rechargeable = true  (bool)
  battery.present = true  (bool)
  battery.rechargeable.is_charging = false  (bool)
  battery.rechargeable.is_discharging = true  (bool)
  battery.remaining_time = 0  (0x0)  (int)
  battery.remaining_time.calculate_per_time = false  (bool)
  battery.reporting.current = 311  (0x137)  (int)
  battery.reporting.design = 1241  (0x4d9)  (int)
  battery.reporting.last_full = 0  (0x0)  (int)
  battery.reporting.unit = 'mAh'  (string)
  battery.type = 'pda'  (string)
  battery.voltage.current = 3684  (0xe64)  (int)
  battery.voltage.design = 4200  (0x1068)  (int)
  battery.voltage.unit = 'mV'  (string)
  info.addons = {'hald-addon-bme'} (string list)
  info.capabilities = {'battery'} (string list)
  info.category = 'battery'  (string)
  info.parent = '/org/freedesktop/Hal/devices/computer'  (string)
  info.product = 'Battery (BME-HAL)'  (string)
  info.subsystem = 'unknown'  (string)
  info.udi = '/org/freedesktop/Hal/devices/bme'  (string)
  maemo.charger.connection_status = 'disconnected'  (string)
  maemo.charger.type = 'none'  (string)
  maemo.rechargeable.charging_status = 'off'  (string)
  maemo.rechargeable.positive_rate = false  (bool)

Oviously, the corrects values are the ones from bme.

Hope it help ...

A++

PS : I have also posted same message here : http://talk.maemo.org/showpost.php?p...&postcount=799

pali 2011-05-11 19:42
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by colin.stephane (Post 1004389)
Hi pali,

The new driver bq27x00_battery does not report properly parameters :

Here is output from the new driver :

Code:
-bash-2.05b# lshal -u /org/freedesktop/Hal/devices/computer_power_supply_battery_bq27200_0
udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_bq27200_0'
  battery.charge_level.current = 0  (0x0)  (int)
  battery.charge_level.design = 2056  (0x808)  (int)
  battery.charge_level.last_full = 1531  (0x5fb)  (int)
  battery.charge_level.percentage = 0  (0x0)  (int)
  battery.charge_level.rate = 161  (0xa1)  (int)
  battery.is_rechargeable = true  (bool)
  battery.present = true  (bool)
  battery.rechargeable.is_charging = false  (bool)
  battery.rechargeable.is_discharging = true  (bool)
  battery.reporting.current = 0  (0x0)  (int)
  battery.reporting.design = 2056  (0x808)  (int)
  battery.reporting.last_full = 1531  (0x5fb)  (int)
  battery.reporting.rate = 161  (0xa1)  (int)
  battery.reporting.technology = 'Li-ion'  (string)
  battery.reporting.unit = 'mAh'  (string)
  battery.technology = 'lithium-ion'  (string)
  battery.type = 'primary'  (string)
  battery.voltage.current = 3757  (0xead)  (int)
  info.capabilities = {'battery'} (string list)
  info.category = 'battery'  (string)
  info.parent = '/org/freedesktop/Hal/devices/computer'  (string)
  info.product = 'Generic Battery Device'  (string)
  info.subsystem = 'power_supply'  (string)
  info.udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_bq27200_0'  (string)
  linux.hotplug_type = 2  (0x2)  (int)
  linux.subsystem = 'power_supply'  (string)
  linux.sysfs_path = '/sys/class/power_supply/bq27200-0'  (string)
And here is output from bme :

Code:
-bash-2.05b# lshal -u /org/freedesktop/Hal/devices/bme
udi = '/org/freedesktop/Hal/devices/bme'
  battery.charge_level.capacity_state = 'ok'  (string)
  battery.charge_level.current = 3  (0x3)  (int)
  battery.charge_level.design = 8  (0x8)  (int)
  battery.charge_level.last_full = 0  (0x0)  (int)
  battery.charge_level.percentage = 25  (0x19)  (int)
  battery.charge_level.unit = 'bars'  (string)
  battery.is_rechargeable = true  (bool)
  battery.present = true  (bool)
  battery.rechargeable.is_charging = false  (bool)
  battery.rechargeable.is_discharging = true  (bool)
  battery.remaining_time = 0  (0x0)  (int)
  battery.remaining_time.calculate_per_time = false  (bool)
  battery.reporting.current = 311  (0x137)  (int)
  battery.reporting.design = 1241  (0x4d9)  (int)
  battery.reporting.last_full = 0  (0x0)  (int)
  battery.reporting.unit = 'mAh'  (string)
  battery.type = 'pda'  (string)
  battery.voltage.current = 3684  (0xe64)  (int)
  battery.voltage.design = 4200  (0x1068)  (int)
  battery.voltage.unit = 'mV'  (string)
  info.addons = {'hald-addon-bme'} (string list)
  info.capabilities = {'battery'} (string list)
  info.category = 'battery'  (string)
  info.parent = '/org/freedesktop/Hal/devices/computer'  (string)
  info.product = 'Battery (BME-HAL)'  (string)
  info.subsystem = 'unknown'  (string)
  info.udi = '/org/freedesktop/Hal/devices/bme'  (string)
  maemo.charger.connection_status = 'disconnected'  (string)
  maemo.charger.type = 'none'  (string)
  maemo.rechargeable.charging_status = 'off'  (string)
  maemo.rechargeable.positive_rate = false  (bool)

Oviously, the corrects values are the ones from bme.

Hope it help ...

A++

PS : I have also posted same message here : http://talk.maemo.org/showpost.php?p...&postcount=799
This values are exported by HAL, not by my program/module, so I cannot change it. And it is correct, see specification battery.charge_level of HAL. BME has bad values (it use its own values which is not correct for HAL).

Do not create duplicate messages!!! (Remove duplicate from other threads!)

colin.stephane 2011-05-11 20:06
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by pali (Post 1004404)
This values are exported by HAL, not by my program/module, so I cannot change it. And it is correct, see specification battery.charge_level of HAL. BME has bad values (it use its own values which is not correct for HAL).

Do not create duplicate messages!!! (Remove duplicate from other threads!)
Ok, so let me give you more informations :

The values reported are BAD when fetched with the command (you can trust me on that) :

Code:

lshal -u /org/freedesktop/Hal/devices/computer_power_supply_battery_bq27200_0
How can you explain the 'battery.charge_level.percentage' reported as '0' in the example with a 25% charged battery properly reported by the other command :

Code:
lshal -u /org/freedesktop/Hal/devices/bme
Since I also use the 'battery' applet v0.4 you patched to reflect values from the backported driver, I can afirm the values are FALSE ...

Easy to verify step by step, if I modprobe -r bq27x00_battery then on the desktop, after some seconds for the applet refresh, the value revert back to the bme value and report properly 25% of battery available, if I modprobe the backported driver then, the applet refresh and show 0% of battery available ...

I have installed the v47 since you released it, and no problem until today.

So the question is : What I have made today ?

Answer, here is how I triggered this BUG :

I have a desktop battery charger, and yesterday night I have omitted to charge my N900, so this morning I have powered off the N900 because I have no more battery power and the device reported 2%.

Then I have replaced the battery by the one fully charged by my desktop charger some days ago, and during today the problem occur ...

Since the problem occur, the value reported for parameter 'battery.charge_level.percentage' is '0' and this is the value used by the applet 'battery' you patched ...

How can you explain, today, my applet reported 0% battery available during all the afternoon ?

It look like bme values reported take care of this scenario (changing physically the used battery by one fully charged) where the new driver does not ...

So there is really a bug when we fetch information from the backported driver ...

A++

pali 2011-05-11 20:24
Re: [Announce] kernel-power v47
 
As I wrote, I cannot change informations exported to HAL. HAL is userspace application which does not have anythink with my patches.

If you have problem with incorrect battery values, check first what kernel driver are reporting. It is in folder /sys/class/power_supply/bq27200-0 and in file uevent.

colin.stephane 2011-05-11 21:12
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by pali (Post 1004431)
As I wrote, I cannot change informations exported to HAL. HAL is userspace application which does not have anythink with my patches.

If you have problem with incorrect battery values, check first what kernel driver are reporting. It is in folder /sys/class/power_supply/bq27200-0 and in file uevent.
Well I don't understand why you ask me to check here :

Code:
-bash-2.05b# cat /sys/class/power_supply/bq27200-0/uevent
PHYSDEVPATH=/class/i2c-adapter/i2c-2/2-0055
PHYSDEVBUS=i2c
PHYSDEVDRIVER=bq27x00-battery
POWER_SUPPLY_NAME=bq27200-0
POWER_SUPPLY_TYPE=Battery
POWER_SUPPLY_STATUS=Charging
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_VOLTAGE_NOW=4103000
POWER_SUPPLY_CURRENT_NOW=-449463
POWER_SUPPLY_CAPACITY=47
POWER_SUPPLY_TEMP=323
POWER_SUPPLY_TIME_TO_EMPTY_NOW=0
POWER_SUPPLY_TIME_TO_EMPTY_AVG=0
POWER_SUPPLY_TIME_TO_FULL_NOW=9720
POWER_SUPPLY_TECHNOLOGY=Li-ion
POWER_SUPPLY_CHARGE_FULL=1531708
POWER_SUPPLY_CHARGE_NOW=715785
POWER_SUPPLY_CHARGE_FULL_DESIGN=2056320
Then, so ?

Correct me if I'm wrong ...

If I understand properly your patch at http://atrey.karlin.mff.cuni.cz/~pali/battery.patch

Code:
--- battery.c.orig        2011-01-17 13:39:36.000000000 +0100
+++ battery.c        2011-01-18 18:42:10.000000000 +0100
@@ -5,6 +5,7 @@
 #include <dbus/dbus.h>
 
 #include <stdio.h>
+#include <stdlib.h>
 
 #include <libhildondesktop/libhildondesktop.h>
 
@@ -55,7 +56,12 @@ static gboolean battery_plugin_on_timeou
        }
        else
        {
-                battery->percent = libhal_device_get_property_int(ctx, "/org/freedesktop/Hal/devices/bme", "battery.charge_level.percentage", NULL);
+                if ( libhal_device_property_exists(ctx, "/org/freedesktop/Hal/devices/computer_power_supply_battery_bq27200_0", "battery.charge_level.percentage", NULL) )
+                        battery->percent = libhal_device_get_property_int(ctx, "/org/freedesktop/Hal/devices/computer_power_supply_battery_bq27200_0", "battery.charge_level.percentage", NULL);
+                else if ( system("pgrep -f ^/usr/sbin/bme_RX-51") == 0 )
+                        battery->percent = libhal_device_get_property_int(ctx, "/org/freedesktop/Hal/devices/bme", "battery.charge_level.percentage", NULL);
+                else
+                        battery->percent = 0;
        }
       
        //GtkWidget *widget = GTK_WIDGET(data);
The patch say :

Code:
+                if ( libhal_device_property_exists(ctx, "/org/freedesktop/Hal/devices/computer_power_supply_battery_bq27200_0", "battery.charge_level.percentage", NULL) )
+                        battery->percent = libhal_device_get_property_int(ctx, "/org/freedesktop/Hal/devices/computer_power_supply_battery_bq27200_0", "battery.charge_level.percentage", NULL);
Translate in human language :

If Kernel module driver 'bq27x00_battery' IS loaded, then we can access '/org/freedesktop/Hal/devices/computer_power_supply_battery_bq27200_0' values and we use the value from the field 'battery.charge_level.percentage'.

After that :

Code:
+                else if ( system("pgrep -f ^/usr/sbin/bme_RX-51") == 0 )
+                        battery->percent = libhal_device_get_property_int(ctx, "/org/freedesktop/Hal/devices/bme", "battery.charge_level.percentage", NULL);
Translate in human language :

Else, Kernel module driver 'bq27x00_battery' IS NOT loaded, and we cannot access '/org/freedesktop/Hal/devices/computer_power_supply_battery_bq27200_0', so we check if bme IS loaded, and if so, then we can access '/org/freedesktop/Hal/devices/bme' values and we use the value from the field 'battery.charge_level.percentage'.

And finally :

Code:
+                else
+                        battery->percent = 0;
Translate in human language :

Else, we cannot access any parameters, so just report battery percent as '0%'

Do you agree with my analyze of your patch ?

If so, how can you explain that :

Code:
-bash-2.05b# lshal -u /org/freedesktop/Hal/devices/computer_power_supply_battery_bq27200_0 | grep battery.charge_level.percentage && lshal -u /org/freedesktop/Hal/devices/bme | grep battery.charge_level.percentage
  battery.charge_level.percentage = 56  (0x38)  (int)
  battery.charge_level.percentage = 95  (0x5f)  (int)
And what is your opinion about the right and the false value ???

You can trust me, the right is the one reported by bme !!!

A++

joerg_rw 2011-05-11 21:37
Re: [Announce] kernel-power v47
 
bq27x00.ko kernel module is deprecated as it breaks bme by exclusively occupying the I2C bus to that chip. BME otoh wants to access the chip directly, and so segfaults whenever bq27x00.ko is loaded.

Please keep this in mind

thanks
/jOERG

colin.stephane 2011-05-11 21:44
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by joerg_rw (Post 1004498)
bq27x00.ko kernel module is deprecated as it breaks bme by exclusively occupying the I2C bus to that chip. BME otoh wants to access the chip directly, and so segfaults whenever bq27x00.ko is loaded.

Please keep this in mind

thanks
/jOERG
Thanks, problem finally solved with this command line :

Code:
clear && ID=$(id -un) ; if [ ${ID} != "root" ] ; then echo "You are not 'root', please use this command line as 'root' ..." ; else echo "Ok, you are 'root' ..." ; if grep -q "blacklist bq27x00_battery" /etc/modprobe.d/blacklist 2>/dev/null ; then echo "Patch already applyed, nothing to be done ..." ; echo "" ; else echo "Applying patch now ..." ; echo "blacklist bq27x00_battery" >>/etc/modprobe.d/blacklist ; echo "" ; echo "DONE, PLEASE REBOOT YOUR DEVICE ..." ; echo "" ; fi ; fi
And rebooted ...

A++

kyros 2011-05-12 12:23
Re: [Announce] kernel-power v47
 
5 Attachment(s)
I have "Linux kernel for power users v.1:2.6.28-10power47" installed (additionally CSSU and multiboot-kernel-power v.0.3.1).
Since some days the system denies updating to "linux kernel for power users (boot image) 2.6.28.10" with showing the following screens:

Attachment 20036
Linux kernel for power users (boot image) 2.6.28.10 in order to be updated in the program manager

Attachment 20037
Error message that this is breaks the 3rd party package policiy

Attachment 20038
Program details summary

Attachment 20039
Program details description

Attachment 20040
Program details problem info

Does someone has an idea to solve the problem?
Regards, Kyros

petur 2011-05-12 13:53
Re: [Announce] kernel-power v47
 
Regarding my GPS/network location issue, possibly related to v47, I have split it to another thread:
http://talk.maemo.org/showthread.php...53#post1004853

Any hint/confirmation/... welcome!

EDIT: as one report of v46 + CSSU claims there is no problem, this probably rules out CSSU, meaning v47 has our attention :/

shardul 2011-05-12 14:25
Re: [Announce] kernel-power v47
 
How can we use uboot with kernel power 47v

Mentalist Traceur 2011-05-12 16:46
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by shardul (Post 1004906)
How can we use uboot with kernel power 47v
Take extracted zImage of the power47 kernel.
Convert zImage to uImage using mkimage.
Take the available for download uboot image that works on your hardware revision.
Use dd to write the kernel image to the end of the uboot image.
Flash this combined image.

Each of these directions can be found with actual detailed directions on this very forum.

elie-7 2011-05-12 20:37
Re: [Announce] kernel-power v47
 
i have to say that i'm now back to power v47, the battery seems to drain slower than v42 ! and as always v47's performance is just awesome, loving it so far .....

col37400 2011-05-12 21:05
Re: [Announce] kernel-power v47
 
Apologies if any of this is covered earlier in the thread - I can't read through 54 pages though.

I used to have the power kernel installed, but ran into conflicts with Fcamera and eventually had to reflash my device.

I'd like to get the power kernel back because my phone is pretty laggy without it, but I don't want to mess things up by installing an unstable version.

Can anyone tell me, is there a relatively stable version, that is compatible with Fcam, and if so where is it and how do I install it? The one in application manager comes up as "not installable" for me.

Thanks if anyone can help.

vi_ 2011-05-12 21:36
Re: [Announce] kernel-power v47
 
Don't quote me on this bro but I think the stable software is kept in the stable repository called 'extras'. You will also find the appropriate fcam driver there too.

lifenexus 2011-05-12 22:06
Re: [Announce] kernel-power v47
 
i have this audo issuse. it stuttering issue when playing music. its happens when cpu is at load and it didnt happen with power 46. i have cssu installed but so did i have it with 46 with no issue.

Mentalist Traceur 2011-05-12 22:56
Re: [Announce] kernel-power v47
 
fcam, blessN900, and power kernel do not conflict if you follow very basic instructions: After you change your kernel, reinstall all fcam-driver-using-programs (fcam, blessN900, etc).

misiak 2011-05-12 23:58
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by lifenexus (Post 1005196)
i have this audo issuse. it stuttering issue when playing music. its happens when cpu is at load and it didnt happen with power 46. i have cssu installed but so did i have it with 46 with no issue.
Could you tell us what does the output of
Code:
dpkg -s ogg-support
show? Well, the most important line is
Quote:
[...]
Version: 1.0.5
[...]
Does it say "1.0.5" or "1.0.7~rc1"? ;> If it does say "1.0.7~rc1" or "1.0.6~rc1", you should run:
Code:
root
apt-get install ogg-support=1.0.5
apt-get autoremove
And keep in mind that it is not kernel-related problem but ogg-support package related problem and has nothing to do with this kernel ;)

col37400 2011-05-13 00:44
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by vi_ (Post 1005175)
Don't quote me on this bro but I think the stable software is kept in the stable repository called 'extras'. You will also find the appropriate fcam driver there too.
In extras-testing there is "kernel-flasher-maemo" 2.6.28-maemo23

In the maemo.org catalogue there is
"Enhanced Linux kernel for power users" 2.6.28-maemo42
and
"Enhanced Linux kernel for power users (settings)" 0.11

All of these are "not installable" (conflicting application packages)

Am I missing something?

Estel 2011-05-13 00:45
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by vi_ (Post 1005175)
Don't quote me on this bro but I think the stable software is kept in the stable repository called 'extras'. You will also find the appropriate fcam driver there too.
Sorry for going into flamewar related area, but could You please stop bloating this thread with this crap? Personally, i respect (and even like) Your overall contribution to community on this forum, but since d*ckish russian roulette script, you create at least same amount of bloat as people unable to read entire topic for possible solution.

Rationale: extras-devel repository, keeping in mind all warnings about eating dogs taking wifes etc, is still supposed to be used and cross-tested for all kind of problems, then, reporting them.

I know that guys about battery temperature are most irritating, but Fcam drivers were reported SECOND time, and guy just excused in advance, that he was not able to read whole topic. Also, he asked for working combination of code versions, EXCLUDING extras-only (because kernel-power is in devel, so from start this question exclude "stick to extras" variant).

I feel little disgusted by explaining such basic things to intelligent person, especially that You know all of this already... In such a light, your post was totally useless, ignoring what user asked about. Also, it creates another useless post (mine), cause I'm sick of seeing Your ego-creative useless bloat again and again - and it is NOT less irritating that battery temp posts.

Thanks in advance and i hope that no offense taken.

// edit

Quote:
Originally Posted by col37400
In extras-testing there is "kernel-flasher-maemo" 2.6.28-maemo23

In the maemo.org catalogue there is
"Enhanced Linux kernel for power users" 2.6.28-maemo42
and
"Enhanced Linux kernel for power users (settings)" 0.11

All of these are "not installable" (conflicting application packages)

Am I missing something?
Yes, You're missing that vi_ post wasn't aimed at helping anyone. So bloat count caused by him increased +1 post above what i written here...

Kerlen-power v23 is still in testing just because former developer dropped it without any notice, and other package maintainers doesn't want to give maintainer rights to pali or anyone else. So, It's outdated as hell. Current version of kernel-power that can be considered "Stable" is v46, you can find it in devel.

Also, outside repositories, there is v46wl1 version, that incorporates bleeding-edge wifi drivers - allow to use packet injections, like aircrack-ng thing. The only difference is because injection drivers modules were added, so it's also stable.

Kernel-power from pali is v47 and it got wl1 things also, and its in extras-devel. You're encouraged to try it and report problems, but keep in mind all extras-devel warnings. Also, please search this thread before posting bug report - maybe this bug was already posted.

[Off-topic]
Thank You for Your question, cause because of this my post is not as useless as it was before, thanks to vi_...
[/Off-topic]

// edit 2

Quote:
Originally Posted by petur
Regarding my GPS/network location issue, possibly related to v47, I have split it to another thread:
http://talk.maemo.org/showthread.php...53#post1004853

Any hint/confirmation/... welcome!

EDIT: as one report of v46 + CSSU claims there is no problem, this probably rules out CSSU, meaning v47 has our attention :/
As we can read in topic linked by petur, this problem is already solved, and was unrelated to both CSSU and kernel-power (expired certificate of supl.google.com). Petur forget to edit his post after that, so i add it here - we can filter out gps thing from possible kernel-powerv47 problems.

lifenexus 2011-05-13 01:49
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by misiak (Post 1005233)
Could you tell us what does the output of
Code:
dpkg -s ogg-support
show? Well, the most important line is
Does it say "1.0.5" or "1.0.7~rc1"? ;> If it does say "1.0.7~rc1" or "1.0.6~rc1", you should run:
Code:
root
apt-get install ogg-support=1.0.5
apt-get autoremove
And keep in mind that it is not kernel-related problem but ogg-support package related problem and has nothing to do with this kernel ;)
oh yes it was 1.0.7rc 1. I downgraded with ur instructions. thanks a lot. coming to think of it, the problems occoured when thee was an update available for ogg support and i installed. thanks a lot. ill do some testing now

col37400 2011-05-13 02:22
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by Estel (Post 1005243)



Yes, You're missing that vi_ post wasn't aimed at helping anyone. So bloat count caused by him increased +1 post above what i written here...

Kerlen-power v23 is still in testing just because former developer dropped it without any notice, and other package maintainers doesn't want to give maintainer rights to pali or anyone else. So, It's outdated as hell. Current version of kernel-power that can be considered "Stable" is v46, you can find it in devel.

Also, outside repositories, there is v46wl1 version, that incorporates bleeding-edge wifi drivers - allow to use packet injections, like aircrack-ng thing. The only difference is because injection drivers modules were added, so it's also stable.

Kernel-power from pali is v47 and it got wl1 things also, and its in extras-devel. You're encouraged to try it and report problems, but keep in mind all extras-devel warnings. Also, please search this thread before posting bug report - maybe this bug was already posted.

[Off-topic]
Thank You for Your question, cause because of this my post is not as useless as it was before, thanks to vi_...
[/Off-topic]
I can't find v46 in extras-devel .... v47 is there, but if I try and install it, I just get an error message, saying it can't install because of conflicting application packages (kernel-modules-maemo and kernel-maemo).

Benson 2011-05-13 06:02
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by misiak (Post 1005233)
Could you tell us what does the output of
Code:
dpkg -s ogg-support
show? Well, the most important line is
Does it say "1.0.5" or "1.0.7~rc1"? ;> If it does say "1.0.7~rc1" or "1.0.6~rc1", you should run:
Code:
root
apt-get install ogg-support=1.0.5
apt-get autoremove
And keep in mind that it is not kernel-related problem but ogg-support package related problem and has nothing to do with this kernel ;)
It's actually an issue with gstreamer0.10-av, which was depended on by the new ogg-support.

And it was fixed days ago, so no need to revert.

And all this was already covered in this thread that everybody likes to post in, but nobody can be bothered to read.:mad:

Estel 2011-05-13 07:12
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by col37400 (Post 1005267)
I can't find v46 in extras-devel .... v47 is there, but if I try and install it, I just get an error message, saying it can't install because of conflicting application packages (kernel-modules-maemo and kernel-maemo).
Can't provide direct link, as now I'm @ area with low edge signal = searching take ages, but I'm absolutely sure that problem with conflicting packages was already mentioned few times in this thread, not so long ago (last 10 pages?) - please, search it for yourself

Also, You can force apt-get to install older version, which i discourage you to do, because v47 is HUGE step forward (new kernel version weren't released for a long time - because old maintainer disappeared - so pali implemented many upgrades in just +1 version number)

Good luck on searching

vi_ 2011-05-13 07:58
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by Estel (Post 1005243)
Sorry for going into flamewar related area, but could You please stop bloating this thread with this crap? Personally, i respect (and even like) Your overall contribution to community on this forum, but since d*ckish russian roulette script, you create at least same amount of bloat as people unable to read entire topic for possible solution.

Rationale: extras-devel repository, keeping in mind all warnings about eating dogs taking wifes etc, is still supposed to be used and cross-tested for all kind of problems, then, reporting them.

I know that guys about battery temperature are most irritating, but Fcam drivers were reported SECOND time, and guy just excused in advance, that he was not able to read whole topic. Also, he asked for working combination of code versions, EXCLUDING extras-only (because kernel-power is in devel, so from start this question exclude "stick to extras" variant).

I feel little disgusted by explaining such basic things to intelligent person, especially that You know all of this already... In such a light, your post was totally useless, ignoring what user asked about. Also, it creates another useless post (mine), cause I'm sick of seeing Your ego-creative useless bloat again and again - and it is NOT less irritating that battery temp posts.

Thanks in advance and i hope that no offense taken.

// edit



Yes, You're missing that vi_ post wasn't aimed at helping anyone. So bloat count caused by him increased +1 post above what i written here...

Kerlen-power v23 is still in testing just because former developer dropped it without any notice, and other package maintainers doesn't want to give maintainer rights to pali or anyone else. So, It's outdated as hell. Current version of kernel-power that can be considered "Stable" is v46, you can find it in devel.

Also, outside repositories, there is v46wl1 version, that incorporates bleeding-edge wifi drivers - allow to use packet injections, like aircrack-ng thing. The only difference is because injection drivers modules were added, so it's also stable.

Kernel-power from pali is v47 and it got wl1 things also, and its in extras-devel. You're encouraged to try it and report problems, but keep in mind all extras-devel warnings. Also, please search this thread before posting bug report - maybe this bug was already posted.

[Off-topic]
Thank You for Your question, cause because of this my post is not as useless as it was before, thanks to vi_...
[/Off-topic]

// edit 2



As we can read in topic linked by petur, this problem is already solved, and was unrelated to both CSSU and kernel-power (expired certificate of supl.google.com). Petur forget to edit his post after that, so i add it here - we can filter out gps thing from possible kernel-powerv47 problems.
My only regret is not posting an ash compliant script first time around.

Quote:
I feel little disgusted by explaining such basic things to intelligent person, especially that You know all of this already... In such a light, your post was totally useless, ignoring what user asked about. Also, it creates another useless post (mine), cause I'm sick of seeing Your ego-creative useless bloat again and again - and it is NOT less irritating that battery temp posts.
Are you on ****** drugs? You seem to attribute a great deal more information to the OP post than it contains. At which point did he state 'extras' only.


Quote:
Thanks in advance and i hope that no offense taken.
orly?

Estel 2011-05-13 14:18
Re: [Announce] kernel-power v47
 
He not stated that he want "extras only", but You "helped" him by suggesting to use "extras only".

Quote:
the stable software is kept in the stable repository called 'extras'. You will also find the appropriate fcam driver there too.
Nice statement, but totally not on-topic of the question he askes. Especially, that power-kernel on extras is VERY old now and totally unusable in pr1.3, due to mess with package maintaining.

Anyway, you EXACTLY know what i mean. If you only regret not making more people harm their devices by your "advises", I'm not going to continue this discussion - let mods judge on this. It's just sad that respected member like You can fall so low, literally under the bottom.

/Estel

mauron85 2011-05-13 14:29
Re: [Announce] kernel-power v47
 
Is it possible to multiboot with U-Boot?
As far I understand currently multiboot works that it always flashes selected kernel.

Reflektorfalke 2011-05-13 17:09
Re: [Announce] kernel-power v47
 
A couple of users already reported problems with bluetooth after upgrading to powerv47, but never got a response.

I am using updated openobex/obexd from this thread (also see wiki) for accessing N900 from my carkit.
Connecting to my carkit and dialling is still working, but the other day I noticed that sound is not transmitted anymore.

I am pretty sure this was introduced by powerv47.
Can someone please confirm that v47 includes some bluetooth related changes and what?
Maybe the relevant information will help the devs of obexd creating a new version that works with v47!?

freemangordon 2011-05-13 17:40
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by Reflektorfalke (Post 1005659)
A couple of users already reported problems with bluetooth after upgrading to powerv47, but never got a response.

I am using updated openobex/obexd from this thread (also see wiki) for accessing N900 from my carkit.
Connecting to my carkit and dialling is still working, but the other day I noticed that sound is not transmitted anymore.

I am pretty sure this was introduced by powerv47.
Can someone please confirm that v47 includes some bluetooth related changes and what?
Maybe the relevant information will help the devs of obexd creating a new version that works with v47!?
Yes, there is a patch for bluetooth system in KP46, it is for (lots of) bluetooth mice to work. What seems very strange for me is that all those reports appear last couple of weeks, KP46 was in extras-devel for about six months or so. Which kernel were you using before KP47?

Anyway, I am the author of the patch which is suspected to break compatibility with some BT audio devices. I will appreciate any information that will help me (or other kernel developers here) to produce a patch that will allow both mice and audio devices to coexist in peace. But please, there is a place to report bugs, throwing information in a thread with several hundred posts won't speed things up. I have already been PMed by retsaw and have his promise for a bug report when he has some information to share.

And I realy hope it is not the same situation where both KP and CSSU were blamed to break functionality because of gstreamer-av.

Reflektorfalke 2011-05-13 17:52
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by freemangordon (Post 1005672)
Yes, there is a patch for bluetooth system in KP46, it is for (lots of) bluetooth mice to work. What seems very strange for me is that all those reports appear last couple of weeks, KP46 was in extras-devel for about six months or so. Which kernel were you using before KP47?

Anyway, I am the author of the patch which is suspected to break compatibility with some BT audio devices. I will appreciate any information that will help me (or other kernel developers here) to produce a patch that will allow both mice and audio devices to coexist in peace. But please, there is a place to report bugs, throwing information in a thread with several hundred posts won't speed things up. I have already been PMed by retsaw and have his promise for a bug report when he has some information to share.

And I realy hope it is not the same situation where both KP and CSSU were blamed to break functionality because of gstreamer-av.
I was using v46 before and BT was working fine with my carkit.
Sorry, but I am no developer and canīt give you detailed information besides what can be found in the thread/wiki I mentioned...maybe those developers (e.g. mirakels) who created the updated obexd can give you more details.
I have also no idea where and how to create a bug report, sorry again.
I blamed neither KP nor CSSU to be the cause, just asking if it "might" be possible as I am pretty sure it broke with v47 update ;)

freemangordon 2011-05-13 18:11
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by Reflektorfalke (Post 1005680)
I was using v46 before and BT was working fine with my carkit.
Sorry, but I am no developer and canīt give you detailed information besides what can be found in the thread/wiki I mentioned...maybe those developers (e.g. mirakels) who created the updated obexd can give you more details.
I have also no idea where and how to create a bug report, sorry again.
I blamed neither KP nor CSSU to be the cause, just asking if it "might" be possible as I am pretty sure it broke with v47 update ;)
Follow bugtracker link here http://maemo.org/packages/view/kernel-power/ for bug reporting. And as bluetooth mice patch was existing in KP46, I am pretty sure that it is not the root of your problems. Which does not mean that some other patch in KP47 does not break thinks.

Mentalist Traceur 2011-05-14 03:42
Re: [Announce] kernel-power v47
 
Quote:
Originally Posted by mauron85 (Post 1005544)
Is it possible to multiboot with U-Boot?
As far I understand currently multiboot works that it always flashes selected kernel.
You can, but one of the kernels you include in Multiboot (or more than one, or all of them, depending on how often you want access to U-Boot) needs to have the u-boot image prepended to the kernel image.

Basically, you do the process you normally do to the kernel image to add u-boot to it, but repeat it on the kernel images that multiboot uses to reflash the kernel partition. (I don't vouch for the safety of u-boot being prepended to the NITDroid kernel, but everything I do know suggests it should be fine).

Anyway, what will happen is uboot will load first, and then when you tell it to keep loading the kernel, if you're booting with the keyboard out, it'll take you to the multiboot menu like normal.

If you neglect to include a u-boot+kernel kernel image as one of your kernels that multiboot has, however, once you switch kernels with multiboot you'll loose u-boot. As for how to actually replace multiboot's kernels... I'd say just take the zImage and do the u-boot attaching process as always (convert to uImage, append to u-boot image with dd); then rename to whatever multiboot wants you to name the kernels, and overwrite. I would think that's all you need to do...

teohhanhui 2011-05-14 07:12
Re: [Announce] kernel-power v47
 
I've been using v46 before this without issues, but on v47 with my phone plugged in for overnight charging the battery sometimes drains/stops charging at some point (perhaps after receiving a message). It's quite a serious problem to find your battery almost empty in the morning.


All times are GMT. The time now is 00:11.
Page 14 of 75 « First 41213 14 151624 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8