-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have not forgotten about your kernel, but I do think I have figured out the source of our grief.
Basically, I build a new kernel and it works great, for a little while. Then at some point it stops responding on resume. Well after a lot of trial and error, I think I have the problem pinpointed. For me, the problems appear after I install the vmware kernel modules. Since I don't use VMware all that often, it would take days before I would get around to configuring it for use with the new kernel. I am pretty sure I saw a video of you using vmware on your blog and I suspect that this is your problem as well. As a work around stop your vmware services with the following command: /etc/init.d/vmware stop before suspending your laptop. Even better, prevent vmware from starting automatically at boot with the following: update-rc.d -f vmware remove When you need to use vmware, just start it up with sudo or as root: /etc/init.d/vmware start The init.d script will also add/remove the loaded kernel modules, which is where I suspect the problem is (death to binary only modules). This has been working good for me today, as I have suspended and resumed several times throughout the day. Let me know how this works. Cheers, - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEkPpswRXgH3rKGfMRAiLgAJ0eyksL4qCvwp5heb+DG22pZJNGCgCgoMfv WDqsdgN/67Ni8vYsc95P1vM= =NClB -----END PGP SIGNATURE----- _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
