Problem with suspend and hibernate in opensuse 11.0

English Applications
1

I have a problem with suspend/hibernate. It freeze after 1/6th of the suspend/hibernate splash bar. I don’t have this problem with openSUSE 10.2 and openSUSE 10.3. I have tried methods i found from other but it doesn’t work. It did work after updating and adding some configuration. But now it’s not working again. Now i’m not sure where too look to fix it.

This is my last /var/log/pm-suspend.log:
Mon Aug 18 10:21:15 WIT 2008: running hibernate hooks.
===== Mon Aug 18 10:21:15 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/00clear =====
===== Mon Aug 18 10:21:15 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/01logging =====
hibernate initiated: Mon Aug 18 10:21:15 WIT 2008

Module Size Used by
nfs 266580 1
lockd 72184 2 nfs
nfs_acl 7680 1 nfs
sunrpc 197244 11 nfs,lockd,nfs_acl
ip6t_LOG 11140 9
xt_tcpudp 7296 25
xt_pkttype 6016 4
ipt_LOG 10500 14
xt_limit 6788 23
microcode 15888 0
firmware_class 13696 1 microcode
binfmt_misc 15752 1
autofs4 25988 0
af_packet 26368 2
snd_seq_dummy 7940 0
snd_seq_oss 38684 0
snd_seq_midi_event 11648 1 snd_seq_oss
snd_pcm_oss 52096 0
snd_mixer_oss 21120 1 snd_pcm_oss
snd_seq 61376 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 12812 3 snd_seq_dummy,snd_seq_oss,snd_seq
ip6t_REJECT 9088 3
nf_conntrack_ipv6 21240 4
ipt_REJECT 8064 3
xt_state 6656 12
iptable_mangle 7424 0
iptable_nat 11400 0
nf_nat 23448 1 iptable_nat
iptable_filter 7552 1
ip6table_mangle 7296 0
nf_conntrack_netbios_ns 6912 0
nf_conntrack_ipv4 15364 11 iptable_nat,nf_nat
nf_conntrack 66900 6 nf_conntrack_ipv6,xt_state,iptable_nat,nf_nat,nf_conntrack_netbios_ns,nf_conntrack_ipv4
ip_tables 17936 3 iptable_mangle,iptable_nat,iptable_filter
ip6table_filter 7424 1
ip6_tables 19088 3 ip6t_LOG,ip6table_mangle,ip6table_filter
x_tables 21380 11 ip6t_LOG,xt_tcpudp,xt_pkttype,ipt_LOG,xt_limit,ip6t_REJECT,ipt_REJECT,xt_state,iptable_nat,ip_tables,ip6_tables
ipv6 269160 25 ip6t_REJECT,nf_conntrack_ipv6,ip6table_mangle
fuse 54044 5
loop 23044 0
dm_mod 66388 0
via_chrome9 26628 0
drm 80152 1 via_chrome9
snd_hda_intel 374172 3
snd_pcm 87812 2 snd_pcm_oss,snd_hda_intel
snd_timer 28424 2 snd_seq,snd_pcm
rtc_cmos 14752 0
snd_page_alloc 14984 2 snd_hda_intel,snd_pcm
snd_hwdep 14084 1 snd_hda_intel
rtc_core 24860 1 rtc_cmos
rtc_lib 7040 1 rtc_core
snd 67256 16 snd_seq_dummy,snd_seq_oss,snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_pcm,snd_timer,snd_hwdep
soundcore 11976 1 snd
video 27024 0
output 7936 1 video
sdhci 21388 0
joydev 15936 0
mmc_core 53276 1 sdhci
wmi 12200 0
ac 10628 0
battery 18820 0
shpchp 37908 0
i2c_viapro 12820 0
sr_mod 21032 0
via_agp 13568 1
button 13072 0
pci_hotplug 33828 1 shpchp
i2c_core 28820 1 i2c_viapro
cdrom 38300 1 sr_mod
via_rhine 29192 0
mii 9600 1 via_rhine
serio_raw 11140 0
agpgart 35636 2 drm,via_agp
sg 39732 0
ehci_hcd 39436 0
uhci_hcd 28432 0
usbcore 152140 3 ehci_hcd,uhci_hcd
sd_mod 32920 4
edd 14152 0
ext3 143624 2
mbcache 13060 1 ext3
jbd 61216 1 ext3
fan 10372 0
sata_via 15492 3
pata_via 15492 0
libata 164188 2 sata_via,pata_via
scsi_mod 156020 4 sr_mod,sg,sd_mod,libata
dock 15248 1 libata
thermal 28060 0
processor 53552 1 thermal

         total       used       free     shared    buffers     cached

