| ch | josch: having to bring just one charger is sooo good | 00:33 |
|---|---|---|
| ch | henesy: i think the highest i've seen it draw power is 1A @ 20V | 00:34 |
| ch | doesnt need a massive charger | 00:34 |
| josch | wow 20 W is comfy! | 00:35 |
| minute | i was a bit more careful this time with charging current, lipo and all... | 00:35 |
| josch | the big reform might draw 88 W from my adapter but it hey it charges *fast*! :D | 00:37 |
| henesy | ch: hmmm, there goes my hope that a chunkier charger would solve my problems | 00:44 |
| ch | well it might | 00:45 |
| henesy | ill pick up a ugreen or whatever the charger was someone mentioned on the charging thread and see if it works for me with my cabling | 00:45 |
| henesy | the goal is to test combinations of the crowd supply brick, anker cable, lenovo x1 brick | 00:45 |
| ch | hard to tell what your charger supports without actually trying to charge something with it :) | 00:45 |
| henesy | and the ugreen thing | 00:45 |
| henesy | true! | 00:45 |
| - ephase (QUIT: Quit: WeeChat 4.3.1) (~ephase@2a01:e0a:2a:5300:8af3:6216:8fce:7058) | 00:45 | |
| ch | which anker cable do you have btw? | 00:46 |
| henesy | uhhhh | 00:47 |
| ch | minute: is the sysctl stdio hooked up to anything by default btw? | 00:48 |
| henesy | some 100W braided cable 10' | 00:48 |
| henesy | i dont think there's a model # on it | 00:48 |
| ch | 100w should have an emarker in it. maybe that confuses stuff | 00:49 |
| henesy | What wattage should I be using | 00:50 |
| ch | the usb4 certified cable i've got certainly causes a lot of extra PD traffic. but forgot to try it before flashing the sysctl | 00:51 |
| ch | i guess i'd try with a less fancy cable. sth thats rated for 30W? | 00:52 |
| henesy | Alright | 00:55 |
| minute | ch: yes, ttyACM0 in linux | 00:55 |
| ch | thanks! | 01:02 |
| ch | drawing 1.2A @ 19.4V now, so 25W should really be fine | 01:05 |
| - mjw (QUIT: Ping timeout: 276 seconds) (~mjw@gnu.wildebeest.org) | 01:46 | |
| - mtm (QUIT: Ping timeout: 276 seconds) (~textual@c-71-228-84-213.hsd1.fl.comcast.net) | 02:03 | |
| + mtm (~textual@c-71-228-84-213.hsd1.fl.comcast.net) | 02:05 | |
| - Gooberpatrol_66 (QUIT: Quit: Konversation terminated!) (~Gooberpat@user/gooberpatrol66) | 02:09 | |
| + Gooberpatrol_66 (~Gooberpat@user/gooberpatrol66) | 02:09 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50) | 02:22 | |
| - pandora (QUIT: Read error: Connection reset by peer) (uid585533@ilkley.irccloud.com) | 02:23 | |
| - svp (QUIT: Ping timeout: 252 seconds) (sid537750@uxbridge.irccloud.com) | 02:23 | |
| + pandora (uid585533@id-585533.ilkley.irccloud.com) | 02:23 | |
| + svp (sid537750@id-537750.uxbridge.irccloud.com) | 02:27 | |
| - xktr (QUIT: Ping timeout: 252 seconds) (~xktr@user/xktr) | 03:21 | |
| + xktr (~xktr@user/xktr) | 03:22 | |
| + reform7624 (~brandon@144.89.4.1) | 04:50 | |
| - reform7624 (QUIT: Client Quit) (~brandon@144.89.4.1) | 04:50 | |
| + jacobk (~quassel@47-186-105-237.dlls.tx.frontiernet.net) | 05:43 | |
| + reform23456 (~matt@pool-71-162-2-172.pitbpa.fios.verizon.net) | 06:04 | |
| - reform23456 (QUIT: Client Quit) (~matt@pool-71-162-2-172.pitbpa.fios.verizon.net) | 06:05 | |
| henesy | ch: latest findings for charging -- i was able to induce a charge to start while running! required swapping out the charging brick to one reported working on the forum | 06:49 |
| henesy | UGREEN 65W USB C Charger, Nexode 3 Ports GaN Fast Charger Block | 06:50 |
| henesy | same 100W anker braided cable as before, so i don't think the cable is the issue | 06:50 |
| henesy | seems the stock crowd supply US charger isn't cutting it though | 06:50 |
| + mjw (~mjw@gnu.wildebeest.org) | 06:58 | |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 07:00 | |
| - Gooberpatrol_66 (QUIT: Ping timeout: 276 seconds) (~Gooberpat@user/gooberpatrol66) | 07:01 | |
| + NanoCodeBug (~NanoCodeB@c-73-35-191-67.hsd1.wa.comcast.net) | 07:38 | |
| - hairu (QUIT: Remote host closed the connection) (m-uotkmd@user/hairu) | 07:48 | |
| + hairu (m-uotkmd@user/hairu) | 07:50 | |
| - hairu (QUIT: Remote host closed the connection) (m-uotkmd@user/hairu) | 07:50 | |
| + hairu (m-uotkmd@user/hairu) | 07:53 | |
| - mjw (QUIT: Ping timeout: 245 seconds) (~mjw@gnu.wildebeest.org) | 08:03 | |
| NanoCodeBug | so! i have my pd charger working while the pocket is booted now | 08:08 |
| NanoCodeBug | reading up on the docs on the fusb302b chip - and going by that i saw no pd traffic when the pocket was powered on, i thought that the fdusb302b conditions for when it should negotiate a connection were never being reached. | 08:09 |
| NanoCodeBug | specifically, it uses vbus detection as the trigger - the vbusOk interrupt - my theory was that the this or another start negotiation trigger was not occuring | 08:14 |
| NanoCodeBug | - it appears that when the port is powered - the pocket powers vbus internally - this trigger becomes flakey | 08:14 |
| NanoCodeBug | by disabling vbus power to the port - gpio_put(PIN_USB_SRC_ENABLE, 0); - it reliably connects to the pd charger. | 08:15 |
| ^alex | oho | 08:18 |
| NanoCodeBug | my naive guess is that the other chargers are either A) sending a vbus with higher voltage than the pockets internal 5 volt regulator, triggering the fusb302b internal vbus interrupt comparator to flip or B) grounding the vbus line in some way. | 08:18 |
| NanoCodeBug | B\) not smiley glasses emoji, thank you web libera chat | 08:18 |
| NanoCodeBug | my hack solution is to keep the port unpowered - this is obv not a good solution. but if it is a vbus power conflict for the vbus interrupt, presumably there is some better way to detect if a client device is attached or a power source device is attached that does not involve keeping the port always powered on | 08:20 |
| henesy | cool! | 08:20 |
| NanoCodeBug | perhaps the current logic needs to be reversed, the port is unpowered until the fusb302b confirms that the newly attached device is not sending any power. | 08:32 |
| NanoCodeBug | yeah, the DRP Software flow as indicated in the onsemi documentation suggests this behavior | 08:34 |
| NanoCodeBug | https://www.onsemi.com/pdf/datasheet/fusb302b-d.pdf | 08:34 |
| NanoCodeBug | figure 11 DRP Software Flow | 08:34 |
| NanoCodeBug | "Manual Dual-Role Detection and Configuration" | 08:34 |
| NanoCodeBug | VBUS stays powered off, the host swaps the fusb302b between two modes searching for a source (aka regular usb device that wants power) or a sink (charger) | 08:35 |
| NanoCodeBug | until it can confirm the existence of either | 08:36 |
| minute | NanoCodeBug: ahhh. great detective work | 08:40 |
| - NanoCodeBug (QUIT: Quit: Client closed) (~NanoCodeB@c-73-35-191-67.hsd1.wa.comcast.net) | 09:09 | |
| Twodisbetter | Sounds like improvements are on the horizon! | 10:08 |
| josch | the plan "sell more hardware, get more experts on board" seems to be panning out nicely :) | 10:09 |
| ch | uhuh interesting | 10:26 |
| henesy | it seems the bluetooth issue might be the kernel module doing smth funky? | 10:35 |
| henesy | https://paste.sr.ht/~henesy/8b1fb7b7c79592c6c256c8cdd9fdf4ede05a598b | 10:35 |
| ch | the ar6k_wlan firmware messages are normal, some thread i found claims they are only used for testing | 10:37 |
| ch | regulatory.db however might be useful, there should be a debian package containing that | 10:37 |
| ch | dunno if any of that is really related to bluetooth issues | 10:37 |
| henesy | yeah i have no idea | 10:40 |
| henesy | having trouble finding useful errors | 10:40 |
| - jacobk (QUIT: Ping timeout: 248 seconds) (~quassel@47-186-105-237.dlls.tx.frontiernet.net) | 11:04 | |
| + jacobk (~quassel@47-186-105-237.dlls.tx.frontiernet.net) | 11:05 | |
| + mjw (~mjw@gnu.wildebeest.org) | 11:24 | |
| minute | henesy: these errors are "normal" i think. bluetooth is done via mainline driver | 12:27 |
| minute | henesy: output of > hcitool dev ? | 12:28 |
| minute | henesy: and > hcitool scan | 12:28 |
| grimmware | heh, glad I didn't look closer at the PD stuff based on what NanoCodeBug found out, I wouldn't have figured that out | 12:45 |
| grimmware | I've also got that Ugreen Nexode 65W GaN 3 port on the way | 12:45 |
| grimmware | should be here today | 12:45 |
| - mjw (QUIT: Ping timeout: 255 seconds) (~mjw@gnu.wildebeest.org) | 13:17 | |
| minute | reenabled vop_mmu now on rk3588 pocket reform (had that turned off for dsi, turns out that isn't necessary), and appears stable now | 13:47 |
| - mtm (QUIT: Ping timeout: 246 seconds) (~textual@c-71-228-84-213.hsd1.fl.comcast.net) | 14:03 | |
| + mtm (~textual@c-71-228-84-213.hsd1.fl.comcast.net) | 14:06 | |
| * Guest4625 -> mjw | 14:19 | |
| - cobra (QUIT: Ping timeout: 248 seconds) (~cobra@user/Cobra) | 14:20 | |
| + andypiper (~andypiper@89.36.117.58) | 14:30 | |
| + cobra (~cobra@user/Cobra) | 14:41 | |
| [tj] | cool, I've got freebsd running from sd card on imx8mp | 14:46 |
| [tj] | final piece was removing the existing clock logic in the fsl sdhci driver | 14:47 |
| [tj] | now my pocket can arrive and I won't feel bad that there is no support yet | 14:47 |
| josch | uuuh nice! now i wish we still had a Debian/kFreeBSD port in a working state. We could probably bootstrap freebsd proper from there... | 14:49 |
| - bkeys (QUIT: Quit: bkeys) (~Thunderbi@45.134.140.153) | 14:49 | |
| + bkeys (~Thunderbi@45.134.140.153) | 14:50 | |
| minute | [tj]: woah ok? does freebsd support imx8mp officially or did you base it on imx8mq drivers? | 14:54 |
| [tj] | I have a little time from my employer to work on a port | 14:59 |
| [tj] | this is the first time I've managed anything useful | 14:59 |
| andypiper | oh cool, would be interested in giving freebsd a shot on my Pocket at some point (mostly because I want to try All The Things) | 14:59 |
| [tj] | there was great imx6 support, but the developer behind that passed away a couple of years ago. Someone was working in imx8mq support, but there were some politics and he stopped contributing | 15:00 |
| - bkeys (QUIT: Ping timeout: 246 seconds) (~Thunderbi@45.134.140.153) | 15:06 | |
| + bkeys (~Thunderbi@45.134.140.153) | 15:08 | |
| andypiper | cpufetch now supports the A311D (well, I'm about to confirm that the feature branch that the dev made for it works as expected) | 15:37 |
| andypiper | https://github.com/Dr-Noob/cpufetch/issues/268#issuecomment-2321295636 | 15:39 |
| minute | andypiper: nice | 16:12 |
| - andypiper (QUIT: Ping timeout: 276 seconds) (~andypiper@89.36.117.58) | 16:15 | |
| + andypiper (~andypiper@89.36.117.58) | 17:30 | |
| - andypiper (QUIT: Quit: My device has gone to sleep. Zzzz…) (~andypiper@89.36.117.58) | 18:01 | |
| - chrcav (QUIT: Quit: Lost terminal) (~chrcav@user/chrcav) | 18:45 | |
| grimmware | Can heartily recommend getting a right-angled USB-C cable. Not only is it a better fit for plugging into the PD socket unobtrusively but it also means that if you plan on regularly bricking your system controller you don’t have to unscrew the mobo and leave it floating. https://usercontent.irccloud-cdn.com/file/fsx5UFIY/1725037037.JPG | 18:58 |
| grimmware | Also, can confirm that Ugreen Nexode 65W 3 port charger is The One for initiating charging whilst powered on (until firmware fix at any rate). It’s also just a nice compact charger. | 19:00 |
| ^alex | yeah, we've been using the right-angle usb-c to unbrick our syscon a lot | 19:04 |
| + pochet (~ch@94.45.248.226) | 19:05 | |
| + andypiper (~andypiper@2a00:23c7:b703:a401:d19:6950:b517:bbb4) | 19:17 | |
| minute | grimmware: nice | 19:21 |
| grimmware | saves you 6 screws, removing the side plate and having to move the mobo at all | 19:23 |
| grimmware | [tj]: aw dude congrats! | 19:25 |
| grimmware | I'm quite in to the idea of running the imx8mp as a mini desktop when whatever mini desktop project materializes and I'd love to have some FreeBSD back in my life | 19:26 |
| andypiper | re: angled adapters, yup, I threw that suggestion in the forum https://community.mnt.re/t/mnt-pocket-reform-essentials/2094/31 | 19:34 |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50) | 19:35 | |
| andypiper | I'm going to try the updated version of wlmaker that should now support wayland transformation and be possible to rotate for the Pocket... https://github.com/phkaeser/wlmaker/issues/97#issuecomment-2316335970 :-) | 19:36 |
| andypiper | (part of my quest to Pocket Reform-enable All The Things haha) | 19:36 |
| - pochet (QUIT: Quit: WeeChat 4.3.1) (~ch@94.45.248.226) | 19:46 | |
| + mark_ (~mjw@gnu.wildebeest.org) | 19:52 | |
| - andypiper (QUIT: Ping timeout: 244 seconds) (~andypiper@2a00:23c7:b703:a401:d19:6950:b517:bbb4) | 19:53 | |
| ^alex | [tj], we would love to test the freebsd-on-pocket at some point :) | 19:53 |
| + gustav28 (~gustav@c-bd37524e.019-141-67626730.bbcust.telenor.se) | 20:02 | |
| + reform21270 (~pewpew@p200300e89724b9004f1c563888bb5e84.dip0.t-ipconnect.de) | 20:06 | |
| henesy | minute: https://paste.sr.ht/~henesy/05b2b6429aff63f8f1d709a8d44914df4040d339 | 20:07 |
| minute | henesy: ok, so the bt driver is not probed at all | 20:10 |
| minute | henesy: anything for dmesg | grep -i sdio ? | 20:10 |
| + andypiper (~andypiper@45.146.10.36) | 20:10 | |
| minute | henesy: ah one moment, are you on debian stable or sth? | 20:12 |
| henesy | https://paste.sr.ht/~henesy/86f28377e391db016f7b5e3f4e85b37b6fbd0e46 | 20:12 |
| henesy | unstable as per stock | 20:12 |
| - andypiper (QUIT: Quit: bye) (~andypiper@45.146.10.36) | 20:19 | |
| + andypiper (~andypiper@45.146.10.36) | 20:22 | |
| - andypiper (QUIT: Client Quit) (~andypiper@45.146.10.36) | 20:25 | |
| + ephase (~ephase@2a01:e0a:2a:5300:8af3:6216:8fce:7058) | 20:49 | |
| reform21270 | !h | 20:53 |
| - reform21270 (QUIT: Quit: Leaving) (~pewpew@p200300e89724b9004f1c563888bb5e84.dip0.t-ipconnect.de) | 21:03 | |
| gustav28 | evening! | 21:11 |
| gustav28 | minute that mastodon post with the pocket running shadertoy was so good, then I saw it was available in the web shop (eu customer here)! | 21:12 |
| gustav28 | tempted to get one without wifi and use it as my focused game/framework coding device/linux introduction.. I assume connecting it to external display via micro-hdmi works well? what about usb-c -> hdmi adapter/hub with hdmi? | 21:15 |
| + andypiper (~andypiper@45.146.10.36) | 21:15 | |
| gustav28 | (rk3588) | 21:15 |
| minute | gustav28: hi! microhdmi, yep. it doesn't have display over usb-c though. | 21:31 |
| gustav28 | will the rk3588 have worse battery life than the stated ~4 hours? also, the battery is Li-Ion, not LiFePO4 as in the big reform? | 21:44 |
| minute | gustav28: batteries are li-ion. for the battery life with rk3588 i haven't yet made real measurements. it does use more power than the a311d, yeah. | 21:50 |
| minute | but also depends a lot on the load | 21:50 |
| gustav28 | ok, thanks :) | 21:51 |
| + NanoCodeBug (~NanoCodeB@c-73-35-191-67.hsd1.wa.comcast.net) | 21:52 | |
| gustav28 | one more: I also saw someone on the forum saying that the Pocket lost 20% charge when in off mode during the night, is this accurate or was that a bug that has been fixed? | 22:06 |
| gustav28 | it would be nice to be able to shut it down and not have to worry about state of charge (or even better, put it to sleep, but that's not in yet afaik) | 22:07 |
| + xorraxrax (~pewpew@p200300e89724b9004f1c563888bb5e84.dip0.t-ipconnect.de) | 22:07 | |
| ^alex | gustav28, weve got some patches that improve it a bit, but, yeah, the syscon and the keyboard run at full tilt even when the SoC is off, currently. | 22:11 |
| gustav28 | and they consume that much power? :o | 22:12 |
| ^alex | apparently! the rp2040 isn't exactly a low-power part | 22:13 |
| - gustav28 (QUIT: Quit: Quit) (~gustav@c-bd37524e.019-141-67626730.bbcust.telenor.se) | 22:15 | |
| NanoCodeBug | it is not, it can get low but not that low. the lpc in the atsamd21 in the big reform can get much lower idle draw. | 22:15 |
| ^alex | https://source.mnt.re/atax1a/pocket-reform/-/tree/atax1a/power-down-core-and-sleep?ref_type=heads our branch in progress - it downclocks everything to the USB clock and shuts off large swaths of peripherals we aren't using | 22:16 |
| + gustav28 (~gustav@c-bd37524e.019-141-67626730.bbcust.telenor.se) | 22:18 | |
| ^alex | reposting for gustav28: https://source.mnt.re/atax1a/pocket-reform/-/tree/atax1a/power-down-core-and-sleep?ref_type=heads our branch in progress - it downclocks everything to the USB clock and shuts off large swaths of peripherals we aren't using | 22:18 |
| gustav28 | sounds good, does it make a difference? | 22:20 |
| gustav28 | what about using the stand-by power switch? I guess that should shut it down completely? | 22:20 |
| ^alex | our patches decreases the power draw by ~10% overnight, but left alone it'll still gnaw on the battery and die over a few days | 22:21 |
| ^alex | and yeah, the standby switch would indeed shut it down completely | 22:21 |
| gustav28 | nice improvements | 22:22 |
| NanoCodeBug | a larger switch or 3d printing a switch cover would be a good idea | 22:22 |
| gustav28 | so why are people not using the switch? | 22:22 |
| gustav28 | because it's tricky to push? | 22:22 |
| NanoCodeBug | the switch is tiny and recessed | 22:22 |
| NanoCodeBug | you need a pin to toggle it | 22:22 |
| ^alex | yeah we use a SIM-removal tool for that | 22:23 |
| gustav28 | ok, doesn't sound too bad if you know it will be powered off for a while | 22:23 |
| gustav28 | probably dumb idea: does each key on the keyboard consume power while "checked"? what about only checking the trigger keys? | 22:24 |
| ^alex | that was one of our thoughts yeah | 22:24 |
| ^alex | but we've been metaphorically afk for the past couple of days (it was our birthday yesterday) | 22:24 |
| josch | oh belated congratulations! :) | 22:25 |
| ^alex | our previous experiments in trying to use the deeper sleep modes wound up with either jittery keystrokes or a non-enumerating brick | 22:25 |
| gustav28 | ah | 22:26 |
| ^alex | but that's more likely just us doing something wrong | 22:27 |
| gustav28 | are you with the mnt team or doing external research? | 22:28 |
| ^alex | i'm a coyote :) | 22:28 |
| gustav28 | (congrats btw!) | 22:28 |
| ^alex | (also we appreciate that this is the kinda place where nobody gives us fuzz for the plural pronouns) | 22:28 |
| ^alex | but yeah we're just some hacker who got a Pocket Reform and promptly started hacking on its firmware | 22:29 |
| ^alex | our partner, looking at us with the laptop 3 kinds of apart: "are you having fun?" | 22:29 |
| * andypiper -> andypiper[afk] | 22:29 | |
| gustav28 | hehe | 22:29 |
| - andypiper[afk] (QUIT: Quit: My device has gone to sleep. Zzzz…) (~andypiper@45.146.10.36) | 22:30 | |
| ^alex | josch, thanks :) | 22:30 |
| josch | :) | 22:30 |
| josch | (in my experience hacker circles in general give no fuzz about pronouns other than choosing the one that the person prefers to be addressed by :) ) | 22:31 |
| - ephase (QUIT: Ping timeout: 260 seconds) (~ephase@2a01:e0a:2a:5300:8af3:6216:8fce:7058) | 22:45 | |
| + ephase (~ephase@2a01:e0a:2a:5300:8af3:6216:8fce:7058) | 22:47 | |
| grimmware | ^alex: happy birthday :D | 22:49 |
| NanoCodeBug | ^alex: :D a coyote! happy birthday! i've been doing the same, popped open the pocket reform and immediately started messing with the internals. the back panel has spent more time detached than attached to it now. | 22:51 |
| grimmware | I think it's a really important part of the device - to be able to *properly* get to know it and to not be afraid of tinkering with it | 22:52 |
| grimmware | I'm not great at anything mechanical or 3D design or I'd be trying to think of a way to attach a tiny pop-out screwdriver in the chassis | 22:53 |
| grimmware | The right-angled USB cable is part of that, by the time I'd had to externally flash the system controller twice I was like "gonna need better tools for this because it's gonna keep happening"! | 22:54 |
| josch | ACTION always has a screwdriver in the backpack to pop open the underside of the big reform in an emergency :) | 22:55 |
| josch | (also helps with other emergencies) | 22:55 |
| NanoCodeBug | a dual spudger + hex + phillips screwdriver came with my framework laptop, its perfect for the reform as well | 22:56 |
| + andypiper (~andypiper@45.146.10.36) | 22:58 | |
| gustav28 | would you recommend it to me if I want to mostly do programming on it? I'm not afraid to tinker but would not want it be the only thing I do with it :) | 23:10 |
| gustav28 | like, is it expected that you need to reflash the system controller from time to time? can the device to that itself or do I need a separate computer? | 23:11 |
| NanoCodeBug | on the pocket reform you can flash it from within the os, without needing a cable, for updates that are tested and confirmed to work properly. | 23:12 |
| NanoCodeBug | the cable is only needed if it ends up in a odd state | 23:12 |
| gustav28 | ok | 23:13 |
| NanoCodeBug | i love the pocket, but if you are thinking of using it as a device to learn how to do general programming, you would probably be better served by a regular laptop, ideally a linux compatible one. | 23:13 |
| NanoCodeBug | from purely a cost standpoint | 23:14 |
| gustav28 | I'm thinking of using it as an mostly offline, focused device on which I program my next game/framework (written in C) | 23:16 |
| gustav28 | I like the form factor and it being linux first (I'm tired of all hoops I have to jump through to get a macbook running linux) | 23:17 |
| grimmware | If you're not in to tinkering it's possibly worth waiting until more of the bugs are ironed out | 23:17 |
| NanoCodeBug | gustav28 I plan to use mine similarly - but for gameboy color/gba dev | 23:18 |
| grimmware | idk, I mean the fact of the matter is that it runs Debian unstable so you've got a chance of occasionally pulling in broken packages | 23:18 |
| NanoCodeBug | yeah, it is a hacking/tinkering device at its core, some familiarity with linux + debian package management and how to recover the system is ideal | 23:19 |
| NanoCodeBug | that can be something that gets in the way of learning how to program or focusing | 23:20 |
| grimmware | personally a lot of the appeal was having a device I could tinker with and truly own | 23:20 |
| josch | it will likely become a similar thing as the big reform in terms of going from "device to tinker" to "device to be daily driver" i think/hope | 23:21 |
| grimmware | I'm absolutely in love with it for writing out and about at the moment | 23:22 |
| josch | in the beginning i had my thinkpad and my big reform was open all the time as i was changing and testing things | 23:22 |
| josch | but for over a year now, that stopped and the thing is stable and just does its job | 23:22 |
| gustav28 | both big reform and pocket are on debian unstable? | 23:23 |
| gustav28 | why unstable btw? | 23:23 |
| josch | i'm running my reform on stable | 23:24 |
| josch | this can theoretically also work for the pocket reform | 23:24 |
| josch | https://reform.debian.net/images/ | 23:24 |
| josch | but this is *not* tested | 23:24 |
| josch | and i cannot test it because i do not own a pocket | 23:24 |
| josch | maybe it works well maybe it does not :) | 23:24 |
| gustav28 | what is "backports kernel"? | 23:25 |
| josch | the kernel from stable cannot work for the pocket reform as it is too old | 23:26 |
| josch | debian stable backports is a suite which builds packages from debian testing for debian stable | 23:26 |
| gustav28 | aha | 23:26 |
| josch | that way, debian stable can get the much more recent kernel from testing | 23:26 |
| gustav28 | but what is the reason pocket is on unstable to begin with? | 23:27 |
| josch | same as for the big reform -- during its development, bleeding edge package versions are needed | 23:27 |
| josch | much of it isn't even in debian yet in the first place | 23:27 |
| josch | rk3588 support isn't even in the upstream kernel | 23:27 |
| gustav28 | I understand that it needs a more recent kernel, but why not use this "stable + backports kernel"? | 23:28 |
| gustav28 | ah ok | 23:28 |
| gustav28 | so it's mostly device support? | 23:28 |
| josch | for the big reform, the reason for that used to be parts like mesa or ffmpeg or clapper or flash-kernel | 23:28 |
| josch | all things from userspace which were too old in stable | 23:28 |
| josch | it's about time | 23:29 |
| josch | MNT is a very tiny company and they can only do so much | 23:29 |
| josch | by developing on and for unstable, they do not spread themselves too thinly | 23:29 |
| josch | it is a lot of effort to target multiple suites | 23:29 |
| josch | so the debian stable support comes from the community and is not official | 23:29 |
| gustav28 | ah okay | 23:30 |
| gustav28 | (I've never used linux as a daily driver so I'm very new to this) | 23:30 |
| - xorraxrax (QUIT: Ping timeout: 248 seconds) (~pewpew@p200300e89724b9004f1c563888bb5e84.dip0.t-ipconnect.de) | 23:31 | |
| ch | josch: if i want to help out with stable on pocket, what do you recommend i try? | 23:31 |
| gustav28 | so when is the next debian stable and do we expect reform to be able to use that? | 23:31 |
| josch | ch: anything really :D | 23:31 |
| josch | ch: download the system image and see if it works at all | 23:31 |
| ch | josch: ok, so download image to sdcard and see? | 23:31 |
| josch | or try debian-installer and see what happens | 23:31 |
| josch | yup | 23:31 |
| grimmware | #YOLOps | 23:32 |
| ch | honestly i have no idea how to boot d-i on non-x86/non-uefi :D | 23:32 |
| josch | ch: instructions here: https://reform.debian.net/d-i/ | 23:32 |
| ch | ok, i'll put it into a tab | 23:33 |
| josch | gustav28: next debian stable release might be around summer next year | 23:34 |
| josch | gustav28: it might support the pocket if enough people help make that happen :) | 23:35 |
| gustav28 | hehe ok | 23:35 |
| gustav28 | when looking at the product from the outside (website/manual etc), it seems to be quite user friendly in that there is a good manual, a setup wizard etc etc - would you say that I will run into problems if I just use the official images? I guess I could now as it's still early, but say in a few months? | 23:35 |
| ch | hmm, does the on-emmc uboot try to boot from sdcard first? | 23:36 |
| josch | ch: it should, yes | 23:36 |
| ch | ok | 23:36 |
| ch | should get myself a serial console | 23:36 |
| josch | ch: it should because if it does not, then messing up your /boot on eMMC would make it impossible to repair it because you would not be able to put in a vanilla system-image on sd-card to rescue your system | 23:37 |
| ch | right | 23:37 |
| josch | ch: it is very likely that the d-i image lacks critical kernel modules | 23:37 |
| ch | hm right | 23:38 |
| ch | anyway, has to wait for tomorrow. am at an outdoor hacker camp, and i have neither an sdcard or a source of power (...) | 23:39 |
| josch | :) | 23:39 |
| gustav28 | I'm off, thanks everyone for your input | 23:40 |
| josch | drop by any time if you have questions :) | 23:40 |
| gustav28 | thanks :) | 23:40 |
| * andypiper -> andypiper[afk] | 23:51 | |
| - andypiper[afk] (QUIT: Quit: My device has gone to sleep. Zzzz…) (~andypiper@45.146.10.36) | 23:51 | |
| - gustav28 (QUIT: Quit: Quit) (~gustav@c-bd37524e.019-141-67626730.bbcust.telenor.se) | 23:53 | |
| - ephase (QUIT: Quit: WeeChat 4.3.1) (~ephase@2a01:e0a:2a:5300:8af3:6216:8fce:7058) | 23:58 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
