Hello, amd64, Please add keyword also the dependency to dev-libs/libx86 Test scenario: 1. Compile your kernel with software suspend. 2. Merge this package. 3. Update /etc/suspend.conf and set resume device to your swap partition (If you don't use raw partition, please don't check this package, as you need more time to figure out how to do this). 4. Follow instructions at bug#156445 to build initramfs with suspend binary and modified linuxrc. 5. Merge hibernate-script 6. As root: # hibernate 7. Power on your computer an see if it resumes. Good luck!
amd64, someone must been using this... :)
sys-power/suspend has a dep on dev-libs/libx86 that fails to build with multilib-strict with the following error: >>> Install libx86-0.99 into /var/tmp/portage/dev-libs/libx86-0.99/image/ >>> category dev-libs install -D libx86.so.1 /var/tmp/portage/dev-libs/libx86-0.99/image//usr/lib/libx86.so.1 install -D libx86.a //var/tmp/portage/dev-libs/libx86-0.99/image//usr/lib/libx86.a ln -sf libx86.so.1 /var/tmp/portage/dev-libs/libx86-0.99/image//usr/lib/libx86.so install -D lrmi.h //var/tmp/portage/dev-libs/libx86-0.99/image//usr/include/libx86.h >>> Completed installing libx86-0.99 into >>> /var/tmp/portage/dev-libs/libx86-0.99/image/ strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment usr/lib/libx86.so.1 usr/lib/libx86.a removing executable bit: usr/lib/libx86.a Files matching a file type that is not allowed: usr/lib/libx86.so.1 * * ERROR: dev-libs/libx86-0.99 failed. * Call stack: * misc-functions.sh, line 566: Called install_qa_check * misc-functions.sh, line 342: Called die * * multilib-strict check failed! * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/dev-libs/libx86-0.99/temp/build.log'. * !!! install_qa_check failed; exiting.
(In reply to comment #2) > sys-power/suspend has a dep on dev-libs/libx86 that fails to build with > multilib-strict with the following error: Thanks! Fixed.
(In reply to comment #3) > (In reply to comment #2) > > sys-power/suspend has a dep on dev-libs/libx86 that fails to build with > > multilib-strict with the following error: > > Thanks! > Fixed. > I'll try tomorrow, as it's a bit late and I don't have time now :-/
What should I do if I don't use genkernel? I have never used genkernel (only first time I compiled my gentoo kernel)
In order to use suspend you must be able to know how to create initramfs. The best way to do so is using genkernel (bug#156445). However, you can try to use the create-resume-initrd.sh script which comes in the suspend tarball, I never checked it with Gentoo but the following command should be used: RESUME="/usr/lib/suspend/resume" \ CONFIG_FILE="/etc/suspend.conf" \ create-resume-initrd.sh It will create /boot/resume-initrd for you.
I get: ./create-resume-initrd.sh: line 38: [: argument expected But don't worry, maybe other amd64 user could help as also suspend has never worked for me on this machine (suspend or suspend2)
RESUME="/usr/lib/suspend/resume" \ CONFIG_FILE="/etc/suspend.conf" \ create-resume-initrd.sh your_resume_device Where your_resume_device should be your swap partition...
(In reply to comment #8) > RESUME="/usr/lib/suspend/resume" \ > CONFIG_FILE="/etc/suspend.conf" \ > create-resume-initrd.sh your_resume_device > > Where your_resume_device should be your swap partition... > OK, thanks, I run this and it created a /boot/resume-initrd file, but after hibernating, it didn't resume, it only boot like when system isn't halted properly My grub.conf has: title Gentoo Linux 2.6.23-gentoo root (hd0,0) kernel /boot/vmlinuz-2.6.23-gentoo root=/dev/sda1 vga=0x31B video=vesafb:mipal,ywrap,mtrr:3 oops=panic console=tty1 initrd /boot/resume-initrd My /etc/suspend.conf has: snapshot device = /dev/snapshot resume device = /dev/sda2 /dev/sda2 is my swap partition
You should have gotten somekind of messages during resume to help you know why it did not resume.
(In reply to comment #10) > You should have gotten somekind of messages during resume to help you know why > it did not resume. > I have checked the dmesg but nothing :-/
It goes into stdout... You will see nothing in dmesg.
(In reply to comment #12) > It goes into stdout... You will see nothing in dmesg. > Yes, but stout goes too fast for checking anything
we (ppc64) will add our keywords once a user requests it.
ppc64: I rewrote and maintain upstream's build system... It will be good to know if it at least compiles successfully at your installation. Don't add keyword, just tell me if all seems to be OK. Thanks!
it does not compile. in fact, it does not configure. checking for _FILE_OFFSET_BITS value needed for large files... no configure: error: Unsupported architecture
Thanks! Can you please attach config.log?
Created attachment 135980 [details] config.log as requested
Thanks! Do you use cross-compile in order to check this, or this is a native?
Created attachment 135991 [details] suspend-0.9_pre20071109-ppc64.patch Can you please try the following patch? Thanks!
ppc64: Can you please try to see if the patch at attachment#135991 [details] make it compile at your side? (Don't test, just compile). Thanks!
whoops.. sorry, I'm late. yes, this compiles now on ppc64. I think we are out here now. Please readd if I'm wrong.
compiles for ppc. I will add a keyword on user request. FIXed.