Mem: 773392 495200 278192 0 24580 295292
-/+ buffers/cache: 175328 598064
Swap: 2104504 0 2104504

===== Mon Aug 18 10:21:15 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/05led =====
===== Mon Aug 18 10:21:15 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/06autofs =====
Shutting down automount …done
===== Mon Aug 18 10:21:15 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/10NetworkManager =====
===== Mon Aug 18 10:21:15 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/20reset-bluetooth =====
===== Mon Aug 18 10:21:16 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/30s2disk-check =====
INFO: checking for suspend-to-disk prerequisites…
using userspace suspend method
setting resume device to /dev/sda2
setting image size to 356379033
adding these parameters from /etc/suspend.conf:
shutdown method = reboot
===== Mon Aug 18 10:21:16 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/45pcmcia =====
ejecting PCMCIA cards…
===== Mon Aug 18 10:21:16 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/50modules =====
===== Mon Aug 18 10:21:16 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/55battery =====
===== Mon Aug 18 10:21:16 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/80acpi-fan =====
===== Mon Aug 18 10:21:16 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/80videobios =====
===== Mon Aug 18 10:21:16 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/94cpufreq =====
===== Mon Aug 18 10:21:16 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/95led =====
===== Mon Aug 18 10:21:16 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/95packagekit =====
===== Mon Aug 18 10:21:16 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/99Zgrub =====
INFO: running prepare-grub
Skipping grub entry #1, because it has the noresume option
Skipping grub entry #3, because it has the noresume option
running kernel is grub menu entry 0 (vmlinuz-2.6.25.11-0.1-default)
preparing boot-loader: selecting entry 0, kernel /boot/2.6.25.11-0.1-default
grub-once: saving original /boot/grub/default
running ‘/usr/sbin/grubonce 0’
Using entry #0: openSUSE 11.0 - 2.6.25.11-0.1 (default)
time needed for sync: 1.3 seconds, time needed for grub: 0.0 seconds.
===== Mon Aug 18 10:21:17 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/99info =====
Mon Aug 18 10:21:17 WIT 2008: done running hibernate hooks.

  • /usr/sbin/s2disk --config /var/lib/s2disk.conf

Is there anyone who can help me?

2

According your log file the hibernate process is going correctly… May you, please, also post here your ‘/etc/suspend.conf’ and ‘/var/lib/s2disk.conf’ files. Seems you forced ‘reboot’ shutdown method and probably it’s not exactly what you expected…

Rgds,
-dim

3

I’ve made another test this morning. I cleared out all my mess in all the places that i remembered. I hope this time we can spot something. It just stuck there with nothing else after s2disk. Is there any thing we could do to know what goes after s2disk?

/etc/suspend.conf:
#############################################################################

note:

using pm-utils or powersaved, this file (/etc/suspend.conf) only serves as

a template, image_size and resume_device are filled in dynamically

and the generated /var/lib/s2disk.conf is used to suspend.

If you enter stuff here, it will be copied to that file unchanged,

but this might skip some features and sanity checks.

#############################################################################

your snapshot device. You should not need to change this.

snapshot device = /dev/snapshot

enter your swap device here. Read the warning on pm-utils above, please!

#resume device = <path_to_resume_device_file>

image size will also be filled in by pm-utils

#image size = 350000000
#image size = 2147483648

#suspend loglevel = 2
#max loglevel = 2

compute checksum will slow down suspend and resume.

Debugging option, default n

#compute checksum = y

compression will often speed up suspend and resume (default y)

#compress = n

encryption support is rather basic right now - e.g. USB keyboards will not

work to enter the key in the standard initrd, also beware of

