2023-11-19.log

- mjw (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org)00:43
- chomwitt (QUIT: Ping timeout: 255 seconds) (~chomwitt@ppp-94-67-202-40.home.otenet.gr)01:21
- S0rin (QUIT: Ping timeout: 276 seconds) (~S0rin@user/s0rin)01:22
+ S0rin (~S0rin@user/s0rin)01:29
+ bkeys (~Thunderbi@45.134.140.153)01:45
+ mjw (~mjw@gnu.wildebeest.org)02:26
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@45.134.140.153)02:33
+ bkeys (~Thunderbi@45.134.140.153)02:36
- S0rin (QUIT: Ping timeout: 264 seconds) (~S0rin@user/s0rin)03:13
+ S0rin (~S0rin@user/s0rin)03:18
+ XYZ_ (~XYZ@78-80-26-147.customers.tmcz.cz)04:10
- XYZ_ (QUIT: Ping timeout: 256 seconds) (~XYZ@78-80-26-147.customers.tmcz.cz)04:16
+ XYZ_ (~XYZ@78-80-26-147.customers.tmcz.cz)04:29
- klardotsh (QUIT: Ping timeout: 264 seconds) (~klardotsh@c-67-170-115-80.hsd1.wa.comcast.net)04:34
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20)04:51
- mjw (QUIT: Ping timeout: 255 seconds) (~mjw@gnu.wildebeest.org)05:17
+ ggoes_ (~gregf@ool-44c1517f.dyn.optonline.net)07:05
- ggoes (QUIT: Ping timeout: 256 seconds) (~gregf@fsf/staff/ggoes)07:06
* ggoes_ -> ggoes07:06
- ggoes (QUIT: Remote host closed the connection) (~gregf@ool-44c1517f.dyn.optonline.net)07:07
- eibachd (QUIT: Ping timeout: 276 seconds) (~eibachd@p200300dcf704e50023abe5077160597e.dip0.t-ipconnect.de)07:44
+ eibachd (~eibachd@p200300dcf704e500f57b2038674c76f7.dip0.t-ipconnect.de)07:46
+ ggoes (~gregf@fsf/staff/ggoes)08:08
- GNUmoon (QUIT: Quit: Leaving) (~GNUmoon@gateway/tor-sasl/gnumoon)08:22
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)09:08
- eibachd (QUIT: Ping timeout: 276 seconds) (~eibachd@p200300dcf704e500f57b2038674c76f7.dip0.t-ipconnect.de)09:26
+ eibachd (~eibachd@2a01:599:30f:992b:21ea:360a:a0ca:9f04)09:27
- eibachd (QUIT: Read error: Connection reset by peer) (~eibachd@2a01:599:30f:992b:21ea:360a:a0ca:9f04)10:08
+ eibachd (~eibachd@p200300dcf704e50044057a53f6d77a25.dip0.t-ipconnect.de)10:09
- XYZ_ (QUIT: Ping timeout: 256 seconds) (~XYZ@78-80-26-147.customers.tmcz.cz)11:49
- eibachd (QUIT: Ping timeout: 256 seconds) (~eibachd@p200300dcf704e50044057a53f6d77a25.dip0.t-ipconnect.de)11:54
+ eibachd (~eibachd@p200300dcf704e5019b4ffd9451e18951.dip0.t-ipconnect.de)11:58
+ XYZ_ (~XYZ@78-80-26-147.customers.tmcz.cz)12:10
- vkoskiv (QUIT: Ping timeout: 260 seconds) (~vkoskiv@87-100-141-229.bb.dnainternet.fi)12:26
- eibachd (QUIT: Ping timeout: 276 seconds) (~eibachd@p200300dcf704e5019b4ffd9451e18951.dip0.t-ipconnect.de)12:29
+ eibachd (~eibachd@p200300dcf704e500e2307ac6f963b7fa.dip0.t-ipconnect.de)12:30
- XYZ_ (QUIT: Ping timeout: 264 seconds) (~XYZ@78-80-26-147.customers.tmcz.cz)12:41
+ chomwitt (~chomwitt@ppp-94-67-189-25.home.otenet.gr)12:57
+ XYZ_ (~XYZ@78-80-26-147.customers.tmcz.cz)13:08
+ reformer (~reformer@softboy.mntmn.com)14:02
- vkoskiv (QUIT: Ping timeout: 256 seconds) (~vkoskiv@87-100-141-229.bb.dnainternet.fi)14:41
- eibachd (QUIT: Ping timeout: 276 seconds) (~eibachd@p200300dcf704e500e2307ac6f963b7fa.dip0.t-ipconnect.de)14:47
+ eibachd (~eibachd@p200300dcf704e5006151593f4220f62a.dip0.t-ipconnect.de)14:47
+ vkoskiv (~vkoskiv@87-100-141-229.bb.dnainternet.fi)14:48
joschminute: some 15:05
joschminute: i have some more product feedback :)15:05
joschi just repaired my keyboard (successfully) but when attaching the keyboard bezel15:06
joschdue to the bezel having quite the curvature15:06
joschone of the four latches of the bezel slid into the space between battery board and case15:06
joschsparks flew15:06
f_josch: oof.15:07
joschmaybe this would not've happened if i had disconnected the battery board before making this mistake wtih the bezel15:07
joschbut i also didn't expect replacing the keyboard affecting the battery board at all15:07
joschwell, the machine still works15:08
joschbatteries also still seem to work15:08
joschi don't know yet whether there was any lasting damage15:08
joschi also had kapton tape around my battery board edges as it was recommended15:09
joschso i don't even know which parts actually touched15:09
minutejosch: ah, maybe you literally only created some sparks16:27
joschi charged until full and am now down to 65% which looks normal16:29
joschin addition to "only some sparks" i also nearly created a tiny heart attack XD16:30
- Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.8.188)16:57
+ Ar|stote|is (~linx@149.210.8.188)16:58
joschbattery is now at 44% and everything seems fine17:12
joschphew... seems like i was very, very lucky17:13
f_:D17:13
Zabayeah, i think it's best to always follow paranoid safety protocols around batteries17:19
joschi'm surprised there was some contact at all because the battery boards are covered with tape at the point where i think things touched each other... hrm...17:23
joschi just wish there was a lesson to be learned from this other than "make sure all the latches are where you expect them to be and nowhere else"17:24
+ cwebber (~user@user/cwebber)17:36
joscherr... maybe there was a victim after all?18:43
joschI continously get this in my dmesg and no connection to my wifi:18:45
joschhttps://paste.debian.net/1298601/18:46
joschi booted my reform with a rescue image to make sure that this is not a software problem18:46
joschand the issue was identical18:46
joschso i swapped my pcie wifi card for another one and the issue is gone18:46
joschis this at all plausible that a short at the battery board somehow fried my wifi card such that i would see the wifi but connecting to it would fail? this is very odd...18:47
Boostisbetterdoes anyone know if there is a way to have fstab auto load a drive, but load it with the users permissions, such that all of the contentof the drive has those permissions. Currently it is auto mounting it, but the permission all belong to root. I can't sudo chown it, because it says the the operation is not permitted. 19:34
f_josch: hm19:49
- eibachd (QUIT: Ping timeout: 276 seconds) (~eibachd@p200300dcf704e5006151593f4220f62a.dip0.t-ipconnect.de)20:05
+ eibachd (~eibachd@p200300dcf704e5002f024df12aa61ae8.dip0.t-ipconnect.de)20:06
Boostisbetterjosch: considering that your board has something preventing suspend from working, I think it is very plausible that and errant voltage fried your wifi card. 20:18
joschi'd find the connection between my suspend not working and wifi being fried an even more wild idea than fried wifi was in the first place :D21:03
joschthings will get solved once i can order my second mainboard because then i can for example try this "fried" wifi card and see if it is really the culprit or not21:03
- nsc (QUIT: Quit: leaving) (~nicolas@251-48-142-46.pool.kielnet.net)21:04
f_josch: A311D reform?21:06
joschf_: imx8mq reform21:06
f_oh ok21:06
joschwhat would you have said otherwise?21:07
f_That AFAICT on at least amlogic S905 suspend b0rks21:08
f_(and power off actually results in a reboot, on my s905 box)21:08
joschah kk -- no with the imx8mq som, suspend apparently starts being reliable with linux 6.521:08
joschi don't think suspend on a311d with the reform works yet21:08
f_Doubt suspend ever worked on Amlogic..let me check21:09
f_oh, not mentioned on linux-meson.com21:11
+ nsc (~nicolas@251-48-142-46.pool.kielnet.net)21:12
joschthanks for checking!21:12
f_np21:12
f_suspend didn't work on my S905 box for sure though21:13
- qbit (QUIT: Remote host closed the connection) (~qbit@h.suah.dev)21:22
+ qbit (~qbit@h.suah.dev)21:24
- qbit (QUIT: Remote host closed the connection) (~qbit@h.suah.dev)21:47
+ qbit (~qbit@h.suah.dev)21:49
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20)22:08
sevanI guess since it's the 25th birthday, half life is free on the Steam store23:43
sevananyone tried it on the Reform?23:43
joschsevan: https://mastodon.social/@mntmn/11028874623916489623:45
sevannice :)23:45
sevannew version has some fixes apparently. (I haven't tried it)23:47
sevanhttps://store.steampowered.com/app/70/HalfLife/23:47

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