Kyocera KPC650 Cellular Modem Not Recognized in Yast

Hi all!

I just signed up for wireless broadband and was sold a Kyocera KPC 650 cellular modem (if that’s the correct name for the device). It works fine in Windows, so it’s not a hardware problem.

I have read many posts claiming you can set this up as a regular modem in Yast and use Kinternet to dial out with it, but my problem is that neither of these programs can even see the device.

However, when I boot up I can see a listing for it on the post screen showing it as a USB device at USB1, USB2, and USB3, IIRC.

Also, if I do a hardware scan in Yast, it shows up in the USB section as /dev/ttyUSB2 along with the correct name and a vendor ID, etc.

So my question is, what do I need to do to get Yast and Kinternet to recognize it? Is there a kernel module or something? Or a special console command?

I can’t find any info on Google of anyone else having this problem, they were all apparently able to see the device in Yast.

Thanks in advance!

Just to clarify, the device is not seen in Yast / Network Devices / Modems. There is no entry at all after the system searches for a modem. I then manually installed a modem under /dev/ttyUSB2 but Kinternet did not respond when I tried to dial out.

If I run KPPP and try to “query modem” under /dev/ttyUSB2 a message saying “can’t open modem” appears.

Also, I am running OpenSuse 11.

Hi
When you plug the device in, run the command dmesg, is it seen?


Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.11-0.1-default
up 4 days 13:49, 1 user, load average: 0.04, 0.11, 0.18
GPU GeForce 6600 TE/6200 TE - Driver Version: 173.14.12

demsg produces the following (edited) output:

usb 4-1: new device found, idVendor=0c88, idProduct=17da
usb 4-1: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 4-1: Product: Qualcomm CDMA Technologies MSM
usb 4-1: Manufacturer: Qualcomm, Incorporated
usb 4-1: configuration #1 chosen from 1 choice
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for airprime
airprime 4-1:1.0: airprime converter detected
usb 4-1: airprime converter now attached to ttyUSB0
usb 4-1: airprime converter now attached to ttyUSB1
usb 4-1: airprime converter now attached to ttyUSB2
airprime 4-1:1.1: airprime converter detected
usb 4-1: airprime converter now attached to ttyUSB3
usb 4-1: airprime converter now attached to ttyUSB4
usb 4-1: airprime converter now attached to ttyUSB5
usbcore: registered new interface driver airprime

When I try to run Kinternet, here is the log from there:



SuSE Meta pppd (smpppd-ifcfg), Version 1.59 on linux-uwcp.
Status is: disconnected
trying to connect to smpppd
connect to smpppd
Status is: disconnected
Status is: connecting
pppd[0]: Plugin passwordfd.so loaded.
pppd[0]: --> WvDial: Internet dialer version 1.56 (abuild@mandelbrot)
pppd[0]: --> Initializing modem.
pppd[0]: Caught signal 1:  Attempting to exit gracefully...

I downgraded to 10.3 to see if that would help, but it did not. Am currently running 10.3 but will probably go back to 11 in the next day or so.

Hi
Have you tried USB0?


Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.11-0.1-default
up 4 days 14:35, 1 user, load average: 0.08, 0.21, 0.29
GPU GeForce 6600 TE/6200 TE - Driver Version: 173.14.12

I will try USB0, but I think I tried that already in KPPP with no luck. I’ll try again in both KPPP and in Kinternet.

I was hoping to see a USB entry in Yast / Network Devices / Modem but no luck, just /dev/tty/ entries.

OK, thanks much for getting me this far.

USB0 did nothing in KPPP, but I went into Yast / Network Devices / Modems and added /dev/ttyUSB0 manually to the list. Then I rebooted, since changes in Kinternet seem to require this before they take effect.

Then I tried to connect with Kinternet, and according to the log, the modem is responding and dialing out, but there is some sort of authentication problem keeping me from connecting to the network. So once I get that sorted out, I should be good to go.

If anyone knows how to get through the authentication process for Cricket Wireless Broadband, that would be most helpful. I thought all I needed was my phone number to log on to the network, but this does not seem to be working.

Here is my Kinternet log, in case anyone is interested:

SuSE Meta pppd (smpppd-ifcfg), Version 1.59 on linux-uwcp.
Status is: disconnected
trying to connect to smpppd
connect to smpppd
Status is: disconnected
Status is: connecting
pppd[0]: Plugin passwordfd.so loaded.
pppd[0]: --> WvDial: Internet dialer version 1.56 (abuild@mandelbrot)
pppd[0]: --> Initializing modem.
pppd[0]: --> Sending: ATZ
pppd[0]: ATZ
pppd[0]: OK
pppd[0]: --> Sending: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
pppd[0]: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
pppd[0]: OK
pppd[0]: --> Sending: ATM1
pppd[0]: ATM1
pppd[0]: OK
pppd[0]: --> Sending: ATX3
pppd[0]: ATX3
pppd[0]: OK
pppd[0]: --> Modem initialized.
pppd[0]: --> Sending: ATDT#777
pppd[0]: --> Waiting for carrier.
pppd[0]: ATDT#777
pppd[0]: CONNECT
pppd[0]: --> Carrier detected.  Waiting for prompt.
pppd[0]: ~[7f]}#@!}!}!} }9}"}&} } } } }#}%B#}%}%}&[0e];~o}'}"}(}"z:~
pppd[0]: --> PPP negotiation detected.
pppd[0]: Serial connection established.
pppd[0]: Renamed interface ppp0 to modem0
pppd[0]: Using interface modem0
Status is: connecting
pppd[0]: Connect: modem0 <--> /dev/ttyUSB0
pppd[0]: CHAP authentication failed
Authentication error. Maybe bad account or password.
pppd[0]: CHAP authentication failed
Authentication error. Maybe bad account or password.
pppd[0]: Connection terminated.
Status is: disconnected
pppd[0] died: Authentication error (exit code 19)

Hi
Disable the chap authentication in the ppp options


noauth

There may be others… have a read of man pppd


Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.11-0.1-default
up 4 days 18:27, 1 user, load average: 0.13, 0.12, 0.19
GPU GeForce 6600 TE/6200 TE - Driver Version: 173.14.12