2023-02-09.log

- mtm (QUIT: Ping timeout: 248 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)01:03
- ajr (QUIT: Quit: WeeChat 3.7) (~ajr@user/ajr)02:08
- robin (QUIT: Quit: Leaving) (~robin@user/terpri)02:47
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)03:09
- buckket (QUIT: *.net *.split) (~buckket@pdp8.buckket.org)04:15
- sevan (QUIT: *.net *.split) (~sevan@user/venture37)04:15
+ buckket (~buckket@pdp8.buckket.org)04:27
+ sevan (~sevan@user/venture37)04:27
- sevan (QUIT: Ping timeout: 248 seconds) (~sevan@user/venture37)04:32
+ sevan (~sevan@2001:470:1f1d:1d6:5a55:caff:fe24:ed4)04:34
- XgF (QUIT: Remote host closed the connection) (~quassel@2001:19f0:5001:1174:5400:2ff:fef2:1fa2)04:43
+ XgF (~quassel@2001:19f0:5001:1174:5400:2ff:fef2:1fa2)04:45
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:40)05:23
- Boostisbetter (QUIT: Ping timeout: 252 seconds) (4a410829d7@irc.cheogram.com)07:33
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:40)07:35
* Guest7015 -> nsc09:10
+ MajorBiscuit (~MajorBisc@2001:1c00:2408:a400:67e:5371:52a7:9b9a)09:35
nscMy ath9k wifi cards does no more connect; I am suspecting ath9k/regdomain handling, as `iw reg set DE` before loading ath9k.ko successfully changes the regdomain to DE, but ath9k.ko resets it to global/US and afterwards it is not settable any more.09:40
nscDoes anyone experience something similiar?  Does someone have any pointers?09:41
nsc(Problems appeared a few weeks ago after updating via MNT Reform + Debian/testing repos; can't spot it more concretely)09:41
- MajorBiscuit (QUIT: Ping timeout: 252 seconds) (~MajorBisc@2001:1c00:2408:a400:67e:5371:52a7:9b9a)09:49
+ MajorBiscuit (~MajorBisc@c-001-003-046.client.tudelft.eduvpn.nl)09:50
* wielaard -> mjw11:39
+ bgs (~bgs@212-85-160-171.dynamic.telemach.net)12:08
_nrb_nsc, I think I have the same issue. It is probably unrelated to any updates. Most likely your AP changed its frequency due to DFS or so... I do not have a solution though12:36
- scops (QUIT: Quit: Bridge terminating on SIGTERM) (~scopstchn@2001:470:69fc:105::8da)12:36
- rafostar[m] (QUIT: Quit: Bridge terminating on SIGTERM) (~rafostarm@2001:470:69fc:105::2:52da)12:37
- c-keen[m] (QUIT: Quit: Bridge terminating on SIGTERM) (~c-keenner@2001:470:69fc:105::2:8760)12:37
- eery[m] (QUIT: Quit: Bridge terminating on SIGTERM) (~eerymatri@2001:470:69fc:105::2:e4bc)12:37
- q66[m]1 (QUIT: Quit: Bridge terminating on SIGTERM) (~q66matrix@2001:470:69fc:105::3104)12:37
- JC[m] (QUIT: Quit: Bridge terminating on SIGTERM) (~jclibremo@2001:470:69fc:105::2:ce68)12:37
- shearwater[m] (QUIT: Quit: Bridge terminating on SIGTERM) (~shearwate@2001:470:69fc:105::3:44b)12:37
- qbit_m (QUIT: Quit: Bridge terminating on SIGTERM) (~qbittapen@2001:470:69fc:105::194)12:37
- pandora[m] (QUIT: Quit: Bridge terminating on SIGTERM) (~pandorami@2001:470:69fc:105::2:b5e8)12:37
+ eery[m] (~eerymatri@2001:470:69fc:105::2:e4bc)12:39
+ qbit_m (~qbittapen@2001:470:69fc:105::194)12:42
+ q66[m] (~q66matrix@2001:470:69fc:105::3104)12:42
+ scops (~scopstchn@2001:470:69fc:105::8da)12:42
+ rafostar[m] (~rafostarm@2001:470:69fc:105::2:52da)12:42
+ shearwater[m] (~shearwate@2001:470:69fc:105::3:44b)12:42
+ pandora[m] (~pandorami@2001:470:69fc:105::2:b5e8)12:42
+ JC[m] (~jclibremo@2001:470:69fc:105::2:ce68)12:42
+ c-keen[m] (~c-keenner@2001:470:69fc:105::2:8760)12:42
nsc_nrb_: Do you see those 'ath: EEPROM regdomain: 0x0' and 'ath: EEPROM indicates default country code should be used', too?  I am wondering whether it is (simply) possible to modify these EEPROM settings.12:59
- mtm (QUIT: Ping timeout: 268 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)13:03
- eery[m] (QUIT: Ping timeout: 252 seconds) (~eerymatri@2001:470:69fc:105::2:e4bc)13:13
- pandora[m] (QUIT: Ping timeout: 252 seconds) (~pandorami@2001:470:69fc:105::2:b5e8)13:13
- scops (QUIT: Ping timeout: 252 seconds) (~scopstchn@2001:470:69fc:105::8da)13:13
- c-keen[m] (QUIT: Ping timeout: 246 seconds) (~c-keenner@2001:470:69fc:105::2:8760)13:13
- shearwater[m] (QUIT: Ping timeout: 256 seconds) (~shearwate@2001:470:69fc:105::3:44b)13:14
- JC[m] (QUIT: Ping timeout: 260 seconds) (~jclibremo@2001:470:69fc:105::2:ce68)13:14
- rafostar[m] (QUIT: Ping timeout: 252 seconds) (~rafostarm@2001:470:69fc:105::2:52da)13:14
- q66[m] (QUIT: Ping timeout: 260 seconds) (~q66matrix@2001:470:69fc:105::3104)13:15
- qbit_m (QUIT: Ping timeout: 260 seconds) (~qbittapen@2001:470:69fc:105::194)13:15
+ eery[m] (~eerymatri@2001:470:69fc:105::2:e4bc)13:29
+ pandora[m] (~pandorami@2001:470:69fc:105::2:b5e8)13:31
+ scops (~scopstchn@2001:470:69fc:105::8da)13:31
+ shearwater[m] (~shearwate@2001:470:69fc:105::3:44b)13:33
+ JC[m] (~jclibremo@2001:470:69fc:105::2:ce68)13:36
+ c-keen[m] (~c-keenner@2001:470:69fc:105::2:8760)13:38
+ q66[m] (~q66matrix@2001:470:69fc:105::3104)13:55
+ rafostar[m] (~rafostarm@2001:470:69fc:105::2:52da)14:12
+ qbit_m (~qbittapen@2001:470:69fc:105::194)14:19
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)15:10
+ robin (~robin@user/terpri)15:29
- ec0 (QUIT: Ping timeout: 252 seconds) (~ec0@vps-446f4f39.vps.ovh.ca)15:30
+ ec0 (~ec0@vps-446f4f39.vps.ovh.ca)15:31
- sevan (QUIT: Changing host) (~sevan@2001:470:1f1d:1d6:5a55:caff:fe24:ed4)15:51
+ sevan (~sevan@user/venture37)15:51
- bgs (QUIT: Remote host closed the connection) (~bgs@212-85-160-171.dynamic.telemach.net)16:23
+ Boostisbetter (4a410829d7@irc.cheogram.com)17:46
+ chomwitt (~chomwitt@2a02:587:7a12:aa00:1ac0:4dff:fedb:a3f1)17:57
- chomwitt (QUIT: Ping timeout: 264 seconds) (~chomwitt@2a02:587:7a12:aa00:1ac0:4dff:fedb:a3f1)18:34
- GNUmoon (QUIT: Ping timeout: 255 seconds) (~GNUmoon@gateway/tor-sasl/gnumoon)18:51
+ ajr (~ajr@user/ajr)19:27
- MajorBiscuit (QUIT: Ping timeout: 264 seconds) (~MajorBisc@c-001-003-046.client.tudelft.eduvpn.nl)19:38
+ MajorBiscuit (~MajorBisc@2001:1c00:2408:a400:67e:5371:52a7:9b9a)19:40
- MajorBiscuit (QUIT: Ping timeout: 265 seconds) (~MajorBisc@2001:1c00:2408:a400:67e:5371:52a7:9b9a)19:47
+ chomwitt (~chomwitt@2a02:587:7a12:aa00:1ac0:4dff:fedb:a3f1)20:17
+ andreas-e (~Andreas@2001:861:c4:f2f0::c64)20:36
- qbit (QUIT: Quit: WeeChat 3.7.1) (~qbit@h.suah.dev)20:53
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20)21:00
- mjw (QUIT: Killed (NickServ (GHOST command used by markw!~wielaard@gnu.wildebeest.org))) (~mjw_@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)21:02
+ wielaard (~mjw_@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)21:02
+ bluerise_ (~bluerise@p5b211f97.dip0.t-ipconnect.de)21:15
- bluerise (QUIT: Ping timeout: 260 seconds) (~bluerise@user/bluerise)21:15
chartreusensc: For ath9k I compiled a custom kernel for it before, basically modifying the source to patch out the EPROM country code overriding the user specified one. I can see if I can find the source code I had and update it21:20
chartreuseI've been meaning to do that with the newer kernel now (this was the v2 sys image I modded)21:20
chartreuseMaybe I can figure out how to do it proper with DKMS so it could be more easilly shared21:21
+ qbit (~qbit@h.suah.dev)21:49
- Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149-210-16-58.mobile.nym.cosmote.net)21:50
+ Ar|stote|is (~linx@149-210-16-58.mobile.nym.cosmote.net)21:52
chartreuseCant't find the original source of the patch I used and modified, but I'll go find my .patch I made for 5.14 (should still work on newer with maybe minimal changes)22:18
chartreusehttps://gist.github.com/ChartreuseK/a6947e50912dd9e867bf357752e32daa22:21
chartreuseThe patch adds a kernel option to the ath driver to support user REGD, so that ath5k and ath9k's regulatory region can be set using iw reg set22:23
chartreuseAh here's the original, though I had to change it for 5.14 https://gist.github.com/ChartreuseK/a6947e50912dd9e867bf357752e32daa22:23
chartreuseOoops wrong paste https://github.com/twisteroidambassador/arch-linux-ath-user-regd/blob/master/README.md22:23
chartreuseShouldn't be difficult to adapt/directly use with the current kernel. I never submitted it as a patch to the MNT kernel as I didn't want people running it without setting a regulatory domain by mistake22:24
* bluerise_ -> bluerise22:45
- bluerise (QUIT: Changing host) (~bluerise@p5b211f97.dip0.t-ipconnect.de)22:46
+ bluerise (~bluerise@user/bluerise)22:46
blueriseminute: I think I should have a look at using the mainline U-Boot to boot the Reform Linux and weed out bugs22:47
blueriseso long term goal, switch boundary u-boot to the mainline one + patches?22:47
joschbluerise: "The goal is to migrate to mainstream u-boot or barebox ASAP" sounds faster than "long term goal" :D https://source.mnt.re/reform/reform-boundary-uboot22:52
blueriseI mean, migrate from old boundary to u-boot mainline22:52
bluerisenot mainstream22:52
- chomwitt (QUIT: Ping timeout: 264 seconds) (~chomwitt@2a02:587:7a12:aa00:1ac0:4dff:fedb:a3f1)23:08
vagrantcdefinitely encountered a few quirks with mainline u-boot plus patches running linux on the reform23:14
vagrantce.g. starting sway from the commandline ... would just sit there and not display anything23:14
vagrantcthe ath9k wifi would see networks, but not be able to connect to any of them23:15
blueriseyeah, I gotta check what that's about23:19
vagrantcbluerise: both with and without your extra patches ... applied on 2023.04-rc1 ... haven't tested u-boot git master branch23:29
vagrantcstill great to see progresss on it :)23:29
vagrantcoh, i should try with the vendor atf ... i was trying atf from debian, which is basically mainline atf.23:30
vagrantcACTION notes to self and wanders off for a bit23:30
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20)23:37
bluerise:D23:56

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