Can't get sound working. I've seen http://forum.porteus.org/viewtopic.php? ... lsa#p61806 that changing preferences from pulseaudio to alsa works, but no luck for me.
Any advice?
Cheers!
Sound not working
Moderator: M. Eerie
Sound not working
> Does not compute_
https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584
https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584
Sound not working
I think I got it
Does it work for you?
I've tried to overwrite that package, but "errors ocurred"
Does it work for you?
I've tried to overwrite that package, but "errors ocurred"
Code: Select all
[guest@porteus ~]$ yaourt -Syy alsa-firmware
:: Synchronizing package databases...
system 173.4 KiB 1002K/s 00:00 [#############################################] 100%
world 482.4 KiB 7.85M/s 00:00 [#############################################] 100%
galaxy 102.1 KiB 0.00B/s 00:00 [#############################################] 100%
extra 1595.2 KiB 5.28M/s 00:00 [#############################################] 100%
community 4.1 MiB 29.4M/s 00:00 [#############################################] 100%
resolving dependencies...
looking for conflicting packages...
Packages (1) alsa-firmware-1.0.29-1
Total Download Size: 3.21 MiB
Total Installed Size: 12.94 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
alsa-firmware-1.0.29-1-any 3.2 MiB 8.45M/s 00:00 [#############################################] 100%
(1/1) checking keys in keyring [#############################################] 100%
(1/1) checking package integrity [#############################################] 100%
(1/1) loading package files [#############################################] 100%
(1/1) checking for file conflicts [#############################################] 100%
error: failed to commit transaction (conflicting files)
alsa-firmware: /usr/lib/firmware/asihpi/dsp5000.bin exists in filesystem
alsa-firmware: /usr/lib/firmware/asihpi/dsp6200.bin exists in filesystem
alsa-firmware: /usr/lib/firmware/asihpi/dsp6205.bin exists in filesystem
alsa-firmware: /usr/lib/firmware/asihpi/dsp6400.bin exists in filesystem
alsa-firmware: /usr/lib/firmware/asihpi/dsp6600.bin exists in filesystem
alsa-firmware: /usr/lib/firmware/asihpi/dsp8700.bin exists in filesystem
alsa-firmware: /usr/lib/firmware/asihpi/dsp8900.bin exists in filesystem
alsa-firmware: /usr/lib/firmware/cs46xx/cwc4630 exists in filesystem
alsa-firmware: /usr/lib/firmware/cs46xx/cwcasync exists in filesystem
alsa-firmware: /usr/lib/firmware/cs46xx/cwcbinhack exists in filesystem
alsa-firmware: /usr/lib/firmware/cs46xx/cwcdma exists in filesystem
alsa-firmware: /usr/lib/firmware/cs46xx/cwcsnoop exists in filesystem
alsa-firmware: /usr/lib/firmware/digiface_firmware.bin exists in filesystem
alsa-firmware: /usr/lib/firmware/digiface_firmware_rev11.bin exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/3g_asic.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/darla20_dsp.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/darla24_dsp.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/echo3g_dsp.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/gina20_dsp.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/gina24_301_asic.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/gina24_301_dsp.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/gina24_361_asic.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/gina24_361_dsp.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/indigo_dj_dsp.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/indigo_djx_dsp.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/indigo_dsp.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/indigo_io_dsp.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/indigo_iox_dsp.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/layla20_asic.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/layla20_dsp.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/layla24_1_asic.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/layla24_2A_asic.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/layla24_2S_asic.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/layla24_dsp.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/loader_dsp.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/mia_dsp.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/mona_2_asic.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/mona_301_1_asic_48.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/mona_301_1_asic_96.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/mona_301_dsp.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/mona_361_1_asic_48.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/mona_361_1_asic_96.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/ea/mona_361_dsp.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/emu/audio_dock.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/emu/emu0404.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/emu/emu1010_notebook.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/emu/emu1010b.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/emu/hana.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/emu/micro_dock.fw exists in filesystem
alsa-firmware: /usr/lib/firmware/mixart/miXart8.elf exists in filesystem
alsa-firmware: /usr/lib/firmware/mixart/miXart8.xlx exists in filesystem
alsa-firmware: /usr/lib/firmware/mixart/miXart8AES.xlx exists in filesystem
alsa-firmware: /usr/lib/firmware/multiface_firmware.bin exists in filesystem
alsa-firmware: /usr/lib/firmware/multiface_firmware_rev11.bin exists in filesystem
alsa-firmware: /usr/lib/firmware/pcxhr/dspb1222e.b56 exists in filesystem
alsa-firmware: /usr/lib/firmware/pcxhr/dspb1222hr.b56 exists in filesystem
alsa-firmware: /usr/lib/firmware/pcxhr/dspb882e.b56 exists in filesystem
alsa-firmware: /usr/lib/firmware/pcxhr/dspb882hr.b56 exists in filesystem
alsa-firmware: /usr/lib/firmware/pcxhr/dspb924.b56 exists in filesystem
alsa-firmware: /usr/lib/firmware/pcxhr/dspd1222.d56 exists in filesystem
alsa-firmware: /usr/lib/firmware/pcxhr/dspd222.d56 exists in filesystem
alsa-firmware: /usr/lib/firmware/pcxhr/dspd882.d56 exists in filesystem
alsa-firmware: /usr/lib/firmware/pcxhr/dspe882.e56 exists in filesystem
alsa-firmware: /usr/lib/firmware/pcxhr/dspe924.e56 exists in filesystem
alsa-firmware: /usr/lib/firmware/pcxhr/xlxc1222e.dat exists in filesystem
alsa-firmware: /usr/lib/firmware/pcxhr/xlxc1222hr.dat exists in filesystem
alsa-firmware: /usr/lib/firmware/pcxhr/xlxc222.dat exists in filesystem
alsa-firmware: /usr/lib/firmware/pcxhr/xlxc882e.dat exists in filesystem
alsa-firmware: /usr/lib/firmware/pcxhr/xlxc882hr.dat exists in filesystem
alsa-firmware: /usr/lib/firmware/pcxhr/xlxc924.dat exists in filesystem
alsa-firmware: /usr/lib/firmware/pcxhr/xlxint.dat exists in filesystem
alsa-firmware: /usr/lib/firmware/rpm_firmware.bin exists in filesystem
alsa-firmware: /usr/lib/firmware/vx/bd56002.boot exists in filesystem
alsa-firmware: /usr/lib/firmware/vx/bd563s3.boot exists in filesystem
alsa-firmware: /usr/lib/firmware/vx/bd563v2.boot exists in filesystem
alsa-firmware: /usr/lib/firmware/vx/bx_1_vp4.b56 exists in filesystem
alsa-firmware: /usr/lib/firmware/vx/bx_1_vxp.b56 exists in filesystem
alsa-firmware: /usr/lib/firmware/vx/l_1_v22.d56 exists in filesystem
alsa-firmware: /usr/lib/firmware/vx/l_1_vp4.d56 exists in filesystem
alsa-firmware: /usr/lib/firmware/vx/l_1_vx2.d56 exists in filesystem
alsa-firmware: /usr/lib/firmware/vx/l_1_vxp.d56 exists in filesystem
alsa-firmware: /usr/lib/firmware/vx/x1_1_vp4.xlx exists in filesystem
alsa-firmware: /usr/lib/firmware/vx/x1_1_vx2.xlx exists in filesystem
alsa-firmware: /usr/lib/firmware/vx/x1_1_vxp.xlx exists in filesystem
alsa-firmware: /usr/lib/firmware/vx/x1_2_v22.xlx exists in filesystem
Errors occurred, no packages were upgraded.
> Does not compute_
https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584
https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584
- ncmprhnsbl
- DEV Team
- Posts: 3936
- Joined: 20 Mar 2012, 03:42
- Distribution: v5.0-64bit
- Location: australia
- Contact:
Sound not working
the firmware files in the alsa-firmware package are already in 000-kernel module(but not as a package, hence the 'exists in filesystem' messages)
and shouldn't be necessary, i think..
have you tried? : opening alsamixer (either via volume-icon(rightclick) or terminal)
1. is the 'master channel' muted(MM)? (m key to unmute)
2. is the correct hardware(sound card) selected (F6 to change) you generally don't want to use anything with HDMI in it)
and shouldn't be necessary, i think..
have you tried? : opening alsamixer (either via volume-icon(rightclick) or terminal)
1. is the 'master channel' muted(MM)? (m key to unmute)
2. is the correct hardware(sound card) selected (F6 to change) you generally don't want to use anything with HDMI in it)
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44
Sound not working
That make sense. I'd swear it worked before. Maybe with a previous kernel. (Using 4.14.16)ncmprhnsbl wrote: ↑11 Feb 2018, 02:14the firmware files in the alsa-firmware package are already in 000-kernel module(but not as a package, hence the 'exists in filesystem' messages)
and shouldn't be necessary, i think..
1. Yes I've tried. That trick remembers me of the old days with XFCE. (Also icons not keeping position in desktop, mixed cursor theme and other minor glitches)have you tried? : opening alsamixer (either via volume-icon(rightclick) or terminal)
1. is the 'master channel' muted(MM)? (m key to unmute)
2. is the correct hardware(sound card) selected (F6 to change) you generally don't want to use anything with HDMI in it)
2. I'm trying just the opposite --> Selecting HDMI Intel card.
Will do as you recommend.
Many thanks
> Does not compute_
https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584
https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584
- normalGuy
- Black ninja
- Posts: 52
- Joined: 06 Nov 2015, 23:36
- Distribution: porteus 3.2 xfce archBang
- Location: uk & portugal
Sound not working
yaourt -Syy alsa-firmware
With arch linux do not use partial updates:
pacman -Syu...partial upgrades are not supported. Do not use pacman -Sy package or any equivalent such as pacman -Sy followed by pacman -S package. Always upgrade (with pacman -Syu) before installing a package...
pacman -Syyu (after a pacnew list new mirrors )
pacman -S <package name>
Sound not working
Oh, I've missed your reply. Thanks for the advice. Will keep it in mind
> Does not compute_
https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584
https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584
- ncmprhnsbl
- DEV Team
- Posts: 3936
- Joined: 20 Mar 2012, 03:42
- Distribution: v5.0-64bit
- Location: australia
- Contact:
Sound not working
remember this is only true if you are using the changes cheatcode..
eg. if you update base packages live and then install something(and make a module) that depends on those updated packages and then reboot, those correct versions aren't there..
pacman -S will pull in the required dep(versions) anyhow, as will pman -S ..
you can also do pman -Syu which will make a module of the updated packages..
but this can get messy when there's: changes in the filesystem, package removals/replacements etc...
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44