| josch | hramrach: koay? | 00:00 |
|---|---|---|
| - cow321 (QUIT: Ping timeout: 268 seconds) (~deflated8@50.39.247.54) | 00:08 | |
| Zaba | 'okay' i assume | 00:17 |
| Zaba | when a device tree just sets status to "okay" without further changes, it's probably just enabling a piece of hardware that is disabled in the parent device tree | 00:18 |
| josch | right, but the label vanished from the parent | 00:19 |
| AbortRetryFail | josch: what needs checking with imx8mq and clapper? | 00:34 |
| AbortRetryFail | Oh, i guess i need to update first. | 00:34 |
| - chomwitt (QUIT: Ping timeout: 256 seconds) (~chomwitt@2a02:587:7a18:fc00:1ac0:4dff:fedb:a3f1) | 00:35 | |
| josch | AbortRetryFail: in that lies the problem | 00:35 |
| josch | AbortRetryFail: be *very* careful when you update your unstable installation these days | 00:35 |
| AbortRetryFail | >_> | 00:35 |
| AbortRetryFail | I already had to remove u-boot-menu to get it booting again | 00:36 |
| AbortRetryFail | haven't updated since you said not to the other day. | 00:36 |
| josch | AbortRetryFail: well, you are using Debian unstable, so... :) | 00:36 |
| AbortRetryFail | Yeah, it breaks more than Arch does. | 00:36 |
| AbortRetryFail | and I ran Arch unstable for like 5 years. | 00:37 |
| josch | usually what people do who want a usable system but still a rolling release is to use testing | 00:37 |
| AbortRetryFail | maybe that was it i forget. i had to do that to get the latest AMD drivers from git | 00:38 |
| AbortRetryFail | these days the AMD drivers are just A+ excellent. | 00:38 |
| josch | AbortRetryFail: i think it would be safest if i prepare an sd-card image, you flash that to an empty card and try booting from that | 00:40 |
| josch | once you are in a fresh system, you could also try running "rm /usr/share/initramfs-tools/scripts/init-top/reform && update-initramfs -u" and see if display still comes on reliably when booting | 00:44 |
| josch | AbortRetryFail: here is a forum thread about the current Debian unstable upgrade problems: https://community.mnt.re/t/both-sway-and-wayfire-stopped-working-after-an-upgrade/1916 | 00:46 |
| - S0rin (QUIT: Ping timeout: 264 seconds) (~S0rin@user/s0rin) | 00:54 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 01:07 | |
| + S0rin (~S0rin@user/s0rin) | 01:16 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 01:50 | |
| - mark_ (QUIT: Ping timeout: 255 seconds) (~mjw@82-169-127-166.fixed.kpn.net) | 01:52 | |
| + mrdaught (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 01:56 | |
| - S0rin (QUIT: Ping timeout: 272 seconds) (~S0rin@user/s0rin) | 02:00 | |
| - mrdaught (QUIT: Read error: Connection reset by peer) (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 02:00 | |
| + cobra_ (~cobra@user/Cobra) | 02:04 | |
| - cobra (QUIT: Ping timeout: 272 seconds) (~cobra@user/Cobra) | 02:04 | |
| + S0rin (~S0rin@user/s0rin) | 02:06 | |
| - S0rin (QUIT: Ping timeout: 264 seconds) (~S0rin@user/s0rin) | 02:17 | |
| + S0rin (~S0rin@user/s0rin) | 02:19 | |
| - S0rin (QUIT: Ping timeout: 256 seconds) (~S0rin@user/s0rin) | 02:25 | |
| + S0rin (~S0rin@user/s0rin) | 02:29 | |
| + cow321 (~deflated8@50.39.247.54) | 03:04 | |
| - S0rin (QUIT: Ping timeout: 252 seconds) (~S0rin@user/s0rin) | 03:24 | |
| + S0rin (~S0rin@user/s0rin) | 03:27 | |
| vkoskiv | Ticket to Revision + flights to Frankfurt booked. Would love to meet/hang out if any of you here end up going! | 03:57 |
| - nsc (QUIT: Ping timeout: 264 seconds) (~nicolas@159-96-142-46.pool.kielnet.net) | 03:58 | |
| + nsc (~nicolas@13-48-142-46.pool.kielnet.net) | 04:00 | |
| - jn (QUIT: Ping timeout: 268 seconds) (~quassel@user/jn/x-3390946) | 04:26 | |
| + jn (~quassel@2001-4dd4-6624-0-20d-b9ff-fe49-15fc.ipv6dyn.netcologne.de) | 04:27 | |
| - jn (QUIT: Changing host) (~quassel@2001-4dd4-6624-0-20d-b9ff-fe49-15fc.ipv6dyn.netcologne.de) | 04:27 | |
| + jn (~quassel@user/jn/x-3390946) | 04:27 | |
| - S0rin (QUIT: Ping timeout: 264 seconds) (~S0rin@user/s0rin) | 04:29 | |
| + mark_ (~mjw@82-169-127-166.fixed.kpn.net) | 04:38 | |
| + S0rin (~S0rin@user/s0rin) | 04:47 | |
| - mark_ (QUIT: Ping timeout: 255 seconds) (~mjw@82-169-127-166.fixed.kpn.net) | 05:27 | |
| + mrdaught (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 05:56 | |
| - mrdaught (QUIT: Read error: Connection reset by peer) (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 05:57 | |
| - S0rin (QUIT: Remote host closed the connection) (~S0rin@user/s0rin) | 06:18 | |
| + mrdaught (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 06:47 | |
| - mrdaught (QUIT: Read error: Connection reset by peer) (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 07:04 | |
| + mrdaught (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 07:10 | |
| - mrdaught (QUIT: Read error: Connection reset by peer) (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 07:18 | |
| + mrdaught (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 07:22 | |
| - mrdaught (QUIT: Read error: Connection reset by peer) (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 07:25 | |
| + mrdaught (~mrdaught@184.147.249.228) | 07:42 | |
| - mrdaught (QUIT: Read error: Connection reset by peer) (~mrdaught@184.147.249.228) | 07:46 | |
| + mrdaught (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 08:04 | |
| - mrdaught (QUIT: Read error: Connection reset by peer) (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 08:14 | |
| + mrdaught (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 09:55 | |
| - mrdaught (QUIT: Read error: Connection reset by peer) (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 10:00 | |
| josch | so... | 10:22 |
| josch | one cell is completely dead | 10:22 |
| josch | i switched it for a new cell and everything works again | 10:22 |
| josch | odd... | 10:22 |
| josch | but something is still weird | 10:23 |
| josch | when looking at the oled battery monitor, i can see that the current switches between 0.0A and around 0.4A | 10:24 |
| josch | it is probably trying to charge the one cell which is more empty than the rest but shouldn't it be constantly at around -0.4A then? | 10:24 |
| josch | why does it switch forth and back every few seconds? | 10:24 |
| josch | at least my system does not power off when i remove it from wall power | 10:25 |
| + mark_ (~mjw@82-169-127-166.fixed.kpn.net) | 10:34 | |
| josch | but somehow, according to the OLED my new cell is stuck at 2.9V even though i've had the system plugged in for half an hour. Seems it's not charging it. | 10:55 |
| + mrdaught (~mrdaught@184.147.249.228) | 11:05 | |
| - mrdaught (QUIT: Read error: Connection reset by peer) (~mrdaught@184.147.249.228) | 11:08 | |
| minute | josch: do you still use that weird pwm charging patch? | 12:18 |
| minute | if so, i would say remove it and use my soft start patch for lpc fw | 12:19 |
| - Nixkernal (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@2a02:1210:1613:e600:1cb7:1fd3:e008:ef75) | 12:20 | |
| + Nixkernal (~quassel@2a02:1210:1613:e600:ec71:516a:6d9c:5759) | 12:22 | |
| + reform27856 (~root@win7148.informatik.uni-wuerzburg.de) | 12:29 | |
| reform27856 | hello from ls1028a reform | 12:29 |
| reform27856 | the good news: display comes on with ls1028a even without the initramfs explicitly modprobing a bunch of modules | 12:30 |
| reform27856 | the bad news: i swapped my mainboard for the old one (which had the ls1028a attached) and still have the new protected battery boards. one of my cells doesn't charge and is stuck at 2.9V for more than half an hour | 12:30 |
| reform27856 | also odd: could it be that the unprotected and the protected battery boards are wired differently? I have this one cell at 2.9V and it shows up at the top of the oled with the new boards and at the bottom with the old unprotected battery board | 12:31 |
| reform27856 | i'll read your reply in the online irc logs | 12:32 |
| - reform27856 (QUIT: Client Quit) (~root@win7148.informatik.uni-wuerzburg.de) | 12:32 | |
| + reform15008 (~root@win7148.informatik.uni-wuerzburg.de) | 12:40 | |
| reform15008 | i now swapped the battery board to the old unprotected one. The 2.9V battery switched places. I'm quite sure that i'm inserting the cells in the identical order as they are color-coded. | 12:40 |
| reform15008 | but still no charging. with both old mainboard and old battery board... uff... | 12:40 |
| reform15008 | on the plus side, i found some bugs for the new reform-tools version... now switching back to the new mainboard and a311d... | 12:41 |
| - reform15008 (QUIT: Client Quit) (~root@win7148.informatik.uni-wuerzburg.de) | 12:41 | |
| josch | i also replaced the 2.9V cell with another -- same effect | 12:55 |
| josch | well, at least the reform doesn't switch off anymore when i pull the plug | 12:55 |
| minute | josch: maybe an issue with the power supply/usb-c adapter then? | 12:58 |
| josch | minute: throughout all my tests in the past four hours i used the original power supply | 13:08 |
| josch | golly it charges now | 13:08 |
| josch | wtf | 13:08 |
| josch | okay, current setup is the new motherboard 2.5 but the side that had the failing batteries has the old unprotected battery board | 13:08 |
| josch | once i find more time for this, i shall swap the unprotected for a protected one and see what happens... | 13:09 |
| josch | no, false alarm | 13:09 |
| josch | it charged for a bit and managed to get the cell from 2.9 V to 3.0 V | 13:09 |
| josch | this is now with the usb-c pd adapter. Again it switches from 0.0A to -0.9A every few seconds | 13:10 |
| - erle (QUIT: Remote host closed the connection) (~erle@2a02:8109:da01:6400::311a) | 13:45 | |
| + chomwitt (~chomwitt@2a02:587:7a18:fc00:1ac0:4dff:fedb:a3f1) | 13:48 | |
| sir-photch | USB-C power delivery? On the reform? | 14:00 |
| - chomwitt (QUIT: Ping timeout: 268 seconds) (~chomwitt@2a02:587:7a18:fc00:1ac0:4dff:fedb:a3f1) | 14:17 | |
| josch | sir-photch: using an adapter like this: | 14:21 |
| josch | https://community.mnt.re/t/will-we-be-able-to-usb-power-mnt-reform/241/40 | 14:22 |
| josch | sir-photch: there are multiple options in that thread | 14:22 |
| + mrdaught (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 14:51 | |
| minute | josch: maybe it works as intended, as the cells are disbalanced | 14:59 |
| minute | so it has to stop regularly and discharge all the other cells | 14:59 |
| minute | josch: if you call up the system status (circle s) regularly maybe you see balancing or cooldown status? | 15:00 |
| + chomwitt (~chomwitt@2a02:587:7a18:fc00:1ac0:4dff:fedb:a3f1) | 15:06 | |
| josch | which part in the circle-s output shows me the balancing/cooldown status? | 15:16 |
| josch | it's just odd because the thing has now been plugged in for 3 hours and isn't balanced yet | 15:17 |
| josch | it might of course also be that my replacement cells are faulty | 15:17 |
| josch | i'm going to get a few more from eremit to make sure | 15:17 |
| - chomwitt (QUIT: Ping timeout: 264 seconds) (~chomwitt@2a02:587:7a18:fc00:1ac0:4dff:fedb:a3f1) | 15:18 | |
| josch | can anybody recommend a device dedicated to finding out how much charge my lifepo4 cells have left? | 15:19 |
| - mrdaught (QUIT: Read error: Connection reset by peer) (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 15:20 | |
| + mrdaught (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 15:21 | |
| josch | funny, the cell is now down to 1.5 V | 15:24 |
| josch | the oled keeps cycling with "starting up lpc X %" message | 15:24 |
| josch | but the system is still on | 15:24 |
| - mrdaught (QUIT: Read error: Connection reset by peer) (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 15:40 | |
| - Nixkernal (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@2a02:1210:1613:e600:ec71:516a:6d9c:5759) | 15:42 | |
| - mark_ (QUIT: Ping timeout: 255 seconds) (~mjw@82-169-127-166.fixed.kpn.net) | 15:42 | |
| + mrdaught (~mrdaught@184.147.249.228) | 15:43 | |
| - mrdaught (QUIT: Read error: Connection reset by peer) (~mrdaught@184.147.249.228) | 15:43 | |
| + mrdaught (~mrdaught@184.147.249.228) | 15:55 | |
| - mrdaught (QUIT: Read error: Connection reset by peer) (~mrdaught@184.147.249.228) | 15:57 | |
| minute | josch: ok something is seriously weird | 16:17 |
| minute | josch: i used to use a nightcore charger to charge individual cells | 16:17 |
| hramrach | josch: they removed some of the USB3 support between revisions because of https://gitlab.collabora.com/hardware-enablement/rockchip-3588/linux/-/issues/8 | 16:34 |
| hramrach | but they also changed the structure of the bindings so it's difficult to enable again | 16:36 |
| + mrdaught (~mrdaught@184.147.249.228) | 16:37 | |
| hramrach | Would be nice if the patches in debian/patches/rk3588 applied with git am. While the Collabora patches do the Refrom patches are missing some header and won't apply | 16:40 |
| - mrdaught (QUIT: Read error: Connection reset by peer) (~mrdaught@184.147.249.228) | 16:42 | |
| + mark_ (~mjw@145.15.244.207) | 16:53 | |
| hramrach | they removed the USB PHY bindings from all boards betweent the patchset revisions so it's probably OK to not habve them, there is a lot of other changes as well | 16:56 |
| + chomwitt (~chomwitt@2a02:587:7a18:fc00:1ac0:4dff:fedb:a3f1) | 17:08 | |
| + wielaard (~mjw@84.241.199.219) | 17:18 | |
| - mark_ (QUIT: Ping timeout: 272 seconds) (~mjw@145.15.244.207) | 17:21 | |
| - chomwitt (QUIT: Ping timeout: 268 seconds) (~chomwitt@2a02:587:7a18:fc00:1ac0:4dff:fedb:a3f1) | 17:29 | |
| + erle (~erle@2a02:8109:da01:6400::311a) | 17:36 | |
| + mrdaught (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 17:38 | |
| + mjw (~mjw@84.241.201.90) | 17:40 | |
| - mrdaught (QUIT: Read error: Connection reset by peer) (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 17:42 | |
| - wielaard (QUIT: Ping timeout: 256 seconds) (~mjw@84.241.199.219) | 17:43 | |
| - mjw (QUIT: Ping timeout: 272 seconds) (~mjw@84.241.201.90) | 18:01 | |
| josch | hramrach: which patch do you see that is missing a header? I exported the collabora rk3588 patch stacks using git format-patch | 18:09 |
| + mjw (~mjw@84.241.201.90) | 18:10 | |
| josch | minute: but does that charger have a mode that allows you to fully discharge, then charge and it tells you how much "fits"? | 18:10 |
| josch | or fully charge and then discharge across a resistor and measure how much got out until down to X volts? | 18:11 |
| + mark_ (~mjw@gnu.wildebeest.org) | 18:15 | |
| - mjw (QUIT: Ping timeout: 252 seconds) (~mjw@84.241.201.90) | 18:17 | |
| - erle (QUIT: Remote host closed the connection) (~erle@2a02:8109:da01:6400::311a) | 18:22 | |
| + erle (~erle@2a02:8109:da01:6400::311a) | 18:23 | |
| + chomwitt (~chomwitt@2a02:587:7a18:fc00:1ac0:4dff:fedb:a3f1) | 18:28 | |
| minute | josch: hmm i think not | 18:34 |
| josch | i've now bought at eremit four times, so the cells i have here are in a wild stage of how much they were used | 18:45 |
| josch | and even those that came from the same batch (for example the very first) varied a lot in how quickly they dropped voltage when discharged by the reform | 18:45 |
| minute | hmmhmm | 18:58 |
| josch | my current method is to plug them into the reform, wait for the reform to switch off and see which of the eight batteries was the culprit :) | 19:00 |
| josch | minute: can you confirm that the protected battery boards are wired in opposite order compared to the non-protected ones? | 19:00 |
| minute | josch: i recently figured out the order | 19:01 |
| minute | and wrote in handbook v2 | 19:01 |
| minute | the order of left and right pack are mirrored | 19:01 |
| minute | but not in the UI | 19:01 |
| minute | not really mirrored, but rotated, the board is rotated 180 degrees | 19:01 |
| minute | so in the interface the 4 right batteries are like 4,3,2,1 in the pack and the ones on the left are like 1,2,3,4 when you look at the reform | 19:02 |
| josch | minute: but it depends on which battery board you have, right? | 19:05 |
| minute | josch: should not. | 19:05 |
| minute | josch: the old battery board is rotated in the same way | 19:05 |
| josch | i will check again tomorrow | 19:06 |
| minute | did you perhaps plug a cable in the wrong way around? (not sure if that's possible though) | 19:06 |
| josch | but i put the batteries in in the same order (100% sure of the order because the cells are color coded) but the one cell with 2.9 V showed up at the right bottom in the oled for the unprotected boards | 19:06 |
| minute | (it definitely wouldn't charge then ^^) | 19:06 |
| josch | and with the protected battery boards the 2.9 V cell shows up at the right top | 19:06 |
| josch | it's possible to plug in the cable the wrong way round??? o0 | 19:07 |
| josch | that would be something | 19:07 |
| minute | i'm asking because you were not aware of the locking mechanism before | 19:07 |
| josch | i would've expected that such a mistake would fry my reform XD | 19:07 |
| minute | but perhaps it's not possible | 19:07 |
| josch | yes, my locking mechanism is totally non-existant | 19:07 |
| josch | (because it got ripped out too often) | 19:07 |
| josch | i'll check again tomorrow | 19:07 |
| minute | ok so maybe you're seeing another effect... the top cell at least shows a slightly different voltage on protected vs non-protected pack | 19:08 |
| minute | i think the most "real" values are measured when the reform is off and not connected to power jack | 19:09 |
| minute | i.e. when the cells are neither under load nor being charged | 19:09 |
| josch | i think if i had plugged the cable the wrong way round, no connection would be made at all (if i understand the connector correctly) | 19:09 |
| minute | yeah you're right | 19:09 |
| josch | but i'm quite sure it's connected because if i remove wall power | 19:09 |
| josch | currently without wall power -- can stilly type :) | 19:09 |
| josch | something to investigate for tomorrow | 19:10 |
| josch | this is quite odd | 19:10 |
| minute | ok | 19:12 |
| minute | yeah | 19:12 |
| josch | more info from lukas about the rk3588 release: https://community.mnt.re/t/mnt-reform-rcore-rk3588-processor-module-release/1924/1 | 19:30 |
| hramrach | josch: dw-hdmi-rockchip-avoid-tmds-spam.patch and dts are not exported with format-patch | 19:30 |
| josch | ah :) | 19:32 |
| josch | thank you, that was quite the obvious oversight from my end | 19:32 |
| josch | hramrach: you are currently looking at the .dsc sources i uploaded? | 19:33 |
| hramrach | yes | 19:33 |
| josch | hramrach: i assume it's sufficient from your end if i only fix this on my next upload? | 19:34 |
| hramrach | yes, that's completely fine | 19:34 |
| hramrach | I was looking if there is some obvios discrepancy between the two patches and the only conclusion I have is that they updated the patchstack with multiple changes, and if the update does not work the individual changes need to be bisected | 19:35 |
| josch | yes, i prepared two different uploads to find out whether the breaking change is in the patch stack or in the changes between 6.8-rc1 and 6.8-rc7 | 19:36 |
| hramrach | for that I tried to apply the patchstack on the Linux git tree to compare with range-diff, and obviously that works poorly when the patches don't apply | 19:36 |
| josch | right :) | 19:36 |
| + mrdaught (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 19:38 | |
| - mrdaught (QUIT: Read error: Connection reset by peer) (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 19:39 | |
| - erle (QUIT: Quit: Democracy must always be better armed than tyranny.) (~erle@2a02:8109:da01:6400::311a) | 19:56 | |
| - elektron (QUIT: Ping timeout: 255 seconds) (~elektron@dom0.halo.nu) | 19:59 | |
| + elektron (~elektron@dom0.halo.nu) | 20:00 | |
| + erle (~erle@2a02:8109:da01:6400::311a) | 20:02 | |
| minute | current uptime on my rk3588 reform: 20:49:05 up 1 day, 4:34 | 20:49 |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 21:20 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 22:59 | |
| + mrdaught (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 23:39 | |
| - mrdaught (QUIT: Read error: Connection reset by peer) (~mrdaught@bras-base-toroon01zb3-grc-78-184-147-249-228.dsl.bell.ca) | 23:40 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!