non-US keyboard layouts. Only use this if you know what you are doing.

#encrypt = n

RSA key file that is used for encryption

#RSA key file = /etc/suspend.key

start writing out the image early, before buffers are full.

will most of the time speed up overall writing time (default y)

#early writeout = n

use splash picture? (default y)

#splash = y

shutdown method:

platform - go through ACPI BIOS to power off the machine (default on

machines that support it)

shutdown - just power off like after a shutdown

reboot - reboot instead of powering off. For debugging only.

#shutdown method = platform
#shutdown method = shutdown
#shutdown method = reboot

resume offset: for use with swapfiles, use “swap-offset” to find out.

#resume offset = 12345

pause after resume for n seconds, so that the timing information can

actually be read (default 0 => don’t pause)

#resume pause = 2

/etc/pm/config.d/hibernate.conf:

Syntax: HIBERNATE_METHOD={userspace|kernel}

#HIBERNATE_METHOD=kernel

/var/lib/s2disk.conf:
resume device = /dev/sda2
image size = 356379033

parameters taken from /etc/suspend.conf:

/var/log/pm-suspend.log:
Fri Aug 22 08:02:23 WIT 2008: running hibernate hooks.
===== Fri Aug 22 08:02:23 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/00clear =====
===== Fri Aug 22 08:02:23 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/01logging =====
hibernate initiated: Fri Aug 22 08:02:23 WIT 2008

Module Size Used by
ip6t_LOG 11140 9
xt_tcpudp 7296 25
xt_pkttype 6016 4
ipt_LOG 10500 14
xt_limit 6788 23
binfmt_misc 15752 1
autofs4 25988 0
snd_seq_dummy 7940 0
snd_seq_oss 38684 0
snd_seq_midi_event 11648 1 snd_seq_oss
snd_pcm_oss 52096 0
af_packet 26368 2
snd_mixer_oss 21120 1 snd_pcm_oss
snd_seq 61376 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 12812 3 snd_seq_dummy,snd_seq_oss,snd_seq
ip6t_REJECT 9088 3
nf_conntrack_ipv6 21240 4
ipt_REJECT 8064 3
xt_state 6656 12
iptable_mangle 7424 0
iptable_nat 11400 0
nf_nat 23448 1 iptable_nat
iptable_filter 7552 1
ip6table_mangle 7296 0
nf_conntrack_netbios_ns 6912 0
nf_conntrack_ipv4 15364 11 iptable_nat,nf_nat
nf_conntrack 66900 6 nf_conntrack_ipv6,xt_state,iptable_nat,nf_nat,nf_conntrack_netbios_ns,nf_conntrack_ipv4
ip_tables 17936 3 iptable_mangle,iptable_nat,iptable_filter
ip6table_filter 7424 1
ip6_tables 19088 3 ip6t_LOG,ip6table_mangle,ip6table_filter
x_tables 21380 11 ip6t_LOG,xt_tcpudp,xt_pkttype,ipt_LOG,xt_limit,ip6t_REJECT,ipt_REJECT,xt_state,iptable_nat,ip_tables,ip6_tables
ipv6 269160 25 ip6t_REJECT,nf_conntrack_ipv6,ip6table_mangle
microcode 15888 0
firmware_class 13696 1 microcode
fuse 54044 5
loop 23044 0
dm_mod 66388 0
via_chrome9 26628 0
drm 80152 1 via_chrome9
rtc_cmos 14752 0
rtc_core 24860 1 rtc_cmos
rtc_lib 7040 1 rtc_core
snd_hda_intel 374172 1
snd_pcm 87812 2 snd_pcm_oss,snd_hda_intel
snd_timer 28424 2 snd_seq,snd_pcm
snd_page_alloc 14984 2 snd_hda_intel,snd_pcm
joydev 15936 0
snd_hwdep 14084 1 snd_hda_intel
serio_raw 11140 0
snd 67256 12 snd_seq_dummy,snd_seq_oss,snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_pcm,snd_timer,snd_hwdep
soundcore 11976 1 snd
video 27024 0
sdhci 21388 0
output 7936 1 video
mmc_core 53276 1 sdhci
wmi 12200 0
via_rhine 29192 0
battery 18820 0
shpchp 37908 0
via_agp 13568 1
ac 10628 0
i2c_viapro 12820 0
mii 9600 1 via_rhine
button 13072 0
sr_mod 21032 0
agpgart 35636 2 drm,via_agp
cdrom 38300 1 sr_mod
pci_hotplug 33828 1 shpchp
i2c_core 28820 1 i2c_viapro
sg 39732 0
ehci_hcd 39436 0
uhci_hcd 28432 0
usbcore 152140 3 ehci_hcd,uhci_hcd
sd_mod 32920 4
edd 14152 0
ext3 143624 2
mbcache 13060 1 ext3
jbd 61216 1 ext3
fan 10372 0
sata_via 15492 3
pata_via 15492 0
libata 164188 2 sata_via,pata_via
scsi_mod 156020 4 sr_mod,sg,sd_mod,libata
dock 15248 1 libata
thermal 28060 0
processor 53552 1 thermal

         total       used       free     shared    buffers     cached

