| - bkeys (QUIT: Ping timeout: 240 seconds) (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 00:10 | |
| + bkeys (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 00:53 | |
| - mjw (QUIT: Quit: Leaving) (~mark@gnu.wildebeest.org) | 00:56 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:40) | 01:02 | |
| - chomwitt (QUIT: Ping timeout: 272 seconds) (~chomwitt@2a02:587:dc0d:e600:8f05:e6fa:1178:1d79) | 01:35 | |
| - bkeys (QUIT: Ping timeout: 268 seconds) (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 01:48 | |
| + bkeys (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 02:04 | |
| - mtm (QUIT: Ping timeout: 246 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 02:04 | |
| - NanoCodeBug (QUIT: Ping timeout: 252 seconds) (~NanoCodeB@c-67-160-118-90.hsd1.wa.comcast.net) | 02:31 | |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 02:53 | |
| ex-parrot | I need to do a similar UART mod I think | 02:54 |
|---|---|---|
| flowy | unfortunately i think i may have fried something on my reform motherboard. i did a keyboard pcb swap with the reform standalone kbd. also put in some of the better trackball parts. the really stupid part that i probably shouldn't have attempted- shaving off some of the taller pins on the back of the motherboard. also shouldn't have done all of this at once | 03:17 |
| flowy | err not pins but solder joints i guess | 03:18 |
| ex-parrot | shaving down the pins should be relllatively safe | 03:19 |
| flowy | anyways now when the power is connected i get two white lights, only one red light- and no activity/response at all from the keyboard | 03:19 |
| flowy | swapped the original keyboard back, same thing | 03:19 |
| ex-parrot | did you re-flash the keyboard firmware? | 03:19 |
| flowy | i did, on the new one | 03:19 |
| flowy | but left the old one alone and it's still not working | 03:19 |
| ex-parrot | I'd suggst checking the cables / connectors very carefully | 03:19 |
| ex-parrot | between the keyboard and motherboard | 03:19 |
| flowy | k will try again yeah | 03:20 |
| flowy | is it normal for some strange sort of buzzing/white led flashing to occur when only one of the two battery boards are connected? when i was reconnecting them, was weirded out by this | 03:20 |
| flowy | now i'm just running it with the battery boards disconnected to be safe | 03:21 |
| ex-parrot | you definitely don't want any missing cells within a pack but I'm not sure what the topology would be like with just one pack connected | 03:21 |
| flowy | i mean, you gotta connect one at a time heh | 03:21 |
| ex-parrot | I haven't seen my unit power on just from battery attachment | 03:21 |
| ex-parrot | yeah indeed | 03:21 |
| ex-parrot | make sure you don't have the charger in while plugging in the packs? | 03:21 |
| flowy | yeah the lights surprised me | 03:21 |
| - erle (QUIT: Quit: Just say no, then Putin can not legally invade your nation without your consent.) (~erle@86-82-248-88.fixed.kpn.net) | 03:22 | |
| flowy | definitely not | 03:22 |
| ex-parrot | _b | 03:22 |
| ex-parrot | someone more qualified might have to comment on that | 03:22 |
| flowy | i don't recall lights coming on when i've connected the battery boards before yeah | 03:22 |
| flowy | so maybe i've shorted something | 03:22 |
| ex-parrot | yeah I wonder. little bit of clipped component leg or something siting on the board maybe? | 03:22 |
| flowy | ex-parrot: whew maybe it's all good! got it turned on. one of the things i did when i swapped the keyboard pcbs- i also swapped their respective OLED screens, because one had a better fitting ribbon cable or whatever those very fragile things are called | 03:56 |
| flowy | i had already tried reseating that a couple times but this time i swapped them back and it worked right away | 03:56 |
| flowy | the keyboard wasn't even powering on when connecting usb power to it | 03:57 |
| flowy | not until i swapped the OLED screens back | 03:57 |
| flowy | then i put it in the reform and everything worked | 03:57 |
| flowy | so maybe their designs are subtly different | 03:57 |
| flowy | or i kept doing something wrong again and again | 03:58 |
| flowy | guess i will ask minute tmw | 03:58 |
| ex-parrot | great | 04:00 |
| ex-parrot | yeah those flex cables are finnicky at best | 04:00 |
| + NanoCodeBug (~NanoCodeB@c-67-160-118-90.hsd1.wa.comcast.net) | 04:06 | |
| + mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 04:10 | |
| flowy | everything back to normal. this time the board didn't turn on when i connected the batteries | 04:21 |
| flowy | ex-parrot: thanks for the encouragement lol. was starting to feel despair | 04:21 |
| ex-parrot | all good. | 04:22 |
| flowy | these white clicky switches are nice in the reform | 04:22 |
| ex-parrot | I built an Iris with the white clicky chocs a few years ago | 04:23 |
| ex-parrot | was very satisfying | 04:23 |
| flowy | like, you built a keyboard w/ white chocs and used them with the iris? | 04:24 |
| ex-parrot | https://keeb.io/products/iris-keyboard-split-ergonomic-keyboard <-- built one of these | 04:24 |
| flowy | ah, those look nice | 04:25 |
| flowy | are you still using it? | 04:26 |
| ex-parrot | nah I gave it to a friend | 04:26 |
| flowy | it made me a bit sad to learn how the clickbar works in these switches. it's unsatisfying to know | 04:27 |
| flowy | but whatever, they feel good | 04:27 |
| ex-parrot | what makes it unsatisfying? I thought it was quite a good design | 04:28 |
| flowy | well didn't mechanical switches back in the day have tactility associated with actuation? now they are separate functions | 04:28 |
| flowy | i can make these actuate without clicking. | 04:28 |
| flowy | but that's only if i try. so i try to forget and enjoy. | 04:30 |
| ex-parrot | most switch designs I can think of even going back to the 80s the tactile component is just a separate little plastic or metal thing | 04:32 |
| ex-parrot | and they just coincide with the activation point to some extnt | 04:32 |
| flowy | i guess it depends where you draw the line. the buckling springs will always be dear to my heart as i grew up with an ibm model m | 04:34 |
| flowy | with buckling springs the tactility is definitely more connected to actuation, they went through different designs, but even the last one was sort of like a piano | 04:35 |
| flowy | the spring buckles and causes something to hit a membrane | 04:35 |
| flowy | the clickbar is less associated with actuation. the switch can work without it | 04:36 |
| flowy | it's an addition | 04:36 |
| ex-parrot | yeah definitely | 04:37 |
| ex-parrot | they're a counterexample | 04:37 |
| ex-parrot | but e.g. ALPS and Cherry MX the tactility is both caused by little plastic bumps on the slider | 04:37 |
| ex-parrot | the actual switch closing doesn't strongly correspond to it | 04:38 |
| flowy | i guess it all makes sense | 04:38 |
| ex-parrot | or for ALPS it has that click leaf thing | 04:38 |
| flowy | esp. for low profile switches | 04:38 |
| ex-parrot | then you have like Topre where the switch "actuation point" is just a specific level of capacitance judged by a microcontroller :P | 04:38 |
| flowy | huh will have to read about that sometime | 04:39 |
| ex-parrot | but yeah I know what you mean, some people definitely prefer the actuation point to be very carefully correlated to the tactice point | 04:39 |
| ex-parrot | tactile* | 04:39 |
| flowy | but yeah i'm lovin this upgrade | 04:42 |
| flowy | this turned into a late one. night | 04:42 |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 05:10 | |
| - sl (QUIT: Remote host closed the connection) (~sl@104-59-85-219.lightspeed.iplsin.sbcglobal.net) | 05:26 | |
| + sl (~sl@104-59-85-219.lightspeed.iplsin.sbcglobal.net) | 05:30 | |
| - NanoCodeBug (QUIT: Ping timeout: 252 seconds) (~NanoCodeB@c-67-160-118-90.hsd1.wa.comcast.net) | 06:52 | |
| + NanoCodeBug (~NanoCodeB@c-67-160-118-90.hsd1.wa.comcast.net) | 07:01 | |
| NanoCodeBug | as a part of the lpc-spi support i've been digging into lots of different parts of uboot, kernel, and the device tree. | 07:08 |
| NanoCodeBug | I'm wondering, is there a reason the sdma firmware is not included in the reform image? | 07:08 |
| + nano_ (~nano@c-67-160-118-90.hsd1.wa.comcast.net) | 07:13 | |
| - NanoCodeBug (QUIT: Quit: Client closed) (~NanoCodeB@c-67-160-118-90.hsd1.wa.comcast.net) | 07:18 | |
| - nano_ (QUIT: Quit: Leaving) (~nano@c-67-160-118-90.hsd1.wa.comcast.net) | 07:18 | |
| + NanoCodeBug (~NanoCodeB@c-67-160-118-90.hsd1.wa.comcast.net) | 07:20 | |
| + chomwitt (~chomwitt@2a02:587:dc0d:e600:e74a:b005:c722:73f7) | 07:57 | |
| - chomwitt (QUIT: Ping timeout: 268 seconds) (~chomwitt@2a02:587:dc0d:e600:e74a:b005:c722:73f7) | 08:11 | |
| + chomwitt (~chomwitt@2a02:587:dc0d:e600:59fa:73d0:5de3:cb11) | 10:20 | |
| minute | NanoCodeBug: there's default sdma firmware in rom iirc... not sure how useful the update blob is | 10:32 |
| - vkoskiv (QUIT: Ping timeout: 240 seconds) (~vkoskiv@89-166-62-97.bb.dnainternet.fi) | 11:08 | |
| + Christoph_ (~Christoph@p4fe73d26.dip0.t-ipconnect.de) | 12:15 | |
| - S0rin (QUIT: Ping timeout: 240 seconds) (~S0rin@user/s0rin) | 12:17 | |
| + S0rin (~S0rin@user/s0rin) | 12:18 | |
| - NanoCodeBug (QUIT: Ping timeout: 246 seconds) (~NanoCodeB@c-67-160-118-90.hsd1.wa.comcast.net) | 12:58 | |
| - arminweigl (QUIT: Ping timeout: 248 seconds) (~arminweig@sourcehut/user/arminweigl) | 13:00 | |
| + arminweigl (~arminweig@sourcehut/user/arminweigl) | 13:05 | |
| - arminweigl (QUIT: Ping timeout: 272 seconds) (~arminweig@sourcehut/user/arminweigl) | 13:11 | |
| - GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon) | 13:21 | |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 13:23 | |
| + arminweigl (~arminweig@sourcehut/user/arminweigl) | 13:28 | |
| - mtm (QUIT: Ping timeout: 268 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 14:04 | |
| - GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon) | 14:35 | |
| flowy | minute: i'm having some problems but i'll only allow myself one simple question since it's the weekend. | 14:37 |
| flowy | (dont expect a response:) | 14:37 |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 14:38 | |
| flowy | but say the flex cable isn't connected on the reform keyboard, for the OLED screen. what is the expected behaviour if it is powered and connected to USB host? should there be signs of life? say if the programming DIP is switched on, too? | 14:38 |
| minute | flowy: depends if standalone or not | 14:45 |
| minute | flowy: non-standalone version is missing a 3.3v ldo in the middle on the top | 14:46 |
| minute | little 3 pin chip | 14:46 |
| minute | if you want to convert between standalone and internal, you have to transplant this chip | 14:46 |
| flowy | gotcha, thanks. helps me focus my troubleshooting | 14:48 |
| - GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon) | 15:37 | |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 15:38 | |
| + mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 16:09 | |
| - lexik (QUIT: Ping timeout: 240 seconds) (~lexik@171.25.222.230) | 17:39 | |
| + lexik (~lexik@171.25.222.217) | 17:40 | |
| - chomwitt (QUIT: Ping timeout: 272 seconds) (~chomwitt@2a02:587:dc0d:e600:59fa:73d0:5de3:cb11) | 17:48 | |
| + NanoCodeBug (~NanoCodeB@c-67-160-118-90.hsd1.wa.comcast.net) | 18:28 | |
| + nano_ (~NanoCodeB@c-67-160-118-90.hsd1.wa.comcast.net) | 18:28 | |
| - nano_ (QUIT: Client Quit) (~NanoCodeB@c-67-160-118-90.hsd1.wa.comcast.net) | 18:28 | |
| + chomwitt (~chomwitt@2a02:587:dc0d:e600:15f0:abfd:c02c:258d) | 18:35 | |
| + vkoskiv (~vkoskiv@89-166-62-97.bb.dnainternet.fi) | 19:25 | |
| vkoskiv | Is it intended to have the dmesg be printed to stdout even after logging in on the text console or did I mess something up? | 19:31 |
| bluerise | minute: rebased my u-boot patches, now there's no output after | 19:38 |
| bluerise | U-Boot SPL 2022.07-rc5-00014-g55f2108e47-dirty (Jun 25 2022 - 19:36:51 +0200) | 19:38 |
| bluerise | how I love this shit... | 19:38 |
| bluerise | it's probably the ATF though | 19:38 |
| bluerise | At least that's what I hope | 19:39 |
| bluerise | hm nah | 19:40 |
| vkoskiv | Also, how is the default browser set? I configured it to firefox, but it still keeps opening Chromium | 19:43 |
| bluerise | maybe I'll just send it in anyway and someone else can debug that after it's in the tree | 20:06 |
| - chomwitt (QUIT: Ping timeout: 255 seconds) (~chomwitt@2a02:587:dc0d:e600:15f0:abfd:c02c:258d) | 20:10 | |
| + mjw (~mark@gnu.wildebeest.org) | 20:25 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 21:56 | |
| + chomwitt (~chomwitt@2a02:587:dc0d:e600:8c30:8a72:c29d:62b2) | 22:00 | |
| flowy | vkoskiv: dmesg to console is the default on any linux distro i've used. you can google ways to disable it. | 22:26 |
| flowy | as for browser default i dunno! in which context has the default not been changed for you | 22:27 |
| - bluerise (QUIT: Changing host) (~bluerise@p5b0acfb5.dip0.t-ipconnect.de) | 22:55 | |
| + bluerise (~bluerise@user/bluerise) | 22:55 | |
| NanoCodeBug | some programs - like gui terminals - you set the url handler in the app settings. | 23:08 |
| NanoCodeBug | others default to desktop environment settings | 23:08 |
| NanoCodeBug | its not unified, very dependent on DE and app | 23:08 |
| sigrid | vkoskiv: xdg-settings --list | 23:28 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!