Upgrade to kernel 3.5 - s2ram does not work

English Install/Boot/Login
#1

After upgrade kernel fropm 3.4 to 3.5 command s2ram does not not work. It looks that there is a problem with the graphic driver - the card is GeForce 8600 GT, driver nouveau Gallium (7.11). The computer goes to sleep, but after wake-up it is frozen after while or after next command s2ram restarts.
Downgrade to 3.1 solved the problem.

#2

Humm, yet another problem with kernel 3.5 and Tumbleweed. In one case, two people have keyboard issues. In another a user seems to have memory issues causing a compile to fail and now a suspend to ram issue when using kernel 3.5 which might be related somehow to the second issue I mention. Of course, using kernel 3.1 can be OK, but you can use kernel 3.4.6 if you like, downloaded from kernel.org and compiled using my bash script SAKC you can find here: S.A.K.C. - SUSE Automated Kernel Compiler - Version 2.75 - Blogs - openSUSE Forums

Thank You,

#3

Thank you for your answer. I am only a common user - two perhaps stupid questions:

  1. Why there is not version 3.4.6 in TW repo? There is only 3.1 version.
  2. Is there possiblity use zypper dup without upgrading kernel? There will be new upgrades, but I do not want to upgrade kernel.
    Thanks.
#4

I guess if you locked your kernel version in Software Management, perhaps it would be left alone and if you set up YaST to allow multiple kernel versions, perhaps it would leave both, but zypper dup is intended to do a full distro version upgrade. And, there is no reason not to use the bash script SAKC and then fetch what ever kernel version you want to use.

Thank You,

#5

Thank you. I tried to edit zypp.conf
**
multiversion = provides:multiversion(kernel)

**as Nikos78 recommended, but I cannot see more versions of kernel. Regarding SAKC - it looks a bit dangerous for me. Anyway - version 3.1 works without problems, I will keep it until a new version of kernel is out.
**
**

#6

Adding in the “multiversion = provides:multiversion(kernel)” option after the problem popped up is like fixing the fence after the cows got out. It will prevent the losing of future kernel versions, but its too late to bring back the older one you already lost. As for SAKC, its very user friendly, just adds one more kernel to grub to select from and keeps your original kernel versions installed by YaST intact. SAKC has no automatic method to remove old kernels, but having an extra one or two does not cause any problems. In any event, if kernel 3.1 is working for you, then that is fine by me.

Thank You,

#7

Thanks for excellent explanation. I am busy now, but I would like to try SAKC in the near future. As far as I can remember, the older versions OpenSuse kept one older kernel in grub menu. When there is something new, I let you know. Sunshine keeps me out all day :slight_smile:

#8

Can you please subscribe to the Factory mail list and submit your problem as a question.

Greg (the maintainer of Tumbleweed and kernel developer) will respond to your problem.

#9

When I had a problem in the past, I submitted it to https://bugzilla.novell.com. What is better? I never used Factory mail list.

#10

I have just installed S.A.K.C. version of kernel 3.4.7-1.16, it was very long job… So far so good. s2ram works.

#11

Happy to hear that the new 3.4 kernel compiled with SAKC is working for you. I will keep my ears open for any info on memory issues and kernel 3.5.

Thank You,

#12

Thank you for S.A.K.C. There was only one problem - I am using non English version of OpenSuse, so I had to make new folders manually - Downloads etc. When there is an upgrade of kernel 3.5, I’ll try it.

#13

All expected folder names in SAKC are at the top of the bash script. You can modify these names before you use SAKC to be what ever you want. See below:

#
# Make Sure the Following Folder/File names are correct and exist!!!
#

#
# Where do you Keep/Download Your Kernel Source Files? This Folder Name Must Exist!
#
kernel_folder=$HOME/**Downloads**

#
# Where do you want to place your Compiled Kernels? This Folder Name Must Exist!
#
compile_folder=$HOME/**Kernel**

# Where do you want to place your Saved Configs? To be inside of compile_folder above 
# As in $compile_folder/$config_folder OR /home/username/Kernel/Configs by default 
#
config_folder=**Configs**

# Where is SAKC located and what is it called  (folder/name)
# Don't Like the name sakc?  Save it as anything you like, 
# but make sure this is the name/location that you used!
sakc_name=$HOME**/bin/sakc**

#
# Kernel Compile/Configuration Log File. Do you wish to save all information for viewing later?
#
log_file=true
log_file_location=$HOME/**Documents**

#
# Do You Wish SAKC to play a Sound When the Compile is complete? (true / false)
# play is included with the --> sox <-- application found in YaST
#
Play_Sound=true
wav_Player=/usr/bin/play
wav_File=/usr/share/sounds/alsa/test.wav

Change each name to something that exists and it will be used.

Thank You,

#14

Thanks for your explanation. The SAKC compilation is “time” consuming job. When I compile SAKC kernel once - may I install it later in “Yast” way? I mean to choose compiled SAKC version and make quick installation.

#15

Depending on your PC speed, doing a compile can take a while. There are several ways to get a newer kernel but SAKC compiles and installs it outside of YaST and so YaST will simply be unable to load or remove a kernel installed by SAKC. You would use SAKC to get kernel not found in any repository or to modify a kernel’s configuration not being done for you my default. It is just another option to get a kernel installed like you want, but like all things it has its good parts and its bad ones. On a slower machine kernel compiles can take a while, but I would assume you don’t need to compile a new kernel every day. I just start the kernel compile and go do something else while it is running.

Thank You,

#16

Thank you. It do not have to be Yast way. I think about possibility compiling several SAKC kernels (3.1, 3.4 and 3.5 for example) only once and then install any of them. Perhaps when I will install 3.5 version now, I will have in grub versions 3.1, 3.4 and 3.5?

#17

Yes, compiling three different versions will add three new selections in your grub menu. I give instructions on how to manually remove these if you need to. I have found that having more that 10 kernels installed can be a problem for the Grub Selection menu though I just normally use my fastboot bash utility which has no such problem. But again, having three extra is no problem just don’t go totally crazy and compile 10 different ones and before you say never, consider the security updates and basic fixes that comes out. Kernel 3.4 is up to the 7th fix since it was released. So, its not impossible to end up with 10 if your don’t watch it. If you need help in removing one you don’t want, just let me know. Here is a link to my fastboot script: FastBoot for Grub 2 or Grub Legacy Menu using Kexec - Version 2.13 - Blogs - openSUSE Forums

Thank You,

#18

OK, thank you. I removed 3.1, so I have now 3.4 and 3.5 for playing. When there is something new, I let you know.

#19

I installed nvidia driver several minutes ago, it looks that there is no problem with s2ram and kernel 3.5.0.36 i686.

#20

That is good news to hear vidmal. Not that you need to install it yet, but kernel 3.5.1 has been released and I installed it with S.A.K.C. and the nvidia 295.71 driver last night and all is working just fine.

Thank You,