Tiny Core Extensions > TCE Q&A Forum

suspend - after resume sound stops working (OSS)

(1/2) > >>

netnomad:
hi juanito,

although my hardware offers all kind of working suspends to ram or disk on different distributions,
(everything works fine after resume: sound, lan, wifi, cpufreq, sd-card-reader and so on)
with tinycore i had problems to get a working xvesa-screen after resume until now.

today i used following command:

sudo s2ram --force --vbe_save

and the resume returned to a working display.
i use 4.1 on a usbstick onboot and ondemand-configuration, so my loaded tczs are looped  under /tmp/tcloop.

after the resume everything seemed to work fine, but my sound stopped working (oss).
i'm not sure whether it has something to do with my dev-system
or with loaded modules that should be unloaded before suspending!?

would you have an idea?
every help is welcomed.

later i will give you actual hw-informations that i get with sudo s2ram -n...

netnomad:
i solved the problem quick & dirty:


--- Code: ---#!/bin/sh
sudo rmmod oss_usb &&
sudo rmmod oss_ich &&
sudo rmmod osscore &&
sudo s2ram --force --vbe_save
sudo modprobe osscore
sudo modprobe oss_usb
sudo modprobe oss_ich

--- End code ---

with this script the sound works also after the resume...
does someone knows a more elegant way?

thanks for every proposal or suggestion for improvement!

curaga:
It's a known issue, OSS does not support suspend right now. Instead of modules, you can use soundoff and soundon.

netnomad:
hi curaga,

thank you for your reply, i will test this soundon/off hard and will report my experiences.
another thing: on some workstations my live-usbstick with my tce-dir doesn't  work properly after a resume:
so i can't load additional tcz and perhaps some more strange dev-behavior.
after remounting another partition of this live-usbstick, f.e. the boot partition,
the whole device is freshly initialized, so everything works fine again...
would you know a tool or a command for refreshing the dev-relationship or some modules or daemons?

thank you for sharing your knowledge, bye.

netnomad:
hi curaga,

it can happen that the command
sudo soundoff
stops with a conflict, f.e. flit or ossxmix or sgmixer is still busy on the sound-device,
so it's not possible to stop the sound over this command.

tc@box:~$ sudo soundoff
Some applications are still using OSS - cannot unload
16102 /usr/local/bin/ossxmix
Please stop these applications and run soundoff again

on the other hand, different hardware loads different modules.
f.e. i started my usbstick on a workstation that loads additionally a further module:
oss_hdaudio
beside the other common three modules
oss_core, oss_ich, oss_usb.

so soundoff/on would be much more flexible, despite of that risk to have a conflict!
how can i solve this or make a workaround for programs that hold the device busy?

Navigation

[0] Message Index

[#] Next page