During testing TS7000 device we tried to install USB to serial
adapter in TS-Linux OS. (adapter has 8 serial ports and uses FTDI
FT2232C chipsets). The istallation process included manual "insmod"
commands for proper kernel modules and was successful. But when we
tried to transmit some data into port with "echo" command, after
several attempts we bumped into kernel panic:
*****************************************************************
BusyBox v1.00-rc2 (2004.08.05-21:44+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.
$ insmod usbcore
Using /lib/modules/2.4.26-ts11/kernel/drivers/usb/usbcore.o
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
$ insmod pcipool
Using /lib/modules/2.4.26-ts11/kernel/arch/arm/common/pcipool.o
$ insmod usb-ohci
Using /lib/modules/2.4.26-ts11/kernel/drivers/usb/host/usb-ohci.o
$ insmod usb-ohci-ep93xx
Using /lib/modules/2.4.26-ts11/kernel/drivers/usb/host/usb-ohci-
ep93xx.o
usb-ohci.c: USB OHCI at membase 0xe0020000, IRQ 56
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 3 ports detected
$ hub.c: new USB device not_pci-3, assigned address 2
hub.c: USB hub found
hub.c: 5 ports detected
hub.c: new USB device not_pci-3.1, assigned address 3
usb.c: USB device 3 (vend/prod 0x403/0x6010) is not claimed by any
active driver.
hub.c: new USB device not_pci-3.2, assigned address 4
usb.c: USB device 4 (vend/prod 0x403/0x6010) is not claimed by any
active driver.
hub.c: new USB device not_pci-3.3, assigned address 5
usb.c: USB device 5 (vend/prod 0x403/0x6010) is not claimed by any
active driver.
hub.c: new USB device not_pci-3.4, assigned address 6
usb.c: USB device 6 (vend/prod 0x403/0x6010) is not claimed by any
active driver.
$
$ insmod usbserial vendor=0x403 product=0x6010
Using /lib/modules/2.4.26-ts11/kernel/drivers/usb/serial/usbserial.o
usb.c: registered new driver serial
usbserial.c: USB Serial support registered for Generic
usbserial.c: Generic converter detected
usbserial.c: Generic converter now attached to ttyUSB0 (or usb/tts/0
for devfs)
usbserial.c: Generic converter detected
usbserial.c: Generic converter now attached to ttyUSB1 (or usb/tts/1
for devfs)
usbserial.c: Generic converter detected
usbserial.c: Generic converter now attached to ttyUSB2 (or usb/tts/2
for devfs)
usbserial.c: Generic converter detected
usbserial.c: Generic converter now attached to ttyUSB3 (or usb/tts/3
for devfs)
usbserial.c: Generic converter detected
usbserial.c: Generic converter now attached to ttyUSB4 (or usb/tts/4
for devfs)
usbserial.c: Generic converter detected
usbserial.c: Generic converter now attached to ttyUSB5 (or usb/tts/5
for devfs)
usbserial.c: Generic converter detected
usbserial.c: Generic converter now attached to ttyUSB6 (or usb/tts/6
for devfs)
usbserial.c: Generic converter detected
usbserial.c: Generic converter now attached to ttyUSB7 (or usb/tts/7
for devfs)
usbserial.c: USB Serial Driver core v1.4
****************************************************************
The same effect we had in Debian Linux environment. Could somebody so
kind as to explain us how we can resolve this problem?
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|