I added a post previous to this with some ideas on procceeding prior to full install of Ubuntu. Unfortunately it was marked as spam. Basically i sugested trying to dl drivers for devices that existed pre W8. Also to look at firmware drivers for the Sony vaio Duo 11 I kept on doing a little research and came across: http://answers.microsoft.com/en-us/surface/forum/surfpro3-surfupdate/failed-installation-of-1118-firmware-update/3a35b526-276a-4d11-82a8-87d818f79767 Seems like code 10 and IRQ issues is a frequent occurence with the surface. Currys stating 5 returns on the same day in 1 local store!!
I'd also look at the drivers & firmware from other hardware. I think we can safely asume 1) >=2 sets of firmware installed on the Ntrig. Base firmware we can see on the chip as V1.1 v 1 +++ 2) The installed underlying firmware matches 'a' basic/user updatable firmware 3) That the factory didnt put these in production for the !&&* of it. And as such there may be a windows device/ manufacturer that has the correct user installeable firmware/ drivers. Either for W7 or W8 or W8.1 To me trying ubuntu would be for investigative purposes only. I think it may be worth while trying to find other devices that use the Ntrigg duo sence. The list can easily be obtained by looking at the available drivers/firmware on the Ntrigg website. I would start with drivers for machines that were pre W8. I also found this list of drivers whilst looking for drivers for the Sony Vaio Duo 11 http://www.driversdownloader.com/drivers-other/n-trig%20innovative%20technologies/n-trig%20duosense%20multitouch%20hid%20dev... Good luck.
Well at least you can get one up and running -assuming the 'original' screen was a V1) as the v1 screen is also widely available. From what I read other trials gave no response other than code 10 or 14. I personally haven't tried as yet as am too busy with other things. Before looking at other OS unless it is to make a log of effect on firmware on device ids e.g from ubuntu dmesg, then I would go down the route of trialing drivers for other machines that use the chip. The firmware installed and the component ids must be set that way for a machine.. mustnt they?
Hi, :).. sorry just anxious to read the results. I would contact MS before thinking of returning it. Remember according to Ntrig MS and their service agents HAVE the firmware tool (presumably software) and can update the firmware. Given you were fed poor advice by MS rep, maybe you could speak to somebody a little more senior in the team and see if they can help. at least you have 'some' leverage. The exact responce from Ntrigg was: We understand your request, however, the installation process of the SW & FW on the DSP-4196 can only be done with dedicated tools. These tools are only available to Microsoft and their authorized distributers/repair labs. We regret not being able to assist more on this matter.
Have either of you tried with Linux Ubuntu? If its IDs and they are mismatched which from the result of device manager is what it looks like it would be interesting to see hwo other drivers/ os handle. Obviously with just running the OS from CD or usb. "sudo lsusb -v" "sudo dmesg | grep ntrig" Should give details of device IDs that could then be compared to a 1.1
I asked Ntrig how one could flash the chip. They said MS and service repairers have the tool (presumably software) to do so. I wonder what they would charge for the same.
Ok. So unless I am mistaken, it has found drives and installed correctly. All be it not functioning. Interesting! it would seem similar to discussed here: https://bugs.launchpad.net/ubuntu/+sourc... It would be interesting to see the results of the following 2 commands from within a live run (CD) of Ubuntu "sudo lsusb -v" "sudo dmesg | grep ntrig" from both a working and non working surface. interesting that the questionable advice (Shawn) came from MS rep.