elderK has quit [Quit: Connection closed for inactivity]
groovy2shoes has quit [Ping timeout: 240 seconds]
groovy2shoes has joined #crux
_moth_ has quit [Ping timeout: 240 seconds]
ppetrov^ has joined #crux
<ocb>
anyone using some setup to decrypt ssl/tls and filter malicious (ddos) traffic based on specific string before forwarding to backend app
Guest72 has joined #crux
Guest72 has quit [Client Quit]
pedja has joined #crux
volgk has joined #crux
groovy2shoes has quit [Remote host closed the connection]
groovy2shoes has joined #crux
_moth_ has joined #crux
_whitelogger has joined #crux
tilman has quit [Ping timeout: 256 seconds]
tilman has joined #crux
emmett1 has joined #crux
_moth_ has quit [Remote host closed the connection]
_moth_ has joined #crux
<frinnst>
firefox-bin is laggig a bit
_moth_ has quit [Remote host closed the connection]
_moth_ has joined #crux
emmett1_ has joined #crux
emmett1 has quit [Read error: Connection reset by peer]
volgk has quit [Quit: Client closed]
_moth_ has quit [Remote host closed the connection]
_moth_ has joined #crux
_moth_ has quit [Remote host closed the connection]
_moth_ has joined #crux
_moth_ has quit [Remote host closed the connection]
_moth_ has joined #crux
_moth_ has quit [Remote host closed the connection]
_moth_ has joined #crux
ivandi has quit [Quit: WeeChat 3.4]
ivandi has joined #crux
nepie has joined #crux
<nepie>
hello, i am trying to get sound working on my system
<nepie>
anyone can point me in the right direction?
<ppetrov^>
are you using pulseaudio?
<nepie>
i just installed alsa-tools so i think i am using alsa...
<nepie>
i assume, i shoud start by verifying that crux can see my sound card. what is a good way to do it?
<ppetrov^>
well, i configured pulseaudio, since i need bluetooth
<ppetrov^>
try
<ppetrov^>
alsaconfig? if that was the tool name
<ppetrov^>
no
<ppetrov^>
alsamixer
<ppetrov^>
check if things are not muted, put volumes up where necessary. Then, if i remember right: alsactl store
<ppetrov^>
you sure you built your sound card's driver?
<nepie>
i am not sure i built sound cards driver. how can i verify that?
<stenur>
just to mention i use bluealsa which works gracefully in the meantime. (Even with my shitty TV that is.)
<stenur>
and apulse for firefox-bin. Ditto.
<stenur>
..Of course.. only one output device via bluetooth.
<stenur>
..and i stop/start dnsmasq, bluez and bluealsa in my zzz hook before/after LID close; i have seen problems with 5.10 otherwise.
<stenur>
But, hey! Kernel 5.15 of my rtw_8822be Realtek shared wifi/bluetooth is _so_ much better than 5.10!
<stenur>
I can play music while doing downloads, the downloads to not stall to 0, the music does not stutter (only during DHCP packets when associating).
<stenur>
It has improved so much with so few lines of code (once i looked last) that i wondered why the Realtek employees (i think) that write this driver have not ported the few improvements back to 5.10 despite quite some bug reports of more than just me. They did not even speak on Bugzilla.
<stenur>
And "Go Go Godzilla" was Japanese instead, no? Hm.
<stenur>
nepie: look at dmesg(1) output
<stenur>
nepie: look at lspci(1) output
<stenur>
Eh, lspci(8)
<stenur>
For example: lspci |grep -i audio
<nepie>
i don't have errors in dmesg and lspci reports audio devices
<stenur>
And with -vv you see which kernel driver is in use, here it is: lspci -vv |grep -A10 -i audio
<stenur>
And there i see: Kernel driver in use: snd_hda_intel
<pedja>
or 'lspci -k'
<stenur>
..even better
<pedja>
does CRUX has inxi or hwinfo ports these days?
<stenur>
Just yesterday i did three hours of searching the balkan pissbox; i hate it; wc -l src/.PEDJA -> 23 src/.PEDJA
<nepie>
i get that driver in use is snd_hda_intel on my system
<nepie>
so i assume my sound card is installed
<nepie>
i did get alsalib version error when trying to install alsa-utils
<stenur>
If nothing is in these 69 hours i must have missed it once again. I swear i got that oh so often fifteen years ago when that "yugoslavian" woman lived in this house, she liked it.
<stenur>
well then compile it anew; just did that Saturday rest Monday to step anything to glibc 2.34, it is working here.
<stenur>
'Had binaries from April 2019, CRUX 3.5?, still.
<stenur>
But all working, thanks to the monster that is library symbol versioning i presume.
<pedja>
nepie, what's the output of 'aplay -l'?
<pedja>
that should list the sound devices alsa sees, iirc
<stenur>
And have you called alsaconf? I think that it was, it needs to initialize itself.
<stenur>
And have you started the alsa port?
<nepie>
aplay -l displays a list of devices. sorry, not sure how to copy and paste in xterm
<pedja>
don't paste here, use a paste site, share the link
<nepie>
i just installed alsaconf. not sure how to start alsaport
<stenur>
prt-get info alsa
<stenur>
/etc/rc.d/alsa start
<nepie>
hey!! i am getting somewhere. i initialized alsa and now my alsamixer is showing info
<nepie>
alsaconf does not find any cards...
<pedja>
so which info is alsamixer showing then?
<nepie>
sorry, having difficulties pasting.
<nepie>
alsamixer shoing coexant card but it is in the second position after hdmi.
<nepie>
i created defaults.pch.card 1 and defaults.hdmi.card 0 in asound.conf
<nepie>
restarted alsa but default is not being picked up. do i need to restart my system?
<stenur>
no
<stenur>
ctl.!default { type hw; card 0; }
<stenur>
ditto pcm.!default
<stenur>
restarting never
<stenur>
asound.conf is a terrible undocumented mess. Unfortunately!
<pedja>
I've been using pulseaudio for so long I forgot about the whole alsa config mess :)
<stenur>
It is also an ALSA fault that bluealsa can use one device only
<stenur>
I always hated that concept of audio going app->kernel->server->kernel if all i need is possibly adjustment of frequency/bitrate
<nepie>
ctl says event not found; i type ctl.!default {pch; card 1;}
<stenur>
What is pch?
<pedja>
'pcm' typo, I presume :)
<stenur>
I also have pcm.hda_intel { type hw; card 0; }
<stenur>
Alsa is too native, a "type plug" cannot be used by "type dmix" because dmix uses the hardware timers of the underlaying device which (thus) must be "type hw".
<stenur>
And without a "dmix" only one program ever can use the device. What a pity.
<stenur>
nepie: http://ix.io/2QzX is my /etc/asound.cnf; super primitive as i have no idea, but it works just fine in practice, no clicks no stutters regardless how high the load; less bluetooth audio which goes many ways through bluetooth, it can show delays at load averages of 10.0 and above.
<stenur>
(I can set $ALSAPCM environment variable to switch the default device to say "bt", or "xmix".
<nepie>
thank you all for your help. i have a work thing. catch you all later.
<stenur>
That is actually all i know of Alsa.
<stenur>
Oh. With my last breath.
<stenur>
Think i can go peel potatoes for animal friends :)
ppetrov^ has quit [Quit: Leaving]
emmett1_ has quit [Ping timeout: 250 seconds]
<nepie>
thank you again #stenur & #ppetrov; very grateful for your help