| - paperManu (QUIT: Ping timeout: 245 seconds) (~paperManu@modemcable141.205-200-24.mc.videotron.ca) | 00:12 | |
| + paperManu (~paperManu@204.48.0.160) | 01:20 | |
| + paperManu_ (~paperManu@204.48.0.160) | 01:21 | |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 01:21 | |
| + fkw (~fkw@user/fkw) | 01:52 | |
| - vagrantc (QUIT: Ping timeout: 245 seconds) (~vagrant@2600:3c01:e000:21:7:77:0:50) | 02:38 | |
| - paperManu_ (QUIT: Ping timeout: 244 seconds) (~paperManu@204.48.0.160) | 03:25 | |
| - paperManu (QUIT: Ping timeout: 272 seconds) (~paperManu@204.48.0.160) | 03:26 | |
| + paperManu (~paperManu@204.48.0.160) | 03:28 | |
| - mjw (QUIT: Ping timeout: 244 seconds) (~mjw@gnu.wildebeest.org) | 04:10 | |
| - paperManu (QUIT: Ping timeout: 246 seconds) (~paperManu@204.48.0.160) | 04:11 | |
| - fkw (QUIT: Remote host closed the connection) (~fkw@user/fkw) | 04:50 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50) | 04:58 | |
| - xktr (QUIT: Quit: leaving) (~xktr@user/xktr) | 05:14 | |
| + xktr (~xktr@user/xktr) | 05:18 | |
| - xktr (QUIT: Client Quit) (~xktr@user/xktr) | 05:21 | |
| + xktr (~xktr@user/xktr) | 05:27 | |
| - RandyK (QUIT: Ping timeout: 252 seconds) (~RandyK@user/randyk) | 06:11 | |
| + RandyK (~RandyK@user/randyk) | 06:12 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50) | 06:30 | |
| + GNUmoon2 (~GNUmoon@gateway/tor-sasl/gnumoon) | 07:58 | |
| josch | hi, i would appreciate some help with my a311d classic reform kernel 7.0.10. I get this spam on dmesg: https://paste.debian.net/hidden/3624776f | 09:37 |
|---|---|---|
| josch | my system is essentially unusable. Trying to run sudo leads to infinite stalling. I'm now connected to the system via serial uart and am typing these lines from my rk3588 pocket reform. | 09:38 |
| josch | doing anything via serial will be challenging due to this spam on dmesg -- how could i proceed | 09:38 |
| ephase | josch: have you tries to unload wireless modules? | 09:44 |
| josch | ephase: how would i do that without sudo and with 100 lines of messages per second filling my screen? :D | 09:48 |
| amospalla | josch: may sound silly, but if you can not shut down receiving packets on your side, can you stop the other side sending them by shutting down temporarily your AP? | 09:58 |
| josch | amospalla: oh you think the problem goes away by killing the wifi it is connected to? | 10:00 |
| amospalla | josch: wondering, if the spam is because of each received packet, that would help. | 10:00 |
| amospalla | not that I know what happens :'( | 10:01 |
| ephase | josch: booting from a fresh system on SD card, mounting root partition and edit module file to blacklist the module? | 10:16 |
| + siviq (~siviq@user/siviq) | 10:21 | |
| josch | amospalla: was a good idea but didnt work | 10:25 |
| josch | ephase: but then i would have to reboot and when i reboot the problem is gone :D | 10:26 |
| siviq | josch if you could reduce the console log level not to show those warnings, will provide enough space to fix what's broken. But this of course, require some access to CLI. During networking classes, we had to simulate same console flood message situation but for different purpose - how taxing is to networking equipment CPU. | 10:29 |
| josch | i wrote a shell script using sed to filter out the repeating dmesg entries from what i get over serial | 10:29 |
| josch | but it appears the console is completely dead or stalled now | 10:29 |
| josch | to reduce the log level i'd have to have a way to run dmesg, yes | 10:30 |
| josch | i rebooted now, everything back to normal | 10:30 |
| siviq | :( guess no RCA after all | 10:30 |
| josch | i was trying to rescue the situation because i had some unsaved documents open that i didnt want to loose | 10:30 |
| josch | oh funny after a reboot i now get new (much less frequent and much less annoying) spam: rtw88_8822cs mmc2:0001:1: sdio read32 failed (0x30): -84 | 10:33 |
| + oliverD (~Thunderbi@user/oliverd) | 10:33 | |
| josch | and my wifi card is gone | 10:33 |
| siviq | Does not look good then after all. Maybe WIFI driver is broken or the card died. | 10:35 |
| - Chwoka (QUIT: Ping timeout: 246 seconds) (~Chwoka@216.73.127.21) | 10:45 | |
| - siviq (QUIT: Quit: Client closed) (~siviq@user/siviq) | 10:49 | |
| ephase | Realtek wifi driver on linus is a long hate story :D | 10:59 |
| minute | josch: there's a person on irc who can probably help with this issue | 11:05 |
| minute | josch: xdarklight in #linux-amlogic | 11:07 |
| - oliverD (QUIT: Ping timeout: 248 seconds) (~Thunderbi@user/oliverd) | 11:07 | |
| josch | minute: thank you! I made a note for next time this happens | 11:10 |
| josch | The "sdio read32 failed" message was gone after a cold boot. | 11:10 |
| + oliverD (~Thunderbi@user/oliverd) | 11:29 | |
| josch | OB | 11:36 |
| josch | sry | 11:37 |
| minute | np! | 11:46 |
| + vkoskiv (~vkoskiv@109-204-186-7.cust.valoonet.fi) | 12:04 | |
| + mjw (~mjw@gnu.wildebeest.org) | 12:47 | |
| - oliverD (QUIT: Ping timeout: 276 seconds) (~Thunderbi@user/oliverd) | 13:27 | |
| - mjw (QUIT: Ping timeout: 244 seconds) (~mjw@gnu.wildebeest.org) | 13:34 | |
| + paperManu (~paperManu@204.48.0.160) | 13:41 | |
| * Guest8689 -> mjw | 13:53 | |
| + oliverD (~Thunderbi@user/oliverd) | 13:54 | |
| - oliverD (QUIT: Ping timeout: 245 seconds) (~Thunderbi@user/oliverd) | 13:58 | |
| - paperManu (QUIT: Ping timeout: 272 seconds) (~paperManu@204.48.0.160) | 14:32 | |
| - marty (QUIT: Ping timeout: 272 seconds) (~marty@143.244.47.102) | 14:45 | |
| + paperManu (~paperManu@modemcable141.205-200-24.mc.videotron.ca) | 14:48 | |
| + AnimaInvicta (~AnimaInvi@88-169-191-86.subs.proxad.net) | 14:51 | |
| josch | my pocket refor still shows 100% battery at all times -- i'm very interested in trying out the new sysctl and keyboard firmware beta once it's ready to receive some testing :) | 15:13 |
| + stephano (~stephano@71.238.14.13) | 16:31 | |
| - stephano (QUIT: Quit: stephano) (~stephano@71.238.14.13) | 16:41 | |
| + stephano (~stephano@71.238.14.13) | 16:41 | |
| - rodion_goritskov (QUIT: Remote host closed the connection) (~rodion_go@mail.goritskov.com) | 16:54 | |
| + rodion_goritskov (~rodion_go@mail.goritskov.com) | 16:55 | |
| + talos4 (~talos@2600:6c5d:f0:1fd0:96b7:80a9:eebb:e934) | 17:02 | |
| - talos (QUIT: Ping timeout: 245 seconds) (~talos@2600:6c5d:f0:1fd0:e21a:6acb:9b6:63a4) | 17:04 | |
| * talos4 -> talos | 17:04 | |
| - RandyK (QUIT: Ping timeout: 252 seconds) (~RandyK@user/randyk) | 18:05 | |
| + RandyK (~RandyK@user/randyk) | 18:14 | |
| josch | gordon1: i 3d printed another mock-up and realized that the chamfering around the hole we talked about is actually not necessary | 18:53 |
| josch | why? because on the bottom of the keyboard pcb are all the metal pins from the keyboard switches poking out, so we cannot mount the trackstick pcb flat against the keyboard pcb anyways :D | 18:54 |
| josch | and some components are mounted on the underside as well -- i totally forgot about those XD | 18:56 |
| - vkoskiv (QUIT: Changing host) (~vkoskiv@109-204-186-7.cust.valoonet.fi) | 18:56 | |
| + vkoskiv (~vkoskiv@user/vkoskiv) | 18:56 | |
| josch | i'm now designing a PLA spacer with holes at just the right locations | 18:56 |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50) | 19:13 | |
| + wielaard (~mjw@gnu.wildebeest.org) | 19:41 | |
| gordon1 | josch: those are diodes, i guess they can be safely relocated on top, and switch pins arguably can be cut very short | 20:00 |
| gordon1 | but probably not flush | 20:00 |
| * mjw -> Guest7856 | 20:30 | |
| - Guest7856 (QUIT: Killed (gallium.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:4600:5952:3a9:6e0e:555a) | 20:30 | |
| * wielaard -> mjw | 20:30 | |
| + Guest7856 (~mjw@2001:1c06:2486:4600:5952:3a9:6e0e:555a) | 20:31 | |
| josch | gordon1: but as long as there is enough space, why do this extra effort instead of just a thin spacer? | 20:40 |
| josch | sure, the components can be moved but shortening the switch legs seems... inellegant? | 20:40 |
| stephano | minute: I'm looking at the panel driver for the JDI and Huai Zhi (Wisecoco) panels and had a quick question. The upstream JDI driver uses different clock and vtotal. Are those upstream values wrong, or did you intentionally tune the timing? | 20:45 |
| + exark (~exark@user/exark) | 21:33 | |
| gordon1 | josch: i mean if there is space there, then sure | 22:05 |
| gordon1 | i need to take a peek what's below the keyboard | 22:06 |
| josch | gordon1: yes, usually the spacer bars are there keeping the space | 22:06 |
| gordon1 | oh right i remember those | 22:07 |
| josch | yeah, the official ones are 3.25 mm | 22:09 |
| gordon1 | and what's the thickness of the module? | 22:10 |
| - talos (QUIT: Ping timeout: 256 seconds) (~talos@2600:6c5d:f0:1fd0:96b7:80a9:eebb:e934) | 22:12 | |
| josch | 1.4 mm | 22:16 |
| josch | the pins poke out about 1.1 mm -- that even leaves 0.6 mm for a screw head :D | 22:16 |
| - paperManu (QUIT: Ping timeout: 264 seconds) (~paperManu@modemcable141.205-200-24.mc.videotron.ca) | 23:47 | |
| + talos (~talos@2600:6c5d:f0:1fd0:e3f0:8302:b915:735a) | 23:50 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!