Re: BTW, I know the modem is healthy because I got it to work on Windoze. Do the modem diagnostics under Windoze. and return the info, including the driver name and the AT responses. Also from wwwl.linuxant.com, download and try the Listmodem tool from http://www.linuxant.com/drivers/modemident.php and see what it reports. MarvS On 9/18/07, C M Ackerman <c.m.ackerman@xxxxxxxxx> wrote: > Sorry for the delay, I was out of commission for a couple days, and just > returned. > wvdialconf still doesn't seem to recognize the modem. I copied the session > log at the bottom of this email. > > Since I'm not that familiar with Linux, is it possible that I might not have > the right modprobe's installed? > It didn't do much until I installed the following two modules > modprobe usbserial vendor=0x148d product=0x1671 > modprobe cdc-acm > Then it seemed to work partially. For example, it does create and remove > /dev/ttyUSB0 when I plug in and unplug the modem. > > Here's the things that don't look right to me: > > 1) When plugged it in, the last line in /var/log/messages says something > failed. Here's the log: > debian10:/var/log# tail /var/log/messages > Sep 18 18:07:33 localhost -- MARK -- > Sep 18 18:15:40 localhost kernel: usb 1-2: new full speed USB device > using uhci_hcd and address 11 > Sep 18 18:15:46 localhost kernel: usb 1-2: configuration #1 chosen from > 1 choice > Sep 18 18:15:46 localhost kernel: usbserial_generic 1-2:1.0: generic > converter detected > Sep 18 18:15:46 localhost kernel: usb 1-2: generic converter now > attached to ttyUSB0 > Sep 18 18:15:46 localhost kernel: usbserial_generic 1-2:1.1: generic > converter detected > Sep 18 18:15:46 localhost kernel: usbserial_generic: probe of 1-2:1.1 > failed with error -5 > debian10:/var/log# > > 2) When looking at /proc/bus/usb/devices it shows this and > the last line that says Driver=(none) doesn't look right. > >>> P: Vendor=148d ProdID=1671 Rev= 1.00 > >>> S: Manufacturer=Creative Pte Ltd. > >>> S: Product=Creative Modem Blaster V.92 USB > >>> S: SerialNumber=00000000 > >>> C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=260mA > >>> I: If#= 0 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 > >>> Driver=usbserial_generic > >>> E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms > >>> E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms > >>> I: If#= 1 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=01 Prot=ff Driver=(none) > > 3) I went a bit deeper and the command "lsusb -v -d 0x148d:" shows some > errors at the end: > CDC Header: > bcdCDC 1.10 > CDC Union: > bMasterInterface 0 > bSlaveInterface 1 > CDC Call Management: > bmCapabilities 0x00 > bDataInterface 1 > UNRECOGNIZED CDC: 04 24 03 00 > Country Selection: > iCountryCodeRelDate 5 (??) > wCountryCode 0x4803 > cannot read device status, Protocol error (71) > > 4) And finally, I can't communicate with the modem. It doesn't respond to > an "at" command when I try to talk to it using picocom /dev/ttyUSB0 > It just hangs. > > Also, I wasn't sure about Jacques 2cd point in his response below. Does it > mean that I should go to Linuxant to find a driver > if the ACM driver doesn't work? > > Thanks for your help! > -Chaim > > BTW, I know the modem is healthy because I got it to work on Windoze. > > > ============ wvdialconf session (with modem plugged in) ================= > debian10:~# wvdialconf > Editing `/etc/wvdial.conf'. > > Scanning your serial ports for a modem. > > ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud > ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud > ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. > ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud > ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud > ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. > Modem Port Scan<*1>: S2 S3 > WvModem<*1>: Cannot get information for serial port. > ttyUSB0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud > ttyUSB0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud > ttyUSB0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. > > > Sorry, no modem was detected! Is it in use by another program? > Did you configure it properly with setserial? > > Please read the FAQ at http://open.nit.ca/wiki/?WvDial > > If you still have problems, send mail to <wvdial-list@xxxxxxxxxxxx>. > > ----- Original Message ----- > From: "Jacques Goldberg" <Jacques.Goldberg@xxxxxxx> > To: "Marvin Stodolsky" <marvin.stodolsky@xxxxxxxxx> > Cc: "C M Ackerman" <c.m.ackerman@xxxxxxxxx>; <discuss@xxxxxxxxxxxxx> > Sent: Monday, September 17, 2007 3:04 AM > Subject: Re: Chaim, Creative USB Modem Blaster?, USA, Debian GNU/Linux 4.0, > kernel 2.6.18-5-486 > > > > Chaim, > > > > 1-Sure enough, the Creative Modem Blaster V.90 (not V.92) USB modem using > > the 5670 chip is directly supported under Linux as you can see if you > > look, again, at http://xmodem.org/modems/usblist.html (for your > > information, it uses an Agere 480 chip with a Venus controller which goes > > along with no need for a special driver). > > It costs nothing and cannot do any damage to bet that the much more recent > > 5671 uses the same or a similar chip: just run wvdialconf ! > > > > 2-Marvin's advice is great, so much the more that your modem is > > manufactured by BroadXANT, a company which belongs to the Creative group. > > Linuxant makes Linux drivers as quoted by Marv for ConeXANT modems (XANT > > emphaiszed by me). > > > > Jacques > > > > Marvin Stodolsky wrote: > >> CM > >> > >> Some of Creative modems are supported by hsfmodem software. > >> So from wwwl.linuxant.com, download and try the Listmodem tool from > >> http://www.linuxant.com/drivers/modemident.php > >> > >> MarvS > >> > >> On 9/16/07, C M Ackerman <c.m.ackerman@xxxxxxxxx> wrote: > >>>> Please, which are the make of your modem? > >>> Creative Labs Modem Blaster V.92 USB Modem > >>> http://us.creative.com/products/product.asp?category=7&subcategory=40&product=266&nav=features > >>> > >>>> Please give as much information as you can, including everything > >>>> written > >>>> on the modem. > >>> I just bought this from Amazon.com. Here's what's written on the back: > >>> Creative Modem Blaster V.92 DES5671-1 > >>> Powered by BroadXent > >>> > >>> Here's some relevent info from /proc/bus/usb/devices > >>> T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 > >>> D: Ver= 1.10 Cls=02(comm.) Sub=00 Prot=ff MxPS=64 #Cfgs= 1 > >>> P: Vendor=148d ProdID=1671 Rev= 1.00 > >>> S: Manufacturer=Creative Pte Ltd. > >>> S: Product=Creative Modem Blaster V.92 USB > >>> S: SerialNumber=00000000 > >>> C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=260mA > >>> I: If#= 0 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 > >>> Driver=usbserial_generic > >>> E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms > >>> E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms > >>> I: If#= 1 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=01 Prot=ff Driver=(none) > >>> E: Ad=82(I) Atr=03(Int.) MxPS= 64 Ivl=1ms > >>> > >>>> Have you read http://tldp.org/HOWTO/Modem-HOWTO-2.html ? > >>>> And specially section 2.9 ? > >>> wvdialconf can't find it. > >>> > >>> I'm relatively new to Linux, so I'm not very sure about what I'm doing, > >>> but > >>> I couldn't find an acm driver anywhere in my 2.6 system. > >>> so after looking around on the web, I tried this: > >>> modprobe usbserial vendor=0x148d product=0x1671 > >>> depmod > >>> > >>> Then I looked in /var/log/messages and there was much more going on, but > >>> it > >>> still ended in an error: > >>> Sep 16 06:36:27 localhost kernel: usb 3-1: new full speed USB device > >>> using > >>> uhci_hcd and address 3 > >>> Sep 16 06:36:32 localhost kernel: usb 3-1: configuration #1 chosen from > >>> 1 > >>> choice > >>> Sep 16 06:36:32 localhost kernel: usbserial_generic 3-1:1.0: generic > >>> converter detected > >>> Sep 16 06:36:32 localhost kernel: usb 3-1: generic converter now > >>> attached to > >>> ttyUSB0 > >>> Sep 16 06:36:32 localhost kernel: usbserial_generic 3-1:1.1: generic > >>> converter detected > >>> Sep 16 06:36:32 localhost kernel: usbserial_generic: probe of 3-1:1.1 > >>> failed > >>> with error -5 > >>> > >>> I persisted and tried opening /dev/ttyUSB0, but it hung. > >>> > >>> Thank you, > >>> Chaim > >>> > >>> ----- Original Message ----- > >>> From: "Jacques Goldberg" <Jacques.Goldberg@xxxxxxx> > >>> To: "C M Ackerman" <c.m.ackerman@xxxxxxxxx> > >>> Cc: <DISCUSS@xxxxxxxxxxxxx> > >>> Sent: Sunday, September 16, 2007 5:12 PM > >>> Subject: Re: Chaim, Creative USB Modem Blaster?, USA, Debian GNU/Linux > >>> 4.0, > >>> kernel 2.6.18-5-486 > >>> > >>> > >>>> Chaim, > >>>> It is impossible to identify an USB modem by its chipset, at least I do > >>>> not know how to do that. > >>>> Please, which are the make of your modem? > >>>> Please give as much information as you can, including everything > >>>> written > >>>> on the modem. > >>>> If the device would be a PCI chip embedded in the USB modem, then 148d > >>>> means that the manufacturer is Digicom which has only one modem, 1003, > >>>> in > >>>> its catalog (a Conexant HCF clone or embedded). But this is not your > >>>> case. > >>>> There is no information for any device model 1671 made by Digicom. > >>>> Rob Clark's well maintained table http://xmodem.org/modems/usblist.html > >>>> shows two modems made by ASKEY using Digicom chips: none has the same > >>>> USB > >>>> chip 148d:1671 as yours. > >>>> Have you read http://tldp.org/HOWTO/Modem-HOWTO-2.html ? > >>>> And specially section 2.9 ? > >>>> Have you tried to run wvdialconf (see man wvdialconf or > >>>> http://linmodems.technion.ac.il/wvdial.html) to see if by chance your > >>>> modem is USB CDC ACM compliant and thus will work without any extra > >>>> driver? > >>>> Are you aware that the modem has to be powered when trying wvdialconf? > >>>> > >>>> Jacques > >>>> > >>>> C M Ackerman wrote: > >>>>> The usb modem reports: > >>>>> ID 148d:1671 > >>>>> > >>>>> Is there support for this? > >>>>> > >>>>> Thanks in advance, > >>>>> Chaim > >>> > >
