i am looking in compiling cifs.ko for stock kernel xoom UK.
i can't seems to find any similar source to the xoom.
i tried to compile from tiamat AOSP, something seems to be wrong, and it did not work.
i then tried the Asus Eee Transformers, it manage to compile and load, but when i tried to use it, only restart the xoom..
can someone compile me a cifs.ko with
"vermagic=2.6.36.3 SMP preempt mod_unload ARMv7"
to try?
thanks.
Related
I have been trying to get other game controllers to work with the transformer and from what I have found is that it is missing a module that I'm guessing isn't compiled by default. I downloaded the kernel source from asus and it does indeed have the source file for the module. I haven't compiled a kernel for a few years so I figured someone else may be able to help. I am running prime rom and have tried a few different kernels and none seem to make a difference. The device shows up in dmesg but never is assigned to anything. The module is joydev I have included links to the driver source and devices supported by the driver.
Source file:
https://github.com/netarchy/android_kernel_TF101/blob/master/drivers/input/joydev.c
https://github.com/netarchy/android_kernel_TF101/blob/master/Documentation/input/joystick.txt
Supported Devices:
http://atrey.karlin.mff.cuni.cz/~vojtech/input/hardware.html
P6200: https://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-P6200
P6210: https://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-P6210
any more info? i am assuming that this cannot compile to a fully working rom? there must be missing binary blobs? perhaps this is just kernel source? anything else you can tell me would be awesome thank you!
SGH-T869: https://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SGH-T869
The zip files each contain two tarballs. One for kernel source and the other for platform stuff.
The kernel stuff is semi-complete... it'll compile a proper kernel, but won't be bootable on your device unless you add an initramfs image. You'll also need to pull the proprietary loadable modules from your device and embed them in that same initramfs. There's enough there that with some know-how and tools you can create a new kernel image...
The platform stuff... well, I haven't messed with that. I honestly don't know what is in there that isn't already in the AOSP. I do know that it doesn't contain things like touchwiz...
Take care
Gary
this is great news! i juat recently got a good build platform put together on an old laptop so this will be fun to take a crack at!
garyd9 said:
The zip files each contain two tarballs. One for kernel source and the other for platform stuff.
The kernel stuff is semi-complete... it'll compile a proper kernel, but won't be bootable on your device unless you add an initramfs image. You'll also need to pull the proprietary loadable modules from your device and embed them in that same initramfs. There's enough there that with some know-how and tools you can create a new kernel image...
The platform stuff... well, I haven't messed with that. I honestly don't know what is in there that isn't already in the AOSP. I do know that it doesn't contain things like touchwiz...
Take care
Gary
Click to expand...
Click to collapse
Are there any proprietary kernel modules? There aren't for other Exynos devices (GSII, Galaxy Note).
Original GalaxyS had some (FSR/RFS, also j4fs - j4fs is open-source on Exynos devices)
Entropy512 said:
Are there any proprietary kernel modules? There aren't for other Exynos devices (GSII, Galaxy Note).
Click to expand...
Click to collapse
Well... I thought there were. I know there were modules on my 6210 /lib/modules that didn't get built from the kernel. I don't remember right now which ones, though. (I'm at work...)
Take care
Gary
garyd9 said:
Well... I thought there were. I know there were modules on my 6210 /lib/modules that didn't get built from the kernel. I don't remember right now which ones, though.
Click to expand...
Click to collapse
Okay, you were correct. For the GTP6210, only one module from the factory recovery (and main boot) which isn't being built by the kernel build:
j4fs.ko (as you already mentioned.)
Take care
Gary
garyd9 said:
Okay, you were correct. For the GTP6210, only one module from the factory recovery (and main boot) which isn't being built by the kernel build:
j4fs.ko (as you already mentioned.)
Take care
Gary
Click to expand...
Click to collapse
Odd... On Exynos devices, j4fs should be getting built...
https://github.com/Entropy512/linux_kernel_sgh-i777/tree/master/drivers/samsung/j4fs
Its odd location for an FS driver (in drivers/staging/samsung) puts it in a weird location in menuconfig too.
j4fs is used to access param.lfs
There also seems to be missing a "ar6000" device, but it's not in /lib/modules on the factory initramfs either. Of all things, it's in /system/wifi. (and there's no source.)
if I recompile the kernel sources from samsung's website (doing everything properly, of course), it won't load that module... claims a version mismatch (and won't allow me to override.)
Here's the uname string from the factory normal boot (KL1) kernel:
Code:
Linux localhost 2.6.36-P6210UEKL1-CL583281 #3 SMP PREEMPT Fri Dec 2 21:14:23 KST 2011 armv7l GNU/Linux
The kernels I recompile have a slightly different string:
Code:
Linux localhost 2.6.36 #4 SMP PREEMPT Sat Dec 10 23:40:09 EST 2011 armv7l GNU/Linux
I guess that makes the kernel source a bit less useful. Perhaps after they drop the KL1 updated kernel sources I'll be in better shape.
Yet, I can't help but to feel like I missing something obvious... Just can't remember what. perhaps after a good night sleep it'll come to me.
edit: found a source for the ar6000 code (http://nv-tegra.nvidia.com/gitweb/?p=3rdparty/atheros.git) I'll play with it more tomorrow or over the weekend.
Take care
Gary
Would anyone know how to go about getting the drivers for the IR port? I have an early version of the 7.7 that has the IR blaster but the Peel app is saying it's not present. I think I just need to flash the drivers for it, but I'm rather ignorant of this. Any ideas?
Hi I looked for sometime for answers but could not find anything relevant.
Looking to get the ftdi VCP drivers to install on Xoom. Which means I either have to compile a kernel or add them as a module. I can not for the life of me find the correct source tree.
I downloaded kernel 2.6.36.3 from google which matches my kernel version.
My kernel version on the tablet is 2.6.36.3-gb899258 .
When I cross compile the module and try to do an insmod its complaining about the magic version is different which leads me to believe that I have the wrong kernel.
Where can I get the right stock kernel?
If i can not find it there is another option to download the config.gz from the device and recompile another version of the kernel with native support for the ftdi drivers.. How do i just install just the kernel on the device? Is it a uImage bzImage and how do I just flash that?
cd
Thanks
edit:
scrap that ...
sorry, not really helpful in your case
I'm assuming you got your source from here? This is the link from the Android website:
git clone https://android.googlesource.com/kernel/tegra.git
If you decide to go the route of compiling another kernel source, the easiest way (and a good way to keep snapshots of various configs) would be to use Koush's AnyKernel to flash the kernel. I don't know anything about what you're trying to do but I hope that helps some.
Yep the code comes from there.....
I finally got it to work , I downloaded the stock kernel from google then when I make the modules I had to modify the Makefile to get it to match the kernel versions.
It seems to work for now...
Thanks for your help
I just installed ICS and it works fine. I never expected it to work as well as it does, but now I can get down to griping about little things that I use that don't yet work
Normally I use CIFS (Common Internet File System, like Samba was before) to access shares on the net. This worked fine on HoneyComb because I built my own kernel modules.
For ICS, I think the source is not yet released for the kernel. I did see that there was a tun.ko and cifs.ko for ICS over in the transformer prime section of XDA, so I tried those out but it appears the tegra 3 kernel is too different for these to work. (although I think the version is the same).
If anyone has seen or has a working cifs.ko module I'd appreciate getting ahold of it (or especially the ICS kernel source code).
Thanks -
I don't know about cifs.ko as I don't use it, but I do use OpenVPN and found out that tun is part of ICS now, you no longer need a separate module.
hachamacha said:
I just installed ICS and it works fine. I never expected it to work as well as it does, but now I can get down to griping about little things that I use that don't yet work
Normally I use CIFS (Common Internet File System, like Samba was before) to access shares on the net. This worked fine on HoneyComb because I built my own kernel modules.
For ICS, I think the source is not yet released for the kernel. I did see that there was a tun.ko and cifs.ko for ICS over in the transformer prime section of XDA, so I tried those out but it appears the tegra 3 kernel is too different for these to work. (although I think the version is the same).
If anyone has seen or has a working cifs.ko module I'd appreciate getting ahold of it (or especially the ICS kernel source code).
Thanks -
Click to expand...
Click to collapse
I didn't have much success with tun and cifs for my purpose which was to wirelessly access the sd card of the phone/tablet vice versa until I used the Samba app fom the market. In combination with Ghost commander and after upgrading to ICS everything was intact. Not sure if this is helpful to you or not. Just throwin it out there.
Thanks both of you -
I realized that tun was there but thanks. As for cifs, I suppose the module isn't really needed except to use certain utils that rely on it, like root explorer.
I found a number of samba/cifs compatible file managers that're fine for me like ES explorer etc.
Those will be fine and I'll look forward to getting kernel source for ICS anyway.
hachamacha said:
Thanks both of you -
I realized that tun was there but thanks. As for cifs, I suppose the module isn't really needed except to use certain utils that rely on it, like root explorer.
Click to expand...
Click to collapse
I've just rooted my TF101 (ICS) so that I could get Junos pulse working with its ssl vpn. Doing a bit of reading I found I needed tun.ko (at least with 3.2). That automatic tun.ko installer from the market reports that tun.ko is installed (compiled into the kernel?)
I can see the tun0 created, with an IP address. But it doesn't work, not a single bit travels the tunnel interface.
I'm officially confused...
Still too few posts under this account name to be able to post links, but have you seen this thread in Dev?
xpad / cifs modules for stock kernel ICS v9.2.1.11
Thanks for that... that confirms tun.ko is built in, which doesn't help me find/fix my problem.
Will keep at it!
I want to build a module for my atrix HD w/ kernel ver 3.0.42-gebf622c. I think I found the source code, but I cannot figure out which config file to use. I have never built a linux kernel for an android before, so I am sure I will run into all kinds of trouble. Can someone give me some pointers for bootstrapping this process? I at least need to know where to find the .config file used to configure this kernel. Shorter term, does anyone have a tun.ko for this kernel?
Thanks!