Bugzilla Bug 146333

There has been small talk on gentoo-user about stabilising
suspend2-sources-2.6.17.  I've been using 2.6.17 evern since it made ~x86 up to
the current -r5, and I haven't had any issues with it yet.  I've used with and
without vesafb-tng, gensplash, radeonfb, suspend to disk, ati fglrx 8.28.8...

I have a Dell Inspiron 9100 laptop, ATI Mobility Radeon 9600.  Any more info I
can provide?

Created an attachment (id=96019) [details]
output from emerge --info

Still need to wait a bit, till I finished fixing/stabilizing
hibernate-script-1.93 (that's needed/recommended with >=2.6.17). Currently I'm
working on getting bug 146352 resolved, but its a bit hard since I can't
reproduce it.

(In reply to comment #2)
> Still need to wait a bit, till I finished fixing/stabilizing
> hibernate-script-1.93 (that's needed/recommended with >=2.6.17). Currently I'm
> working on getting bug 146352 resolved, but its a bit hard since I can't
> reproduce it.

OK, that helped. Just need to stabilize hibernate-script-1.93 before
suspend2-sources-2.6.17 will go stable too! (that means 30 days from today)

*** Bug 146352 has been marked as a duplicate of this bug. ***

Removing the DEPEND on 146352, as its fixed in the current patch tarball.
UPSTREAM agrees with me, that removing the dash-feature of hibernate-script is
the best solveable way.

Any chance of stabilizing 2.6.18 instead? I'd love to be able to use the
in-kernel ieee80211 stack (and no, I won't run unstable sources ... ;-).

(In reply to comment #6)
> Any chance of stabilizing 2.6.18 instead? I'd love to be able to use the
> in-kernel ieee80211 stack (and no, I won't run unstable sources ... ;-).
> 

You can try this "testing" version. You don't need to remove your old kernel
and I am using 2.6.18 sources without problems (and latest hibernate-script ;-)
also)

(In reply to comment #6)
> Any chance of stabilizing 2.6.18 instead? I'd love to be able to use the
> in-kernel ieee80211 stack (and no, I won't run unstable sources ... ;-).

let's leave 2.6.18 to it's own trial period! from the suspend2 list, there are
still various problems with it :)

What's the current status concerning the stabilization?
2006-10-26 had been the target date according to comment #3. :)

(In reply to comment #9)
> What's the current status concerning the stabilization?
> 2006-10-26 had been the target date according to comment #3. :)

Yup, I'm a slacker :)

Adding x86 for stabilization.

Closing, as the new target for stabilization is 2.6.18. New bug is 157584.