Hi
I'm trying to compile FUSE (the kernel module fuse.ko) for my Galaxy S2. (to run ntfs-3g)
My Galaxy S2 is running Android 2.3.3 (XWKF4)
Kernel: 2.6.35.7-I9100XWKF4-CL280512
modinfo of a working kernel module:
Code:
$ file vibrator.ko
vibrator.ko: ELF 32-bit LSB relocatable, ARM, version 1 (SYSV), not stripped
$ modinfo ./vibrator.ko
filename: ./vibrator.ko
license: GPL v2
description: TouchSense Kernel Module
author: Immersion Corporation
depends:
vermagic: 2.6.35.7-I9100XWKF4-CL280512 SMP preempt mod_unload modversions ARMv7
I tried to compile the module with different setups - but "insmod" on the device fails always with "insmod: init_module 'fuse.ko' failed (Exec format error)" and " fuse disagrees about version of symbol module_layout"
My setups were:
plain 2.6.35.7 Kernel + toolchain of Android NDK
Official GT-I9100 Source + Sourcery G++ Lite 2009q3-68 toolchain (Samsung recommended)
Official GT-I9100 Source Update 1+ Sourcery G++ Lite 2009q3-68 toolchain
Official GT-I9100 Source Update 2+ Sourcery G++ Lite 2009q3-68 toolchain
The builds of the three official Samsung sources gave me the following fuse.ko:
Code:
$ file ~/Desktop/fuse.ko
fuse.ko: ELF 32-bit LSB relocatable, ARM, version 1 (SYSV), not stripped
$ modinfo ~/Desktop/fuse.ko
filename: fuse.ko
alias: devname:fuse
alias: char-major-10-229
license: GPL
description: Filesystem in Userspace
author: Miklos Szeredi
depends:
vermagic: 2.6.35.7-I9100XWKF4-CL280512 SMP preempt mod_unload modversions ARMv7
parm: max_user_bgreq:Global limit for the maximum number of backgrounded requests an unprivileged user can set (uint)
parm: max_user_congthresh:Global limit for the maximum congestion threshold an unprivileged user can set (uint)
Has anyone a idea how to create a working fuse.ko?
Thanks!
Indeed does anyone have any information about compiling new kernel modules for the Galaxy SII?
edit. Found this for you, should solve your problem.
http://forum.xda-developers.com/showthread.php?t=1123643&highlight=compile+module#
How did you set the vermagic to the correct string? I just get:
2.6.35.7 SMP preempt mod_unload modversions ARMv7
without the I9100XWKF4-CL280512 part.
edit2. Never mind, appended it to the EXTRAVERSION variable in the Makefile.
How does one set kernel version?
I have disabled CONFIG_LOCALVERSION_AUTO and set CONFIG_LOCALVERSION to CONFIG_LOCALVERSION="evo3dguy".
I have even changed ro.build.display.id but the kernel version still displays Linux version 2.6.35.13-g84f8edd ([email protected]) (gcc version 4.4.0 (GCC) ) #1 SMP PREEMPT Fri Aug 5 01:14:20 CST 2011
From my understanding the g84f8edd would be added via CONFIG_LOCALVERSION_AUTO=y so I set it to # CONFIG_LOCALVERSION_AUTO is not set, which should disable it, so it can't git rev-parse --verify HEAD and display g84f8edd, yet it does anyway.
So what is needed to change this
Linux version 2.6.35.13-g84f8edd ([email protected]) (gcc version 4.4.0 (GCC) ) #1 SMP PREEMPT Fri Aug 5 01:14:20 CST 2011
Linux version 2.6.35.13-evo3dguy ([email protected]) (gcc version 4.4.0 (GCC) ) #1 SMP PREEMPT Fri Aug 5 01:14:20 CST 2011
I download the source from htc, made my changes build kernel but the version doesn't change, I have also downloaded other sources posted here and compiled those kernels they display the authors name.
So what do I need to change or add to have evo3dguy displayed?
evo3dguy said:
How does one set kernel version?
I have disabled CONFIG_LOCALVERSION_AUTO and set CONFIG_LOCALVERSION to CONFIG_LOCALVERSION="evo3dguy".
I have even changed ro.build.display.id but the kernel version still displays Linux version 2.6.35.13-g84f8edd ([email protected]) (gcc version 4.4.0 (GCC) ) #1 SMP PREEMPT Fri Aug 5 01:14:20 CST 2011
From my understanding the g84f8edd would be added via CONFIG_LOCALVERSION_AUTO=y so I set it to # CONFIG_LOCALVERSION_AUTO is not set, which should disable it, so it can't git rev-parse --verify HEAD and display g84f8edd, yet it does anyway.
So what is needed to change this
Linux version 2.6.35.13-g84f8edd ([email protected]) (gcc version 4.4.0 (GCC) ) #1 SMP PREEMPT Fri Aug 5 01:14:20 CST 2011
Linux version 2.6.35.13-evo3dguy ([email protected]) (gcc version 4.4.0 (GCC) ) #1 SMP PREEMPT Fri Aug 5 01:14:20 CST 2011
I download the source from htc, made my changes build kernel but the version doesn't change, I have also downloaded other sources posted here and compiled those kernels they display the authors name.
So what do I need to change or add to have evo3dguy displayed?
Click to expand...
Click to collapse
There are a few ways to go about changing this.
The most handy version I have at the moment is a flag to add to the make command:
make -j2 LINUX_VERSION="2.6.29 jk original"
I know there is a place in the kernel source code also you can edit. If you've downloaded somebody else's custom source code, grep the code for their linux version output. I want to say it was in the actual .config file is where I used to change it.
Hope that helps!
There are several way to do this. What I do is create a small bash script to compile my kernels.
Code:
#!/bin/bash
export LOCALVERSION="-Vampirefo"
make clean
make -j4
if I type uname -r
I get
2.6.35.14-Vampirefo
if i type
cat /proc/version
I get
Linux version 2.6.35.14-Vampirefo ([email protected]) (gcc version 4.4.4 (crosstool-NG 1.12.4) ) #1 SMP PREEMPT Sat Oct 22 22:18:02 EDT 2011
vampirefo said:
There are several way to do this. What I do is create a small bash script to compile my kernels.
Code:
#!/bin/bash
export LOCALVERSION="-Vampirefo"
make clean
make -j4
if I type uname -r
I get
2.6.35.14-Vampirefo
if i type
cat /proc/version
I get
Linux version 2.6.35.14-Vampirefo ([email protected]) (gcc version 4.4.4 (crosstool-NG 1.12.4) ) #1 SMP PREEMPT Sat Oct 22 22:18:02 EDT 2011
Click to expand...
Click to collapse
to bring the question round circle, in android about phone -> software information where it shows the kernel version, it obtains the information from the /proc/version file and then uses regex to parse and display!
hope that helps connect all the dots!
joeykrim said:
to bring the question round circle, in android about phone -> software information where it shows the kernel version, it obtains the information from the /proc/version file and then uses regex to parse and display!
hope that helps connect all the dots!
Click to expand...
Click to collapse
Joeykrim, Vampirefo
Thanks so much for the help and information, my kernel now displays what I wanted.
So we have a portal writer that has written multiple articles on the stuff I made and the stuff we've been doing. He asked us for more info on the Amaze source so he can write about it and help us get more recognition. Don't believe me? Look for yourself.
https://twitter.com/PoorCollegeGuy/status/222516466711396352
So can you say what new changes have been made. Did HTC make it harder on us to hack it? Did they not release anything we need? anything so we can get this published. Write it all here and I'll pass the link to this thread to him when we get responses.
Please, only respond here with information on source. NOTHING ELSE! I want to keep it nice and clean here.
Well my understanding is the wi-fi drivers are there they just commented out what we need to build it and a compat-wireless modules that they didn't include but i found another way to get it working just fine
sportsstar89 said:
Well my understanding is the wi-fi drivers are there they just commented out what we need to build it and a compat-wireless modules that they didn't include but i found another way to get it working just fine
Click to expand...
Click to collapse
That is one long run on sentence lol. Any other info you guys found out. We need to add more so he can write more about it!
hasoon2000 said:
That is one long run on sentence lol. Any other info you guys found out. We need to add more so he can write more about it!
Click to expand...
Click to collapse
Don't criticize my grammar and writing ability I go to school for that lol but my teachers tell me I'm the best writer in the class
Sent from my HTC_Amaze_4G using xda premium
sportsstar89 said:
Don't criticize my grammar and writing ability I go to school for that lol but my teachers tell me I'm the best writer in the class
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
hard to believe =D lol. But GETTING BACK ON THE TOPIC! lol. Any other info you guys find out?
Wifi is working using the existing modules that HTC provided. Currently we are still looking for a way to get the modules that are compiled by the kernel to work.
Sent from my HTC One X using xda premium
sportsstar89 said:
Well my understanding is the wi-fi drivers are there they just commented out what we need to build it and a compat-wireless modules that they didn't include but i found another way to get it working just fine
Click to expand...
Click to collapse
kozmikkick said:
Wifi is working using the existing modules that HTC provided. Currently we are still looking for a way to get the modules that are compiled by the kernel to work.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yeah, it appears that they commented out the building of the wl12xx drivers, but the stock ICS does have wl12xx modules. The evidence (commentd out makefile, presence of compat.ko, wl12xx.ko, wl12xx_sdio.ko, etc.) points to HTC using a version of compat-wireless drivers, but which one, I don't know. I also don't know if HTC made any modifications to the wireless drivers, but if they did, they'd be obligated by the GPL to release the updates.
Since the tweaks sportsstar used to get wifi work in his kernel worked, that means that we should have everything we need on the kernel side of things, we just need to get and build the proper version of compat wireless. I also wonder if we need to match the version of compat-wireless with the binary firmware blob from TI. In all the work building different versions of compat-wireless, it could be we also need the proper firmware.
oryan_dunn said:
Yeah, it appears that they commented out the building of the wl12xx drivers, but the stock ICS does have wl12xx modules. The evidence (commentd out makefile, presence of compat.ko, wl12xx.ko, wl12xx_sdio.ko, etc.) points to HTC using a version of compat-wireless drivers, but which one, I don't know. I also don't know if HTC made any modifications to the wireless drivers, but if they did, they'd be obligated by the GPL to release the updates.
Since the tweaks sportsstar used to get wifi work in his kernel worked, that means that we should have everything we need on the kernel side of things, we just need to get and build the proper version of compat wireless. I also wonder if we need to match the version of compat-wireless with the binary firmware blob from TI. In all the work building different versions of compat-wireless, it could be we also need the proper firmware.
Click to expand...
Click to collapse
The only problem with the current tweak to use existing wifi modules is that I think it may be breaking other functions. Not sure about this yet though.
When I get my amaze this week my plan is to try a few different firmware from ti. I think you're right about needing to swap out the blobs. If this is the case then it should make things pretty easy.
Sent from my HTC One X using xda premium
Ok, since this is a generic thread about ICS source, I'm moving all of my kernel ramblings here, instead of taking up space in Kozmik's kernel thread.
Anyways, I ran modinfo on all the modules in the T-Mobile ICS update. Here are the results:
Code:
filename: bluetooth.ko
alias: net-pf-31
license: GPL
version: 2.16
description: Bluetooth Core ver 2.16
author: Marcel Holtmann <[email protected]>
srcversion: 7F6941AC162E74AA0B26DAF
depends:
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
parm: disable_esco:Disable eSCO connection creation (bool)
parm: disable_ertm:Disable enhanced retransmission mode (bool)
parm: enable_hs:Enable High Speed (bool)
parm: enable_mgmt:Enable Management interface (bool)
parm: enable_le:Enable LE support (bool)
parm: force_acl_master:Always try to switch to master role on ACL link (int)
filename: bnep.ko
alias: bt-proto-4
license: GPL
version: 1.3
description: Bluetooth BNEP ver 1.3
author: Marcel Holtmann <[email protected]>
srcversion: 77A9BE70DF012F020FC7798
depends: bluetooth
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
parm: compress_src:Compress sources headers (bool)
parm: compress_dst:Compress destination headers (bool)
filename: btwilink.ko
license: GPL
version: 1.0
description: Bluetooth Driver for TI Shared Transport1.0
author: Raja Mani <[email protected]>
srcversion: 269FE2F6F705EA176E7CD4D
depends: bluetooth
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
filename: cfg80211.ko
description: wireless configuration support
license: GPL
author: Johannes Berg
depends:
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
parm: ieee80211_regdom:IEEE 802.11 regulatory domain code (charp)
parm: cfg80211_disable_40mhz_24ghz:Disable 40MHz support in the 2.4GHz band (bool)
filename: compat.ko
license: GPL
description: Kernel compatibility module
author: Luis R. Rodriguez
license: Dual BSD/GPL
author: Broadcom Corporation
description: Cordic functions
license: Dual BSD/GPL
author: Broadcom Corporation
description: CRC8 (by Williams, Ross N.) function
depends:
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
parm: compat_base_tree:The upstream tree used as base for this backport (charp)
parm: compat_base_tree_version:The git-describe of the upstream base tree (charp)
parm: compat_version:Version of the kernel compat backport work (charp)
filename: fm_drv.ko
license: GPL
depends:
staging: Y
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
filename: hid-magicmouse.ko
license: GPL
alias: hid:b0005v000005ACp0000030E
alias: hid:b0005v000005ACp0000030D
depends:
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
parm: emulate_3button:Emulate a middle button (bool)
parm: emulate_scroll_wheel:Emulate a scroll wheel (bool)
parm: scroll_speed:Scroll speed, value from 0 (slow) to 63 (fast)
parm: scroll_acceleration:Accelerate sequential scroll events (bool)
parm: report_touches:Emit touch records (otherwise, only use them for emulation) (bool)
parm: report_undeciphered:Report undeciphered multi-touch state field using a MSC_RAW event (bool)
filename: hidp.ko
alias: bt-proto-6
license: GPL
version: 1.2
description: Bluetooth HIDP ver 1.2
author: Marcel Holtmann <[email protected]>
srcversion: AC3509329E41D74FA70B7C0
depends: bluetooth
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
filename: mac80211.ko
license: GPL
description: IEEE 802.11 subsystem
depends: cfg80211
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
parm: ieee80211_default_rc_algo:Default rate control algorithm for mac80211 to use (charp)
parm: max_nullfunc_tries:Maximum nullfunc tx tries before disconnecting (reason 4). (int)
parm: max_probe_tries:Maximum probe tries before disconnecting (reason 4). (int)
parm: probe_wait_ms:Maximum time(ms) to wait for probe response before disconnecting (reason 4). (int)
filename: rfcomm.ko
alias: bt-proto-3
license: GPL
version: 1.11
description: Bluetooth RFCOMM ver 1.11
author: Marcel Holtmann <[email protected]>
srcversion: 436C8832D80BAD759212601
depends: bluetooth
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
parm: disable_cfc:Disable credit based flow control (bool)
parm: channel_mtu:Default MTU for the RFCOMM channel (int)
parm: l2cap_mtu:Default MTU for the L2CAP connection (uint)
parm: l2cap_ertm:Use L2CAP ERTM mode for connection (bool)
filename: wl12xx.ko
author: Juuso Oikarinen <[email protected]>
author: Luciano Coelho <[email protected]>
license: GPL
alias: platform:wl12xx
depends: cfg80211,mac80211
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
parm: debug_level:wl12xx debugging level (uint)
parm: fwlog:charp
parm: keymap:FW logger options: continuous, ondemand, dbgpins or disable
parm: bug_on_recovery:BUG() on fw recovery (bool)
parm: fref:FREF clock: 19.2, 26, 26x, 38.4, 38.4x, 52 (charp)
parm: tcxo:TCXO clock: 19.2, 26, 38.4, 52, 16.368, 32.736, 16.8, 33.6 (charp)
filename: wl12xx_sdio.ko
firmware: ti-connectivity/wl128x-fw-4-mr.bin
firmware: ti-connectivity/wl128x-fw-4-sr.bin
firmware: ti-connectivity/wl127x-fw-4-mr.bin
firmware: ti-connectivity/wl127x-fw-4-sr.bin
author: Juuso Oikarinen <[email protected]>
author: Luciano Coelho <[email protected]>
license: GPL
alias: sdio:c*v0097d4076*
depends: wl12xx
vermagic: 3.0.16-ga4fb83c SMP preempt mod_unload ARMv7
They are all GPL with the exception of compat.ko being dual licensed. I don't think that should be an issue (ie. doubt HTC had modifications) as I think that modules function is to interface with the other drivers (wl12xx, etc.) to the current kernel version. The rest are GPL and therefore HTC must release the source for it.
oryan_dunn said:
They are all GPL with the exception of compat.ko being dual licensed.
Click to expand...
Click to collapse
I'm not perfectly clear on dual licenses, so it should be posed to FSF, but from what I understand, it allows the code to be compatible with GPL and BSD projects. However, if used in a GPL project, I believe the GPL portion of the license is what takes effect, since the BSD portion is not compatible with the GPL project.
A quote from Linus Torvalds:
"This is no different from the fact that we have some drivers that are GPLv2/BSD licensed. Within the kernel, they are GPLv2. But on their own, you can choose to use them under the BSD license, make your changes to them, and release them commercially. And correct - I cannot (and neither can anybody else) then accept those *non*GPLv2 changes back."
Click to expand...
Click to collapse
I'm having trouble with "on their own" and "within the kernel".
I guess this simply means that if the modules are released within a kernel like a single entity then it has to be GPLv2 but if the module's source is not released as "part of the Linux kernel" but just like "a module to make that piece of hardware working with the Linux kernel" then it can be released under BSD license.
Sent from my HTC_Amaze
johnride said:
I guess this simply means that if the modules are released within a kernel like a single entity then it has to be GPLv2 but if the module's source is not released as "part of the Linux kernel" but just like "a module to make that piece of hardware working with the Linux kernel" then it can be released under BSD license.
Sent from my HTC_Amaze
Click to expand...
Click to collapse
The only module that's dual licensed is the compat.ko module, not the actual driver files, which are all still GPL. I assume that if HTC did make modifications to compat.ko, that they'd have to update the license to say BSD and not BSD/GPL. I believe all the code in compat-wireless is from the kernel itself, just a newer version, that you compile for an older kernel.
On another note, I am supposed to get a call from HTCdev escalation on the GPL driver issue. I wonder if the person who will call me will actually know what's going on, or if it will just be the generic customer support escalation team.
oryan_dunn said:
I assume that if HTC did make modifications to compat.ko, that they'd have to update the license to say BSD and not BSD/GPL.
Click to expand...
Click to collapse
I'm still fuzzy on dual licensing, but seeing that HTC released the module as dual licensed (GPL/BSD), doesn't that allow the user to decide the license? So, if you decide that it is GPL, shouldn't they release the source for it?
oryan_dunn said:
On another note, I am supposed to get a call from HTCdev escalation on the GPL driver issue. I wonder if the person who will call me will actually know what's going on, or if it will just be the generic customer support escalation team.
Click to expand...
Click to collapse
Either way, keep up the good fight.
brainbone said:
Either way, keep up the good fight.
Click to expand...
Click to collapse
Well, becuase 6pm eastern is within the window of 8-11pm eastern I told them to call, I missed their call. I'll try calling them tonight.
Just a heads up, we are going to have an article written on this soon. Our portal writer is going fix up some small kinks and then we will hopefully have more exposure and support.
http://www.xda-developers.com/android/telus-amaze-4g-ics-kernel-source-released-no-ti-wlan-present/
Sent From My HTC Amaze 4G Via Someone's Room
I ended up talking to HTC this weekend. It was as I expected, some guy who couldn't really do anything, but he listened and wasn't really all that hostile. He said he'd pass it on to the dept responsible. I told him that HTC was oblicated to release the source for all GPL code and that they need to release it the day the executable code is in the hands of customers. We'll see if it leads anywhere.
oryan_dunn said:
I ended up talking to HTC this weekend. It was as I expected, some guy who couldn't really do anything, but he listened and wasn't really all that hostile. He said he'd pass it on to the dept responsible. I told him that HTC was oblicated to release the source for all GPL code and that they need to release it the day the executable code is in the hands of customers. We'll see if it leads anywhere.
Click to expand...
Click to collapse
Im hoping the tmo kernel source might include what the devs need, but has htc released stuff like this by itself?
Sent from my iPad using Tapatalk HD
oryan_dunn said:
I ended up talking to HTC this weekend. It was as I expected, some guy who couldn't really do anything, but he listened and wasn't really all that hostile. He said he'd pass it on to the dept responsible. I told him that HTC was oblicated to release the source for all GPL code and that they need to release it the day the executable code is in the hands of customers. We'll see if it leads anywhere.
Click to expand...
Click to collapse
Well this is what i got from the gb drivers
filename: /home/steve/modules/kineto_gan.ko
license: GPL
version: 1.0
alias: gannet
description: Kineto GAN Virtual Ethernet Device
srcversion: FA8E773097534C9326F7196
depends:
vermagic: 2.6.35.13-g52e85af SMP preempt mod_unload ARMv7
Click to expand...
Click to collapse
filename: /home/steve/modules/st_drv.ko
license: GPL
description: Shared Transport Driver for TI BT/FM/GPS combo chips
author: Pavan Savoy <[email protected]>
depends:
staging: Y
vermagic: 2.6.35.13-g52e85af SMP preempt mod_unload ARMv7
Click to expand...
Click to collapse
filename: /home/steve/modules/tiap_drv.ko
license: Dual BSD/GPL
description: TI WLAN Embedded Station Driver
author: Ohad Ben-Cohen <[email protected]>
alias: TIWLAN_SDIO
license: GPL
description: TI WLAN 1283 SDIO interface
alias: sdio:c07v*d*
depends:
vermagic: 2.6.35.13-g52e85af SMP preempt mod_unload ARMv7
parm: driver_status:int
parm: g_sdio_debug_level:TIWLAN SDIO debug level (int)
Click to expand...
Click to collapse
filename: /home/steve/modules/ti_hci_drv.ko
license: GPL
depends: st_drv
staging: Y
vermagic: 2.6.35.13-g52e85af SMP preempt mod_unload ARMv7
Click to expand...
Click to collapse
filename: /home/steve/modules/tiwlan_drv.ko
author: Ohad Ben-Cohen <[email protected]>
alias: TIWLAN_SDIO
license: GPL
description: TI WLAN 1283 SDIO interface
license: Dual BSD/GPL
description: TI WLAN Embedded Station Driver
alias: sdio:c07v*d*
depends:
vermagic: 2.6.35.13-g52e85af SMP preempt mod_unload ARMv7
Click to expand...
Click to collapse
But tiwlan_drv.ko and tiap_drv.ko doesn't get built while compiling the kernel
My response from HTC was that they were using proprietary drivers.
Even still since the source is available from Texas it should be possible to use their code if we swap out the firmware. May have to do some calibrations and build our own WPA_supplicant though.
Sent from my HTC One X using xda premium
Hallo,
Is there someone here who can create a tun.ko VPN Adapter for the Archos XS JB?
I am desperately looking for it,
Thanks, Ingo
Hi !
please , can you post here :
> adb shell uname -a
> adb shell uname -r
...also please > adb shell cat /proc/version
Thanks !
Linux localhost 3.0.21 #1 SMP PREEMPT Tue Dec 4 23:29:16 CET 2012 armv7l unknown
3.0.21
Linux version 3.0.21 ([email protected]) (gcc version 4.4.1 (GCC) ) #1 SMP PREEMPT Tue D
ec 4 23:29:16 CET 2012
IngoPan said:
Linux localhost 3.0.21 #1 SMP PREEMPT Tue Dec 4 23:29:16 CET 2012 armv7l unknown
3.0.21
Linux version 3.0.21 ([email protected]) (gcc version 4.4.1 (GCC) ) #1 SMP PREEMPT Tue D
ec 4 23:29:16 CET 2012
Click to expand...
Click to collapse
OK , thanks !
Here is your tun.ko ! :good:
...also, I had reached the same result, but I was not 100% sure
[email protected]:~/archos/g10/firm/raw$ dd if=zImage bs=1 skip=836674 | lzop | strings | grep 'Linux version'
Linux version 3.0.21 ([email protected]\
3392386+0 records in
3392386+0 records out
3392386 bytes (3.4 MB) copied, 1.47227 s, 2.3 MB/s
Click to expand...
Click to collapse
THANKS! But to get this working, we need the rooted initramfs you posted in the the other thread. Right now, its just impossible to flash the initramfs (initramfs could not be found).
Hello! Could you please re-share this tun.ko?
Hallo,
i want to upstream-patch a kernel (with patches from kernel. org). Cat /proc/version gives me that (and uname -a even less):
Linux version 3.4.0-cyanogenmod-g57d54c6 ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue Oct 21 07:11:50 PDT 2014
How can i determine the exact kernel version like 3.4.104?
It's probably not needed for CM kernels but Samsung kernel use the same pattern and for incremental patches i need the exact version number i guess.
DualJoe said:
Hallo,
i want to upstream-patch a kernel (with patches from kernel. org). Cat /proc/version gives me that (and uname -a even less):
Linux version 3.4.0-cyanogenmod-g57d54c6 ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue Oct 21 07:11:50 PDT 2014
How can i determine the exact kernel version like 3.4.104?
It's probably not needed for CM kernels but Samsung kernel use the same pattern and for incremental patches i need the exact version number i guess.
Click to expand...
Click to collapse
Your Kernel is 3.4.0-cyanogenmod-g57d54c6, if thats what you wanted to know.
Tommy-Geenexus said:
Your Kernel is 3.4.0-cyanogenmod-g57d54c6, if thats what you wanted to know.
Click to expand...
Click to collapse
Not exactly. The latest 3.4 kernel is 3.4.104. The one that Samsung provides for the I9506 is probably 3.4.98, 3.4.92 or something else. Correct me if i'm wrong, but i need to know the exact version of my kernel to use the incremental patches from kernel.org to get to latest patch state.
Edit:
This is the output of the target kernel:
Code:
# uname -a
Linux localhost 3.4.0 #3 SMP PREEMPT Tue Sep 23 23:09:10 CEST 2014 armv7l GNU/Linux
# cat /proc/version
Linux version 3.4.0 (gcc version 4.8 (GCC) ) #3 SMP PREEMPT Tue Sep 23 23:09:10 CEST 2014
DualJoe said:
Not exactly. The latest 3.4 kernel is 3.4.104. The one that Samsung provides for the I9506 is probably 3.4.98, 3.4.92 or something else. Correct me if i'm wrong, but i need to know the exact version of my kernel to use the incremental patches from kernel.org to get to latest patch state.
Edit:
This is the output of the target kernel:
Code:
# uname -a
Linux localhost 3.4.0 #3 SMP PREEMPT Tue Sep 23 23:09:10 CEST 2014 armv7l GNU/Linux
# cat /proc/version
Linux version 3.4.0 (gcc version 4.8 (GCC) ) #3 SMP PREEMPT Tue Sep 23 23:09:10 CEST 2014
Click to expand...
Click to collapse
Like i said, your kernel is 3.4.0.
No oem upstreams their kernels.
You need to start upstreaming from the scratch.
Sent from my Xperia Z C6603
Tommy-Geenexus said:
Like i said, your kernel is 3.4.0.
No oem upstreams their kernels.
You need to start upstreaming from the scratch.
Click to expand...
Click to collapse
Oh, i didn't know that. I can probably check first patch diffs as well then to double prove that. At least the minor "0" in "3.4.0" makes sense now. The good thing probably is i can use the all-in-one patch so i don't need to use all the incremental patches one by one.
Thank you for clearing that up.