Hi,
I am one of those who want to upload custom kernel in my Nexus S (SHW-M200K which is for Korean). When I updated my android by the methods in android source. It worked.
I also downloaded android kernel by using following commands.
$ git clone samsung.git kernel
$ git branch -a
$ git checkout remotes/origin/android-samsung-2.6.35-gingerbread
And, configured the kernel using herring_defconfig without any modification. The compilation was okay, but the device cannot be booted. I used fastboot to flash my new kernel into the device.
I am wondering if I know how to make the device booted with my new kernel.
Second, I want to see the kernel bootlog, the device is not working with my kernel, so I cannot use adb shell dmesg. Is there a way to see device's serial out? and is there a way to configure the kernel to make it show kernel logs to microUSB port?
I googled and found some links, unfortunately I cannot pase the url because I am newbie , but I did not work in my environment. The contents of the link uses 150k resistor to link ID and GND of microUSB ports and links D+/D- to UART port.
I also found some threads about Nexus S's kernel console out, but they have a little message which makes me confused.
I also found microUSB to serial cable, which is named as FlexSerial™ Serial (RS232) Data Cable for Samsung Nexus S, I cannot also attach url links, and you can easily found the module by using google. But I am not sure it will work or not. Is there anybody used this device?
Finally, I will also wonder if I know a specific configuration in kernel to see kernel's serial out?
It would be very nice if you let me know how to do or give me useful links.
Thanks in advance.
I am using the nightly build of CM for galaxy s2 I-9100. I can compile and install from recovery to my phone, but I need to compile the /driver/usb/serial/ftdi_sio.c driver file into a .ko file that I can insmod into the kernel.
I have tried compiling with make modules ARCH=arm CROSS_COMPILER=..../arm-eabi-
It compiles for the wrong kernel.
I want to use the mm() function from . build/envsetup.sh. However I don't know how to setup the Android.mk file.
Does anyone know how to alter the properties of the CM9 mod so that it compiles the ftdi_sio driver dynamically or statically for the kernel?
I am trying to connect a FTDI usb-to-serial chip to the S2 in order to control an arduino custom board.
All help will be greatly appreciated.
Edit: I have tryed the "make menuconfig" and set the ftdi-sio.c to be a module, but ". build/envsetup.sh" and "mm()" seem to ignore it. Are they using a different .config file that is located elsewhere?
sddimitrov said:
I am using the nightly build of CM for galaxy s2 I-9100. I can compile and install from recovery to my phone, but I need to compile the /driver/usb/serial/ftdi_sio.c driver file into a .ko file that I can insmod into the kernel.
I have tried compiling with make modules ARCH=arm CROSS_COMPILER=..../arm-eabi-
It compiles for the wrong kernel.
I want to use the mm() function from . build/envsetup.sh. However I don't know how to setup the Android.mk file.
Does anyone know how to alter the properties of the CM9 mod so that it compiles the ftdi_sio driver dynamically or statically for the kernel?
I am trying to connect a FTDI usb-to-serial chip to the S2 in order to control an arduino custom board.
All help will be greatly appreciated.
Click to expand...
Click to collapse
I build modules like this
Code:
cd ~/Android/Build/kernel-msm
ARCH=arm CROSS_COMPILE=~/Android/Build/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- make menuconfig
Then when menuconfig comes, search module and instead of Y or N, press M and then save. It will build .ko file.
Are you electronical engineer?. Nice to see some people like me here .
Btw, if you can get arduino any wireless communication between arduino and Android, it will be so cool (I did some time ago with BT).
Cyanogen uses different kernel
:Yes I am an EE at UCLA
I tried changing the menuconfig. When I set it in
Code:
~/android/system/kernel/samsung/smdk4210$ make menuconfig ARCH=arm CROSS_COMPILER=/opt/arm-eabi-
It changes the ftdi_sio to be a module, but then
Code:
. build/envsetup samsung kernel
it ignores that .config file
If I change the .config in
Code:
~/android/system/kernel/samsung/smdk4210/build/galaxys2/
and then run the cyanogenmod build command, it resets my config file.
Compiling using
Code:
~/android/system/kernel/samsung/smdk4210$ make SUBDIRS=drivers/usb/serial ARCH=arm CROSS_COMPILER=opt/toolchains/arm-eabi-4.4.3/bin/arm-eabi-
Compiles the modules, but when I try to
Code:
insmod ftdi_sio.ko
I get
Code:
ftdi_sio: version magic '3.0.15+ mod_unload modversions ARMv5 ' should be '3.0.15-CM-ge1bddfe-dirty SMP preempt mod_unload ARMv7 p2v8 '
I also get this warning when I compile them using make
Code:
WARNING: Symbol version dump /home/stoyan/android/system/kernel/samsung/smdk4210/Module.symvers
is missing; modules will have no dependencies and modversions.
How do I compile this module right? Any suggestions?
sddimitrov said:
Compiles the modules, but when I try to
Code:
insmod ftdi_sio.ko
I get
Code:
ftdi_sio: version magic '3.0.15+ mod_unload modversions ARMv5 ' should be '3.0.15-CM-ge1bddfe-dirty SMP preempt mod_unload ARMv7 p2v8 '
Click to expand...
Click to collapse
Edit scripts/setlocalversion
Find the following lines :
Code:
# running further git commands
if $short; then
echo "+"
return
fi
Change the line - echo "+" to echo ""
Now edit your .config file
Find CONFIG_LOCALVERSION
Change to CONFIG_LOCALVERSION="-CM-ge1bddfe-dirty"
ARMv5 ? Try with this toolchain https sourcery.mentor dot com/sgpp/lite/arm/portal/release2032 ( sorry i can't post link )
Hope this will help.
Has anyone tested if it works on our tab or not....Plus does anyone know ho to find the power output of our tab's usb host mode????
I'll be geting my new usbotg cable soon so i'll also try n post the result....
For those who don't know about pppwidget, its a which allows you to use your 3G/2G stick(dongle) on your tab using the otg cable...
Market link
Read More about project here..
Hi thanks for this information, I tried this and it requires extra kernel modules (option, which is not included in cm10 kernel).
proudfoot said:
Hi thanks for this information, I tried this and it requires extra kernel modules (option, which is not included in cm10 kernel).
Click to expand...
Click to collapse
Can you please tell the steps you took and the result you got...This isn't supposed to need any modules except usb_modswitch which it already include....It works on CM10 nexus 7 too...Which dongle did you use???
Yup, it works it requires couple of modules not included in cm10 p5100 kernel, i already build the modules (see attachment) . Enjoy
I uses zte cdma modem, that modem requires 'option' module but most 3g/CDMA dongle uses this module.
You just need to copy those modules to /system/lib/modules.
edit: forgot to actually attaching the modules ~_~
Update: Vpn doesn't seem to work with pppwidget.
Update2: works, needs to manually set the gateway
cool...i'll get back to you in couple of days(waiting for my new otg cable)... can you please give the .c file for the modules also....still learning all this stuff so wlll be helpful....
kan_bleach said:
cool...i'll get back to you in couple of days(waiting for my new otg cable)... can you please give the .c file for the modules also....still learning all this stuff so wlll be helpful....
Click to expand...
Click to collapse
clone it from here -> https://github.com/cmenard/android_kernel_samsung_espresso10
as for compiling it follow/adapt from this tutorial -> http://stevechui.blogspot.com/2011/10/compiling-kernel-modules-tunko-for.html
Its giving 'port not found'....any solutions??
Did you directly connected the dongle to tab or used a powered hub???
kan_bleach said:
Its giving 'port not found'....any solutions??
Did you directly connected the dongle to tab or used a powered hub???
Click to expand...
Click to collapse
Directly, what the log (it should be in /sdcard/pppwidget/log/) say?
edit: actually with this -> http://www.amazon.com/Samsung-EPL-1PL0BEGXAR-USB-Connection-Kit/dp/B005518J6Q it's still count as directly right?
proudfoot said:
Directly, what the log (it should be in /sdcard/pppwidget/log/) say?
edit: actually with this -> http://www.amazon.com/Samsung-EPL-1PL0BEGXAR-USB-Connection-Kit/dp/B005518J6Q it's still count as directly right?
Click to expand...
Click to collapse
Yup that's direct
Checked the log...mod_switch successful, but loading option module fails...option.ko is in the correct folder..
I tried insmod but it says operation not permitted...
Tried su and then insmod but then it says failed (trying using terminal emulator)..
kan_bleach said:
Yup that's direct
Checked the log...mod_switch successful, but loading option module fails...option.ko is in the correct folder..
I tried insmod but it says operation not permitted...
Tried su and then insmod but then it says failed (trying using terminal emulator)..
Click to expand...
Click to collapse
Your option.ko probably not compatible with the kernel, try to do
Code:
strings option.ko | grep vermagic
uname -a
and compare both output, it should be similar.
also if you use insmod I think you'll need to insmod usb_wwan.ko first, because option.ko depends on that module, so it should be
Code:
insmod usb_wwan.ko
insmod option.ko
then, move the pppwidget to launcher and plug the dongle.
proudfoot said:
Your option.ko probably not compatible with the kernel, try to do
Code:
strings option.ko | grep vermagic
uname -a
and compare both output, it should be similar.
also if you use insmod I think you'll need to insmod usb_wwan.ko first, because option.ko depends on that module, so it should be
Code:
insmod usb_wwan.ko
insmod option.ko
then, move the pppwidget to launcher and plug the dongle.
Click to expand...
Click to collapse
Tried the command...output is the same...still not able to use insmod...
Log
Code:
USB_ModeSwitch log from Sat Oct 27 16:23:19 IST 2012
Raw args from udev: 1-1.4/1-1.4:1.0
Using top device dir /sys/bus/usb/devices/1-1.4
----------------
USB values from sysfs:
manufacturer ZTE, Incorporated
product USB Storage
serial 000000000002
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/19d2.fff5
! matched. Reading config data
config: TargetVendor set to 19d2
config: TargetProductList set to fff1,fffe,ffff
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Logger is: /system/bin/log
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 14 -v 19d2 -p fff5 -f $configBuffer
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.4 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x19d2
DefaultProduct= 0xfff5
TargetVendor= 0x19d2
TargetProduct= not set
TargetClass= not set
TargetProductList="fff1,fffe,ffff"
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="5553424312345678c00000008000069f030000000000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 001/014 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 19d2:fff5
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x0a (out) and 0x89 (in)
USB description data (for identification)
-------------------------
Manufacturer: ZTE, Incorporated
Product: USB Storage
Serial No.: 000000000002
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x0a for message sending ...
Trying to send message 1 to endpoint 0x0a ...
OK, message successfully sent
Resetting response endpoint 0x89
Resetting message endpoint 0x0a
Could not reset endpoint (probably harmless): -34
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Waiting for device file system (1 sec.) ...
Reading attributes ...
All attributes matched
Mode switching was successful, found 19d2:fff1 (ZTE, Incorporated: ZTE CDMA Tech)
Now checking for bound driver ...
No driver has bound to interface 0
Module loader is /system/bin/insmod
Trying to find module "option"
Have you try to insert those modules manually first, before running pppwidget and plug-in the dongle? I think we use the same dongle, so it should works ~_~
anyway this is how i get this to work:
1. create directory /data/loca/modules/ on tab
2. move all those modules (option.ko, usb_wwan.ko, ppp_async.ko) to this directory.
3. su and insmod all those modules:
Code:
insmod /data/local/modules/usb_wwan.ko
insmod /data/local/modules/option.ko
insmod /data/local/modules/ppp_async.ko
5. move pppwidget to launcher and plug the dongle.
optional:
create this script and put it in /data/local/userinit.d/93loadmod directory
Code:
#!/system/bin/sh
/system/bin/insmod /data/local/modules/usb_wwan.ko
/system/bin/insmod /data/local/modules/option.ko
/system/bin/insmod /data/local/modules/ppp_async.ko
so it will load all those modules at boot time.
I am doing the same thing...but insmod is giving error
When i run the insmod command i get
insmod: init_module 'usb_wwan.ko' failed(Exec format error)
kan_bleach said:
insmod: init_module 'usb_wwan.ko' failed(Exec format error)
Click to expand...
Click to collapse
From a bit of googling it looks like your module is not build for your kernel (or even build for wrong architecture), what is your kernel? and where do you get the modules, do you compile it yourself or is it from somebody else?
try to do dmesg after you do insmod to see more information.
btw, the module that i have posted only works for p5100 and cm10 kernel (3.0.8-CM-g11fad65)
proudfoot said:
From a bit of googling it looks like your module is not build for your kernel (or even build for wrong architecture), what is your kernel? and where do you get the modules, do you compile it yourself or is it from somebody else?
try to do dmesg after you do insmod to see more information.
btw, the module that i have posted only works for p5100 and cm10 kernel (3.0.8-CM-g11fad65)
Click to expand...
Click to collapse
I used the modules you posted...I am using CMOC-10 kernel....Maybe that is the issue...But the kernels are supposed to be identical except for the OC and the governors feature...i am on 3.0.8-CM-gbd034d0
kan_bleach said:
gbd034d0
Click to expand...
Click to collapse
Yup that the problem, it needs to have the same extra version number even though it comes from same source. I guess I could compile it for you.
proudfoot said:
Yup that the problem, it needs to have the same extra version number even though it comes from same source. I guess I could compile it for you.
Click to expand...
Click to collapse
Please do...
kan_bleach said:
Please do...
Click to expand...
Click to collapse
Here, I hope it works because it comes from cm10 source, I only change the extra version to match yours.
proudfoot said:
Here, I hope it works because it comes from cm10 source, I only change the extra version to match yours.
Click to expand...
Click to collapse
Thanks i'll try and post the result...can you give me the github link for the cm10 kernal for our tab???
I posted a question earlier that got no traction regarding compiling the RTL8187 drivers for the infinity for use in backtrack for ARM.
I have since completed the compile and have successfully used the adapter I bought on the tablet with them. What is attached are the compiled compat-wireless drivers, specifically: compat-wireless-3.6.8-1-snpc.tar.bz2
They include the "mac80211.compat08082009.wl_frag+ack_v1.patch" and the "channel-negative-one-maxim.patch"
I am attaching them for those interested or who have a similar need. I am not interested in being bombarded with questions/complaints about it not working for them or whatever. I may post a tutorial later with the problems I ran across and how I compiled these drivers that may help others with different chipsets.
These drivers work successfully with BT5 for ARM on my infinity and an ebay RTL8187L chipset external USB wireless device. To see more ID's they might work check here for RTL8187 PCI ID's that compat-wireless drivers might work for: http://linuxwireless.org/en/users/Drivers/rtl8187
Once in backtrack you will need to MAKE SURE the built in wireless is turned off on the tablet then in terminal with SU:
rmmod bcmdhd.ko
You will have to have the compat-wireless package I referenced above downloaded and uncompress and run: make wlunload in the folder you uncompress it to.
This will get rid of cfg80211.ko rmmod would probably work for that too but I know this works.
Now insmod in the following order:
insmod eeprom_93cx6.ko
insmod compat.ko
insmod cfg80211.ko
insmod mac80211.ko
insmod rtl8187.ko
It can all be scripted, feel free to do so.
With your wireless device plugged in to USB run airmon-ng and you should see your card in the list.
You will have to of course reboot to re-enable the built-in wireless.
Enjoy!
If you ever get the time I would appreciate a brief tutorial on the steps you took to build the modules. I've been struggling with doing this on the nexus 7 for a few days now and don't seem to be making much headway.
Nexus 7
Hi,
Yes please post a tutorial as I'm using a Nexus 7 also.
I already use a modified kernel on my Galaxy Nexus where I don't need to do those modification it's all built in the kernel (http://www.kernel-xp.net/index.php/en/) and would like the same but I would also take your procedure
Thank you!
I am also working on this and need help, to install the compat drivers i need the source code for my kernel but i dont know where or how to unpack the source code so that compat wireless will recognize it, i think it said in /lib/modules/*mykernelsource* if anyone is reading this and can help please reply with instructions thank you
compiling and building modules
alexcass4 said:
I am also working on this and need help, to install the compat drivers i need the source code for my kernel but i dont know where or how to unpack the source code so that compat wireless will recognize it, i think it said in /lib/modules/*mykernelsource* if anyone is reading this and can help please reply with instructions thank you
Click to expand...
Click to collapse
This is something that I am also struggling with. Any help or direction would be much appreciated.