libera/#devuan/ Thursday, 2023-12-21

_ds_“options snd-hda-intel id=PCH,HDMI index=0,1”, I think00:00
_ds_Reading further, looks like ‘id’ applies labels00:02
_ds_There are examples which use vid & pid, using the PCI IDs for the devices00:03
_ds_So maybe the USB audio example is closer to what's needed here.00:03
gnarfacei'm not sure00:03
gnarfaceCERAPIO: try "options snd-hda-intel id=PCH,HDMI index=0,1" first, but it might need to be something slightly different like "options snd-hda-intel id=PCH,HDMI index=1,0" or "options snd-hda-intel id=PCH,HDMI index=1,-1" ... we're not exactly sure00:04
_ds_0,1 or 1,0; the -1 is for next available card number00:05
gnarfaceah, hmm00:05
_ds_Output of “aplay -l | grep '^card'” would be useful (with the module options applied & active)00:07
* _ds_ notices that “aplay -l” also identifies connected monitors, which helps when identifying which HDMI audio device to use00:08
_ds_e.g. “card 1: HDMI [HDA ATI HDMI], device 10: HDMI 4 [Acer KG241 P]”00:09
_ds_CERAPIO, lspci -nn|grep '^[[:digit:]].*Audio'00:12
_ds_(safe to paste here; should be 2 lines of text)00:13
CERAPIOI restart and come back. Since I made the command that tells me left and right, from today I am hearing left and right00:13
gnarfaceCERAPIO: so it's working now?00:14
CERAPIO00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller [8086:160c] (rev 09)00:14
CERAPIO00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP High Definition Audio Controller [8086:9ca0] (rev 03)00:14
CERAPIOgnarface, no,00:15
onefangDamn aplay -l isn't identifying connected monitors here.  Would have been useful when I was trying to figure out which of the SIX sound devices my ONE graphics card has is actually hooked up to one of my TWO monitors, only one of which has speakers.  BTW the graphics card only has FOUR actual physical outputs, so no idea why it has SIX audio devices.00:18
gnarfaceonefang: i'm not seeing them either but i'm using the displayport->dvi cables instead of just hdmi->hdmi00:19
gnarfaceadapters could interfere00:20
_ds_onefang, could be a kernel thing (running 6.5.13 here)00:20
_ds_Ah, that might explain it00:20
gnarfaceoh, or that, i'm only on 6.100:20
_ds_HDMI to HDMI & DP to DP here00:20
_ds_Nothing to add interference00:20
gnarfaceCERAPIO: when you get that conf file right, "speaker-test -c 2 -t wav" should work right without needing the "-D hw:1,0" part00:21
gnarfacein fact i think it would stop working with the -D part, actually00:22
_ds_grep monitor_name /proc/asound/card*/eld*00:22
_ds_Well. “-D hw:0,0” (or “-D plughw:0,0”) would still work.00:22
onefangDisplayPort to DisplayPort (the monitor with the speakers) and HDMI to DVI.  6.1.0-0.deb11.13-rt-amd64 for my kernel, chimaera-backport.00:23
_ds_Locally-compiled kernel here00:24
onefang"grep monitor_name /proc/asound/card*/eld*"  Showed me my monitor name, the one with the speakers,  Wish I knew that last year.  lol00:24
_ds_In my case, eld#0.1 corresponds to card 1 device 7 and eld#0.4 to card 1 device 10 (available devices are 3, 7, 8, 9, 10).00:28
_ds_(and yes, the card has only 4 outputs despite the 5 audio devices).00:29
movedToDevuanOnMhello again.. after successfully moving from fedora to dev1 .. i see few drivers are missing from macbookpro00:34
movedToDevuanOnMfor* .. like sound drivers and facetime camera drivers00:34
movedToDevuanOnMhas any one ever experienced that accross distros?00:35
movedToDevuanOnMnow am in search of drivers for sound for this device..00:35
XenguymovedToDevuanOnM, I can't speak to your specific issue, but I find it hard to believe that fedora's software collection would be more comprehensive that Debian's (Devuan is based on Debian)00:36
movedToDevuanOnMfor this device - https://wiki.debian.org/InstallingDebianOn/Apple/MacBookPro/Early-2015-13-inch00:36
movedToDevuanOnMexactly.. i was shocked to find that out... but that i just figured it now that sound drivers are not installed00:36
XenguyRecommend you wait for the experts to arrive, it may take a little time, so please be patient : -)00:36
movedToDevuanOnMalso my keyboard volume keys arent working... i think that is also because those sound drivers..00:37
movedToDevuanOnMmost things worked out of the box wheneven i chose debian or ubuntu... this was shocking..00:38
XenguyI would guess that there is some package that needs to be installed, but again, idle in the channel and if anyone can help, they will, eventually00:38
XenguyWell Devuan *is* Debian, just without systemd, so hopefully there is a logical explanation, and also a solution : -)00:39
movedToDevuanOnMsure... few folks like mason and fsmithred already helped me out already during installation and went out for lunch/dinner i guess.00:39
XenguyGlad to hear it00:40
_ds_Volume keys should be returning appropriate key codes, at least00:40
movedToDevuanOnMi wish so...00:40
_ds_(keycode 121, XF86AudioMute; keycode 122, XF86AudioLowerVolume; keycode 123, XF86AudioRaiseVolume)00:40
movedToDevuanOnMactually only mute button is music control keys are displaying null symbol on gnome ... but vol up, down and mute doesnt show anything...00:40
_ds_GNOME's probably handling them, but without an audio device…00:41
movedToDevuanOnMon fedora ... they showed up volume meter and increasing and decreasing pop sound.... i am running gnome on both..00:41
movedToDevuanOnMalso.. an interesting find is that the gnome settings app on fedora allowed me to use my wifi as hotspot when am connected via ethernet... this was out of the box... but such option is not present in dev1 gnome00:43
movedToDevuanOnMand fedora was on latest kernel - 6.5 or 6.6.200 i guess.. and of course dev1 is on 6.100:43
movedToDevuanOnMmore close to latest*00:44
_ds_6.6.200? Unless 6.6 is an LTS kernel and is supported for years, there won't be a 6.6.200.00:44
fsmithredmovedToDevuanOnM, did you look at /etc/apt/sources.list to make sure that non-free-firmware is enabled?00:45
movedToDevuanOnMi played with xfce on dev1 .. i think sound wasnt picked up there as well...00:45
movedToDevuanOnMyes..00:46
movedToDevuanOnMdeb http://deb.devuan.org/merged daedalus main non-free-firmware00:46
movedToDevuanOnMdeb-src http://deb.devuan.org/merged daedalus main non-free-firmware00:46
fsmithredok00:46
fsmithredis network-manager installed?00:46
movedToDevuanOnMthis is up when i choose apt edit-sources00:46
movedToDevuanOnMnetwork-manager is already the newest version (1.42.4-1devuan1).00:46
movedToDevuanOnMas per apt output00:46
fsmithredok00:47
movedToDevuanOnMand it just set to manually installed when i tried to install it again00:47
fsmithredyou should add daedalus-security and probably daedalus-updates too00:47
fsmithredtaht message was telling you that you changed the status from Automatically installed to manually (you chose to install it)00:48
movedToDevuanOnMyes.. those 2 things are already the next part of the sources.list00:48
movedToDevuanOnMtrue..00:48
_ds_Using Xfce4 here. I have key bindings set up for audio volume (via the keyboard settings) using commands “amixer set Master toggle”, “amixer set Master 2%+”, “amixer set Master 2%-”00:49
fsmithredyou might need to add some other n-m package(s) to do the hotspot.00:49
_ds_(using plain ALSA here, and those commands affect the default audio device)00:49
movedToDevuanOnMbut was that for this machine - https://wiki.debian.org/InstallingDebianOn/Apple/MacBookPro/Early-2015-13-inch00:51
_ds_The volume control using amixer? That's generic.00:52
movedToDevuanOnMamixer00:53
movedToDevuanOnMamixer: Mixer attach default error: Host is down00:53
movedToDevuanOnMroot@dvn:~# alsamixer00:53
movedToDevuanOnMcannot open mixer: Host is down00:53
movedToDevuanOnMroot@dvn:~# amixer00:53
movedToDevuanOnMamixer: Mixer attach default error: Host is down00:53
_ds_pulseaudio? pipewire?00:54
_ds_(volume control for those is handled differently)00:54
_ds_Or maybe the problem's similar to CERAPIO's problem…00:55
_ds_– in which case, run “aplay -l” and see what it outputs00:56
movedToDevuanOnMthat worked... removed pipewire audio and install pulseaudio..00:58
movedToDevuanOnMthat magically made the keyboard buttons to work as well00:59
_ds_Could be that pipewire  just needed some configuration, but I've not really played with it (or with pulseaudio, for that matter)00:59
CERAPIO"speaker-test -c 2 -t wav", Playback open error: -112, The 'host' is not operational00:59
movedToDevuanOnMaplay -l gave me the same thing... when i had the issue..00:59
movedToDevuanOnMlol.. i thought cerapio is some other driver name01:00
CERAPIOjajajajaja01:00
movedToDevuanOnMi remember using pulseaudio and alsamixer on ubuntu before 5-6 years.. it always worked OOB01:01
CERAPIOi am skynet...01:01
movedToDevuanOnMnow for facetime camera01:01
movedToDevuanOnMthis is the one where i manually made it work on fedora..01:02
movedToDevuanOnMi doubt if this is available on debian01:02
movedToDevuanOnMhttps://github.com/patjak/facetimehd/wiki/Get-Started01:02
_ds_CERAPIO, looks like you've interpreted the error text into English literally – the correct text for error 112 (in English) is “Host is down”.01:04
_ds_(EHOSTDOWN, if you want the label for it)01:04
movedToDevuanOnMone other interesting shell behaviour b/w fedora and debian/dev1 ... on my user.. when am in a specific directory and then i switch to root user.. am in that same directory.. but on fedora.. am on the root - /root directory01:06
_ds_Sounds like “su -” to me01:07
movedToDevuanOnMyes01:08
_ds_Or “su” vs. “su -”01:08
* _ds_ wonders if the pipewire problem is one of the desktop environment, during startup, not starting it up01:11
movedToDevuanOnMlol.. rookie mistakes ... when copy pasting stuff to terminal.. just to find out that git command not found and make command not found errors...01:11
movedToDevuanOnMam pretty sure ... EFI and GRUB are the major problems that doesnt even allow DE to load even a bit01:12
movedToDevuanOnMand on that 6.6.200.. i think it was 6.6.0-200 something..01:14
movedToDevuanOnMsorry my bad01:14
_ds_Seems likely. Probably not even 6.6.0 but (then-)current 6.6.[latest]01:16
_ds_(probably 6.6.8 now)01:16
movedToDevuanOnMfinally most things are setup..01:23
movedToDevuanOnMi really like that wireless hotspot package.. i gotta find that out...01:24
movedToDevuanOnMoh yes.. one other thing that worked OOB for gnome on fedora is three finger swipe on trackpad to switch between workspaces... that thing is missing on debian/dev101:25
movedToDevuanOnMi gotta search it up...01:25
movedToDevuanOnMwow.. chatGPT is like... "you should figure out that you are missing out drivers" ...01:29
movedToDevuanOnMsuch a useful response -01:30
movedToDevuanOnMIt seems that you are encountering issues with missing drivers on your Linux system, particularly related to network connectivity. This can be a common challenge, but there are steps you can take to address it.01:30
movedToDevuanOnMChecking for Available Drivers01:30
movedToDevuanOnMFirst, it's important to identify the specific drivers that are missing. This can be done by checking the system logs or using diagnostic tools to determine which drivers are needed for your network hardware.01:30
movedToDevuanOnMInstalling Missing Drivers01:30
movedToDevuanOnMOnce you have identified the missing drivers, you can proceed with installing them. This typically involves obtaining the necessary driver packages and installing them on your system.01:30
movedToDevuanOnMTroubleshooting Network Connectivity01:30
movedToDevuanOnMAfter installing the missing drivers, you may need to troubleshoot network connectivity to ensure that the drivers are functioning as expected. This can involve checking network settings, verifying hardware connections, and testing network functionality.01:30
movedToDevuanOnMBy following these steps, you can address the issue of missing drivers and work towards restoring network connectivity on your Linux system. If you encounter specific error messages or challenges during this process, it may be helpful to seek assistance from the Linux community or support resources for your particular distribution.01:30
movedToDevuanOnMRemember, addressing missing drivers is an important aspect of maintaining a well-functioning Linux system, and with the right approach, you can overcome these challenges and ensure reliable network connectivity.01:30
_ds_CERAPIO, just been testing on a laptop which has HDMI output as card 0 – I've used01:50
_ds_options snd-hda-intel index=1,0 id=HDMI,PCH01:50
_ds_to swap them over and label them (first card, index 1, “HDMI”; second card, index 0, “PCH”) – “aplay -l” will show these labels01:50
_ds_And it is enough to run “modprobe -r snd-hda-intel; modprobe snd-hda-intel” (as root) to apply the new settings.01:51
movedMacToDev1helloo there...09:20
movedMacToDev1thanks for helping me to install dev1 yesterday on a macbook09:21
movedMacToDev1i now see that some of the fonts that i need in my local language are missing on system fonts due to which the browser isnt displaying it when i visit local sites. on checking about font installation, i see font-manager was needed to be installed and so i did that and that app allowed me install fonts of my locale - but browser still doesnt pick up09:23
movedMacToDev1those fonts... how do i debug this ?09:23
movedMacToDev1hmm... ok browser automagically picked up the fonts after sometime and renders it well..09:23
movedMacToDev1i wanna install this browser https://librewolf.net/installation/debian/ because https://privacytests.org/ ... but the second line of their script identies this distro as based out of focal  and not of bookworm .. how do i fix that lsb_release09:30
movedMacToDev1hmm.. ok... i overrode that script and manually assigned it to value bookworm... but i get GPG error on the repo -09:34
movedMacToDev1Reading package lists... Done09:34
movedMacToDev1W: GPG error: https://deb.librewolf.net bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D29FBD5F93C0CFC309:34
movedMacToDev1E: The repository 'https://deb.librewolf.net bookworm InRelease' is not signed.09:34
movedMacToDev1hmm.. i went through the flatpak way and made a workaround09:44
movedMacToDev1wow... flatpak says it installed the browser but it isnt listed in gnome applications09:52
movedMacToDev1had to launch the app via terminal lol10:03
Wonkahttps://yiff.life/@koko/111618932283595363 - hihi17:45
truckhmm; is openssh 9.6p1-1 likely to be produced for daedalus?20:38
fsmithredtruck, probably not. Daedalus is stable so no new versions - just security and bug fixes.20:47
fsmithredsecurity patches usually get backported to stable release.20:48
Nietzmeetup21:07
truckthat's why I asked - as this _is_ a security update.21:10
truckit'll probably show in ... a few days, I suppose. After it's been declared "ok" in debian sid.21:11
truckjust trying to plan outages during the holidays (:21:11
rwptruck, Stable gets security upgrades okay.  But it does this by backpatching vulnerabilities into the release.21:13
rwpOpenSSH 9.2p1 in Stable daedalus has already had several security patch releases for various vulnerabilities.  But those were patched into 9.2p1.21:13
rwpThe entire purpose of doing things this is way is produce Stable a stable behavior release.  Upgrading to the latest upstream for everything would produce a rolling release.21:14
rwpRolling releases are by definition not Stable.  If you want a rolling release then don't use Stable but then you can't complain when changes happen at unexpected times and breaks things.21:16
truckmmm-hmm.21:26
truckso, this vulnerability - just ignore it then?21:27
truckdespite the mitm possibility in data centers where you don't have physical access?21:27
truck(my stable openbsd boxes recieved a patch already, but one could expect that as they _develop_ openbsd.)21:29
truckI am also familiar with https://security-tracker.debian.org/tracker/source-package/openssh which shows the various items that are still vulnerable. It's going to be a few days of patching things.21:31
truckI am just trying to _plan_ the updates over the holidays. If you don't want to patch _your_ critical systems, that's on you (:21:32
unixman_homeRisk really depends on the DC in question, truck. If it is a DC with shared resources for the public, such as AWS and so on, then the risk is likely higher. If it is a closed DC in a corporation, then the risk is relatively low. Unless a bad guy is already in the network, but then one already has a problem.21:34
truckyeah. sadly, it's "cloud" style. I would certainly prefer it being in house, like it was once... but you know. "management."21:35
unixman_homeBean counters will ruin us all. ;)21:35
truckI'll check various openbsd/ssh areas and see if someone is backporting this to earlier versions, but I have a feeling that may happen _after_ Christmas. Which, well, is probably ok.21:36
truckappreciate the information on the likelyhood.21:37
rwpThe reason there is that CVE tracker is so that everyone, users and developers, can track the flow of security patches through the system.21:42
rwpWhich specific CVE are you concerned about here?21:42
rwpAs I am reading things the primary thing you are not happy about is the speed at which security patches are flowing through the system.  Is that right?21:42
truckNo. It's planning the outages for when the patch _is_ available.21:50
truckas it will be, sometime "soon."21:50
truckCVE-2023-48795 (aka Terrapin.)  You're familiar, yes?  (:21:51
truckif not: the release notes from openssh are fairly easy to read.21:53
truckthere's a new "strict KEX" protocol extension.21:53
truckthis isn't... well, you DO need a MITM to exploit it, so, for many folks, as unixman pointed out, it's not AS likely.21:54
truckso: I _expect_ in the coming days, which are holidays... we'll have a patch - and folks will be pushing for it to be applied. I'm trying to anticipate if I'll be patching on any holidays (:21:55
truck- and yes, this realization that we weren't patched came AFTER I upgraded several things, and used the provided scanner, which reported "still vulnerable."  I did NOT expect that.21:56
truckwent to find out why, found the reason - "ah, we are still using an older version, that makes sense. I wonder if we'll get a backport, or if it will be suggested that we move to the new version instead of keeping the old version."21:57
rwpI have also been having a hard time understanding the concept of "outage" in regards to this upgrade for openssh-server.  Which should have fractional seconds of downtime when applied.  I don't schedule downtime for such upgrades.  I simply notify a window of time when upgrades are going to be applied and then do them then.21:57
truckso: no, I am not _complaining_ about speed of updates. I understand that the version that is in stable hasn't been patched with the new KEX extention. It likely _won't_ be.21:58
truckgiven that beancounters and people who panic about things they don't fully understand may see the news reports, and as this is yet another "security vuln with it's own website and cute logo" ...21:58
rwpCVE-2023-48795 as described by the OpenSSH developers is of very limited nature.  As described in the release notes.21:58
truckyes. it is. and, as I just noted, for you and I, that's something we can mitigate - MOSTLY.21:59
truckthe MITM part in the cloud - not so much.21:59
trucknow, pretend you're a beancounter or manager who doesn't do tech, but does see news items and gets worried; they may issue some sort of "OMG! DID YOU PATCH?" email to folks.21:59
truckand may require emergency work to be scheduled, even on holidays.22:00
rwpI have gone head-to-head with people who are reacting to inflated news reports but did not understand the problem.  And while I was gentle I was also firm that they did not understand the problem.22:00
truckI imagine you have. Especially given your responses to me.22:01
rwpAnyway...  Let's feel free to continue this discussion/rant/chat in #devuan-offtopic instead of here.22:01
truckyeah, that would work. We know the answer - "when it happens, it happens, there is nothing indicating it would happen before Christmas."22:02
rwpYou are always free to compile up OpenSSH yourself and then keep it updated as a Rolling Release yourself for just that one service.  No reason not to do it!  Just say'n...22:02
trucknaw, I'd apply the 'sid' (I forget our codename for sid) version first.22:04
truckI could pin that. I just don't think that's a particularly ... good idea.22:04
golinuxceres22:35

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!