Hi Nicolaslafo,
I'm Rodrigo and I will help you.
The adapter needs to be connected to a USB 3.0 port to work correctly, if it is connected to a USB 2.0 port it will work on a maximum resolution of 800x600.
If it is already connected to a USB 3.0 port, try another available port
Answer from Rodrigo Queiroz on learn.microsoft.comHi Nicolaslafo,
I'm Rodrigo and I will help you.
The adapter needs to be connected to a USB 3.0 port to work correctly, if it is connected to a USB 2.0 port it will work on a maximum resolution of 800x600.
If it is already connected to a USB 3.0 port, try another available port
With a little research, I found that it is a common issue with this adapter, here is a possible fix that I've found:
Go to the Fresco Logic driver installation folder (default path: C:\Program Files\Fresco Logic\Fresco Logic USB Display Driver\FL2000\x64) and open fresco_monitor_tool.exe . Set the resolution and refresh rate but slowly increase from 800x600 until you find a suitable working resolution. Set the refresh rate to 60HZ, and if needed, reduce it. Select Set EDID to apply the changes, Clear EDID will clear the changes you did.
fresco logic fl2000 - DisplayLink Forum
How to properly install USB display driver for Fresco Logic FL2000DX on Ubuntu? - Unix & Linux Stack Exchange
Problem with Fresco Logic IDDCX Adapter (hdmi to usb) Screen Flashing black
Fresco Logic FL2000 USB3.0 to HDMI adapter problem
Videos
Telling the full story so all the keywords will be included in my response for future searchability:
I've been looking everywhere for a driver or chipset info for the unbranded "Mini HD USB 3.0 HDMI Adapter" for years. I finally dug though enough duck duck go results to find a page that claims it uses the Fresco logic USB display driver, which brought me here.
I was able to get the driver to work using Linux Mint 18.2 "Sonya" with linux-headers-4.13.0-45-generic, but the instructions on git hub were not perfect.
- Clone the repository
git clone https://github.com/FrescoLogic/FL2000.git(If you don't have git installed you can install it withsudo apt install git) - Navigate to src:
cd FL2000/src/ - Run
make(contrary to the instructions, you don't need to editKERNEL_PATHas the bug was fixed) - Insert the module
sudo insmod fl2000.ko - Change to sample
cd ../sample/ - Run
make(I got an error here, but was able to test the driver and see an image despite the error) - Run
sudo ./fltest 0
This crashed the first time I ran it but worked when I re-ran it a second time. Running it a 3rd time, it hangs my system.
Rebooting with the device plugged into the USB port seems to help. It will work at first launch. However, during shutdown my system is unable to disconnect from it's built in RAMDrive and will hang, ctrl-alt-del will move it a few steps further, but then it hangs again forcing me to do a hard shutdown.
I'm not sure if fixing the error when running make in the sample directory make: /opt/hi3798/arm-hisiv200-linux/bin/arm-hisiv200-linux-gnueabi-gcc: Command not found would make this any more stable.
I googled and came across this thread saying I "need to add head file <sys/ioctl.h>" -- I didn't know how to do that so I followed the recommendation in this thread mentioning I should install some gcc packages:
sudo apt-get install gcc-arm-none-eabi gcc-arm-linux-gnueabi
After installing, make progressed further, but I am now getting a make: /opt/hi3798/arm-hisiv200-linux/bin/arm-hisiv20/opt/hi3798/arm-hisiv200-linux/bin/arm-hisiv200-linux-gnueabi-gcc: Command not found error.
Installing ia32-libs hasn't helped.
Just in case someone is still looking, it seems there is a clean-sheet re-implementation of the driver, by klogg from opensource community.
Hi Vijay,
Thank you for your response.
Unluckily, none of these points changed the black screen... I tried point 1 and 2b, both didn't change anything. For 2a, I couldn't click the rollback option.
Maybe this could help: In the device manager, when I expand the monitors, the non-working monitor is marked as Non-PnP-Monitor. Unluckily, I have no idea what this could mean :)
Thank you very much.
Hi ASi6,
I am Vijay, an Independent Advisor. I am here to work with you on this problem.
Please try these options one by one and check after each option.
- Use the Hardware & Devices Troubleshooter
Type Troubleshoot in Windows Start Search box > Click Troubleshoot > Scroll down & Click Hardware & Devices > Click Run the Troubleshooter & follow on-screen directions > Restart the computer after troubleshooting is completed
- Take actions related to Display Driver
Windows Key+X > Click Device Manager > Expand Display Adapter > Right click on entry below >
A. Rollback the Driver
Click Properties > Go to Driver tab > If there is rollback option, click it
B. Update driver from manufacturer's website
Go to the website of the driver's manufacturer or computer's manufacturer > See if some driver is released for your model and OS > If yes, download that > In previous option, click Uninstall > Install the downloaded driver > Restart your computer
Do let me know if you require any further help on this. Will be glad to help you.
I purchased the Oculus recommended Fresco Logic USB expansion card and installed it into my PC. It's not supposed to require any external drivers with the included Windows 10 drivers being sufficient. Oculus Home however is complaining with "USB driver update recommended".
I've searched and cannot find any drivers to update to. Is anybody else getting this warning?
You can get the Fresco Logic drivers here:
https://support.zoho.com/portal/frescologic/home (USB 3.0 Host Driver (FL1000, FL1009, FL1100) v3.6.8.0)
But beware, I have had the best experience with the windows 10 drivers. I got two scenarios:
-
Installed an older fresco logic driver from the Inateck website -> Got bluescreens after reboot
-
Installed the latest driver from fresco logic website (the one from the link) -> Worked flawlessly at first, but made my rift shut off for a few seconds now and then.
Went back to windows 10 drivers: Everything worked again as expected.
Don't do it. The new drivers didn't work right with my CV1 and I had to roll them back.