Hi pals
I just received Galaxy Tab 10.1 Kernel source code as .tar and I worked on a common git repository for us all developers to ease our work as team. It helps facilitating exchanges.
The source presented here are Samsung unmodified, for your forking pleasure.
Now your turn to build OC and more custom stuff from it. I'll focus on Image, Sound and Video
Kernel sources:
github.com/GalaxyTab101/samsung-kernel-galaxytab101
Initramfs collection you can use with:
github.com/GalaxyTab101/samsung-initramfs-galaxytab101
Template build scripts:
https://github.com/project-voodoo/scripts/blob/supercurio/galaxytab101_build_kernel.sh
https://github.com/project-voodoo/scripts/blob/supercurio/galaxytab101_mkbootimage.sh
Samsung README:
https://github.com/GalaxyTab101/sam...p7510-honeycomb-3.1/README_Samsung_kernel.txt
First custom kernel built with all this:
- It's insecure (adb root)
First custom kernel available!
- It contains associated cifs.ko in /lib/modules
http://dl.project-voodoo.org/galaxytab10.1/gt-p7510-supercurio-insecure-boot.img
How to test-boot it:
- reboot fastboot mode
- fastboot boot gt-p7510-supercurio-insecure-boot.img
Have fun
Click to expand...
Click to collapse
First!
Good News Supercurio!
Great news looking forward to some custom kernals
Sent from my HTC Desire HD using XDA App
Good to see you working on the 10.1 tablet. Thanx for the work on the kernel & instructions. Cant wait to overclock.
great to see supercurio and shep working on the Tab 10.1!!!
Lots of custom roms and kernels in the galaxy tab future!!
Its happening here live if you're curious
https://github.com/GalaxyTab101
Last night I prayed for some Voodoo love, and the lord answered our prayers! YES!
Actually diffing manually to find which repo/commit Samsung based it source from.
Code:
38988 /tmp/diffandroid-tegra-2.6.36-honeycomb-mr1+samsung
39040 /tmp/diffandroid-tegra-2.6.36-honeycomb+samsung
14992 /tmp/diffandroid-tegra-2.6.36-release-f982fa0f+samsung
14996 /tmp/diffandroid-tegra-2.6.36-release+samsung
Awesome, can't wait for some overclocking awesomeness!
Now if Google would release the Honeycomb source code...
Sent from my GT-P7510 using Tapatalk
Will this enable us to get cifs.ko that we desperately need on this platform? (I'm spoiled since I have a Droid Incredible)
Very cool.. glad to see your working on this supercurio
Thanks supercurio, I've been waiting for this!
You just made my day Supercurio
Very very cool. Thanks for posting this and I look forward to digging in..
Yeah !
Source now online.
I recreated a git repository with many manual cherry-picking based on an old NVIDIA repository state (march) to serve as base:
https://github.com/GalaxyTab101/samsung-kernel-galaxytab101/tree/gt-p7510-base
Close but not exactly Samsung's repo, it would have taken days of work: not reasonable ^^
Then I added Samsung source, fixed a few things et voilà !
github.com/GalaxyTab101/samsung-kernel-galaxytab101
Now, initramfs time!
supercurio said:
Yeah !
Source now online.
I recreated a git repository with many manual cherry-picking based on an old NVIDIA repository state (march) to serve as base:
https://github.com/GalaxyTab101/samsung-kernel-galaxytab101/tree/gt-p7510-base
Close but not exactly Samsung's repo, it would have taken days of work: not reasonable ^^
Then I added Samsung source, fixed a few things et voilà !
github.com/GalaxyTab101/samsung-kernel-galaxytab101
Now, initramfs time!
Click to expand...
Click to collapse
you are my hero
thank you all for working on custom rom.
Sent from my SHW-M110S using XDA App
First custom kernel available!
- It's insecure (adb root)
- It contains associated cifs.ko in /lib/modules
http://dl.project-voodoo.org/galaxytab10.1/gt-p7510-supercurio-insecure-boot.img
How to test-boot it:
- reboot fastboot mode
- fastboot boot gt-p7510-supercurio-insecure-boot.img
Have fun
Note: all the sources are available now, It's time to update the first post
Hi guys i've compiled succesfully an AOSP rom built from google code but it doesn't boot....it stay on LG logo and goes in bootloop.....here's my logcat....i have problem in thunderg_gralloc.so....i've used the CM7 device folder of Mik_os.....anyone can help me please??
lupohirp said:
Hi guys i've compiled succesfully an AOSP rom built from google code but it doesn't boot....it stay on LG logo and goes in bootloop.....here's my logcat....i have problem in thunderg_gralloc.so....i've used the CM7 device folder of Mik_os.....anyone can help me please??
Click to expand...
Click to collapse
gralloc is a proprietary from LG's 2.2. Between 2.2 and 2.3 there are much API changes and CM project added old libraries support. You need to port it to AOSP or replace gralloc props with opensource libgralloc (get it from zte blade cm7 device, but lg's is faster).
mik_os said:
gralloc is a proprietary from LG's 2.2. Between 2.2 and 2.3 there are much API changes and CM project added old libraries support. You need to port it to AOSP or replace gralloc props with opensource libgralloc (get it from zte blade cm7 device, but lg's is faster).
Click to expand...
Click to collapse
IT BOOTED MIK thanks ))) but now there are many bugs....gsm doesn't work if i lock screen device doesn't turn on(maybe debug.hw.sf=1 i must set =0??) usb doesn't work UI is very slow ((( for now i've discovered these bugs
Some background info:
I'm the author of PPP Widget which is an app that enables mobile data connections on Android devices with USB host capabilities - even if they are WiFi-only.
It turned out that many Android devices have the drivers for 3G sticks already on board, included with the stock kernel. The one large exception are Samsung devices ...
I started to provide the missing drivers as modules (mostly "ppp_async" and "option" which depends on "usb_wwan"). That worked well for some Google devices and also for Samsung devices running ICS, using the source packages from
http://opensource.samsung.com/
In their JB kernels though, Samsung enabled the "MODVERSION" option. Furthermore, compiling the modules with the officially recommended toolchain resulted in a different "module_layout" checksum than in the modules provided in the firmware.
This prevents using any additonal modules on the devices. "insmod" refuses to load these modules.
The only explanation for this problem is that the custom device configuration provided in the source packages does not match the configuration of the device kernel.
This is the case for all GT-P31xx and GT-P51xx models as far as I can tell.
My take is that Samsung is required to provide the correct kernel configuration under the rules of the GPL. Maybe anyone else wants to contact Samsung on this behalf; I already did several times - still waiting for an answer ...
That's the reason why I build everyting from source including the GPU driver and lost exFAT support http://forum.xda-developers.com/showthread.php?t=1859227 and the boot image result http://forum.xda-developers.com/showthread.php?t=1855700 .
ketut.kumajaya said:
That's the reason why I build everyting from source including the GPU driver and lost exFAT support
Click to expand...
Click to collapse
Unfortunately, replacing the kernel is no option for end users. The modules I provide are going into a folder on the sdcard, and can be "insmod'ed" from there with no problem - once their magic string and the "modversions" are matching the kernel on the device. The latter is the wall I'm hitting ...
JFDee said:
Unfortunately, replacing the kernel is no option for end users. The modules I provide are going into a folder on the sdcard, and can be "insmod'ed" from there with no problem - once their magic string and the "modversions" are matching the kernel on the device. The latter is the wall I'm hitting ...
Click to expand...
Click to collapse
Thanx alot for such a great development. ...
Adi™
Creator Of Sungsonic™HD
I have received a reply from Samsung. They have updated the JB open source package for GT-P3110, GT-P5110 and GT-N7100 (which previously included a config file from 3.0.15 for a kernel version of 3.0.31 !!).
Unfortunately, the modversions of the compiled kernel are still different and incompatible. I have replied with these finding.
Waiting again ...
BTW, the only recent kernel config consistent with the actual device kernel that I have found is for the GT-N8000 (3.0.31). So it is possible to provide a matching configuration.
JFDee said:
I have received a reply from Samsung. They have updated the JB open source package for GT-P3110, GT-P5110 and GT-N7100 (which previously included a config file from 3.0.15 for a kernel version of 3.0.31 !!).
Unfortunately, the modversions of the compiled kernel are still different and incompatible. I have replied with these finding.
Waiting again ...
BTW, the only recent kernel config consistent with the actual device kernel that I have found is for the GT-N8000 (3.0.31). So it is possible to provide a matching configuration.
Click to expand...
Click to collapse
If You will start to work with kernel I'm willing to beta test with my P5110. Only issue for me is that I need to know what 3G dongle to buy (well need it anyway so would prefer an advice from someone who know something about it). I'm living in Poland and Ireland (once here once there) so I can even test LTE modems (well donations here, myself can spend up to ~50€ on 3G one) because in Wroclaw, Poland I heard it's quite good, also I got H+/H on SGSII here. While in Ireland signal is not THAT strong due to fact most of places are quite remote (except Dublin, Galway etc). Hope I can help in either way
This is what I wrote to Samsung concerning the botched configuration file provided with the latest GT-P3110 kernel source:
Thank you for the source code update.
However, I have asked for the kernel configuration that matches exactly the kernel on the GT-P3110.
I have compiled the kernel from the provided update, but the module layout checksum does *not* match the one from the kernel running on my device.
On the device: module_layout 0xb5a27644
From source: module_layout 0x143474f1
I have used the recommended toolchain "CodeSourcery 2010q1" and the unchanged config file provided with the source ("android_espresso_omap4430_r04_user_defconfig").
Please be aware that you are obliged by the GPL to provide the correct config file for the binary kernel that you are distributing.
As a side note: the configuration provided with the kernel source for the GT-N8000 *does* match the kernel on the device, so there is no doubt that it is possible to get the configuration right.
Other Android vendors are just enabling the "embedded" config file in the kernel, so that the correct configuration is simply available on the device as "/proc/config.gz". This is so much less trouble. I suggest that you enable this option for Samsung kernels too.
Regards,
...
Click to expand...
Click to collapse
The GT-N8010 is also in the same situation you describe - config for 3.0.15 and jb stock kernel at 3.0.31, can't build working modules for stock.
davp, there seems to have been some activity at the Samsung open source center after my messages.
I suggest you make yourself heard as well. Use the "Inquiry" button next to the package download link in the table for your device.
To be able to add working modules to the device, the kernel configuration for the source has to be 100% compatible. It does not matter if any closed drivers are missing as we don't want to replace the kernel - but all those general debugging config options should be correct.
BTW, there is a history of similar issues:
http://forum.xda-developers.com/showthread.php?t=1123643
The kernel source for the GT-P3110 has been updated once more, and this time they have fixed the configuration.
With the latest JB update we can actually build working modules for the current firmware.
I confirmed this to the Samsung people and reminded them of the other devices in need of this fix: GT-P3100, GT-P5100, GT-P5110, GT-N7100 and probably more (like the GT-N8010).
JFDee said:
The kernel source for the GT-P3110 has been updated once more, and this time they have fixed the configuration.
With the latest JB update we can actually build working modules for the current firmware.
I confirmed this to the Samsung people and reminded them of the other devices in need of this fix: GT-P3100, GT-P5100, GT-P5110, GT-N7100 and probably more (like the GT-N8010).
Click to expand...
Click to collapse
So for now we might get stock kernel which will support 3G modems via USB OTG? How about other kernels such as CM10.1?
I'm looking for good 3G dongle then Any advices?
Additional kernel modules for stock JB P31xx (tested) and P51xx (untested), contains:
- usb_wwan, ppp_async, and option module for PPP Widget
- dns_resolver, md4, and cifs module for cifs/samba filesystem support
- sunrpc, lockd, and nfs module for nfs filesystem support
Kernel config file attached.
FTDI Single Port Serial Driver added.
cifs.ko not working on P3100 JB 4.1.2 (stock rooted)
ketut.kumajaya said:
Additional kernel modules for stock JB P31xx (tested) and P51xx (untested), contains:
- usb_wwan, ppp_async, and option module for PPP Widget
- dns_resolver, md4, and cifs module for cifs/samba filesystem support
- sunrpc, lockd, and nfs module for nfs filesystem support
Kernel config file attached.
Click to expand...
Click to collapse
Hi ketut.kumajaya,
I'm trying to use cifs.ko but i get:
/system/lib/modules # insmod cifs.ko
insmod: can't insert 'cifs.ko': unknown symbol in module or invalid parameter
I have:
/system/lib/modules # uname -a
Linux localhost 3.0.31-1084989 #1 SMP PREEMPT Mon Mar 25 14:53:07 KST 2013 armv7l GNU/Linux
I tried other cirs.ko with same result.
Can you give me some clues of what can I do?
Thank you.
Try insmod in order:
insmod dns_resolver.ko
insmod md4.ko
insmod cifs.ko
If something goes wrong, see the kernel messages using dmesg.
ketut.kumajaya said:
Try insmod in order:
insmod dns_resolver.ko
insmod md4.ko
insmod cifs.ko
If something goes wrong, see the kernel messages using dmesg.
Click to expand...
Click to collapse
Great!!!
That's the solution.
In my Tab 10.1 4.0.4 I'm loading (different kernel and different modules, of course):
insmod cifs.ko
insmod md4.ko
insmod nls_utf8.ko
So I was not thinking I should use a different order.
Thank you.
Hi,
So I've taken up the task to make a new kernel for Moto G 2014.
So if somebody could help me out in giving me different mods and tweaks ( BTW I'm still new at this).
Progress:
Updated Cyanogenmod Kernel msm8226 to Linux 3.4.110
Added a couple of new governers.
(I don't know how to 'change?' I/O shedulers).
Oh yeah if you are going to help me then please tell me how to add that feature to the kernel source(Just the terminal commands or link me to the page which tells me how to do it. Like I said I'm a newbie at this)
If somebody could help me out I'd be really grateful.