Related
Here are some kernel modules for common operations that can't be done using the vanilla SE 2.1 kernel. Those modules should work on X10mini/X10minipro/X8
Requirements: working busybox, adb
Firstly, you need to remount RW your /system partition to be able to put the modules in place:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
tun.ko, used for vpnc networks
Installation (kernel part):
Code:
adb push tun.ko /sdcard/
adb shell
su
busybox mv /sdcard/tun.ko /system/lib/modules/
busybox chmod 644 /system/lib/modules/tun.ko
Installation (gui part):
Get the latest apk of get-a-robot from here
Code:
adb install VPN_Connections_v099.apk
launch the app and add the network according to the config parameters that you have. This app also handles insmoding the tun.ko kernel module when needed.
cifs.ko, used for mounting windows/samba shares
Installation (kernel part):
Code:
adb push cifs.ko /sdcard/
adb shell
su
busybox mv /sdcard/cifs.ko /system/lib/modules/
busybox chmod 644 /system/lib/modules/cifs.ko
Usage:
Code:
insmod /system/lib/modules/cifs.ko
busybox mount -t cifs //<serverip>/<sharename> <local mount point> -o username=<name>,password=<password>
e.g. for guest authentication to share named 'samba' at server with ip 192.168.0.3:
busybox mkdir /sdcard/samba
busybox mount -t cifs //192.168.0.3/samba /sdcard/samba -o username=guest
nfs.ko, used for mounting NFS shares
Installation (kernel part):
Code:
adb push sunrpc.ko /sdcard/
adb push lockd.ko /sdcard/
adb push nfs.ko /sdcard/
adb shell
su
busybox mv /sdcard/sunrpc.ko /system/lib/modules/
busybox mv /sdcard/lockd.ko /system/lib/modules/
busybox mv /sdcard/nfs.ko /system/lib/modules/
busybox chmod 644 /system/lib/modules/sunrpc.ko
busybox chmod 644 /system/lib/modules/lockd.ko
busybox chmod 644 /system/lib/modules/nfs.ko
Usage:
Code:
insmod /system/lib/modules/sunrpc.ko
insmod /system/lib/modules/lockd.ko
insmod /system/lib/modules/nfs.ko
busybox mount -t nfs <serverip>:/<share> <local mount point> -o nolock
e.g.
busybox mkdir /sdcard/nfs
busybox mount -t nfs 192.168.0.3:/home/data /sdcard/nfs -o nolock
Utf8 support
This can be used with cifs or nfs when mounted partitions contain characters in utf8 and thus appear as junk
Installation (kernel part):
Code:
adb push nls_utf8.ko /sdcard/
adb shell
su
busybox mv /sdcard/nls_utf8.ko /system/lib/modules/
busybox chmod 644 /system/lib/modules/nls_utf8.ko
Usage:
Code:
insmod /system/lib/modules/nls_utf8.ko
Filesystems
I have not used these modules since I have not partitioned my sdcard for these types of filesystems. I guess they can be useful in a multi-partition scheme or with app2sd and something else other than ext2
ext3.ko (needs jbd.ko to be insmoded first)
ext4.ko (needs jbd2.ko to be insmoded first)
jfs.ko
reiserfs.ko
xfs.ko (needs exportfs.ko to be insmoded first)
ntfs.ko (read-only support)
App2sd for froyo
These modules are only useful if you have an custom froyo ROM in order to get the app2sd functionality working
dm-mod.ko (needs jbd.ko to be insmoded first)
dm-crypt.ko (needs jbd2.ko to be insmoded first)
twofish_common.ko
twofish.ko
Installation (kernel part):
Code:
adb push dm-mod.ko /sdcard/
adb push dm-crypt.ko /sdcard/
adb push twofish_common.ko /sdcard/
adb push twofish.ko /sdcard/
adb shell
su
busybox mv /sdcard/dm-mod.ko /system/lib/modules/
busybox mv /sdcard/dm-crypt.ko /system/lib/modules/
busybox mv /sdcard/twofish_common.ko /system/lib/modules/
busybox mv /sdcard/twofish.ko /system/lib/modules/
busybox chmod 644 /system/lib/modules/*
Disclaimer:
I can't be held responsible if any of those modules brick your device. Use them at your own risk!
Changelog:
- 22/3/11 2.1.A.0.435 kernel image for x10mini
- 20/3/11 Updated tun.ko and kernel .config using 2.1.1.A.0.6
- 11/2/11 Added modules for froyo's app2sd
- 20/1/11 Added .config file
- 17/12/10 Initial posting
- 22/12/10 Added missing filesystems deps to filesystems.zip
Feel free to post any module requests you may have.
Can u explain me ths much further..what it is..?how the change when we get this in e10i
Sent from my E10i
you can find very helpful information on wikipedia:
(unfortuneately i cannot post external urls by now yet)
so, put in wikipedia this:
tun.ko - you can create VPN connection with this module
VPN
OpenVPN
cifs.ko - you can mount your samba/windows share on your device (if u dont know what it means.. you can basically have a folder on your phone, which represents the shared folder from your windows computer ..e.g. movies, music..etc
Server Message Block
Samba
Mount
nfs.ko - that is the same actually, but with this module u mount linux network file system, which also is capable of permissions management etc
NFS
Great! Nice Addition!
Just a point though:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
Click to expand...
Click to collapse
Shouldn't this be:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
Click to expand...
Click to collapse
any module to overclok?
any module (or modification) to overclock cpu over 600 mhz?
DaRk_dOg said:
Great! Nice Addition!
Just a point though:
Shouldn't this be:
Click to expand...
Click to collapse
That's correct. Fixed.
Even though it works with mtdblock2 also
DrBios said:
any module (or modification) to overclock cpu over 600 mhz?
Click to expand...
Click to collapse
Is there some particular module in the vanilla kernel that can provide this?
I've seen it on other phones but with custom kernel modules / modifications
where can i read about all the possible modules?
What about psfreedom.ko (used to jailbreak the PS3)
It is possible to import?
Lef.teris said:
What about psfreedom.ko (used to jailbreak the PS3)
It is possible to import?
Click to expand...
Click to collapse
yeah psfreedom.ko would be so great on mini
any one can help me to run debian on my device???
theres a program called "Linux Installer", but its seem to need some kernel modules that the U20 dosnt have:
Code:
The Linux is installed separetly of android, the application doesn't delete any android files.
For that the application need some preriquieres :
- Rooted phone with id 0.
- Ext2, Ext3 or Ext4 support.
- If you install into loop, LOOP is needed into kernel.
- It is recommanded to reboot your phone before lunch this app to freed your memory.
(more info here http://android.galoula.com/en/LinuxInstall/)
the high priority is the LOOP thing!
any help? regards!
you need a kernel supporting loop, no addon will enable this,
you need a KERNEL that supports loop ( same as for NETFILTER needed for proper WiFi tethering )
see this thread
morning_wood said:
you need a kernel supporting loop, no addon will enable this,
you need a KERNEL that supports loop ( same as for NETFILTER needed for proper WiFi tethering )
see this thread
Click to expand...
Click to collapse
The default kernel DOES have loopback support. E.g:
cd /sdcard/
dd if=/dev/urandom of=1.img bs=1024 count=20000
mkfs.ext2 -F 1.img
mkdir /sdcard/loop
mount -o loop 1.img /sdcard/loop
This will create a loop device (1.img) formatted with ext2 and mount it under /sdcard/loop
Netfilter though is not build in, hence there can be no iptables module for this kernel for Wifi tethering
Hi nobodyAtall,
How to implement method for app2sd with ext4 with these new modules?
daemon-rj said:
Hi nobodyAtall,
How to implement method for app2sd with ext4 with these new modules?
Click to expand...
Click to collapse
This shouldn't be too hard.
- Place the required module in /system/lib/modules/
- Format your 'app' partition of the sd card in ext4 or any other FS
- Have /system/bin/sh modified so that the respective module is insmoded at boot, e.g:
Code:
#!/system/bin/sh_bak
busybox sh <<eof
if [ -f /sqlite_stmt_journals/app2sd ] ;
then
sleep 0
else
[B]insmod /system/lib/modules/jbd2.ko[/B]
[B]insmod /system/lib/modules/ext4.ko[/B]
busybox sh /system/etc/mount_sd.sh >> /sqlite_stmt_journals/app2sd.log
fi
eof
/system/bin/sh_bak "[email protected]"
- Have /system/etc/mount_sd.sh updated so that the correct FS type is used when mounting:
e.g.
Code:
mount -t ext4 /dev/block//vold/179:2 /system/sd
And it should work. As already said, I have not tried this, hence can't guarantee for it!
nobodyAtall said:
This shouldn't be too hard.
- Place the required module in /system/lib/modules/
- Format your 'app' partition of the sd card in ext4 or any other FS
- Have /system/bin/sh modified so that the respective module is insmoded at boot, e.g:
Code:
#!/system/bin/sh_bak
busybox sh <<eof
if [ -f /sqlite_stmt_journals/app2sd ] ;
then
sleep 0
else
[B]insmod /system/lib/modules/ext4.ko[/B]
busybox sh /system/etc/mount_sd.sh >> /sqlite_stmt_journals/app2sd.log
fi
eof
/system/bin/sh_bak "[email protected]"
- Have /system/etc/mount_sd.sh updated so that the correct FS type is used when mounting:
e.g.
Code:
mount -t ext4 /dev/block//vold/179:2 /system/sd
And it should work. As already said, I have not tried this, hence can't guarantee for it!
Click to expand...
Click to collapse
I had some problems with it:
# insmod /system/lib/modules/ext3.ko
insmod /system/lib/modules/ext3.ko
insmod: init_module '/system/lib/modules/ext3.ko' failed (No such file or direct
ory)
Click to expand...
Click to collapse
What could have gonne wrong?
DaRk_dOg,
Could you post the output from:
Code:
ls -la /system/lib/modules/ext3.ko
and
Code:
dmesg
after insmoding the module?
nobodyAtall said:
DaRk_dOg,
Could you post the output from:
Code:
ls -la /system/lib/modules/ext3.ko
and
Code:
dmesg
after insmoding the module?
Click to expand...
Click to collapse
Ok still can't insmod:
# ls -la /system/lib/modules/ext3.ko
ls -la /system/lib/modules/ext3.ko
-la: No such file or directory
/system/lib/modules/ext3.ko
Click to expand...
Click to collapse
And dsmeg output:
<4>[ 303.281915] select 2041 (re.rootexplorer), adj 15, size 5010, to kill
<4>[ 303.281975] send sigkill to 2041 (re.rootexplorer), adj 15, size 5010
<3>[ 303.296963] init: untracked pid 2053 exited
<4>[ 318.617897] ext3: Unknown symbol journal_force_commit
<4>[ 318.620697] ext3: Unknown symbol journal_dirty_data
<4>[ 318.621781] ext3: Unknown symbol journal_force_commit_nested
<4>[ 318.624642] ext3: Unknown symbol journal_init_dev
<4>[ 318.625722] ext3: Unknown symbol journal_dirty_metadata
<4>[ 318.626801] ext3: Unknown symbol journal_forget
<4>[ 318.628947] ext3: Unknown symbol journal_wipe
<4>[ 318.630355] ext3: Unknown symbol journal_blocks_per_page
<4>[ 318.636724] ext3: Unknown symbol journal_errno
<4>[ 318.639097] ext3: Unknown symbol journal_extend
<4>[ 318.643832] ext3: Unknown symbol journal_invalidatepage
<4>[ 318.649460] ext3: Unknown symbol journal_create
<4>[ 318.651390] ext3: Unknown symbol journal_unlock_updates
<4>[ 318.653257] ext3: Unknown symbol journal_revoke
<4>[ 318.655039] ext3: Unknown symbol journal_lock_updates
<4>[ 318.656995] ext3: Unknown symbol journal_start_commit
<4>[ 318.661068] ext3: Unknown symbol journal_flush
<4>[ 318.662145] ext3: Unknown symbol journal_load
<4>[ 318.664970] ext3: Unknown symbol journal_try_to_free_buffers
<4>[ 318.667287] ext3: Unknown symbol journal_update_format
<4>[ 318.668987] ext3: Unknown symbol journal_get_write_access
<4>[ 318.670397] ext3: Unknown symbol journal_get_undo_access
<4>[ 318.671827] ext3: Unknown symbol journal_get_create_access
<4>[ 318.673858] ext3: Unknown symbol journal_destroy
<4>[ 318.675905] ext3: Unknown symbol journal_clear_err
<4>[ 318.679265] ext3: Unknown symbol journal_stop
<4>[ 318.684682] ext3: Unknown symbol journal_init_inode
<4>[ 318.685760] ext3: Unknown symbol journal_start
<4>[ 318.687413] ext3: Unknown symbol log_wait_commit
<4>[ 318.692583] ext3: Unknown symbol journal_release_buffer
<4>[ 318.694160] ext3: Unknown symbol journal_check_available_features
<4>[ 318.695243] ext3: Unknown symbol journal_abort
<4>[ 318.696633] ext3: Unknown symbol journal_restart
<3>[ 516.699960] init: untracked pid 2271 exited
Click to expand...
Click to collapse
Thanks DaRk_dOg.
Apparently the jbd.ko module is also needed for journaling to work for ext3.
jbd2.ko is needed for ext4.
Added those to the initial post, please re-download the updated filesystems.zip
I'm having an issue insmoding a kernel I built for my rooted galaxy s2. My end game is to get USB-ethernet working by building the asix module but I cant even get a ko from the default build to insmod. (I also cant load the kernel I compiled, i tried with odin... but I feel like this is a separate issue)
I compiled a kernel based on what I downloaded from samsungs website "GT-I9100_OpenSource_Update3.zip" and followed the instructions included (basically run make with defconfig) I chose scsi_wait_scan.ko as a test because it was built with the default config and currently wasn't loaded on my phone.
Here's some info that's pertinent. Any help would be appreciated. I'm running Ubuntu 11.
# lsmod
lsmod
dhd 242604 0 - Live 0xbf02e000
j4fs 65002 1 - Live 0xbf018000 (P)
Si4709_driver 17347 0 - Live 0xbf00d000
bthid 3384 0 - Live 0xbf007000
vibrator 6724 2 - Live 0xbf000000
# insmod scsi_wait_scan.ko
insmod scsi_wait_scan.ko
insmod: init_module 'scsi_wait_scan.ko' failed (Exec format error)
# dmesg
...
<4>[19668.986907] scsi_wait_scan: disagrees about version of symbol module_layout
# modinfo scsi_wait_scan.ko
modinfo scsi_wait_scan.ko
modinfo: can't open '/2.6.35.7-I9100XWKI4-CL575468/': No such file or directory
# pwd
/mnt/sdcard
# ls -l
...
-rwxrwxr-x system sdcard_rw 32484 2012-01-12 10:21 scsi_wait_scan.ko
$ file scsi_wait_scan.ko
scsi_wait_scan.ko: ELF 32-bit LSB relocatable, ARM, version 1 (SYSV), not stripped
USB Host support
Has any body had luck with usb host working for devices other then sdcards on the S2? I got the kernel compiled and removed the whitelist but it looks like the USB host support is not fully implimented? Does the S2 support usb asynchronous mode? I'm not a usb expert but the kernel fails hard (lots of messges to dmesg and then the phone reboots) when I try it with an asix usb device.
Hi there,
I've attached the tun and ntfs kernel modules, let me know if you're unable to download/use them
tun.ko
md5sum: 08956c574f72929f3c831e834ff9860d *tun.ko
ntfs.ko
md5sum: 5bbfa6ce8ddd66f7dda885a333fdf027 *ntfs.ko
to use them move them to a persistent folder like /data/local/lib
you may have to chmod them and then from a root shell run:
insmod /data/local/lib/tun.ko
or whatever module you want to install.
To ensure this runs at boot you'll likely have to add a script to init.d, I assume.
This is for the Sony ICS build of kernel 2.6.39.4
Let me know if people would like additional modules and I can build and upload them.
I hope this helps.
A
I don't have enough posts under my belt to list this in the dev forum, could somebody put a link there to this thread in case people are still looking for these modules?
Thanks,
A
Could you please write step by step installation tutorial for dummies like me?
Sent from my Sony Tablet S using xda app-developers app
installing kernel modules, init.d
Sure thing! Here's how to install the modules and make them work persistently.
I'm going to have to assume you have root and a terminal emulator (and utilities like busybox).
To simply install the kernel modules, you'll have to download that tarball I posted, unpack it, ensure you have the right permissions on the files, and run the install command from a root prompt (we'll assume you've downloaded the tarball to /sdcard/download, though if you've used /sdcard2/download or some other directory use that instead):
mkdir /data/local/kmods
cd /data/local/kmods
chmod 775 /data/local/kmods
cp /sdcard/download/tun_and_ntfs_modules_2.6.39.4.tar /data/local/kmods/
tar -xvf tun_and_ntfs_modules_2.6.39.4.tar
(if you're not yet in a root prompt at this point type: su)
chmod 775 ntfs.ko
chmod 775 tun.ko
insmod ntfs.ko
insmod tun.ko
to check to see if the module loaded properly, at the prompt type:
lsmod | grep tun
lsmod | grep ntfs
and check to see if anything is printed, with "Live" on the line.
And that should be that, but at this point you'll have to load it manually every time you want to use it.
A better way is to create a script that will run at startup every time you boot by placing it in /system/etc/init.d. To do this, first ensure that you've followed the above steps and placed the modules in /data/local/kmods (you can use any name you want for the kmods folder, as long as you're consistent. Using the /data/local/ directory ensures the modules persist after reboot); also, you'll need to use condi's all-in-one tool to enable the init.d support --- it's option 4 -> 4 (using version 4.1).
ok, so using vi or a text editor create the following file, we'll call it "kmodboot" (it doesn't need a file extension!)
so the file should contain the following lines:
#!/system/bin/sh
insmod /data/local/kmods/ntfs.ko
insmod /data/local/kmods/tun.ko
You can run this script at this point to ensure that it works (insmod will throw an error if the module is already loaded):
chmod 775 kmodboot
./kmodboot
Next you're going to need to remount /system as writeable, you can use ghost commander or ES File Explorer. (To do this manually, at a root prompt type:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p2 /system
But be careful! You've just made your system directory writable! type
mount -o remount,ro -t ext4 /dev/block/mmcblk0p2 /system
to remount it back to read only, when you're done!
mv kmodboot /etc/init.d
cd /etc/init.d
chmod 775 kmodboot
That's it! reboot and see if it the modules have loaded, using lsmod.
I hope this helps, remeber to be careful when you have your /system directory writeable! I can't help you if you mess up.
Take care,
A
kulen said:
Could you please write step by step installation tutorial for dummies like me?
Click to expand...
Click to collapse
thank you for quick and detailed response
I tried what you said to do but this is what I got.
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ mkdir /data/local/kmods//
mkdir failed for /data/local/kmods//, Permission denied
255|[email protected]:/ $ su
[email protected]:/ # mkdir /data/local/kmods
[email protected]:/ # cd /data/local/kmods
[email protected]:/data/local/kmods # mv /sdcard/xda_download/tun_and_ntfs_modules_2.6.39.4.tar /data/local/kmods
failed on '/sdcard/xda_download/tun_and_ntfs_modules_2.6.39.4.tar' - Cross-device link
255|[email protected]:/data/local/kmods #
So, what am I doing wrong?
in this other part, which I don't intend to do for now because it seems complicated to me, system needs to be writable just to copy script to init.d?
in this post are two other modules for other kernel:
http://forum.xda-developers.com/showthread.php?t=1557868
it would be great if you could make them for this kernel also.
Thank you
Hi there,
I'll look into posting those other modules when I get a chance (so the serial and cifs modules, any others?)
As for that cross-link error, try doing a copy (cp) instead of a move (mv) and ensuring thr permissions of the kmods directory are correct. I've edited the tutorial above to reflect this.
As for the init.d stuff, I think that's the way to go: in order to copy the script to the startup directory you need to make the whole system mount writeable.
Let me know if this helps.
A
I just continued last session and this is what I got now:
[email protected]:/ $ export PATH=/data/local/bin:$PATH [email protected]:/ $ mkdir /data/local/kmods//mkdir failed for /data/local/kmods//, Permission denied 255|[email protected]:/ $ su [email protected]:/ # mkdir /data/local/kmods [email protected]:/ # cd /data/local/kmods [email protected]:/data/local/kmods # mv /sdcard/xda_download/tun_and_ ntfs_modules_2.6.39.4.tar /data/local/kmods failed on '/sdcard/xda_download/tun_and_ntfs_modules_2.6.39.4.tar' - Cross-device link 255|[email protected]:/data/local/kmods # mv /sdcard/xda_download/tun_and_ ntfs_modules_2.6.39.4.tar /data/local/kmods failed on '/sdcard/xda_download/tun_and_ntfs_modules_2.6.39.4.tar' - Cross-device link 255|[email protected]:/data/local/kmods # chmod 775 /data/local/kmods [email protected]:/data/local/kmods # cp /sdcard/xda_download/tun_and_ ntfs_modules_2.6.39.4.tar /data/local/kmods [email protected]:/data/local/kmods # tar -xvf tun_and_ntfs_modules_2.6.39.4.tar ntfs.ko tun.ko [email protected]:/data/local/kmods # chmod 775 ntfs.ko [email protected]:/data/local/kmods # chmod 775 tun.ko [email protected]:/data/local/kmods # lsmod ntfs.ko ath6kl_sdio 190837 0 - Live 0xbf081000 cfg80211 155484 1 ath6kl_sdio, Live 0xbf04c000 compat 4748 1 ath6kl_sdio, Live 0xbf044000 quick_tp 9806 0 - Live 0xbf03f000 (P) cyttsp_i2c 1347 0 - Live 0xbf039000 cyttsp_core 4862 1 cyttsp_i2c, Live 0xbf032000 hid_sony 1573 0 - Live 0xbf02c000 stuid 159606 0 [permanent], Live 0xbf000000 (P) [email protected]:/data/local/kmods # lsmod tun.ko ath6kl_sdio 190837 0 - Live 0xbf081000 cfg80211 155484 1 ath6kl_sdio, Live 0xbf04c000 compat 4748 1 ath6kl_sdio, Live 0xbf044000 quick_tp 9806 0 - Live 0xbf03f000 (P) cyttsp_i2c 1347 0 - Live 0xbf039000 cyttsp_core 4862 1 cyttsp_i2c, Live 0xbf032000 hid_sony 1573 0 - Live 0xbf02c000 stuid 159606 0 [permanent], Live 0xbf000000 (P) [email protected]:/data/local/kmods # lsmod | grep tun 1|[email protected]:/data/local/kmods # lsmod | grep ntfs 1|[email protected]:/data/local/kmods #
When I connect my hard drive with 2 ntfs and 1 fat32 partitions only fat32 is recognized.
What did I do wrong this time?
Well I would like to make my usb 3g modem to work with this tablet and usb to serial is needed for that as I understood.
Cifs I don't need for now but I plan to buy network hard drive so it's good to be prepared and maybe there are some others that want it but stay silent.
So if it's not a problem for you it would be nice if you post it here also. If it's a problem it's ok.
If this is messy I can post it again from computer but not sooner than tomorow
Sent from my Sony Tablet S using xda app-developers app
Hi,
it looks like you're trying to install the modules using the list function (lsmod) instead of the install function: insmod.
It's hard to tell as there are no line breaks, but try
insmod tun.ko
insmod ntfs.ko
i'm going to attach the cifs and usbserial modules to my first post, so look out for an edit coming soon.
let me know if this resolves anything.
a
Sent from my Sony Tablet S using xda app-developers app
It seems it is installed now but I still can see only fat32 partition
[email protected]:/ $ export PATH=/data/local/bin:$PATH [email protected]:/ $ mkdir /data/local/kmods//mkdir failed for /data/local/kmods//, Permission denied 255|[email protected]:/ $ su [email protected]:/ # mkdir /data/local/kmods [email protected]:/ # cd /data/local/kmods [email protected]:/data/local/kmods # mv /sdcard/xda_download/tun_and_ ntfs_modules_2.6.39.4.tar /data/local/kmods failed on '/sdcard/xda_download/tun_and_ntfs_modules_2.6.39.4.tar' - Cross-device link 255|[email protected]:/data/local/kmods # mv /sdcard/xda_download/tun_and_ ntfs_modules_2.6.39.4.tar /data/local/kmods failed on '/sdcard/xda_download/tun_and_ntfs_modules_2.6.39.4.tar' - Cross-device link 255|[email protected]:/data/local/kmods # chmod 775 /data/local/kmods [email protected]:/data/local/kmods # cp /sdcard/xda_download/tun_and_ ntfs_modules_2.6.39.4.tar /data/local/kmods [email protected]:/data/local/kmods # tar -xvf tun_and_ntfs_modules_2.6.39.4.tar ntfs.ko tun.ko [email protected]:/data/local/kmods # chmod 775 ntfs.ko [email protected]:/data/local/kmods # chmod 775 tun.ko [email protected]:/data/local/kmods # lsmod ntfs.ko ath6kl_sdio 190837 0 - Live 0xbf081000 cfg80211 155484 1 ath6kl_sdio, Live 0xbf04c000 compat 4748 1 ath6kl_sdio, Live 0xbf044000 quick_tp 9806 0 - Live 0xbf03f000 (P) cyttsp_i2c 1347 0 - Live 0xbf039000 cyttsp_core 4862 1 cyttsp_i2c, Live 0xbf032000 hid_sony 1573 0 - Live 0xbf02c000 stuid 159606 0 [permanent], Live 0xbf000000 (P) [email protected]:/data/local/kmods # lsmod tun.ko ath6kl_sdio 190837 0 - Live 0xbf081000 cfg80211 155484 1 ath6kl_sdio, Live 0xbf04c000 compat 4748 1 ath6kl_sdio, Live 0xbf044000 quick_tp 9806 0 - Live 0xbf03f000 (P) cyttsp_i2c 1347 0 - Live 0xbf039000 cyttsp_core 4862 1 cyttsp_i2c, Live 0xbf032000 hid_sony 1573 0 - Live 0xbf02c000 stuid 159606 0 [permanent], Live 0xbf000000 (P) [email protected]:/data/local/kmods # lsmod | grep tun 1|[email protected]:/data/local/kmods # lsmod | grep ntfs 1|[email protected]:/data/local/kmods # insmod ntfs.ko [email protected]:/data/local/kmods # insmod tun.ko [email protected]:/data/local/kmods # lsmod | grep tun tun 12984 0 - Live 0xbf0e4000 [email protected]:/data/local/kmods # lsmod | grep ntfs ntfs 196520 0 - Live 0xbf0b2000 [email protected]:/data/local/kmods #
P.S. I use ES file explorer to check this and fat32 shows as usbdisk1. Usbdisk2 - 8 are empty
Sent from my Sony Tablet S using xda app-developers app
Hey kulen,
I'm glad to hear the module is loaded. I haven't tried to access an ntfs drive yet, I'll be able to test that in a couple weeks.
However, have you ensured that the drive is even mounted? I'm not sure ES file explorer can mount a device. So you'll need to mount it before accessing it.
you can check the current mounts with the command
mount
Additionally, you might be able to use fuse: forum.xda-developers.com/showthread.php?t=1724078
I've just compiled the fuse.ko module, but it should be included in the standard sony kernel. I'll post that too.
take care,
a
kulen said:
It seems it is installed now but I still can see only fat32 partition
[email protected]:/ $ export PATH=/data/local/bin:$PATH [email protected]:/ $ mkdir /data/local/kmods//mkdir failed for /data/local/kmods//, Permission denied 255|[email protected]:/ $ su [email protected]:/ # mkdir /data/local/kmods [email protected]:/ # cd /data/local/kmods [email protected]:/data/local/kmods # mv /sdcard/xda_download/tun_and_ ntfs_modules_2.6.39.4.tar /data/local/kmods failed on '/sdcard/xda_download/tun_and_ntfs_modules_2.6.39.4.tar' - Cross-device link 255|[email protected]:/data/local/kmods # mv /sdcard/xda_download/tun_and_ ntfs_modules_2.6.39.4.tar /data/local/kmods failed on '/sdcard/xda_download/tun_and_ntfs_modules_2.6.39.4.tar' - Cross-device link 255|[email protected]:/data/local/kmods # chmod 775 /data/local/kmods [email protected]:/data/local/kmods # cp /sdcard/xda_download/tun_and_ ntfs_modules_2.6.39.4.tar /data/local/kmods [email protected]:/data/local/kmods # tar -xvf tun_and_ntfs_modules_2.6.39.4.tar ntfs.ko tun.ko [email protected]:/data/local/kmods # chmod 775 ntfs.ko [email protected]:/data/local/kmods # chmod 775 tun.ko [email protected]:/data/local/kmods # lsmod ntfs.ko ath6kl_sdio 190837 0 - Live 0xbf081000 cfg80211 155484 1 ath6kl_sdio, Live 0xbf04c000 compat 4748 1 ath6kl_sdio, Live 0xbf044000 quick_tp 9806 0 - Live 0xbf03f000 (P) cyttsp_i2c 1347 0 - Live 0xbf039000 cyttsp_core 4862 1 cyttsp_i2c, Live 0xbf032000 hid_sony 1573 0 - Live 0xbf02c000 stuid 159606 0 [permanent], Live 0xbf000000 (P) [email protected]:/data/local/kmods # lsmod tun.ko ath6kl_sdio 190837 0 - Live 0xbf081000 cfg80211 155484 1 ath6kl_sdio, Live 0xbf04c000 compat 4748 1 ath6kl_sdio, Live 0xbf044000 quick_tp 9806 0 - Live 0xbf03f000 (P) cyttsp_i2c 1347 0 - Live 0xbf039000 cyttsp_core 4862 1 cyttsp_i2c, Live 0xbf032000 hid_sony 1573 0 - Live 0xbf02c000 stuid 159606 0 [permanent], Live 0xbf000000 (P) [email protected]:/data/local/kmods # lsmod | grep tun 1|[email protected]:/data/local/kmods # lsmod | grep ntfs 1|[email protected]:/data/local/kmods # insmod ntfs.ko [email protected]:/data/local/kmods # insmod tun.ko [email protected]:/data/local/kmods # lsmod | grep tun tun 12984 0 - Live 0xbf0e4000 [email protected]:/data/local/kmods # lsmod | grep ntfs ntfs 196520 0 - Live 0xbf0b2000 [email protected]:/data/local/kmods #
P.S. I use ES file explorer to check this and fat32 shows as usbdisk1. Usbdisk2 - 8 are empty
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
Sent from my Sony Tablet S using xda app-developers app
Kulen,
I've uploaded the fuse.ko, cifs.ko, and usbserial.ko modules to the first post.
Sent from my Sony Tablet S using xda app-developers app
I just tried USB OTG helper that I found in post you linked. And it did work but mounted all partitions under sdcard/usb***
strange thing is that when I reboot tablet and ntfs module is not mounted this also works?!
Thanks for all of this stuff
Sent from my Sony Tablet S using xda app-developers app
Glad to hear it's working. I think the reason this works without the ntfs module is that the fuse.ko module is compiled into the kernel by default and it takes care of this for you.
kulen said:
I just tried USB OTG helper that I found in post you linked. And it did work but mounted all partitions under sdcard/usb***
strange thing is that when I reboot tablet and ntfs module is not mounted this also works?!
Thanks for all of this stuff
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
I might be going a little off topic here.
It seems I need some more modules to make my usb modem work.
I found an app PPPWidget which should make my modem work with tablet, but I can't make it work.
This is what app creator said to somebody with same problem as mine, but other tablet:
"Make sure you have "usbserial.ko", "option.ko" and "usb_wwan.ko". The "option" module is depending on the others, at least in more recent kernel versions."
so I guess I need option.ko and usb_wwan.ko
could you provide those too?
I would be very thankful.
i don't know much about this so I don't know if you already have sources or you need me to try to find them?
thank you
Hi Kulen,
I've updated the first post to include those other modules (option.ko and usb_wwan.ko). Hopefully this will work, but let me know if there are other dependencies. Can you post a link to the thread you were referring to (where they mention those kernel modules) in case others want to know what you can do with them. Are you going to tether your tablet to a 3G device over USB? I'd like to give that a shot myself as I feel like tethering over wifi is doubly inefficient.
take care,
a
p.s. actually compiling the modules is pretty simple once the toolchain is in place. All the kernel sources are available from samsung. I'm actually compiling the modules by running make/gcc on my tablet within a debian chroot.
kulen said:
I might be going a little off topic here.
It seems I need some more modules to make my usb modem work.
I found an app PPPWidget which should make my modem work with tablet, but I can't make it work.
This is what app creator said to somebody with same problem as mine, but other tablet:
"Make sure you have "usbserial.ko", "option.ko" and "usb_wwan.ko". The "option" module is depending on the others, at least in more recent kernel versions."
so I guess I need option.ko and usb_wwan.ko
could you provide those too?
I would be very thankful.
i don't know much about this so I don't know if you already have sources or you need me to try to find them?
thank you
Click to expand...
Click to collapse
this is working!!!
here are the links:
this is software in general - http://www.draisberghof.de/usb_modeswitch/
this is android version - it includes all necessary things except kernel modules - http://www.draisberghof.de/android/pppwidget.html
this is problem I had - http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=6&t=1019
and this is my 3g modem - not important but for you to know with which modem this works for sure - http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?t=368
If posting this links is against some rules somebody please warn me or mods please delete this.
all you need is download pppwidget from market instal usbserial.ko, usb_wwan.ko and option.ko.
and of course you need to know your operator apn, username and password.
hope this can help somebody else also.
I'm "getting wings" now. I would like to make my usb dvb-t tuner work if possible
and about this modules building, it may be easy to somebody who is into linux and programming, but it still sounds as science fiction to me
hey, I've added more dvb tuner modules. Sorry about the .tar.bz2.zip file extension. XDA has a higher limit on .zip files and this file was > 8MB.
Can anyone compile ASIX AX88772B .ko module for tablet s on 2.6.39.4 ? I want to run USB-Ethernet adapter
ASIX AX88772B
Original thread (compile for Asus tf101) http://forum.xda-developers.com/showthread.php?t=1224660
Driver source attached (latest 4.4.0)
I have Sony Tablet S
kernel 2.6.39.4 unrooted
Android 4.0.3 (release5)
current module tun.ko not suitable!
Code:
insmod: init_module '/data/local/kmods/tun.ko' failed (Exec format error)
Need new modules.
Big thanks.
I'm away cureently but will look into the axis stuff when I can (2+ weeks).
As for the insmod issue, you mention you have an unrooted device? You need root to load kernel modules.
Sent from my T-Mobile G2 using xda app-developers app
Hello,
does somebody know, how to mount network shares on a phone running Android 6? Its rooted using SuperSU, Busybox installed and the Kernel supports CIFS, its listed in /proc/filesystems. Methods that seemed to work on Lollipop are failing with the error "mounting //192.168.x.x/xxx on /mnt/nas failed: Invalid argument"
Maybe someone knows a solution.
Thanks,
Witti
CyanogenMod 13.0 (cm-13.0-20160712-NIGHTLY-acclaim.zip)
su
setenforce 0
or
echo 0 > /sys/fs/selinux/enforce
getenforce
>Permissive
After that I mounted with success:
busybox mount -o rw,nolock,hard,intr,vers=3 -t nfs 192.168.1.1:/nfs4_share /storage/emulated/0/cifs/nfs4_share
But folder is empty in file managers.
"busybox mount" show two mounting points:
192.168.1.1:/nfs4_share on /storage/emulated/0/cifs/nfs4_share type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nolock,proto=tcp,port=2049,timeo=70,retrans=3,sec=sys,local_lock=all,addr=192.168.1.1)
192.168.1.1:/nfs4_share on /mnt/runtime/default/emulated/0/cifs/nfs4_share type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nolock,proto=tcp,port=2049,timeo=70,retrans=3,sec=sys,local_lock=all,addr=192.168.1.1)
"adb logcat" show:
07-13 09:37:23.461 458 458 I Binder_1: type=1400 audit(0.0:1119): avc: denied { ioctl } for path="socket:[43380]" dev="sockfs" ino=43380 ioctlcmd=7704 scontext=u:r:system_server:s0 tcontext=u:r:system_server:s0 tclass=unix_stream_socket permissive=1
I changed mounting point to /mnt/media_rw/nfs4_share, and now I have one line in "busybox mount":
192.168.1.1:/nfs4_share on /mnt/media_rw/nfs4_share type nfs (rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,nolock,proto=udp,port=2049,timeo=70,retrans=3,sec=sys,local_lock=all,addr=192.168.1.1)
And when I executed mount command over "adb shell && su", files became accessible. But I have wrong user:group on Android /mnt/media_rw/nfs4_share (uid:gid of user on PC), so some programs can't read files. But I think this must be fixed on server side in /etc/exports.
Look like root rights required to access this mount folder, can't figure out where and how properly mount it.
Same problem when I trying to mount /storage/media:
/dev/block/mmcblk0p10
/dev/block/platform/omap/omap_hsmmc.1/by-name/media
So this is more general problem with proper mounting.
Dirty hack.
mount -o remount,rw /
mkdir -p /emmc; chown -R sdcard_r:everybody /emmc
mount -o remount,ro /
busybox mount -o rw,nolock,hard,intr,vers=3,rsize=32768,wsize=32768,proto=udp,timeo=70 -t nfs 192.168.1.1:/nfs4_share /emmc
For "media" disk (/dev/block/mmcblk0p10) mounting to /emmc working too:
busybox mount -t vfat /dev/block/platform/omap/omap_hsmmc.1/by-name/media /emmc -o rw,seclabel,nosuid,nodev,noatime
Files accessible by manages and payers without root access.
On another device with CM 11 I made additional steps:
Load nfs module on Android:
modprobe nfs
Executed on "server" (my PC), to match user:group on client "sdcard_r:media_rw":
chown -R 1028:1015 /nfs4_share
And for test only:
chmod -R 0777 /nfs4_share
And what is more important executed command over SuperSu with "--mount-master" argument:
su --mount-master -c "busybox mount -o rw,nolock,hard,intr,vers=3,rsize=32768,wsize=32768,proto=udp,timeo=70 -t nfs 192.168..1:/nfs4_share /emmc"
Details: http://forum.xda-developers.com/showthread.php?t=718719&page=6
So now on this devise all programs can see files in this share too.
First, I apologize if I am writing a duplicate thread. If so, please link it.
As part of my Android-hobby-experiments with a rooted Sony Xperia Z5 Compact e5823 with Android MarshMallow, I attempted to use a partition of my external microSD card as swap area but ended up in a boot loop after reboot.
I have two partitions on the microSD card. One is fat32 and the other one is linux-swap. Both partitions were made under Debian using GParted, at different timepoints.
If I remember well, I did the following on a terminal emulator:
Code:
$ su
# mkswap /dev/block/mmcblk0p2
# swapon /dev/block/mmcblk0p2
(here I got an error. something like "Invalid argument".)
# free -m
I saw no improvement, so then I did:
Code:
$ su
# mkswap /dev/block/mmcblk0p3
# swapon /dev/block/mmcblk0p3
(here I got the same error.)
# free -m
(no improvement)
# exit
$ exit
Device was working normal after this.
Hours later, I reboot the phone (the camera sometimes crashes/freezes after taking a pic, so I took a pic, screen froze, took a screenshot, and rebooted). Then I reached a boot loop.
The screen showes the Sony Xperia logo, then the screen attempts to load the "powered-by.-ndroid-animation" but instead there is a black screen and a blinking red LED (4 times). The screen is then gray and the show repeats. I turned off the phone by opening it and disconnecting the battery
Then I took the microSD card out and the SIM card aswell. I swiched on the phone and the bootloop continued. :silly:
I can enter fastboot-mode (volume up + USB connection). Which I now use to switch off the phone instead of opening and disconnecting the battery :cyclops:.
Luckily, the device on fastboot-mode is listed the under Debian by the command
Code:
$ fastboot devices -l
, so I believe in hope to fix this boot loop w/o (re)flashing a ROM
It is also possible to run a custom recovery. I have run TWRP3.0 from this post and nilezon's version from this posts using the command
Code:
$ fastboot boot recovery.img
At the very beginning of the console of the recoveries there is an error:
Code:
Updating partition details . . .
Failed to mount '/lta-label' (No such device)
. . . done
Full SELinux support is present.
MTP Enabled
--- Update ---
I used the terminal using TWRP3.0 to read the file
Code:
/etc/fstab
and it looks as follows
Code:
/dev/block/mmcblk0p43 /system ext4 rw 0 0
/dev/block/mmcblk0p42 /data ext4 rw 0 0
/dev/block/mmcblk0p41 /cache ext4 rw 0 0
/external_sd vfat rw 0 0
/usb-otg vfat rw 0 0
/dev/block/mmcblk0p3 /firmware vfat rw 0 0
/dev/block/mmcblk0p38 /appslog ext4 rw 0 0
/dev/block/mmcblk0p40 /oem ext4 rw 0 0
/dev/block/mmcblk0p31 /persist ext4 rw 0 0
/dev/block/mmcblk0p2 /lta-label swap rw 0 0
/dev/block/mmcblk0p39 /diag ext4 rw 0 0
I decided to comment out
Code:
/dev/block/mmcblk0p2 /lta-label swap rw 0 0
and reboot. Boot loop persists in the same way and at the console of the recovery there is still, at the very beginning,
Code:
Failed to mount '/lta-label' (No such device)
I rechecked the
Code:
/etc/fstab
file and my modification was gone.
--- Update 2 ---
Today After connecting the SD card with a microSD-USB-adapter Debian shows the following error:
Code:
Error mounting /dev/sdb1 at /media/user/4C25-AD09: Command-line `mount -t "vfat" -o
"uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush" "/dev/sdb1"
"/media/jk/4C25-AD09"' exited with non-zero exit status 32: mount: /dev/sdb1: can't read superblock
Still, both partitions are recognized by GParted. "/dev/sdb1" is the fat32-partition. "/dev/sdb2" is the swap-partition. I can't access the first . . .
so I am stuck. dou you guys have any suggestion about what to try next?