Active Topics

 


Reply
Thread Tools
Posts: 102 | Thanked: 9 times | Joined on Jul 2012 @ Istanbul TURKEY
#291
Originally Posted by reinob View Post
Who/what says "incompatible package". I don't think I've ever seen such a message on my N900.

Please post the exact output of what happens when you install the packages with dpkg.

You are using dpkg aren't you?
of course i'm using dpkg, don't panic boy! But when i installed via terminal, i couldn't boot my phone and reflashed again. Any of your brillant idea??
 
Posts: 203 | Thanked: 125 times | Joined on Jan 2011
#292
have u install with the right order?? kernel-power-flasher must be install last.
 

The Following User Says Thank You to hadjistyllis For This Useful Post:
Posts: 177 | Thanked: 152 times | Joined on Oct 2011
#293
Please install in this order
kernel-power
kernel-power modules
kernel-power flasher
kernel-power bootimg

correct me if I am wrong
 

The Following User Says Thank You to Sourav.dubey For This Useful Post:
int_ua's Avatar
Posts: 676 | Thanked: 1,067 times | Joined on Jul 2010 @ Kyiv, Ukraine
#294
Here are two oopslogs and the telepathy-ring core dump (can someone please forward it?) which (supposedly) led to them. I was on the street and was gonna receive sms and a phone call. Looks like they came simultaneously, maybe that's the problem. Or maybe it just turned off because it was cold, -10°C at most. But it booted afterwards.

Edit: attaching mtd2 on freemangordon's request.

kernel-config: http://pastebin.com/q8ye84aa

Edit 2: Bug tracker is readonly.
Attached Files
File Type: gz telepathy-oopslogs.tar.gz (210.3 KB, 84 views)
File Type: gz mtd2.tar.gz (27.0 KB, 84 views)

Last edited by int_ua; 2012-12-19 at 08:15.
 

The Following 8 Users Say Thank You to int_ua For This Useful Post:
int_ua's Avatar
Posts: 676 | Thanked: 1,067 times | Joined on Jul 2010 @ Kyiv, Ukraine
#295
Another two reboots in one day. This time reports extended with the syslog. I hope it doesn't contain any confidential info (looks like it includes GSM CellIDs, but it's just from the first glance, didn't have time to check). The second one is not kernel oops but reboot-32wd_to crash 0_o. Maybe it's hardware failures, after all?

At 22:22 I just closed Marble which was the only opened application. And at 00:32 IIRC I was playing with dpkg -S / dpkg -L / fileorphan.sh in terminal + a couple of windows in the background.

Edit: checking syslog, it looks like nothing there:
22:20:14kernel: [89844.591369] kb_lock (GPIO 113) is now closed
22:20:15 kernel: [89844.864715] kb_lock (GPIO 113) is now open
22:20:29 syslogd 1.5.0#5maemo7+0m5: restart.
...
00:29:00cellular: csd[824]: ISI_SMS .160766> incoming_cell_broadcast(): Incoming cell broadcast
00:29:03 cellular: csd[824]: ISI_SMS .553009> ind_reg_status(): Net registration (ind) status:1 rc:0
00:29:03 cellular: csd[824]: ISI_SMS .554199> set_timeout(): Timeout 3587 s event type:-1
00:30:28 syslogd 1.5.0#5maemo7+0m5: restart.
Attached Files
File Type: gz oopslog-and-reboot-crash-with-syslog.tar.gz (266.4 KB, 79 views)

Last edited by int_ua; 2012-12-20 at 13:34.
 

The Following 6 Users Say Thank You to int_ua For This Useful Post:
Posts: 102 | Thanked: 9 times | Joined on Jul 2012 @ Istanbul TURKEY
#296
Originally Posted by hadjistyllis View Post
have u install with the right order?? kernel-power-flasher must be install last.
of course. except for the flasher, i tried all the others. but it said shortly ''kernel-power-flasher first'' and i tried to install flasher, but then it said ''incompatible package''. don't understand why but this is the error that i got
sorry for my bad english, cause i can speak turkish and french...
 
Posts: 119 | Thanked: 24 times | Joined on Jun 2012
#297
when the Kernel-power version v51 (r1) push into extras..
 
Posts: 2,290 | Thanked: 4,134 times | Joined on Apr 2010 @ UK
#298
Originally Posted by viento23 View Post
when the Kernel-power version v51 (r1) push into extras..
I am not certain but from what I have read here it won't.
KP52 will be the next "extras" KP after it has past QA.
__________________

Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -


Before posting or starting a thread please try this.
 

The Following User Says Thank You to sixwheeledbeast For This Useful Post:
int_ua's Avatar
Posts: 676 | Thanked: 1,067 times | Joined on Jul 2010 @ Kyiv, Ukraine
#299
So, I reflashed. But after installing part of packages reboots continue. The first and yet only thing that crashed besides system rebooting is drlaunch widget and maybe hildon-desktop with it, but none of this triggered a core-dump creation, thus not really a crash. It just wiped all desktop widgets. It happened right after setting icon size to 60px, grid size to 8x4 and margins to 0. Also, I've changed transitions.ini radically in the same day before. Attached the oopses, dpkg selections, transitions.ini, drlaunch config.

Also, I have -devel enabled and I've done apt-get upgrade...
Attached Files
File Type: tar oops,selections,drlaunch_config,transitions.tar (200.0 KB, 72 views)

Last edited by int_ua; 2012-12-26 at 12:20.
 

The Following 5 Users Say Thank You to int_ua For This Useful Post:
int_ua's Avatar
Posts: 676 | Thanked: 1,067 times | Joined on Jul 2010 @ Kyiv, Ukraine
#300
Anyone else having sudden reboots?

How much does power consumtion change during WiFi authentication compared to the state right before? I was able to reproduce sudden reboot at will finally. By connecting/disconnecting to WiFi ~6 times in a row. Also it was at ~15% charge, maybe it's the battery failing. Right now I can't reproduce it and it's fully charged.

Also I've uninstalled drlaunch and changed transitions.ini less radically, only decreasing durations to 30.
Attached Files
File Type: tar oops_wifi_auth_deauth_many_times.tar (50.0 KB, 73 views)

Last edited by int_ua; 2012-12-27 at 17:23.
 

The Following 6 Users Say Thank You to int_ua For This Useful Post:
Reply

Tags
bq2415x_charger, bq27200, kernel-power


 
Forum Jump


All times are GMT. The time now is 09:03.