Driver Cam For Asus 52c Fixed
LINK ->>->>->> https://bltlly.com/2t7MYw
This issue happens for a lot of users, especially with Windows 7. There is no clear root cause for the error, but some users began seeing it after installing a specific update, and the update was different, meaning there are a few of them that might have caused the issue. It basically indicates a driver failure, and Microsoft would recommend either running the troubleshooter or updating the drivers manually.
hmmm.. getting confused by this issue. It seems to be (somehow) device tree related. When I play around with asus miniarm device tree (which solved the camera support differently) the board boots with the activated drivers.
too late.. the image is away (running out of SD-Cards so I've to erase them from time to time).. dmesg showed that it fails to touch it and multiple errors with the isp10 driver (that's the one Asus uses for camera support, according to the RK config it's ok to have both activated)...
I've hit the same wall you have, I'm getting a kernel oops as the first thing that happens, tied to the ISP1 driver. Nothing is particularly different about the device tree between tinker and firefly, and as you pointed out, someone claimed to have gotten it working on firefly... Tomorrow I will investigate any changes that were made to the other camera drivers that may not have been made to the rpi cameras...
 of note, it happens on both cameras, same fault, so it is either a common error to the 2 drivers, or it is the isp1 driver itself. This is of particular interest as the same configuration is required for the rk3399.
Dumb question: Has anybody tried to use the old driver (CONFIG_VIDEO_RK_CIF_ISP10) as a workaround, until the new one works? @TonyMac32 said in some other thread that it requires more tweaking to work, so I'm guessing it won't work "out-of-the-box" just enabling the kernel config.
2. This driver is for below PID code: HardwareID=USB\Vid_064e&Pid_a111&MI_00 HardwareID2=USB\Vid_064e&Pid_f111&MI_00 HardwareID3=USB\Vid_064e&Pid_f116&MI_00 HardwareID4=USB\Vid_064e&Pid_a116&MI_00 HardwareID5=USB\Vid_064e&Pid_f115&MI_00 HardwareID6=USB\Vid_064e&Pid_a115&MI_00 HardwareID7=USB\Vid_064e&Pid_a122&MI_00 HardwareID8=USB\Vid_064e&Pid_a124&MI_00 HardwareID9=USB\Vid_064e&Pid_a136&MI_00
Problem is I originally tried downloading the chipset drivers from the mobo website and it partially installed, but keep running into error 1603. Will trying to install the chipset drivers from the AMD website (possibly a different version) mess with the partially installed drivers from the mobo website? I'm a complete noob here. 2b1af7f3a8