Sound lost again [Solved]
Sound lost again [Solved]
I had good sound with a level adjuster in the tray but I was playing with the sound and it all disappeared
No tray level . Looking for sound problems I go through the alsa configuration setup but the machine now does not find a sound card
Its got one of these built in sound and graphics motherboards from Dell
Anyone got any clues?
No tray level . Looking for sound problems I go through the alsa configuration setup but the machine now does not find a sound card
Its got one of these built in sound and graphics motherboards from Dell
Anyone got any clues?
Last edited by tytower on Sat 24 Mar 2012, 06:03, edited 1 time in total.
in what way were you playing with sound?
that output do you get if you tap
or
into the terminal?
the tray volume Retrovol won't load if its set to a soundcard that doesn't exist.
does the sound come back if you boot without pup save file
(if your using frugal)
that output do you get if you tap
Code: Select all
aplay -l
Code: Select all
alsamixer
the tray volume Retrovol won't load if its set to a soundcard that doesn't exist.
does the sound come back if you boot without pup save file
(if your using frugal)
I am trying to work out how to copy the output of the urxvt console to post here
Sound does come back when I boot without pupsave file
In the meantime this is from pupscan
DESCRIPTION: Audio device: nVidia Corporation MCP51 High Definition Audio
VENDOR: 10de DEVICE: 026c
KERNEL DRIVER (builtin): Intel
KERNEL MODULE: snd-hda-intel
and the attached screenshot is from Hardware info
Sound does come back when I boot without pupsave file
In the meantime this is from pupscan
DESCRIPTION: Audio device: nVidia Corporation MCP51 High Definition Audio
VENDOR: 10de DEVICE: 026c
KERNEL DRIVER (builtin): Intel
KERNEL MODULE: snd-hda-intel
and the attached screenshot is from Hardware info
- Attachments
-
- Console screenshot.png
- (60.79 KiB) Downloaded 1163 times
okay I've found its hard to get the sound system back on track.
looks like ALSA should use snd_hda_intel
I think the following file is where it gets loaded:
/etc/modprobe.d/alsa-base.conf
could try comparing what's in the pupsave with the pupbase.sfs
-make a copy of the pupbase.sfs
-boot without pupsave
-now both pupsave and pupbase.sfs can be mounted and inspected
btw- to get text from terminal highlight text, go to destination and press middle mouse button-
http://puppylinux.org/wikka/HowToCopyFromTerminal
looks like ALSA should use snd_hda_intel
I think the following file is where it gets loaded:
/etc/modprobe.d/alsa-base.conf
could try comparing what's in the pupsave with the pupbase.sfs
-make a copy of the pupbase.sfs
-boot without pupsave
-now both pupsave and pupbase.sfs can be mounted and inspected
btw- to get text from terminal highlight text, go to destination and press middle mouse button-
http://puppylinux.org/wikka/HowToCopyFromTerminal
OK Thanks
I'll look into both config files
The output you requested is
# aplay -l
**** List of PLAYBACK Hardware Devices ****
ALSA lib conf.c(parse_value) card is not a string
ALSA lib conf.c(snd_config_load1) _toplevel_:2:20:Invalid argument
ALSA lib conf.c(snd_config_hook_load) /etc/asound.conf may be old or corrupted: consider to remove or fix it
ALSA lib conf.c(snd_config_hooks_call) function snd_config_hook_load returned error: Invalid argument
ALSA lib conf.c(snd_config_update_r) hooks failed, removing configuration
aplay: device_list:249: control open (0): Invalid argument
#
# alsamixer
alsamixer.bin: option requires an argument -- 'c'
Usage: alsamixer [options]
Useful options:
-h, --help this help
-c, --card=NUMBER sound card number or id
-D, --device=NAME mixer device name
-V, --view=MODE starting view mode: playback/capture/all
Debugging options:
-g, --no-color toggle using of colors
-a, --abstraction=NAME mixer abstraction level: none/basic
#
I am thinking alsamixer needs an argument ,perhaps -c but I dont know where I would get the card number
I also guess that aplay is just revealing that the sound module is not correctly loaded
I'll look into both config files
The output you requested is
# aplay -l
**** List of PLAYBACK Hardware Devices ****
ALSA lib conf.c(parse_value) card is not a string
ALSA lib conf.c(snd_config_load1) _toplevel_:2:20:Invalid argument
ALSA lib conf.c(snd_config_hook_load) /etc/asound.conf may be old or corrupted: consider to remove or fix it
ALSA lib conf.c(snd_config_hooks_call) function snd_config_hook_load returned error: Invalid argument
ALSA lib conf.c(snd_config_update_r) hooks failed, removing configuration
aplay: device_list:249: control open (0): Invalid argument
#
# alsamixer
alsamixer.bin: option requires an argument -- 'c'
Usage: alsamixer [options]
Useful options:
-h, --help this help
-c, --card=NUMBER sound card number or id
-D, --device=NAME mixer device name
-V, --view=MODE starting view mode: playback/capture/all
Debugging options:
-g, --no-color toggle using of colors
-a, --abstraction=NAME mixer abstraction level: none/basic
#
I am thinking alsamixer needs an argument ,perhaps -c but I dont know where I would get the card number
I also guess that aplay is just revealing that the sound module is not correctly loaded
Your /etc/asound.conf file is probably corrupt. Please post the results of:
I'm guessing it may look like this:
This can happen if Multiple-Sound-Card-Wizard was run, but couldn't find any sound devices.
A good file will have an integer at the end of each line. If yours does not, delete the file and try aplay -l again. If the result is something like
then one or more of your sound modules have probably been unloaded, and should return when you next reboot if nothing else is broken.
You do not need /etc/asound.conf unless you have multiple sound cards and need to change the default. ALSA is happy without the file, but gets very confused if it exists and is corrupt.
Code: Select all
cat /etc/asound.conf
Code: Select all
# cat /etc/asound.conf
defaults.pcm.card
defaults.pcm.device
A good file will have an integer at the end of each line. If yours does not, delete the file and try aplay -l again. If the result is something like
Code: Select all
aplay: device_list:223: no soundcards found...
You do not need /etc/asound.conf unless you have multiple sound cards and need to change the default. ALSA is happy without the file, but gets very confused if it exists and is corrupt.
@darkcity
Nope,
both config files are identical -alsa.config and alsa-base.config
Will have a look at npierce's suggestion
,thanks
@npierce The file looked as you suggested. I deleted it
Now
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 0: HDA Generic [HDA Generic]
Subdevices: 1/1
Subdevice #0: subdevice #0
#
and now I'll try a reboot.
Brilliant the sound icon is back in the tray and the woof works -Thanks a lot for posting - Porn without sound is just plain boring hey!
Nope,
both config files are identical -alsa.config and alsa-base.config
Will have a look at npierce's suggestion
,thanks
@npierce The file looked as you suggested. I deleted it
Now
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 0: HDA Generic [HDA Generic]
Subdevices: 1/1
Subdevice #0: subdevice #0
#
and now I'll try a reboot.
Brilliant the sound icon is back in the tray and the woof works -Thanks a lot for posting - Porn without sound is just plain boring hey!
You're welcome. 'Tis good to hear that the problem is solved.
darkcity,
You asked the right questions. If you had not I wouldn't have suspected that asound.conf was missing its integers. The "ALSA lib conf.c(parse_value) card is not a string" from aplay, and the "alsamixer.bin: option requires an argument -- 'c'" from amixer were the tip-offs. So thank you.
By the way, this problem could sometimes arise from running the Multiple Sound Card Wizard (item "THREE" in the Sound Wizard) after ALSA Wizard had unloaded a necessary sound module. Barry recently uploaded an improved Multiple Sound Card Wizard to the repository which should prevent this from happening in future Puppies.
darkcity,
You asked the right questions. If you had not I wouldn't have suspected that asound.conf was missing its integers. The "ALSA lib conf.c(parse_value) card is not a string" from aplay, and the "alsamixer.bin: option requires an argument -- 'c'" from amixer were the tip-offs. So thank you.
By the way, this problem could sometimes arise from running the Multiple Sound Card Wizard (item "THREE" in the Sound Wizard) after ALSA Wizard had unloaded a necessary sound module. Barry recently uploaded an improved Multiple Sound Card Wizard to the repository which should prevent this from happening in future Puppies.