In the end, you should get the kext with your modifications. There would be a plenty errors because of old macro used: you could use the unmerged pull request to solve them. The YOUR_DEVICE_PASSTHROUGH_MODE is more complicated, it seems that there is no public info about usb bridge type used there, so I advice to try different values, starting from sat16 and jmicron.Īfter you changed the ist you will need to build the driver.
Here the PID and VID is a product and vendor ids, there are a lot ways to find such from your device, including IORegistryExplorer. What you will need to do to match SATSMART driver to your Samsung T5, is to add its record to ist of the driver in the same format, like: Samsung T5 To keep long story short: matching is a process, when the system decides, what driver is a proper for a new device. However I think the problem starts earlier, the driver is not matched to the T5 device. This is a complicated process with a lot of places for you to shoot in the leg. If it is there, which I would say is less possible, I have a bad news: you will need to debug the driver and try to find, what is going on there during data exchange, why it can't retreive SMART data from the device. I suggest you to diagnose it with IORegistryExplorer: find your T5 device and check, whether there is a fi_dungeon_driver_IOSATDriver in the device tree. This could be a long journey, hold on tight.Īs this SMART reading is based on SATSMART driver, I would say there is something bad with driver to device part.
0 kommentar(er)
