At the end of emerging media-gfx/argyllcms-1.3.0 the ebuild states: * If you have a Spyder2 you need to extract the firmware * from the spyder2_setup.exe (ColorVision CD) * and store it as /usr/bin/spyd2PLD.bin This seems wrong. I have a spyder2, and dispcal won't find the firmware file because: blackknight ~ # strace dispcal [...] open("/dev/", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 5 getdents(5, /* 167 entries */, 32768) = 4880 getdents(5, /* 0 entries */, 32768) = 0 close(5) = 0 stat("/root/.local/share/color/spyd2PLD.bin", 0x7fff8c4a8fc0) = -1 ENOENT (No such file or directory) stat("/usr/local/share/color/spyd2PLD.bin", 0x7fff8c4a8fc0) = -1 ENOENT (No such file or directory) stat("/usr/share/color/spyd2PLD.bin", 0x7fff8c4a8fc0) = -1 ENOENT (No such file or directory) write(2, " 1 = 'usb:/bus4/dev2/ (ColorV"..., 77 1 = 'usb:/bus4/dev2/ (ColorVision Spyder2)' !! Disabled - no firmware !! [...] So I guess the firmware should be in one of the paths dispcal searches in. The hint for extracting the firmware also did not work for me. I had to: 1) Download http://support.datacolor.com/index.php?_m=downloads&_a=downloadfile&downloaditemid=42 (Or search for spyder2 in the support DB and lookout for Spyder2 2.3.5 - Win) 2) Install with wine (spyd2en would not find the firmware in the archive) 3) run tbart@blackknight ~ $ spyd2en -v ~/.wine/drive_c/Program\ Files/ColorVision/Spyder2/CVSpyder.dll Size of input file '/home/tbart/.wine/drive_c/Program Files/ColorVision/Spyder2/CVSpyder.dll' is 86016 bytes Located firmware in driver file Firmware is being save to '/home/tbart/.local/share/color/spyd2PLD.bin' About to write binary '/home/tbart/.local/share/color/spyd2PLD.bin' Binary '/home/tbart/.local/share/color/spyd2PLD.bin' sucessfully written Might be worth a note as well. If other users had the same experience I can adapt the ebuild...
I corrected the firmware search path in the ebuild, thanks. For the firmware extraction instructions, I'd suggest you e-mail the author and ask him to add them to the linux installation page mentioned in the ebuild. This would probably be best.
thanks for the update. i contacted Graeme just now.
Seems this is fixed now! --- Date: Wed, 30 Nov 2011 10:34:48 +1100 From: Graeme Gill <graeme@argyllcms.com> Organization: Argyll CMS To: Thomas Bartosik <tbartdev@gmx-topmail.de> Subject: Re: Suggested correction to the documentation Hi, I've fixed up the VIZE code so that the next release will work on the setup.exe that is currently downloadable from the manufacturer. So there is still no need to install it. Graeme Gill.
