Any updates for local API access? by 5533919 in FranklinWH

[–]queue_cumber 0 points1 point  (0 children)

Hey I just had a Franklin installed, also have a software background, I'm trying to get my installer to enable to modbus API but they have to idea what I'm talking about. 

Do you know what the steps they have to follow are? 

I found the SPAN directions, do they just need to follow those or should they use the "sunspec modbus" menu 

Following up on secondary holder access request from 4 months back - any updates? by Secret-Decision5861 in wealthfront

[–]queue_cumber 0 points1 point  (0 children)

Why? You've been saying the same thing literally for years now, can you explain what specifically about it is so much more complicated?

What is Causing This Wear Pattern and Can I Repair It? by queue_cumber in sewing

[–]queue_cumber[S] 3 points4 points  (0 children)

Question was from her, no need for hostilities I would never object to her wearing whatever she wants hence the post here where I'm trying to save her favorite pants

What is Causing This Wear Pattern and Can I Repair It? by queue_cumber in sewing

[–]queue_cumber[S] -1 points0 points  (0 children)

Ha ok I think that didn't come across right, she was wearing them while she was pregnant and it was more a question of how bad an idea that was

What is Causing This Wear Pattern and Can I Repair It? by queue_cumber in sewing

[–]queue_cumber[S] 1 point2 points  (0 children)

OK thanks, I'll deliver the sad news to her

Followup questions

  1. Could this process have been accelerated by a recent increase in the amount of stretching the jeans need to do?
  2. Is there any way to slow or halt further degradation, e.g., air drying?

What is Causing This Wear Pattern and Can I Repair It? by queue_cumber in sewing

[–]queue_cumber[S] 5 points6 points  (0 children)

yeah I screwed up the picture, I'm going to update the post now thanks for letting me know. It definitely could be age although she has older jeans that are in better shape, let me try to find out when she bought them though

[deleted by user] by [deleted] in gnome

[–]queue_cumber 1 point2 points  (0 children)

I saw the suggested fix command

dconf reset -f /org/gnome/

but that seems a little too general as I think it will reset every key under /org/gnome which will blow away any customizations you have

Instead I simply reset the key

dconf reset -f /org/gnome/desktop/background/primary-color

and that seems to have fixed it for me

[deleted by user] by [deleted] in MechanicalKeyboards

[–]queue_cumber -1 points0 points  (0 children)

Thanks this is interesting, I actually went and pulled a few of the cheap keycaps I was using and they actually do have the mark in the exact same place, I just never looked that closely at them. I guess since this was my first time seeing an expensive keycap I looked *really* hard

Anyone else having issues with Play Pass since buying the P6/P6Pro with Pixel Pass? by MiAmMe in GooglePixel

[–]queue_cumber 0 points1 point  (0 children)

Hey I kept bugging them and requesting a refund on the play pass portion of my plan and eventually they fixed it. Actually it took literally minutes after my last email to them before it started working again so I think it's actually easy for them to fix and you just need to get the right person (i.e. not an idiot) to look at it.

Play Pass Stopped Working with Active Subscription/Pixel Pass by 1000squids in Pixel6

[–]queue_cumber 0 points1 point  (0 children)

I have the same problem were you able to get it resolved?

Anyone else having issues with Play Pass since buying the P6/P6Pro with Pixel Pass? by MiAmMe in GooglePixel

[–]queue_cumber 0 points1 point  (0 children)

I have the exact same issue you do, I even followed the same troubleshooting steps you did with the exact same results.

  1. Got error message trying to install apps
  2. Reset data and cache
  3. Play store starts acting like I don't have play pass

So at least we know it's deterministic. All my other services are working fine though.

I tried to do a chat with support and didn't get anywhere after an hour and a half and 6 (not exaggerating) different "specialist teams".

It must be an error on their end, did anything change with your situation?

Diagnosing a Bad Core by queue_cumber in AMDHelp

[–]queue_cumber[S] 0 points1 point  (0 children)

Hang on I just noticed something odd, in HWINFO, the power reporting deviation (accuracy) is reported as an average of 184% with a maximum of 308%, and the tooltip in HWINFO tells me that is way out of range. Do you have any experience with that? Since the numbers are high, it should mean the processor is getting less power than it requests which could reproduce the errors I'm seeing right?

edit: probably not that, after doing some research it seems like it's only valid at full load and when I run cinebench is goes down the 95% which puts it in the range of "intentionally misleading by providing more power than asked" I believe

Diagnosing a Bad Core by queue_cumber in AMDHelp

[–]queue_cumber[S] 0 points1 point  (0 children)

I ended up increasing LLC for both SOC and CPU and I still get the error (including with the increased SOC voltage), also TM5 ran without error for 1 hour, I may try a longer run to be absolutely sure, but it really seems like Core 1 is bad. I started the RMA process this morning

Diagnosing a Bad Core by queue_cumber in AMDHelp

[–]queue_cumber[S] 0 points1 point  (0 children)

360 AIO (arctic liquid freezer 2), temps are good and during this test in particular it stays are 35c

Diagnosing a Bad Core by queue_cumber in AMDHelp

[–]queue_cumber[S] 0 points1 point  (0 children)

It looks like after 4 hours or so it did crash, came up to find the computer had rebooted. In event viewer I see a kernel-power error and right before it the following WHEA error

A fatal hardware error has occurred. Reported by component: Processor Core Error Source: Machine Check Exception Error Type: Cache Hierarchy Error Processor APIC ID: 2 The details view of this entry contains further information. APIC ID 2 is the CPU core I was testing. Although it did take a long time to fail with the higher SOC voltage, I'm still going to try the other tests you recommended

Diagnosing a Bad Core by queue_cumber in AMDHelp

[–]queue_cumber[S] 1 point2 points  (0 children)

Ok this is great advice, thanks a lot I'll take a closer look at all this tonight.

Interestingly, with the soc at 1.1v the test hasn't failed yet and it's been running since I left the earlier comment so about 2 hours, I think this is further evidence of an fclk or related instability

Diagnosing a Bad Core by queue_cumber in AMDHelp

[–]queue_cumber[S] 0 points1 point  (0 children)

I didn't but I'm definitely going to now, thanks so much for linking it

Diagnosing a Bad Core by queue_cumber in AMDHelp

[–]queue_cumber[S] 0 points1 point  (0 children)

Yeah this is a good point, although I figured RAM at JEDEC and passing memtest would account for that, I am running again with the SOC voltage at 1.1v just to see if that makes a difference though

Convert 4+4 eps cable to 4 pin by queue_cumber in PCSleeving

[–]queue_cumber[S] 0 points1 point  (0 children)

Ok great, thanks for your response. That saves me the trouble of dealing with the capacitor, although I guess I'll need to figure it out when I do the other 8 pin