Suspend to RAM, what file would upload it? Because I have to force reboot push AC button. 2013/11/18 Greg KH :

On Sun, Nov 17, 2013 at 07:18:31PM +0000, Álvaro Castillo wrote:

...

Dear Factory mailing list.

Some weeks ago, I swtiched 12.3 into Tumbleweed repo. So I have a lot of system full upgraded. I was experimenting a very nice and stability system.

I have a one bug found. I cannot suspend my laptop HP-g6 2145ss with latest kernel. Only I can suspend with official kernel got of 12.3 repo is 3.7.10-1.16-desktop. I don't know why. kernel-desktop-3.11.6-33.1.gf7498bf.x86_64 and kernel-desktop-3.12.0-34.2.ge8fa6b4.x86_64 same bug.

Could help me please?

Suspend to disk or to RAM?

What is the failure? Care to file a bug for it?

thanks,

greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am Dienstag, 19. November 2013, 21:38:28 schrieb Greg KH:

Now that Tumbleweed is empty, please try out 13.1 and see if the issue is there or not. If it is, please file a bug at bugzilla.novell.com

Tumbleweed empty = Reset to 13.1? Then it is indeed still not a rolling release. :-( /Ax

Hello Greg, Am Mittwoch, 20. November 2013, 09:28:50 schrieben Sie:

...

...

Now that Tumbleweed is empty, please try out 13.1 and see if the issue is there or not. If it is, please file a bug at bugzilla.novell.com

Tumbleweed empty = Reset to 13.1? Then it is indeed still not a rolling release. :-(

It rolled forward to 13.1, which seems like the definition of a rolling release to me...

As long as Tumbleweed does not contain more actual packages than factory at release, resp. the newly released version, this is OK. But mostly this is the case, so we get a downgrade of most packages. I was using Tumbleweed on 12.1 (or was it 12.2?), and the release of a new version of openSUSE forced a downgrade of most packages, including several issues. So I went for a new installation, and kept away from Tumbleweed On the other hand, I would love to have an early stable upgrade, e.g. to come around the nasty suspend bug, that turns my laptop into an electrical heater (https://bugzilla.novell.com/show_bug.cgi?id=826945), which is still existing in the current kernel version of 12.3. But I feel the process on release change needs some tuning. If it works in the current version, I would be happy to hear. Cheers/Axel

Am Freitag, 22. November 2013, 09:29:31 schrieb Greg KH:

...

...

...

Tumbleweed empty = Reset to 13.1? Then it is indeed still not a rolling release. :-(

It rolled forward to 13.1, which seems like the definition of a rolling release to me...

As long as Tumbleweed does not contain more actual packages than factory at release, resp. the newly released version, this is OK. But mostly this is the case, so we get a downgrade of most packages.

I was using Tumbleweed on 12.1 (or was it 12.2?), and the release of a new version of openSUSE forced a downgrade of most packages, including several issues. So I went for a new installation, and kept away from Tumbleweed

"most" packages? What ones specifically? git and the kernel and vim were the only ones that I knew of that this happened to.

After nearly two years I cant remember anymore, sorry.

And it will continue to happen, as Tumbleweed does pick up newer versions for some packages than the "release" has in them, due to when the release is "frozen" in time. That's just how the build process goes.

And this is OK! But was probably not always the case, because the 'reset' to the older version of the release compared to the newer version of Tumbleweed caused the problem. So as long as the newer Tumbleweed packages compile against the updated (12.3 ->13.1) standard repository packages, but keep the newer Tumbleweed-release, then everything should be fine. Then we have a rolling release.

...

On the other hand, I would love to have an early stable upgrade, e.g. to come around the nasty suspend bug, that turns my laptop into an electrical heater (https://bugzilla.novell.com/show_bug.cgi?id=826945), which is still existing in the current kernel version of 12.3.

But I feel the process on release change needs some tuning. If it works in the current version, I would be happy to hear.

It works for me, specifics on how it doesn't work for you, or anyone else, would be appreciated.

Fine, I will give it a try! Thanks for your effort Axel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Sat, Nov 23, 2013 at 03:53:06PM +0000, Álvaro Castillo wrote:

I don't understand what is "rolling distro" concept here.

When you use Tumbleweed and openSUSE project launch new release. Should you *must* upgrade your system into new version such as 13.1?

It will automatically happen for you.

After you continue get Tumbleweed updates for that? Or you stay at 12.3 Tumbleweed for example, and get updates after 2-3 weeks ago with new updates? (As says Tumbleweed is empty now).

No, due to the "current" links, all should be fine, you will be running 13.1 now.

E.g: 12.3 -> Tumbleweed -> 13.1 -> Tumbleweed or 12.3 -> Tumbleweed -> Wait 2-3 weeks -> Continue Tumbleweed.

Nope: Tumbleweed -> Tumbleweed No need to "change" anything, if you leave your repos alone, you will get a constantly updating system, moving from 12.3 + additional updates to 13.1 + additional updates.

Maybe should improve openSUSE wiki section about Tumbleweed for everybody for understand better.

Suggestions, and even better, edits, are always welcome. greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

2013/11/24 Axel Braun :

Am Samstag, 23. November 2013, 15:53:06 schrieb Álvaro Castillo:

...

Anyway, I made a clean openSUSE 13.1 KDE's install and still continue problem. I reported bug into Novell's bugzilla for somebody can help me.

https://bugzilla.novell.com/show_bug.cgi?id=851873

Did you try systemctl suspend and report error messages? What does /var/log/pm-suspend.log report?

HTH Axel

Ok, Here it's a video of what's happend when I suspend to disk, or RAM. (I'm very worried more about RAM), but result of same, does not work. # pm-suspend -> http://www.youtube.com/watch?v=qnau7KDdYDU $ systemctl suspend Uses KDE's button to suspend. ----------- Laptop going to suspend, screen is off, AC LED going to set stand-by, laptop is suspended. ------------ Wake up proccess. Push Enter button or AC power button, fan is working, LEDs Wi-Fi, Uppercases, Ethernet.... works. Screen continues off. # pm-hibernate -> http://www.youtube.com/watch?v=7kM-AUBNIbg ------------ Laptop going to hibernate, screen is off, AC LED power does not off, laptop does not power off. All ways does not work. I installed old kernel of 12.3 (3.7.10-1.16-desktop.). That's works all suspend and hibernate. I think is a bug kernel because I tried a LiveDVD of Fedora 19 KDE with kernel kernel-3.11.6-200.fc19.x86_64 and does not work too. Should report to kernel.org Bugzilla? I've attached systemctl suspend. I found a possible bug on pm-powersave (?) log attached too.

2013/11/24 Carlos E. R. :

On 2013-11-24 16:28, Álvaro Castillo wrote:

...

Ok, Here it's a video of what's happend when I suspend to disk, or RAM. (I'm very worried more about RAM), but result of same, does not work.

Increase log verbosity and disable splash as I told you elsewhere.

I did that from you told me.

Greg KH writes:

Now that Tumbleweed is empty, please try out 13.1 and see if the issue is there or not. If it is, please file a bug at bugzilla.novell.com

Did I miss an announcement? Besides, it isn't really possible to do any upgrade at the moment with the recommended settings. These two already point to the 13.1 repo at the moment: http://download.opensuse.org/distribution/openSUSE-current/repo/non-oss/ http://download.opensuse.org/distribution/openSUSE-current/repo/oss/ While these four still point to 12.3 repos at the very moment: http://download.opensuse.org/update/openSUSE-current/ http://download.opensuse.org/update/openSUSE-non-oss-current/ http://download.opensuse.org/debug/distribution/openSUSE-current/repo/oss http://download.opensuse.org/debug/update/openSUSE-current This isn't your fault of course, but it would be nice if such inconsistencies weren't possible at all. In the same vein, I guess it would make sense if the Tumbleweed repo would have the same structure as the release it is tied to (i.e. Tumbleweed-12.3, Tumbleweed-13.1 and Tumbleweed-current pointing to the appropriate repo). That way the outgoing Tumbleweed could simply be frozen when the next one is ready for release and when the pointer switch is done on *-current the repo is already populated. BTW, how to find out if or when when these have been (re)built against the "new" Tumbleweed, respectively? http://download.opensuse.org/repositories/windows:/mingw:/win32/openSUSE_Tum... http://download.opensuse.org/repositories/LibreOffice%3a/Unstable/openSUSE_T... http://download.opensuse.org/repositories/science/openSUSE_Tumbleweed http://ftp.uni-erlangen.de/pub/mirrors/packman/suse/openSUSE_Tumbleweed/ Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Patrick Shanahan writes:

Appears you were caught in between, perhaps mirrors not completely updated as the last four url's for me point to 13.1 repos.

I have been looking at the website, I know that mirrors can take some time to update, but that's not the case here.

Some patience *is* required.

This doesn't have anything to do with patience or the lack of it. Changing the "current" links (all of them, at the same time) should be part of the release procedure, but apparently isn't. Like things are now, there is no real benefit from having these links since the fallback solution is to point to the individual version branches in each repository by editing the repo definitions again each time a release is done. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

…aaaaand: Tumbleweed is back with git & vim. That was quick! Thanks, Greg. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org