Hi!
I'm having problems with SeaClear II v1.0.0.196.
After setting up the symlinks in ~/.wine/dosdevices pointing
to my gps-device (GlobalSat BU-353 USB) everything works as
expected, but for some reason Wine/SeaClear steals all
available CPU-time. 100% all the time. This problem does
not exist if I start SeaClear with the GPS disconnected,
making me belive there is a problem with Wine's handling of
the "serial" port. What confuses me is that nobody else
seems to have run into this problem (according to google
atleast). Is there some setting or tweak needed?
This behaviour is verified in Wine 1.1.22 on both Kubuntu
9.04 and Vector 6.0 (can't remember the Wine-version here).
Just running SeaClearII from the shell shows me (amongst
some semingly unrelated stuff):
--<snip>--
fixme:comm:set_queue_size insize 4096 outsize 8192 unimplemented stub
--</snip>--
And after figuring out how to get more info (great wiki
btw.) I ran the following line:
==WINEDEBUG="+comm" wine .wine/drive_c/Program\
Files/SeaClear/SeaClear_2.exe
What looks suspicious in the output is a continuous printing
of the following two lines:
--<snip>--
trace:comm:io_control 0x9c IOCTL_SERIAL_WAIT_ON_MASK (nil) 0 0x83d058 4 0x83d060
trace:comm:get_irq_info TIOCGICOUNT err Invalid argument
--</snip>--
And upon exiting the app I get the followin output:
--<snip>--
trace:comm:io_control 0x9c IOCTL_SERIAL_WAIT_ON_MASK (nil) 0 0x83d058 4 0x83d060
trace:comm:io_control 0x9c IOCTL_SERIAL_PURGE 0x32fe48 4 (nil) 0 0x32fddc
trace:comm:io_control 0x9c IOCTL_SERIAL_PURGE 0x32fe50 4 (nil) 0 0x32fde4
trace:comm:io_control 0x9c IOCTL_SERIAL_PURGE 0x32fe44 4 (nil) 0 0x32fdd8
trace:comm:io_control 0x9c IOCTL_SERIAL_PURGE 0x32fe30 4 (nil) 0 0x32fdc4
trace:comm:SetCommMask handle 0x9c, mask 0
trace:comm:io_control 0x9c IOCTL_SERIAL_SET_WAIT_MASK 0x32fe3c 4 (nil) 0
0x32fdd0
trace:comm:io_control 0x9c IOCTL_SERIAL_PURGE 0x32fe3c 4 (nil) 0 0x32fdd0
trace:comm:get_irq_info TIOCGICOUNT err Invalid argument
--</snip>--
ls -la ~/.wine/dosdevices/
lrwxrwxrwx 1 henrik henrik 12 2009-05-16 12:54 com1 -> /dev/ttyUSB0
ls -la /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 0 2009-05-23 14:07 /dev/ttyUSB0
And for reference, this is what the kernel says when
inserting the USB-GPS-receiver:
cat /var/log/kern.log
--<snip>--
usb 2-3: newfull speed USB device using ohci_hcd and address 3
usb 2-3: configuration #1 chosen from 1 choice
pl2303 2-3:1.0: pl2303 converter detected
usb 2-3: pl2303 converter now attached to ttyUSB0
--</snip>--
I'm more than happy to supply more data/logs but maybe there
is an easy fix that I just overlooked..
Thanks in advance..
/H
