https://bugzilla.novell.com/show_bug.cgi?id=432420 Summary: 51-gpsd.rules breaks most (all?) non-gps usb-serial devices (incl. gpsbabel for gps devices!) Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: koenig@linux.de QAContact: qa@suse.de Found By: --- your rules in /etc/udev/rules.d/51-gpsd.rules to start gpsd for many usb serial devices breaks many non-gps devices using the same usb chips/ids and even breaks manual gps usages like using gpsbabel to read out data from my WinTec WBT201 gps logger. details: I have a regular usb-serial converter/cable Bus 004 Device 008: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port for which in 11.0 gpsd gets started. gpsd intercepts data, changes the baud rate etc. while "looking" for a gps device, so e.g. while running minicom suddenly the baudrate changes or data gets lost. bad! same is true for other USB gadgets which use those usb-serial chips too. I finally noticed this automatic gpsd startup now for a demo kit for acceleration sensors from VTI (www.vti.fi). the VTI demo it: Bus 004 Device 009: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC the Wintec WNT-201 Bus 004 Device 010: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x Composite Device all those USB ids are for very generic usb-serial adapters which are used in _many_ devices, not just some GPS receivers -- and even for GPS it's questionable to start gpsd without request or possibility to configure/disable: now I understand my problems with my WinTec WBT-201 since I updated to 11.0: I use this gps logger regularly. it works "offline" and I only wand to read/save the logged data using gpsbabel (using a wintec proprietary protocol). since 11.0 I have severe trouble reading out the logged data using a usb connection with gpsbabel: very often I get checksum errors for the treansfer or even connection timeouts which aborts the whole transfer and I have to start again (for large data sets it takes _many_ retries of multiple minutes each:-( so even for some GPS devices/usages your automagic start of gpsd breaks things. *PLEASE* disable these udev rules!!! some more comments about deficiencies of current implementation: - gpsd runs as nobody, so the regular console user can't kill it if needed - there is no way to disable startup of gpsd in /lib/udev/gpsd.sh at least you should have added some settings to (a) select a specific usb id or (b) completely disable startup -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.