2023-12-12.log

minutejosch: ok :300:03
- mjw (QUIT: Ping timeout: 256 seconds) (~mjw@gnu.wildebeest.org)00:12
- S0rin (QUIT: Ping timeout: 255 seconds) (~S0rin@user/s0rin)00:16
+ S0rin (~S0rin@user/s0rin)00:16
- sevan (QUIT: Quit: upgrade) (~sevan@user/venture37)00:18
- S0rin (QUIT: Ping timeout: 268 seconds) (~S0rin@user/s0rin)00:50
+ S0rin (~S0rin@user/s0rin)00:53
- mtm (QUIT: Ping timeout: 246 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)01:02
hramracher, bluetooth01:31
hramrachI found blueman does not work for whatever reason and bluetoothctl is needed instead01:33
hramrachalso the service is not automatically started, and sometimes the device isn't01:33
hramrachnever used BT since I got a proprietary protocol RF dongle that just works01:39
hramrachsome standards are just bad01:39
- colinsane (QUIT: Quit: bye) (~colinunin@97-113-159-4.tukw.qwest.net)01:43
+ colinsane (~colinunin@97-113-159-4.tukw.qwest.net)01:49
- eibachd (QUIT: Ping timeout: 240 seconds) (~eibachd@p200300dcf7231c00dd202e0c390dcc5f.dip0.t-ipconnect.de)02:22
+ eibachd (~eibachd@p200300dcf7231c001b92a6b843690591.dip0.t-ipconnect.de)02:23
- jacobk (QUIT: Ping timeout: 240 seconds) (~quassel@utdpat241106.utdallas.edu)02:46
- nsc (QUIT: Ping timeout: 252 seconds) (~nicolas@i5E86127F.versanet.de)03:08
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)03:09
+ nsc (~nicolas@154-121-142-46.pool.kielnet.net)03:10
+ jacobk (~quassel@129.110.242.173)03:12
+ skeletronix2 (~skeletron@p200300d70f2b9100dccf75bcb601b1b4.dip0.t-ipconnect.de)03:25
- skeletronix1 (QUIT: Ping timeout: 256 seconds) (~skeletron@p200300d70f024800dccf75bcb601b1b4.dip0.t-ipconnect.de)03:28
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20)03:50
- jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@129.110.242.173)03:52
+ jacobk (~quassel@utdpat242093.utdallas.edu)04:28
- jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@utdpat242093.utdallas.edu)04:37
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20)05:12
- S0rin (QUIT: Ping timeout: 256 seconds) (~S0rin@user/s0rin)05:44
+ S0rin (~S0rin@user/s0rin)05:50
- GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon)06:59
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)06:59
- anzu (QUIT: Ping timeout: 246 seconds) (~anzu@melkki.cs.helsinki.fi)07:04
+ anzu (~anzu@melkki.cs.helsinki.fi)07:04
+ jacobk (~quassel@utdpat241033.utdallas.edu)07:56
- eibachd (QUIT: Ping timeout: 260 seconds) (~eibachd@p200300dcf7231c001b92a6b843690591.dip0.t-ipconnect.de)08:03
+ eibachd (~eibachd@2a01:599:215:5c6d:790c:2a36:99ff:2b14)08:03
- colinsane (QUIT: Ping timeout: 252 seconds) (~colinunin@97-113-159-4.tukw.qwest.net)08:39
+ colinsane (~colinunin@97-113-159-4.tukw.qwest.net)08:52
- jacobk (QUIT: Ping timeout: 268 seconds) (~quassel@utdpat241033.utdallas.edu)09:03
- skeletronix2 (QUIT: Read error: Connection reset by peer) (~skeletron@p200300d70f2b9100dccf75bcb601b1b4.dip0.t-ipconnect.de)09:09
- mlarkin (QUIT: Ping timeout: 252 seconds) (~mlarkin@047-036-115-056.res.spectrum.com)09:18
+ mlarkin (~mlarkin@047-036-115-056.res.spectrum.com)09:25
- eibachd (QUIT: Read error: Connection reset by peer) (~eibachd@2a01:599:215:5c6d:790c:2a36:99ff:2b14)09:25
+ eibachd (~eibachd@p200300dcf7231c00c9ef7948f2906687.dip0.t-ipconnect.de)09:26
Boostisbetterhramrach: You are totally right. Bluetoothctl, while SUPER clunky got it working. The mouse paired with no problem. I'm not really wanting to use a mouse, just seeing if this bluetooth dongle works on the Reform. 10:09
BoostisbetterIt does. 10:09
+ mjw (~mjw@gnu.wildebeest.org)10:15
- mtm (QUIT: Ping timeout: 260 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)13:02
- eibachd (QUIT: Ping timeout: 256 seconds) (~eibachd@p200300dcf7231c00c9ef7948f2906687.dip0.t-ipconnect.de)13:34
+ eibachd (~eibachd@p200300dcf7231c007b057467ff8ebe1e.dip0.t-ipconnect.de)13:35
- mjw (QUIT: Ping timeout: 264 seconds) (~mjw@gnu.wildebeest.org)14:01
- eibachd (QUIT: Ping timeout: 256 seconds) (~eibachd@p200300dcf7231c007b057467ff8ebe1e.dip0.t-ipconnect.de)14:03
+ eibachd (~eibachd@p200300dcf7231c00654e9fa1678b75d9.dip0.t-ipconnect.de)14:03
* mark_ -> mjw14:09
joschminute: for qcacld2, did you adjust something related to include directories? When I run build.sh it complains that it cannot find stdarg.h which should come from /usr/src/linux-headers-*-common/include/linux/stdarg.h14:29
- XgF (QUIT: Ping timeout: 268 seconds) (~quassel@45.63.43.12)14:30
+ XgF (~quassel@2001:19f0:5001:1174:5400:2ff:fef2:1fa2)14:32
minutejosch: hmm no, i did not. but you need the linux build directory referenced in build.sh and the kernel needs to have built "modules" before i think14:44
- eibachd (QUIT: Ping timeout: 268 seconds) (~eibachd@p200300dcf7231c00654e9fa1678b75d9.dip0.t-ipconnect.de)15:03
+ eibachd (~eibachd@2a01:599:322:6626:14a8:feb6:ced0:1742)15:07
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)15:08
joschreplacing #include <stdarg.h> with #include <linux/stdarg.h> fixes the problem15:09
joschsome random people on the internet say that in "newer kernels" stdarg.h includes should be replaced with linux/stdarg.h15:09
joschis that correct?15:09
- eibachd (QUIT: Read error: Connection reset by peer) (~eibachd@2a01:599:322:6626:14a8:feb6:ced0:1742)15:19
+ eibachd (~eibachd@p200300dcf7231c008372b1ba5110887d.dip0.t-ipconnect.de)15:20
- nsc (QUIT: Remote host closed the connection) (~nicolas@154-121-142-46.pool.kielnet.net)15:22
minutejosch: this sounds good15:24
minutejosch: this driver's origins are quite old i think15:24
minutealso they have .c files with 10000s of lines of code15:24
minuterecently there was an error in like line 3500015:24
minutemind blown15:24
joschminute: there are more errors: https://mister-muffin.de/p/IuvV.txt15:27
minutejosch: ah, it's probably not compatible with 6.5 anymore15:33
minutejosch: because i did the changes to support 6.6+15:33
minutethe prototype for the function passed to change_beacon has changed recently15:34
joschminute: i can push my changes and then you build and try it?15:34
joschminute: oh no wait, you are not running the kernel from Debian, right?15:35
minutejosch: sure thing15:35
joschbecause i'm packaging this as a dkms module15:36
joschso it's triggered by the Debian kernel maintainer script15:36
joschminute: anyways, here is the debianization patch: https://mister-muffin.de/p/jo1j.diff15:44
minutejosch: i'm not running the debian kernel ATM because i'm trying the newest git kernel, trying to track down gpu issues etc15:46
joschyes, makes sense15:47
- natalie (QUIT: Ping timeout: 252 seconds) (~natalie@user/natalie)16:46
+ natalie (~natalie@user/natalie)16:49
- natalie (QUIT: Ping timeout: 264 seconds) (~natalie@user/natalie)16:55
+ natalie (~natalie@user/natalie)16:58
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)17:56
- achasen (QUIT: Remote host closed the connection) (~achasen@2600:1700:e70:7f9f:cc6c:d0f5:78a1:52c0)18:29
+ mark_ (~mjw@gnu.wildebeest.org)18:45
Boostisbetterdo the ext4 issues in the recent debian kernel affect us? IE: have those already been seen to? 18:57
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50)19:14
- S0rin (QUIT: Ping timeout: 252 seconds) (~S0rin@user/s0rin)19:35
+ S0rin (~S0rin@user/s0rin)19:35
- mjw (QUIT: Killed (NickServ (GHOST command used by mark_!~mjw@gnu.wildebeest.org))) (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)20:07
+ mjw (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)20:08
- mjw (QUIT: Killed (NickServ (GHOST command used by mark_!~mjw@gnu.wildebeest.org))) (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)20:08
* mark_ -> mjw20:08
+ wielaard (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)20:08
- colinsane (QUIT: Quit: bye) (~colinunin@97-113-159-4.tukw.qwest.net)20:13
+ colinsane (~colinunin@97-113-159-4.tukw.qwest.net)20:15
+ nsc (~nicolas@154-121-142-46.pool.kielnet.net)20:31
- Asmadeus (QUIT: Ping timeout: 260 seconds) (~asmadeus@240b:13:8c80:d300::42:13)20:39
- [tj] (QUIT: Ping timeout: 260 seconds) (sid609767@id-609767.lymington.irccloud.com)20:39
+ Asmadeus (~asmadeus@240b:13:8c80:d300::42:13)20:39
+ [tj] (sid609767@id-609767.lymington.irccloud.com)20:43
- colinsane (QUIT: Quit: bye) (~colinunin@97-113-159-4.tukw.qwest.net)20:44
+ colinsane (~colinunin@97-113-159-4.tukw.qwest.net)20:47
joschBoostisbetter: since you are talking about the "recent Debian kernel" you probably don't mean the data corruption bug that appeared in 6.1 because of a patch that was backported from 6.5 -- so what issue do you mean?21:13
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20)21:50
Boostisbetterjosch: I think it was 6.6 that had the issue. They said the ext4 has a problem, and they told people to hold off on updating that until it was sorted. 22:02
- XYZ (QUIT: Ping timeout: 246 seconds) (~XYZ@37-48-32-224.nat.epc.tmcz.cz)22:13
+ XYZ (~XYZ@37-48-11-13.nat.epc.tmcz.cz)22:27
+ jacobk (~quassel@utdpat241106.utdallas.edu)23:53

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