crwdns2933423:0crwdne2933423:0
crwdns2918538:0crwdne2918538:0

crwdns2934241:0crwdne2934241:0 champagnecharly

crwdns2934249:0crwdne2934249:0:

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?

crwdns2915684:0crwdne2915684:0:

open