I just got my xoom back after getting the 4G LTE sim installed and the 3.2.2 version of Honeycomb.
I have rooted it again and restored my apps and data, but am stuck on a lot of things work related since there is no kernel that provides tun.ko and keeps 4g working.
Is there a kernel being built that provides tun and 4g or maybe possibly a Moray type rom that has 4g support? (That would be super sweet).
Dude the only one was in the universal root thread. If you changed kernals I think your stuck till we can get the img.
Sent from my Xoom using xda premium
I used the Universal Xoom Root process available in Development. It gave me back root access and superuser, but the kernel is still stock and lacking write access to the microsd card and tun.ko in the kernel so that IPSEC VPN connections work.
Was just searching around to see if a kernel with 4g support was in the works. Was going to use the Rogue kernel, but there is a post about waiting until it can be updated to handle 4g access.
I will just sit back and monitor the forum for an update.
The Tachi kernel is working for a few people so far. I don't live in a 4G area (VZW says it will be here next month), only work in one so I can't test the LTE yet, though the 3G works fine from my home.
I've identified a few minor annoyances and work arounds as compared to running the kernel (and Moray ROM) prior to 3.2.2 HLK75D as listed in this post:
PengLord said:
Interesting... I installed File Manager HD, enabled Root Explorer (in the settings menu) and it prompted for Root permissions. It works great. The next step in resolving this is going to be remounting the external1 device on boot to enable global write support. As I'm not so well versed in Android architecture to do that, I'll use MicroSD Mounter manually on boot.
The final step to getting this all sorted will be for me to figure out how to mount usbOTG devices, If anybody has experience with that on this kernel with a 4G Xoom, I'd very much appreciate it.
I figured out my problem with usbOTG support... I needed to added the "usbOTG" folder in the "mnt" directory using Root Explorer and then install a mount manager such as USB Mass Storage Watcher OTG
Click to expand...
Click to collapse
This will get you set up with R/W support for the external1 folder and usbOTG, VPN support may be in there as well since the kernel supports it, I however haven't tried it nor have I read about it being tested as functional on the HLK75D build.
Sadly solarnz announced he will not be working on a 4G Tiamat ROM due to life getting in the way, this means we will likely need to wait until another dev gets caught up or until ICS gets released to us by Motorola (fingers crossed for next month) before it gets any easier.
EtchG said:
I used the Universal Xoom Root process available in Development. It gave me back root access and superuser, but the kernel is still stock and lacking write access to the microsd card and tun.ko in the kernel so that IPSEC VPN connections work.
Was just searching around to see if a kernel with 4g support was in the works. Was going to use the Rogue kernel, but there is a post about waiting until it can be updated to handle 4g access.
I will just sit back and monitor the forum for an update.
Click to expand...
Click to collapse
See the arcturus kernel thread over on xoomforums... there is now an open beta for a postupgrade kernel if you want to try it
Hi Etchg,
I had a similar issue. I sent my Xoom in for the 4g update. When it came back I rooted it. Trying to vpn into work (ipsec) I found that my new kernel 2.6.36.3-g6963abe has no tun.ko file. I found some instructions online and compiled one myself. Attached is my tun.ko (You will need to unzip and put in the systems/lib/modules directory. If your kernel is exactly the same as mine then it should work. BTW, with the new tun, I have successfully VPN'd into my work.
-Jared
I just came back to this thread and saw the tun.zip you uploaded. I tried to open it, but it tells me it is corrupt.
Can you either upload it again or use dropbox and send me the link?
I was able to extract the module and load it on my Xoom. I have the same kernel, but I keep getting an authorization error when I try to connect. Darnit all to heck!
I fixed the authentication issue I was having. Thanks for the module...works like a charm.
Thanks for compiling the tun.ko. It works correctly with Cisco AnyConnect for Rooted Devices.
Glad to help
Hi Guys,
Been absent for the week. Glad to hear that you got it downloaded and working!
-Jared
This always comes back as corrupt for me. I've tried everything I can think of, but I can't extract the tun.ko out of the zip. I haven't been able to create my own either, so I'd really appreciate someone posting this.
Related
This post is now irrelevant, Alex put these commands into the main program. See second post for links.
I figured out how to get it fully working. Big thank you to tonyb486 and canteenboy for figuring out that you need to disable adb and usb mass storage for tethering to work. That only left the problem of disk mounting not working after you are tethering. Here are two scripts to get the whole thing running smoothly and without a problem.
First, if you haven't already, install android-wired-tether. Next install GScript Lite (on the Market) which will let us automate toggling the USB function switch.
Create a new script with SU enabled and use this as the code.
Code:
echo 0 > /sys/devices/platform/msm_hsusb/usb_function_switch
That command shuts off usb_mass_storage and adb so everything is disabled and ready for Wired Tether to come in and do its job. Your usb_function_switch will look like this after running the command.
usb_mass_storage:disable
adb:disable
diag:disable
serial:disable
ether:disable
modem:disable
nmea:disable
When you are done tethering, use this command to re-enable adb and usb_mass_storage:
Code:
echo 3 > /sys/devices/platform/msm_hsusb/usb_function_switch
If for some reason you don't use USB debugging (adb), you can use this command to turn on usb_mass_storage by itself.
Code:
echo 1 > /sys/devices/platform/msm_hsusb/usb_function_switch
For those of you new to GScript, you can place shortcuts to scripts on your home screen. To simplify my life, I put them in a folder with Wired Tether so I have everything in one place. It's not an elegant solution, but you won't need to reboot your phone to get SD card mounting to work again. Perhaps someone with more knowledge of GScript can write some code that will automate running the first script, starting Wired Tether, and then running the last script after it notices that tethering has stopped. (Or better yet, get these commands into the actual program itself.)
(Optional)
For completeness, if you use any of the other usb functions listed above, you can use other 'echo #' commands to find the right combination. They don't toggle individual settings, but rather represent entire combinations of settings. I think around 32-33 it cycles back to 0 (everything off), I didn't have time to figure out if there is a pattern. You can find out what each number does by using another script to read out the switches.
Code:
cat /sys/devices/platform/msm_hsusb/usb_function_switch
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Thanks! I'd like to add that the scripts and the patched app are both working great on my Incredible.
O Whoa, Wired Tether works on my stock Eris now Thank You
Saturn2K said:
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Click to expand...
Click to collapse
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
jerdog said:
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
Click to expand...
Click to collapse
Same. I was going to try the app on the Eris because the same manual fix works :\
jerdog said:
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
Click to expand...
Click to collapse
yeah me too cant find it
Wow, I thought nobody gave a **** about this. Here it is, all compiled and ready to go.
Thanks duder, works like a charm...
Sent from my phone.
THANKS!!!!
Has anyone figured out how to get this to work on Froyo? I get a kernel unsupported error when trying to run it.
dalstrs said:
Has anyone figured out how to get this to work on Froyo? I get a kernel unsupported error when trying to run it.
Click to expand...
Click to collapse
Same here, I'm using netarchy's 4.0.3a kernel and SteelH's stock Froyo RevE.1 ROM.
I have stock froyo on my evo and use easythether, it works perfect, all you have to do is set it to debug mode in the settings, install the app on your computer and when connected set it to charge only.
Sent from my Evo using XDA App
striker012 said:
I have stock froyo on my evo and use easythether, it works perfect, all you have to do is set it to debug mode in the settings, install the app on your computer and when connected set it to charge only.
Sent from my Evo using XDA App
Click to expand...
Click to collapse
The problem with that is having to install stuff on the computer. With wired tether you don't have to install anything on the computer.
XevoX said:
Same here, I'm using netarchy's 4.0.3a kernel and SteelH's stock Froyo RevE.1 ROM.
Click to expand...
Click to collapse
I'm running the same kernel on evio rom and it's working fine for me...
Sent from my phone.
I've been able to make this work on my stock kernel, rooted FroYo Evo, so this is indeed possible and I've narrowed it down to what is necessary. Please star/follow issue 23 in the Google Code tracker for updates.
Unsupported Kernel message...
Hello, all. I'm running Fresh Evo 3.1.0.1 and King's latest kernel and I get the unsupported kernel message. When I try to ignore as is suggested in post 24 on the Google code page for the wired tether, I get a FC once I click to start tethering. Any ideas? Thanks in advance. -E
Hello, all. I'm running Fresh Evo 3.1.0.1 and King's latest kernel and I get the unsupported kernel message. When I try to ignore as is suggested in post 24 on the Google code page for the wired tether, I get a FC once I click to start tethering. Any ideas? Thanks in advance. -E
Click to expand...
Click to collapse
Hi EindhovenOne, I responded to you on the issue tracker for Wired Tether, but I'll respond here just for some others to know the situation.
I found a fix that worked for me on my stock, rooted FroYo Evo and I coded the change and sent Harald a patch. He incorporated the patch and did the build for Wired Tether for me to test, which I have done (and it does indeed work for me, but does currently have the unsupported kernel dialog*). At the same time, though, it is listed in the downloads (you have to select all and then search), but this is in beta state for the changes (hence the deprecated tag I believe).
* I have fixed the unsupported kernel message and sent Harald a patch on this as well, so when he finds time to build it, that should be corrected, too.
So back to the "it's not working" portion, since I'm not running anything but stock (ROM and kernel), my system won't be the same as everyone's. I have no problem with other variations of ROMs and kernels (Evo's and non-Evo's) trying the 1.3 APK, giving feedback, and I'll try to do what I can (and someone else can step in if more suited than me even).
If you do run into issues, you can tag them in the issue tracker, which I try to follow frequently right now. Also, most importantly, if you can provide as much information as possible (what ROM and kernel you're using, a LogCat run just after the error occurs, any other pertinent information we can use to diagnose the problem, etc.), that helps tremendously in tracking down the problem and identifying a fix.
Saturn2K said:
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Click to expand...
Click to collapse
Is there a way we can find this patched version of android-tether? It is no longer attached to the first post. Also, the version I download from google still says incompatible kernel. It would be awesome to get wired tether working for the EVO
superevilllama said:
Is there a way we can find this patched version of android-tether? It is no longer attached to the first post. Also, the version I download from google still says incompatible kernel. It would be awesome to get wired tether working for the EVO
Click to expand...
Click to collapse
The beta-in-progress version 1.3 is located here. It still warns about the kernel currently but you can ignore it (simple lapse in patching that as well at the time). It works perfectly for me (starting and stopping), but there are a couple of issues outstanding right now that I'm working through with the users.
If you do run into a problem, though, just let me/us know through the issue tracker preferably, but you can also contact me directly (here, or my email via the issue tracker).
PS: I have patched the kernel message already, but I don't have write access to the project yet and I don't have the build system in place to handle the native code just yet, so I have been handing builds off to Harald who graciously has done the 1.3 so far for me. When he has time to do the one including the kernel warning fix, I'll post again with an update on that.
I am thinking of picking up one of these, but I would need to be able to connect to an ad-hoc wifi network. does anyone know if this is possible? Also if anyone can tell me how much faster it appears to run after the stock overlay is removed I would appreciate it. Thanks all
matthewallen72 said:
I am thinking of picking up one of these, but I would need to be able to connect to an ad-hoc wifi network. does anyone know if this is possible? Also if anyone can tell me how much faster it appears to run after the stock overlay is removed I would appreciate it. Thanks all
Click to expand...
Click to collapse
As far as Ad Hoc, yes it can be done. Worked for me when I still had mine. Connected to the wifi from my Droid 1. You have to hack the wifi file a bit but its not hard.
can you tell me what you did to the wifi file? are you using wireless tether on the droid? thanks
this worked for me
http://forum.xda-developers.com/showthread.php?t=754961
this one worked for me
kitzuki said:
http://forum.xda-developers.com/showthread.php?t=754961
this one worked for me
Click to expand...
Click to collapse
Can you just rename the zip as update and run through the stock recovery?
The newer TnT Lite and VEGAn mods have this binary, already.
As for how much faster, not a lot versus adding a Tegra performance pack. If you want speed, you want the performance pack or run one of the mods above (especially VEGAn).
I want to keep it stock until after the next update. I just want to see how it works stock. Testing to see if this will be a good device for my father he isn't going to be flashing ROMS so I want to see what I can do with a stock ROM.
How do I get the Ad Hoc working with Stock ROM?
jasco13 said:
How do I get the Ad Hoc working with Stock ROM?
Click to expand...
Click to collapse
The Adhoc fix is in the wpa_supplicant file. You'll need to replace the stock version of that file from the version in the latest vegan or TnTlite build.
I'm not sure if you can simply connect to computer via USB, find the file, and replace it (I doubt it).
Perhaps you can create a recovery update that only replaces that one file. I don't know if it works, but you could try starting with a Vegan or Tnt build, keep the recovery folder, and delete everything in the update.zip except for the wpa_supplicant file.
Hello!
I'm very new to the android os and owner of an infuse (android 2.2.1, kernel version: 2.6.32.9, froyo.uckd5) since a couple of weeks.
Honestly I feel a bit lost because I'm looking for a tun.ko module for this device and as far as I can see there isn't, at least for the production rom. All the tun.ko I found are compiled for kernel different from mine.
I really need openvpn and now I'm wondering if I should:
1) keep looking
2) figure out how to compile a tun.ko on my linux machine for the arm7 architecture
3) look at some modified rom with the module built in
Do you have any suggestion?
Thank you
Cheers
dventurin said:
Hello!
I'm very new to the android os and owner of an infuse (android 2.2.1, kernel version: 2.6.32.9, froyo.uckd5) since a couple of weeks.
Honestly I feel a bit lost because I'm looking for a tun.ko module for this device and as far as I can see there isn't, at least for the production rom. All the tun.ko I found are compiled for kernel different from mine.
I really need openvpn and now I'm wondering if I should:
1) keep looking
2) figure out how to compile a tun.ko on my linux machine for the arm7 architecture
3) look at some modified rom with the module built in
Do you have any suggestion?
Thank you
Cheers
Click to expand...
Click to collapse
3) As far as I can tell, all of the alternative kernels have this module. The Infused ROM contains the Voodoo kernel, but I believe you can run the Voodoo or Infusion kernels on the stock ROM.
ok I see.
Could you suggest to me a starting point to deal with the custom roms?
I'm have a good experience with linux since years but not enough on smart phones and android in general.
For instance, is there an official website for Infused ROM?
Any tip is welcome.
Thank you!
@dventurin - I had the same issue. I have the Infused rom installed and it has the same issue. I installed SL4A and wrote my own scripts, the app is what's broke everything works at the CLI. I then used Tasker but I think you can do it with Gscripts as well build my own shortcuts. As for where to find the Infused ROM look in the Dev section here. There a several ROM's available but I've only used Infused.
@3GBeyotch
were did you get the Infused rom? Is there an official website with documentation? Honestly I don't feel comfortable when I have to use stuff found on a forum: how can I trust them?
dventurin said:
were did you get the Infused rom? Is there an official website with documentation? Honestly I don't feel comfortable when I have to use stuff found on a forum: how can I trust them?
Click to expand...
Click to collapse
If you want the Infused ROM, head over to the "Infuse 4G Android Development" forum....
http://forum.xda-developers.com/forumdisplay.php?f=1161
From there, you will want to look at 2 threads....
1. You need to root your device first. Check out the very first thread (entitled: [How To] Root the Samsung Infuse 4G) shows how to root your device.....
http://forum.xda-developers.com/showthread.php?t=1082247
(the second link under SOURCE: has a video tutorial)
Side note: When downloading Superoneclick, make sure to get the one that has the drivers included. Also, make sure your external SD card is unmounted!
======================
2. Next, you'll need to install the Infused ROM. Look at the thread (entitled: [ROM] Infused v1.5.0 - (06/18/11) - Faster and smoother than ever!), which has the instructions, etc, for installing the Infused ROM.....
http://forum.xda-developers.com/showthread.php?t=1105413
You basically need to root your device first, then install the Infused ROM.
As far as feeling comfortable with using the sources from the forum, you have nothing to worry about. In regards to the Infused ROM, gtg465x is the one who developed it. All you have to do is follow the instructions, and if you feel uncomfortable about doing one of the steps, ask someone here!
I've had the Infused ROM installed now for a few weeks, and I have not been disappointed! Hope this helps.
Open VPN on Infused ROM tun.ko problems?
Greetings! This discussion is about what I am trying to solve, so I decided to post here. I have searched and read other threads, but can not figure out a solution. I am a noob in this.
Anyway, I also would like to make OpenVPN working on my Samsung Infuse.
I have rooted it, installed the Infused ROM Version 1.5.3 (awesme!)
About Phone gives me the following info:
Firmware version 2.2.1
Baseband version i997UCKE3
Kernel version 2.6.32.9
Build number Infused v1.5.3
No the problem. I have openvpn installed with OpenVPN Installer. My config, key, certificate files are in /sdcard/openvpn folder. Everything seems okay.
When I try to connect to my router at home, however, the tun.ko module would not load. It gives an error. I even tried to load it manually from the Terminal Emulator (insmod /system/lib/modules/tun.ko) It gives me an error still. The module file is in the folder.
What am I doing wrong? Has anyone been able to make openvpn work on the Infused ROM?
I had the same problem on the original AT&T ROM, but that one did not have the tun.ko at all, so it was understandable.
I would appreciate any suggestions.
Thank you in advance.
iovchinn said:
Greetings! This discussion is about what I am trying to solve, so I decided to post here. I have searched and read other threads, but can not figure out a solution. I am a noob in this.
Anyway, I also would like to make OpenVPN working on my Samsung Infuse.
I have rooted it, installed the Infused ROM Version 1.5.3 (awesme!)
About Phone gives me the following info:
Firmware version 2.2.1
Baseband version i997UCKE3
Kernel version 2.6.32.9
Build number Infused v1.5.3
No the problem. I have openvpn installed with OpenVPN Installer. My config, key, certificate files are in /sdcard/openvpn folder. Everything seems okay.
When I try to connect to my router at home, however, the tun.ko module would not load. It gives an error. I even tried to load it manually from the Terminal Emulator (insmod /system/lib/modules/tun.ko) It gives me an error still. The module file is in the folder.
What am I doing wrong? Has anyone been able to make openvpn work on the Infused ROM?
I had the same problem on the original AT&T ROM, but that one did not have the tun.ko at all, so it was understandable.
I would appreciate any suggestions.
Thank you in advance.
Click to expand...
Click to collapse
What's the error?
Entropy512 said:
What's the error?
Click to expand...
Click to collapse
OpenVPN Settings gives the following error: "FATAL: Cannot allocate tun/tap dev dynamically".
When I run "insmod /system/lib/modules/tun.ko" it gives me: "Failed (Exec format error)
Again, thank you for your response.
iovchinn said:
OpenVPN Settings gives the following error: "FATAL: Cannot allocate tun/tap dev dynamically".
When I run "insmod /system/lib/modules/tun.ko" it gives me: "Failed (Exec format error)
Again, thank you for your response.
Click to expand...
Click to collapse
out of curiosity, is there also a tun.ko in /lib/modules in addition to /system/lib/modules?
Entropy512 said:
out of curiosity, is there also a tun.ko in /lib/modules in addition to /system/lib/modules?
Click to expand...
Click to collapse
Man, my hat is off!
Indeed, there is one in /lib/modules and it did work when I tried to load it, instead of the one in /system/lib/modules/. Any idea, why the other one did not work? Not that it matters now.
Also, your signature says that you run Cyanogen Mod with Infuse. My understanding was that Infuse was not yet supported. Is it easy to install it? Any published instructions?
Again, thanks a bunch for the tip.
iovchinn said:
Man, my hat is off!
Indeed, there is one in /lib/modules and it did work when I tried to load it, instead of the one in /system/lib/modules/. Any idea, why the other one did not work? Not that it matters now.
Also, your signature says that you run Cyanogen Mod with Infuse. My understanding was that Infuse was not yet supported. Is it easy to install it? Any published instructions?
Again, thanks a bunch for the tip.
Click to expand...
Click to collapse
My guess is in your previous attempts to add a tun.ko module, you stuck one in /system/lib, or maybe gtg accidentally included some "cruft" in /system/lib that shouldn't be there.
As to CM7 - Right now it's a source-only unofficial build, links to the git repo are in the Development section. There are occasionally binary releases floating around, however not anywhere on these forums. Good things come to those who expand their horizons and do research.
Entropy512 said:
My guess is in your previous attempts to add a tun.ko module, you stuck one in /system/lib, or maybe gtg accidentally included some "cruft" in /system/lib that shouldn't be there.
As to CM7 - Right now it's a source-only unofficial build, links to the git repo are in the Development section. There are occasionally binary releases floating around, however not anywhere on these forums. Good things come to those who expand their horizons and do research.
Click to expand...
Click to collapse
It seems, you are right. /system/lib/modules/ has only one file in it and it is tun.ko. That one did not load. Must be some left-overs from previous reincarnation. The one in /lib/modules/ has lots of different *.ko files and tun.ko among them. This one loads just fine.
Again, thank you very much for your help.
Entropy512 said:
My guess is in your previous attempts to add a tun.ko module, you stuck one in /system/lib, or maybe gtg accidentally included some "cruft" in /system/lib that shouldn't be there.
As to CM7 - Right now it's a source-only unofficial build, links to the git repo are in the Development section. There are occasionally binary releases floating around, however not anywhere on these forums. Good things come to those who expand their horizons and do research.
Click to expand...
Click to collapse
By the way. Perhaps, I can get a bit more help with this. My joy was short-lived. My Infuse connects to my Tomato - no problem. However, it does not force traffic to the VPN tunnel. It is still using whatever service I connect: Wi-Fi, or Cell Provider's.
Any hints on how to fix it? I tried the "Fix HTC Routes" option in "OpenVPN Settings." No luck.
I would appreciate some help.
iovchinn said:
By the way. Perhaps, I can get a bit more help with this. My joy was short-lived. My Infuse connects to my Tomato - no problem. However, it does not force traffic to the VPN tunnel. It is still using whatever service I connect: Wi-Fi, or Cell Provider's.
Any hints on how to fix it? I tried the "Fix HTC Routes" option in "OpenVPN Settings." No luck.
I would appreciate some help.
Click to expand...
Click to collapse
Unfortunately someone else will have to help you there - I haven't used VPN functions on my phone.
iovchinn said:
By the way. Perhaps, I can get a bit more help with this. My joy was short-lived. My Infuse connects to my Tomato - no problem. However, it does not force traffic to the VPN tunnel. It is still using whatever service I connect: Wi-Fi, or Cell Provider's.
Any hints on how to fix it? I tried the "Fix HTC Routes" option in "OpenVPN Settings." No luck.
I would appreciate some help.
Click to expand...
Click to collapse
Having the same problem, am able to connect to openVPN running on ddwrt but the phone isn't directing traffic through it. Anyone have any ideas?
Hi!
I would like to establish a Cisco IPSEC-connection with my Xoom, using get-a-robot-vpnc. The problem is that I'm missing a tun-kernel-module and can't find one for the xoom on the web
Does anyone have one for the Xoom WiFi only running 3.2 (Build HTJ85B) with stock kernel?
Thanks!
McDV
Pulled this out of the EU32Update file, not sure if its what youre looking for??
Questions and requests belong in Q&A. Thread moved.
tonyb15re said:
Pulled this out of the EU32Update file, not sure if its what youre looking for??
Click to expand...
Click to collapse
Thanks, I tried this but it looks like it's only for that ROM.
Maybe someone else has a tun-kernel-module for the stock 3.2?!
Greetings
McDV
yup, I'd like to see this too..
Just instal tiamat kernel 2.1 it contains tun.ko and several other modules.
http://forum.xda-developers.com/showthread.php?t=1200063
also you need to use this modified vpn connections
http://forum.xda-developers.com/showpost.php?p=12124163&postcount=23
Here is tun.ko for 3.2 stock.
wonderful! many, many thanks.
hi,
Will this work on 3.2.1? I copied it /system/lib/modules but when I try to openvpn I get cannot allocate tun/tap dev dynamically.
Is this just a bad file for 3.2.1 or am I missing something else?
I did install busybox and openvpn.
Thanks,
Your tun.ko kernel module needs to be compiled specifically against your kernel source. I don't work with stock anymore, however the developer kernel now floating on xda have this module specifically rolled into their kernels. You would have to root however to install these kernels.
Thanks Kevdog..
I searched and i couldn't find any for 3.2.1. I am the rooted stock 3.2.1 already downloaded from xda. Just need to tun.ko for 3.2.1.
If u know where to find, please send me the link.
Thanks.
Ok 3.2.1 -- Stock or Rooted? What kernel are you running?
I got my rom from this thread
http://forum.xda-developers.com/showthread.php?t=1278214
Thanks,
Ok -- I know this is a lot of work, however I tried it myself and I'm not sure if the rom you linked to is corrupted or my download process failed. (***Rant -- why all the developers who put out files don't match the file to an md5 sum so us users can verify the integrity of the dowload -- I'll never know!!), but I can't seem to extract your system.img. You'll need a tool such as unyaffs to unpack the system.img and then search around in the modules folder until you find the tun.ko. Or you could just flash a Tiamat 3.2.1 kernel which has these modules built in!!
I checked checksum and it was correct before I installed it. Not sure what u mean, I thought this rom doesn't have it period.
I also tried to use tiamat 2.2 which says its for 3.2 but it got stuck at boot for 30 minutes at the honeycomb screen. I thought maybe tiamat ker
Net doesn't support 3.2.1 yet.
http://forum.xda-developers.com/showthread.php?t=1200063
As far as i know this is latest. Doesn't mention 3.2.1. Didn't work for me.
I don't want to go to tiamat rom to avoid a full rebuild.
I just installed ICS and it works fine. I never expected it to work as well as it does, but now I can get down to griping about little things that I use that don't yet work
Normally I use CIFS (Common Internet File System, like Samba was before) to access shares on the net. This worked fine on HoneyComb because I built my own kernel modules.
For ICS, I think the source is not yet released for the kernel. I did see that there was a tun.ko and cifs.ko for ICS over in the transformer prime section of XDA, so I tried those out but it appears the tegra 3 kernel is too different for these to work. (although I think the version is the same).
If anyone has seen or has a working cifs.ko module I'd appreciate getting ahold of it (or especially the ICS kernel source code).
Thanks -
I don't know about cifs.ko as I don't use it, but I do use OpenVPN and found out that tun is part of ICS now, you no longer need a separate module.
hachamacha said:
I just installed ICS and it works fine. I never expected it to work as well as it does, but now I can get down to griping about little things that I use that don't yet work
Normally I use CIFS (Common Internet File System, like Samba was before) to access shares on the net. This worked fine on HoneyComb because I built my own kernel modules.
For ICS, I think the source is not yet released for the kernel. I did see that there was a tun.ko and cifs.ko for ICS over in the transformer prime section of XDA, so I tried those out but it appears the tegra 3 kernel is too different for these to work. (although I think the version is the same).
If anyone has seen or has a working cifs.ko module I'd appreciate getting ahold of it (or especially the ICS kernel source code).
Thanks -
Click to expand...
Click to collapse
I didn't have much success with tun and cifs for my purpose which was to wirelessly access the sd card of the phone/tablet vice versa until I used the Samba app fom the market. In combination with Ghost commander and after upgrading to ICS everything was intact. Not sure if this is helpful to you or not. Just throwin it out there.
Thanks both of you -
I realized that tun was there but thanks. As for cifs, I suppose the module isn't really needed except to use certain utils that rely on it, like root explorer.
I found a number of samba/cifs compatible file managers that're fine for me like ES explorer etc.
Those will be fine and I'll look forward to getting kernel source for ICS anyway.
hachamacha said:
Thanks both of you -
I realized that tun was there but thanks. As for cifs, I suppose the module isn't really needed except to use certain utils that rely on it, like root explorer.
Click to expand...
Click to collapse
I've just rooted my TF101 (ICS) so that I could get Junos pulse working with its ssl vpn. Doing a bit of reading I found I needed tun.ko (at least with 3.2). That automatic tun.ko installer from the market reports that tun.ko is installed (compiled into the kernel?)
I can see the tun0 created, with an IP address. But it doesn't work, not a single bit travels the tunnel interface.
I'm officially confused...
Still too few posts under this account name to be able to post links, but have you seen this thread in Dev?
xpad / cifs modules for stock kernel ICS v9.2.1.11
Thanks for that... that confirms tun.ko is built in, which doesn't help me find/fix my problem.
Will keep at it!