libera/#devuan/ Friday, 2022-10-07

NeverAlonemodprobe iwlwifi?00:03
NeverAloneOh yesh00:04
NeverAlone* Oh yeah00:05
rwpI think the difference between "insmod filename" and "modprobe modulename" is what is actually the problem FilipZ1 was experiencing.02:04
* u-amarsh04 wonders how messed up things need to be before even the magic sysreq reboot key sequence fails03:26
xrogaanUnpacking dbus (1.12.24-0+deb11u1) over (1.12.20-2+devuan2) ...08:51
xrogaanis this a problem?08:51
Jorilxrogaan: Not an expert, but that doesn't look good09:04
xrogaandbus was forked by devuan, forgot why.09:05
brocashelmare you using a debian repository containing that version of dbus?09:05
xrogaanyeah, security.09:06
brocashelmotherwise, i always get the forked versions of packages09:06
brocashelmfor testing?09:06
brocashelmif so, then i would try apt pinning to prefer the devuan versions09:07
JorilJust asked on #devuan-dev, let's see09:07
xrogaanbrocashelm:  https://lists.debian.org/debian-security-announce/2022/msg00219.html09:07
xrogaanJoril: they're usually right here too :)09:07
brocashelmi just updated and i have the 1.14.4-1devuan1 version09:09
brocashelmon ceres/unstable09:09
Unit193What's the top two entries in /usr/share/doc/dbus/changelog.gz (or changelog.Debian.gz) say?09:09
xrogaanI'm running stable.09:09
brocashelmthen that's a problem09:09
brocashelmi thought this was on testing09:10
xrogaanUnit193: IDK why you ask -> dbus (1.12.24-0+deb11u1) bullseye-security; urgency=medium09:10
u-amarsh04I had some problems with dbus packages at 1.14.4-1devuan1 and running a Linus git head kernel so I've gone back to 1.14.2-1 (non-Devuan as I don't know the Devuan snapshot repository address)09:18
u-amarsh04doing a restart into a newer kernel so if replying wait until I get back in09:18
u-amarsh04back with bleeding edge kernel and non-Devuan 1.14.2-1 dbus09:27
xrogaanI believe the fork is just about machine-id: https://bugs.devuan.org/cgi/bugreport.cgi?bug=30409:37
u-amarsh04thanks xrogaan09:39
xrogaanI'm not sure though.09:39
xrogaanCould also be to make extra sure that systemd is gone.09:39
u-amarsh04although I normally run unstable, I'll avoid dbus 1.14.4-1devuan109:43
xrogaanI have to sleep. If possible, could somebody post the dbus business on the ML? My brain is really starting to fail.09:43
FilipZ1So this issue happened again, and trying to fix it at least temporarily, I unloaded the iwlwifi and one somehow related driver. First, I tried modprobe -r iwlwifi, and got an error saying that it is in use, so I tried with rmmod iwlwifi, and then I got an answer that it is in use by iwlmvm, so I did rmmod iwlmvm succesfully, and then rmmod iwlwifi.10:31
FilipZ1Then I tried to load it again with modprobe. First with iwlmvm, and then iwlwifi. Then I tried ifup wlan0, but then the same error as before got returned. Therefore I have 2 questions:  1. What more could I do to functionally reset it, without restarting the entire system, so the effect could be the same, and I could at least temporarily resolve10:31
FilipZ1this issue with commands? 2. What exactly is for, the iwlmvm driver, described as "The new Intel(R) wireless AGN driver for Linux"? I tried to search info about this, but failed.10:31
___usedA 5.x kernel appeared in backports for Beowulf this week, then disappeared. What's the story behind that, besides it lit up a lot of packages red in aptitude when selected for upgrade. I deselected it.17:47
___used?18:39
___usedIt was not the Intel GPU/display killer 5.19.12 right?18:40
___usedhttps://www.theregister.com/2022/10/06/intel_linux_gpu_laptop_displays/ ref:18:40
onefangAlso reported by other tech news sites.18:41
___usedI was asking about the vanishing kernel in Beowulf backports, was it this one or another? It was 5.19.x for sure.18:41
onefangDunno, I didn't see it.18:41
onefangIt would have come and gone on the Debian infrastructure side of things, which I don't have visibility into.18:42
ltsNothing here https://tracker.debian.org/pkg/linux/news/18:50
onefangThough I'm on chimaera, using chimaera-backport kernel, which is currently 5.18.16-1~bpo11+1 so I doubt beowulf-backport would be getting 5.19.12.18:53
___usedIt might have been 5.19.1219:01
Rosie60Hi, wit debian going non-free will devuan remain free as in freedom?20:01
Rosie60*by deafult20:01
XenguyRosie60, Devuan already went over to the dark side  = )20:02
Rosie60:(20:02
Rosie60do you mean by live distro20:02
XenguyIf you want to avoid non-free during install, use 'expert' install and you will be given that option20:02
fsmithrednonfree firmware is in the isos.20:03
XenguyI don't know about Live20:03
fsmithredwhat Xenguy said20:03
fsmithredthe live isos have wireless firmware installed already. There is a script to remove it, and non-free is not in sources.list.20:03
Rosie60yeah so the option to remove blobs will remain20:03
fsmithredyes20:03
Rosie60oh that's probably the best option20:03
Rosie60thx, y'all as community are so useful <320:04
fsmithredif it's not included, we get lots of support requests for getting wireless working20:04
gnarfaceanyone happen to know how to successfully pass a usb device through to a qemu guest? i've got it showing up when i type "info usbhost" at the qemu "monitor" shell but it does not show up in the output of lsusb inside the guest21:12
rwpgnarface, Using libvirt's virt-manager?  (It's a menu pick item.)  Or doing it completely manually?  (No idea.)21:44
hagbardWhat's the deal with changelog from the devuan repositories? I get "This change is not coming from a source that supports changelogs. Failed to fetch the changelog for libdbus-1-dev URI was empty" when trying to download those with synaptic."22:16
___usedHistory has been erased ;)23:21

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