Re: [gentoo-user] usb- seriial(minicom) problem

2006-10-08 Thread Iain Buchanan
On Fri, 2006-10-06 at 19:04 +, James wrote: 
 Hello,

Hi James :)

 
 I have (2) different usb-serial converters, both of
  which are listed
 when I build the drivers-usb-serial-converter in  a 
 2.6.17-r8  kernel:

I see this (I have a pegasys based usb-232): 

Oct  9 08:42:46 orpheus usb 3-2: pl2303 converter now attached to ttyUSB0

and you see this:

 usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0

which is strange cause I also see /dev/ttyUSB0...

 pr port /dev/ttyUSB0
 pr port /dev/bus/usb/002
 pr port /dev/bus/usb/002/002

did you actually manually check for the device /dev/ttyUSB0?

apart from that, I'm not sure what could be wrong...
-- 
Iain Buchanan iaindb at netspace dot net dot au

Running Windows on a Pentium is like having a brand new Porsche but only
be able to drive backwards with the handbrake on.
(Unknown source)

-- 
gentoo-user@gentoo.org mailing list



[gentoo-user] usb- seriial(minicom) problem

2006-10-06 Thread James
Hello,

I have (2) different usb-serial converters, both of
 which are listed
when I build the drivers-usb-serial-converter in  a 
2.6.17-r8  kernel:

 USB Serial Converter support 
  USB Generic Serial Driver 
   USB FTDI Single Port Serial Driver (EXPERIMENTAL)
   USB HP4x Calculators support
 USB Xircom / Entregra Single Port Serial Driver

 here I show everything selected in this section

so I build a new kernel
make  make modules_install
and boot off the new kernel.  All looks find from the 
subsequent
dmesg(snipped for brevity)
usbcore: registered new driver usb-storage
input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical
 Mouse] on usb-:00:13.1-3
drivers/usb/serial/usb-serial.c: USB Serial support 
registere  for generic
drivers/usb/serial/usb-serial.c: USB Serial support
 registered for  FTDI USB Serial Device
drivers/usb/serial/ftdi_sio.c: Detected FT232BM
usb 2-1: FTDI USB Serial Device converter now attached to 
ttyUSB0
usbcore: registered new driver ftdi_sio
drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial 
Converters  Driver
drivers/usb/serial/usb-serial.c: USB Serial support registered 
for hp4X
usbcore: registered new driver hp4X
drivers/usb/serial/hp4x.c: HP4x (48/49) Generic Serial driver 
v1.00
drivers/usb/serial/usb-serial.c: USB Serial support registered 
for Keyspan PDA
drivers/usb/serial/usb-serial.c: USB Serial support registered 
for Xircom /
Entregra PGS - (prerenumeration)
usbcore: registered new driver keyspan_pda
drivers/usb/serial/keyspan_pda.c: USB Keyspan PDA Converter 

driver v1.1


lsusb reveals:
Bus 001 Device 001: ID :
Bus 003 Device 003: ID 046d:c01b Logitech, Inc. MX310 
Optical Mouse
Bus 003 Device 002: ID 22b8:2a62 Motorola PCS
Bus 003 Device 001: ID :
Bus 002 Device 003: ID 1645:8003 Entrega [hex]
Bus 002 Device 002: ID 0403:6001 Future Technology Devices 
International, Ltd 8-bit FIFO
Bus 002 Device 001: ID :


So it all looks fine. Next I configure minicom...
I have mincom working on regular 9pin serial ports on multiple
systems. I know my cabling, and 8N1, 9600 baud and no hard/soft
FC work to the serial port on the test (cisco) device.
 So I know that minicom is installed and the 
etc/minicom/minirc.dfl  match with system that work.

So my best guess the problem is the port device driver,
converter device or the port setting in /etc/mincom/minirc.dfl
I've tried all of these with the ftdi device:

pr port /dev/ttyUSB0
pr port /dev/bus/usb/002
pr port /dev/bus/usb/002/002

Any suggestions are most welcome.  
The Entrega device was not plugged in during the reboot
so it does not show up in dmesg. The Entrega device
is the other device I have, but all attempts with it
fail alsoI did notice the device has the name
Entrega printed on it and the kernel uses the name
Entregra, but, I was hoping they're the same?

ideas?

James








-- 
gentoo-user@gentoo.org mailing list