Hello!
I need to make my Android BSP support Sierra SL8082 usb modem. I have two sources with drivers for android 2.6.32 and linux 2.6.38. My kernel is 2.6.35. I installed sierra.c from Linux package, and sierra_net.c from android package and have such log in dmesg.
<6>usb 1-1: new high speed USB device using fsl-ehci and address 5
<4>usb 1-1: config 1 has an invalid interface number: 7 but max is 3
<4>usb 1-1: config 1 has no interface number 2
<6>sierra 1-1:1.0: Sierra USB modem converter detected
<6>usb 1-1: APM supported, enabling autosuspend.
<6>usb 1-1: Sierra USB modem converter now attached to ttyUSB0
<6>sierra 1-1:1.1: Sierra USB modem converter detected
<6>usb 1-1: APM supported, enabling autosuspend.
<6>usb 1-1: Sierra USB modem converter now attached to ttyUSB1
<6>sierra 1-1:1.3: Sierra USB modem converter detected
<6>usb 1-1: APM supported, enabling autosuspend.
<6>usb 1-1: Sierra USB modem converter now attached to ttyUSB2
<6>usb1: register 'sierra_net' at usb-fsl-ehci.1-1, Sierra Wireless USB-Ethernet Modem, 9a:1f:2a:ad:04:07
lsusb log : Bus 001 Device 005: ID 1199:68a3
Is it correct log? What i should do next to get internet access through that modem?
Related
Hi, when i connect an Huawei 3g usb dongle i see this in dmesg:
[ 2706.844241] usb 2-1: new high speed USB device using tegra-ehci and address 7
[ 2706.876571] usb 2-1: New USB device found, idVendor=12d1, idProduct=1c05
[ 2706.876627] usb 2-1: New USB device strings: Mfr=2, Product=1, SerialNumber=0
[ 2706.876671] usb 2-1: Product: HUAWEI Mobile
[ 2706.876705] usb 2-1: Manufacturer: HUAWEI
but i can't find the associated device under /dev (I guess it should be ttyHS[X])
Thanks for any help!
Several guides explain how to install APX drivers "on Windows only", and that they are not required on Linux (e.g. this one). Unfortunately I think that I do require such a driver on Linux, because I want to pass the APX device to my VirtualBox guest (where Win7 is running). And I think I can only pass usb devices to the guest that appear in VirtualBox's usb device list - which is a list of devices that have a Linux driver. So here's the question:
How can I pass an APX device to a VirtualBox guest (Win7) on a Linux host?
My APX device is a LG P990. It's based on nvidia tegra, so dmesg says:
Code:
[ 7386.292082] usb 2-1: new high-speed USB device number 13 using ehci_hcd
[ 7386.424943] usb 2-1: New USB device found, idVendor=0955, idProduct=7f20
[ 7386.424954] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 7386.424961] usb 2-1: Product: APX
[ 7386.424967] usb 2-1: Manufacturer: NVIDIA Corp.
And this APX device actually is already being passed to VirtualBox, because an error window pops up (not a Windows window, but a VirtualBox window):
Code:
Failed to attach the USB device NVIDIA Corp. APX [0103] to the virtual machine Win7.
Failed to create a proxy device for the USB device. (Error: VERR_READ_ERROR).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Console
Interface:
IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}
Might be a permission problem. However, I don't know how to solve it, because there's no device in /dev that appears when plugging in the LG P990. Google says that my user needs to be in the vboxusers group - but he already is. All the virtualbox devices in /dev are also accessible with my user. So in the end I think that my user should be able to access all devices that are available as a "file" in /dev. But I think there's something missing in /dev. It might be either...
a) /dev/ttyUSB0, which is the device of the usbserial module. It is not being loaded automatically, but I can force it with "sudo modprobe usbserial vendor=0x0955 product=0x7f20". But this doesn't seem to be the correct driver, because it says that the device has been disconnected as soon as the module is loaded. These dmesg entries appear all at once:
Code:
[ 4187.867971] usbcore: registered new interface driver usbserial
[ 4187.867997] usbcore: registered new interface driver usbserial_generic
[ 4187.869407] USB Serial support registered for generic
[ 4187.869436] usbserial_generic 2-1:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes.
[ 4187.869440] usbserial_generic 2-1:1.0: Tell [email protected] to add your device to a proper driver.
[ 4187.869443] usbserial_generic 2-1:1.0: generic converter detected
[ 4187.870237] usb 2-1: generic converter now attached to ttyUSB0
[ 4187.870251] usbserial: USB Serial Driver core
[ 4188.312867] usb 2-1: USB disconnect, device number 7
[ 4188.313295] generic ttyUSB0: generic converter now disconnected from ttyUSB0
[ 4188.313319] usbserial_generic 2-1:1.0: device disconnected
So with the usbserial drivers there's neither /dev/ttyUSB0 nor a USB device in VirtualBox (the APX device that was available without any driver has disappeared).
b) /dev/ttyACM0 is the device of the module cdc_acm, which I think might could also handle the APX device; this is what happens in dmesg when attaching the LG to the USB port while cdc_acm is loaded (and usbserial is not loaded):
Code:
[ 4323.356889] usbcore: registered new interface driver cdc_acm
[ 4323.356895] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
But nothing is happening at all. Again, there's no /dev/ttyACM0. And this time the APX device in VirtualBox is still there (with the VERR_READ_ERROR again). So cdc_acm seems to have no effect at all.
c) loading usbserial AND cdc_acm - the same as if usbserial is loaded without cdc_acm; cdc_acm has no effect, so the same happens as in a)
Now I'm stuck. I don't know how to fix the permission error without a proper device in /dev. My best guess was the usbserial device that should have created /dev/ttyUSB0, but doesn't, and even prevents the APX "raw device" (without driver) to appear in VirtualBox's usb device list.
fyi: I've updated this VirtualBox bug report with my problem.
silly question
thorstenhirsch said:
Several guides explain how to install APX drivers "on Windows only", and that they are not required on Linux (e.g. this one). Unfortunately I think that I do require such a driver on Linux, because I want to pass the APX device to my VirtualBox guest (where Win7 is running). And I think I can only pass usb devices to the guest that appear in VirtualBox's usb device list - which is a list of devices that have a Linux driver. So here's the question:
How can I pass an APX device to a VirtualBox guest (Win7) on a Linux host?
My APX device is a LG P990. It's based on nvidia tegra, so dmesg says:
Code:
[ 7386.292082] usb 2-1: new high-speed USB device number 13 using ehci_hcd
[ 7386.424943] usb 2-1: New USB device found, idVendor=0955, idProduct=7f20
[ 7386.424954] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 7386.424961] usb 2-1: Product: APX
[ 7386.424967] usb 2-1: Manufacturer: NVIDIA Corp.
And this APX device actually is already being passed to VirtualBox, because an error window pops up (not a Windows window, but a VirtualBox window):
Code:
Failed to attach the USB device NVIDIA Corp. APX [0103] to the virtual machine Win7.
Failed to create a proxy device for the USB device. (Error: VERR_READ_ERROR).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Console
Interface:
IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}
Might be a permission problem. However, I don't know how to solve it, because there's no device in /dev that appears when plugging in the LG P990. Google says that my user needs to be in the vboxusers group - but he already is. All the virtualbox devices in /dev are also accessible with my user. So in the end I think that my user should be able to access all devices that are available as a "file" in /dev. But I think there's something missing in /dev. It might be either...
a) /dev/ttyUSB0, which is the device of the usbserial module. It is not being loaded automatically, but I can force it with "sudo modprobe usbserial vendor=0x0955 product=0x7f20". But this doesn't seem to be the correct driver, because it says that the device has been disconnected as soon as the module is loaded. These dmesg entries appear all at once:
Code:
[ 4187.867971] usbcore: registered new interface driver usbserial
[ 4187.867997] usbcore: registered new interface driver usbserial_generic
[ 4187.869407] USB Serial support registered for generic
[ 4187.869436] usbserial_generic 2-1:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes.
[ 4187.869440] usbserial_generic 2-1:1.0: Tell [email protected] to add your device to a proper driver.
[ 4187.869443] usbserial_generic 2-1:1.0: generic converter detected
[ 4187.870237] usb 2-1: generic converter now attached to ttyUSB0
[ 4187.870251] usbserial: USB Serial Driver core
[ 4188.312867] usb 2-1: USB disconnect, device number 7
[ 4188.313295] generic ttyUSB0: generic converter now disconnected from ttyUSB0
[ 4188.313319] usbserial_generic 2-1:1.0: device disconnected
So with the usbserial drivers there's neither /dev/ttyUSB0 nor a USB device in VirtualBox (the APX device that was available without any driver has disappeared).
b) /dev/ttyACM0 is the device of the module cdc_acm, which I think might could also handle the APX device; this is what happens in dmesg when attaching the LG to the USB port while cdc_acm is loaded (and usbserial is not loaded):
Code:
[ 4323.356889] usbcore: registered new interface driver cdc_acm
[ 4323.356895] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
But nothing is happening at all. Again, there's no /dev/ttyACM0. And this time the APX device in VirtualBox is still there (with the VERR_READ_ERROR again). So cdc_acm seems to have no effect at all.
c) loading usbserial AND cdc_acm - the same as if usbserial is loaded without cdc_acm; cdc_acm has no effect, so the same happens as in a)
Now I'm stuck. I don't know how to fix the permission error without a proper device in /dev. My best guess was the usbserial device that should have created /dev/ttyUSB0, but doesn't, and even prevents the APX "raw device" (without driver) to appear in VirtualBox's usb device list.
Click to expand...
Click to collapse
I use LG P990, someday i learn how to change GB partition to ICS partition,but it turn that i cant use my NVFlash, so i flash with kdz other country but nothing , what should i do to get my nvflash work?
a bug in vb
Seems that it's a known bug in VirtualBox: unfortunately, after a day of playing around - i took an old laptop and installed XP.
I didn't find workaround for VirtualBox: and I've tried them plenty (running VB as root is one of them).
Hello,
I have problem with device T-R42.
I cannot enable ethernet - every time I try enable connection it logs to logcat:
dmesg reports:
<6>[ 3.329844] usb 2-1.4: new full speed USB device number 3 using usb20_host
<3>[ 3.409848] usb 2-1.4: device descriptor read/64, error -32
<3>[ 3.599841] usb 2-1.4: device descriptor read/64, error -32
whilest properly operational device has
<6>[ 3.390032] usb 2-1.4: new high speed USB device number 3 using usb20_host
<6>[ 3.502644] usb 2-1.4: New USB device found, idVendor=0b95, idProduct=772b
<6>[ 3.502680] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 3.502716] usb 2-1.4: Product: AX88772C
<6>[ 3.502741] usb 2-1.4: Manufacturer: ASIX Elec. Corp.
<6>[ 3.502766] usb 2-1.4: SerialNumber: 0002B1
<6>[ 4.153134] ASIX USB Ethernet Adapter:v4.1.1 17:50:33 Aug 13 2013
Is there anybody who can help me, please?
Many thanks
Jan
Hi,
First i'm french si sorry for grammar
I 'm on cyanogenmod 12 / nethunter /root /busybox
I recently bought an wifi adaptater and plug it on my phone but I doesn't show up on ifconfig or airmon-ng.I have tried an other card who work with no problem. The strange thing is that the card show up in lsusb and dmesg
Output of lsusb:
Code:
[email protected]:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Output of dmesg:
Code:
[53625.557927] init: untracked pid 1031 exited with status 0[53636.095878] msm-dwc3 msm_dwc3: DWC3 exited from low power mode
[53636.098024] qpnp_chg_ext_charger_reset: qpnp_chg_ext_charger_reset reset:1
[53636.100268] qpnp_chg_ext_charger_reset: qpnp_chg_ext_charger_reset reset:0
[53636.104646] qpnp_chg_ext_charger_wdt_set: qpnp_chg_ext_charger_wdt_set seconds:0
[53636.105999] bq24196_charge_en enable:0
[53636.108919] bq24196_vddmax_set voltage:4350
[53636.115950] bq24196_charge_en enable:2
[53636.125106] xhci-hcd xhci-hcd: xHCI Host Controller
[53636.125408] xhci-hcd xhci-hcd: new USB bus registered, assigned bus number 1
[53636.137471] xhci-hcd xhci-hcd: irq 163, io mem 0xf9200000[53636.155514] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[53636.156186] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[53636.156286] usb usb1: Product: xHCI Host Controller
[53636.156439] usb usb1: Manufacturer: Linux 3.4.67-cyanogenmod-g399b32b xhci-hcd
[53636.156536] usb usb1: SerialNumber: xhci-hcd
[53636.160953] xHCI xhci_add_endpoint called for root hub
[53636.160962] xHCI xhci_check_bandwidth called for root hub[53636.161638] hub 1-0:1.0: USB hub found
[53636.161736] hub 1-0:1.0: 1 port detected
[53636.162783] xhci-hcd xhci-hcd: xHCI Host Controller
[53636.162936] xhci-hcd xhci-hcd: new USB bus registered, assigned bus number 2
[53636.163183] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[53636.163330] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[53636.163473] usb usb2: Product: xHCI Host Controller
[53636.163554] usb usb2: Manufacturer: Linux 3.4.67-cyanogenmod-g399b32b xhci-hcd
[53636.163701] usb usb2: SerialNumber: xhci-hcd
[53636.165570] xHCI xhci_add_endpoint called for root hub
[53636.165579] xHCI xhci_check_bandwidth called for root hub[53636.166218] hub 2-0:1.0: USB hub found
[53636.166310] hub 2-0:1.0: 1 port detected
[53636.653437] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[53636.686391] usb 1-1: New USB device found, idVendor=148f, idProduct=7601
[53636.686847] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[53636.687281] usb 1-1: Product: 802.11 n WLAN
[53636.687521] usb 1-1: Manufacturer: MediaTek
[53636.687759] usb 1-1: SerialNumber: 1.0
[email protected]:~#
If anyone know how to fix or patch it let me know how.
TurtleForGaming said:
Hi,
First i'm french si sorry for grammar
I 'm on cyanogenmod 12 / nethunter /root /busybox
I recently bought an wifi adaptater and plug it on my phone but I doesn't show up on ifconfig or airmon-ng.I have tried an other card who work with no problem. The strange thing is that the card show up in lsusb and dmesg
Output of lsusb:
Code:
[email protected]:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Output of dmesg:
Code:
[53625.557927] init: untracked pid 1031 exited with status 0[53636.095878] msm-dwc3 msm_dwc3: DWC3 exited from low power mode
[53636.098024] qpnp_chg_ext_charger_reset: qpnp_chg_ext_charger_reset reset:1
[53636.100268] qpnp_chg_ext_charger_reset: qpnp_chg_ext_charger_reset reset:0
[53636.104646] qpnp_chg_ext_charger_wdt_set: qpnp_chg_ext_charger_wdt_set seconds:0
[53636.105999] bq24196_charge_en enable:0
[53636.108919] bq24196_vddmax_set voltage:4350
[53636.115950] bq24196_charge_en enable:2
[53636.125106] xhci-hcd xhci-hcd: xHCI Host Controller
[53636.125408] xhci-hcd xhci-hcd: new USB bus registered, assigned bus number 1
[53636.137471] xhci-hcd xhci-hcd: irq 163, io mem 0xf9200000[53636.155514] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[53636.156186] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[53636.156286] usb usb1: Product: xHCI Host Controller
[53636.156439] usb usb1: Manufacturer: Linux 3.4.67-cyanogenmod-g399b32b xhci-hcd
[53636.156536] usb usb1: SerialNumber: xhci-hcd
[53636.160953] xHCI xhci_add_endpoint called for root hub
[53636.160962] xHCI xhci_check_bandwidth called for root hub[53636.161638] hub 1-0:1.0: USB hub found
[53636.161736] hub 1-0:1.0: 1 port detected
[53636.162783] xhci-hcd xhci-hcd: xHCI Host Controller
[53636.162936] xhci-hcd xhci-hcd: new USB bus registered, assigned bus number 2
[53636.163183] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[53636.163330] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[53636.163473] usb usb2: Product: xHCI Host Controller
[53636.163554] usb usb2: Manufacturer: Linux 3.4.67-cyanogenmod-g399b32b xhci-hcd
[53636.163701] usb usb2: SerialNumber: xhci-hcd
[53636.165570] xHCI xhci_add_endpoint called for root hub
[53636.165579] xHCI xhci_check_bandwidth called for root hub[53636.166218] hub 2-0:1.0: USB hub found
[53636.166310] hub 2-0:1.0: 1 port detected
[53636.653437] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[53636.686391] usb 1-1: New USB device found, idVendor=148f, idProduct=7601
[53636.686847] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[53636.687281] usb 1-1: Product: 802.11 n WLAN
[53636.687521] usb 1-1: Manufacturer: MediaTek
[53636.687759] usb 1-1: SerialNumber: 1.0
[email protected]:~#
If anyone know how to fix or patch it let me know how.
Click to expand...
Click to collapse
I guess this thread can help you:
https://forum.xda-developers.com/oneplus-one/general/unleash-true-potential-oneplus-t3394310
Nope. In my case I think it's driver related because other card work but I can't install the linux driver for the MT7601U due software dependencies / 404 error
UP
I have custom 3.4.49 kernel with Android 5.1 and for some reason, I broke it and now the modem ports do not appear in /dev
This is the debug output I see with custom kernel:
<6>[ 2.868000] usbcore: registered new interface driver usbserial
<6>[ 2.876000] usbcore: registered new interface driver usbserial_generic
<6>[ 2.884000] USB Serial support registered for generic
<6>[ 2.944000] usb 1-1.2: new high-speed USB device number 3 using nxp-ehci
<6>[ 3.052000] usb 1-1.2: New USB device found, idVendor=1e0e, idProduct=9001
<6>[ 3.052000] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 3.060000] usb 1-1.2: Product: SimTech, Incorporated
<6>[ 3.064000] usb 1-1.2: Manufacturer: SimTech, Incorporated
<6>[ 3.068000] usb 1-1.2: SerialNumber: 0123456789ABCDEF
<6>[ 3.076000] usbserial: USB Serial Driver core
<6>[ 3.080000] usbcore: registered new interface driver ch341
<6>[ 3.084000] USB Serial support registered for ch341-uart
<6>[ 3.088000] usbcore: registered new interface driver cp210x
<6>[ 3.096000] USB Serial support registered for cp210x
<6>[ 3.100000] usbcore: registered new interface driver ftdi_sio
<6>[ 3.104000] USB Serial support registered for FTDI USB Serial Device
<6>[ 3.112000] ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver
<6>[ 3.116000] usbcore: registered new interface driver option
<6>[ 3.124000] USB Serial support registered for GSM modem (1-port)
<6>[ 3.128000] usbcore: registered new interface driver pl2303
<6>[ 3.136000] USB Serial support registered for pl2303
<6>[ 3.140000] usbcore: registered new interface driver ti_usb_3410_5052
<6>[ 3.148000] USB Serial support registered for TI USB 3410 1 port adapter
<6>[ 3.152000] USB Serial support registered for TI USB 5052 2 port adapter
<6>[ 3.160000] ti_usb_3410_5052: v0.10:TI USB 3410/5052 Serial Driver
Now, if I load back the original kernel, then this is what I see in the debug output.
[ 2.936000] usbcore: registered new interface driver usbserial
[ 2.940000] usbcore: registered new interface driver usbserial_generic
[ 2.948000] USB Serial support registered for generic
[ 3.012000] usb 1-1.2: new high-speed USB device number 3 using nxp-ehci
[ 3.124000] usb 1-1.2: New USB device found, idVendor=1e0e, idProduct=9001
[ 3.124000] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.132000] usb 1-1.2: Product: SimTech, Incorporated
[ 3.136000] usb 1-1.2: Manufacturer: SimTech, Incorporated
[ 3.144000] usb 1-1.2: SerialNumber: 0123456789ABCDEF
[ 3.152000] usbserial: USB Serial Driver core
[ 3.152000] usbcore: registered new interface driver ch341
[ 3.156000] USB Serial support registered for ch341-uart
[ 3.164000] usbcore: registered new interface driver cp210x
[ 3.168000] USB Serial support registered for cp210x
[ 3.172000] usbcore: registered new interface driver ftdi_sio
[ 3.180000] USB Serial support registered for FTDI USB Serial Device
[ 3.184000] ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver
[ 3.192000] usbcore: registered new interface driver option
[ 3.196000] USB Serial support registered for GSM modem (1-port)
[ 3.204000] option 1-1.2:1.0: GSM modem (1-port) converter detected
[ 3.208000] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB0
[ 3.216000] option 1-1.2:1.1: GSM modem (1-port) converter detected
[ 3.220000] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB1
[ 3.228000] option 1-1.2:1.2: GSM modem (1-port) converter detected
[ 3.236000] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB2
[ 3.244000] option 1-1.2:1.3: GSM modem (1-port) converter detected
[ 3.248000] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB3
[ 3.256000] option 1-1.2:1.4: GSM modem (1-port) converter detected
[ 3.260000] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB4
[ 3.268000] usbcore: registered new interface driver pl2303
[ 3.272000] USB Serial support registered for pl2303
[ 3.280000] usbcore: registered new interface driver ti_usb_3410_5052
[ 3.284000] USB Serial support registered for TI USB 3410 1 port adapter
[ 3.292000] USB Serial support registered for TI USB 5052 2 port adapter
[ 3.300000] ti_usb_3410_5052: v0.10:TI USB 3410/5052 Serial Driver
Right after [ 3.196000] USB Serial support registered for GSM modem (1-port), the 5 ttyUSB ports are listed. So what am I missing from the kernel build that is failing to handle the modem and add the ports? The Android build is identical and only the kernel has been changed.
I've uploaded the complete debug capture for both here if that will help to narrow this down.
http://www.axoninstruments.biz/download/ttyUSB-notdetected.txt
http://www.axoninstruments.biz/download/ttyUSB-detected.txt
I found the issue with this. It was an update via git pull that overwrote code I had added to option.c to add the modem USB VID and PID. Once I added them back in, it's working again. DOH!!