 |
Hi folks, only two or three days ago I was patting myself on the back for bringing my Lenovo T470s onto Ventura, with pretty much 100% functionality. Everything, HDMI included! A tiny bit of patching was required to modify the config file to output to a display. Everything based around https://github.com/Lochneska/t470s-hackintosh The main specs of the computer: Lenovo T470s Intel Core i5-6300U 2,4 GHz (Dual-Core) 256 GB NVME 20 GB RAM Intel HD Graphics 620 Thunderbolt/USB-C Port (and 3 USB-A ports), SD card reader All running Ventura 13.7.2 I was just a little underwhelmed with the performance of Windows 10 Pro as a VM in VMWare (and yes, I know VMs are going to be a little slow!) despite the upgrade to 20GB, so I instead decided to use Win2USB to run it from a USB stick. I had earlier tried to do things as a dual boot (all on one local hard drive) but the config file appears not to be set up for such a scenario. All well and good. Ran software updates in Windows until none remained. When I booted back into Mac OS and connected my iTec Universal Dockingstation (USB-C) nothing seemed to be going on when I moved my mouse around the desk (it works via a dongle attached to the dockingstation), same for the keyboard and same for JABRA USB-A headset. Nor were USB-C hard drives working. Tried the usual unplugging and plugging back in etc. This was never a problem before Win2USB entered the frame!! I could connected everything at will, no problems. All USB-A ports and the SD card reader are all just fine. Win2USB was set up on a USB-A type of hard drive and Thunderbolt had no direct involvement here. I have verified that the Dockingstation is OK with other computers. These accessories and storage media now only work when they are connected at boot time. Any subsequent disconnects and re-connects do nothing. I have cleared the NVRAM and have even gone as far as resetting BIOS to factory default and wiping the hard drive and re-installing everything from scratch. Still no joy. The status quo remains unchanged. The fact that it works OK when connected at boot time suggests that the 'mapping' is OK. Have I made some kind of long-term change (deep in the hardware) that has pretty much 50% killed Thunderbolt 3.1 functionality, all thanks to Win2USB? Possibly having to restart the Mac to read anything over Thunderbolt is a bit of a head-wrecker, but now I am glad I have at all (albeit somewhat limited). Relevant info from system report. With device (USB stick) connected at boot time - all looks good, can see it in Finder etc. Whatever is wrong here seems to be pretty obscure. Thanks for any help that you can lend. WL. [link] [comments] |
Post a Comment