Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
modinfo extracts information from the Linux Kernel modules given on the command line. If the module name is not a filename, then the
/lib/modules/version directory is searched, as is also done by modprobe(8) when loading kernel modules.
modinfo by default lists each attribute of the module in form fieldname : value, for easy reading. The filename is listed the same way (although it's
not really an attribute).
This version of modinfo can understand modules of any Linux Kernel architecture.
Print the modinfo version.
Only print this field value, one per line. This is most useful for scripts. Field names are case-insensitive. Common fields (which may not be in
every module) include author, description, license, parm, depends, and alias. There are often multiple parm, alias and depends fields. The special
field filename lists the filename of the module.
Provide information about a kernel other than the running one. This is particularly useful for distributions needing to extract information from a
newly installed (but not yet running) set of kernel modules. For example, you wish to find which firmware files are needed by various modules in a
new kernel for which you must make an initrd/initramfs image prior to booting.
Use the ASCII zero character to separate field values, instead of a new line. This is useful for scripts, since a new line can theoretically appear
inside a field.
-a -d -l -p -n
These are shortcuts for author, description, license. parm and filename respectively, to ease the transition from the old modutils modinfo.
Please look at the following FYIs' to help you with future posts;
FYI: Netiquette is a set of social conventions that facilitate interaction over networks, ranging from Usenet and mailing lists to blogs and forums.
FYI: I suggest that you look at 'How to Ask Questions the Smart Way' so in the future your queries provide information that will aid us in diagnosis of the problem or query.
"Knowledge is of two kinds. We Know a subject ourselves, or we know where we can find information upon it."- Samuel Johnson
“A tool is but the extension of a man's hand and a machine is but a complex tool. He that invents a machine augments the power of man and the well being of mankind.” - Henry Ward Beecher
The two most common USB protocols are USB storage and MTP typically used by MP3 players and cameras. However there are many devices that use proprietary protocols and without any way to access them natively from within linux. I've never tried but
but you would need to reverse engineer the watches communication protocol. There are many articles that can be found by searching like the following. Using libusb to write the driver and create a fuse file system so the watch can be mounted like a USB storage device.
michaelk: I tried installing the Timex device agent through Wine and everything worked ... except recognizing the watch, that is - I was checking out the links you provided and it seems that the only way of possibly making it work would be to snatch the files from the Win registry?
Note that even in Windows, Timex cannot be used as a Mass storage device (in contrast to Garmin), it just downloads files through the Device agent software
Here are outputs from the lsusb, dmesg, syslog and others:
Bus 006 Device 004: ID 0cc2:d702 Timex Corp.
Jan 27 19:26:20 xxxx kernel: [22674.536112] usb 6-1: new full-speed USB device number 4 using uhci_hcd
Jan 27 19:26:20 xxxx kernel: [22674.719829] usb 6-1: New USB device found, idVendor=0cc2, idProduct=d702
Jan 27 19:26:20 xxxx kernel: [22674.719837] usb 6-1: New USB device strings: Mfr=2, Product=3, SerialNumber=0
Jan 27 19:26:20 xxxx kernel: [22674.719843] usb 6-1: Product: Timex Ironman Run Trainer GPS Watch
Jan 27 19:26:20 xxxx kernel: [22674.719847] usb 6-1: Manufacturer: Timex Corporation
Jan 27 19:26:20 xxxx mtp-probe: checking bus 6, device 4: "/sys/devices/pci0000:00/0000:00:1d.0/usb6/6-1"
Jan 27 19:26:20 xxxx mtp-probe: bus: 6, device: 4 was not an MTP device
Jan 27 19:26:20 xxxx kernel: [22674.731000] hid-generic 0003:0CC2702.0004: hiddev0,hidraw0: USB HID v1.11 Device [Timex Corporation Timex Ironman Run Trainer GPS Watch] on usb-0000:00:1d.0-1/input0
fdisk -l; blkid -o list -c /dev/null:
returns nothing which would pertain to the watch.
[ 1.751212] usb 6-1: Product: Timex Ironman Run Trainer GPS Watch
[ 1.751216] usb 6-1: Manufacturer: Timex Corporation
[ 2.303403] hid-generic 0003:0CC2702.0001: hiddev0,hidraw0: USB HID v1.11 Device [Timex Corporation Timex Ironman Run Trainer GPS Watch] on usb-0000:00:1d.0-1/input0
[22529.651141] usb 6-1: Product: Timex Ironman Run Trainer GPS Watch
[22529.651146] usb 6-1: Manufacturer: Timex Corporation
[22529.662286] hid-generic 0003:0CC2702.0003: hiddev0,hidraw0: USB HID v1.11 Device [Timex Corporation Timex Ironman Run Trainer GPS Watch] on usb-0000:00:1d.0-1/input0
[22674.719843] usb 6-1: Product: Timex Ironman Run Trainer GPS Watch
[22674.719847] usb 6-1: Manufacturer: Timex Corporation
[22674.731000] hid-generic 0003:0CC2702.0004: hiddev0,hidraw0: USB HID v1.11 Device [Timex Corporation Timex Ironman Run Trainer GPS Watch] on usb-0000:00:1d.0-1/input0
I have also checked the Timex/TrainingPeaks folder on my windows partition. In the TimexDrivers folder there are files: DPInstx64.exe DPInstx86.exe TimeCycleTrainer.inf TimexGlobalTrainer.inf
I will try using a QEMU / Vbox VM with React OS
I am unfortunately not quite good at writing drivers (I rather suck massively, lol) so that I am going to use this approach.
but I will keep an eye on this thread, if somebody knows how to make the stuff run using the Wind DLLs it would be awesome.
My Timex is in fact the only reason that I keep a version of Win7 on my hard drive.
It seems that we Linux people aren't too much into sports
(I am ultra-runner, BTW).
We will have to work on that. First stop getting my Garmin running... and else... who cares, we have been keeping track of our times using chronometers for decades.