Hi.
Using Servers Ultimate to start a new NFS server on my Android device - Z ultra rooted.
I have firewall turned off both on the server and client.
First I replaced the "linker" file due to google disabling of pie
error: only position independent executables (PIE) are supported.
NFS server is able to being executed now.
192.168.1.84 = server
192.168.1.90 = client
When active I can see my client in the Server ultimate log on the android when searching the network with yast: 192.168.1.90 - New request...
But the server (android phone) says, this version (3) not handled: min=2 max=2...**
What does this mean?
I have NFS server working on Windows 7 and FreeNAS and client working on Suse so this issue is isolated to android. Not my network or my client.
Having the option to choose and setup NFS servers in the Servers ultimate app must mean its possible to use NFS on android?
Servers ultimate log:
2015-10-24 05:31:29 [testing] - Port map handler: PMAP_CALLIT called...
2015-10-24 05:31:29 [testing] - 192.168.1.90 - New request...
**2015-10-24 05:31:28 [testing] - this version (3) not handled: min=2 max=2...**
2015-10-24 05:31:28 [testing] - 192.168.1.90 - New request...
2015-10-24 05:31:24 [testing] - Port map handler: PMAP_CALLIT called...
2015-10-24 05:31:24 [testing] - 192.168.1.90 - New request...
**2015-10-24 05:31:24 [testing] - this version (3) not handled: min=2 max=2...**
2015-10-24 05:31:24 [testing] - 192.168.1.90 - New request...
2015-10-24 05:31:03 [testing] - Listening for connections...
2015-10-24 05:31:03 [testing] - Registering prog 100005 vers 1 prot 17 port 2049...
2015-10-24 05:31:03 [testing] - Registering prog 100003 vers 2 prot 17 port 2049...
2015-10-24 05:31:00 [testing] - Registering prog 100000 vers 2 prot 17 port 1111...
2015-10-24 05:31:00 [testing] - Port mapper started...
2015-10-24 05:31:00 [testing] - Forwarding ports done. Exit code: 0 - Returned: ""
2015-10-24 05:31:00 [testing] - Applying forwarding rules (root, 111)...
2015-10-24 05:31:00 [testing] - Preparing.
2015-10-24 05:31:00 [testing] - Server started
2015-10-24 05:31:00 [testing] - Starting server
2015-10-24 05:31:00 [testing] - Request has been send to servers pack
Limitation of the Android software
I found that on my Ubuntu desktop, I could only user version 2 of the NFS protocol with Servers Ultimate.
If it helps, the command I've used is:
sudo mount -o soft,intr,rsize=32768,wsize=32768,vers=2 192.168.2.55:/mnt/usb_storage/USB_DISK0/250gb/ /data/stuff/NFS
However, the rsize and wsize are arbitrary at the moment since version 2 of NFS has a maximum of 8192\
Anyway, hope that helps!
Related
Hello, there.
I installed void #e a while ago on my O1, everything went smoothly until I had to setup a VPN with L2TP/IPsec.
After poking around with adb logcat, I found that the bundled kernel (mik_os's one) missed support for NETKEY sockets, IPSec over IPv4 and PPP altogether, so I rebuilt the kernel from source adding all missing options to .config.
I flashed the new kernel, boot it and tried to start the VPN, but it failed again.
This time - however - racoon was able to set up an IPsec security association with the remote host, but pppd complained about missing PPP support in kernel:
Code:
I/racoon ( 4330): ISAKMP-SA established <scrubbed>[500]-<scrubbed>[500] spi:<scrubbed>
I/racoon ( 4330): initiate new phase 2 negotiation: <scrubbed>[500]<=><scrubbed>[500]
I/racoon ( 4330): IPsec-SA established: ESP/Transport <scrubbed>[0]-><scrubbed>[0] spi=<scrubbed>(0x<scrubbed>)
I/racoon ( 4330): IPsec-SA established: ESP/Transport <scrubbed>[500]-><scrubbed>[500] spi=<scrubbed>(0x<scrubbed>)
I/mtpd ( 4532): Tunnel established
D/mtpd ( 4532): Received ICRP (remote_session = 65060) -> Sending ICCN
D/mtpd ( 4532): Received ACK
I/mtpd ( 4532): Session established
I/mtpd ( 4532): Creating PPPoX socket
I/mtpd ( 4532): Starting pppd (pppox = 13)
I/mtpd ( 4532): Pppd started (pid = 4533)
I/pppd ( 4533): Using PPPoX (socket = 13)
E/pppd ( 4533): This system lacks kernel support for PPP. This could be because
E/pppd ( 4533): the PPP kernel module could not be loaded, or because PPP was not
E/pppd ( 4533): included in the kernel configuration. If PPP was included as a
E/pppd ( 4533): module, try `/sbin/modprobe -v ppp'. If that fails, check that
E/pppd ( 4533): ppp.o exists in /lib/modules/`uname -r`/net.
E/pppd ( 4533): See README.linux file in the ppp distribution for more details.
I/mtpd ( 4532): Received signal 17
I/mtpd ( 4532): Pppd is terminated (status = 4)
D/mtpd ( 4532): Sending STOPCCN
I/mtpd ( 4532): Mtpd is terminated (status = 36)
I double-checked /proc/conf.gz and sure enough it contains all ppp options:
Code:
# zcat /proc/config.gz | grep PPP
CONFIG_PPP=y
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=y
CONFIG_PPP_SYNC_TTY=y
CONFIG_PPP_DEFLATE=y
CONFIG_PPP_BSDCOMP=y
CONFIG_PPP_MPPE=y
CONFIG_PPPOE=y
CONFIG_PPPOL2TP=y
CONFIG_PPPOLAC=y
CONFIG_PPPOPNS=y
I noticed in mik_os's sources that LG also set CONFIG_ANDROID_PARANOID_NETWORK to y, while in mik_os's build it is set to n.
Does anyone know if they are related and/or if I'm running into another issue (permissions, maybe)?
Thanks in advance
Sure enough, it was CONFIG_ANDROID_PARANOID_NETWORK.
For future reference, if this option is undefined AID_NET_ADMIN and AID_NET_RAW have no special meaning for the kernel (iow, CAP_NET_ADMIN and CAP_NET_RAW are not granted to non-root processes belonging to those special groups).
Moreover, network access restrictions are completely ignored, so any application can create sockets and/or access the bluetooth stack even if its manifest does not specify the relevant permissions.
Hi all !
I see that project :
http://code.google.com/p/android-vnc-server/
I wan't to compile it on my PC for including the vnc server into my furture APK.
I have compiled it but the vnc client have a real bad image (See attachment)
There is the logs :
Code:
/ # androidvncserver
Initializing framebuffer device /dev/graphics/fb0...
xres=480, yres=800, xresv=480, yresv=1600, xoffs=0, yoffs=0, bpp=32
Initializing keyboard device /dev/input/event3 ...
Initializing touch device /dev/input/event1 ...
Initializing VNC server:
width: 480
height: 800
bpp: 32
port: 5901
Initializing server...
28/09/2011 14:13:44 Listening for VNC connections on TCP port 5901
# I just connect with an VNC Client
28/09/2011 14:14:13 Got connection from client 192.168.70.138
28/09/2011 14:14:13 other clients:
28/09/2011 14:14:13 Client Protocol Version 3.8
28/09/2011 14:14:13 Protocol version sent 3.8, using 3.8
Dirty page: 480x800+0+0...
28/09/2011 14:14:13 rfbProcessClientSecurityType: executing handler for type 1
28/09/2011 14:14:13 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8
28/09/2011 14:14:13 Pixel format for client 192.168.70.138:
28/09/2011 14:14:13 8 bpp, depth 6
28/09/2011 14:14:13 true colour: max r 3 g 3 b 3, shift r 4 g 2 b 0
28/09/2011 14:14:13 Enabling full-color cursor updates for client 192.168.70.138
28/09/2011 14:14:13 Enabling NewFBSize protocol extension for client 192.168.70.138
28/09/2011 14:14:13 Using ZRLE encoding for client 192.168.70.138
28/09/2011 14:14:14 Pixel format for client 192.168.70.138:
28/09/2011 14:14:14 32 bpp, depth 24, little endian
28/09/2011 14:14:14 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
28/09/2011 14:14:14 Enabling full-color cursor updates for client 192.168.70.138
28/09/2011 14:14:14 Enabling NewFBSize protocol extension for client 192.168.70.138
28/09/2011 14:14:14 Switching from ZRLE to hextile Encoding for client 192.168.70.138
# I disconnect the VNC Client.
28/09/2011 14:14:51 Client 192.168.70.138 gone
28/09/2011 14:14:51 Statistics events Transmit/ RawEquiv ( saved)
28/09/2011 14:14:51 FramebufferUpdate : 2 | 0/ 0 ( 0.0%)
28/09/2011 14:14:51 hextile : 1 | 1351415/ 1536012 ( 12.0%)
28/09/2011 14:14:51 ZRLE : 1 | 15792/ 384000 ( 95.9%)
28/09/2011 14:14:51 RichCursor : 2 | 342/ 342 ( 0.0%)
28/09/2011 14:14:51 TOTALS : 6 | 1367549/ 1920354 ( 28.8%)
28/09/2011 14:14:51 Statistics events Received/ RawEquiv ( saved)
28/09/2011 14:14:51 ClientCutText : 1 | 32/ 32 ( 0.0%)
28/09/2011 14:14:51 PointerEvent : 285 | 1710/ 1710 ( 0.0%)
28/09/2011 14:14:51 FramebufferUpdate : 3 | 30/ 30 ( 0.0%)
28/09/2011 14:14:51 SetEncodings : 2 | 64/ 64 ( 0.0%)
28/09/2011 14:14:51 SetPixelFormat : 2 | 40/ 40 ( 0.0%)
28/09/2011 14:14:51 TOTALS : 293 | 1876/ 1876 ( 0.0%)
Do you know why my screen is "green" and "entralaced" ?
With other binarie of vncserver in android, with the same client, the image is good.
Thanks for help !
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Hi all,
I'm trying to get OpenVPN running on my Galaxy S2. I installed the OpenVPN Installer and OpenVPN Settings from Market (OpenVPN 2.1.1), and I am starting with an OpenVPN config file that I know works (it's a working config that I use on my XUbuntu system):
client
dev tun
proto udp
remote somehost.somedomain.com 1194
ifconfig 192.168.21.10 255.255.255.0
redirect-gateway def1
nobind
ca ca.crt
cert my.crt
key my.key
verb 3
mute 10
The first thing is that the "ifconfig" doesn't seem to be accepted:
Options error: Unrecognized option or missing parameter(s) in config.ovpn:5: ifconfig (2.1.1)
If I comment this out, I get:
Fri Dec 30 21:32:07 2011 NOTE: unable to redirect default gateway -- VPN gateway parameter (--route-gateway or --ifconfig) is missing
However, I ALSO do not see any "ifconfig" calls in the openvpn log this way, which makes me thing that OpenVPN isn't actually setting up the tunnel, which probably explains the later errors (see below).
If I add a "route-gateway 192.168.21.5", (that's the def gateway that my Xubuntu system ends up with when i start this VPN connection) I get:
Fri Dec 30 21:34:27 2011 /system/xbin/route add -net 0.0.0.0 netmask 128.0.0.0 gw 192.168.21.5
route: SIOCADDRT: No such process
Fri Dec 30 21:34:27 2011 ERROR: Linux route add command failed: external program exited with error status: 1
Fri Dec 30 21:34:27 2011 /system/xbin/route add -net 128.0.0.0 netmask 128.0.0.0 gw 192.168.21.5
route: SIOCADDRT: No such process
Fri Dec 30 21:34:27 2011 ERROR: Linux route add command failed: external program exited with error status: 1
On my Xubuntu system I don't actually need to add any "route-gateway", as I think the OpenVPN version there (2.2.0) understands the "redirect-gateway" directive, while I don't think that OpenVPN 2.1.1 understands that yet.
Can anybody recommend correct settings so I can make this work?
Regards
[edit] Oh, nice. I flashed an insecure ROM to my phone, then used the "openvpn-static.bz2" binary from this location (copied to /system/xbin/openvpn), and now it works.
Hello guys this is my first HOW to so please be a lil bit patient.
Questions and comments are welcomed of course!
Because I sent my SGS 2 for repair I took my older blackberry from my box with old garbage and tried to think about internet connection.
BB doesn't have wifi hotspot or something like this so how can we dial up internet connection from android?
Here we go.
Some stuff which must be installed before procedure:
1) ROOTed device
2) Busybox installed
3) Linux in loop device - maybe this is not needed but I am lazy ass and this was the fastest solution.
Procedure:
First of all we need to determine what is your bluetooth address (blackberry in my case).
For this one you have two options.
1) Determine it on your PC (I don't have windows so I will describe linux method only)
Turn bluetooth on your PC on.
Turn bluetooth on your cellphone and enable device discovery (device needs to be visible!!)
Open terminal and write:
Code:
hcitool scan
You will get something like this: " f4:0b:93:08:a0:16 "
Write it down you will need it for later use.
2) How to determin a bluetooth address on android
Because standart busybox and asus rom don't have hcitool we will need to use it from Linux environment (from loop device).
So if you haven't installed linux distro in loop file do it! It's up to you which one you preffere. I made following steps in ubuntu 12.04.
After installing ubuntu to the loop device start it and write from command line:
Code:
sudo apt-get update && sudo apt-get install bluetooth
Ok now we have tools for bluetooth installed.
Now turn on bluetooth on your android, turn on bluetooth on cellphone (discovery enabled).
chroot into your linux in loop and write:
Code:
hcitool scan
Write down your address like in the example above.
Now we need to determine which number of channel is dialup networking
This command is included in android terminal with busybox so you don't have to write it in the loop linux distro.
So write in the terminal like SU:
Code:
sdptool browse f4:0b:93:08:a0:16 <--- here is YOUR address of bluetooth cellphone
You will get something like this:
Code:
Browsing F4:0B:93:08:A0:16 ...
Service Name: Dialup Networking
Service RecHandle: 0x10000
Service Class ID List:
"Dialup Networking" (0x1103)
"Generic Networking" (0x1201)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100
Service Name: Voice gateway
Service RecHandle: 0x10001
Service Class ID List:
"Headset Audio Gateway" (0x1112)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 2
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Headset" (0x1108)
Version: 0x0100
Service Name: Hands-free
Service RecHandle: 0x10002
Service Class ID List:
"Handsfree Audio Gateway" (0x111f)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 3
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Handsfree" (0x111e)
Version: 0x0105
Service Name: Advanced Audio
Service Provider: BlackBerry
Service RecHandle: 0x10003
Service Class ID List:
"Audio Source" (0x110a)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 25
"AVDTP" (0x0019)
uint16: 0x102
Profile Descriptor List:
"Advanced Audio" (0x110d)
Version: 0x0102
Service Name: AVRCP Remote Control
Service Provider: BlackBerry
Service RecHandle: 0x10004
Service Class ID List:
"AV Remote" (0x110e)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 23
"AVCTP" (0x0017)
uint16: 0x102
Profile Descriptor List:
"AV Remote" (0x110e)
Version: 0x0103
Service Name: AVRCP Remote Control Target
Service Provider: BlackBerry
Service RecHandle: 0x10005
Service Class ID List:
"AV Remote Target" (0x110c)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 23
"AVCTP" (0x0017)
uint16: 0x102
Profile Descriptor List:
"AV Remote" (0x110e)
Version: 0x0103
Service Name: SIM Access
Service RecHandle: 0x10006
Service Class ID List:
"SIM Access" (0x112d)
"Generic Telephony" (0x1204)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 4
Profile Descriptor List:
"SIM Access" (0x112d)
Version: 0x0102
Service Name: Phonebook Access PSE
Service RecHandle: 0x10007
Service Class ID List:
"Phonebook Access - PSE" (0x112f)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 5
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Phonebook Access" (0x1130)
Version: 0x0100
#
In the example above we need to find dialup networking (you can grep it of course but the name can be a little different).
When you locate in your output this sevice (once again Dialup networking), look for channel.
In my case channel is 1.
Code:
Service Name: Dialup Networking
Service RecHandle: 0x10000
Service Class ID List:
"Dialup Networking" (0x1103)
"Generic Networking" (0x1201)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Write the channel number down.
Now you have your address and we won't need linux distro anymore (in this case )
Now run android terminal and write:
Code:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
This will remount system for read and write.
Now download latest package of berry from this address:
https://bitbucket.org/tcolar/berry4all/downloads
and save it unpacked to somewhere on sdcard.
These configurations file are for blackberry but with some modifications it can work for another cellphones !!!!!!!!!
We will use configuration files in the folder config.
I am from Czech republic and I use T-Mobile.
It unfortunately means that I didn't have right dial configuration file in the config folder. So I took tmobile and tmobile-bb-chat and rename it to tmobilecz and tmobilecz-chat. After that I created folder on the sdcard called chatscripts and moved tmobilecz-chat there.
File tmobilecz needs to be moved to the /etc/ppp/peers.
So here is how to do that from android terminal:
Code:
su
cp /sdcard/download/berry/config/tmobile /etc/ppp/peers/tmobilecz
mkdir /sdcard/chatscripts && cp /sdcard/download/berry/config/tmobile-bb-chat /sdcard/chatscripts/tmobilecz-chat
Here is output of my configs:
Code:
/ $ su
# cat /etc/ppp/peers/tmobilecz
# was tested as working by Me
#460800
115200
/dev/rfcomm1
## No detach = PPP dialing stays in foreground
nodetach
#noipdefault
defaultroute
#nomultilink
#ipcp-restart 7
#ipcp-accept-local
#ipcp-accept-remote
#lcp-echo-interval 0
#lcp-echo-failure 99
#nopcomp
#noaccomp
#noauth
nomagic
#noccp
#crtscts
#pap-timeout 20
#pap-restart 20
#lcp-restart 10
#novj
user "gprs"
password "gprs"
usepeerdns
#debug debug debug
# does not exist in all pppd versions (osx)
#replacedefaultroute
connect "/system/bin/chat -f /sdcard/chatscripts/tmobilecz-chat"
and chat file:
Code:
/ $ cat /sdcard/chatscripts/tmobilecz-chat
TIMEOUT 10
ABORT 'BUSY'
ABORT 'NO ANSWER'
ABORT 'ERROR'
ABORT "NO DIALTONE"
ABORT VOICE
ABORT RINGING
SAY 'Starting GPRS connect script\n'
'' 'BBT_OS'
'' 'ATZ'
OK 'AT+CGDCONT=1,"IP","internet.t-mobile.cz"'
ABORT 'NO CARRIER'
SAY 'Dialing...\n'
OK 'ATD*99#'
CONNECT
~p
/ $
Now we have configs on the place last thing is that we need initiate dun connection between android and phone.
You can imagine it like a tunnel for dialing, so it needs to be established before dialing (pppd daemon).
Now we will use our determined bluetooth address and chanel with rfcomm command.
Android terminal like SU:
Code:
su
rfcomm bind /dev/rfcomm1 f4:0b:93:08:a0:16 1
rfcomm is utility for creating connecting, bind option will create device under /dev/rfcomm1, after bind is bluetooth address and at the end is 1 this is number of channel.
THIS COMMAND NEEDS TO BE RUN AFTER EACH REBOOT when you want to dial internet from your phone.
During this commnd you can receive request for pairing, do it of course.
After this command run as root pppd daemon with your config file, in my case named tmobilecz:
Code:
su
pppd call tmobilecz
If you have nodetach option in the peers config file like me, dial process stays in the foreground. You can close it by ctrl+c or closing terminal window.
After pppd you should receive ip address by the phone and connectio to the internet!!
WOALA!
If it is not working or you want to check what is going on during dialing install application ALOGCAT from market and filter messages with pppd only.
If you have difficulties write it down and I will try to help you.
After this setup everytime when you want connect to the internet through phone you have to write this in terminal (i created script for myself but it's up to you)
EXAMPLE:
android terminal:
Code:
su
rfcomm bind /dev/rfcomm1 f4:0b:93:08:a0:16 1
pppd file /etc/ppp/peers/tmobilecz
That's all!
When I have a time I will better format and color this post.
Now I have to cut my grass in the garden sorry
placeholder for future use
deadlocked007 said:
You do know you could've just used pdanet tablet
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
Code:
This software allows you to get FULL Internet on an Android tablet if you have an Android phone.
I don't have android phone so answer is no it can't be used.
Hi, I am having issues with a Huawei modem E173u-1 on my tablet Archos 101 g9 8gb
driver not found.
Can you help me, pls?
USB_ModeSwitch log from Wed Apr 09 17:50:44 PKT 2014
Raw args from udev: 1-1/1-1:1.0
Using top device dir /sys/bus/usb/devices/1-1
----------------
USB values from sysfs:
manufacturer HUAWEI
product HUAWEI Mobile
serial
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/12d1.14fe
! matched. Reading config data
devList 1:
config: TargetVendor set to 12d1
config: TargetProduct set to 1506
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Logger is: /system/bin/log
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 2 -v 12d1 -p 14fe -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= 0x12d1
DefaultProduct= 0x14fe
TargetVendor= 0x12d1
TargetProduct= 0x1506
TargetClass= not set
TargetProductList=""
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="55534243123456780000000000000011062000000100000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 001/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 12d1:14fe
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 0x01 (out) and 0x81 (in)
USB description data (for identification)
-------------------------
Manufacturer: HUAWEI
Product: HUAWEI Mobile
Serial No.: not provided
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Could not reset endpoint (probably harmless): -34
Resetting message endpoint 0x01
Could not reset endpoint (probably harmless): -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.) ...
Waiting for device file system (3 sec.) ...
Waiting for device file system (4 sec.) ...
Waiting for device file system (5 sec.) ...
Waiting for device file system (6 sec.) ...
Waiting for device file system (7 sec.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 12d1:1506 (HUAWEI: HUAWEI Mobile)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0 yet
Module loader is /sbin/insmod
Trying to find and install main driver module "option"
Trying to find module "option"
Loading support module /lib/modules/usb_wwan.ko
Error: insmod: cannot insert '/lib/modules/usb_wwan.ko': Invalid module format (-1): Exec
format error
Loading main driver module "option"
Error: insmod: cannot insert '/lib/modules/option.ko': Invalid module format (-1): Exec
format error
Falling back to "usbserial"
Module "usb_serial" not found, can't do more here
Driver binding seems to have failed
All done, exiting
please answer!!!
i'm solved the problem by replacing the nucleus