On Friday June 15 2007 3:14:53 am E. Robert Tisdale wrote: > Claude Jones wrote: > > Pete Cull x2315 wrote: > >> I do remember that in a Windows XP Pro environment the > >> USR5610B did appear as COM3 which translated to /dev/ttys2 or > >> /dev/ttys3. Then, I seem to remember that we needed to link > >> /dev/modem with /dev/ttys3 or /dev/ttys2. > > > > This reminded me of something. With my 5610b, it was NOT being > > assigned ttys2 or ttys3 as was to be expected but a higher one. > > As I recall, I ascertained the tty assignment by > > running "kudzu -p" and then created a symlink between that ttys# > > Which ttys#? > Where does "kudzu -p" tell me which device is associated with the modem? > > class: MODEM > > bus: PCI > > detached: 0 > > driver: 8250_pci > > desc: "3Com Corp, Modem Division 56K FaxModem Model 5610" > > vendorId: 12b9 > > deviceId: 1008 > > subVendorId: 12b9 > > subDeviceId: 00d3 > > pciType: 1 > > pcidom: 0 > > pcibus: 2 > > pcidev: 4 > > pcifn: 0 > > - > > > and /dev/modem The fact that it is not listed is at least a part, your problem, I believe. In reviewing my old doc I wrote up at the time, which I finally found, it says it should be assigned ttys2 or 3, which was not my memory. In any event, the ttys# line would always appear when I ran kudzu -p if the driver was working properly and the device got installed -- mere detection is insufficient -- I was able to detect many winmodems in those days, but I never got one of them to work or get a ttys# assigned to them -- Claude Jones Levit & James, Inc. Leesburg, VA
