Hi
I have an emachine e510 and the sound is not working very well?
Can anyone direct me to a driver etc that I need.
1: udi = ‘/org/freedesktop/Hal/devices/pci_8086_284b_sound_card_0_oss_pcm_0_0’
info.subsystem = ‘sound’
info.product = ‘ALC268 Analog OSS PCM Device’
oss.device_file = ‘/dev/audio’
info.udi = ‘/org/freedesktop/Hal/devices/pci_8086_284b_sound_card_0_oss_pcm_0_0’
oss.originating_device = ‘/org/freedesktop/Hal/devices/pci_8086_284b_sound_card_0’
linux.sysfs_path = ‘/sys/devices/pci0000:00/0000:00:1b.0/sound/card0/audio’
info.category = ‘oss’
oss.card = 0 (0x0)
info.capabilities = { ‘oss’, ‘access_control’ }
info.parent = ‘/org/freedesktop/Hal/devices/pci_8086_284b_sound_card_0’
oss.card_id = ‘HDA Intel’
oss.device_id = ‘ALC268 Analog’
oss.type = ‘pcm’
access_control.file = ‘/dev/audio’
oss.device = 0 (0x0)
linux.hotplug_type = 2 (0x2)
access_control.type = ‘sound’
linux.subsystem = ‘sound’
linux.device_file = ‘/dev/audio’
info.callouts.add = { ‘hal-acl-tool --add-device’ }
info.callouts.remove = { ‘hal-acl-tool --remove-device’ }
Thanks
oldcpu
September 20, 2009, 8:34am
2
The driver that you need is likely the alsa driver and it is probably installed already.
Please explain what “the sound is not working very well” means?
Hi
Thanks for the reply.
The lap top is dual booted with Windows and when in windows the sound is a good level and clear. In Linux the sound is very low level and distorted, so much so that the startup jingle is broken up. Yet in Amarok the sound is fine. I have used the control panel and the settings in Kmix which are set to almost max.
Thanks
oldcpu
September 20, 2009, 4:20pm
4
signetone:
The lap top is dual booted with Windows and when in windows the sound is a good level and clear. In Linux the sound is very low level and distorted, so much so that the startup jingle is broken up. Yet in Amarok the sound is fine. I have used the control panel and the settings in Kmix which are set to almost max.
Please follow step-7 in this guide:
SDB:AudioTroubleshooting - openSUSE
… lets see if that helps, before we try anything else.
load-module module-hal-detect
in /etc/pulse/default.pa by
load-module module-hal-detect tsched=0
Hi thanks for reply.
I have found the first line but do not know how to alter it?
Can you please advise
Thanks
Hi
I can open a root window.
I can get to the file
It’s the syntax of how to alter
the line
load-module module-hal-detect
to
load-module module-hal-detect tsched=0
Thanks
oldcpu
September 21, 2009, 6:45pm
7
signetone:
I can open a root window.
I can get to the file
It’s the syntax of how to alter
the line
load-module module-hal-detect
to
load-module module-hal-detect tsched=0
Thanks
Open a terminal as a REGULAR USER. Then
if using gnome type: gnomesu gedit /etc/pulse/default.pa
#and enter root password when prompted, and edit the file
*]if using KDE type: kdesu ‘kwrite /etc/pulse/default.pa’ #and enter root password when prompted, and edit the file
Thanks
I use KDE and have backed up the file and done the amendment.
Yes it works. The sound is much, much better no distortion, seems to be ok in bbc iplayer and Amarok and system sounds.
Thanks for your help.
oldcpu
September 21, 2009, 7:55pm
9
Glad to read that works.
I note a number of fedora Linux users also have to apply the same fix.
Hi
I was checking out various applications and the sound and a note came up. CPU overload, sound system closing down.
I will try and get the exact syntax again?
Any ideas?
Thanks
Your running Intel’s built-in Audio, so go with the flow.
Yast>Hardware>Sound
make sure your using the HDA sound card.
Select Edit model
add “ref”
select ok
follow it though and reboot your sound.
Close Yast, restart kmix or what ever it is in Gnome.
open kmix or … un-mute and turn the volume up on everything, in my case I chose ‘right’.
Close mixer, make sure volume is at a reasonable level.
Reboot your puter. after you login, you should be hearing the startup file play.
enjoy.
signetone:
Hi
I have an emachine e510 and the sound is not working very well?
Can anyone direct me to a driver etc that I need.
1: udi = ‘/org/freedesktop/Hal/devices/pci_8086_284b_sound_card_0_oss_pcm_0_0’
info.subsystem = ‘sound’
info.product = ‘ALC268 Analog OSS PCM Device’
oss.device_file = ‘/dev/audio’
info.udi = ‘/org/freedesktop/Hal/devices/pci_8086_284b_sound_card_0_oss_pcm_0_0’
oss.originating_device = ‘/org/freedesktop/Hal/devices/pci_8086_284b_sound_card_0’
linux.sysfs_path = ‘/sys/devices/pci0000:00/0000:00:1b.0/sound/card0/audio’
info.category = ‘oss’
oss.card = 0 (0x0)
info.capabilities = { ‘oss’, ‘access_control’ }
info.parent = ‘/org/freedesktop/Hal/devices/pci_8086_284b_sound_card_0’
oss.card_id = ‘HDA Intel’
oss.device_id = ‘ALC268 Analog’
oss.type = ‘pcm’
access_control.file = ‘/dev/audio’
oss.device = 0 (0x0)
linux.hotplug_type = 2 (0x2)
access_control.type = ‘sound’
linux.subsystem = ‘sound’
linux.device_file = ‘/dev/audio’
info.callouts.add = { ‘hal-acl-tool --add-device’ }
info.callouts.remove = { ‘hal-acl-tool --remove-device’ }
Thanks
oldcpu
October 3, 2009, 8:59am
12
China_Jobs, welcome to openSUSE forums.
I note you replied to a number of sound support threads, and in every case recommended the application of the model “ref”.
In fact, that model option does NOT work in most cases. If one looks at the 1.0.18 version of alsa-configuration.txt file, and does a search for ref, one will find that option “might” only work for the following options …
STAC9200, STAC9205/9254, STAC9220/9221, STAC9202/9250/9251, STAC9227/9228/9229/927x, STAC92HD71B*, STAC92HD73*
In the case of user signetone they did not indicate what hardware audio code their emachine e510 has, although I suspect it is an ALC268 and not a “stacxxxx”. Hence I believe ref would likely break their sound, as opposed to fix it. One needs to be very precise on the model options that are applied, and they must be selected from the alsa-configuration.txt or hd-audio-models.txt file that is documented by the alsa packagers.
We can use all the help we can get in the forums, so if you get the chance you could read the following files (comes with the documentation in every alsa tarball):
alsa-configuration.txt
hd-audio-models.txt
hd-audio.txt
and that should shed some light on this, and the various aspects associated with troubleshooting Linux sound.
oldcpu:
China_Jobs, welcome to openSUSE forums.
I note you replied to a number of sound support threads, and in every case recommended the application of the model “ref”.
In fact, that model option does NOT work in most cases. If one looks at the 1.0.18 version of alsa-configuration.txt file, and does a search for ref, one will find that option “might” only work for the following options …
STAC9200, STAC9205/9254, STAC9220/9221, STAC9202/9250/9251, STAC9227/9228/9229/927x, STAC92HD71B*, STAC92HD73*
In the case of user signetone they did not indicate what hardware audio code their emachine e510 has, although I suspect it is an ALC268 and not a “stacxxxx”. Hence I believe ref would likely break their sound, as opposed to fix it. One needs to be very precise on the model options that are applied, and they must be selected from the alsa-configuration.txt or hd-audio-models.txt file that is documented by the alsa packagers.
We can use all the help we can get in the forums, so if you get the chance you could read the following files (comes with the documentation in every alsa tarball):
alsa-configuration.txt
hd-audio-models.txt
hd-audio.txt
and that should shed some light on this, and the various aspects associated with troubleshooting Linux sound.
hi oldcpu,
yes the last post does not work.
the change i did do works to some degree then a program takes over the cpu artsd and i have to kill it before i can carry on.
Thanks
oldcpu
October 3, 2009, 3:12pm
14
I confess I do not understand what you are describing.
If you believe there is a process hogging the cpu, please as soon as you start openSUSE type in a terminal/konsole “top” and keep that konsole / terminal above your various window applications. And then try to repeat the behaviour and report what process is causing you a cpu problem (you mentioned some program takes over the “cpu artsd” which means nothing to me).
Note also per the audio troubeshooting guide you can determine what application/process is using your sound driver by copying and pasting into a different terminal / konsole : SDB:AudioTroubleshooting - openSUSE
lsof /dev/dsp* /dev/audio* /dev/mixer* /dev/snd/*
oldcpu:
I confess I do not understand what you are describing.
If you believe there is a process hogging the cpu, please as soon as you start openSUSE type in a terminal/konsole “top” and keep that konsole / terminal above your various window applications. And then try to repeat the behaviour and report what process is causing you a cpu problem (you mentioned some program takes over the “cpu artsd” which means nothing to me).
Note also per the audio troubeshooting guide you can determine what application/process is using your sound driver by copying and pasting into a different terminal / konsole : SDB:AudioTroubleshooting - openSUSE
lsof /dev/dsp* /dev/audio* /dev/mixer* /dev/snd/*
Hi
Will do.
Thats what I did. I ran Amarok and then closed it. The curser would hardly move and processor going full on, managed to open konsole window and an application alsa or alsd was usuing 95% so i killed the process.
Will get back on the lap top and see if I can repeat the problem.
Thanks
From the hardware config.
3: udi = ‘/org/freedesktop/Hal/devices/pci_8086_284b_sound_card_0_oss_mixer__1’
info.subsystem = ‘sound’
info.product = ‘ALC268 Analog OSS Control Device’
oss.device_file = ‘/dev/mixer’
info.udi = ‘/org/freedesktop/Hal/devices/pci_8086_284b_sound_card_0_oss_mixer__1’
oss.originating_device = ‘/org/freedesktop/Hal/devices/pci_8086_284b_sound_card_0’
linux.sysfs_path = ‘/sys/devices/pci0000:00/0000:00:1b.0/sound/card0/mixer’
info.category = ‘oss’
oss.card = 0 (0x0)
info.capabilities = { ‘oss’, ‘access_control’ }
info.parent = ‘/org/freedesktop/Hal/devices/pci_8086_284b_sound_card_0’
oss.card_id = ‘HDA Intel’
oss.device_id = ‘ALC268 Analog’
oss.type = ‘mixer’
access_control.file = ‘/dev/mixer’
linux.hotplug_type = 2 (0x2)
access_control.type = ‘sound’
linux.subsystem = ‘sound’
linux.device_file = ‘/dev/mixer’
info.callouts.add = { ‘hal-acl-tool --add-device’ }
info.callouts.remove = { ‘hal-acl-tool --remove-device’ }
I will check out the link you gave above.
Thanks
oldcpu
October 3, 2009, 6:54pm
17
alsa using 95% ? I’ve never seen that. If you see alsa running 95% again, and if you can, please run the "lsof … " command to see what application is using alsa to cause this.
BTW I have a card 82801H (ICH8 Family) Index 0 HD Audio controller
from YAST
Thanks
Hi
is this a command in a Konsole window?
I have tried but not sure of the syntax?
Thanks
oldcpu
October 3, 2009, 7:40pm
20
To avoid worrying about the syntax, just copy and paste this into a terminal/konsole:
lsof /dev/dsp* /dev/audio* /dev/mixer* /dev/snd/*
do that when you are playing no sound. Copy and paste the output to a text file. Keep that file!
Then play some audio. and while playing again copy and paste the same into a terminal/konsole:
lsof /dev/dsp* /dev/audio* /dev/mixer* /dev/snd/*
Copy and paste that into a different text file. Compare the two. It will show you what app is using your sound device.