| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50) | 00:04 | |
| * brennen -> brennen|afk | 00:45 | |
| - gnou_liber (QUIT: Read error: Connection reset by peer) (~gnou_libe@223.pool85-50-3.static.orange.es) | 01:10 | |
| + gnou_liber (~gnou_libe@223.pool85-50-3.static.orange.es) | 01:10 | |
| - gnou_liber (QUIT: Ping timeout: 268 seconds) (~gnou_libe@223.pool85-50-3.static.orange.es) | 01:15 | |
| + gnou_liber (~gnou_libe@223.pool85-50-3.static.orange.es) | 01:15 | |
| - eschaton (QUIT: Remote host closed the connection) (~eschaton@li541-49.members.linode.com) | 01:17 | |
| - mtm- (QUIT: Ping timeout: 240 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 02:02 | |
| chartreuse | Alright old FET removed, now to clean the pads | 03:13 |
|---|---|---|
| chartreuse | Did accidentally desolder D7 next to it >_> | 03:15 |
| chartreuse | Ooph, completely burned the connector next to it, even with the foil. Clearly took too long in heating it up | 03:25 |
| chartreuse | And damaged the hack the plannet connector some as well. Ooops. Guess I can replace those later, but need to be more careful with hot air | 03:25 |
| + mtm- (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 04:10 | |
| - gnou_liber (QUIT: Ping timeout: 268 seconds) (~gnou_libe@223.pool85-50-3.static.orange.es) | 04:15 | |
| + bluerise_ (~bluerise@pc19f8093.dip0.t-ipconnect.de) | 04:30 | |
| - bluerise (QUIT: Ping timeout: 276 seconds) (~bluerise@user/bluerise) | 04:31 | |
| - S0rin (QUIT: Ping timeout: 268 seconds) (~S0rin@user/s0rin) | 04:32 | |
| + S0rin (~S0rin@user/s0rin) | 04:34 | |
| + gnou_liber (~gnou_libe@223.pool85-50-3.static.orange.es) | 04:42 | |
| chartreuse | Well crud, plug it in and immediately see some smoke in that area. Can't see where it was coming from though so will have to plug it in again >_> | 04:42 |
| chartreuse | Possible I guess the hack the planet connector could have shorted two pins, but seems unlikely | 04:43 |
| chartreuse | U12 looks a little suspicious like I might have heated it enough to shift the pins and possibly bridge | 04:45 |
| chartreuse | Oh what the... The body diode on the brand new 7850 is shorted again, it was fine before I powered it | 04:46 |
| chartreuse | It's like something in the circuit is killing it | 04:47 |
| + eschaton (~eschaton@li541-49.members.linode.com) | 04:49 | |
| chartreuse | Can't tell if D5 died with it or if it maybe was shorted and I somehow missed that before. | 04:50 |
| chartreuse | Considering D5 is in parallel with the mosfet body diode, I'm not sure how I measured that diode fine before but Q17 blown.... | 04:51 |
| chartreuse | Though checking the mosfet I removed it definitly was blown | 04:52 |
| chartreuse | Welp removed D5 and it seems shorted, but annoyingly Q17 is shorted again... I did buy a second but would like to make sure that's the root cause of the problem before just redoing it again :/ | 05:04 |
| chartreuse | I don't believe it was shorted before since I measured the body diode on Q17 after replacing it as a test and didn't see a short then | 05:05 |
| chartreuse | I am seeing seemingly 0.0 ohms across L1, though not sure what the DC resistance of a 11uH inductor would be | 05:08 |
| + hochata (~user@user/hochata) | 07:01 | |
| Boostisbetter | bummer chartreuse: I hope you are able to get it sorted regardless. | 07:10 |
| Boostisbetter | josch: this may be idiotic, but how exactly do I install the headers you compiled. When I try it says they are dependent on other things, and when I install those things that say it is dependent on the other. | 07:10 |
| josch | Boostisbetter: i need console output to understand what is going on | 07:12 |
| Boostisbetter | ok, well could you tell me which files need to be installed? Should be only 2 right? | 07:22 |
| Boostisbetter | josch: I have these files: | 07:23 |
| Boostisbetter | linux-headers-5.12.0-trunk-arm64_5.12-1~exp1.1_arm64.deb | 07:23 |
| Boostisbetter | linux-headers-5.12.0-trunk-common_5.12-1~exp1.1_all.deb | 07:23 |
| Boostisbetter | linux-headers-arm64_5.12-1~exp1.1_arm64.deb | 07:23 |
| Boostisbetter | linux-libc-dev_5.12-1~exp1.1_arm64.deb | 07:23 |
| Boostisbetter | linux-support-5.12.0-trunk_5.12-1~exp1.1_all.deb | 07:23 |
| Boostisbetter | do all of them need to be installed? | 07:24 |
| Boostisbetter | and to install them I am just using apt? | 07:25 |
| josch | Boostisbetter: i don't think you need the linux-support package | 07:25 |
| josch | Boostisbetter: yes, you install them with apt | 07:25 |
| Boostisbetter | does the order matter? Or is apt smart enough to sort that? | 07:26 |
| - Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149-210-16-215.mobile.nym.cosmote.net) | 07:26 | |
| josch | Boostisbetter: the order should not matter | 07:26 |
| + Ar|stote|is (~linx@149-210-16-215.mobile.nym.cosmote.net) | 07:27 | |
| Boostisbetter | The following packages have unmet dependencies: | 07:28 |
| Boostisbetter | linux-headers-5.12.0-trunk-arm64 : Depends: linux-kbuild-5.12 (>= 5.12-1~exp1.1) but it is not installable | 07:28 |
| Boostisbetter | but also apt keeps defaulting to other packages already installed. | 07:28 |
| Boostisbetter | Note, selecting 'linux-headers-5.12.0-trunk-arm64' instead of '/home/committed88/Downloads/linux-headers-5.12.0-trunk-arm64_5.12-1~exp1.1_arm64.deb' | 07:29 |
| Boostisbetter | just as an example of what I mean | 07:29 |
| josch | Boostisbetter: you have to install linux-kbuild-5.12 as well | 07:36 |
| josch | Boostisbetter: of course apt keeps defaulting to other packages :) | 07:37 |
| Boostisbetter | josch: why of course? | 07:39 |
| Boostisbetter | josch: also kbuild is not somethign in your directory tree and it is not available in the repos i'm using | 07:39 |
| josch | Boostisbetter: if it's not available in that directory, i have to investigate | 07:40 |
| Boostisbetter | josch: thanks. Sorry for being such a pain. | 07:44 |
| Boostisbetter | I was trying to use the latest kernel with the workaround, but it is starting to crash every 3-4 times I resume from it. | 07:45 |
| Boostisbetter | WIth 5.12 this was more like every 20-30 times | 07:45 |
| Boostisbetter | josch: also is there a way to know that you should restart after getting updates? | 07:47 |
| josch | Boostisbetter: you are not running stable, so there are no security fixes :) | 07:49 |
| Boostisbetter | josch: well I am occasionally. In my uboot menu I have a 6.1.0 kernel and a 6.1.0-8 kernel | 07:57 |
| Boostisbetter | I have been using the -8 one assuming that this is the most current version. | 07:57 |
| Boostisbetter | would that be correct? | 07:57 |
| josch | Boostisbetter: no, you are not using stable. You are using testing. | 07:59 |
| josch | yes, 6.1.0-8 is maybe the most current one | 07:59 |
| josch | mabe, because there are multiple varieties of 6.1.0-8 -- this number doesn't tell you the kernel version precise enough to know whether you really have the latest version | 08:00 |
| josch | you can check whether you have the latest one by running "apt update" and then "apt-cache policy linux-image-arm64" | 08:01 |
| Boostisbetter | what if I want stable and not latest? | 08:05 |
| josch | Boostisbetter: you could do that if you backport the patches to the Debian stable kernel | 08:06 |
| Boostisbetter | josch: well I guess I don't mean what I am saying. I want whatever I'm supposed to have. | 08:06 |
| Boostisbetter | if that makes sense. | 08:07 |
| josch | what are you supposed to have? | 08:07 |
| Boostisbetter | and should I be using plain 6.1.0 instead of the -8 version if stability is my preference? | 08:07 |
| Boostisbetter | whatever comes with v3 of the system image | 08:07 |
| josch | then you should be using 6.1.25-1+reform20230428T084918Z1 | 08:07 |
| josch | 6.1.0 is just the kernel version without abi number | 08:08 |
| Boostisbetter | yeah, so that should be what I am using, if I didn't do anything other than install 5.12 | 08:09 |
| Boostisbetter | according to apt-policy, I have the version you are talking about installed. | 08:10 |
| Boostisbetter | So I guess my question is, which kernel should I be selecting at uboot to use that. | 08:11 |
| Boostisbetter | because I have a 6.1.0 and a 6.1.0-8 option there | 08:11 |
| josch | Boostisbetter: ah the reason for that is because i messed up the abi number in the past and only recently fixed it | 08:14 |
| josch | Boostisbetter: you should be selvecting 6.1.0-8 | 08:14 |
| Boostisbetter | josch, never fear I have been. | 08:14 |
| Boostisbetter | thanks! | 08:14 |
| - hochata (QUIT: Ping timeout: 256 seconds) (~user@user/hochata) | 08:48 | |
| - gnou_liber (QUIT: Read error: Connection reset by peer) (~gnou_libe@223.pool85-50-3.static.orange.es) | 09:12 | |
| + gnou_liber (~gnou_libe@223.pool85-50-3.static.orange.es) | 09:18 | |
| * bluerise_ -> bluerise | 10:04 | |
| - GNUmoon2 (QUIT: Read error: Connection reset by peer) (~GNUmoon@gateway/tor-sasl/gnumoon) | 10:19 | |
| + GNUmoon2 (~GNUmoon@gateway/tor-sasl/gnumoon) | 10:19 | |
| - gnou_liber (QUIT: Read error: Connection reset by peer) (~gnou_libe@223.pool85-50-3.static.orange.es) | 10:47 | |
| + gnou_liber (~gnou_libe@223.pool85-50-3.static.orange.es) | 11:07 | |
| minute | chartreuse: in case you're stuck, send us the board (we can also make a ups label to make that not hyper expensive from outside EU, in that case just email support@mntre.com) | 12:15 |
| josch | Boostisbetter: I'm afraid building a 5.12 kernel with kbuild will be challenging because of some compilation errors: https://mister-muffin.de/p/S5fR.txt | 12:24 |
| josch | scripts/kconfig/menu.c:43:9: error: ‘current_entry’ undeclared (first use in this function) | 12:25 |
| josch | Boostisbetter: I will need to find some time to look into those. No idea when I'll manage that. | 12:25 |
| Boostisbetter | josch: I really appreciate all of your help. If it is too difficult with please don't stress. I can also just work with the 6.1 kernel v3 is using. | 12:41 |
| - mtm- (QUIT: Ping timeout: 268 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 14:04 | |
| - klardotsh (QUIT: Quit: zzz) (~klardotsh@172.58.47.100) | 15:36 | |
| + mtm- (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 16:10 | |
| Booster[m] | it is kind of a bummer, but i am finding the resume a lot more hit or miss. I am getting about 3 or 4 resumes before a crash. I am really curious what is causing the screen to not initialize. | 19:31 |
| josch | Boostisbetter: with 6.1, right? | 19:35 |
| sigrid | does it always look the same, just black screen with backlight on? | 19:35 |
| Boostisbetter | yes | 19:38 |
| Boostisbetter | josch: yes. | 19:38 |
| Boostisbetter | I wonder if there is something I can do before suspending that will kind of protect open programs in the event that there is a crash. | 19:39 |
| Boostisbetter | For me suspend is so convienent becuase I can get back into my workflow immediately. On a cold boot I have to fire everything back up, and wait for it all to be ready. | 19:39 |
| josch | that's how it is for everybody :) | 19:44 |
| Boostisbetter | I was just about to ask that. | 19:44 |
| josch | this is why i have my system running 24/7 | 19:44 |
| josch | i don't want to loose my state | 19:44 |
| Boostisbetter | I like the idea of allowing hardware to rest while not being completely powered down. I'm not crazy about leaving the machine on all the time as a result of temps and things not ever really getting a rest period. | 19:44 |
| Boostisbetter | josch: but I might have to start doing something similar. | 19:45 |
| Boostisbetter | and just rely on standby when I have to take the Reform with me somewhere and need to conserve power. | 19:45 |
| Boostisbetter | I wonder if we could put a bounty together to solve this issue. | 19:45 |
| Boostisbetter | I'm sure whatever is discovered here will help the Pocket Reform as well. | 19:45 |
| josch | if somebody does that, it would be worth my money as well | 19:53 |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50) | 19:57 | |
| Boostisbetter | I'm just getting started with Linux development as someone who has been doing Windows development most of his adult life. | 20:42 |
| Boostisbetter | I would love to tackle it, but I know it is beyond the time i have to personally throw at it. | 20:43 |
| Boostisbetter | maybe one day. It would be awesome to contribute to the dev party surrounding MNT. | 21:19 |
| chartreuse | minute: All the voltage rails seem fine (not shorted) checking resistance. 5v, 3.3, 1.2, LPC_VCC, 1.8, and 1.5 so looking like I might have to take you up on that | 23:46 |
| chartreuse | I'll poke around a little more but we'll see | 23:46 |
| chartreuse | Did just spot a small piece of al foil left behind, even though I thoughogly cleaned the board and inspected it before powering, not sure if I accidentally introduced that when probing just now or if it maybe was there and caused a short before :/ | 23:49 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!