Hi,
I couldn't seem to find any of the above-mentioned kernel modules in the latest version of Overcome rom/kernel. I could manually copy the 3 files in the /lib/modules or /modules directory but which init startup script can I include so as to automatically start those modules upon reboot of the tab? Many thanks in advance for any advice and suggestions.
•Built in CIFS/TUN/SlowWork support
Related
Hello,
wich are the components from an android on a HTC HD2.
There are different types like Kernel, Moduls, etc...
But where can I find it and understand how they work together.
What I found:
zImage includes the Kernel for the complete system
startup.txt includes the parameter how to start the system
CLRCAD.EXE is used for the sound in android
HaRet.exe is used to start/boot the android
Is this correct? What I can't assign is:
the ROM on which the release based - can I see the files on my SD or is this included in other files?
the modules like WiFi and so on (maybe here /system/lib/modules)?
The next questions would be:
Could I use a new kernel with an existing system (Only with changing the existing zImage-File and unsing a modified startup.txt)?
Could I update seperate moduls without install new system? (new version for WiFi or GPS or else)
The kernel is the core of any linux based os, some base drivers are included in kernel and other linkes as modules, if you install a new kernel that don't need any external module you can simple copy zImage, if new kernel need new modules you have to copy into /system/lib/modules directory. Modules are related to kernel you cannot update modules without apdate kernel.
Hi,
When you want to perform some scripts at boot-time, there is two possibilities :
- modify init.rc, but it requires to reflashing the rootfs image (modification in / does not hold after a reboot),
- using an android app like script manager, which will load your scripts at java/dalvik platform boot-time.
I've managed to find a way based on activating tf-daemon, which is a script called by the asus/ventana initrc, but disabled at boot-time. Basically, we're re-enabling this daemon by setting the property tf.enable to yes, and then creating a script called tf-daemon and put it in /system/bin. Since this script is called by init.ventana.rc as root, you can put whatever you want inside this script.
I don't know what is the original purpose of this daemon, but probably it's used by the asus team for internal and debugging purpose.
Be aware that in the next firmware update, this possibility could disappear.Let's hope the asus team does not read this post. Or at least they could allow power users to call custom scripts at boot-time.
As a case study, you will find as attachment a script for loading nfs modules at boot-time.
PS: damn, can't upload. Here is a temporary link : http://dl.free.fr/hwTZ0YBq2
Untar the archive, then su, and sh install.sh
At reboot, you should have nfs modules loaded.
Good find:
I gave this a try just to load a couple of my own modules that work with the kernel I'm using. Works fine -- Thanks, -
Another method is to make a script and just call it in the init.rc. After a firmware update you only have to add the "exec myscript.sh" line to init.rc. I personally prefer this method because it allows me to control when the script is executed, whereas the tf-daemon method is always executed at the same point(AFAIK). Good research though, always nice to know all the boot calls.
Modifying the init.rc was my first shot, but the problem is that init.rc lies in ramdisk. So when trying to modify, the modification does not hold
after reboot. So a real modification involves to reflash rootfs with nvflash, too much hassle for me. The method I'm providing is for lazy ones. ;-)
nice find, but the link is dead, could you please provide a new link for the script?
also, how do I load nfs module for there is none under /lib/modules, compile the kernel myself?
I have been a fan of DJ Steve's ROMs and his dev skills. But right now I am running a deodexed 351 that is otherwise stock, in portrait mode. haha
I love his ability to compile ROMs and Kernels and such, but I really want just the kernel that supports overclocking.
I can get any of the kernels to work from 1.91
no vol, no ppt
no vol, ppt
vol and ppt
vol and no ppt
I even add the proper dhd.ko file for the modules folder and correct the permissions and even the reset.ko file too.
But no matter what I do, I can't get the kernel to work AND wifi to work. It seems like either or for a stock rom. Either you have a plain kernel with no overclocking, or you can use the kernel with no wifi working.
Does anyone know of:
1: If there are other files I should be bringing over from the rom to make the kernel and wifi work together
or
2: What specifically I can edit to allow the stock kernel to allow overclocking?
Sorry for the long post.
Thanks for the help in advance.
OK. I guess no one out there knows either.
What I have been doing so far to achieve overclocking is create a .txt file (according to the instructions on setcpu.com) and put that at the root of my sdcard and have setcpu do the rest.
I would prefer to use the kernel method so I can add the volboost and/or ppt tweaks in 1.91.
I will wait patiently for your guidence.
Maybe try this
http://forum.xda-developers.com/showpost.php?p=14679059&postcount=135
Ok I figured out which one will work.
http://forum.xda-developers.com/showthread.php?t=1113256
Ok go to Simple Streak's thread.
1. Download the .zip for version 1.2
2. copy the files in /system/lib/modules to your /system/lib/modules
3. fix permissions, they should be 644, which are rw-r--r--
4. boot into fastboot, and flash his boot.img
Thank you Spidla for a kernel I can use that supports overclocking, that I dont have to use the entire ROM and most importantly, my wifi works.
rsalib said:
Ok I figured out which one will work.
http://forum.xda-developers.com/showthread.php?t=1113256
Ok go to Simple Streak's thread.
1. Download the .zip for version 1.2
2. copy the files in /system/lib/modules to your /system/lib/modules
3. fix permissions, they should be 644, which are rw-r--r--
4. boot into fastboot, and flash his boot.img
Thank you Spidla for a kernel I can use that supports overclocking, that I dont have to use the entire ROM and most importantly, my wifi works.
Click to expand...
Click to collapse
I am interested in this, can you explan the procedure in more detail, copy files from what rom to what rom and how to fix permissions?
thanks
/*Update Nov 09 2011: Added cryptoloop.ko */Update
/*Update Nov 02 2011: Added option.ko for some usb 3G modems and asix.ko for usb ethernet adapters that uses Asix AX88772 chipset */Update
*/Update Oct 12 2011: NTFS support comes standard with the 3.2's kernel, so I removed ntfs.ko module. */Update
Since I could not find all the modules I needed, and did not want to bug devs any more, I decided to bite the bullet and compile myself.
These are for the plain 3.2 kernel, which is 2.6.36.3+
I compiled the following modules, which are all in the same 7zip file:
Network:
tun.ko #for openvpn
option.ko #for some 3G modems
asix.ko #for usb ethernet adapters that uses Asix AX88x72 chipset
Filesystem:
cifs.ko #windows shares
nfs.ko #unix/linux shares
isofs.ko #cd iso images
udf.ko #cd udf images
USB to serial converter:
ftdio_sio.ko #ftdi usb2serial converters. Prolific chipset is already in the kernel so I did not compile that.
I have tested these under the stock 3.2 with root rom, the one in http://forum.xda-developers.com/showthread.php?t=1290318 and they load fine without errors on dmesg.
Enjoy.
Let me know if you need any other modules and I will try to compile them.
I have a request I have looked around and have not been able to find this module anywhere. It is the joydev module that supports many gamepads, joysticks and even some racing wheels. The source is available and even some modules for other devices but nothing for any tegra devices. I have a transformer myself but being the same hardware the module should work on either device. I have included the list of devices that are supported by the driver and the source for the driver. Any help would be greatly appreciated.
Supported devices:
http://atrey.karlin.mff.cuni.cz/~vojtech/input/hardware.html
Source:
https://github.com/netarchy/android_kernel_TF101/blob/master/drivers/input/joydev.c
This is kind of beyond my skillset as I do not know how to patch the kernel tree so that this driver shows on the menuconfig. Sorry.
Could you please build usb_wwan.ko and option.ko for 2.6.36.3+ ?
VicDeo said:
Could you please build usb_wwan.ko and option.ko for 2.6.36.3+ ?
Click to expand...
Click to collapse
usb_wwan seems to be statically compiled into the kernel already (USB driver for GSM and CDMA modems), so there isn't any module but it is always there in the kernel.
I am going to update the original post for the option.ko shortly.
Getting some errors on some of these. Anyone else having issues?
Tried these from both /system/lib/modules and sdcard.
option.ko:
Code:
insmod: init_module '/sdcard/modules/option.ko' failed (Invalid argument)
nfs.ko:
Code:
insmod: init_module '/sdcard/modules/nfs.ko' failed (No such file or directory)
Triple checked that the nfs.ko file was there and named correctly.
Following modules have installed fine.
asix, ftdi_sio, and cifs
I've just checked those two on my a500. It seems like option.ko is statically linked into the kernel, because on dmesg it says "option: module is already loaded". If I am guessing it correct (e.g. driver is statically linked in the kernel) than it means you don't need the .ko at all.
For the nfs, it throws bunch of "unknown symbol" errors on dmesg, I am guessing it cannot read symbols from the kernel. If that's the case, it would need a new kernel with a modified makefile, which is beyond my abilities unfortunately.
How to make the system load the module automatically when boot up? Thanks
mcmugchu said:
How to make the system load the module automatically when boot up? Thanks
Click to expand...
Click to collapse
That I don't know, I manually load them whenever I need.
mcmugchu said:
How to make the system load the module automatically when boot up? Thanks
Click to expand...
Click to collapse
You need system/etc/init.d folder with modules file.
I posted a patch for testing here is link maybe it works , flash with cwm.
Based on this thread. so all credits go to OP.
http://www38.zippyshare.com/v/75708872/file.html
Hi does anybody know if these support netbios name, i can't download and try right now. I've only found modules that works with the ip but not the name. Not practical when moving a lot.
Thanks
Hi,
I am using the same kernel 2.6.36.3+ and I'd like to have please:
eeprom_93cx6.ko, mac80211.ko, rtl8187.ko
Thank you in advance and if you can provide a tutorial that would be awesome!
Thanks!!
Good jobs.
but the modules don't work on Sumsung P7500 tablet,(Kernel 2.6.36.4)
htt p:// droidbasement.com /db-blog/?p=2395
10.1 3G, Touchwiz UX (HC 3.1 (stock); GT-P7500):
boot-cm_2636.4_p4_ux-oc-xtra-vfpv3-d16_fp-112011.zip
insmod isofs.ko, I got a error message" Exec format error"
Can you compile them for this kernal version? Thanks!
I need isofs.ko,udf.ko to support DVD image files.
MyMinds_Kernel_Swap
===================
Based on AnyKernel, but pretty much rebuilt in every way so that it will actually work. So, many thanks to Koush for the idea.
The Idea and What It Does...
=======================
Some but not all of this script has been snippets here and there from ArchiKitchen and DSIXDA Kitchen.
This has allowed me to formulate a zip as such without the need to technically build from scratch saving me LOADS OF HOURS.
It currently uses my static compiled mkbootimg, unmkbootimg, and mkbootfs binaries to allow editing, and rebuilding of the boot.img.
Some serious modifications were made to get this to work successfully with MUCH DEBUGGING. If you change something and it breaks another function then that is on you!
# IT IS CURRENTLY STABLE!
1. It will pull your current boot.img using dd.
2. It will search for the Android! header in the boot.img and remove the unnecessary junk before it if needed to.
3. It will split the boot.img in to the kernel and ramdisk.
4. It will unpack the contents inside the ramdisk.
5. It will modify the default.prop file giving you insecure ADB. If you already have it then this will not affect you.
6. It will modify the init.rc file to give support for init.d. If you already have it then this will not affect you.
7. It will write to sysinit and install-recovery.sh for the completion of init.d support. If already done, then this will not affect you.
8. It will make the init.d folder under /system/etc on your device with required permissions.
9. It will place an init.d script to test to see if init.d is fully working. If it works, you will find a file called, HAS_INIT, located in the /dev directory of your device.
10. It will swap out the original kernel with a new prebuilt kernel upon rebuilding the new boot.img
11. It will repack you a new ramdisk using mkbootfs to be applied to your new boot.img upon rebuilding it.
12. It will remove your old modules and push your new modules that came with your new prebuilt kernel.
13. It will write your new boot.img to your boot partition using dd.
14. Hopefully, more to come!
MAKE SURE YOU CHANGE...
=======================
"$BOOT_PARTITION" ACCORDING TO YOUR DEVICE BEFORE USING THIS SCRIPT!!!!!!
How to use it...
==============
1. Place your prebuilt kernel in the prebuilt folder and insure it is named, zImage.
2. Place kernel modules in the modules folder.
3. Zip, and flash in TWRP recovery.
If you have any suggestions then let me know. My ears are open to them.
https://github.com/ModdingMyMind/MyMinds_Kernel_Swap
Sent from my C525c using Tapatalk