Mem: 773392 524620 248772 0 31068 299352
-/+ buffers/cache: 194200 579192
Swap: 2104504 0 2104504

===== Fri Aug 22 08:02:23 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/05led =====
===== Fri Aug 22 08:02:23 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/06autofs =====
Shutting down automount …done
===== Fri Aug 22 08:02:23 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/10NetworkManager =====
===== Fri Aug 22 08:02:23 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/20reset-bluetooth =====
===== Fri Aug 22 08:02:23 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/30s2disk-check =====
INFO: checking for suspend-to-disk prerequisites…
using userspace suspend method
setting resume device to /dev/sda2
setting image size to 356379033
adding these parameters from /etc/suspend.conf:
===== Fri Aug 22 08:02:23 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/45pcmcia =====
ejecting PCMCIA cards…
===== Fri Aug 22 08:02:23 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/50modules =====
===== Fri Aug 22 08:02:23 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/55battery =====
===== Fri Aug 22 08:02:23 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/80acpi-fan =====
===== Fri Aug 22 08:02:23 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/80videobios =====
===== Fri Aug 22 08:02:23 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/94cpufreq =====
===== Fri Aug 22 08:02:23 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/95led =====
===== Fri Aug 22 08:02:24 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/95packagekit =====
===== Fri Aug 22 08:02:24 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/99Zgrub =====
INFO: running prepare-grub
Skipping grub entry #1, because it has the noresume option
Skipping grub entry #3, because it has the noresume option
running kernel is grub menu entry 0 (vmlinuz-2.6.25.11-0.1-default)
preparing boot-loader: selecting entry 0, kernel /boot/2.6.25.11-0.1-default
grub-once: saving original /boot/grub/default
running ‘/usr/sbin/grubonce 0’
Using entry #0: openSUSE 11.0 - 2.6.25.11-0.1 (default)
time needed for sync: 1.3 seconds, time needed for grub: 0.0 seconds.
===== Fri Aug 22 08:02:25 WIT 2008: running hook: /usr/lib/pm-utils/sleep.d/99info =====
Fri Aug 22 08:02:25 WIT 2008: done running hibernate hooks.

  • /usr/sbin/s2disk --config /var/lib/s2disk.conf
4

Did you put any configuration file in “/etc/pm/config.d”? If you did let us know what code you put in there. Is your computer in the whilelist? Its not clear to me. And also let us know hardware configuration of your system.

5

It’s quite strange: your hibernate process is going well and seems to freeze on ‘s2disk’ (if your log file is complete)… And it’s strange because s2disk process is quite straightforward - it should just work (and works on all laptops I have around, even very old or very new)…

But seems you’re not alone as there is even a wiki article about: Suspend to disk tips - openSUSE

So, may you try ‘kernel’ hibernate method?
(set via ‘/usr/lib/pm-utils/defaults’)

Rgds,
-dim

6

I’ve tried that, it doesn’t work. I’ve tried the ‘kernel’ and ‘userspace’ mode, looks different but still stuck.

I didn’t change here:
/usr/lib/pm-utils/defaults

But here instead:
/etc/pm/config.d/hibernate.conf
/etc/pm/sleep.d/hibernate.conf

