Hello everybody,
I want to connect my iconia A700 with wired network. So i plugged in my usb network adapter.
And this is what dmesg has showed
<6>[46753.465362] tegra-ehci tegra-ehci.0: new USB bus registered, assigned bus number 1
<6>[46753.491903] tegra-ehci tegra-ehci.0: irq 52, io mem 0x7d000000
<6>[46753.514954] tegra-ehci tegra-ehci.0: USB 2.0 started, EHCI 1.00
<6>[46753.516316] utmi_phy_irq: usb device plugged-in
<6>[46753.517581] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[46753.518916] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[46753.519656] usb usb1: Product: Tegra EHCI Host Controller
<6>[46753.521311] usb usb1: Manufacturer: Linux 3.1.10+ ehci_hcd
<6>[46753.522243] usb usb1: SerialNumber: tegra-ehci.0
<6>[46753.532426] hub 1-0:1.0: USB hub found
<6>[46753.533294] hub 1-0:1.0: 1 port detected
<6>[46753.855044] usb 1-1: new full speed USB device number 2 using tegra-ehci
<6>[46753.940886] usb 1-1: New USB device found, idVendor=0bda, idProduct=8150
<6>[46753.942477] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[46753.943250] usb 1-1: Product: USB 10/100 LAN
<6>[46753.944526] usb 1-1: Manufacturer: REALTEK
<6>[46753.945240] usb 1-1: SerialNumber: 0219
Click to expand...
Click to collapse
is there a possible solution for my problem? Or has anyone a working driver?
1) This should go in general.
2) You can try loading the attached module using insmod or modprobe.
pawitp said:
1) This should go in general.
2) You can try loading the attached module using insmod or modprobe.
Click to expand...
Click to collapse
Is there also a driver for the Delock 61147 (MOdule need is mcs7830.ko)?
elhennig said:
Is there also a driver for the Delock 61147 (MOdule need is mcs7830.ko)?
Click to expand...
Click to collapse
All compiled from Acer's released kernel source. (Note: don't use these on CyanogenMod, the drivers are already built into the kernel)
asix.ko
cdc_eem.ko
cx82310_eth.ko
dm9601.ko
gl620a.ko
hso.ko
int51x1.ko
ipheth.ko
kalmia.ko
lg-vl600.ko
mcs7830.ko
net1080.ko
plusb.ko
sierra_net.ko
smsc75xx.ko
zaurus.ko
Pawitp, while you're at it, maybe you can compile md4.ko? In your CM10 rom, no md4.ko - cifs manager doesn't work without it on stock rom...
zeer said:
Pawitp, while you're at it, maybe you can compile md4.ko? In your CM10 rom, no md4.ko - cifs manager doesn't work without it on stock rom...
Click to expand...
Click to collapse
MD4 has been built into the CM kernel for maximum compatibility. Anyway, here's the md4.ko if you want to use stock.
Hi pawit, thanks a lot for the module pack.
One question comes up as the module loads perfectly: How can I route traffic like for the standard mail client through eth0 device? The mail client and the play store app seem to need a wlan device
I don't know. The standard android is supposed to recognize eth0 as a valid internet connection and route automatically. CM does, I'm not sure how Acer configured it.
Sent from my GT-I9000 using xda app-developers app
how does one implement this into stock?
Please, could someone help me!
Iam on Icianian 2.4 and try to get the dm9601.ko work!
But every time, i load the kernel module, the tap froze!
any idea?
Could the kernel module wrong?
PLEASE help me
djsven said:
Please, could someone help me!
Iam on Icianian 2.4 and try to get the dm9601.ko work!
But every time, i load the kernel module, the tap froze!
any idea?
Could the kernel module wrong?
PLEASE help me
Click to expand...
Click to collapse
I'm working on this for iconiaN
It's going to require more than just kernel modules to work
Hi,
not realy!
I can tell you, it work!
But you have to plugin, get on terminal and configer the eth0.
netcfg eth0 dhcp
setprop net.dns1 8.8.8.8
and it work
I've got it working now without having to use terminal.
Tested using a Galaxy S Mini USB Tether.
It uses usb0 instead of eth0 but it worked without issues.
I have built the kernel with the network modules built-in and also patched framework files.
Bamm your are the best.This would realy nice.
Please could you build the right mount points inside the kernel?
Think about sdcard.This is /Removeable/xxx
I guess its /mnt/external_usb
Can we point the uab device to eth0?
So Android Firewall would work.
Gesendet von meinem GT-I9100 mit Tapatalk 2
pawitp said:
All compiled from Acer's released kernel source. (Note: don't use these on CyanogenMod, the drivers are already built into the kernel)
asix.ko
cdc_eem.ko
cx82310_eth.ko
dm9601.ko
gl620a.ko
hso.ko
int51x1.ko
ipheth.ko
kalmia.ko
lg-vl600.ko
mcs7830.ko
net1080.ko
plusb.ko
sierra_net.ko
smsc75xx.ko
zaurus.ko
Click to expand...
Click to collapse
Hi, i have A700 with original Acer software. I made it to the "root" description: http://forum.xda-developers.com/showthread.php?t=1953917 , and i ave unlocked bootloader (http://forum.xda-developers.com/showthread.php?t=1710755).
I want to use the tablet Asix AX88772 with, but when they want linked asix.ko was inserted, I get this message:
[email protected]:/system/lib/modules # modprobe asix.ko
modprobe: chdir(/lib/modules): No such file or directory
We could be the problem? Can you help me?
The correct sw version (Settings menu/ About tablet):
Android version: 4.1.1
Kernel version: 3.1.10+
Image version: Acer_AV051_A700_RV16RC02_WW_GEN1
Build number: Acer_AV051_A700_1.050.00_WW_GEN1
Image P/N: FM.S1MA0.0.40
Hi there
I bought one of these sticks hoping to get a Linux distro onto it and try it as a plain PC, but am stymied at step 1. I plain cannot get my PC to enumerate the USB connection!
The actual thing I bought seems to run Android OK.
The PCB is blue/green and has CYX_809III on it with v5_0 20140510 under that. Now when I try a USB connection to my PC I get
Code:
usb 4-2: device descriptor read/64, error -62
usb 4-2: device descriptor read/64, error -62
usb 4-2: device descriptor read/64, error -62
usb 4-2: device descriptor read/64, error -62
usb 4-2: device not accepting address 17, error -62
usb 4-2: device not accepting address 18, error -62
hub 4-0:1.0: unable to enumerate USB device on port 2
And of course lsusb shows nothing new.
I have enabled developer options/USB debugging, I have tried 3 different power supplies, I have tried all 3 USB ports on the stick, I have even tried it into my Raspberry Pi (to sanity check my PC which sees my LG phone fine) and am at a complete loss.
Similarly when I hold the "factory reset" button and plug in a USB cable the stick does a factory image reload (Android picture with rotating thing at stomach) for 3 minutes then reboots - it does not offer any kind of recovery menu.
The only bits from Dr Google I have not tried are shorting pins 8-9 of the NAND (as I cannot find a clear description of what this actually achieves and whether it is relevant to this version) and another post (which I can no longer find, thought it was on XDA but ...) that seemed to have instructions for forcing the USB Vendor and Product IDs somehow ?via modprobe? but apart from the fact I can't find the post I have no idea what the IDs should be.
Any suggestions welcome - TIA
Me and another guy are having the same problem with this device (or actually a CX-919 with the same PCB inside).. We're still looking for a solution.. PM me and I'll send you a link to the thread on another forum.
dukla2000 said:
Hi there
I bought one of these sticks hoping to get a Linux distro onto it and try it as a plain PC, but am stymied at step 1. I plain cannot get my PC to enumerate the USB connection!
The PCB is blue/green and has CYX_809III on it with v5_0 20140510 under that. Now when I try a USB connection to my PC I get
Code:
usb 4-2: device descriptor read/64, error -62
usb 4-2: device descriptor read/64, error -62
usb 4-2: device descriptor read/64, error -62
usb 4-2: device descriptor read/64, error -62
usb 4-2: device not accepting address 17, error -62
usb 4-2: device not accepting address 18, error -62
hub 4-0:1.0: unable to enumerate USB device on port 2
And of course lsusb shows nothing new.
I have enabled developer options/USB debugging, I have tried 3 different power supplies, I have tried all 3 USB ports on the stick, I have even tried it into my Raspberry Pi (to sanity check my PC which sees my LG phone fine) and am at a complete loss.
Similarly when I hold the "factory reset" button and plug in a USB cable the stick does a factory image reload (Android picture with rotating thing at stomach) for 3 minutes then reboots - it does not offer any kind of recovery menu.
The only bits from Dr Google I have not tried are shorting pins 8-9 of the NAND (as I cannot find a clear description of what this actually achieves and whether it is relevant to this version) and another post (which I can no longer find, thought it was on XDA but ...) that seemed to have instructions for forcing the USB Vendor and Product IDs somehow ?via modprobe? but apart from the fact I can't find the post I have no idea what the IDs should be.
Any suggestions welcome - TIA
Click to expand...
Click to collapse
same problems here
Cooler_King said:
Me and another guy are having the same problem with this device (or actually a CX-919 with the same PCB inside).. We're still looking for a solution.. PM me and I'll send you a link to the thread on another forum.
Click to expand...
Click to collapse
same thing here i was just got from ebay member paq999
this is the title i have got
CX919 RK3188 Quad Core Android 4.2 TV BOX 5-in-1 Wireless Control Fly Air Mouse
guess not
I have a Nexus 4 and I have accidentaly damaged the bootloader so I cannot access my device to flash again a bootloader to fix it. When I connect my phone to my PC via USB my phone seems to be alive (see below) but with no functional software.
I would like to know if there is any tool like nvflash (http://forum.xda-developers.com/wiki/Nvflash) to access in a low level way to my storage via Qualcomm APQ8064 Snapdragon S4 Pro chipset. There should be a way to flash a new bootloader via the chipset. How does the manufacturer install the software after having the finished hardware so?
If you know any other kind solution please let me know, too.
Please Help!
Thanks!
$ dmesg | tail
[ 4956.392041] usb 9-4: new high-speed USB device number 11 using xhci_hcd
[ 4956.410551] usb 9-4: New USB device found, idVendor=05c6, idProduct=9008
[ 4956.410555] usb 9-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4956.410558] usb 9-4: Product: QHSUSB_DLOAD
[ 4956.410561] usb 9-4: Manufacturer: Qualcomm CDMA Technologies MSM
[ 4956.410832] qcserial 9-4:1.0: Qualcomm USB modem converter detected
[ 4956.411044] usb 9-4: Qualcomm USB modem converter now attached to ttyUSB0
Hey guys!
I have a rooted Samsung Galaxy S6 G920I.
The problem with this thing is that I had the debug mode disable and I forgot about that.
I started the phone in TWRP and wipe everything to install another OS.
Problem is...Now I can't connect my phone to install the new OS. Windows, Linux or MacOS does not detects the phone.
When I connect my phone to Linux or MacOS it's like I never connected anything. Windows detects the USB connection but says "The last USB device you connected to this computer malfunctioned and Windows does not recognise it.".
In Device Manager appears as "Unknown USB Device (Device Descriptor Request Failed)"
I tried with Samsung USB Drivers, Android SDK, 4 USB different cables, OTG, and nothing.
I see a Terminal in TWRP, so I was wondering if it's possible to enable Debug mode or whatever I need to connect the phone and transfer a new OS.
Thanks in advance!
I had official Android 11 Beta on it (there was the guide how to update it).
Got OTA with Android 11 today.
And now it does not boot - staying on "androidtv" splash screen.
Does anyone have it? How to get to recover or something on it? Any way to perform reset on it or manual update while PC (adb) does not see it.
Reported this issue to google's tracker: https://issuetracker.google.com/issues/169172450
Linux machine sees USB device connected but obviously no ADB at this point:
Code:
[ +8,588816] usb 3-5: new high-speed USB device number 24 using xhci_hcd
[ +0,150146] usb 3-5: New USB device found, idVendor=1b8e, idProduct=c003, bcdDevice= 0.07
[ +0,000002] usb 3-5: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Code:
$ adb kill-server
$ adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
Issue solved: Most probably booting sequence was blocked by USB connection to my linux host machine (yeah, development device is connected to linux machine for development). Unplugging USB (keeping power line from Y-shaped usb cable) make it bootable.