[Openicc] Argyl, Ubuntu, Spyder2, please help

[L]

My system: ubuntu gutsy for amd64, icewm as "desktop", no gnome guis and 
such - I'm new to Ubuntu and not so experienced with Linux, but I've 
written enough script in enough languages to be reasonably comfortable 
with a command line (prefer cli to guis).  I'm trying to get Argyll to 
work my Spyder2. I have nVidia restricted driver and a dual-monitor 
setup, but I've rewritten xorg.conf to comment out all references to a 
dual-monitor setup and the second monitor is turned off.

I installed Argyll (see 1 below.); I successfully imported the Spyder 
firmware (see 2.); I'm not sure if I really have Ubuntu recognizing the 
Spyder "all the way" (see 3. for lsusb and USB Viwer; see 4. for 
/etc/udev/rules.d rule for Argyll).  Alas, Argyll is not working with 
Ubuntu and the Spyder.  Any help, any suggestion of what to try next 
would be so very, very, very appreciated.  

1. I installed argyll V0.70, twice actually.  The "from source" 
installation is at /usr/local/src/argyllcms and the "from binary" 
(patched) is at /usr/local/argyll.

Both installations seem to work just fine.  The command "dispwin -r" 
returns the following:

elle at rn:~$ export PATH=PATH$:/usr/local/src/argyllcms/bin
elle at rn:~$ dispwin -r
Darkening screen
Lightening screen
Restoring screen
Normal beep
Good beep
Bad double beep

elle at rn:~$ export PATH=PATH$:/usr/local/argyll/bin
elle at rn:~$ echo $PATH
PATH$:/usr/local/argyll/bin
elle at rn:~$ dispwin -r
Darkening screen
Lightening screen
Restoring screen
elle at rn:~$

and the screen lightens and darkens appropriately (I don't hear a beep, 
but then again I've never configured my system for sound).  Similarly 
"dispwin" runs and presents various color patches in the center of my 
screen, more patches (white, grey etc) for the source install than for 
the binary install.  


2. I ran spyd2en for each installation, first by pointing spyd2en at the 
CVSpyder.dll in my old windows installation, then by pointing spyd2en at 
the setup.exe file on the installation cd.  Each time spyd2en ended with 
success.  Sample output below:

Input file '/mnt/cdrom/setup/setup.exe' is a VISE archive file
Located driver file 'CVSpyder.dll' at offset 0x17cb0c
Located and decompressed driver file 'CVSpyder.dll' from archive
Located firmware in driver file
Path to executables is assumed to be '/usr/local/argyll/bin/'


When I try to run "dispcal -v -r" what I get is the following:
elle at rn:~$ dispcal -v -r
Setting up the instrument
The instrument can be removed from the screen.
dispcal: Error - dispread failed with 'Instrument Access Failed'


When I try to run "dispcal -v -a" (the "-a" apparently isn't a current 
flag, but the output is informative) what I get is the following:
elle at rn:~$ dispcal -v -a
Calibrate a Display, Version 0.70 (BETA 7)
(. . . a bunch of stuff . . .)
    1 = 'usb:/bus0/dev3 (ColorVision Spyder2)' !! Disabled - no firmware !!
    2 = '/dev/ttyS0'
    3 = '/dev/ttyS1'
    4 = '/dev/ttyS2'
    5 = '/dev/ttyS3'
(. . . a bunch more stuff . . .)


When I run the same command as root:
elle at rn:~$ sudo /usr/local/argyll/bin/dispcal -v -a
Setting up the instrument
Segmentation fault
elle at rn:~$


So I'm guessing that despite the "success" at loading the spyder 2 
firmware, something is still amiss.


3. Is Ubuntu recognizing the Spyder?
elle at rn:~$ lsusb
Bus 002 Device 003: ID 040d:6205 VIA Technologies, Inc.
Bus 002 Device 001: ID 0000:0000  
Bus 001 Device 003: ID 085c:0200 ColorVision, Inc. Monitor Spyder
Bus 001 Device 001: ID 0000:0000  
elle at rn:~$

And when I run "USB Viewer" the "ColorVision Monitor etc" shows up under 
"OHCI Host Controller", but it is in red, which apparently means it's 
there, but not quite all the way.


4. Here's my latest "/etc/udev/rules.d/45-argyll.rules" file:F
SUBSYSTEMS=="usb", SYSFS{idVendor}=="085c", SYSFS{idProduct}=="0200", 
MODE="664", GROUP="plugdev"

I've tried many suggested variations of the above udev rules.d, to no avail.

I've run out of bright ideas about what to try next.  I've searched the 
Argyll mailing list and read a lot of the online documentation.  I've 
searched the internet and the Ubuntu forums.  I've poured over 
suggestions about how to write udev rules.  I suppose I could reinstall 
windows (the Spyder was working fine under windows) and dual-boot, just 
to be able to generate a monitor profile.   Any suggestions would be so 
gratefully received.

Elle
I'm sorry I haven't become a member before sending this email.  I tried 
- I'm now getting all of the list's submissions, but apparently there's 
another step before I can send an email myself.