Re: 3Com USRobotics 5699B 56k fax modem install
Hi there, On Sat, Feb 07, 2004 at 10:46:35AM -0800, Alex Teslik wrote: Arg! This is indeed a winmodem according to the USRobotics website. I knew to avoid those like the plague, but since the modem cost twice as much as all the other modems and it didn't say winmodem anywhere on the box I figured it was safe. I thought USR was reputable. This sucks. I feel duped. Off to the store to replace this Try: /usr/ports/comms/ltmdm Works for my laptop builtin winmodem (Compaq Evo N610c) Best of luck, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3Com USRobotics 5699B 56k fax modem install
If you can, take your 5699B back and get a 5610B. It's a great non-winmodem made by USR, and it gave me many successful and uninterrupted dial-up hours. As an aside, someone should make a database of working modems, like with working printers. Someone might have done so already, /me shrugs. -- I abhor a system designed for the user, if that word is a coded pejorative meaning stupid and unsophisticated. -- Ken Thompson - Please CC me in all replies, even if I'm on the relevant list(s). pgp0.pgp Description: PGP signature
Re: 3Com USRobotics 5699B 56k fax modem install
Christopher Nehren wrote: If you can, take your 5699B back and get a 5610B. It's a great non-winmodem made by USR, and it gave me many successful and uninterrupted dial-up hours. OK, mine is the 5610B as well. I was not sure if the 5699B was a winmodem or not. I misread the thread thinking that he replaced a winmodem with a non-winmodem.So, I concur get the 5610B and your problems will be gone. Jeff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3Com USRobotics 5699B 56k fax modem install
Hey Jeff, No, you are correct. I had a 5699B and I have now replaced it with a 5610B. Both modems do not work with 4.8_RELEASE. I started another thread called struggling with hylafax install which you have already responded to that details the problems with the 5610B modem. From your uname output I have decided to upgrade to 4.9 RELEASE in the hopes that that supports it. I can't do a 5 branch upgrade right now. fingers crossed and thanks, Alex P.S.- I'll update after the results of my upgrade. -- Original Message --- From: Jeff Gardner [EMAIL PROTECTED] To: Christopher Nehren [EMAIL PROTECTED] Cc: Alex Teslik [EMAIL PROTECTED], FreeBSD Questions List [EMAIL PROTECTED] Sent: Sun, 08 Feb 2004 20:52:51 -0500 Subject: Re: 3Com USRobotics 5699B 56k fax modem install Christopher Nehren wrote: If you can, take your 5699B back and get a 5610B. It's a great non-winmodem made by USR, and it gave me many successful and uninterrupted dial-up hours. OK, mine is the 5610B as well. I was not sure if the 5699B was a winmodem or not. I misread the thread thinking that he replaced a winmodem with a non-winmodem.So, I concur get the 5610B and your problems will be gone. Jeff --- End of Original Message --- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3Com USRobotics 5699B 56k fax modem install
You stumped me... All I know is I have this modem and it works with any FreeBSD I threw at it: sio0: 3COM PCI FaxModem port 0xb400-0xb407 irq 17 at device 2.0 on pci2 and ati* commands respond: ati9 (1.0USR1008\\Modem\PNP00A2\U.S. Robotics 56K FAX INT)FF OK ati7 Configuration Profile... Product type US/Canada Internal Product ID:00561000 OptionsV32bis,V.80,V.34+,x2,V.90 Fax OptionsClass 1/Class 2.0 Line Options Caller ID, Distinctive Ring Clock Freq 92.0Mhz EPROM 256k RAM32k FLASH date 10/1/99 FLASH rev 5.20.3 DSP date 10/1/99 DSP rev5.20.3 OK ati3 U.S. Robotics 56K FAX INT V5.20.3 OK Alex Teslik wrote: Hey Jeff, No, you are correct. I had a 5699B and I have now replaced it with a 5610B. Both modems do not work with 4.8_RELEASE. I started another thread called struggling with hylafax install which you have already responded to that details the problems with the 5610B modem. From your uname output I have decided to upgrade to 4.9 RELEASE in the hopes that that supports it. I can't do a 5 branch upgrade right now. fingers crossed and thanks, Alex P.S.- I'll update after the results of my upgrade. -- Original Message --- From: Jeff Gardner [EMAIL PROTECTED] To: Christopher Nehren [EMAIL PROTECTED] Cc: Alex Teslik [EMAIL PROTECTED], FreeBSD Questions List [EMAIL PROTECTED] Sent: Sun, 08 Feb 2004 20:52:51 -0500 Subject: Re: 3Com USRobotics 5699B 56k fax modem install Christopher Nehren wrote: If you can, take your 5699B back and get a 5610B. It's a great non-winmodem made by USR, and it gave me many successful and uninterrupted dial-up hours. OK, mine is the 5610B as well. I was not sure if the 5699B was a winmodem or not. I misread the thread thinking that he replaced a winmodem with a non-winmodem.So, I concur get the 5610B and your problems will be gone. Jeff --- End of Original Message --- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: 3Com USRobotics 5699B 56k fax modem install
On 4.8 the dmesg pci0: unknown card (vendor=0x12b9, dev=0x1007) at 10.0 irq 2 Means one of 2 things. your modem is what is known as an winmodem. A cheap modem mfg just for ms/windblows market. Which FBSD does not work with. If this PCI modem card works under windows with special driver loaded then it's am winmodem. You can look at the modem circuit board and if it has lucent chips, it's an winmodem. You are SOL. Replace it with an PCI modom card that has onboard controller and DSP functions. Or use any external serial modem. Your PC has legacy bios which does not ID PCI modem cards correctly. In this case add device pun to your kernel source and recompile it. This device has additional code to probe your system's bio's using different methods which in most cases results on your PCI modem card being found. Also works for unknown Nic cards on PC with legacy bio's. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Alex Teslik Sent: Saturday, February 07, 2004 12:09 PM To: list-freebsd-questions Subject: 3Com USRobotics 5699B 56k fax modem install Hello, I've been trying to get this faxmodem setup so I can use hylafax, but with marginal luck. There is lots of documentation for adding support for ISA PNP modems, but I can't find anything for PCI PNP modems. I don't know what to do from here. Here is some output - any recommendations greatly appreciated: dmesg: ... pci0: unknown card (vendor=0x12b9, dev=0x1007) at 10.0 irq 2 ... sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A pciconf -lv: [EMAIL PROTECTED]:10:0:class=0x078000 card=0x00c212b9 chip=0x100712b9 rev=0x00 hdr=0x00 vendor = '3COM Corp, Modem Division (Formerly US Robotics)' device = 'ERL3263A-0 USR 56k Internal DF GWPCI PC99' class= simple comms uname -a: FreeBSD xxx.xxx.xxx 4.8-RELEASE FreeBSD 4.8-RELEASE #5: Fri Feb 6 07:22:37 PST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DUALP3-4_8_0-RELEASE i386 pnpinfo is not relevant with this card because this card is PCI, not ISA. Thanks! Alex ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: 3Com USRobotics 5699B 56k fax modem install
Arg! This is indeed a winmodem according to the USRobotics website. I knew to avoid those like the plague, but since the modem cost twice as much as all the other modems and it didn't say winmodem anywhere on the box I figured it was safe. I thought USR was reputable. This sucks. I feel duped. Off to the store to replace this Thanks, Alex -- Original Message --- From: JJB [EMAIL PROTECTED] To: Alex Teslik [EMAIL PROTECTED], list-freebsd-questions [EMAIL PROTECTED] Sent: Sat, 7 Feb 2004 12:56:45 -0500 Subject: RE: 3Com USRobotics 5699B 56k fax modem install On 4.8 the dmesg pci0: unknown card (vendor=0x12b9, dev=0x1007) at 10.0 irq 2 Means one of 2 things. your modem is what is known as an winmodem. A cheap modem mfg just for ms/windblows market. Which FBSD does not work with. If this PCI modem card works under windows with special driver loaded then it's am winmodem. You can look at the modem circuit board and if it has lucent chips, it's an winmodem. You are SOL. Replace it with an PCI modom card that has onboard controller and DSP functions. Or use any external serial modem. Your PC has legacy bios which does not ID PCI modem cards correctly. In this case add device pun to your kernel source and recompile it. This device has additional code to probe your system's bio's using different methods which in most cases results on your PCI modem card being found. Also works for unknown Nic cards on PC with legacy bio's. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Alex Teslik Sent: Saturday, February 07, 2004 12:09 PM To: list-freebsd-questions Subject: 3Com USRobotics 5699B 56k fax modem install Hello, I've been trying to get this faxmodem setup so I can use hylafax, but with marginal luck. There is lots of documentation for adding support for ISA PNP modems, but I can't find anything for PCI PNP modems. I don't know what to do from here. Here is some output - any recommendations greatly appreciated: dmesg: ... pci0: unknown card (vendor=0x12b9, dev=0x1007) at 10.0 irq 2 ... sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A pciconf -lv: [EMAIL PROTECTED]:10:0:class=0x078000 card=0x00c212b9 chip=0x100712b9 rev=0x00 hdr=0x00 vendor = '3COM Corp, Modem Division (Formerly US Robotics)' device = 'ERL3263A-0 USR 56k Internal DF GWPCI PC99' class= simple comms uname -a: FreeBSD xxx.xxx.xxx 4.8-RELEASE FreeBSD 4.8-RELEASE #5: Fri Feb 6 07:22:37 PST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DUALP3-4_8_0-RELEASE i386 pnpinfo is not relevant with this card because this card is PCI, not ISA. Thanks! Alex ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] --- End of Original Message --- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]