Thanks for responding. I have these: crw-rw---- 1 root dialout 166, 0 Oct 8 13:07 /dev/usb/ttyACM0 crw-rw---- 1 root dialout 166, 1 Apr 4 2001 /dev/usb/ttyACM1
acm is loaded. I am getting this: usb.c: USB new device connect, assigned device number 2 usb.c: USB device 2 (vend/prod 0x4c1/0x3021) is not claimed by any active driver. Needless to say seyon is unhappy. This is a Viking modem. Could it be that it's trying to do something weird? Thanks. On Monday 08 October 2001 13:26, you wrote: > Bob, > > If you haven't brought up your USB modem yet, you might try the following: > > type: > > ls -l /dev/usb/ttyACM* > > you should see something like: > > crw-rw---- 1 root dialout 166, 0 Oct 8 13:07 /dev/usb/ttyACM0 > crw-rw---- 1 root dialout 166, 1 Apr 4 2001 /dev/usb/ttyACM1 > > I use Debian, so your group and permissions will most likely be different. > If you don't see any ttyACM* devices, you'll need to "mknod" them (assuming > you aren't using devfs). > > Now as root, load the USB modem handler by typing: > > insmod acm > > If that loads, cycle power or disconnect and reconnect the modem's USB > cable. > > Then type: > > dmesg | tail > > you should see something like: > > usb.c: registered new driver acm > ttyACM0: USB ACM device > usb.c: USB disconnect on device 2 > usb.c: USB new device connect, assigned device number 2 > ttyACM0: USB ACM device > > But, if you see something like: > > usb.c: USB new device connect, assigned device number 2 > usb.c: USB device 2 (vend/prod 0x4c1/0x3021) is not claimed by any active > driver. > > something went wrong. Assuming all went well, you should now be able to > run a serial terminal emulation program using ttyACM0 as your modem device. > For example, if you have seyon, typing: > > seyon -modem /dev/usb/ttyACM0 > > should let you talk to your modem. > > Hope this helps, > > Mark Bigler > [EMAIL PROTECTED] -- Bob Crandell Assured Computing 30004 Carol Ave. Eugene, Ore 97402 [EMAIL PROTECTED] www.assuredcomp.com 541-914-3985
