Active Topics
| The Following 3 Users Say Thank You to iDont For This Useful Post: | ||
|
2011-08-23
, 22:59
|
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#112
|
I had a bug upgrading from busybox 1.18.5power3 to 1.19.0power2 (missed update to 1.19.0power1). History got stuck, not saving any changes, after the updates. I deleted /root/.ash_history and /home/user/.ash_history and the problem seems to be solved, just thought I'd throw out a heads-up to that effect.
|
|
2011-08-24
, 14:33
|
|
Posts: 268 |
Thanked: 1,053 times |
Joined on May 2010
@ The Netherlands
|
#113
|
Originally Posted by Mentalist Traceur
Thanks for the heads up!
I had a bug upgrading from busybox 1.18.5power3 to 1.19.0power2 (missed update to 1.19.0power1). History got stuck, not saving any changes, after the updates. I deleted /root/.ash_history and /home/user/.ash_history and the problem seems to be solved, just thought I'd throw out a heads-up to that effect.
I remember experiencing something similar to this too during development, but I can't seem to reproduce it now by:
- Removing all history files
- Downgrade to 1.18.5power3
- Type some commands (and verify that they're in the history file)
- Upgrade to 1.19.0power2
- Type some new commands
I'm also having an issue with swapoff with the busybox-power 1.19.0 series, which seems to be the result of a parsing error of the options passed to it. However, busybox-power doesn't touch (i.e. patch or otherwise modify) swapoff.c and getopt32.c of BusyBox. If possible, I'd like to receive some confirmation from another busybox-power user (one or two confirmations will suffice) whether swapoff works or not for him/her. If not, I'll dig deeper in this.
Update: it seems like something broke upstream: swapoff fails with the same message using vanilla source on my laptop too.
Second update: Fixed in busybox-power 1.19.0power3 by applying the hotfixes that'll eventually make up BusyBox 1.19.1.
Last edited by iDont; 2011-08-25 at 11:47.
| The Following 4 Users Say Thank You to iDont For This Useful Post: | ||
 |
|
2011-08-24
, 16:39
|
|
Posts: 185 |
Thanked: 111 times |
Joined on Jul 2010
@ Mexico DF, Mexico
|
#114
|
Originally Posted by iDont
Thanks, I didn't know what was that error related to. I hope it may be solved soon...
Thanks for the heads up!
I remember experiencing something similar to this too during development, but I can't seem to reproduce it now by:which resulted in the new commands being appended to the history file as they're supposed to be. I'd love to hear back from other people whether their history is/was stuck too. If so, I might push out 1.19.0power3 to unstuck the history by some postinst magic.
- Removing all history files
- Downgrade to 1.18.5power3
- Type some commands (and verify that they're in the history file)
- Upgrade to 1.19.0power2
- Type some new commands
I'm also having an issue with swapoff with the busybox-power 1.19.0 series, which seems to be the result of a parsing error of the options passed to it. However, busybox-power doesn't touch (i.e. patch or otherwise modify) swapoff.c and getopt32.c of BusyBox. If possible, I'd like to receive some confirmation from another busybox-power user (one or two confirmations will suffice) whether swapoff works or not for him/her. If not, I'll dig deeper in this.
Update: it seems like something broke upstream: swapoff fails with the same message using vanilla source on my laptop too. The bugreport can be found here. I don't need to receive confirmation anymore regarding swapoff in busybox-power.
__________________
Linux Registered User # 492214
http://counter.li.org/
------------------------
N900 registered as Linux Machine # 426325
Linux Registered User # 492214
http://counter.li.org/
------------------------
N900 registered as Linux Machine # 426325
|
|
2011-08-25
, 14:53
|
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#115
|
This might be relevant - I THINK I had two xterms open when updating busybox, so I suppose that could have something to do with it.
 |
|
2011-08-25
, 18:38
|
|
Posts: 723 |
Thanked: 519 times |
Joined on Nov 2010
@ Kuching:Malaysia
|
#116
|
i got a bug since i update to your latest update....my device fails to reboot properly...
if i use TC & choose "auto-reboot after saving setting" the device shutdown not reboot...when i run the reboot command on x-term it also fails to reboot properly....it just shutdown my device....
i suspected if it not this it might be related to kernel power v48 aswell...
if i use TC & choose "auto-reboot after saving setting" the device shutdown not reboot...when i run the reboot command on x-term it also fails to reboot properly....it just shutdown my device....
i suspected if it not this it might be related to kernel power v48 aswell...
__________________
My Phone Evolution : Nokia 3650-Nokia 6600-Nokia 6630-Motorola Rizr-Sony P1i-Nokia E63-Nokia X3-Samsung E980-Iphone 2G-Sony W595-Nokia E71-Nokia 5800-Nokia N900-HTC Hero-Xperia Mini Pro
My Phone Evolution : Nokia 3650-Nokia 6600-Nokia 6630-Motorola Rizr-Sony P1i-Nokia E63-Nokia X3-Samsung E980-Iphone 2G-Sony W595-Nokia E71-Nokia 5800-Nokia N900-HTC Hero-Xperia Mini Pro
 |
|
2011-08-26
, 04:23
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#117
|
I got no problems with manual reboot, using bot latest busybox-power and kp48.
Ho ever, other strange problems is showing up, which may be related to busybox-power *or* kp48. Could You guys please open xterm, gain root via "root", then
leafpad /usr/bin/whateveronescript_in_that_location
... then try "save as"?
In my case, it result in spontaneous reboot all the time. Furthermore, calling upon leafpad after "sudo gainroot" - instead of "root" and trying to "save as" result in leafpad crashing with "Segmentation fault" output in xterm (this time, without rebooting N900).
As odd it may sound, I'm pretty sure that this started after busybox power "big update" OR KP48. Most likely the latter, but I'm reporting here "just in case".
Also, it's possible that people with R&D mode enabled, won't experience this problem - it may be some watchdog reaction. Mentalist, I'm looking at You
Ho ever, other strange problems is showing up, which may be related to busybox-power *or* kp48. Could You guys please open xterm, gain root via "root", then
leafpad /usr/bin/whateveronescript_in_that_location
... then try "save as"?
In my case, it result in spontaneous reboot all the time. Furthermore, calling upon leafpad after "sudo gainroot" - instead of "root" and trying to "save as" result in leafpad crashing with "Segmentation fault" output in xterm (this time, without rebooting N900).
As odd it may sound, I'm pretty sure that this started after busybox power "big update" OR KP48. Most likely the latter, but I'm reporting here "just in case".
Also, it's possible that people with R&D mode enabled, won't experience this problem - it may be some watchdog reaction. Mentalist, I'm looking at You
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
| The Following 2 Users Say Thank You to Estel For This Useful Post: | ||
 |
|
2011-08-26
, 06:50
|
|
Posts: 323 |
Thanked: 189 times |
Joined on Oct 2010
@ Brazil
|
#118
|
Originally Posted by pusak gaoq
This is a Kernel Power related problem. There are at least 2 threads about this kernel power problem.
i got a bug since i update to your latest update....my device fails to reboot properly...
if i use TC & choose "auto-reboot after saving setting" the device shutdown not reboot...when i run the reboot command on x-term it also fails to reboot properly....it just shutdown my device....
i suspected if it not this it might be related to kernel power v48 aswell...
http://talk.maemo.org/showthread.php?t=71127
http://talk.maemo.org/showthread.php?t=72002
May I ask if you have the PS3 Sixaxis installed too? May seem random, but I'm just curious.
__________________
Love and Goodness are not a property. Are not a franchising. They are present in each one of us, and must be cultivated with KNOWLEDGE.
Love and Goodness are not a property. Are not a franchising. They are present in each one of us, and must be cultivated with KNOWLEDGE.
| The Following 3 Users Say Thank You to Temporal For This Useful Post: | ||
|
|
2011-08-26
, 19:29
|
|
Posts: 268 |
Thanked: 1,053 times |
Joined on May 2010
@ The Netherlands
|
#119
|
Originally Posted by strange1712
In case you've missed the last edit of my previous post: it's fixed in the latest busybox-power
Thanks, I didn't know what was that error related to. I hope it may be solved soon...
Originally Posted by Mentalist Traceur
Hmm, I tried reproducing the stuck history the same way as before, only now with multiple xterms open while upgrading (both root and non-root): same result, the history didn't got stuck. No clues yet :-/
This might be relevant - I THINK I had two xterms open when updating busybox, so I suppose that could have something to do with it.
Originally Posted by Estel
I'm experiencing what you just described with my own KP48-derived kernel too. After downgrading busybox-power to 1.18.5power3 the issue persisted, so at the moment I'm leaning towards kernel-power as being the source of the issue. This post seems to support that.
In my case, it result in spontaneous reboot all the time. Furthermore, calling upon leafpad after "sudo gainroot" - instead of "root" and trying to "save as" result in leafpad crashing with "Segmentation fault" output in xterm (this time, without rebooting N900).
As odd it may sound, I'm pretty sure that this started after busybox power "big update" OR KP48. Most likely the latter, but I'm reporting here "just in case".
I must add that I haven't tried your scenario with a pre-KP48 kernel
| The Following 2 Users Say Thank You to iDont For This Useful Post: | ||
|
|
2011-08-26
, 20:42
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#120
|
No PS3 sixaxis here, but it's now 99% sure, that it's kp48 related. Thanks for quick answers and tracing!
Last edited by Estel; 2011-08-26 at 20:44.
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
Last edited by Estel; 2011-08-26 at 20:44.
I apparently forgot to enable ipv6 support in the config file of busybox_root. Expect a fixed v1.19.0power2 to hit the repositories soon