When I run hibernate(tuxonice) like this: hibernate -n -v3 Then I saw some error messages: ... hibernate: [97] Executing ChangeToSwsuspVT ... hibernate: [98] Executing CheckRunlevel ... hibernate: [98] Executing FullSpeedCPUSuspend ... Switched to performance, with min freq at 2000000 hibernate: [98] Executing Swsusp2ConfigSet ... hibernate: [99] Executing DoSwsusp2 ... hibernate: Not actually suspending (--no-suspend given) hibernate: [98] Executing FullSpeedCPUResume ... /tmp/tmp.hibernate.WCxY9Q: line 6: syntax error near unexpected token `>' /tmp/tmp.hibernate.WCxY9Q: line 6: `[ -f "/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed" ] && echo <unsupported> > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed' hibernate: [97] Executing ChangeFromSwsuspVT ... ... And I see there is a new release at www.tuxonice.net: hibernate-script-1.99 So please update hibernate-script ebuild with this new release.
About wwhich version of hibernate-script do we speak? Please prepend the summary with "category/ebuild-x.y" in future
sys-power/hibernate-script Right now, in portage tree, the highest version is 1.98.1. When I ran hibernate of this version, I could see some error messages(see above). A few days ago, I reported this bug to www.tuxonice.net, and Nigel Cunningham, the author, told me "The cpu frequency issue can be fixed by updating the hibernate script to version 1.99 (released last night)." So, I think we should update this new release (hibernate-script-1.99) into our portage tree.
1.99 version bump request together with ebuild is in bug #222113. 1.99 version is also only one which fully works with the current stable version of kernel: sys-kernel/tuxonice-sources-2.6.24-r9
(In reply to comment #3) > 1.99 version bump request together with ebuild is in bug #222113. > 1.99 version is also only one which fully works with the current stable version > of kernel: > sys-kernel/tuxonice-sources-2.6.24-r9 > Why does no body update the hibernate-script?
(In reply to comment #5) > (In reply to comment #3) > > 1.99 version bump request together with ebuild is in bug #222113. > > 1.99 version is also only one which fully works with the current stable version > > of kernel: > > sys-kernel/tuxonice-sources-2.6.24-r9 > > > Why does no body update the hibernate-script?(In reply to comment #5) > (In reply to comment #3) > > 1.99 version bump request together with ebuild is in bug #222113. > > 1.99 version is also only one which fully works with the current stable version > > of kernel: > > sys-kernel/tuxonice-sources-2.6.24-r9 > > > Why does no body update the hibernate-script? > I really can't understand why the assignnee (mobile@gentoo.org) hasn't yet become alive both here, and in bug 222113 too, by reporting on the issues that prevents her/him to make the job done. Does anyone know who we can give notice of the disappearing of this person? I mean, who is the manager (in the Gentoo's hierarchy) that could be contacted in order to reassign bugs when something like this fact happens?
The asignee "Mobile Herd" isn't actually a person, it's a herd of packages (like a herd of sheep, I guess) related to mobile computing. The maintainers are listed here: http://gentoo.org/proj/en/metastructure/herds/herds.xml#doc_chap74 (but don't email them personally, they already get mail by bugzilla). Alonbl, the former maintainer of this specific package, has unfortunately left Gentoo some time ago. I guess the adoption of this package isn't a high priority to the other maintainers of the mobile herd. The ebuild is actually available (see bug #222113), which is good enough reason to prioritize other things as long as manpower is short.
sys-power/hibernate-script Available versions: 1.97-r4 2.0-r1 {vim-syntax} Installed versions: 2.0-r1(23:20:24 01/08/2009)(-vim-syntax) Homepage: http://www.tuxonice.net/ Description: Hibernate script supporting multiple suspend methods Only available versions are 1.97-r4 and 2.0-r1. You should upgrade to 2.0-r1 (x86/amd64 stable) and report back. Mobile Herd, should this bug me CLOSEd ?
I have upgraded to 2.0-r1 and the bugs doesn't show anymore. I think the thread should be closed.
Yes, I have upgraded to 2.0 too, and this bug can be closed.
thanks for the feedback. sorry for the delay.
