Related
Compiling Pershoot's Vision Kernel for CyanogenMod 7
Why would I do this?
1. You must enjoy punishment
2. You want to know how a kernel gets compiled for Android.
3. You want to modify your kernel somehow, such as adding the Interactive Scheduler to the default Pershoot config or switching between CFS and BFS.
4. You want to modify the overclocking frequencies or voltages.
I don't teach how to do anything but #1 and 2, the rest I might get into later, but this guide is the gateway to all that.
You will need a working Ubuntu system. 10.04, 10.10, or 11.04 should all be fine. I did it with 11.04, so bleeding edge is working 100%.
On Ubuntu 10.04 and 10.10, get the following packages:
Code:
sudo apt-get install git-core gnupg sun-java6-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev
On Ubuntu 11.04 get:
Code:
sudo apt-get install git-core gnupg openjdk-6-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev
Let's create our compilation area:
Code:
cd ~
mkdir kernel-compilation
mkdir kernel-compilation/toolchain
mkdir kernel-compilation/finals
mkdir kernel-compilation/staging
Download the following files:
http://www.mediafire.com/file/5aqhkl69fq75253/arm-eabi-4.3.1.zip - Unzip to ~/kernel-compilation/toolchain
http://www.mediafire.com/file/7lo2ctg7r56urky/staging.zip - Unzip to ~/kernel-compilation/staging
And lastly, grab the source from Pershoot's GIT, which will end up in kernel-compilation/vision-2632:
Code:
cd ~/kernel-compilation/
git clone https://github.com/pershoot/vision-2632.git -b gingerbread
Next we'll set up the compiler to use the ARM toolchain through an environment variable to make it easier later:
Code:
export CCOMPILER=~/kernel-compilation/toolchain/arm-eabi-4.3.1/bin/arm-eabi-
Next we'll use Pershoot's default configuration file as a starting point:
Code:
cd ~/kernel-compilation/vision-2632
cp arch/arm/configs/pershoot_vision_defconfig .config
If you wish to modify his configuration:
Code:
make ARCH=arm CROSS_COMPILE=$CCOMPILER menuconfig
Next we'll compile the newly configured kernel:
Code:
make ARCH=arm CROSS_COMPILE=$CCOMPILER -j4 (replace 4 with the number of physical processor cores on your system, or leave the -j option off altogether if you don't know)
And the modules:
Code:
make ARCH=arm CROSS_COMPILE=$CCOMPILER modules
Now we'll start installing the kernel into our staging area.
Copy the kernel image from the source area into staging:
Code:
cp arch/arm/boot/zImage ~/kernel-compilation/staging/kernel/zImage
and install the modules (and fix where it puts them):
Code:
make ARCH=arm INSTALL_MOD_PATH=~/kernel-compilation/staging/system modules_install
cp ~/kernel-compilation/staging/system/lib/modules/2.6.32.38-cyanogenmod/kernel/drivers/net/wireless/bcm4329/bcm4329.ko ~/kernel-compilation/staging/system/lib/modules/bcm4329.ko
rm -rf ~/kernel-compilation/staging/system/lib/modules/2.6.32.38-cyanogenmod
Now let's finish up by zipping it all into the finals area:
Code:
cd ~/kernel-compilation/staging
zip -r ~/kernel-compilation/finals/mykernel.zip *
Now go to your finals directory and get to flashing!
References:
http://wiki.cyanogenmod.com/index.php?title=Building_Kernel_from_source
http://forum.xda-developers.com/showthread.php?t=916198#
Thanks to Pershoot, CyanogenMod Team, and everybody on #cyanogenmod on Freenode IRC.
you da man.
jbdubbs said:
Compiling Pershoot's Vision Kernel for CyanogenMod 7
Thanks to Pershoot, CyanogenMod Team, and everybody on #cyanogenmod on Freenode IRC.
Click to expand...
Click to collapse
dude, this is one amazingly simple tutorial I have almost zero ubuntu experience, and i have literally NEVER created my own anything for my phone, much less something as seemingly complex as the base kernel, but your easy walkthrough made it one of the easiest things Ive ever done, and now I have a working kernel with all the features i was looking for but never knew how to make myself
EDIT: may have spoken too soon. The kernel compiled fine and booted fine, but when i look for my added governors (interactive and conservative) in the listings, they dont appear there. any thoughts on what I need to do?
Am I right in assuming that the CPU frequencies/voltages are in /arch/arm/mach-msm/acpuclock-7x30.c , and that modifying those values in gedit (default program that opened when I doubleclicked it) would stick once I compile the kernel?
jmwils3 said:
dude, this is one amazingly simple tutorial I have almost zero ubuntu experience, and i have literally NEVER created my own anything for my phone, much less something as seemingly complex as the base kernel, but your easy walkthrough made it one of the easiest things Ive ever done, and now I have a working kernel with all the features i was looking for but never knew how to make myself
EDIT: may have spoken too soon. The kernel compiled fine and booted fine, but when i look for my added governors (interactive and conservative) in the listings, they dont appear there. any thoughts on what I need to do?
Click to expand...
Click to collapse
I'm assuming that you did the 'make ARCH=arm menuconfig' step and didn't properly save your changes. When you exit the menu it'll ask if you'd like to save, obviously select 'yes'. Don't choose the option to save an alternate config at the bottom of the main menu, just keep hitting exit until it asks to explicitly.
Sent from my HTC Vision using XDA App
qzfive said:
Am I right in assuming that the CPU frequencies/voltages are in /arch/arm/mach-msm/acpuclock-7x30.c , and that modifying those values in gedit (default program that opened when I doubleclicked it) would stick once I compile the kernel?
Click to expand...
Click to collapse
The short answer is yes, the long answer is that while that is indeed where the frequencies and voltages are stored, its pretty greek to me. I attempted to copy the 1.9 ghz acpuclock-7x30.c from another post on this forum and it doesn't seem like it compiled it, I still only made it to 1.5.
I'm going to investigate both this and where exactly the smartass governor source is and update this guide later.
Sent from my HTC Vision using XDA App
jbdubbs said:
I'm assuming that you did the 'make ARCH=arm menuconfig' step and didn't properly save your changes. When you exit the menu it'll ask if you'd like to save, obviously select 'yes'. Don't choose the option to save an alternate config at the bottom of the main menu, just keep hitting exit until it asks to explicitly.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
-facepalms- duh, that would make sense. So is there any way to undo the mistake, or would i need to start from scratch? not that bad either way, just wondered
jmwils3 said:
-facepalms- duh, that would make sense. So is there any way to undo the mistake, or would i need to start from scratch? not that bad either way, just wondered
Click to expand...
Click to collapse
You can run 'make clean' then continue from the menuconfig step.
Sent from my HTC Vision using XDA App
jbdubbs said:
You can run 'make clean' then continue from the menuconfig step.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Im sorry for the extremely noob-ish questions (havent felt this noob-ish since my pre-root days on my FIRST G2), but do you mean to run that command on the created zip file, or elsewhere?
jmwils3 said:
Im sorry for the extremely noob-ish questions (havent felt this noob-ish since my pre-root days on my FIRST G2), but do you mean to run that command on the created zip file, or elsewhere?
Click to expand...
Click to collapse
Run that command from ~/kernel-compilation/vision-2632
Sent from my HTC Vision using XDA App
jbdubbs said:
Run that command from ~/kernel-compilation/vision-2632
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
it keeps giving me an error that the selected location is a directory.
jmwils3 said:
it keeps giving me an error that the selected location is a directory.
Click to expand...
Click to collapse
cd ~/kernel-compilation/vision-2632
make clean
make ARCH=arm CROSS_COMPILE=$CCOMPILER menuconfig
Sent from my HTC Vision using XDA App
lol, thanks i had found my mistake, and i just started it from after where it had me retrieve the files (which of course, i already had from before) and it got me to the right place to run the command. everything seems to have worked, but ill see once my phone boots.
EDIT: that did it! thanks again, bro
Instead of:
Code:
make ARCH=arm CROSS_COMPILE=$CCOMPILER -j4 (replace 4 with the number of physical processor cores on your system, or leave the -j option off altogether if you don't know)
You can use this:
Code:
make ARCH=arm CROSS_COMPILE=$CCOMPILER -j`grep 'processor' /proc/cpuinfo | wc -l`
that will put the right value based on your processor.
Out of curiosity, why is the interactive governor & others left out of pershoot's kernel in the first place?
I'm wondering if there are compatibility issues or other optimisations with undervolting etc and you may be running the risk of causing problems/damage to your hardware.
Droid Basement said:
Note:
If you use SetCPU, please do not set any Advanced settings, and you should use the ondemand CPU governor.
Click to expand...
Click to collapse
I only ask as, in pershoot's kernel the sysfs cpufreq directory differs from what seems the norm (from what I've seen); There are two cpufreq directories in (cpu & cpu0), but we only have one processor?
Dunno, maybe I'm just being paranoid and need to download the source and investigate...
waydownsouth said:
Instead of:
Code:
make ARCH=arm CROSS_COMPILE=$CCOMPILER -j4 (replace 4 with the number of physical processor cores on your system, or leave the -j option off altogether if you don't know)
You can use this:
Code:
make ARCH=arm CROSS_COMPILE=$CCOMPILER -j`grep 'processor' /proc/cpuinfo | wc -l`
Click to expand...
Click to collapse
Yeah I left that out for simplicity of the guide. Most people should know how many cores they have.
Out of curiosity, why is the interactive governor & others left out of pershoot's kernel in the first place?
I'm wondering if there are compatibility issues or other optimisations with undervolting etc and you may be running the risk of causing problems/damage to your hardware.
I only ask as, in pershoot's kernel the sysfs cpufreq directory differs from what seems the norm (from what I've seen); There are two cpufreq directories in (cpu & cpu0), but we only have one processor?
Dunno, maybe I'm just being paranoid and need to download the source and investigate...
Click to expand...
Click to collapse
I actually have some issues using BFS (his default scheduler) with the interactive governor regarding stability. I'm assuming that BFS is the culprit for leaving it out.
Sent from my HTC Vision using XDA App
jbdubbs said:
The short answer is yes, the long answer is that while that is indeed where the frequencies and voltages are stored, its pretty greek to me. I attempted to copy the 1.9 ghz acpuclock-7x30.c from another post on this forum and it doesn't seem like it compiled it, I still only made it to 1.5.
I'm going to investigate both this and where exactly the smartass governor source is and update this guide later.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Seems I was right about the CPU frequencies/voltages being there - I finally compiled a kernel that booted - I added a frequency value of 184Mhz, and SetCPU reflects this.
Thank you so much for this guide - I'm so chuffed with myself compiling a working kernel
Because of the newer kernel for Gingerbread (2.6.35.7) we need newer modules for cifs and ext4. Compiled them:
download here: http://xda.richardtrip.org/?dir=tab/Gingerbread/modules
Before you ask.... a tun.ko is not needed (compiled in the kernel).
Correct me if im wrong but will these modules give us EXT4 support on ginger ?
crisvillani said:
Correct me if im wrong but will these modules give us EXT4 support on ginger ?
Click to expand...
Click to collapse
insmod /system/lib/modules/jbd2.ko
insmod /system/lib/modules/ext4.ko
and it should work.
how to?
i have kernel 2.6.32.9
hmm .. i doubt about it ... the rom is very fast and as far its good , why do i need to go for ext4 if the ext4 suck the battery life ?
k0sh said:
hmm .. i doubt about it ... the rom is very fast and as far its good , why do i need to go for ext4 if the ext4 suck the battery life ?
Click to expand...
Click to collapse
I have never heard of a file system sucking the battery life. If anything, FAT32 would be the worst used in practice today.
richardtrip said:
insmod /system/lib/modules/jbd2.ko
insmod /system/lib/modules/ext4.ko
and it should work.
Click to expand...
Click to collapse
So really dumb, newb ( but learning so much so quickly ) question. Can I get my CIFS support back to stream videos on Overcome 2.0.0 if I use
insmod /system/lib/modules/cifs.ko
insmod /system/lib/modules/slow-work ???
( think slow-work is needed from research )
( Settings ->About Device->Kernel Version 2.6.35.7 [email protected] #2 )
fidjit said:
So really dumb, newb ( but learning so much so quickly ) question. Can I get my CIFS support back to stream videos on Overcome 2.0.0 if I use
insmod /system/lib/modules/cifs.ko
insmod /system/lib/modules/slow-work ???
( think slow-work is needed from research )
( Settings ->About Device->Kernel Version 2.6.35.7 [email protected] #2 )
Click to expand...
Click to collapse
you need to load slow-work.ko first.
please,
howto install these modules on the new GB roms?
Wow. This is great now i have working cisco vpn.
Thank you very much
Sent from my GT-P1000 using XDA App
bartito said:
please,
howto install these modules on the new GB roms?
Click to expand...
Click to collapse
Download the modules to /system/lib/modules/ (or anywhere really, just not the SD card) then load them using insmod. If you need them of every boot you can use an init.d script to load them automatically
For those of you who are inept, please find a link below to the same modules inside a CWM flashable zip.
CLICK ME!
TheGrammarFreak said:
Download the modules to /system/lib/modules/ (or anywhere really, just not the SD card) then load them using insmod. If you need them of every boot you can use an init.d script to load them automatically
Click to expand...
Click to collapse
Unfortunatly, init.d doesn't work in current version...
Tried to manually load as per instructions.
Didn't seem to do anything to assist my cifs manager. Figured I'd go back to my nandroid backup I'd made just before. Stuck on Samsung screen. on reboot after restore
Had to do a restock and rebuild. As say in previous post learning a lot ..........like always take an Nandroid
Think I'll be leaving this to the experts and wait for a new already compiled kernel
fidjit said:
Tried to manually load as per instructions.
Didn't seem to do anything to assist my cifs manager. Figured I'd go back to my nandroid backup I'd made just before. Stuck on Samsung screen. on reboot after restore
Had to do a restock and rebuild. As say in previous post learning a lot ..........like always take an Nandroid
Think I'll be leaving this to the experts and wait for a new already compiled kernel
Click to expand...
Click to collapse
Cifs mananager doesn't help you. But it is simple to do that manually:
$su
#busybox insmod /system/lib/modules/easy-work.ko &&
#busybox insmod /system/lib/modules/cifs.ko
#mount -r -t cifs -o <YourShareName,login,password> <MountingPoint>
I use GscriptLite for that.
acolwill said:
For those of you who are inept, please find a link below to the same modules inside a CWM flashable zip.
CLICK ME!
Click to expand...
Click to collapse
so if i flash this via cwm it will give me ext4?
acolwill said:
For those of you who are inept, please find a link below to the same modules inside a CWM flashable zip.
CLICK ME!
Click to expand...
Click to collapse
Sorry for being inept, but that doesn't make CIFS Module to work
--
Enviado desde mi móvil
maxtcee said:
so if i flash this via cwm it will give me ext4?
Click to expand...
Click to collapse
it just copy the *.ko to your /lib/module,you still have to add script inside init.d to make it load automatically when boot
init.d dobt supported in gb, seems to me
howto make these modulez autoloaded without init.d?
bartito said:
init.d dobt supported in gb, seems to me
howto make these modulez autoloaded without init.d?
Click to expand...
Click to collapse
CF-Root will run scripts from init.d. Overcome includes CF-Root.
Sent from my Galaxy Tab. Now that's dedication
Hello,
I would like to use cifsmanager apps but I see that our kernel doesn't have the proper module built in.
I just updated the kernel and modules using the latest available in the the kernel build service (following the incremental updates guide):
http://xdandroid.com/wiki/Incremental_Updates
but I'm not able to insmod the module.
I also tried to manually download the cifs.ko module and to load it telling to cifsmanager app where the module is, but I continue to receive the same error, no such device, like if the module isn't loaded correctly.
How can I solve this problem?
Thank you
Why not just use adb...? I don't see the need for CIFS.
If you can figure out how to get CIFS working, we can look about implementing it mainline.
Have you tried insmodding it after cp'ing the .ko file to /lib/modules?
ok thank you,
I tried to load the module using adb, but I think I'm using a wrong file because when I try to load it insmod return me the "invalid module format" output.
I'm using the kernel downloaded here:
http://zimages.googlecode.com/files/htc-msm-linux-20110914_084441-package.tar.bz2
somebody can tell me if is there a module that I can use with this kernel?
thank you
Caio said:
ok thank you,
I tried to load the module using adb, but I think I'm using a wrong file because when I try to load it insmod return me the "invalid module format" output.
I'm using the kernel downloaded here:
http://zimages.googlecode.com/files/htc-msm-linux-20110914_084441-package.tar.bz2
somebody can tell me if is there a module that I can use with this kernel?
thank you
Click to expand...
Click to collapse
Where did you get the module from...? Our kernel is probably not equipped with that module.
Caio,i've sent you a pm,let me know if it works,so i'll maybe push it in the mainline kernel
I downloaded the module on a thread of HTC Diamond's...can someone link me a module that could work with this kernel?
Or is there another way I can use to mount my samba share on my android?
thank you
Caio said:
I downloaded the module on a thread of HTC Diamond's...can someone link me a module that could work with this kernel?
Or is there another way I can use to mount my samba share on my android?
thank you
Click to expand...
Click to collapse
Did you miss helicopter88's PM? He built you a kernel that should have the module built into it...
arrrghhh said:
Did you miss helicopter88's PM? He built you a kernel that should have the module built into it...
Click to expand...
Click to collapse
Failed to boot,pheraps my fault or too much oc..
Later i'll make a stock kernel
Here's the module http://www.mediafire.com/?w6fp94b464cktkc
So you can put it somewhere and insmod it
well, i have the same problem, can anyone solve it?
helicopter88 said:
Here's the module
So you can put it somewhere and insmod it
Click to expand...
Click to collapse
sadly to say that, but the files had been removed
Here's the module..
thanks for your reply, but seems no luck, it just says "invalid module format" when insmod (using the FRX07.1)
ZSaberLv0 said:
thanks for your reply, but seems no luck, it just says "invalid module format" when insmod (using the FRX07.1)
Click to expand...
Click to collapse
Pheraps I should make it from original xdandroid source..
Here's another one
http://www.mediafire.com/file/wsw6tlah3lzp3gs/cifs.ko
helicopter88 said:
Pheraps I should make it from original xdandroid source..
Here's another one
http://www.mediafire.com/file/wsw6tlah3lzp3gs/cifs.ko
Click to expand...
Click to collapse
Didn't you just say it was some simple config flag?
Make use of that "recognized developer" insignia you throw around there and commit something . (Or at least post something to the ML!!)
still doesn't work, shows the same message when insmod or insmod -f
btw, the kernel is modules-2.6.27.46-01356-gd4c73bd.tar.gz, maybe you should build a complete one? (well, i have never played with linux kernel...)
ZSaberLv0 said:
still doesn't work, shows the same message when insmod or insmod -f
btw, the kernel is modules-2.6.27.46-01356-gd4c73bd.tar.gz, maybe you should build a complete one? (well, i have never played with linux kernel...)
Click to expand...
Click to collapse
Assuming his patch is accepted, it will get committed mainline. It's a quite simple change to how the kernel is built.
arrrghhh said:
Assuming his patch is accepted, it will get committed mainline. It's a quite simple change to how the kernel is built.
Click to expand...
Click to collapse
I think phh had an issue with the patch submitted. I have a patch to commit soon so i can look into this. One question i have is how do yall plan to load the module? Does the app insmod it ? or does it expect the module to be built into the kernel?
[ACL] said:
I think phh had an issue with the patch submitted. I have a patch to commit soon so i can look into this. One question i have is how do yall plan to load the module? Does the app insmod it ? or does it expect the module to be built into the kernel?
Click to expand...
Click to collapse
I think people just want the module available in the 'modules`uname-r`.tar.gz' file. That way they at least have the option of insmodding it...(*.user.conf etc) who knows what they want to do with it afterwards - I guess access their phone on a LAN from their PC?
just want to mount my share folder from my PC to Android, so that i can use the shared files online without copy-paste (it'll be quite annoying by copy-paste, especially when you want to edit file, because you must upload it after editing)
in short, same as Caio, just want to use cifsmanager, and it says "no such device"
ZSaberLv0 said:
just want to mount my share folder from my PC to Android, so that i can use the shared files online without copy-paste (it'll be quite annoying by copy-paste, especially when you want to edit file, because you must upload it after editing)
in short, same as Caio, just want to use cifsmanager, and it says "no such device"
Click to expand...
Click to collapse
The fixed patch has been sent to Mailing List,now let's see if it gets approved..
#compiled new cifs.ko, md4.ko, nls_utf8.ko for the new
IMM76I build
kernel number
3.0.8-gda6252b
attachment "cifs_gda6252b.zip"
------------------------------------------------------------------
hi there, i have compiled modules for CIFS to work on the stock 4.0.4 kernel.
kernel number must match "3.0.8-g034fec9"
in the attached zip,
here are the list of files.
cifs.ko
md4.ko
#above 2 are required to have it work
#here are native language support.
nls_utf8.ko
nls_cp932.ko
nls_cp936.ko
nls_cp950.ko
#above cp9xx are support for chinese characters.
nls_euc-jp.ko
#above is support for japanese letters.
thank you.
additional notes.
apparently you do not need any other native language support apart from utf8
the trick is, during the mounting process, you will need to specify the "iocharset=utf8" under options.
eg
"mount //192.168.15.123/a /home/b/c -t cifs -o username=d,password=e,uid=f,gid=g,iocharset=utf8"
for cifs manager, just put "iocharset=utf8" under the Options, and you should be able to see all different charsets.
do remember you will need to load the nls_utf8.ko
once you have the module install,
you can use cifs manager to manage your mounts.
(you can also set cifs manager to load this module for you).
Thanks, I'll give it a try later today.
soloxp said:
Thanks, I'll give it a try later today.
Click to expand...
Click to collapse
make sure that you have the correct stock kernel.
must match "3.0.8-g034fec9" else insmod will fail.
if anyone of you are running other version of kernel, i can try compile if for you as well, but let me know your kernel version.
do note, i have not tried compiling for other version, it might and might not work.
qwerp_ said:
must match "3.0.8-g034fec9" else insmod will fail.
if anyone of you are running other version of kernel, i can try compile if for you as well, but let me know your kernel version.
Click to expand...
Click to collapse
I've got the ICS 4.0.4 OTA update (IMM76D) to my Nexus S and it says "kernel 3.0.8-g6656123".
Any chance of getting a build for this one?
http :// dl.dropbox.com/u/11754796/imm74d.png
chrkad said:
I've got the ICS 4.0.4 OTA update (IMM76D) to my Nexus S and it says "kernel 3.0.8-g6656123".
Any chance of getting a build for this one?
http :// dl.dropbox.com/u/11754796/imm74d.png
Click to expand...
Click to collapse
here you go.
give it a try.
for stock Nexus S kernel "3.0.8-g6656123"
files included are
cifs.ko
md4.ko
nls_utf8.ko
Samba (CIFS) kernel modules for ICS 4.0.4 (IMM76D) kernel 3.0.8-g6656123.
qwerp_ said:
give it a try.
for stock Nexus S kernel "3.0.8-g6656123"
Click to expand...
Click to collapse
Thanks!
I confirm these work great on ICS 4.0.4 with "kernel 3.0.8-g6656123"
Awesome!
On my galaxy Nexus stock doestn work cifs manager said cannot access a needed shared library
Noob question, what is CIFS?
Enviado do meu Galaxy Nexus usando o Tapatalk
Guto ViP said:
Noob question, what is CIFS?
Click to expand...
Click to collapse
Common Internet File System, is another name for SMB (Server Message Block) also known as Samba. It's most commonly used in Microsoft Windows networks for providing shared network access to files, printers and other services.
These modules allows you to mount a shared directory from your windows computer, on your phone.
I use it to watch movies and play Mp3 on my phone, which is stored on my (windows) media server.
aplatas said:
On my galaxy Nexus stock doestn work cifs manager said cannot access a needed shared library
Click to expand...
Click to collapse
this is the shared library cifs manager is complaining about.
hence you need to download and insmod it.
note. you will need to be rooted to do this.
qwerp_ said:
this is the shared library cifs manager is complaining about.
hence you need to download and insmod it.
note. you will need to be rooted to do this.
Click to expand...
Click to collapse
I am root, now the module is loaded but When i mount cifs manager said the error No such file or directory this is extrange because On my old Nexus S works
aplatas said:
I am root, now the module is loaded but When i mount cifs manager said the error No such file or directory this is extrange because On my old Nexus S works
Click to expand...
Click to collapse
did you load both
cifs.ko and md4.ko
?
both is required to have it work.
qwerp_ said:
did you load both
cifs.ko and md4.ko
?
both is required to have it work.
Click to expand...
Click to collapse
Thanks, the problem it was that the md4.ko it wasn't loaded
qwerp_ said:
did you load both
cifs.ko and md4.ko
?
both is required to have it work.
Click to expand...
Click to collapse
thanks, works well.
Any idea how to get CIFS running on Galaxy Nexus 4.1.1?
funkdified said:
Any idea how to get CIFS running on Galaxy Nexus 4.1.1?
Click to expand...
Click to collapse
In case you didn't see [OP] created a new thread for 4.1.1 here
qwerp_ said:
make sure that you have the correct stock kernel.
must match "3.0.8-g034fec9" else insmod will fail.
if anyone of you are running other version of kernel, i can try compile if for you as well, but let me know your kernel version.
do note, i have not tried compiling for other version, it might and might not work.
Click to expand...
Click to collapse
Hello,
could you compile it for the kernel version 2.6.34.
( I have a Zenithink ZT 280 C91 with ICS 4.0.3)
regards
-janez
cifs help
Hi,
hoping you can help me out. i have an android tv box that id love to get cifs running on so i can use mount manager and download direct to my nas disk. could you possibly compile these modules for the following kernel???
$ cat /proc/versionLinux version 3.0.8 ([email protected]) (gcc version 4.5.1 (Sourcery G++ Lite 2010.09-50)
) #8 PREEMPT Wed Sep 12 11:07:28 CST 2012
[email protected]:/ $
Thanks in advance for your help!!!
Up-to-Date Bare Repositories for TW/AOSP 4.2.2 Kernelsamsung-kernel-jfltexx
Short Info:
I've made this repository to have a central place for everyone to fork their kernel base from. The advantage of this repo is that it is always up-to-date (as in the latest linux kernel version). Imagine the difference from starting at a 3.4.0 kernel base and 3.4.52 kernel base, there are thousands of new patches in that patch range. :good:
Repository Url:
Code:
https://github.com/broodplank/samsung-kernel-jfltexx
Repository Info:
Name: samsung-kernel-jfltexx
Description: Bare repositories for jfltexx (i9505)
Branches: tw-4.2.2 and aosp-4.2.2 (aosp 4.3 coming when 4.3 kernel sources are released)
tw-4.2.2 = Stock i9505 TouchWiz Kernel from Samsung sources patched until latest linux kernel version
aosp-4.2.2 = i9505g Google Edition Kernel (for AOSP 4.2.2 Google Edition and TouchWiz 4.2.2) (for i9505)
Getting the sources:
If you want to compile the kernel directly without much changes it's advised to clone it:
Code:
git clone [url]https://github.com/broodplank/samsung-kernel-jfltexx[/url] -b branchname
If you want to make your own kernel it's advised to fork the kernel:
- Login at github
- Go to https://github.com/broodplank/samsung-kernel-jfltexx
- Click Fork at the right top of the page
Click to expand...
Click to collapse
Usage Info:
Initializing first config:
Code:
make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig
Configuration:
Easiest variant (QT based GUI, needs libqt4-dev libqt4-core and libqt4-gui)
Code:
make xconfig
Default variant:
Code:
make menuconfig
Other less popular variants:
(GTK based, doesn't need any special packages)
Code:
make gconfig
(Ncurses based, needs libncurses5, libncurses5-dev and libncursesw5)\
Code:
make nconfig
Building Kernel:
Code:
export ARCH=arm
export CROSS_COMPILE=/path/to/toolchain/bin/arm-eabi-
make -jx (where x is the amount of cpu cores + 1)
Toolchains:
Toolchains that are suited for building the sources are:
arm-eabi-4.6
Click to expand...
Click to collapse
Building boot.img:
Code:
./build_bootimg
(Choose the rom type you will be using and it will be created in build/output)
Flashing boot.img and modules:
Code:
./flash_bootimg
(This is a process that pushes boot.img to your phone and then to the kernel partition, after that you can choose whether to push modules or not, and finally you can choose to wipe dalvik-cache or not and it will reboot.
Updating Info:
If you have forked the repository do this to fetch the updates from this repository:
First add it to the remote:
Code:
git remote add bare [url]https://github.com/broodplank/samsung-kernel-jfltexx[/url]
git fetch bare
Then search for the commit(s) that you want to merge
For 1 commit:
Code:
git cherry-pick [commit hash here, this is the last part of a commits url]
(for example: https://github.com/broodplank/samsung-kernel-jfltexx/commit/612bbea08b67f16dd5628cb8cd8406973f8fe821 would be: 612bbea08b67f16dd5628cb8cd8406973f8fe821)
For a range of commits:
Code:
git cherry-pick [commit a hash]^..[commit b hash]
Where commit a is the oldest commit and commit b the newest.
for example:
Code:
git cherry-pick 0bff3bdba64c58ea6100d72763f2be3acc9659db^..612bbea08b67f16dd5628cb8cd8406973f8fe821
This would patch the sources from 3.4.40 to 3.4.52
Latest Repository Changes:
3-08-2013
- Switched to real samsung 4.3 sources
29-07-2013
- Updated aosp-4.2.2 and tw-4.2.2 to 3.4.55
25-07-2013
- NEW BRANCH: AOSP-4.3
- NEW BRANCH: TW-4.3
- Added MSM8960 Headers from Google!
23-07-2013
- Update to 3.4.54
14-07-2013
- Update to 3.4.53
- Merge sensor fix from faux123
13-07-2013
- Updated defconfigs for proper building
09-07-2013
- Update to 3.4.52
- Sensor fix by ausdim
- Large update to readme
06-07-2013
- Add samsung sources
- Patch to latest version 3.4.51
- add boot.img creator
05-07-2013
- Initial commit, make repository
Thanks, I just forked it.
I'm a noob at this but am learning fast. I've modified and compiled the 3.0.31 kernel for the 9210T but I'd like to now try 3.4. Appears none of the celox changes for board_msm8x60.c source came across from 3.0 to 3.4 so I think I've got my work cut out for me.
m0tter
This guide is not working for me.
If I follow your guide the resulting kernel boots, but I have no sound and no 3G (PIN pad doesn't show up).
I'm on MF8 stock ROM. Yours, Ausdims or my own (based on Samsung Update 2 sources) work fine.
This is what I did:
$ git clone https://github.com/broodplank/samsung-kernel-jfltexx -b tw-4.2.2
$ make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig
$ export ARCH=arm
$ export CROSS_COMPILE=/path/to/toolchain/bin/arm-eabi-
$ make xconfig (no changes!)
$ make -j3
$ ./build_bootimg && ./flash_bootimg (selected 1 for TW)
What am I doing wrong?
harise100 said:
This guide is not working for me.
If I follow your guide the resulting kernel boots, but I have no sound and no 3G (PIN pad doesn't show up).
I'm on MF8 stock ROM. Yours, Ausdims or my own (based on Samsung Update 2 sources) work fine.
This is what I did:
$ git clone https://github.com/broodplank/samsung-kernel-jfltexx -b tw-4.2.2
$ make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig
$ export ARCH=arm
$ export CROSS_COMPILE=/path/to/toolchain/bin/arm-eabi-
$ make xconfig (no changes!)
$ make -j3
$ ./build_bootimg && ./flash_bootimg (selected 1 for TW)
What am I doing wrong?
Click to expand...
Click to collapse
InitRamfs??
Permisions of initramfs?
ausdim said:
InitRamfs??
Permisions of initramfs?
Click to expand...
Click to collapse
Don't know.
I used the script to build the boot.img. If I do the same with my sources, it works.
In both cases, I haven't touched those files.
Sent from my GT-I9505 using xda app-developers app
harise100 said:
Don't know.
I used the script to build the boot.img. If I do the same with my sources, it works.
In both cases, I haven't touched those files.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Im not on pc to check that and help you but your problem about radio (pin) sounds initramfs problem.
Unpack an stock boot.img and use that ramfs.
Thanks
ausdim said:
Im not on pc to check that and help you but your problem about radio (pin) sounds initramfs problem.
Unpack an stock boot.img and use that ramfs.
Thanks
Click to expand...
Click to collapse
Thank you for trying to help me... but it still doesn't work. Same result.
harise100 said:
Thank you for trying to help me... but it still doesn't work. Same result.
Click to expand...
Click to collapse
Tonight Ill do a little research on this and tell you the solution.
I remember when I started to make my first kernel, I had similar problems with the Samsung sources.
Wanam gave me his jf_defconfig file and it worked. He said that the config file by Samsung is crap. But I forgot to ask for details.
If I use my config file on your sources, it results in a bootloop, whereas they work fine with Samsung update 2 sources.
Does that make sense?
Sent from my GT-I9505 using xda app-developers app
Still figuring out, why i cant even successfully compile the sources. With ktoonse sources it works.
But i'm still a beginner. Will see about that xP
Gesendet von meinem GT-I9505 mit Tapatalk 2
.c0dy said:
Still figuring out, why i cant even successfully compile the sources. With ktoonse sources it works.
But i'm still a beginner. Will see about that xP
Gesendet von meinem GT-I9505 mit Tapatalk 2
Click to expand...
Click to collapse
What is your problem?
Sent from my GT-I9505 using xda app-developers app
harise100 said:
What is your problem?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
I hate it -.- xD
Now it worked. And I do not know why... As I am pretty new to this, as already said, - could this be the problem? :
I think I made this:
$ make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig
$ make xconfig
$ export ARCH=arm
$ export CROSS_COMPILE=/path/to/toolchain/bin/arm-eabi-
Click to expand...
Click to collapse
instead of:
$ make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig
$ export ARCH=arm
$ export CROSS_COMPILE=/path/to/toolchain/bin/arm-eabi-
$ make xconfig
Click to expand...
Click to collapse
So I used xconfig before setting ARCH and CROSS_COMPILE.
Could that be the problem?
Atm i can not paste the error. The first one had something to do with a buffersize. Could "fix" that by setting "CONFIG_FRAME_WARN=1024" higher. Because it said it was 1032.
Second error was something like "‘ret’ may be used uninitialized in this function [-Wuninitialized]".
---------- Post added at 08:08 PM ---------- Previous post was at 07:32 PM ----------
Will add a new post for this, if it's okay.
And i hope it's okay to ask in here
So, first, as wrote in my previous post the compiling worked.
Now, i did the following:
1. Changed in the config: "kernel compression mode -> LZO
2. Removed "Optimize for size"
3. And changed the flag in the makefile to O3.
kernel/workqueue.c: In function 'freeze_workqueues_begin':
kernel/workqueue.c:483:11: warning: array subscript is above array bounds [-Warray-bounds]
error, forbidden warning: workqueue.c:483
make[1]: *** [kernel/workqueue.o] Error 1
make[1]: *** Waiting for unfinished jobs....
While writing this I reset "Optimize for size" and restart compiling. Now it does seem to work.
So i guess there is a problem with the flag. Where is the right place of the flag?
If you want to use O2 or O3, it requires some modification of config and make files.
The build boot.img script worked for me right away.
Sent from my GT-I9505 using xda app-developers app
harise100 said:
If you want to use O2 or O3, it requires some modification of config and make files.
The build boot.img script worked for me right away.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Ah okay, thanks. Will see if I can find a few more infos about that
broodplank1337 said:
Tonight Ill do a little research on this and tell you the solution.
Click to expand...
Click to collapse
Did you find anything?
I do have a working build environment and I can compile and install a kernel that is better than stock kernel.
Only these sources don't work. How is that possible?
Sent from my GT-I9505 using xda app-developers app
.c0dy said:
Ah okay, thanks. Will see if I can find a few more infos about that
Click to expand...
Click to collapse
check out this commit: https://github.com/broodplank/andro...mmit/69b6e56fb4151f547368fc77d5ad682fbf99ea7b
broodplank1337 said:
check out this commit: https://github.com/broodplank/andro...mmit/69b6e56fb4151f547368fc77d5ad682fbf99ea7b
Click to expand...
Click to collapse
I'll give it a try when I get home.
Sent from my GT-I9505 using xda app-developers app
harise100 said:
I'll give it a try when I get home.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
It will work if you have the right toolchain, I use this one:
http://www.mediafire.com/download/i...linaro_4.7.4-2013.07-build_2013_07_12.tar.bz2
It's an optimized Linaro toolchain (http://forum.xda-developers.com/showthread.php?t=2098133)
broodplank1337 said:
check out this commit: https://github.com/broodplank/andro...mmit/69b6e56fb4151f547368fc77d5ad682fbf99ea7b
Click to expand...
Click to collapse
Thanks Will try that.
I already compiled a kernel, but it just booted until the samsung logo.. after that instant reboot... :/