But i’ve made progress by doing regression. I install/downgrade kernel packs from openSUSE 10.3, and it works, suspend and hibernate.

Xv, ALSA, Banshee aren’t working correctly after resume. Other applications looks fine. I also can not have suspend/resume splash screen.

I can only use ‘kernel’ method though. ‘userspace’ method didn’t work well when resuming. It continues to normal boot after finish resuming instead of going directly to screen lock like the ‘kernel’ method.

> uname -r
2.6.22.5-31-default

Now what? report bug? join alpha, beta openSUSE 11.1 test?

7

Find string ‘/etc/pm/config.d’ using your browser in this page, it’s there.

I don’t think it’s in the whitelist. I’m using via P4M900, Clevo M541SE. Where is this whitelist?

8

Seems there are people fixed their s2disk problems by upgrading to the 2.6.26 kernel, and if it worked correctly for you with Suse 10.3 - probably it’s mostly kernel problem rather hardware.

Rgds,
-dim

9

Can you tell me where can i get 2.6.26 kernel? I found 2.6.27 but i feel the repo isn’t solid. Is it an rpm? Not src rpm and not a tarball, right?

10

Some time ago I saved in bookmarks this link posted in Suse forums: How to compile your own linux kernel for openSUSE « Snakeeyes Weblog

And seems the guy started with 2.6.26 kernel and finished with 2.6.27 (according last quotes). This blog record gives an excellent overview of all may happens to you during new kernel install, as well an true guide + troubleshooter. I think probably it’ll be a good idea to conact him first and discuss little bit about expected benefits, etc. - he is often posting in this forum.

Rgds,
-dim

11

I think it’s better for me to just wait for 11.1, if it still isn’t right then i’ll regress and lock.

Hibernate isn’t the only problem for me. I removed pulse audio and use Esound for desktop, ALSA for multimedia, OSS for games. Old stuff lack features but it works, sometimes better.

Thanks for the thought folks.

12

Is your sound restarting now after suspend and hibernate?

If it does not resume properly (after suspend and hibernate) what happens if after suspend and hibernate (when sound doesn’t work) you manually restart alsa with:
su -c ‘rcalsasound restart’

13

Yes, it’s not working after resume. But, it’s not about that. The sound fails at certain points of use. And, it still not just that.

I’m sure there’s always at least one workaround for every problem i have. But i’m too tired doing workarounds and investigating faults. There are too many of them.

Now i know why a friend of mine still uses 10.2 . He uses a worned laptop. Software upgrades just not meant for better performance. Better features, but not better performance. Upgrading/Installing new stuff takes too much resource. I spent two weeks of lack of sleep doing clean install, testing features, investigating faults, applying patches, workarounds, and those are such a waste after i found out that the new softwares needs new hardwares unless you turn off the new feature which become a complete waste of time and internet bandwith.

I don’t mean bad though. I’m sure there’s a good point to do software upgrade. But for me it’s not now. My boss suddenly gave me tasks, and my laptop was in the state of not completely ready.

If i continue working out these problems, would it make it to the next distribution release?

If yes, how?

14

Sorry to read about your tribulations. … But if it were me, and if this was a work provided laptop, I definitely would NOT be playing around with ANY OS on a work provided laptop. I would stick with what the office gives me. That way its the office fault and not mine, for provided equipment failure.

or, alternatively, I would carefully pick and choose my own laptop for Linux compatibility, and use a laptop that I have picked which is 100% compatible (which is what I do) and I simply do not have such problems.

Unlikely IMHO. It only “might” make it to 11.1 IF you contribute to the development effort by writing bug reports on your specific problem, and testing the alpha and beta releases and writing bug reports on those for your specific problem.

Which is why I simply ensure my laptop is supported before:
a. purchasing the laptop, and
b. before updating way from a distribution version that works fine.

Best wishes in the path that you follow.

15

It’s my own personal property, not work provided. It’s either this or a work provided dumb terminal with only wallpaper and a handfull application through right click menu and the keyboard keys swaped around, and prone to black outs. The current state is more acceptable than the other option. lol!

