| - Boostisbetter (QUIT: Ping timeout: 255 seconds) (4a410829d7@irc.cheogram.com) | 00:03 | |
| + Boostisbetter (4a410829d7@irc.cheogram.com) | 00:06 | |
| abortretryfail | oh man... VINREG is tied to INTVCC, explains why it always wants to pull max current from whatever's connected :D | 00:23 |
|---|---|---|
| vkoskiv | minute: is the single display limit on a311d a hw or sw limitation by the way? | 00:43 |
| minute | vkoskiv: sw as far as i know | 00:46 |
| minute | vkoskiv: kadas advertise vim3 with "dual independent displays", same chip | 00:48 |
| minute | so one could look into their kernel/drivers | 00:48 |
| - erle (QUIT: Read error: Connection reset by peer) (~erle@ip5f5bf349.dynamic.kabel-deutschland.de) | 02:04 | |
| + erle (~erle@2a02:8109:da40:c4:f06d:e217:a61c:2e41) | 02:10 | |
| + jacobk (~quassel@utdpat241055.utdallas.edu) | 02:43 | |
| - nsc (QUIT: Ping timeout: 264 seconds) (~nicolas@89-48-142-46.pool.kielnet.net) | 03:59 | |
| + nsc (~nicolas@154-48-142-46.pool.kielnet.net) | 04:00 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50) | 04:49 | |
| - Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.32.15) | 05:02 | |
| + Ar|stote|is (~linx@149.210.32.15) | 05:02 | |
| - Ar|stote|is (QUIT: Client Quit) (~linx@149.210.32.15) | 05:03 | |
| + Ar|stote|is (~linx@149.210.32.15) | 05:03 | |
| josch | ah drats, the version of wlroots in stable is too old for wayfire and firedecor | 07:56 |
| josch | so only sway in stable | 07:56 |
| - jacobk (QUIT: Ping timeout: 255 seconds) (~quassel@utdpat241055.utdallas.edu) | 09:06 | |
| + jacobk (~quassel@64.189.201.150) | 09:34 | |
| - mjw (QUIT: Ping timeout: 255 seconds) (~mjw@77-174-248-71.fixed.kpn.net) | 11:21 | |
| - doctorhoo (QUIT: Ping timeout: 260 seconds) (~doctorhoo@217-210-162-155-no600.tbcn.telia.com) | 11:24 | |
| + doctorhoo (~doctorhoo@2a00:801:7a7:5c1a:9472:da2e:8edf:b925) | 11:26 | |
| - doctorhoo (QUIT: Ping timeout: 258 seconds) (~doctorhoo@2a00:801:7a7:5c1a:9472:da2e:8edf:b925) | 12:53 | |
| + doctorhoo (~doctorhoo@2a00:801:792:5f09:8366:957f:a89b:224e) | 12:54 | |
| - Boostisbetter (QUIT: Ping timeout: 258 seconds) (4a410829d7@irc.cheogram.com) | 13:30 | |
| grimmware | out of interest has anyone tried using a reform with an external GPU? | 14:30 |
| vkoskiv | I think the LS1028 module is the one that has a bigger PCI address space, so that one is most suitable for it | 14:31 |
| vkoskiv | Don't know enough about i.mx8/A311D to say how realistic that would be | 14:32 |
| grimmware | hmm, I've got a GDC Beast kickign around but no spare GPU to put it in. I mean I don't have a reform yet anyway so it's all a bit moot but it just occurred to me. | 14:34 |
| + Boostisbetter (4a410829d7@irc.cheogram.com) | 14:34 | |
| minute | grimmware: yes, i've used an older nvidia card on ls1028a reform in development | 14:35 |
| minute | grimmware: but the other socs can't do it i think. haven't actually tested on the a311d, but i believe it has address space limitations | 14:35 |
| minute | ls1028a has a real beefy pcie system from the layerscape/qoriq family | 14:36 |
| minute | you can probably use like a antique 64MB pci card on imx via pcie/pci adapter ^^ | 14:36 |
| grimmware | gotcha | 14:38 |
| abortretryfail | In that case the GC7000 might be faster | 14:38 |
| abortretryfail | tbh, its really not *that* slow, considering its age and target market | 14:39 |
| grimmware | so something else that wasn't entirely clear to me with the pocket, are the nvme ssd and the wwan modem mutually exclusive? the specs mention that both go in an M.2 slot. | 14:39 |
| - Boostisbetter (QUIT: Quit: Gateway shutdown) (4a410829d7@irc.cheogram.com) | 14:41 | |
| minute | grimmware: no, there are two m.2 slots. one for nvme, the other for modem (that has usb signals) | 14:45 |
| grimmware | <3 excellent | 14:47 |
| minute | grimmware: in this model you can see both populated https://mastodon.social/@mntmn/111171996119037370 | 14:51 |
| - jacobk (QUIT: Ping timeout: 255 seconds) (~quassel@64.189.201.150) | 15:01 | |
| + jacobk (~quassel@2603-8080-b200-7b02-0000-0000-0000-0b71.res6.spectrum.com) | 16:13 | |
| vkoskiv | With wifi enabled, bluetooth audio periodically stutters a bit, and the error 'timed out to flush queue 3' preceeds the stutter by a few seconds | 16:15 |
| vkoskiv | I blocked wifi with rfkill, and that seems to stop the stuttering | 16:16 |
| vkoskiv | Might not be Reform-specific though, I do recall stuttering happening on my desktop machine too. I solved that by switching to wired headphones. | 16:16 |
| minute | vkoskiv: could be either wifi/bt coexistence issue (better to use 5ghz wifi then) or scheduling issue over the same sdio lines | 16:26 |
| vkoskiv | Yeah, this was on 2.4GHz WiFi | 16:26 |
| - doctorhoo (QUIT: Read error: Connection reset by peer) (~doctorhoo@2a00:801:792:5f09:8366:957f:a89b:224e) | 17:33 | |
| + doctorhoo (~doctorhoo@217-210-162-155-no600.tbcn.telia.com) | 17:34 | |
| + Boostisbetter (4a410829d7@irc.cheogram.com) | 18:24 | |
| + pandora (uid585533@id-585533.ilkley.irccloud.com) | 18:38 | |
| - Boostisbetter (QUIT: Ping timeout: 258 seconds) (4a410829d7@irc.cheogram.com) | 18:40 | |
| - jacobk (QUIT: Ping timeout: 248 seconds) (~quassel@2603-8080-b200-7b02-0000-0000-0000-0b71.res6.spectrum.com) | 18:42 | |
| + ndufresne53 (~ndufresne@souvlakia.collabora.co.uk) | 18:46 | |
| - ndufresne5 (QUIT: Ping timeout: 240 seconds) (~ndufresne@souvlakia.collabora.co.uk) | 18:47 | |
| * ndufresne53 -> ndufresne5 | 18:47 | |
| josch | minute: wayfire 0.8.0 got released two weeks ago: https://github.com/WayfireWM/wayfire/releases/tag/v0.8.0 | 18:59 |
| josch | minute: is that new enough for the reform-system-image? | 18:59 |
| josch | minute: i also see that you are upstream of firedecor now -- would you like me to sponsor an upload of that to Debian unstable? | 19:00 |
| josch | then we can drop both wayfire and firedecor custom builds in build_custom.sh | 19:00 |
| + jacobk (~quassel@2603-8080-b200-7b02-0000-0000-0000-0b71.res6.spectrum.com) | 19:43 | |
| - jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@2603-8080-b200-7b02-0000-0000-0000-0b71.res6.spectrum.com) | 21:05 | |
| vkoskiv | Found HDMI cable, I can't get anything showing on there | 21:05 |
| vkoskiv | It just remains inactive in swaymsg -t get_outputs | 21:06 |
| vkoskiv | I think it took the modeline command though, I see a bunch more modes listed now | 21:06 |
| vkoskiv | Not sure if it's got something to do with the fact that I'm outputting to a HDMI capture device instead of a monitor | 21:06 |
| vkoskiv | In fact, I'll just quickly try with a monitor too | 21:06 |
| vkoskiv | Sure enough, works with the monitor just fine | 21:10 |
| vkoskiv | Seems to be working reliably, I tried to crank up the resolution to the native 2560x1440 of the display I'm testing with, and that didn't seem to work | 21:32 |
| vkoskiv | The modeline command just does nothing, no errors anywhere either. | 21:32 |
| vkoskiv | Super weird that these sway tools just hide errors, would make figuring out why things go wrong much easier | 21:43 |
| vkoskiv | I enabled the debug mode, and that log is useless, almost nothing shows up there | 21:43 |
| vkoskiv | If it would just tell me something about *why* nothing happened, I'd be happy | 21:43 |
| vkoskiv | Enabled verbose mode too, still almost nothing. Bleh. | 21:46 |
| + mjw (~mjw@77-174-248-71.fixed.kpn.net) | 21:51 | |
| + Boostisbetter (4a410829d7@irc.cheogram.com) | 21:56 | |
| vkoskiv | Eh, I'll just accept that that res is too much for some unknown reason, 1080p will do. | 22:02 |
| vkoskiv | No stuttering on bt headphones if I'm using 5GHz wifi | 22:06 |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50) | 22:14 | |
| - doctorhoo (QUIT: Ping timeout: 240 seconds) (~doctorhoo@217-210-162-155-no600.tbcn.telia.com) | 22:34 | |
| + doctorhoo (~doctorhoo@2a00:801:792:5f09:8366:957f:a89b:224e) | 22:35 | |
| - sevan (QUIT: Changing host) (~sevan@2001:470:1f1d:1d6:5a55:caff:fe24:ed4) | 22:52 | |
| + sevan (~sevan@user/venture37) | 22:52 | |
| + jacobk (~quassel@129.110.242.224) | 22:55 | |
| + ephase (~ephase@2a01:e0a:2a:5300:f8d4:1fb6:b769:4362) | 22:55 | |
| ephase | hi | 23:00 |
| vkoskiv | Hey | 23:00 |
| ephase | some people here have `iwd` to manage Wifi networks with teir Reform | 23:01 |
| + ZylonMaster (~fujwj@cpe-98-15-248-249.hvc.res.rr.com) | 23:08 | |
| + fokewik (~fujwj@cpe-98-15-248-249.hvc.res.rr.com) | 23:08 | |
| - fokewik (QUIT: Client Quit) (~fujwj@cpe-98-15-248-249.hvc.res.rr.com) | 23:08 | |
| josch | yes, but people have found this problem: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052378 | 23:11 |
| ephase | josch: now Iwd start, but not working (process tagged as defunct ans unkillable) as soon as I try to connect to WPA2/WPA3 network | 23:16 |
| ephase | s/ans/and/ | 23:16 |
| grimmware | minute: so like, the lower half of the pocket is going to essentially be battery, keyboard and mouse, so is there going to be any spare internal USB on the lower half? | 23:32 |
| violet | that was strange. trackball module got into a weird state where the buttons worked but ball didnt, and powering the system off/on through the keyboard oled panel menu didnt fix it | 23:44 |
| violet | i fixed it by opening the laptop up and unplugging the batteries from the mainboard for a few seconds | 23:44 |
| vkoskiv | Did you check for debris on the sensor? | 23:45 |
| violet | it wasnt debris on the sensor | 23:45 |
| violet | it was some chip got into a weird state | 23:45 |
| vkoskiv | Weird, turning off from circle+0 turns off 5V to the trackball, and that's where the chip gets its power | 23:46 |
| vkoskiv | So it def. was reset | 23:46 |
| vkoskiv | My guess would have been a bit of debris that was disloged when you flipped the thing over | 23:46 |
| violet | its possible | 23:47 |
| vkoskiv | I thought about modeling a retaining ring with tighter tolerance that I would then print, the current one has a gap that's a bit bigger than needed | 23:47 |
| vkoskiv | i.e. the ball falls out a bit when flipping it over | 23:47 |
| vkoskiv | But my printer is crusty, and from 2016 | 23:48 |
| - jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@129.110.242.224) | 23:59 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!