| golinux | Looks good. | 00:01 |
|---|---|---|
| critr | update on the jackd problem i'm having. it has nothing to do with devuan. jack just doesn't like my mobo. | 07:37 |
| gnarface | critr: you think maybe it can be traced back to a alsa driver issue? | 07:38 |
| critr | gnarface: i don't know, but i tried a 6.4 kernel and even that didn't work. | 07:40 |
| gnarface | what does "speaker-test -c 2" do? | 07:40 |
| gnarface | critr: ^ (without pulseaudio or jackd or pipewire or esd or arts anything like that running) | 07:42 |
| critr | as a non-root user it runs and gives me some hissing as it alternates between speakers. | 07:43 |
| critr | by the way, normal sound works fine. | 07:43 |
| gnarface | just a small sanity check, since it's possible for "normal sound" to work "fine" in several cases where the driver is still misbehaving in some way that sabotages expected behavior for some programs but not others | 07:45 |
| gnarface | to be specific, you just ran "speaker-test -c 2" and you didn't need to specify any other parameters like the "-D hw:0,0" or such? | 07:46 |
| gnarface | ... and you don't have any custom alsa config in /etc or ~/.asoundrc right? | 07:46 |
| gnarface | (often, in such cases, it's possible to patch around the driver misbehavior with a small amount of alsa config customization but it's important that if you do that, it's complete) | 07:48 |
| critr | i ran the exact command as given. i haven't modified anything sound related on this new devuan install. | 07:48 |
| critr | i do notice that service --status-all shows "alsa-utils" with a qustion mark. | 07:49 |
| gnarface | ok. just making sure. the reason i'm asking is because while it seems possible that jack could be allergic to your motherboard, the way i understand jack works means it's very likely to actually be a problem with your alsa driver, and likely to be something it's doing wrong specifically | 07:49 |
| gnarface | ... and that would be very common if you're using the highly ubiquitous "snd-hda-intel" driver | 07:50 |
| critr | i see. well, i'm listening carefully. | 07:50 |
| gnarface | well the speaker test command suggests its working right, but i'm guessing you need to make sure input and output works simultaneously | 07:51 |
| gnarface | and probably at the right channel-counts | 07:51 |
| critr | i notice that alsa-mixer has three devices, two of which seem to be spdif. the third one works properly for setting levels and turning things on and off. | 07:52 |
| gnarface | snd-hda-intel covers a wide variety of barely related hardware and is supposed to auto-detect the hardware on load but often sneakly fails just partially and picks something that's not an exact fit | 07:52 |
| gnarface | hmmm, are the spdif ones first in the listing order? | 07:53 |
| critr | 1 and 2. | 07:53 |
| gnarface | those are digital outputs, it's unlikely you want to use those for this, and many things will default to whatever is the first in the list | 07:53 |
| gnarface | by "1 and 2" you mean they're the first and second? (the list actually starts at #0) | 07:54 |
| gnarface | check with these commands both: aplay -l arecord -l | 07:54 |
| critr | if i start jack with jackd -dalsa -dhw:2 it seems to run but still doesn't appear for programs that look for it. 0 and 1 refuse to work. | 07:55 |
| gnarface | ok, so my first guess is you need to move #2 to #0 | 07:55 |
| spine-o-saurus | hey how do i get some program to look for includes at /opt? | 07:56 |
| gnarface | then defaults may start behaving as expected if nothing else is also wrong | 07:56 |
| critr | yes, in alsa-mixer, the two with spdif are the first and second. | 07:56 |
| gnarface | spine-o-saurus: usually with a environment variable supplied at build time | 07:56 |
| gnarface | spine-o-saurus: or a command-line parameter | 07:56 |
| gnarface | critr: make sure you have these packages, just to be sure: alsa-tools alsa-topology-conf alsa-ucm-conf alsa-utils | 07:57 |
| gnarface | critr: if you had all of those already, verify your audio driver for hw:2 is different from the one for the other two, and if so just pass "index=0" to the module at load time. | 07:58 |
| critr | ok | 07:59 |
| gnarface | critr: (assuming the driver does support the "index" parameter... i'm not sure they all actually do but the snd-hda-intel one does) | 07:59 |
| critr | the other two devices are the hdmi audio on my gpu and i think the audio provided by the cpu. | 08:00 |
| gnarface | critr: did you have all those alsa packages already? i'm not 100% sure that alsa-ucm-conf or alsa-topology-conf wouldn't fix this automatically | 08:00 |
| critr | i didn't have alsa-tools | 08:01 |
| spine-o-saurus | oh now its building | 08:01 |
| gnarface | spine-o-saurus: you found the environment variable and/or command-line flag for includes? | 08:02 |
| gnarface | critr: eh, that one might not matter as much for boot-time auto-config | 08:02 |
| gnarface | critr: not sure though | 08:02 |
| critr | i'm installing qsynth to see if it made a difference... | 08:03 |
| gnarface | critr: a reboot might be in order after screwing with this stuff. shouldn't be necessary but might be easier | 08:05 |
| critr | nope, unfortunately not. however, what you siad about trying to get the mobo sound to 0 is worth looking into.. | 08:05 |
| gnarface | (i'm not sure if you can change the device order without unloading all the modules) | 08:05 |
| gnarface | (so it might be easier to just set index=0 then reboot) | 08:05 |
| critr | i installed mx to see if it would work with a 6.4 kernel, and mx lets you choose the default sound device. so i chose the mobo sound as default, and that didn't work either. | 08:07 |
| critr | ok, how do i set index=0? | 08:08 |
| critr | i think i see how on superuser.com... | 08:13 |
| gnarface | critr: add a file in /etc/modprobe.d/ with a name that ends with ".conf" and inside that just put this one line: options snd_hda_intel index=0 | 08:18 |
| gnarface | (assuming "snd_hda_intel" is your actual alsa driver; substitute your actual driver for that otherwise) | 08:19 |
| gnarface | you can check if the parameter is actually supported by the module by checking the output of: /sbin/modinfo -p [module name] | 08:20 |
| gnarface | this is assuming the digital outs aren't just piggybacking on the same driver. if they are, you'll have to address this with a alsa config instead | 08:24 |
| critr | i assume i'll have to reboot after writing this conf file? | 08:27 |
| critr | bbiab | 08:27 |
| gnarface | critr: for the /etc/modprobe.d/*.conf file? strictly speaking, no, but for this particular task it's easiest. | 08:27 |
| gnarface | ...since otherwise you'd have to unload ALL the alsa modules first | 08:28 |
| critr | gotcha.... | 08:28 |
| gnarface | hmm, do you have to update ... | 08:28 |
| gnarface | wait, i'm not sure you don't have to update the initramfs too... | 08:28 |
| gnarface | well i guess we'll find out | 08:28 |
| spine-o-saurus | this is production, we never guess | 08:37 |
| gnarface | does anyone remember if /etc/modprobe.d/ gets read into the initrd.img? | 08:42 |
| gnarface | not sure it would matter for sound drivers either way, but for some reason my memory says both are true | 08:43 |
| gnarface | that can't be right | 08:43 |
| tom2023 | Hi all . I would be grateful for advice. I tried to install qemu and saw that after turning on my interface (eth0) is turned on , how can I make sure that after each turn on qemu my interface is turned off? | 10:42 |
| tom2023 | I checked on another distro where the interface is turned off | 10:42 |
| spine-o-saurus | the OS configuration determines if the interface is on or off | 10:50 |
| tom2023 | < spine-o-saurus> hello , that is in Devuan is included ? Well, why then does it not turn on on real hardware? | 10:55 |
| spine-o-saurus | what command did you use to lauch qemu? | 10:57 |
| tom2023 | like this qemu-system-x86_64 -hda devuan.qcow2 -m 2048 -smp 2 -enable | 11:00 |
| tom2023 | like this qemu-system-x86_64 -hda devuan.qcow2 -m 2048 -smp 2 -enable-kvm | 11:00 |
| spine-o-saurus | -netdev script=no Use the network script file to configure it and the | 11:05 |
| spine-o-saurus | network script dfile to deconfigure it. If name is | 11:05 |
| spine-o-saurus | not provided, the OS automatically provides one. The | 11:05 |
| spine-o-saurus | default network configure script is /etc/qemu-ifup and the default network deconfigure script is /etc/qemu-ifdown. Use script=no or downscript=no to disable script execution | 11:05 |
| tom2024 | like this qemu-system-x86_64 -hda devuan.qcow2 -m 2048 -smp 2 -enable-kvm | 11:12 |
| tom2024 | sorry left the chat by accident | 11:12 |
| gnarface | tom2024: you were pasted a section from the man page about the "-netdev" command-line option | 11:15 |
| gnarface | i'm not gonna paste it, it should be easy to find | 11:16 |
| onefang | But then tom2024 left the chat by accident seven seconds later, probably didn't get a chance to read that. | 11:16 |
| onefang | He's not having much luck with his chat connection. | 11:17 |
| onefang | And I'm about to eat dinner soon. | 11:17 |
| gnarface | i think that paste may be partially mangled... | 11:17 |
| leafwiz | Hey, I'm trying to upgrade my testing install to excalibur. But my kernel install fails. https://pastebin.com/zpeh6U0x - "dkms autoinstall on 6.4.0-2-amd64/x86_64 failed for rtl88x2bu(10)" | 21:23 |
| leafwiz | Anyone know what I can do to repair this? | 21:24 |
| rwp | leafwiz, Your build for that module failed. The failure should be logged here: /var/lib/dkms/rtl88x2bu/5.13.1/build/make.log | 22:52 |
| rwp | What does it say the problem is there? | 22:52 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!