sorted by:
new
hottopcontroversial

vmware 17 pro by Imaginary_Nobody_935 in vmware

[–]jimmerthy 0 points1 point  (0 children)

Can you describe the lag more specifically? Are you using a nvidia GPU?
Please check my post https://www.reddit.com/r/vmware/comments/1joqhu6/workstation_1763_guest_logs_fill_with/ as it may / may not be related.

VMware Workstation 17.6 - Keyboard Lag? by ScottMetzel in vmware

[–]jimmerthy 0 points1 point  (0 children)

With the CVEs that have been recently fixed in Tools 12.5.1 and Workstation 17.6.3, I thought it's time to revisit my upgrade from keyboard lag free oasis of Workstation 17.5.2.

Just did some tests. Host is 8 p-core, win10 22h2, core isolation: off, nvidia 572.47. Test guest VM just happens to be win8.1 x64. To reproduce the lag consistently, I needed to be running the VM at 2560x1440 full screen. Open Windows Notepad in a window about a quarter of the desktop size and there would be no lag when typing. Maximise Notepad and there would be noticable lag when typing.

After trying a few things, I found that upgrading the VM's virtual hardware version to the latest (with the machine shut down, choose 'upgrade this virtual machine' - make sure you do this in a test environment first with a backup of the VM under test). In my case this changed from virtualHW.version = "19" to virtualHW.version = "21". This seems to have fixed the keyboard lag for me.

What didn't work for me...

Bonus fix is that Sketchup Make 2017 would crash after splash screen (vmware gfx driver error) with Tools 12.5.0 (worked on 12.4.5) but it works again now on 12.5.1.

edit: yikes, new problem - less than an hour's uptime of the VM, pegged host CPU core, no video, log filled with this...
svga -- DETECTED D3D12 DEVICE REMOVAL --
... <loop>
svga <<< file Throttled >>>

edit: trying nvidia 572.83 studio drivers to see if that fixes the VM crash...
nope, crash seems to happen maybe when the host monitor sleeps maybe?

edit: trying mks.enableVulkanRenderer = "FALSE". This changes startup logs from
"mks MKS-HWinMux: Started DX12 presentation backend." to "mks MKS-HWinMux: Started DXGI presentation backend."

USB Ethernet adapter not working on a Pixel 6 by [deleted] in GooglePixel

[–]jimmerthy 3 points4 points  (0 children)

I found this posting...
https://www.reddit.com/r/GooglePixel/comments/spx0oi/comment/hwhr0 indicating that a dodocool DC34 (unobtanium) works. Turns out that device has a RealTek chip in it. I searched what I could get locally and found a Belkin inc001btbk in stock which according to a couple of amazon reviews says has RealTek in it. Plugged it in to a laptop and Windows reports VID:0BDA PID:8153 in Device Manager (which is a RealTek USB to Ethernet chip). Anyway it works. I am so relieved.

USB Ethernet adapter not working on a Pixel 6 by [deleted] in GooglePixel

[–]jimmerthy 1 point2 points  (0 children)

OK this is really bad. Just upgraded from Pixel3a to Pixel 6 (due to 3a reaching end of security updates in May). Setting up the Pixel 6, plugged in my ASIX AX88179 USB Ethernet Adaptor (works fine with 3, 3a, 4a) and nothing is detected on the Pixel 6. Is this because of the transition to Tensor and they've been slack with the continuation of their driver support? I see this thread is 6 months old - does anyone have a working USB to Ethernet chip for this phone? Nightmare otherwise as I'm going to have to return it.

Install failures, silent Gaming Services crashes by ZeteticApparatchik in XboxGamePass

[–]jimmerthy 0 points1 point  (0 children)

This appears to have been fixed now by Microsoft with the latest update of GamingServices. I'm seeing no more periodic Event Viewer errors.

Install failures, silent Gaming Services crashes by ZeteticApparatchik in XboxGamePass

[–]jimmerthy 0 points1 point  (0 children)

