1. Installation
2. Uninstallation
3. Problems solving
- If this driver crash your system - reboot and press "Space" during load. In boot menu select
"Disable user add-ons" and continue boot. Uninstall driver and reboot again into normal mode.
Write me a e-mail about this problem.
4. "Unknown" devices
If you have something, that looks like USB->RS232(serial) adapter or USB modem and tried it with
this driver but have no success - download
usb device info tool and use it to get required information.
- Unplug all USB devices and hubs from your PC.
- Go into Terminal and run the following command:
ls -alR /dev/bus/usb
You should see something like this:
$ ls -alR /dev/bus/usb/
/dev/bus/usb:
total 0
drw-r--r-- 1 walther users 0 May 31 23:16 .
drw-r--r-- 1 walther users 0 Jun 1 2003 ..
drw-r--r-- 1 walther users 0 May 31 23:16 0
drw-r--r-- 1 walther users 0 May 31 23:16 1
crw-r--r-- 1 walther users 0, 0 May 31 23:16 unload
/dev/bus/usb/0:
total 0
drw-r--r-- 1 walther users 0 May 31 23:16 .
drw-r--r-- 1 walther users 0 May 31 23:16 ..
crw-r--r-- 1 walther users 0, 0 May 31 23:16 hub
/dev/bus/usb/1:
total 0
drw-r--r-- 1 walther users 0 May 31 23:16 .
drw-r--r-- 1 walther users 0 May 31 23:16 ..
crw-r--r-- 1 walther users 0, 0 May 31 23:16 hub
- Note this information.
- Now plug your USB serial adapter into PC and run ls -alR /dev/bus/usb/ again.
You'll get something slightly different:
$ ls -alR /dev/bus/usb/
/dev/bus/usb:
total 0
drw-r--r-- 1 walther users 0 May 31 23:16 .
drw-r--r-- 1 walther users 0 Jun 1 2003 ..
drw-r--r-- 1 walther users 0 May 31 23:16 0
drw-r--r-- 1 walther users 0 May 31 23:16 1
crw-r--r-- 1 walther users 0, 0 May 31 23:16 unload
/dev/bus/usb/0:
total 0
drw-r--r-- 1 walther users 0 May 31 23:16 .
drw-r--r-- 1 walther users 0 May 31 23:16 ..
crw-r--r-- 1 walther users 0, 0 May 31 23:16 hub
/dev/bus/usb/1:
total 0
drw-r--r-- 1 walther users 0 May 31 23:16 .
drw-r--r-- 1 walther users 0 May 31 23:16 ..
crw-r--r-- 1 walther users 0, 0 May 31 23:16 hub
$
- Compare this results with previous one and look for file,
that appeared. This file is your USB serial adapter.
- Unpack downloaded usb_dev_info command and run it with full path to file appeared in
the second listing. For my sample I should run:
usb_dev_info /dev/bus/usb/0/1
I'll get the following:
$ usb_dev_info /dev/bus/usb/0/1
[Device]
Class .................. 0
Subclass ............... 0
Protocol ............... 0
Vendor ID .............. 0x067b
Product ID ............. 0x2303
Version ................ 0x0202
Manufacturer String .... ""
Product String ......... ""
Serial Number .......... ""
[Configuration 0]
[Interface 0]
Class .............. 255
Subclass ........... 0
Protocol ........... 0
[Endpoint 0]
MaxPacketSize .... 10
Interval ......... 1
Type ............. Interrupt
Direction ........ Input
[Endpoint 1]
MaxPacketSize .... 64
Interval ......... 0
Type ............. Bulk
Direction ........ Output
[Endpoint 2]
MaxPacketSize .... 64
Interval ......... 0
Type ............. Bulk
Direction ........ Input
- Send this information to me with some additional words about your device.
What is wrong with BeOS.USB.patches?
All know that "classical" BeOS R5 don't works on OHCI USB hardware. But some time ago on one well-known
BeOS file-sharing network appeared patches for plain R5. Those patches allows to work with OHCI
hardware under this system version. Looks like it is some part of Dan0 or other "leaked" versions.
There are 3 patches in BeOS.USB.patches.zip:
1. beos-usb-patch,
2. beos-usb.modem-patch,
3. beos-usb.modem-patch.sm.
The Evil is in two last patches. The source of problem - changed functions in tty module. The
Dan0 contains two additional functions in the middle of tty module description table. But the module version
was not changed - it is still v1. So if driver, that was compiled with old tty module layout, will try to use it - system
crashes. Looks like those patches contains the same "enchanced" tty module like in Dan0. So - you should roll back
those modem-patches - restore the previous configuration as described in patches readme. The first one
- "beos-usb-patch" is OK.
Information for Dan0 users
The driver is still not working under Dan0 out of box. At first you have no need to use it for ACM-compatible devices,
because Dan0 has it's own implementation of usb_acm driver. There is also one problem with Dan0 - the
"tty" module was chaged in very dangerous way - there is no possibility to create backward compatible
implementation of serial port driver with the new tty interfaces. If you really have one of those USB Serial
Adapters and want to use it under Dan0 - you have to make some hand work. Sorry for this, but I have not
using Dan0 as my main working system. So you must to build Dan0 version by yourself. Thank you for your patience. Below
is an operations you need to install USB serial driver for Dan0:
Siarzuk Zharski
http://www.zharik.host.sk/