registry team mailing list archive

[jim_charlton <charltn@xxxxxxxxx>]

Putting highres=off on the GRUB kernel command line corrupts the audio on the Toshiba NB305.  I have posted these same comments to other bug reports about sound and suspend/reawaken problems on the NB305.  I am hoping that it will stimulate a resolution of the sleep/suspend/reawaken problem without turning off the highres timers.
***********************
The easiest test to see if the audio is working on the Toshiba NB305 is to go to preferences-> sound and make sure the ubuntu sound theme is selected. Then open a terminal window (accessories->terminal) and when the CLI appears, press and hold the back arrow. You will get a system "bong or ping" indicating an incorrect key entry) just hold it down and after 10 to 20 bongs the sound will distort. It requires 6 seconds before you can get normal sound again. Other programs that stress the sound system will cause this sudden distortion.

The problem can be avoided for many programs by removing pulseaudio
(apt-get remove pulseaudio) and reboot. You will lose the volume control
applet (and other pulseaudio stuff) but you can use alsamixer to set
volumes. Like I said... it is hardly a solution.... but many programs
will still work perfectly without pulseaudio installed.

It appears that pulseaudio requires the kernel highres timers in order
to work reliably. When you deactivate the timers by putting highres=off
on the GRUB kernel command line, it dooms pulseaudio. Or at least this
has been my experience. I tried it with a completely clean install, with
and without the "nohz=off highres=off". Without those parameters the
sound is just fine.

What is really required is a patch to make the machine suspend and
reawaken properly when the lid is closed... *without* ... deactivating
the highres timers.

As always... take anything I say with a grain of salt. It is just my
interpretation of what I observe.

-- 
wakeup from sleep fails on toshiba nb305
https://bugs.launchpad.net/bugs/508516
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Fedora.