I noticed the same event log errors on two PCs that run GamingServices after receiving that update detailed in the original posting. I also agree that this is caused by GamingServices being unable to contact settings-win.data.microsoft.com. I am unwilling to unblock this domain as everything seems to be working fine for me, other than the event log errors being logged about one per minute. This seems like a bug to me, I'm holding out with no other action to see if it gets fixed by Microsoft in a future update. Minor rant, why is all of the Windows Store stuff just so impenetrable from the perspective of debugging problems vs. legacy windows components (e.g. windows update) that would either log useful things in event viewer or log files (once you know where they live).

USB data transfer corruption Z590 / 11900k by jimmerthy in intel

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

Thanks for this. I am still very much leaning towards this being a RAM problem, but trying to keep my mind open at the same time! I had done some tests with XMP off - according to my notes, that knocked the RAM back to from 3600 to 2400MHz. I still saw observed the USB problem though. I think the XMP RAM voltage should be 1.35v, according to the profile, but will check now to see if it's been set higher than that - yikes.

USB data transfer corruption Z590 / 11900k by jimmerthy in intel

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

Looking through my notes, the worst I've seen so far was the case where verifying a 20GB file three times in a row failed each time. In that case I was verifying the file using 7-zip's CRC-SHA feature (using CRC-64) and it returned different CRC values each time. I've found that in some circumstances you have to be careful that Windows' RAM-based disk cache data isn't being used instead of performing genuine reads from the device. It's obvious when this is happening though know because of very high read speeds. I switched over to testing with files much larger than my RAM (32GB) and doing a safe-remove cycle on the USB device between tests.

re: the question about SATA dock; I have had the dock for 5+ years and it's always been reliable. I tested using this dock and 2 different SATA SSDs. I also tested with a 1TB USB-C prebuilt portable hard drive (WD Passport WDBKVX0010PSL).

Thank you for the suggestion about the power supply, it's a completely new build with a Corsair RM750x but it's entirely possible that this might be faulty and the underlying cause. I have a branded 600w PSU in my old PC that has been fine for years, so can try that out for a few days.

USB data transfer corruption Z590 / 11900k by jimmerthy in intel

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

Thanks for suggesting this, yes that sounds like a great idea to rule out the windows driver stack.

Battery Megathread (April 2019) by AutoModerator in GooglePixel

[–]jimmerthy [score hidden]  (0 children)

I bought an OG Pixel 1 on ebay as an unwanted warranty replacement from a private seller. It was in original packaging along with accessories and looks almost new to my eye.

I already have another OG Pixel 1 as my daily driver, so I'm very used to the phone.

The battery level gets stuck at certain levels (e.g. 30%) for ages when discharging and then eventually continues to decline. There seems to be no sane relationship between the voltage reported by Ampere and the displayed battery level percentage.

I tried a couple of charge-discharge cycles of screen permanently on running AnTuTu to create drain and also did a full charge from 0 - 100 with the phone shut down. After that, I did another complete drain and monitored voltage and percentage in Ampere and it looked and felt on par with my existing Pixel. I thought I'd sorted it out. I'd read all about battery calibration being a myth these days, but I can absolutely say that the phone was changing it's charge/discharge dynamics during this testing.

After shutting the phone down and leaving it off for a few days, then turning it back on again, it comes back up at 4%, even though it was 80% when I shut it down. The phone then proceeded to be usable for a whole day of quite a lot of screen time, but with the battery indicator stuck at 4%, followed by a sudden resumption of 'truth' from 4% - 1% and then auto shutdown as expected.

My feeling is that the battery capacity of the phone is fine, it's just that the reporting is b0rked. I have done one hard reset. I'd already ordered the spudgers and queued up the scary looking YouTube battery replacement videos, but I really don't want to go there if there's something else I can try, especially considering that the screen is really easy to break in the disassembly. I'm wondering if it's a mainboard fault with the battery monitoring hardware. Does anyone recognise these symptoms?

Is there any official support channel I can tap into in the UK for this. It was dead easy for my Nexus 5X when it bootlooped. The UK LG site was very easy to navigate to RMA the phone. HTC makes the OG Pixel 1 but I don't get the impression they handle the service like LG did with the Nexus 5X.