Hi, i need to know why modinfo isn't working on Android and if there is someother command that replaces it?
Thanks
You can try "insmod".
It needs the path the kernel module file as parameter. E.g.
insmod /path/to/module.ko
Trying to explore / understand installed modules
st_voss said:
You can try "insmod".
It needs the path the kernel module file as parameter. E.g.
insmod /path/to/module.ko
Click to expand...
Click to collapse
I have read that to understand all the drivers / modules installed on my Android device, I must look at everything in these two directories: /system/lib/modules and /sys/module
my device has no modules directory in the /system/lib directory.
in /sys/module, I have:
kernel
printk
wakelock
userwakelock
earlysuspend
spurious
omap3epfb
keyboard
vt
bridgedriver
scsi_mod
usbcore
musb_hdrc
omap_hdq
w1_bq27000
usbhid
binder
lowmemorykiller
snd
snd_timer
snd_pcm
snd_dummy
oprofile
tcp_cubic
rfkill
pvrsrvkm
omaplfb
bc_example
tiwlan_drv
None of these directories has any files ending in .ko? Using Root Explorer to search for *.ko, finds only these:
/etc/wifi/tiwlan_drv.ko
/system/bin/sgx/omaplfb.ko
/system/bin/sgx/pvrsrvkm.ko
Can someone help me figure out how to get the equivalent of modinfo details for these?
Thanks.
Environment info:
device runs Android 2.1 I use adbKonnect to connect wirelessly with my PC
PC is running XP
This is a small mod for Sultanxda's CAF kernel. It's intended to ONLY be used with his CM 12.1 and his CM13, but it *might* work with other CAF ROMs.
The zip also replaces the fstab in the ramdisk to support the F2FS filesystem in /data and /cache (both ext4 and f2fs are supported for these, like the official CM builds), and the fsck.f2fs binary in /system/bin to the latest version (1.5.0).
The only kernel changes are:
- Added F2FS filesystem code. I keep it up-to-date with the Motorola github (right now the latest code is from the Moto X 2014 6.0 release): https://github.com/MotorolaMobilityLLC/motorola-kernel/tree/marshmallow-6.0.0-release-victara.
- Added and improved @sollapse's OTG-Y support patch.
- Eventual cherry picked commits from @sultanxda's Marshmallow branch.
- Updated CIFS/NFS code to the latest 3.4 version.
- Improved support for HIDs (joysticks, keyboards, etc.)
I compiled with GCC 4.8 (the same toolchain @sultanxda uses).
All the mods have been tested and I'm using them personally.
To install, you just need to flash his ROM, and then my zip. Then format /data and /cache to F2FS with TWRP if you wish to use F2FS.
I also made a recovery based on the 2.8.7.0-4 unofficial TWRP, it's rebased on the Sultan CM12.1 ROM and this kernel mod, plus it has:
- updated TWRP code (from the 5.1 branch)
- mounts /data and /cache as F2FS by default, with the same mount options as the fstab in my kernel mod
- theme replaced with the "Materialised Play" one
- updated mkfs.f2fs and fsck.f2fs to 1.5.0.
I included all the source code for the kernel changes, you only need to replace the GCC directory in the bash script and then execute it.
Changelogs:
01/13:
- Updated Sultan's kernel sources for CM13 and CM12.1.
- Updated NFS driver to the latest 3.4 code.
- Merged Sultan's charger improvements to the CM12.1 kernel.
- Enabled support for Force Feedback for a lot of controllers - you can enable this in Input.
- Enabled LED and Force Feedback support for the Xbox controllers (fixes the LED blinking forever).
- Fixed Wiimote support - sadly we can't have support for newer Wii Remotes (the "MotionPlus" ones) with a 3.4 kernel, but older ones are working.
- Cherry picked HID commits from the official CyanogenMod kernel, this improves the Wiimote support (Classic Controllers, Nunchucks etc. are supported) and adds/improves support for a lot of joysticks/keyboards/mice/etc.
01/05:
- Updated Sultan's kernel sources for CM13 and CM12.1.
12/30:
- Updated the F2FS driver with the one from Motorola's 6.0.0 release for Moto X 2014 (it's a couple months newer).
- Updated the fstab accordingly, the "nobarrier" option should bring a small performance improvement.
12/29:
- Actually fixed reboots when inserting OTG-Y devices in deep sleep.
- Fixed OTG-Y not starting when the charger is detected *prior* to the USB device (rare cases in which a charger/OTG-Y setup is disconnected and the driver takes a bit to detect that, and an OTG-Y setup is inserted before that).
12/23:
- Updated Sultan's kernel sources for CM13 (fixes inserting OTG devices in deep sleep and being unable to use USB again).
- Fixed reboots when inserting OTG-Y devices in deep sleep (thanks to the above patch!).
- Further clean-up of the OTG-Y patch code.
12/21:
- OTG-Y improvements and general clean-up. Code is cleaner, some race conditions and corner cases when toggling the parameter are handled better, low power mode is enabled when it's possible, and the charging notification going off, on and off again very fast sometimes after unplugging an OTG-Y setup has been fixed.
- Updated Sultan's kernel sources for CM13 and CM12.1
12/16:
- Overhaul of the OTG-Y patch. Now it's less "hacky" and it detects the charger properly. This removes the false charging notifications when connecting a regular OTG cable+device, makes it possible to use OTG again if charging is stopped and restarted, allows for faster charging rates, and fixes kernel panics when the OTG-Y cable/device are removed *after* charging was stopped.
- Updated Sultan's kernel sources for CM13 and CM12.1 (slow charging fixed)
12/12:
- Improved the OTG-Y patch (again): if you mistakenly connected a regular OTG cable+device when OTG-Y was set to Yes, a charging notification would be shown, and it wouldn't go away after disconnection. Now it properly disappears after the device has been disconnected.
12/10;
- Updated Sultan's kernel sources for CM13 and CM12.1 (including a couple changes still not present in the 12/1 CM12.1)
- Merged some changes from the CM13 kernel into the CM12.1 one: 1 2
- Improved the OTG-Y patch. It's now possible to charge the phone normally in AC mode while the OTG-Y parameter is set to Yes, and there are no more kernel panics or inability to use OTG up to the following reboot when you use OTG-Y inappropriately (disconnecting the OTG devices after changing the parameter status).
- Updated f2fs.fsck in the CM12.1 version and the init.rc in the CM13 version.
12/01:
- Updated Sultan's kernel sources for CM13 and CM12.1
11/28:
- Switched the F2FS code to the Motorola Moto G 5.1.1 F2FS branch: https://github.com/MotorolaMobilityLLC/motorola-kernel/tree/lollipop-5.0.2-release-falcon
- Updated Sultan's kernel sources for CM13
- Merged the new touchscreen fixes and CPU boosting logic to the CM12.1 kernel from the CM13 one.
Important: I'd recommend making a nandroid backup, formatting and restoring. This driver is technically older than upstream, and it might have issues with inlined dentries (the new fstab reflects the mount point configuration of the Moto X 2014 - so no inline_dentry).
11/25:
- Bug fix for F2FS from the dev-test branch
- Updated Sultan's kernel sources for CM13
- Included the touch screen bugfix from Sultan from the CM13 branch in the CM12.1 one.
11/18:
- Added other bug fix commits for F2FS from the dev-test branch
- Updated Sultan's kernel sources for both CM12.1 and CM13
- CM13 build should actually be functional now (thanks to @DerRomtester for the init.rc)
- Recovery has been rebuilt from sources, it now uses the Sultan CM12.1 kernel mod and source tree for his ROM.
11/10:
- Added two bug fix commits for F2FS from the dev-test branch (one of them is a fix to potential data corruption)
- Switched to CM's version of Google GCC
XDA:DevDB Information
Mod for Sultanxda's CAF kernel, Kernel for the OnePlus One
Contributors
Phoenix Wright
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 01/13
Stable Release Date: 2016-01-13
Created 2015-11-07
Last Updated 2016-01-13
Have you already tried marshmallow with f2fs? I dont get it working. Cache on f2fs is bootlooping and data on f2fs shows that the phone is encrypted. And it wants a pw. to decrypt it.
DerRomtester said:
Have you already tried marshmallow with f2fs? I dont get it working. Cache on f2fs is bootlooping and data on f2fs shows that the phone is encrypted. And it wants a pw. to decrypt it.
Click to expand...
Click to collapse
I'm not that interested in marshmallow right now (I'll wait until things get stable and xposed is ported over). Have you checked that the fstab is edited properly?
Phoenix Wright said:
I'm not that interested in marshmallow right now (I'll wait until things get stable and xposed is ported over). Have you checked that the fstab is edited properly?
Click to expand...
Click to collapse
The fstab should be ok. I use the same kernel in 5.1.1. I will inform you if i get it working. It is time to debug.
Hey am still facing the same error upon attempting to mount cifs. I believe it's not due to your mod but some dumb thing I might be missing. Can you post using what tools you mount cifs using the command you specified on the sultan thread?
UPDATE I tried using adb shell(which i guess you would've) and still get the same "No such device" error. dmesg doesn't show anything useful (atleast to my knowledge). But 'cat /proc/filesystems' does NOT show cifs(it does show f2fs). Is it normal?
Sent from my A0001 using Tapatalk
Links?
j1i2a3n4g5 said:
Links?
Click to expand...
Click to collapse
Check the downloads tab / section... Not sure if it works on tapatalk.
Sent from my A0001 using Tapatalk
Added to OnePlus One index thread:
[INDEX] OnePlus One
Added to OnePlus One index thread:
[INDEX] OnePlus One
Phoenix Wright said:
I'm not that interested in marshmallow right now (I'll wait until things get stable and xposed is ported over). Have you checked that the fstab is edited properly?
Click to expand...
Click to collapse
I tried sultans mm version with f2fs. And this log looks quite interesting. I am running f2fs on cache and data but it is looking for ext4.
Code:
EXT4-fs (mmcblk0p14): mounted filesystem with ordered data mode. Opts: barrier=1
fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/system,target=/system,type=ext4)=0
EXT4-fs (mmcblk0p28): VFS: Can't find ext4 filesystem
fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/userdata,target=/data,type=ext4)=-1
fs_mgr: fs_mgr_mount_all(): possibly an encryptable blkdev /dev/block/platform/msm_sdcc.1/by-name/userdata for mount /data type ext4 )
EXT4-fs (mmcblk0p16): VFS: Can't find ext4 filesystem
fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/cache,target=/cache,type=ext4)=-1
fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/platform/msm_sdcc.1/by-name/cache at /cache options: barrier=1,data=ordered,noauto_da_alloc,errors=panic error: Invalid argument
EXT4-fs (mmcblk0p15): recovery complete
EXT4-fs (mmcblk0p15): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
fs_mgr: check_fs(): mount(/dev/block/platform/msm_sdcc.1/by-name/persist,/persist,ext4)=0: Success
fs_mgr: check_fs(): unmount(/persist) succeeded
fs_mgr: Running /system/bin/e2fsck on /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck: e2fsck 1.42.9 (28-Dec-2013)
e2fsck: /dev/block/platform/msm_sdcc.1/by-name/persist: clean, 29/320 files, 1088/1280 blocks
EXT4-fs (mmcblk0p15): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nodelalloc,nomblk_io_submit,errors=panic
Edit i know the problem already
I guess it is a ramdisk problem
ramdisk/sbin/mkfs.f2fs
/system/bin/fsck\.f2fs
Formatting fo f2fs takes a long time
I tried it with the latest 12.1 ROM from 01112015 and it works very fast!
When there's trick to do it with the 6.0 ROM I will try.
ph1dft said:
I tried it with the latest 12.1 ROM from 01112015 and it works very fast!
When there's trick to do it with the 6.0 ROM I will try.
Click to expand...
Click to collapse
It works with my (Tyr) kernel and Sultans CAF 6.0 Rom.
DerRomtester said:
I tried sultans mm version with f2fs. And this log looks quite interesting. I am running f2fs on cache and data but it is looking for ext4.
Code:
EXT4-fs (mmcblk0p14): mounted filesystem with ordered data mode. Opts: barrier=1
fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/system,target=/system,type=ext4)=0
EXT4-fs (mmcblk0p28): VFS: Can't find ext4 filesystem
fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/userdata,target=/data,type=ext4)=-1
fs_mgr: fs_mgr_mount_all(): possibly an encryptable blkdev /dev/block/platform/msm_sdcc.1/by-name/userdata for mount /data type ext4 )
EXT4-fs (mmcblk0p16): VFS: Can't find ext4 filesystem
fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/cache,target=/cache,type=ext4)=-1
fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/platform/msm_sdcc.1/by-name/cache at /cache options: barrier=1,data=ordered,noauto_da_alloc,errors=panic error: Invalid argument
EXT4-fs (mmcblk0p15): recovery complete
EXT4-fs (mmcblk0p15): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
fs_mgr: check_fs(): mount(/dev/block/platform/msm_sdcc.1/by-name/persist,/persist,ext4)=0: Success
fs_mgr: check_fs(): unmount(/persist) succeeded
fs_mgr: Running /system/bin/e2fsck on /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck: e2fsck 1.42.9 (28-Dec-2013)
e2fsck: /dev/block/platform/msm_sdcc.1/by-name/persist: clean, 29/320 files, 1088/1280 blocks
EXT4-fs (mmcblk0p15): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nodelalloc,nomblk_io_submit,errors=panic
Edit i know the problem already
I guess it is a ramdisk problem
ramdisk/sbin/mkfs.f2fs
/system/bin/fsck\.f2fs
Click to expand...
Click to collapse
interesting, when I use disc info (without executing the ramdisk command) I see that both /data and /cache are show as f2fs. Curious to know if you still belief it is nessesary to solve the ramdisk problem?
---------- Post added at 02:44 PM ---------- Previous post was at 02:42 PM ----------
A question for everyone, why would you chose for f2fs on /data has it not be shown that f2fs is not faster than ext4 on /data and only has benefit on /cache?
joefso said:
interesting, when I use disc info (without executing the ramdisk command) I see that both /data and /cache are show as f2fs. Curious to know if you still belief it is nessesary to solve the ramdisk problem?
---------- Post added at 02:44 PM ---------- Previous post was at 02:42 PM ----------
A question for everyone, why would you chose for f2fs on /data has it not be shown that f2fs is not faster than ext4 on /data and only has benefit on /cache?
Click to expand...
Click to collapse
Already solved the ramdisk problem.
I think the benchmarks on android are similar. http://www.phoronix.com/scan.php?page=article&item=linux-40-ssd&num=2
Also Antutu scores are proofing that.
DerRomtester said:
It works with my (Tyr) kernel and Sultans CAF 6.0 Rom.
Click to expand...
Click to collapse
Tried the rom and it works, but not for daily use. Multirom and f2fs doesn't seem to work so back to 5.1.1. Thanx anyway!
sorry where is the download link?
manup85cupra said:
sorry where is the download link?
Click to expand...
Click to collapse
The links are on Downloads tab. Don't use Tapatalk though. This was discussed a few posts above yours.
I added a new version. I just added two bug fix commits for F2FS from the dev-test branch (one of them is a fix to potential data corruption), and switched to CM's version of Google GCC (previously I used the one from the Google repos).
Also, I added a version for CM13. Functionality of the kernel is the same (latest CIFS, UTF8, latest F2FS & fstab, OTG-Y). However, I don't use CM13 yet so I'd need testing This zip *doesn't have* an updated "fsck.f2fs" binary, as that would require downloading the CM13 source tree (25GB) and I can't do that. I'll do it when I switch to CM13. @DerRomtester I saw your kernel replaces the whole boot.img, I don't think it's wise to do (the ramdisk contains some binaries - adbd, the sepolicy binary etc. and configuration files which get updated frequently). You can use my script to automate fstab replacement if you want!
Hey @PhoenixWright I used your command
Code:
busybox mount -t cifs -o username=xxxx,password=yyyyy,rw,noatime,iocharset=utf8,noperm,nounix,noserverino,sec=ntlmssp,dir_mode=0775,file_mode=0775,uid=1023,gid=1023,context=u:object_r:fuse:s0 //192.168.x.x/yourshare /data/media/0/CIFS
after flashing your latest zip. While it mounts without any errors, the folders are not visible on any file manager.
But i can cd into the directory from terminal and it displays the files.
Any suggestions to get it viewable on file managers?