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).
Related
I've read this thread: http://forum.xda-developers.com/showthread.php?t=570452
Actually, I've been using the same setup since the G1, and most recently with my Nexus One. Using those devices, when I start up my VirtualBox session and connect them to the PC, USB debugging mode starts and I can use ADB to connect to the device. As a point of reference, ADB also works from the Windows 7 host environment. What I cannot seem to get working is ADB with my Ubuntu 10.10 guest OS. I'm seeing the following in the dmesg log:
Code:
[ 453.061415] usb 1-1: new high speed USB device using ehci_hcd and address 2
[ 454.132202] usb 1-1: device descriptor read/64, error -32
[ 455.268177] usb 1-1: device descriptor read/64, error -32
[ 456.397201] usb 1-1: new high speed USB device using ehci_hcd and address 3
[ 457.440195] usb 1-1: device descriptor read/64, error -32
[ 458.560189] usb 1-1: device descriptor read/64, error -32
[ 459.684182] usb 1-1: new high speed USB device using ehci_hcd and address 4
[ 459.730509] usb 1-1: device descriptor read/8, error -32
[ 459.874823] usb 1-1: device descriptor read/8, error -32
[ 460.977314] usb 1-1: new high speed USB device using ehci_hcd and address 5
[ 461.042126] usb 1-1: device descriptor read/8, error -32
[ 461.186504] usb 1-1: device descriptor read/8, error -32
[ 461.288285] hub 1-0:1.0: unable to enumerate USB device on port 1
The VirtualBox USB driver looks like it is correctly installed on the host machine. Anyone have any idea?
Chinpokomon said:
I've read this thread: http://forum.xda-developers.com/showthread.php?t=570452
Actually, I've been using the same setup since the G1, and most recently with my Nexus One. Using those devices, when I start up my VirtualBox session and connect them to the PC, USB debugging mode starts and I can use ADB to connect to the device. As a point of reference, ADB also works from the Windows 7 host environment. What I cannot seem to get working is ADB with my Ubuntu 10.10 guest OS. I'm seeing the following in the dmesg log:
Code:
[ 453.061415] usb 1-1: new high speed USB device using ehci_hcd and address 2
[ 454.132202] usb 1-1: device descriptor read/64, error -32
[ 455.268177] usb 1-1: device descriptor read/64, error -32
[ 456.397201] usb 1-1: new high speed USB device using ehci_hcd and address 3
[ 457.440195] usb 1-1: device descriptor read/64, error -32
[ 458.560189] usb 1-1: device descriptor read/64, error -32
[ 459.684182] usb 1-1: new high speed USB device using ehci_hcd and address 4
[ 459.730509] usb 1-1: device descriptor read/8, error -32
[ 459.874823] usb 1-1: device descriptor read/8, error -32
[ 460.977314] usb 1-1: new high speed USB device using ehci_hcd and address 5
[ 461.042126] usb 1-1: device descriptor read/8, error -32
[ 461.186504] usb 1-1: device descriptor read/8, error -32
[ 461.288285] hub 1-0:1.0: unable to enumerate USB device on port 1
The VirtualBox USB driver looks like it is correctly installed on the host machine. Anyone have any idea?
Click to expand...
Click to collapse
may have something to do with the udev adress G1 and N1 where made by HTC using the same UDEV
slowz3r said:
may have something to do with the udev adress G1 and N1 where made by HTC using the same UDEV
Click to expand...
Click to collapse
That was my initial thought as well, but it doesn't look like it's getting that far. I looked and the vendorID already matches what I had in my udev rules. To me, this seems like Virtual Box isn't modeling the Nexus S correctly for some reason.
Chinpokomon said:
That was my initial thought as well, but it doesn't look like it's getting that far. I looked and the vendorID already matches what I had in my udev rules. To me, this seems like Virtual Box isn't modeling the Nexus S correctly for some reason.
Click to expand...
Click to collapse
weird, works perfect using VMware :/
I'm going to have do some serious shuffling. Android requires a 64-bit build environment now, but I use 32-bit Windows to work around driver signing issues. I think my best setup now will be a 64-bit Ubuntu host with a 32-bit Windows 7 guest... That's going to take some work. *sigh*
@Chinpokomon: did you get any solutions to fix this issue? Even i'm hving similar kind of issue. Past 2 days am trying to connect and list my Samsung Captivate Device in Ubuntu, but i failed everytime. Here is my environment
Launching Ubuntu 10.10 (guest OS) from Windows 7 (host OS) using Virtual Box 4.0
In the host OS (Windows 7), i have enabled USB Device Filter for Samsung_Android, and i could see that device in Ubuntu 10.10, but when i use 'lsusb', it doesn't list the samsung device. Any help would be greatly appreciated.
I never have used VBox but if its anything like VMware dont you have to disconnect the device from windows /connect it to VBox
Same here except for the error: -110 instead of -32.
I have three USB filters defined in VBox (product ID 4e20 = fastboot, 4e21 = debug disabled, 4e22 = debug enabled) and corresponding rules defined in /etc/udev/rules.d/51-android.rules
In fastboot mode this works perfectly fine. "fastbood devices" lists the device but when the Nexus S is in normal operation (no matter if debug enabled or disabled), it does not work.
"lsusb" lists the device in fastboot mode but in normal operation it takes a loooooong time and then does not list the Samsung device...
I switched udev to debog logging (/etc/udev/udev.conf -> udev_log="debug") but didn't get any additional logging details in /var/log/udev...
I took the time and recreated the VM using VMware player instead of VirtualBox (after reading the post from slowz3r) and I can confirm exactly the same setup works fine in VMware... It's neither a host nor a Ubuntu setup problem but it seems to be the VirtualBox USB support causing the issue with the NS in debug mode...
Moved to VMWare - works like charm
Hi there,
This is the ONLY thread I have found on the internet where people are actually talking about the same problem I am having. I tried for some days now to get this working, and so far no luck.
I posted a thread over at the VirtualBox forums regarding the issue. Check it out here: (apparently I couldn't post my link as this is my first post, but google "Google Nexus S USB redirection to guest fails" and you'll probably find it). If anyone have any further information on this issue, please post your findings in this thread. I don't like the solution "switch to VMware" though
Thanks in advance!
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!
Hi all,
i am opening this thread to push the development on the mtk65xx phones. The taget is to boot CM10 on those devices and maybe we could achive this goal with bundled effort, here is how far i get on this:
1. the source code for this devices is now accessible through different sources. as i own an alcatel one touch 998 the code is accessible ( and for many other phones ) on http://sourceforge.net/projects/alcatel/files/.
2 Building the source:
2.1 Pass the Target device through the environment variable during build e.g. TARGET_PRODUCT=jrdsh77_cu_ics2 for my phone
2.1 Add the needed Header to the Product through mkimage -> ./mkimage zImage KERNEL > kernel (mkimage is inside mediatek/build/tools/)
this will add the needed header to boot the image to the compiled zImage.
3. Repack the Image with repack-MT65xx.pl ( my honor and rewards to Bruno Martins )
4. Boot Phone to Recovery and flash the kernel through dd if=<PathToBoot.img>/boot.img of=/dev/bootimg && sync
5. Reboot Phone.
Ok this is about it how i do it, i don not mention to flash the System-Partiton here as this is a obvious task and can easily done by the cm-<...>.zip generated by the normal build procedure, by commenting out the kernel flash lines inside the updater-script.
Problem for me is now that i get into a bootloop: My phone only shows the vendor Logo stays there for some seconds an reboots again, on my x86_64 Machine inside dmesg i get:
Code:
[ 6717.986372] usb 2-4: new high-speed USB device number 17 using ehci_hcd
[ 6718.120618] usb 2-4: New USB device found, idVendor=0e8d, idProduct=2000
[ 6718.120629] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6718.120637] usb 2-4: Product: MT65xx Preloader
[ 6718.120642] usb 2-4: Manufacturer: MediaTek
[ 6718.182193] cdc_acm 2-4:1.1: ttyACM0: USB ACM device
[ 6719.142274] usb 2-4: USB disconnect, device number 17
[ 6734.134696] usb 2-4: new high-speed USB device number 18 using ehci_hcd
[ 6734.268987] usb 2-4: New USB device found, idVendor=0e8d, idProduct=2000
[ 6734.268998] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6734.269005] usb 2-4: Product: MT65xx Preloader
[ 6734.269011] usb 2-4: Manufacturer: MediaTek
[ 6734.331210] cdc_acm 2-4:1.1: ttyACM0: USB ACM device
[ 6735.294111] usb 2-4: USB disconnect, device number 18
[ 6750.067450] usb 2-4: new high-speed USB device number 19 using ehci_hcd
[ 6750.201879] usb 2-4: New USB device found, idVendor=0e8d, idProduct=2000
[ 6750.201890] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6750.201897] usb 2-4: Product: MT65xx Preloader
[ 6750.201903] usb 2-4: Manufacturer: MediaTek
[ 6750.263563] cdc_acm 2-4:1.1: ttyACM0: USB ACM device
[ 6751.230653] usb 2-4: USB disconnect, device number 19
[ 6766.000293] usb 2-4: new high-speed USB device number 20 using ehci_hcd
[ 6766.134432] usb 2-4: New USB device found, idVendor=0e8d, idProduct=2000
[ 6766.134443] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6766.134451] usb 2-4: Product: MT65xx Preloader
[ 6766.134456] usb 2-4: Manufacturer: MediaTek
[ 6766.196292] cdc_acm 2-4:1.1: ttyACM0: USB ACM device
[ 6767.150220] usb 2-4: USB disconnect, device number 20
[ 6781.933093] usb 2-4: new high-speed USB device number 21 using ehci_hcd
[ 6782.067271] usb 2-4: New USB device found, idVendor=0e8d, idProduct=2000
[ 6782.067282] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6782.067289] usb 2-4: Product: MT65xx Preloader
[ 6782.067295] usb 2-4: Manufacturer: MediaTek
[ 6782.129241] cdc_acm 2-4:1.1: ttyACM0: USB ACM device
[ 6783.096138] usb 2-4: USB disconnect, device number 21
So it starts -> boots to preloader -> tries to boot the kernel and fails miserably here, as i dont have any chance to get any debug message to find out what is wrong here im stuck, i have no suggestion, i booted a kernel once succesfully but flashing it now does lead to the same beavior. Maybe reseting it to complete stock and starting again would help but i dont know how to do this, maybe someone can provide me here with some Information, or maybe someone can start with the information here, if any Information is needed or some point needs clearification im free to help. i have several Serial debug cables/chips here but i dont see where i could attach a serial console to the phone to read some debug messages, does anyone know if this is possible?
Sorry for my lousy english :/ i try to get better.
Greetz HUELK
I own an mtk6575 device too,Emmc partition, powervr,hvga screen, 512mb ram running J.b 4.1...
But I am new to ROM porting,wish I culd help
I am not sure how far you can go but, atleast booting to CM is an important steps.
I cant understand the log cat, however if you want to use the stock kernel, have you tried this?
BoardConfig.mk file add
TARGET_PREBUILT_KERNEL := device/manufacturer/devicename/kernel
a few words of encouragement
would be great to have CM10 for MTK65xx phones, maybe solve my crap chinaclone GPS problem.
hope you not abandoned the project.
have u checked the CPUgovernor in the original rom, maybe overclocking and setting voltages too high. set the conservative option as default in the kernel build.
stevet99uk said:
would be great to have CM10 for MTK65xx phones, maybe solve my crap chinaclone GPS problem.
hope you not abandoned the project.
have u checked the CPUgovernor in the original rom, maybe overclocking and setting voltages too high. set the conservative option as default in the kernel build.
Click to expand...
Click to collapse
Hello there. At last someone is doing it too. I'm currently downloading the sources again to re attempt the unknown.
I also have that idea of incompatible/unbootable kernel. Have you tried unpacking the stock boot.img by using the mt-65xx-unpack.pl? That is what I'm thinking to do but have not tried it yet since I'm still building the environment.
We get the working kernel from the original boot.img then use it to build the boot.img to be used for cm.
so theres no hope for android chinese. eh. i am trying to port the cm10 but no luck. since there is no real source given to download.
Hi everyone
I'm working on a custom embedbed android version with printing support. I'm having some troubles when connecting the printer do the board (EM210 Android 4.0)
This is the log from dmsg when I connect the usb printer (1.1 USB) the board is compliant with USB 2.0.
[ 3867.524022] usb 1-1.3: new full speed USB device number 14 using s5p-ehci
[ 3867.614000] usb 1-1.3: device descriptor read/64, error -32
[ 3867.804011] usb 1-1.3: device descriptor read/64, error -32
[ 3867.994175] usb 1-1.3: new full speed USB device number 15 using s5p-ehci
[ 3868.084009] usb 1-1.3: device descriptor read/64, error -32
[ 3868.274402] usb 1-1.3: device descriptor read/64, error -32
[ 3868.469008] usb 1-1.3: new full speed USB device number 16 using s5p-ehci
[ 3868.883827] usb 1-1.3: device not accepting address 16, error -32
[ 3868.904184] hub 1-1:1.0: unable to enumerate USB device on port 3
[ 3869.114141] usb 1-1.3: new full speed USB device number 18 using s5p-ehci
I used USB Device INFO app and in Linux tab I can see that the printer was correctly mounted on /sys/bus/usb/devices/1-1.3/ but In Android there is no device detected.
Any idea on how can I try to make this work?
Thanks for any help
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!!