I just finished building a cifs.ko module for my motorola defy from source.
As the module has some dependencies to slow-work.ko you will need to load this prior to cifs.ko.
I finished testing it on my Motorola Defy Stock Froyo ROM (Linux version 2.6.32.9-ga28fcc4) and it worked fine. I was able to listen to music from my pc via a network share.
have fun.
tuxx
p.s. i will merge slow-work and cifs into a single module in order to be compatible with single module loading programs such as cifsmanager.
Hi,
cant wait for the merge
How about adding the nls_utf8.ko ?
nls_utf8.ko
i havent had time yet to merge cifs and slow-worker however i took a minute to build nls_utf8.ko...
i haven't tested it so please let me know if it works.. and if not i'll try to fix it (dont forget to post dmesg log)
tuxx
Thanks but... cifs.ko was already working on defy. In THIS thread its asked, and HERE said how make it work.
I did a cwm3+ flasheable zip for my own use, which I am attaching here, which I had working in CM7 until they were included.
To avoid problems with utf8 characters, in cifsManager settings, load via insmod and use path:
"/system/lib/modules/slow-work.ko:/system/lib/modules/nls_utf8.ko:/system/lib/modules/cifs.ko"
Do you really need to work to merge the files? Isn't it enough?
Perilla_ said:
Thanks but... cifs.ko was already working on defy. In THIS thread its asked, and HERE said how make it work.
I did a cwm3+ flasheable zip for my own use, which I am attaching here, which I had working in CM7 until they were included.
To avoid problems with utf8 characters, in cifsManager settings, load via insmod and use path:
"/system/lib/modules/slow-work.ko:/system/lib/modules/nls_utf8.ko:/system/lib/modules/cifs.ko"
Do you really need to work to merge the files? Isn't it enough?
Click to expand...
Click to collapse
thanks for the tip.
however I dont know how the cifs.ko of the other thread was compiled.. the thread you pasted says that a hex editor was used to change the kernel version string in the binary!?! That doesn't sound like a very nice solution. Also.. i had to port a few functions such as round_jiffie() which i saw in other build instructions was simply commented out due to laziness.. I prefer a clean build in which round_jiffie() is implemented (as i presume this is for latencies and will probably play a role for battery life etc.).
However I was unaware that you can ':' separate modules with cifsmanager. Thanks for that tip.
tuxx
p.s. if anyone is interested, i just built GNU screen for android.
Well... no, the cifs I uploaded in the zip, are from the thread that the solution said (this solution), which are from the milestone 2. HERE are the cifs for milestone 2 thread, they works with defy.
tuxx42 said:
i havent had time yet to merge cifs and slow-worker however i took a minute to build nls_utf8.ko...
i haven't tested it so please let me know if it works.. and if not i'll try to fix it (dont forget to post dmesg log)
tuxx
Click to expand...
Click to collapse
Hi,
going to test it this evening on a stock 2.6.32.9-ga28fcc4. I ll try to use the "multi:module" functionality of CIFSManager.
Perilla_ said:
Thanks but... cifs.ko was already working on defy. In THIS thread its asked, and HERE said how make it work.
Click to expand...
Click to collapse
Hi,
i thought this module was for the .29 kernel and is broken for stock 2.2.2 ?
Thats why i never bothered to try...
I used those cifs from eclair to CM7 ginger!
Related
Both VPNC (e.g. get-a-robot-vpnc) and OpenVPN require tun.ko kernel module to work. The module is included in most popular ROMs but obviously not a part of SE kernel which we have to live with now.
Loading a tun.ko compiled for other kernels fails with a following message, for example:
adb shell dmesg
"tun: version magic '2.6.29-01117-g4bc62c2 preempt mod_unload ARMv7' should be '2.6.29-rel preempt mod_unload ARMv7".
I tried to see if I could compile the module myself from the posted SE kernel source and using this post as a reference - forum.xda-developers.com/showpost.php?p=5692491&postcount=12, but I'm lost in git and cross-compile toolchain. I also tried changing "2.6.29-01117-g4bc62c2" to "2.6.29-rel" in the existing module with a hex editor, but that made the module invalid.
So, I wonder if someone could help?
Thanks.
crimper said:
Both VPNC (e.g. get-a-robot-vpnc) and OpenVPN require tun.ko kernel module to work. The module is included in most popular ROMs but obviously not a part of SE kernel which we have to live with now.
Loading a tun.ko compiled for other kernels fails with a following message, for example:
adb shell dmesg
"tun: version magic '2.6.29-01117-g4bc62c2 preempt mod_unload ARMv7' should be '2.6.29-rel preempt mod_unload ARMv7".
I tried to see if I could compile the module myself from the posted SE kernel source and using this post as a reference - forum.xda-developers.com/showpost.php?p=5692491&postcount=12, but I'm lost in git and cross-compile toolchain. I also tried changing "2.6.29-01117-g4bc62c2" to "2.6.29-rel" in the existing module with a hex editor, but that made the module invalid.
So, I wonder if someone could help?
Thanks.
Click to expand...
Click to collapse
you need to recompile the kernel module (luckily kernel sources are available)
Please help
I don't know how to recompile kernel. Can you send this file here into forum? And tell us, inferior people who just want to use openvpn, how to put this file there it should be?
Why every linux/unix issue ends with advice "just recompile kernel" or "RTFM"... I don't know how to recompile it and don't know where is that f...g manual. If you mean google, please don't say that.
Thank you very much
pepouwek said:
I don't know how to recompile kernel. Can you send this file here into forum? And tell us, inferior people who just want to use openvpn, how to put this file there it should be?
Why every linux/unix issue ends with advice "just recompile kernel" or "RTFM"... I don't know how to recompile it and don't know where is that f...g manual. If you mean google, please don't say that.
Thank you very much
Click to expand...
Click to collapse
luckily for you, I made a guide in this board about how to recompile the kernel
Also in this topic about recompiling the kernel and there's infos about openvpn there too (search button will help).
And don't talk about inferior people, I really wish it was very easy to add all those stuffs but unluckily it's not. I can help you even if you're lost about kernel recompiling but I can't do all the stuffs for you.
how about searching instead of opening new thread......
http://forum.xda-developers.com/showpost.php?p=7054292&postcount=17
someone close this useless thread....
pepouwek said:
I don't know how to recompile kernel. Can you send this file here into forum? And tell us, inferior people who just want to use openvpn, how to put this file there it should be?
Why every linux/unix issue ends with advice "just recompile kernel" or "RTFM"... I don't know how to recompile it and don't know where is that f...g manual. If you mean google, please don't say that.
Thank you very much
Click to expand...
Click to collapse
We can't use a different kernel to the stock one yet, and there's no point in recompiling the 2.6.29 kernel again, as the devs are trying to run the 2.6.32 one instead for froyo - tun.ko probably should be compiled with this instead. (in fact, I think froyo is able to be run already)
I think the custom spl/bootloader now needs to be tweaked by goroh_kun, Bin4ry, jerpelea etc. to:
- Be autobooted or flashed safely
- To be stable when run
- To be able to boot to a recovery partition and/or bootloader with a key combination
Also, I think they need to:
-Sort out phone partitioning to be used with the new bootloader and recovery image.
-Then try to fix bugs in the CyanogenMod 6 rom, if there are any 'major' ones.
I think that's what the devs are trying to do.
@hunteron you are not completely right even though you can't boot a complete kernel image you can insert your own modules
Sent from my X10i using XDA App
sim-value said:
@hunteron you are not completely right even though you can't boot a complete kernel image you can insert your own modules
Sent from my X10i using XDA App
Click to expand...
Click to collapse
I'm sorry; you're right.
Mod. edit: reuse existing thread pls; CLOSED
Hello,
I'm interested in compiling the tun.ko driver necessary for OpenVPN. However, I got stuck when trying to pull the config.gz file from /proc/ since Motorola didn't include it as an option.
I'm not great with all this and was just following a guide. Has anyone created a working .config file that I could use instead?
Thanks
Isn't any config included?
have you tried make oldconfig?
pajn said:
Isn't any config included?
have you tried make oldconfig?
Click to expand...
Click to collapse
I thought you needed the config.gz file (and the resultant .config) pulled from the phone to use make oldconfig?
Yes. But there should be one included or else we have to complain to Motorola.
The config is included in the binary so it have to be provided together with the source to follow GPL
The default configuration in the kernel source should be okay.
I'll compile that later for you
kholk said:
The default configuration in the kernel source should be okay.
I'll compile that later for you
Click to expand...
Click to collapse
Awesome thank you.
Emh, as the default kernel configuration says, the TUN/TAP interface driver is already included into the kernel. You don't need a module.
kholk said:
Emh, as the default kernel configuration says, the TUN/TAP interface driver is already included into the kernel. You don't need a module.
Click to expand...
Click to collapse
So you're saying even though I don't see tun.ko listed in the filesystem that I should be able to initiate TUN when configuring OpenVPN?
Thanks
try it,it working for my razr.
Kernal 2.6.35.7
View attachment tun_gb.ko.zip
Yes you're able to create a TUN/TAP device without tun.ko.
kholk said:
Yes you're able to create a TUN/TAP device without tun.ko.
Click to expand...
Click to collapse
My apologies. On my last phone I had to have a tun.ko module. My understanding after searching these past few days is most phones require it to be built. Is the RAZR different by having it built into the stock kernel?
By the way, finally got OpenVPN working today.
Thanks
Yup, it seems Moto wanted to include support for VPNs on stock!
What does this do? Sorry not familiar with this
Sent from my DROID RAZR using xda premium
blkghost22 said:
What does this do? Sorry not familiar with this
Sent from my DROID RAZR using xda premium
Click to expand...
Click to collapse
It lets you setup a VPN connection from your phone to another server. Basically, your phone encrypts all your data before going to Verizon, etc. then it arrives at (in my situation) my home router which decrypts it then sends the request out to the internet, and back to my phone encrypted and so on.
It's useful for:
1) I can access my home network from anywhere as if I were at home connected to my router over Wifi
2) If I'm out at a hotel or something and I want to use the Wifi to access a bank account or something without worrying about someone else on the network stealing my password.
Just to name a few.
Has anyone gotten cisco annyconnect working on the razr?
I needed a working cifs module for my view and decided to provide modules that people in the other thread were looking for as well.
cifs performed well in both kernels. References to slow_work have been removed.
Honestly, I didn't test tun.ko or nls_utf8.ko other than to make sure that they went through insmod with out any errors. The HC kernel seems to already have tun compiled in to the kernel as the dmesg error said it already existed. YMMV.
I based the update zips off of LeeDroid's last go at it, so thanks to him for that.
With this, the update zips support init.d, but unless you have it, you'll have to do an insmod when needed. I use CIFSManager from the market for cifs. Be sure to go through the settings to load the module as needed.
Here are the goodies:
For GB - Kernel 2.6.35.10-g5b3e78b:
flashable zip here (updated link 3/24/13)
includes:
cifs.ko
tun.ko
nls_utf8.ko
For HC - Kernel 2.6.35.10-g238a0bf:
flashable zip here (updated link 3/24/13)
includes:
cifs.ko
nls_utf8.ko
(does not include tun.ko for reasons stated above)
You're on your own with these from now on. Good luck!
FrakMe
PS: if the links die again, just send me a pm to let me know.
FrakMe said:
I needed a working cifs module for my view and decided to provide modules that people in the other thread were looking for as well.
cifs performed well in both kernels. References to slow_work have been removed.
Honestly, I didn't test tun.ko or nls_utf8.ko other than to make sure that they went through insmod with out any errors. The HC kernel seems to already have tun compiled in to the kernel as the dmesg error said it already existed. YMMV.
I based the update zips off of LeeDroid's last go at it, so thanks to him for that.
With this, the update zips support init.d, but unless you have it, you'll have to do an insmod when needed. I use CIFSManager from the market for cifs. Be sure to go through the settings to load the module as needed.
Here are the goodies:
For GB - Kernel 2.6.35.10-g5b3e78b:
flashable zip here
includes:
cifs.ko
tun.ko
nls_utf8.ko
For HC - Kernel 2.6.35.10-g238a0bf:
flashable zip here
includes:
cifs.ko
nls_utf8.ko
(does not include tun.ko for reasons stated above)
You're on your own with these from now on. Good luck!
FrakMe
Click to expand...
Click to collapse
So do these work or are you just posting them to let people build off of?
Thank you sooo much.
Works on my stock HC.
Been waiting a long time for this. My view is finally perfect.
spartan1987 said:
So do these work or are you just posting them to let people build off of?
Click to expand...
Click to collapse
They work, at least as far as I can test tun and nls_utf8.
I'm using the cifs module now on my hc view.
I just don't plan to do a lot of maintenance/updates on them. I used the flyer hc and view gb kernels from htcdev, if you were wondering.
x51 said:
Thank you sooo much.
Works on my stock HC.
Been waiting a long time for this. My view is finally perfect.
Click to expand...
Click to collapse
Your welcome.
I'm glad someone besides me found them useful.
I reverted my View running ViperRom to Stock GB and these modules are working.... I am restoring my apps from a TitaniumBackup directory on a WDMyBookLive now! Thanks so much!
For those of you that have the openvpn working, can you get all your internet traffic routed thru the vpn tunnel? I install the openvpn-installer-0.2.4.apk and openvpn-settings-0.4.9.apk, got error and couldn't connect. I then substituted the openvpn binary from the openvpn-static-2.1.1.bz2, and am able to connect to the openvpn server, but I keep getting the "connecting" or "connected" message in the status bar, and all my internet traffics don't seem to go thru the tunnel. Anyone has the same problem?
I have a View running HC at the moment.
coolbird said:
For those of you that have the openvpn working, can you get all your internet traffic routed thru the vpn tunnel? I install the openvpn-installer-0.2.4.apk and openvpn-settings-0.4.9.apk, got error and couldn't connect. I then substituted the openvpn binary from the openvpn-static-2.1.1.bz2, and am able to connect to the openvpn server, but I keep getting the "connecting" or "connected" message in the status bar, and all my internet traffics don't seem to go thru the tunnel. Anyone has the same problem?
I have a View running HC at the moment.
Click to expand...
Click to collapse
This isn't the place for that question. Might want to try the Q&A board.
Does anyone still have a copy of these? Specifically the HC ones? Original link no longer works. Thanks.
tselling said:
Does anyone still have a copy of these? Specifically the HC ones? Original link no longer works. Thanks.
Click to expand...
Click to collapse
Sorry for the wait, I don't frequent this forum.
I re-uploaded the files to a new host and updated the links in the OP.
Good luck.
FrakMe said:
Sorry for the wait, I don't frequent this forum.
I re-uploaded the files to a new host and updated the links in the OP.
Good luck.
Click to expand...
Click to collapse
Thanks.
---------- Post added at 05:37 PM ---------- Previous post was at 05:14 PM ----------
FrakMe said:
Sorry for the wait, I don't frequent this forum.
I re-uploaded the files to a new host and updated the links in the OP.
Good luck.
Click to expand...
Click to collapse
Hi, The Honeycomb file appears to be the wrong one. Its and exe file and when opened doesn't have the drivers.. has some other stuff. Could you check on that please. Thanks..
tselling said:
Thanks.
---------- Post added at 05:37 PM ---------- Previous post was at 05:14 PM ----------
Hi, The Honeycomb file appears to be the wrong one. Its and exe file and when opened doesn't have the drivers.. has some other stuff. Could you check on that please. Thanks..
Click to expand...
Click to collapse
The link does indeed go to the correct zip file. View-stock_hc-CIFS-UTF8-FrakMe.zip
Use the "continue as free user" option on sockshare instead of the top one with their downloader.
I decided to make my first custom rom. The main difference over klin1344's klassic is the fact that we can customize what we want with the aroma installer. As of now, there's no customised interface (and there will not be. Consider this like WT Ho's rom for the 5.0).
I stop working on it because I want to try something other than stock. Also thanks for your consideration for this rom. (I will continue the maintenance of it though)
Features:
- Stock 2.3.6 XXKPQ
- Rooted
- Busybox
- Deodexed
- Zipaligned
- Aroma installer: An interactive installer
- Multiple bootanimations.
- Choice between TW 3.0, TW 4.5, Go launcher EX, Xperia S launcher
- Possibility to install DSP manager and voodoo app (for sound enchance)
- Features the CWM 5.0.2.7 (Intl Only. Kernel based from steve's 3.0) (V.1.0)
- US users will recieve the latest klin's R2 custom kernel* (V.1.0).
- Intl and US compatibility in a single zip. (v.2.0)
- SuperSU (v.3.0)
Changelog:
Code:
[B]V.3.0 (Vita) FINAL [/B]
- Deodexed and Zipaligned
- SuperSU is used instead of SuperUser
- Updated Google Play Store, Maps and Youtube app (Can play 720p) (It's real this time)
- Possibility to add Antutu Cpu Master Free (For Overclock)
[B]V.2.0 (Radiance)[/B]
- Name changed only to Renaissance
- Possibility to chose the device type (Thanks to dark_valor's Terra Silent)
- New Honeycomb bootanimation
- Possibility to add terminal to the rom
[B]v.1.0 (Etincelle)[/B]:
- Initial Release.
Download:
1.0
Intl: Intl Renaissance 1.0 Download
US: US Renaissance 1.0 Download
2.0: Renaissance 2.0 Download
3.0: Renaissance 3.0 Download
If you want there's the Xperia S Wallpapers: Xperia S Wallpapers Download
If there's a problem with antutu, install the apk here: Cpu Master Apk Download
If there's a problem with terminal reinstall it.
Instructions:
1. Boot into Cwm
2. Backup
3. Wipe data (BEFORE IT IS MANDATORY)
4. Run renaissance-device.zip
5. Follow the instructions.
6. Reboot
7. Enjoy!
If you do like please hit thanks button. If you have problem with installation, Send me .log file in aroma. If it's problem with the rom please let me know.
Thanks to:
amarullz: for Aroma installer
Klin1344, SteveS and stratosk for the kernel related things.
WT Ho for his base for aroma installer. (and help too )
GO Dev Team , Fr4gg0r and ra3al for their launcher
Dark_balor for his kernel (terra silent)
Jackpal for the terminal emulator
Antutu for the CPU Master
As this is the last version, If you want to use something in the rom (porting) ask me first.(Mostly for Aroma)
These are the possible implementations (suggestions)
- Deodex
- Performance tweaks
- More customisation options
- Better compatibility with apps (Like deviceID hack)
reserved again
screenshots please?
EcHoFiiVe said:
screenshots please?
Click to expand...
Click to collapse
Oh sorry about that. I will put them tomowrrow. (that depends which screenshots you want?)
Is ext4 enabled for data and dbdata? From stock its stuck at rfs.
Wheatly said:
Is ext4 enabled for data and dbdata? From stock its stuck at rfs.
Click to expand...
Click to collapse
Well I didin't enable ext4 so data and dbdata will be stuck at rfs. Sorry about that.
Does the CWM 5 in the kernel I gave you work well? Because when I gave it to you there seemed to be a lot of errors... But if it does, I'll probably apply those changes back to my kernel again and update to cwm 5 because it allows easier converting to ext4. Also, did stratosk give you permission because I used his cwm recovery files from his sources. (just making sure, so he doesn't come and flame me for porting cwm5 from his sources without permission)
Sent using Tapatalk
When you sent it to me back then it wasn't working well. So I fixed the errors on it (I did send a PM for you for testing). I do got permission from stratosk (that's why I put him in the thanks section.) I think I have the US kernel in my mediafire account. I'll upload it so both devices will have justice.
zaclimon said:
When you sent it to me back then it wasn't working well. So I fixed the errors on it (I did send a PM for you for testing). I do got permission from stratosk (that's why I put him in the thanks section.) I think I have the US kernel in my mediafire account. I'll upload it so everyone will have justice.
Click to expand...
Click to collapse
Ok thanks. But how exactly did you fix it? I didn't flash the kernel you gave me but where are your sources? (the Linux kernel is GPL licensed, so it's mandatory to have a source )
Sent using Tapatalk
Never mind for now I will just extract the initrd from your kernel and use git to track the changes from the one I sent to you.
But really, you need to provide a source if you release a kernel, as per the GPL license.
Sent using Tapatalk
From which release of the Klin rom you based yours ?
If it's from the R5, did you had the font that were missing ?
Is it supercharged ?
For the kernel I'm also curious to know what are the change you have done
Dark_Balor said:
From which release of the Klin rom you based yours ?
If it's from the R5, did you had the font that were missing ?
Is it supercharged ?
For the kernel I'm also curious to know what are the change you have done
Click to expand...
Click to collapse
He based it off stock rom. Tomorrow I'll figure out how he fixed cwm 5.0.2.7 from his initramfs.
Sent using Tapatalk
klin1344 said:
Never mind for now I will just extract the initrd from your kernel and use git to track the changes from the one I sent to you.
But really, you need to provide a source if you release a kernel, as per the GPL license.
Sent using Tapatalk
Click to expand...
Click to collapse
I had the source before but my ubuntu 12.04 bugged with my old computer (nvidia problem) so I downloaded 11.04 but I forgot to do a backup.
zaclimon said:
I had the source before but my ubuntu 12.04 bugged with my old computer (nvidia problem) so I downloaded 11.04 but I forgot to do a backup.
Click to expand...
Click to collapse
If you can extract the initramfs then that's basically your source because cwm is only an initramfs change.
But again, how did you do it? Surely you remember what changes you did? It sounds like a minor tweak because you sent me your kernel a matter of hours after I sent you mine.
Btw, you know that you can downgrade ubuntu without losing data right? Ndiswrapper wasn't working on 12.04 so I put my 11.04 disc in and was able to install without losing all my personal files.
Sent using Tapatalk
klin1344 said:
If you can extract the initramfs then that's basically your source because cwm is only an initramfs change.
But again, how did you do it? Surely you remember what changes you did? It sounds like a minor tweak because you sent me your kernel a matter of hours after I sent you mine.
Btw, you know that you can downgrade ubuntu without losing data right? Ndiswrapper wasn't working on 12.04 so I put my 11.04 disc in and was able to install without losing all my personal files.
Sent using Tapatalk
Click to expand...
Click to collapse
I made some changes to the init.rc and lpm.rc I think.
Screenshots like Homescreen, App drawer, Notification place thingy, and settings.
EcHoFiiVe said:
Screenshots like Homescreen, App drawer, Notification place thingy, and settings.
Click to expand...
Click to collapse
Because it is a stock rom (with multiple apps) I won't put screenshots. Once 2.0 will be released (UI modifications) I will put them. You can backup and try it?
zaclimon said:
When you sent it to me back then it wasn't working well. So I fixed the errors on it (I did send a PM for you for testing). I do got permission from stratosk (that's why I put him in the thanks section.) I think I have the US kernel in my mediafire account. I'll upload it so both devices will have justice.
Click to expand...
Click to collapse
zaclimon said:
I made some changes to the init.rc and lpm.rc I think.
Click to expand...
Click to collapse
Ok, I just used git to check your initramfs for your INTL kernel, and lpm.rc is exactly the same as my source, and in init.rc it's also the exact same thing as my source for the CWM 5.0.2.7 beta (not on github anymore), except that you forgot a '/' in enabling bootanimation support.
So I'm confused. When I gave you my kernel, there seemed to be many errors because I was screwing with my partition filesystems, and also got a lot of "md5 mismatches" when trying to convert, so I decided to stop and work on other things. You got it working, and you claimed that you "fixed the errors in init.rc and lpm.rc" without proof with a proper source when you CHANGED NOTHING AT ALL. You probably just got lucky with CWM restoring and no md5 mismatches like I had. So you're releasing a kernel with a CWM 5 port that I completely did, and claiming that YOU fixed most of the errors and got it working when proof shows that all you did was download my source before I deleted it and simply compiled them with SteveS's one click compiling script.
And since you don't have a Github account or a source of any sort, you thought you could get away with tricking everybody that you "fixed the CWM errors", when the work was originally done by me. You changed nothing at all. It was not my intention to flame you, but seriously, I am disapointed . I'm really discouraged and very tempted to just take down all my work for the Galaxy Player and just keep all the development to myself. Maybe that's why precious devs keep leaving XDA because people just use someone else's work and package it as their own. Learn to give proper credit to other people, and if you really didn't make something, don't act or say that you did.
Ok, I'm done. Really needed to vent.
klin1344 said:
Ok, I just used git to check your initramfs for your INTL kernel, and lpm.rc is exactly the same as my source, and in init.rc it's also the exact same thing as my source for the CWM 5.0.2.7 beta (not on github anymore), except that you forgot a '/' in enabling bootanimation support.
So I'm confused. When I gave you my kernel, there seemed to be many errors because I was screwing with my partition filesystems, and also got a lot of "md5 mismatches" when trying to convert, so I decided to stop and work on other things. You got it working, and you claimed that you "fixed the errors in init.rc and lpm.rc" without proof with a proper source when you CHANGED NOTHING AT ALL. You probably just got lucky with CWM restoring and no md5 mismatches like I had. So you're releasing a kernel with a CWM 5 port that I completely did, and claiming that YOU fixed most of the errors and got it working when proof shows that all you did was download my source before I deleted it and simply compiled them with SteveS's one click compiling script.
And since you don't have a Github account or a source of any sort, you thought you could get away with tricking everybody that you "fixed the CWM errors", when the work was originally done by me. You changed nothing at all. It was not my intention to flame you, but seriously, I am disapointed . Maybe that's why precious devs keep leaving XDA because people just use someone else's work and package it as their own. Learn to give proper credit to other people, and if you really didn't make something, don't act or say that you did.
Ok, I'm done. Really needed to vent.
Click to expand...
Click to collapse
ok don't go blaming me BECAUSE IT GOT ERRORS when YOU sent it to me. I corrected some errors but I can't remember which ones is it. I can't get lucky if EVERY of my backups works(Because I got errors for md5 mismatch as well too). It is sure that your init files are the same because I used some of the text you used when you were building YOUR R1 kernel. (so basically I used some of your sources) but you were always complaining about ext4 not working so you gave up on CWMR5.0. and when I said I've fixed them you didin't tested it. DON'T GO COMPLAINING IF YOU DIDIN'T EVEN TESTED IT. (also check all the init files to be sure and also check the thanks it is `kernel related things`.) -___-
EDIT: If you want all the credits. You can have them. I should have said that you made all the changes but the problem was that you gave up on CWMR5.0 so I was like (The kernel works now but I won't release it because you already have your custom kernel with CWMR3.)
Hello,
today I got my update to 4.1.1. Besides a few minor issues the biggest problem is that the Transformer reboots when I start cifs manager.
There were no more reboots after I renamed cifs.ko and md4.ko but of course I coudn't mount any shares without the modules. I searched around and found something for the Nexus which didn't work either but nothing for the Transformer yet.
Any idea where I can find them? Some threads show that others got the updates a bit earlier, so perhaps the modules are already around somewhere. Or would some kind soul compile them if they don't yet exist?
Many thanks
Armin
by the way: Is there a way to stop the almost permanent update notifications? I would have liked to wait with the update but it is impossible to really work with the tablet because every few minutes it asks again if I would like to update -- even though I selected "wait for a day".
So I gave up after some time and allowed the update and now I don't have cifs mounts any longer...
I got same Problem, too. Maybe a custom kernel for stock rom?
Keron23 said:
I got same Problem, too. Maybe a custom kernel for stock rom?
Click to expand...
Click to collapse
I would look at the custom roms that have CIFS capabilities, download them and pick them apart with blobtools2 and ext2explorer.exe to see what modules you can poach for the stock rooted rom you are running.
Perhaps though a simple post in the thread or email to the author might yield the modules you need without that work.
hx4700 Killer said:
I would look at the custom roms that have CIFS capabilities, download them and pick them apart with blobtools2 and ext2explorer.exe to see what modules you can poach for the stock rooted rom you are running.
Click to expand...
Click to collapse
I tried this one: http://forum.xda-developers.com/showthread.php?t=1803557 but could not find a cifs.ko in it. Do you know
one that has the modules?
hx4700 Killer said:
Perhaps though a simple post in the thread or email to the author might yield the modules you need without that work.
Click to expand...
Click to collapse
Tried that too, I asked someone who provided an earlier version in a PM -- but no answer yet.
So, still no luck and hoping for someone to just post the beasts...
armin58 said:
I tried this one: http://forum.xda-developers.com/showthread.php?t=1803557 but could not find a cifs.ko in it. Do you know
one that has the modules?
Tried that too, I asked someone who provided an earlier version in a PM -- but no answer yet.
So, still no luck and hoping for someone to just post the beasts...
Click to expand...
Click to collapse
Here you go.
flumpster said:
Here you go.
Click to expand...
Click to collapse
Thanks a lot, works great!
Now cifs modules works on JB stock for unlocked devices without any crashes. Thanks a lot.