Atualmente, estou inicializando o Arch Linux ARM a partir de um cartão SD no meu Samsung Chromebook (modelo XE303C12). Eu tenho o XFCE4 DE instalado com o PulseAudio e o Alsa-utils. Não consigo fazer com que qualquer áudio funcione como sempre na minha instalação. Eu já tentei ativar o som usando alsamixer , o que não funcionou. Alguém pode me ajudar a corrigir meu problema de áudio? Aqui estão algumas informações adicionais:
Informações gerais do sistema:
[root@alarm alarm]# uname -a
Linux alarm 3.8.11-4-ARCH #1 SMP Sat Oct 22 11:59:55 MDT 2016 armv7l GNU/Linux
Informações da placa de som:
[root@alarm alarm]# cat /proc/asound/cards
0 [DAISYI2S98090 ]: DAISY-I2S-98090 - DAISY-I2S-98090
DAISY-I2S-98090
Solicitou journalctl output:
[root@alarm alarm]# journalctl -xe
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit netctl@mlan0\x2dHoney1.service has begun starting up.
Aug 23 22:08:20 alarm network[556]: Starting network profile 'mlan0-Honey1'...
Aug 23 22:08:20 alarm kernel: IPv6: ADDRCONF(NETDEV_UP): mlan0: link is not ready
Aug 23 22:08:24 alarm kernel: mwifiex_sdio mmc2:0001:1: info: trying to associate to 'Honey1' bssid 60:31:97:e0:97:1b
Aug 23 22:08:24 alarm kernel: mwifiex_sdio mmc2:0001:1: info: associated to bssid 60:31:97:e0:97:1b successfully
Aug 23 22:08:24 alarm kernel: IPv6: ADDRCONF(NETDEV_CHANGE): mlan0: link becomes ready
Aug 23 22:08:24 alarm systemd-networkd[155]: mlan0: Gained carrier
Aug 23 22:08:24 alarm systemd[1]: Started Networking for netctl profile mlan0-Honey1.
-- Subject: Unit netctl@mlan0\x2dHoney1.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit netctl@mlan0\x2dHoney1.service has finished starting up.
--
-- The start-up result is done.
Aug 23 22:08:24 alarm sudo[474]: pam_unix(sudo:session): session closed for user root
Aug 23 22:08:24 alarm dhcpcd[683]: DUID 00:01:00:01:21:26:5f:84:fc:c2:de:31:2a:79
Aug 23 22:08:24 alarm dhcpcd[683]: mlan0: IAID de:31:2a:79
Aug 23 22:08:25 alarm dhcpcd[683]: mlan0: rebinding lease of 192.168.0.8
Aug 23 22:08:25 alarm dhcpcd[683]: mlan0: probing address 192.168.0.8/24
Aug 23 22:08:25 alarm systemd-networkd[155]: mlan0: Gained IPv6LL
Aug 23 22:08:25 alarm systemd-timesyncd[197]: Network configuration changed, trying to establish connection.
Aug 23 22:08:30 alarm dhcpcd[683]: mlan0: leased 192.168.0.8 for 86400 seconds
Aug 23 22:08:30 alarm dhcpcd[683]: mlan0: adding route to 192.168.0.0/24
Aug 23 22:08:30 alarm systemd-timesyncd[197]: Network configuration changed, trying to establish connection.
Aug 23 22:08:30 alarm dhcpcd[683]: mlan0: adding default route via 192.168.0.1
Aug 23 22:08:31 alarm dhcpcd[683]: forked to background, child pid 732
Aug 23 22:08:31 alarm network[556]: Started network profile 'mlan0-Honey1'
Aug 23 22:09:02 alarm systemd-timesyncd[197]: Synchronized to time server 198.60.22.240:123 (2.arch.pool.ntp.org).
Aug 23 22:12:00 alarm su[831]: (to root) alarm on pts/0
Aug 23 22:12:00 alarm su[831]: pam_unix(su:session): session opened for user root by (uid=1000)
lines 2062-2094/2094 (END)
Alguns dos codecs de áudio (os chips) usados nos Chromebooks são suportados nas versões recentes do kernel, mas alguns ainda não são de todo. Você deve verificar se existe um kernel mais recente, já que o 3.8 é muito muito antigo (essa é a desvantagem do prefeito de usar Chromebooks baseados em ARM).
Soluções alternativas incluem o uso de dongles / placas de som / DACs de áudio Bluetooth A2DP ou USB.
Tags audio arch-arm chrome-book