SliTaz Forum

christophe

Member

Registered: 2011-04-17

Posts: 432

sound problem

hey,

I received my new mother board but have no sound, the sound card is not recognised:

tux@slitaz:~$ alsamixer

cannot open mixer: No such file or directory

tux@slitaz:~$ lspci | grep Audio

00:1b.0 Audio device: Intel Corporation Device 1c20 (rev 04)

tux@slitaz:~$

Any suggestion  ? (this is slitaz 3.0)

Tx

mojo

Administrator

Registered: 2011-03-29

Posts: 2,174

Re: sound problem

straw is cheaper,

#modprobe snd-hda-intel

#soundconf

Post output:

lspci -nn

lsmod | grep '^snd'

aplay -L

aplay -l

christophe

Member

Registered: 2011-04-17

Posts: 432

Re: sound problem

#modprobe snd-hda-intel

#soundconf

-> windows no supported PnP or PCI card found. Would you like to probe legacy ISA sound card/chips ? YES

-> no legacy card found

_____________________________________________________________________________________________

root@slitaz:/home/tux# lspci -nn

00:00.0 Host bridge [0600]: Intel Corporation Device [8086:0100] (rev 09)

00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:0102] (rev 09)

00:16.0 Communication controller [0780]: Intel Corporation Device [8086:1c3a] (rev 04)

00:1a.0 USB Controller [0c03]: Intel Corporation Device [8086:1c2d] (rev 04)

00:1b.0 Audio device [0403]: Intel Corporation Device [8086:1c20] (rev 04)

00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:1c10] (rev b4)

00:1c.4 PCI bridge [0604]: Intel Corporation Device [8086:1c18] (rev b4)

00:1c.5 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev b4)

00:1d.0 USB Controller [0c03]: Intel Corporation Device [8086:1c26] (rev 04)

00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:1c5c] (rev 04)

00:1f.2 IDE interface [0101]: Intel Corporation Device [8086:1c00] (rev 04)

00:1f.3 SMBus [0c05]: Intel Corporation Device [8086:1c22] (rev 04)

00:1f.5 IDE interface [0101]: Intel Corporation Device [8086:1c08] (rev 04)

02:00.0 Ethernet controller [0200]: Attansic Technology Corp. Device [1969:1083] (rev c0)

03:00.0 PCI bridge [0604]: Integrated Technology Express, Inc. Device [1283:8892] (rev 30)

04:01.0 Network controller [0280]: RaLink RT2500 802.11g Cardbus/mini-PCI [1814:0201] (rev 01)

root@slitaz:/home/tux# lsmod | grep '^snd'

snd_hda_intel          22020  0

snd_hda_codec          49928  1 snd_hda_intel

snd_hwdep               5988  1 snd_hda_codec

snd_pcm                51780  2 snd_hda_intel,snd_hda_codec

snd_timer              16344  1 snd_pcm

snd                    43584  5 snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer

snd_page_alloc          7256  2 snd_hda_intel,snd_pcm

root@slitaz:/home/tux# aplay -L

root@slitaz:/home/tux# aplay -l

aplay: device_list:223: no soundcards found...

root@slitaz:/home/tux#

christophe

Member

Registered: 2011-04-17

Posts: 432

Re: sound problem

it seems i am having more problems than i first thought with this new hw.

I am booting using a frugal instal on my previous ATA disk, which is now USB mounted.

however, slitaz does not see the internal disk nor internal cdrom (which are both sata)

fdisk -l only shows sda disk (not the internal, new, unformatted internal disk),

gparted only shows the usb disk as sda, too.

i am having the same problem with ubuntu based linux (mint, crunchbang, lxde)

the sata hw is recognised by the bios, and i can boot eg bartpe on it

have not tried to boot slitaz 3 or 4 from cdrom.

Any hint ?

Tx

Christophe

christophe

Member

Registered: 2011-04-17

Posts: 432

Re: sound problem

the sound chip is a realtek 887 and i have seen numerous issues with it and linux

One of the way to solve it seemingly is

edit /etc/modprobe.d/alsa-base.conf

add

options snd-hda-intel model=generic

There is no /etc/modprobe.d/alsa-base.conf file,

should i just create it ?

Thanks

christophe

Member

Registered: 2011-04-17

Posts: 432

Re: sound problem

ok it seems i went through all the search process so ...

- alc887 is not recognised by 3.0 but is by 4.0 (which has a newer version of asla)

- the sata problem is solved also: it needs to be define as ahci in bios (was ide by default).

life is suddenly much better