Batteries included
nassus

Re: Driver Modules (for victims of the "No driver found" iss

Post by nassus » 09 Jan 2013, 16:05

OK.. Let's hope that the mighty Samsung will be kind to us and it will provide the necessary information's.
Thanks anyway.

spondbob
Posts: 15
Joined: 13 Dec 2012, 11:06

Re: Driver Modules (for victims of the "No driver found" iss

Post by spondbob » 10 Jan 2013, 05:09

hi Josh, i've a question
how can i have the driver that match my kernel name? because some time i like to try some custom rom n of course i need the driver that match the kernel. can i just compile the driver's source? could u give some step-by-step tutorial to do that, i dont know exactly how to do that but i know some basic of linux
so in anoher time maybe u dont have to provide the driver one by one for each device, whenever people ask the driver for their device just give the steps

astromedia
Posts: 3
Joined: 10 Jan 2013, 20:14

Re: Driver Modules (for victims of the "No driver found" iss

Post by astromedia » 10 Jan 2013, 20:24

Hi,
i have Samsung Galaxy Note II (GT-N7100, Kernel 3.0.31-590308) and vodafone usb internet (K3520-Z) and i would like to use your solution how use this internet trought usb otg. I tryed to install drivers (copied to specified directory) but that works only in half way, i havent driver not found error now but connection still could not be done (connect->connecting->disconnected). Could you help me pls?

usb_modeswitch.log:

USB_ModeSwitch log from Thu Jan 10 18:53:41 CET 2013

Raw args from udev: 2-1/2-1:1.0

Using top device dir /sys/bus/usb/devices/2-1
----------------
USB values from sysfs:
manufacturer Qualcomm, Incorporated
product USB ZTE Storage
serial P671M8VDF_MS
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/19d2.2000
! matched. Reading config data
devList 1:
config: TargetVendor set to 19d2
config: TargetProductList set to 0001,0002,0015,0016,0017,0031,0037,0052,0055,0061,0063,0064,0066,0091,0108,0117,0128,0157,1402,2002,2003
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1

Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 2 -g 2 -v 19d2 -p 2000 -f $cB

Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------

Reading long config from command line

* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.4 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)

! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor= 0x19d2
DefaultProduct= 0x2000
TargetVendor= 0x19d2
TargetProduct= not set
TargetClass= not set
TargetProductList="0001,0002,0015,0016,0017,0031,0037,0052,0055,0061,0063,0064,0066,0091,0108,0117,0128,0157,1402,2002,2003"

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="5553424312345678000000000000061e000000000000000000000000000000"
MessageContent2="5553424312345679000000000000061b000000020000000000000000000000"
MessageContent3="55534243123456702000000080000c85010101180101010101000000000000"
NeedResponse=1
ResponseEndpoint= not set

InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled


Use given bus/device number: 002/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 19d2:2000
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x09 (out) and 0x89 (in)

USB description data (for identification)
-------------------------
Manufacturer: Qualcomm, Incorporated
Product: USB ZTE Storage
Serial No.: P671M8VDF_MS
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x09 for message sending ...
Trying to send message 1 to endpoint 0x09 ...
OK, message successfully sent
Reading the response to message 1 (CSW) ...
OK, response successfully read (13 bytes).
Trying to send message 2 to endpoint 0x09 ...
OK, message successfully sent
Reading the response to message 2 (CSW) ...
Response reading got error -6
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.

ok:busdev
--------------------------------
(end of usb_modeswitch output)

Checking success of mode switch for max. 20 seconds ...
Waiting for device file system (1 sec.) ...
Waiting for device file system (2 sec.) ...
Reading attributes ...
Warning: USB attribute "2-1:1.0/bInterfaceClass" not found
Essential attributes are missing, continue wait ...
Reading attributes ...
Warning: USB attribute "2-1:1.0/bInterfaceClass" not found
Essential attributes are missing, continue wait ...
Reading attributes ...
Warning: USB attribute "2-1:1.0/bInterfaceClass" not found
Essential attributes are missing, continue wait ...
Reading attributes ...
Warning: USB attribute "2-1:1.0/bInterfaceClass" not found
Essential attributes are missing, continue wait ...
Reading attributes ...
Warning: USB attribute "2-1:1.0/bInterfaceClass" not found
Essential attributes are missing, continue wait ...
Reading attributes ...
Warning: USB attribute "2-1:1.0/bInterfaceClass" not found
Essential attributes are missing, continue wait ...
Reading attributes ...
Warning: USB attribute "2-1:1.0/bInterfaceClass" not found
Essential attributes are missing, continue wait ...
Reading attributes ...
Warning: USB attribute "2-1:1.0/bInterfaceClass" not found
Essential attributes are missing, continue wait ...
Reading attributes ...
Warning: USB attribute "2-1:1.0/bInterfaceClass" not found
Essential attributes are missing, continue wait ...
Reading attributes ...
Warning: USB attribute "2-1:1.0/bInterfaceClass" not found
Essential attributes are missing, continue wait ...
Reading attributes ...
Warning: USB attribute "2-1:1.0/bInterfaceClass" not found
Essential attributes are missing, continue wait ...
Reading attributes ...
Warning: USB attribute "2-1:1.0/bInterfaceClass" not found
Essential attributes are missing, continue wait ...
Reading attributes ...
Warning: USB attribute "2-1:1.0/bInterfaceClass" not found
Essential attributes are missing, continue wait ...
Reading attributes ...
Warning: USB attribute "2-1:1.0/bInterfaceClass" not found
Essential attributes are missing, continue wait ...
Reading attributes ...
Warning: USB attribute "2-1:1.0/bInterfaceClass" not found
Essential attributes are missing, continue wait ...
Reading attributes ...
Warning: USB attribute "2-1:1.0/bInterfaceClass" not found
Essential attributes are missing, continue wait ...
Reading attributes ...
Warning: USB attribute "2-1:1.0/bInterfaceClass" not found
Essential attributes are missing, continue wait ...
Reading attributes ...
Warning: USB attribute "2-1:1.0/bInterfaceClass" not found
Essential attributes are missing, continue wait ...

Target config not matching - current values are
2-1:1.0/bInterfaceClass:
bConfigurationValue: 1
bNumConfigurations: 1
busnum: 2
devnum: 3
idProduct: 0055
idVendor: 19d2
manufacturer: Qualcomm, Incorporated
product: ZTE CDMA Technologies MSM
serial:

Mode switching may have failed. Exiting

ppp.log:

Using port ttyACM0 for connection


I hope U have now all information needed :)

PS: sorry for my english, im not from english speaking country

Josh
Site Admin
Posts: 6593
Joined: 03 Nov 2007, 00:30

Re: Driver Modules (for victims of the "No driver found" iss

Post by Josh » 10 Jan 2013, 21:33

The mode switch is working ("Prepare device"), but there seems to be a problem afterwards.
The "bInterfaceClass" attribute must be available; if it's not, then the device is unusable.

Are you sure the ZTE stick gets 500 mA of power from the tablet? Many problems are caused by insufficient power supply.

astromedia
Posts: 3
Joined: 10 Jan 2013, 20:14

Re: Driver Modules (for victims of the "No driver found" iss

Post by astromedia » 10 Jan 2013, 23:56

Im not sure if i know enought ... i could say only this - diod seems to corectly blinking like device is prepairing :) ... anyway it seems there is enought power ... this device could recharge another mobile device via usb otg :)

saltiveri
Posts: 4
Joined: 11 Jan 2013, 00:51

Re: Driver Modules (for victims of the "No driver found" iss

Post by saltiveri » 11 Jan 2013, 01:07

Hello Josh, first thank you for you excellent work.

I have a GT-5110 tablet with Android 4.1.1 kernel 3.0.31-523998 and I'm trying to connect a ZTE MF190 3G usb modem.

I'm using your latest GT-P3110_GT-P5110_3.0.31-523998 driver modules but I'm getting stuck on the No driver found issue.

When I try insmod command:

u0_a45@android:/sdcard/pppwidget/lib # ls
option.ko
ppp_async.ko
usb_wwan.ko
u0_a45@android:/sdcard/pppwidget/lib # insmod usb_wwan.ko
insmod: init_module 'usb_wwan.ko' failed (No such file or directory)

then I use dmesg:
<4>[5839.620574] C1 [ insmod] usb_wwan: Unknown symbol _GLOBAL_OFFSET_TABLE_ (err 0)

Could you please help me?

Thanks in advance!

spondbob
Posts: 15
Joined: 13 Dec 2012, 11:06

Re: Driver Modules (for victims of the "No driver found" iss

Post by spondbob » 11 Jan 2013, 11:28

hi Josh, could u give me some idea about this?
spondbob wrote:hi Josh, i've a question
how can i have the driver that match my kernel name? because some time i like to try some custom rom n of course i need the driver that match the kernel. can i just compile the driver's source? could u give some step-by-step tutorial to do that, i dont know exactly how to do that but i know some basic of linux
so in anoher time maybe u dont have to provide the driver one by one for each device, whenever people ask the driver for their device just give the steps

Josh
Site Admin
Posts: 6593
Joined: 03 Nov 2007, 00:30

Re: Driver Modules (for victims of the "No driver found" iss

Post by Josh » 11 Jan 2013, 20:54

spondbob wrote:could u give some step-by-step tutorial to do that, i dont know exactly how to do that but i know some basic of linux so in anoher time maybe u dont have to provide the driver one by one for each device, whenever people ask the driver for their device just give the steps
Sorry, I don't have enough time to do this. However, there are many tutorials available already elsewhere.
Also, there is a short but precise README in Samsung's kernel packages.

saltiveri
Posts: 4
Joined: 11 Jan 2013, 00:51

Re: Driver Modules (for victims of the "No driver found" iss

Post by saltiveri » 12 Jan 2013, 11:27

Now my problem derived to Port wasn't found. Do you know if MF190 is compatible with PPPwidget?
saltiveri wrote:Hello Josh, first thank you for you excellent work.

I have a GT-5110 tablet with Android 4.1.1 kernel 3.0.31-523998 and I'm trying to connect a ZTE MF190 3G usb modem.

I'm using your latest GT-P3110_GT-P5110_3.0.31-523998 driver modules but I'm getting stuck on the No driver found issue.

When I try insmod command:

u0_a45@android:/sdcard/pppwidget/lib # ls
option.ko
ppp_async.ko
usb_wwan.ko
u0_a45@android:/sdcard/pppwidget/lib # insmod usb_wwan.ko
insmod: init_module 'usb_wwan.ko' failed (No such file or directory)

then I use dmesg:
<4>[5839.620574] C1 [ insmod] usb_wwan: Unknown symbol _GLOBAL_OFFSET_TABLE_ (err 0)

Could you please help me?

Thanks in advance!

Josh
Site Admin
Posts: 6593
Joined: 03 Nov 2007, 00:30

Re: Driver Modules (for victims of the "No driver found" iss

Post by Josh » 14 Jan 2013, 20:11

We don't have the correct kernel configuration for the newer Samsung firmwares at the moment.

Until these are available, there is no way to provide additional modules for the respective firmware versions.

saltiveri
Posts: 4
Joined: 11 Jan 2013, 00:51

Re: Driver Modules (for victims of the "No driver found" iss

Post by saltiveri » 15 Jan 2013, 21:52

Josh wrote:We don't have the correct kernel configuration for the newer Samsung firmwares at the moment.

Until these are available, there is no way to provide additional modules for the respective firmware versions.
Thank you Josh. I hope that you get the correct kernel configuration to continue you excellent work.

sparkyal
Posts: 4
Joined: 10 Jan 2013, 18:54

Re: Driver Modules (for victims of the "No driver found" iss

Post by sparkyal » 16 Jan 2013, 08:37

Hi, I have the Acer A500 and I'm using the ZTE MF 192 USB modem. It was working properly for a .little bit of time, but now I get the "no drover found" issue. I'm not sure why it would be working then decide that the driver is no longer able to be found. Any suggestions?

(I tried to copy the USB log file in here but the post failed 2 times.)

Josh
Site Admin
Posts: 6593
Joined: 03 Nov 2007, 00:30

Re: Driver Modules (for victims of the "No driver found" iss

Post by Josh » 17 Jan 2013, 01:17

This may be caused by a bug in version 1.2.8 - an update will be available shortly on Google Play.

kirilliussa
Posts: 2
Joined: 18 Jan 2013, 16:17

Re: Driver Modules (for victims of the "No driver found" iss

Post by kirilliussa » 18 Jan 2013, 16:28

Good day!I don't know why ppp widget can't find driver on my motorola Xoom 604 -wingray 4.2.1(Kernel 2.6.39.4) for my stick Huawei e1550?Always same driver not found.Best regards.

Josh
Site Admin
Posts: 6593
Joined: 03 Nov 2007, 00:30

Re: Driver Modules (for victims of the "No driver found" iss

Post by Josh » 18 Jan 2013, 20:20

kirilliussa wrote:I don't know why ppp widget can't find driver on my motorola Xoom 604 -wingray 4.2.1(Kernel 2.6.39.4)
I guess the reason is that the driver is just not there ...

Seriously, is there a kernel source release available for this device? It should be.

Post Reply