1 |
Hello, |
2 |
|
3 |
I have (2) different usb->serial converters, both of |
4 |
which are listed |
5 |
when I build the drivers->usb->serial-converter in a |
6 |
2.6.17-r8 kernel: |
7 |
|
8 |
USB Serial Converter support |
9 |
USB Generic Serial Driver |
10 |
USB FTDI Single Port Serial Driver (EXPERIMENTAL) |
11 |
USB HP4x Calculators support |
12 |
USB Xircom / Entregra Single Port Serial Driver |
13 |
|
14 |
here I show everything selected in this section> |
15 |
|
16 |
so I build a new kernel |
17 |
make && make modules_install |
18 |
and boot off the new kernel. All looks find from the |
19 |
subsequent |
20 |
dmesg(snipped for brevity) |
21 |
usbcore: registered new driver usb-storage |
22 |
input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical |
23 |
Mouse] on usb-0000:00:13.1-3 |
24 |
drivers/usb/serial/usb-serial.c: USB Serial support |
25 |
registere for generic |
26 |
drivers/usb/serial/usb-serial.c: USB Serial support |
27 |
registered for FTDI USB Serial Device |
28 |
drivers/usb/serial/ftdi_sio.c: Detected FT232BM |
29 |
usb 2-1: FTDI USB Serial Device converter now attached to |
30 |
ttyUSB0 |
31 |
usbcore: registered new driver ftdi_sio |
32 |
drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial |
33 |
Converters Driver |
34 |
drivers/usb/serial/usb-serial.c: USB Serial support registered |
35 |
for hp4X |
36 |
usbcore: registered new driver hp4X |
37 |
drivers/usb/serial/hp4x.c: HP4x (48/49) Generic Serial driver |
38 |
v1.00 |
39 |
drivers/usb/serial/usb-serial.c: USB Serial support registered |
40 |
for Keyspan PDA |
41 |
drivers/usb/serial/usb-serial.c: USB Serial support registered |
42 |
for Xircom / |
43 |
Entregra PGS - (prerenumeration) |
44 |
usbcore: registered new driver keyspan_pda |
45 |
drivers/usb/serial/keyspan_pda.c: USB Keyspan PDA Converter |
46 |
|
47 |
driver v1.1 |
48 |
|
49 |
|
50 |
lsusb reveals: |
51 |
Bus 001 Device 001: ID 0000:0000 |
52 |
Bus 003 Device 003: ID 046d:c01b Logitech, Inc. MX310 |
53 |
Optical Mouse |
54 |
Bus 003 Device 002: ID 22b8:2a62 Motorola PCS |
55 |
Bus 003 Device 001: ID 0000:0000 |
56 |
Bus 002 Device 003: ID 1645:8003 Entrega [hex] |
57 |
Bus 002 Device 002: ID 0403:6001 Future Technology Devices |
58 |
International, Ltd 8-bit FIFO |
59 |
Bus 002 Device 001: ID 0000:0000 |
60 |
|
61 |
|
62 |
So it all looks fine. Next I configure minicom... |
63 |
I have mincom working on regular 9pin serial ports on multiple |
64 |
systems. I know my cabling, and 8N1, 9600 baud and no hard/soft |
65 |
FC work to the serial port on the test (cisco) device. |
66 |
So I know that minicom is installed and the |
67 |
etc/minicom/minirc.dfl match with system that work. |
68 |
|
69 |
So my best guess the problem is the port device driver, |
70 |
converter device or the port setting in /etc/mincom/minirc.dfl |
71 |
I've tried all of these with the ftdi device: |
72 |
|
73 |
pr port /dev/ttyUSB0 |
74 |
pr port /dev/bus/usb/002 |
75 |
pr port /dev/bus/usb/002/002 |
76 |
|
77 |
Any suggestions are most welcome. |
78 |
The Entrega device was not plugged in during the reboot |
79 |
so it does not show up in dmesg. The Entrega device |
80 |
is the other device I have, but all attempts with it |
81 |
fail also....I did notice the device has the name |
82 |
Entrega printed on it and the kernel uses the name |
83 |
Entregra, but, I was hoping they're the same? |
84 |
|
85 |
ideas? |
86 |
|
87 |
James |
88 |
|
89 |
|
90 |
|
91 |
|
92 |
|
93 |
|
94 |
|
95 |
|
96 |
-- |
97 |
gentoo-user@g.o mailing list |