One thing I thought I might try is the Generic Serial Driver. Do I have
any chance of getting this to work with the F5U109? I don't need any flow
control - I'm just sending a small string to a serial device.
I have one question, though: How can I determine the device's vendor and
product ID?
--
To enable the generic driver to recognize your device, build the driver
as a module and load it by the following invocation:
insmod usb-serial vendor=0x#### product=0x####
where the #### is replaced with the hex representation of your device's
vendor id and product id.
--
Also, a side question for those of you who do have a working F5U109: When
your adapter sends or receives data, do the Tx and Rx lights blink?
Thanks again for the help.
-Chris
On Tue, 28 May 2002, Chris Kotrla wrote:
>
>
> On Thu, 23 May 2002, Greg KH wrote:
>
> > On Thu, May 23, 2002 at 05:19:08PM -0500, Chris Kotrla wrote:
> > > Hello,
> > >
> > > I'm trying to install the Belkin F5U109 USB-serial adapter in my debian
> > > install running 2.4.18. Searching google for help yielded some mails from
> > > this list, but I didn't find anything conclusive.
> > >
> > > Evidently the belkin module is not the right one to use, but rather the
> > > mct_u232 is the module that has support for the belkin F5U109. I install
> > > it and usbserial, and everything looks good when I plug it in:
> > >
> > > ---
> > > May 23 16:54:47 cottonmouth kernel: hub.c: USB new device connect on
> > > bus1/2, assigned device number 3
> > > May 23 16:54:47 cottonmouth kernel: usbserial.c: Magic Control Technology
> > > USB-RS232 converter detected
> > > May 23 16:54:47 cottonmouth kernel: usbserial.c: Magic Control Technology
> > > USB-RS232 converter now attached to ttyUSB0 (or usb/tts/0 for devfs)
> > > ---
> > >
> > > Note that it's not actually a Magic Control Technology USB-RS232
> > > converter; its a Belkin. I'm guessing Magic Control Tech OEMed the
> > > product?
> >
> > Belkin OEMed the product.
> >
> > > Anyway, the device has three lights on it: LINK, TX, and RX. The link
> > > light is always on when it's plugged in. When I echo 'some stuff' >
> > > /dev/ttyUSB0, the LINK light blinks, but nothing else happens. On a
> > > windows box, when I send stuff, the TX light does blink (as it should).
> >
> > Does the data go through properly?
>
> No, it never makes it. I've tried a couple of different serial devices,
> but not had any luck.
>
>
> >
> > > The device I'm trying to control only works at 2400 baud, so I set the
> > > baudrate: stty 2400 < /dev/ttyUSB0. The device doesn't show any sign of
> > > being sent anything, though.
> >
> > stty doesn't send data, what do you think should be sent?
> >
>
> Right - I mean that later, when I try to send something, it never makes
> it.
>
>
> > > Anyone know what I'm doing wrong here? As far as I can tell, the mct_u232
> > > should work fine. I checked the source code and saw a comment indicating
> > > that it was updated to support the Belkin F5u109.
> > >
> > > Any help would be appreciated!
> >
> > Have you tried using a serial based program to talk to the device,
> > instead of just "echo"? I've found that echo doesn't work very well for
> > serial devices, but programs like minicom or kermit work just fine.
> > Have you tried them?
>
> I tried minicom, and I get similar results. When I try sending something
> to the adapter, the "link" light will blink with each key press. One
> interesting thing I've noticed, though, is that after I press enough keys,
> the usb-serial adapter seems to completely freeze up and doesn't accept
> any more input. Minicom also seems dead at this point. I tried killing
> minicom and reopening it, but it the serial-usb adapter doesn't even blink
> any more.
>
> I'm a relative newbie to linux, so it's entirely possible that I'm missing
> something really simply here - but I know I have the right driver, and I
> know it's recognizing and at least somewhat communicating with the
> adapter. Does it make any difference if I compile the mct_u232 into the
> kernel or load it as a module? (I've tried both).
>
> I've even patched the kernel to the 2.4.19-pre8 but it doesn't seem to
> have made any difference.
>
> I know the adapter works, 'cuz I've used it on a windows box, and at the
> same time, I'm having this problem with two different linux boxes - that's
> why I'm guessing there must be some simple thing I'm missing.
>
> Any clues?
>
> Thanks again for everyone's help.
>
> -Chris
>
>
>
> >
> > thanks,
> >
> > greg k-h
> >
>
>
> _______________________________________________________________
>
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
>
> _______________________________________________
> [EMAIL PROTECTED]
> To unsubscribe, use the last form field at:
> https://lists.sourceforge.net/lists/listinfo/linux-usb-users
>
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
