>Originally my computer dual boot properly and minicom work properly.
>Therefore hardware is ok and the USB software on the computer works
>because my USB keyboard and mouse work.
>After I run the grub program, the computer do not dual boot properly
>(only boot linux), eventually I get the computer dual boot properly
>and everything else works as before, except minicom has this problem
>Start minicom as root
>minicom: cannot open /dev/usb/tts/0: No such file or directory
>minicom version 2.00.0.
>Linux version 2.6.8-r3 x86, distribution is Gentoo 2004.2.
>How to fix this minicom symptom (which may be just the surface of a
Start by ignoring Lutus...
In your kernel source directory, look through the documentation
on usb-serial drivers, .../Documentation/usb/use-serial.txt
Then you need to find answers some specific questions, which
will either lead you to a solution, or you can post the
information here and others will assist.
1) Is the USB-RS232 adaptor being seen?
2) If not, are you loading a kernel module that supports
the USB-RS232 adaptor you have?
3) What is the proper device file for it?
What do you see if you do "more /proc/bus/usb/devices"? That
will be a list of USB devices being seen by the kernel. Here is
an example of a device that is using a USB-RS232 adaptor, though
it might not be the same adaptor that you have,
T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0403 ProdID=fc0b Rev= 2.00
S: Product=Crystalfontz CFA-633 USB LCD
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=250mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=ftdi_sio
E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
In the third to the last line is the key to that particular
device. It says "Driver=ftdi_sio", which is the kernel module
that is loaded to access this device. You can do "lsmod" to
get a list of kernel modules that you have loaded.
These are the various usb related modules that I have loaded on
this particular machine,
ftdi_sio 25860 0
usbserial 22828 1 ftdi_sio
usbmouse 4416 0
usblp 10880 0
ohci_hcd 14912 0
ehci_hcd 25728 0
usbcore 94868 8 ftdi_sio,usbserial,usbmouse, ...
In this case the interesting modules are ftdi_sio and usbserial.
If you don't have something similar, you need to determine which
driver supports your USB-RS232 device and see that the right
modules are compiled and loaded. (See the usb-serial.txt file
Once the device is seen by the kernel, you need to know which
device special file is the one it is attached to.
The use of /dev/usb/tts depends on devfs, which is obsolete. You
probably are not using it. If it doesn't work, look to see if you
have the /dev/ttyUSB* device special files. If not, use mknod to
create at least the first one or two of them (see the usb-serial.txt
file for the major and minor device numbers).
In all probability your device is located on /dev/ttyUSB0. If
that file does not exist, create it with,
mknod /dev/ttyUSB0 c 188 0
And then try minicom again, after you have re-configured it to use
the different device special file.
FloydL. Davidson <http://web.newsguy.com/floyd_davidson>