![](/uploads/1/2/5/3/125379862/347471311.jpg)
Could Not Grab Image Select Timeout Resource Temporarily Unavailable. December 20, 2017. Could Not Grab Image Select Timeout Resource Temporarily Unavailable - DOWNLOAD (Mirror #1) Read More. No Cd Crack Command And Conquer The First Decade. December 19, 2017. No Cd Crack Command And Conquer The First Decade - DOWNLOAD. Could not grab image (select timeout): Resource Temporarily Unavailable. Using it as a VirtualBox webcam device is not a solution as I can't.
I have a server machine hosting a Linux VM using VMWare vSphere 6.0. I am trying to get a webcam to work with it. However, I've been having two main issues:
- The frame rate is extremely low (0.1fps - 1.0fps).
- The output image has several glitches (as seen in the examples below).
I tried to install multiple Linux distributions (i.e. CentOS, Ubuntu 14.04 and 16.04, Mint 18.1), and the results are the same. I also tried with two different webcams: Microsoft LifeCam Cinema HD and a generic one (Sunplus Technology). Both cameras work fine on a physical machine running Mint and Ubuntu.
However, both cameras also work just fine on a Windows 10 running on a Virtual Machine at the same server.
To give some technical details, the following message gets printed very frequently when I run
guvcview
on Linux:V4L2_CORE: Could not grab image (select timeout): Resource temporary unavailable.
I also captured 2 images using 'guvcview' to show how the image quality is. One of them was using MJPG:
and the other one with RGB3:
The remaining 'camera output' options had poor quality results as well. Additionally, as you can see at the top bar, the frame rate is very low.
It is important to note that I also tried to capture the frame using multiple methods besides 'guvcview', such as 'streamer', 'webcam' and OpenCV.
Would anyone know how to solve this problem? Thank you!
I also posted this question on superuser: http://superuser.com/questions/1162697/strange-issues-with-webcam-linux-vmware
Looking at the second output, we see a familiar culprit. As @boltgolt said in a post above:
00000032-0002-0010-8000-00aa00389b71
is the new Microsoft 8-bit IR format, supported in Linux kernels starting from 4.17.So it looks like you need to update your kernel. If you are unfamiliar you should look up how to do this and the risks behind doing this incorrectly before you start, I am not responsible for you not being able to boot back into your install ?
![(select (select](/uploads/1/2/5/3/125379862/327112365.png)
That being said, it's not too difficult, below are the instructions as I recall them (however as I said, look this up before you start as some things may have changed as I haven't used Ubuntu in a while).
The list of Ubuntu Kernels can be found here: https://kernel.ubuntu.com/~kernel-ppa/mainline/. You may as well go for the latest stable version (without an
-rcX
at the end of the name), which at the time of writing is: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.2/.Then you will want to download 3 files for your architecture,
linux-headers-...generic...
, linux-image-...generic...
and linux-modules-...generic...
.After that you should install them with
sudo dpkg -i <filename>.deb
. Finally you will need to update grub so it knows about the new kernel version with sudo update-grub
.After it's installed the output of
uname -r
should change to the new kernel version, and you should still be able to access the old kernel version under the advanced boot menu items in grub when you boot up.![](/uploads/1/2/5/3/125379862/347471311.jpg)