Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Invalid card number would imply that you don't have any functional driver for any of your cards. You have a webcam and a motherboard so that "should" be two sound cards at least. I would assume that alsa isn't installed, but alsamixer and speaker-test ran. And the alsa drivers are in the linux kernel these days, so odds of that are very low.
$ cat /proc/asound/cards
Just to verify that there's no functional cards.
$ lspci -nnk
$ lsusb
To list your devices to verify that the hardware exists.
Invalid card number would imply that you don't have any functional driver for any of your cards. You have a webcam and a motherboard so that "should" be two sound cards at least. I would assume that alsa isn't installed, but alsamixer and speaker-test ran. And the alsa drivers are in the linux kernel these days, so odds of that are very low.
$ cat /proc/asound/cards
Just to verify that there's no functional cards.
$ lspci -nnk
$ lsusb
To list your devices to verify that the hardware exists.
The ones I posted were to provide us with MORE INFORMATION. Some cards are "special", but we cannot tell that if we do not know what you have, and how your system recognizes it.
So the driver recognizes the hardware and runs to a point of presenting a device.
Code:
00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 04)
Subsystem: Samsung Electronics Co Ltd Device [144d:c604]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
That's the magic search string "[8086:1c20]", although many with your issue across many distros. Although with the lack of hits to a point, suggests it's more common that this card works? Or SEO and other algorithms make my search skills ineffective.
$ alsamixer -c 0
Maybe it's muted?
Is the user in the audio group? Sometimes that one slips by depending on how you did an installation.
Just to isolate to hardware/drivers do you dual boot windows still? Any chance of trying in windows at least if it works there then the hardware for sure works
So the driver recognizes the hardware and runs to a point of presenting a device.
Code:
00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 04)
Subsystem: Samsung Electronics Co Ltd Device [144d:c604]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
That's the magic search string "[8086:1c20]", although many with your issue across many distros. Although with the lack of hits to a point, suggests it's more common that this card works? Or SEO and other algorithms make my search skills ineffective.
Code:
$ alsamixer -c 0
Maybe it's muted?
Is the user in the audio group? Sometimes that one slips by depending on how you did an installation.
Code:
$ groups && id
Code:
# groupadd 0 audio -f && groupadd 1000 audio -f
Code:
bash-4.4$ groupadd
Usage: groupadd [options] GROUP
Options:
-f, --force exit successfully if the group already exists,
and cancel -g if the GID is already used
-g, --gid GID use GID for the new group
-h, --help display this help message and exit
-K, --key KEY=VALUE override /etc/login.defs defaults
-o, --non-unique allow to create groups with duplicate
(non-unique) GID
-p, --password PASSWORD use this encrypted password for the new group
-r, --system create a system account
-R, --root CHROOT_DIR directory to chroot into
bash-4.4$
Here, is the above command correct? Honestly I was unaware to the groups with user signups when installing any systems.
Here, I still remember few hardware devices are needed to be manually config during systems installation since Ubuntu 16.10.
Quote:
Originally Posted by Shadow_7
Code:
[hdscania@localhost ~]$ groups && id
hdscania sys wheel sudo
uid=1000(hdscania) gid=1000(hdscania) groups=1000(hdscania),3(sys),10(wheel),1001(sudo) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
[hdscania@localhost ~]$ alsamixer -c 0
invalid card index: 0
try `alsamixer --help' for more information
[hdscania@localhost ~]$ alsamixer -h
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
[hdscania@localhost ~]$ sudo alsamixer -c 0
invalid card index: 0
try `alsamixer --help' for more information
[hdscania@localhost ~]$ groups audio && id audio && sudo groups audio && sudo id audio
groups: ‘audio’: no such user
id: ‘audio’: no such user
groups: ‘audio’: no such user
id: ‘audio’: no such user
[hdscania@localhost ~]$ sudo groupadd audio && sudo gpasswd -a 1000 audio && sudo gpasswd -a 0 audio
groupadd: group 'audio' already exists
[hdscania@localhost ~]$ sudo gpasswd -a 1000 audio && sudo gpasswd -a 0 audio
gpasswd: user '1000' does not exist
[hdscania@localhost ~]$ sudo gpasswd -a hdscania audio && sudo gpasswd -a root audio
Adding user hdscania to group audio
Adding user root to group audio
[hdscania@localhost ~]$ groupmod
Usage: groupmod [options] GROUP
Options:
-g, --gid GID change the group ID to GID
-h, --help display this help message and exit
-n, --new-name NEW_GROUP change the name to NEW_GROUP
-o, --non-unique allow to use a duplicate (non-unique) GID
-p, --password PASSWORD change the password to this (encrypted)
PASSWORD
-R, --root CHROOT_DIR directory to chroot into
[hdscania@localhost ~]$ sudo groupmod -g 829 audio
[hdscania@localhost ~]$ id audio
id: ‘audio’: no such user
[hdscania@localhost ~]$ id --help
Usage: id [OPTION]... [USER]
Print user and group information for the specified USER,
or (when USER omitted) for the current user.
-a ignore, for compatibility with other versions
-Z, --context print only the security context of the process
-g, --group print only the effective group ID
-G, --groups print all group IDs
-n, --name print a name instead of a number, for -ugG
-r, --real print the real ID instead of the effective ID, with -ugG
-u, --user print only the effective user ID
-z, --zero delimit entries with NUL characters, not whitespace;
not permitted in default format
--help display this help and exit
--version output version information and exit
Without any OPTION, print some useful set of identified information.
GNU coreutils online help: <http://www.gnu.org/software/coreutils/>
Full documentation at: <http://www.gnu.org/software/coreutils/id>
or available locally via: info '(coreutils) id invocation'
[hdscania@localhost ~]$ sudo id -G
0 829
[hdscania@localhost ~]$
The results for your commands are here, still no audio playbacks are.
$ sudo usermod -G group1,group2,group3,group4 USER
Or more specifically in my case.
$ sudo usermod -G USER,lp,cdrom,sudo,video,games,lpadmin,audio USER
Which would be the output of groups plus the NEW group. Bear in mind that the user will have to login again to have the group change take affect. Or the usual M$ methodology of rebooting.
# usermod -G USER,lp,cdrom,sudo,video,games,lpadmin,audio USER
Which would be the output of groups plus the NEW group. Bear in mind that the user will have to login again to have the group change take affect. Or the usual M$ methodology of rebooting.
Code:
[hdscania@localhost ~]$ groupmod
Usage: groupmod [options] GROUP
Options:
-g, --gid GID change the group ID to GID
-h, --help display this help message and exit
-n, --new-name NEW_GROUP change the name to NEW_GROUP
-o, --non-unique allow to use a duplicate (non-unique) GID
-p, --password PASSWORD change the password to this (encrypted)
PASSWORD
-R, --root CHROOT_DIR directory to chroot into
[hdscania@localhost ~]$ groupadd
Usage: groupadd [options] GROUP
Options:
-f, --force exit successfully if the group already exists,
and cancel -g if the GID is already used
-g, --gid GID use GID for the new group
-h, --help display this help message and exit
-K, --key KEY=VALUE override /etc/login.defs defaults
-o, --non-unique allow to create groups with duplicate
(non-unique) GID
-p, --password PASSWORD use this encrypted password for the new group
-r, --system create a system account
-R, --root CHROOT_DIR directory to chroot into
[hdscania@localhost ~]$ id
uid=1000(hdscania) gid=1000(hdscania) groups=1000(hdscania),3(sys),10(wheel),829(audio),1001(sudo) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
[hdscania@localhost ~]$ id --help
Usage: id [OPTION]... [USER]
Print user and group information for the specified USER,
or (when USER omitted) for the current user.
-a ignore, for compatibility with other versions
-Z, --context print only the security context of the process
-g, --group print only the effective group ID
-G, --groups print all group IDs
-n, --name print a name instead of a number, for -ugG
-r, --real print the real ID instead of the effective ID, with -ugG
-u, --user print only the effective user ID
-z, --zero delimit entries with NUL characters, not whitespace;
not permitted in default format
--help display this help and exit
--version output version information and exit
Without any OPTION, print some useful set of identified information.
GNU coreutils online help: <http://www.gnu.org/software/coreutils/>
Full documentation at: <http://www.gnu.org/software/coreutils/id>
or available locally via: info '(coreutils) id invocation'
[hdscania@localhost ~]$ groupdel
Usage: groupdel [options] GROUP
Options:
-h, --help display this help message and exit
-R, --root CHROOT_DIR directory to chroot into
-f, --force delete group even if it is the primary group of a user
[hdscania@localhost ~]$ sudo groupdel audio -f
[hdscania@localhost ~]$ sudo usermod -G 1000,audio 1000
usermod: group 'audio' does not exist
[hdscania@localhost ~]$ sudo usermod -G hdscania,audio hdscania
usermod: group 'audio' does not exist
[hdscania@localhost ~]$ usermod
Usage: usermod [options] LOGIN
Options:
-c, --comment COMMENT new value of the GECOS field
-d, --home HOME_DIR new home directory for the user account
-e, --expiredate EXPIRE_DATE set account expiration date to EXPIRE_DATE
-f, --inactive INACTIVE set password inactive after expiration
to INACTIVE
-g, --gid GROUP force use GROUP as new primary group
-G, --groups GROUPS new list of supplementary GROUPS
-a, --append append the user to the supplemental GROUPS
mentioned by the -G option without removing
him/her from other groups
-h, --help display this help message and exit
-l, --login NEW_LOGIN new value of the login name
-L, --lock lock the user account
-m, --move-home move contents of the home directory to the
new location (use only with -d)
-o, --non-unique allow using duplicate (non-unique) UID
-p, --password PASSWORD use encrypted password for the new password
-R, --root CHROOT_DIR directory to chroot into
-s, --shell SHELL new login shell for the user account
-u, --uid UID new UID for the user account
-U, --unlock unlock the user account
-v, --add-subuids FIRST-LAST add range of subordinate uids
-V, --del-subuids FIRST-LAST remove range of subordinate uids
-w, --add-subgids FIRST-LAST add range of subordinate gids
-W, --del-subgids FIRST-LAST remove range of subordinate gids
-Z, --selinux-user SEUSER new SELinux user mapping for the user account
[hdscania@localhost ~]$ sudo groupadd -f audio
[hdscania@localhost ~]$ sudo usermod -G 1000,audio 1000
usermod: user '1000' does not exist
[hdscania@localhost ~]$ sudo usermod -G hdscania,audio hdscania
[hdscania@localhost ~]$ sudo usermod -G root,audio root
[hdscania@localhost ~]$
But still seeing ‘‘dummy’’ output under the sound daemons, which my issue is unlikely to be users and groups related.
You need to logout and login for group changes to take affect. But yes, as long as you have nothing registering under aplay or /proc/asound/cards, it's only a step closer, NOT an arrival at the destination. TBH, you're probably at the stage where you do a fresh distro install (and use the installer this time).
You need to logout and login for group changes to take affect. But yes, as long as you have nothing registering under aplay or /proc/asound/cards, it's only a step closer, NOT an arrival at the destination. TBH, you're probably at the stage where you do a fresh distro install (and use the installer this time).
I have signed OUT THEN IN but is still hearing nothing.
Code:
[hdscania@localhost asound]$ cd /proc/asound && ls -la
total 0
dr-xr-xr-x. 5 root root 0 May 21 12:16 .
dr-xr-xr-x. 219 root root 0 May 21 11:53 ..
dr-xr-xr-x. 3 root root 0 May 21 12:16 card0
-r--r--r--. 1 root root 0 May 21 12:16 cards
-r--r--r--. 1 root root 0 May 21 12:16 devices
-r--r--r--. 1 root root 0 May 21 12:16 hwdep
-r--r--r--. 1 root root 0 May 21 12:16 modules
dr-xr-xr-x. 2 root root 0 May 21 12:16 oss
lrwxrwxrwx. 1 root root 5 May 21 12:16 PCH -> card0
-r--r--r--. 1 root root 0 May 21 12:16 pcm
dr-xr-xr-x. 2 root root 0 May 21 12:16 seq
-r--r--r--. 1 root root 0 May 21 12:16 timers
-r--r--r--. 1 root root 0 May 21 12:16 version
[hdscania@localhost asound]$
Here, you have guessed right nothing here, but why to reinstall the system? But, I have upgraded my system to rc over alpha, still reinstall system anyway?
0 [Generic ]: HDA-Intel - HD-Audio Generic
HD-Audio Generic at 0xfeb44000 irq 25
1 [SB ]: HDA-Intel - HDA ATI SB
HDA ATI SB at 0xfeb40000 irq 16
Is what shows on my system. Which is 2 soundcards (technically). Although only 1 aka hw:1 outputs sound to the speakers. With the /proc/asound/card0 path, you should have at least ONE soundcard with a driver.
$ speaker-test -c 2 -l 1 -D hw:1
Not that it matters for me as I use pulseaudio over a network. One good set of speakers and audio interface (physically connected to a different machine).
FILE: $HOME/.config/pulse/client.conf
Code:
default-server = 192.168.2.1
Although in my case it was more because EQ and other things chew up a lot of system resources, which this machine just doesn't have. I still think you need to do a fresh install with the distro installer. The installer normally creates the first user and adds it to the audio group. Plus a lot of the threads about your hardware that I found were from 2014 and indicated that the card "works".
I'm kind of surprised that the audio driver has "codecs", but it is what it is I guess. With the realtek ALC 662 codec being what's required on this machine by the output of dmesg.
The open error is troubling. And I've seen it before on my own systems. Although mostly not installed or permission type issue historically. Not sure if I've seen it since the olden days of compiling alsa from sources before it was integrated into the kernel. Normally forgot the alsa-lib (libasound2 package wise) or similar back in that day.
$ ls -l /dev/ | grep -i audio
$ ls -l /dev/snd/ | grep -i audio
Trying to recall if that happens when pulseaudio is active. With autospawn=no in the /etc/pulse/ stuff (client.conf?) you can stop pulseaudio. But if other configuration is there, like my $HOME/.config/pulse/client.conf, that could get in the way. Edit it and # (comment) out any active lines in my case to change configuration without un-installing pulse or other tricks.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