I did. At least i thought i did. This is Axioo NVE828NC, a Via P4M900, Clevo M541SE. It has an original linux distribution with it. But the original is Mandrake and i want to try out opensuse. When i tried 10.2 it looks great. Then i tried again with 10.3, i didn’t notice any problem there. But when i tried 11.0 , it’s not going well.

Well at least i tried around before making final decesion to use the best distribution and version for this laptop. I still would try out new releases, partially. My nfs server working right after upgrading to 11.0 .

16

[quote="“rona_dinihari,post:15,topic:6900”]

I did. At least i thought i did. This is Axioo NVE828NC, a Via P4M900, Clevo M541SE. It has an original linux distribution with it. But the original is Mandrake and i want to try out opensuse. When i tried 10.2 it looks great. Then i tried again with 10.3, i didn’t notice any problem there. But when i tried 11.0 , it’s not going well.[/QUOTE]Hmmm… when I tried to search on this laptop, I found no mention. I looked here:

I also went to the Axioo and Clevo web sites, and saw no Linux driver support for the laptop.

I think this goes to show, that just because one gets Linux pre-installed on a Laptop, does not mean the support is good. I sympathisize with your frustration wrt to the effort to find work arounds, but from what I can see after spending 15 minutes surfing, this laptop has poor linux support, not only by the original supplier/manufacturer, but also poor support from the Linux community in general. … Maybe I am missing a good site that you have found, …

What I recommend you do is use various Linux tools to list the exact specification (including product/vendor IDs) for the various components of your laptop, and try to find support / workarounds that way … ie for

  • wireless
  • graphics
  • sound
  • webcam (if any)
    and then look for support and distribution compatibility on a “component” level.

… wrt power management, … take a good look at your “dmesg” output after a boot (pipe it to a text file):
dmesg > dmesg.txtand open dmseg.txt up with a text editor, and look for power management errors. You may need to do some major custom tuning there, … and this is an area that I know nothing about, as the laptops that I have used to date (after doing significant pre-purchase research) “just worked”.

I honestly can not see a way to get this laptop working completely without spending a LOT of time custom tuning. It simply is NOT supported well by Linux in general.

17

New update

oldcpu, i thought about your advise a lot. So i did some more check on the internet. It turn out that Via has released some more codes recently. I tried it out and it WORKED. Now I CAN HIBERNATE without any modification to power management settings. But there still something wrong with sound after resume.

Now since you have gave some advice for the sound, I’d like to continue on that.

i did this as root:
$ rcalsasound restart

$ dmesg
…
ACPI: PCI interrupt for device 0000:06:01.0 disabled
ACPI: PCI Interrupt 0000:06:01.0[A] → GSI 17 (level, low) → IRQ 17
PCI: Setting latency timer of device 0000:06:01.0 to 64
ALSA sound/pci/hda/hda_codec.c:3021: autoconfig: line_outs=1 (0x1f/0x0/0x0/0x0/0x0)
ALSA sound/pci/hda/hda_codec.c:3025: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
ALSA sound/pci/hda/hda_codec.c:3029: hp_outs=1 (0x20/0x0/0x0/0x0/0x0)
ALSA sound/pci/hda/hda_codec.c:3030: mono: mono_out=0x0
ALSA sound/pci/hda/hda_codec.c:3038: inputs: mic=0x1d, fmic=0x21, line=0x1e, fline=0x0, cd=0x24, aux=0x0

No sound came out after resume. What should i check now?

18

So your laptop sound works (before hibernation)? Your laptop then went into hibernation. When it came out no sound. And running: su -c ‘rcalsasound restart’ after coming out of hibernation did not help either ? Is that correct? What what you using as a sound test?

As for those dmesg parameters. Were there no others with either “snd” or “audio” or “alsa” or “hda”? The dmesg output you posted looks ok to me (with the very little that I know). Don’t those logged items just record the assigning of hardware codec aspects to various mixer controls? (I’m guessing there).

What sound modules are loaded after your laptop comes out of hibernation?

What does this give:lsmod | sndand how does it compare to typing the same command BEFORE hibernation?

In truth, I know nothing about hibernation … and know only a little bit about sound.

Good luck.