Related
Hi,
I've being watching all the developments about the emerging tablets and I must say that all Tegra 250 devices look very interesting, although Toshiba Folio 100 already has PCB pads to add more ram... I am sure that Toshiba will add more 500Mb ram on the next Folio to give a better android 2.3 support.
Anyway, here's my question: how can I, or anyone else, recompile the Linux android kernel for Tegra 250 and place it in the FolioMod, well, I'm asking this because I remembered that these tablets are excellent for one thing that many are forgetting...
To watch digital television from a USB TV pen, well, the device has USB host support, it has Linux to manage the devices attached... What else is need ? Video 4 Linux... This is kernel built-in... So, how can I recompile the kernel to add this and other desktop usual features ? Any cons ?
Cheers.
TiagoSilva said:
Hi,
I've being watching all the developments about the emerging tablets and I must say that all Tegra 250 devices look very interesting, although Toshiba Folio 100 already has PCB pads to add more ram... I am sure that Toshiba will add more 500Mb ram on the next Folio to give a better android 2.3 support.
Anyway, here's my question: how can I, or anyone else, recompile the Linux android kernel for Tegra 250 and place it in the FolioMod, well, I'm asking this because I remembered that these tablets are excellent for one thing that many are forgetting...
To watch digital television from a USB TV pen, well, the device has USB host support, it has Linux to manage the devices attached... What else is need ? Video 4 Linux... This is kernel built-in... So, how can I recompile the kernel to add this and other desktop usual features ? Any cons ?
Cheers.
Click to expand...
Click to collapse
I am interested in too, if you make any advance let me know; I am really interested in this!!!!
The process is quite straightforward.
Get the kernel source here: http://tegramid.com/wiki/Main_Page
- unzip the source and cd into the source directory
Get the current kernel config from your device:
Code:
adb pull /proc/config.gz
Unpack and rename the config file
Code:
gunzip config.gz
mv config .config
Adjust the config to your needs.
Now you need the an gcc to compile for arm, the easiest way is to checkout the android source repository (read source.android.com for instructions, actually you would only need the prebuilt toolchain)
Now add the compiler to your path environment variable
Code:
export PATH=<android-source-dir>/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/:$PATH
now you can build the kernel using
Code:
make ARCH=arm CROSS_COMPILE=arm-eabi-
Now you need to repack and flash your new kernel to the device.
An excellent article on how to prepare a new boot.img can be found here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
After that simply create an update.zip and flash using recovery.
Note, AFAIK v4l support is already included in the current FolioMod kernel.
WOW
Really thanks, I will try asap!!
Btw according to dmesg output kernel commandline should be:
Code:
[email protected] [email protected] vmalloc=192M video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=recovery:122000:a00:800,linux:a0e00:1000:800,loader:300:400:800,mbr:700:200:800,system:900:20000:800,cache:20900:80000:800,misc:a0900:400:800,userdata:a1f00:80000:800 boardtype=PR
weeds2000:
So, the kernel is the common Android Tegra 250, have you tried this already ?
I though this could be the thing to do, but I also thought that Toshiba had pulled a fast one by customizing the Android Tegra 250 kernel...
Hum... If this is so, I will buy an Toshiba Folio 100 lol... I hope to add many thing to the kernel... as a programmer I would love to have USB-RS232 adapters too eh eh eh... New horizons then!
I was also thinking, if not this device, the Viewsonic Viewpad 10, that has a BIOS and an Atom, an x86 architecture then, would be much easier to recompile...
It has some modifications ore extra modules.
Compiling the default kernel from the froyo-tegra tree from nvidia failed (not sure what exactly was missing, display simply switched off and it seems there was a kernel panic somewhere)
But yes compiling the kernel from the sources given at the wiki works. I'm running a slightly modified kernel at the moment compiled using the steps given above.
weeds2000:
Its common on embedded devices like most Android devices... The best thing invented is the BIOS lol... Without one, we must hard-code the kernel to map the resources to the specific hardware...
Do you recommend buying a Toshiba Folio 100 ?
Anyway, what modifications have you done (just curious) ?
I would recommend the Folio to someone that can do some modding and is able to flash custom roms to the device.
Before FolioMod the device was pretty much useless to me, but with the modifications done by dexter and the rest of us, it turned out to be a pretty good device.
However I would not order it blind because of the display. Compared to, for example the Galaxy Tab, you can clearly see why the device is that cheap. Viewing angle is really not good on this, so you may want to take a look at a store or something if this bother you or not (it's OK for me though).
Kernel modifications where
- mouse driver (to fix the bug introduced by the rotation fix, without success up to now)
- playing around with the kernel hacking options to get some performance. turning them off however prevent the wifi module to load
- adding utf8 NLS support to the kernel (also this is the default, as this is required to mount NTFS partitions with utf8 support, otherwise some files where missing or have bad encoding and could not be opend by mediaplayer/reader/whatever.
When you do the make config, in the kernel options menu do you recall seeing the video4linux ?
I'm guessing that the tablet only needs that included on the built kernel to fire up TV watching programs, the idea is to load a USB digital TV device and run any Linux TV programs. Not going to MythTV because it might have too many dependencies... and not all libraries are available to ARM...
The view angle doesn't bother me that much, as long as the screen image is flawless eh eh eh, its a media tablet, so, it should be anyway...
One more thing, that key combination to flash the device comes already from factory right? I recall seeing a similar combination on the NVidea Tegra 250 development board. Or does it need the Dexter flasher too ?
I'm new to tablets as you can see lol and I'm seeing lots of tasty looking tablets... I want one that I can use for hack in my (I wish) free time, I guess its just like most people here lol.
The Viewpad 10 is about the same price, has x86 (single core tho) and more 500MB ram and ... a BIOS ... But has pros and cons... damn why can't we have it all... I guess I will try to see some in my hands first. iPad looks great, but lacks connectivity and Apple wants money for a developer membership lol... Android is incredibly but the vendors are crooks that embed the kernel with the hardware instead of adding a BIOS... Windows Mobile is... to limited and simple to use, no console... bah... Is there was one for free I would pick that one, but they all have similar prices... The reviews show that all have pros and cons... oh well...
OK getting mythTV on the device is quite an impressive task.
As not even the c-library is the default glibc known from your desktop PC and may miss a few things here and there. (learned that when trying to port libfuse and ntfs-3g)
To me it seems like v4l is included, this is the config from the multimedia section:
Code:
#
# Multimedia drivers
#
# CONFIG_MEDIA_ATTACH is not set
CONFIG_MEDIA_TUNER=y
# CONFIG_MEDIA_TUNER_CUSTOMISE is not set
CONFIG_MEDIA_TUNER_SIMPLE=y
CONFIG_MEDIA_TUNER_TDA8290=y
CONFIG_MEDIA_TUNER_TDA9887=y
CONFIG_MEDIA_TUNER_TEA5761=y
CONFIG_MEDIA_TUNER_TEA5767=y
CONFIG_MEDIA_TUNER_MT20XX=y
CONFIG_MEDIA_TUNER_XC2028=y
CONFIG_MEDIA_TUNER_XC5000=y
CONFIG_MEDIA_TUNER_MC44S803=y
CONFIG_VIDEO_V4L2=y
CONFIG_VIDEO_V4L1=y
CONFIG_VIDEO_CAPTURE_DRIVERS=y
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set
CONFIG_VIDEO_HELPER_CHIPS_AUTO=y
# CONFIG_VIDEO_VIVI is not set
# CONFIG_VIDEO_CPIA is not set
# CONFIG_VIDEO_CPIA2 is not set
# CONFIG_VIDEO_SAA5246A is not set
# CONFIG_VIDEO_SAA5249 is not set
# CONFIG_SOC_CAMERA is not set
CONFIG_V4L_USB_DRIVERS=y
CONFIG_USB_VIDEO_CLASS=y
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
CONFIG_USB_GSPCA=m
# CONFIG_USB_M5602 is not set
# CONFIG_USB_STV06XX is not set
# CONFIG_USB_GL860 is not set
# CONFIG_USB_GSPCA_CONEX is not set
# CONFIG_USB_GSPCA_ETOMS is not set
# CONFIG_USB_GSPCA_FINEPIX is not set
# CONFIG_USB_GSPCA_JEILINJ is not set
# CONFIG_USB_GSPCA_MARS is not set
# CONFIG_USB_GSPCA_MR97310A is not set
# CONFIG_USB_GSPCA_OV519 is not set
# CONFIG_USB_GSPCA_OV534 is not set
# CONFIG_USB_GSPCA_PAC207 is not set
# CONFIG_USB_GSPCA_PAC7311 is not set
# CONFIG_USB_GSPCA_SN9C20X is not set
# CONFIG_USB_GSPCA_SONIXB is not set
# CONFIG_USB_GSPCA_SONIXJ is not set
# CONFIG_USB_GSPCA_SPCA500 is not set
# CONFIG_USB_GSPCA_SPCA501 is not set
# CONFIG_USB_GSPCA_SPCA505 is not set
# CONFIG_USB_GSPCA_SPCA506 is not set
# CONFIG_USB_GSPCA_SPCA508 is not set
# CONFIG_USB_GSPCA_SPCA561 is not set
# CONFIG_USB_GSPCA_SQ905 is not set
# CONFIG_USB_GSPCA_SQ905C is not set
# CONFIG_USB_GSPCA_STK014 is not set
# CONFIG_USB_GSPCA_SUNPLUS is not set
# CONFIG_USB_GSPCA_T613 is not set
# CONFIG_USB_GSPCA_TV8532 is not set
# CONFIG_USB_GSPCA_VC032X is not set
# CONFIG_USB_GSPCA_ZC3XX is not set
# CONFIG_VIDEO_PVRUSB2 is not set
# CONFIG_VIDEO_HDPVR is not set
# CONFIG_VIDEO_EM28XX is not set
# CONFIG_VIDEO_CX231XX is not set
# CONFIG_VIDEO_USBVISION is not set
# CONFIG_USB_VICAM is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_KONICAWC is not set
# CONFIG_USB_QUICKCAM_MESSENGER is not set
# CONFIG_USB_ET61X251 is not set
# CONFIG_VIDEO_OVCAMCHIP is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_SE401 is not set
# CONFIG_USB_SN9C102 is not set
# CONFIG_USB_STV680 is not set
# CONFIG_USB_ZC0301 is not set
# CONFIG_USB_PWC is not set
CONFIG_USB_PWC_INPUT_EVDEV=y
# CONFIG_USB_ZR364XX is not set
# CONFIG_USB_STKWEBCAM is not set
# CONFIG_USB_S2255 is not set
CONFIG_RADIO_ADAPTERS=y
# CONFIG_I2C_SI4713 is not set
# CONFIG_RADIO_SI4713 is not set
# CONFIG_USB_DSBR is not set
# CONFIG_RADIO_SI470X is not set
# CONFIG_USB_MR800 is not set
# CONFIG_RADIO_TEA5764 is not set
# CONFIG_DAB is not set
If you mean the Power+Vol UP key combination, this is factory default.
Screen itself is quite OK, watching Sintel or Big Buck Bunny was fun.
weeds2000 said:
OK getting mythTV on the device is quite an impressive task.
As not even the c-library is the default glibc known from your desktop PC and may miss a few things here and there. (learned that when trying to port libfuse and ntfs-3g)
To me it seems like v4l is included, this is the config from the multimedia section:
Code:
#
# Multimedia drivers
#
# CONFIG_MEDIA_ATTACH is not set
CONFIG_MEDIA_TUNER=y
# CONFIG_MEDIA_TUNER_CUSTOMISE is not set
CONFIG_MEDIA_TUNER_SIMPLE=y
CONFIG_MEDIA_TUNER_TDA8290=y
CONFIG_MEDIA_TUNER_TDA9887=y
CONFIG_MEDIA_TUNER_TEA5761=y
CONFIG_MEDIA_TUNER_TEA5767=y
CONFIG_MEDIA_TUNER_MT20XX=y
CONFIG_MEDIA_TUNER_XC2028=y
CONFIG_MEDIA_TUNER_XC5000=y
CONFIG_MEDIA_TUNER_MC44S803=y
CONFIG_VIDEO_V4L2=y
CONFIG_VIDEO_V4L1=y
CONFIG_VIDEO_CAPTURE_DRIVERS=y
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set
CONFIG_VIDEO_HELPER_CHIPS_AUTO=y
# CONFIG_VIDEO_VIVI is not set
# CONFIG_VIDEO_CPIA is not set
# CONFIG_VIDEO_CPIA2 is not set
# CONFIG_VIDEO_SAA5246A is not set
# CONFIG_VIDEO_SAA5249 is not set
# CONFIG_SOC_CAMERA is not set
CONFIG_V4L_USB_DRIVERS=y
CONFIG_USB_VIDEO_CLASS=y
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
CONFIG_USB_GSPCA=m
# CONFIG_USB_M5602 is not set
# CONFIG_USB_STV06XX is not set
# CONFIG_USB_GL860 is not set
# CONFIG_USB_GSPCA_CONEX is not set
# CONFIG_USB_GSPCA_ETOMS is not set
# CONFIG_USB_GSPCA_FINEPIX is not set
# CONFIG_USB_GSPCA_JEILINJ is not set
# CONFIG_USB_GSPCA_MARS is not set
# CONFIG_USB_GSPCA_MR97310A is not set
# CONFIG_USB_GSPCA_OV519 is not set
# CONFIG_USB_GSPCA_OV534 is not set
# CONFIG_USB_GSPCA_PAC207 is not set
# CONFIG_USB_GSPCA_PAC7311 is not set
# CONFIG_USB_GSPCA_SN9C20X is not set
# CONFIG_USB_GSPCA_SONIXB is not set
# CONFIG_USB_GSPCA_SONIXJ is not set
# CONFIG_USB_GSPCA_SPCA500 is not set
# CONFIG_USB_GSPCA_SPCA501 is not set
# CONFIG_USB_GSPCA_SPCA505 is not set
# CONFIG_USB_GSPCA_SPCA506 is not set
# CONFIG_USB_GSPCA_SPCA508 is not set
# CONFIG_USB_GSPCA_SPCA561 is not set
# CONFIG_USB_GSPCA_SQ905 is not set
# CONFIG_USB_GSPCA_SQ905C is not set
# CONFIG_USB_GSPCA_STK014 is not set
# CONFIG_USB_GSPCA_SUNPLUS is not set
# CONFIG_USB_GSPCA_T613 is not set
# CONFIG_USB_GSPCA_TV8532 is not set
# CONFIG_USB_GSPCA_VC032X is not set
# CONFIG_USB_GSPCA_ZC3XX is not set
# CONFIG_VIDEO_PVRUSB2 is not set
# CONFIG_VIDEO_HDPVR is not set
# CONFIG_VIDEO_EM28XX is not set
# CONFIG_VIDEO_CX231XX is not set
# CONFIG_VIDEO_USBVISION is not set
# CONFIG_USB_VICAM is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_KONICAWC is not set
# CONFIG_USB_QUICKCAM_MESSENGER is not set
# CONFIG_USB_ET61X251 is not set
# CONFIG_VIDEO_OVCAMCHIP is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_SE401 is not set
# CONFIG_USB_SN9C102 is not set
# CONFIG_USB_STV680 is not set
# CONFIG_USB_ZC0301 is not set
# CONFIG_USB_PWC is not set
CONFIG_USB_PWC_INPUT_EVDEV=y
# CONFIG_USB_ZR364XX is not set
# CONFIG_USB_STKWEBCAM is not set
# CONFIG_USB_S2255 is not set
CONFIG_RADIO_ADAPTERS=y
# CONFIG_I2C_SI4713 is not set
# CONFIG_RADIO_SI4713 is not set
# CONFIG_USB_DSBR is not set
# CONFIG_RADIO_SI470X is not set
# CONFIG_USB_MR800 is not set
# CONFIG_RADIO_TEA5764 is not set
# CONFIG_DAB is not set
If you mean the Power+Vol UP key combination, this is factory default.
Screen itself is quite OK, watching Sintel or Big Buck Bunny was fun.
Click to expand...
Click to collapse
Whoa, CONFIG_MEDIA_TUNER and CONFIG_MEDIA_TUNER_SIMPLE on from default ?! Also V4L ?!?! what is going on here?! Is Toshiba thinking about making an docking station with a TV Tuner in it and a custom software to watch TV ?!
Edit: I was dreaming awake... I didn't noticed that you were writing about FolioMod kernel... But it would be fun if they did had added these features...
I used mythTV as an example LOL It has too much dependencies... I could try to get all the dependencies for ARM... or compile some for ARM... but it would take lots of time... TVTime looks better for Android, I'm off to see a real Folio 100 on my hands, I have lots of doubts LOL...
It also seems that radio was not forgotten, CONFIG_RADIO_ADAPTERS on... also a possible digital audio broadcast support... hum...
It could be fun if I or someone managed to get a TV Tunner on Folio, TV on camping, TV on the bed, TV everywhere !
The Android kernel seems to have fewer drivers tho... a pity...
Was anyone successful on compiling tegra 250 image for flashing board
Howto - creating a boot.img with new kernel
Note: I wrote a small guide how to repack boot.img when you have your new compiled kernel (based on http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images but modified for folio). I also included modified perl scripts and binary files needed under linux (ubuntu 10.10) for that (no need to compile tools from sdk). So that swapping a new zImage kernel instead of an old one is a question of seconds
See - Howto - unpack,edit,repack boot.img: http://forum.xda-developers.com/showthread.php?t=915808
hi guys i dont know if this is related to kernel but i would like to get the android policy jar. do you know how to do it?
thanks!
This is quite interesting topic you are discussing here.....
Can you pls gather the information abt the kernel compilation as well as image assembly so others can experiment too ?
What are chances to brick the device during tests ?
Being a linux user for some time I would be very happy to have something like
- either a custom kernel for android for playing
- or linux distribution to run on the device (as Archos 5 IT have dual boot with Linux for example)
perhaps we can gather up to produce something like it for our device ????
thanks
is possible try compiling kernel 2.6.35 for folio?? anyone has tried?
I am trying to compile and insert the CFG80211.ko module
I have built an Ubuntu VM and installed the correct codesourcery cross compiler.
I have been able to build several modules which successfully insert. (ntfs, lib80211, all three lib80211_crypt modules, all three wusb modules, uwb, veth etc etc)
however the cfg80211.ko module always fails with invalid argument.
dmesg reports :-
Code:
[140146.246732] cfg80211: disagrees about version of symbol wireless_send_event
[140146.246751] cfg80211: Unknown symbol wireless_send_event (err -22)
cfg80211 depends on rfkill which is, as far as I cant tell, precompiled into the phone kernel.
the relevant section of the config file is as follows:-
Code:
#
# Bluetooth device drivers
#
# CONFIG_BT_HCIBTUSB is not set
# CONFIG_BT_HCIBTSDIO is not set
CONFIG_BT_HCIUART=y
CONFIG_BT_HCIUART_H4=y
# CONFIG_BT_HCIUART_BCSP is not set
# CONFIG_BT_HCIUART_LL is not set
# CONFIG_BT_HCIBCM203X is not set
# CONFIG_BT_HCIBPA10X is not set
# CONFIG_BT_HCIBFUSB is not set
# CONFIG_BT_HCIVHCI is not set
# CONFIG_BT_MRVL is not set
CONFIG_BT_HID=m
# CONFIG_AF_RXRPC is not set
CONFIG_FIB_RULES=y
CONFIG_WIRELESS=y
CONFIG_WIRELESS_EXT=y
CONFIG_WEXT_CORE=y
CONFIG_WEXT_PROC=y
CONFIG_WEXT_SPY=y
CONFIG_WEXT_PRIV=y
CONFIG_WIRELESS_COMPAT=m
CONFIG_CFG80211=m
# CONFIG_NL80211_TESTMODE is not set
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_REG_DEBUG is not set
# CONFIG_CFG80211_DEFAULT_PS is not set
# CONFIG_CFG80211_DEBUGFS is not set
# CONFIG_CFG80211_INTERNAL_REGDB is not set
CONFIG_CFG80211_WEXT=y
# CONFIG_WIRELESS_EXT_SYSFS is not set
CONFIG_LIB80211=m
CONFIG_LIB80211_CRYPT_WEP=m
CONFIG_LIB80211_CRYPT_CCMP=m
CONFIG_LIB80211_CRYPT_TKIP=m
# CONFIG_LIB80211_DEBUG is not set
CONFIG_MAC80211=m
CONFIG_MAC80211_HAS_RC=y
# CONFIG_MAC80211_RC_PID is not set
CONFIG_MAC80211_RC_MINSTREL=y
# CONFIG_MAC80211_RC_DEFAULT_PID is not set
CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT="minstrel"
# CONFIG_MAC80211_MESH is not set
# CONFIG_MAC80211_LEDS is not set
# CONFIG_MAC80211_DEBUGFS is not set
# CONFIG_MAC80211_DEBUG_MENU is not set
# CONFIG_WIMAX is not set
CONFIG_RFKILL=y
CONFIG_RFKILL_PM=y
# CONFIG_RFKILL_INPUT is not set
# CONFIG_NET_9P is not set
# CONFIG_CAIF is not set
#
# Device Drivers
#
Full .config file attached below.
I have tried converting RFKILL to a module, in order to enable CONFIG_RFKILL_INPUT to yes but the compile completely fails when this is set.
I have added WIRELESS_COMPAT details in the Kconfig file but this did not help and I am now lost as to how to troubleshoot this?
Anyone have any idea on what might be missing?
If you're able to compile the modules, you should be able to compile the kernel - do the modules insmod against the compiled kernel?
Entropy512 said:
If you're able to compile the modules, you should be able to compile the kernel - do the modules insmod against the compiled kernel?
Click to expand...
Click to collapse
Yes all the other modules I mentioned all insert fine the ones that I have compiled that dont insert have dependancies that all stem back to the cfg80211.ko that is giving me the messages in the first post.
from the documentation cfg80211 is dependant on RFKILL which is precompiled into the kernel.
Entropy512 said:
If you're able to compile the modules, you should be able to compile the kernel - do the modules insmod against the compiled kernel?
Click to expand...
Click to collapse
Ahhh rereading your post, I see what you mean, I haven't installed the built kernel (though I did do the full build) on the phone, not entirely sure how to package it and I haven't tried to look because I really dont want to install a full kernel on the phone.
In any case I have used the default samsung config to build from fro the correct kernel.
curioct said:
I am trying to compile and insert the CFG80211.ko module
I have built an Ubuntu VM and installed the correct codesourcery cross compiler.
I have been able to build several modules which successfully insert. (ntfs, lib80211, all three lib80211_crypt modules, all three wusb modules, uwb, veth etc etc)
however the cfg80211.ko module always fails with invalid argument.
dmesg reports :-
Code:
[140146.246732] cfg80211: disagrees about version of symbol wireless_send_event
[140146.246751] cfg80211: Unknown symbol wireless_send_event (err -22)
cfg80211 depends on rfkill which is, as far as I cant tell, precompiled into the phone kernel.
the relevant section of the config file is as follows:-
Code:
#
# Bluetooth device drivers
#
# CONFIG_BT_HCIBTUSB is not set
# CONFIG_BT_HCIBTSDIO is not set
CONFIG_BT_HCIUART=y
CONFIG_BT_HCIUART_H4=y
# CONFIG_BT_HCIUART_BCSP is not set
# CONFIG_BT_HCIUART_LL is not set
# CONFIG_BT_HCIBCM203X is not set
# CONFIG_BT_HCIBPA10X is not set
# CONFIG_BT_HCIBFUSB is not set
# CONFIG_BT_HCIVHCI is not set
# CONFIG_BT_MRVL is not set
CONFIG_BT_HID=m
# CONFIG_AF_RXRPC is not set
CONFIG_FIB_RULES=y
CONFIG_WIRELESS=y
CONFIG_WIRELESS_EXT=y
CONFIG_WEXT_CORE=y
CONFIG_WEXT_PROC=y
CONFIG_WEXT_SPY=y
CONFIG_WEXT_PRIV=y
CONFIG_WIRELESS_COMPAT=m
CONFIG_CFG80211=m
# CONFIG_NL80211_TESTMODE is not set
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_REG_DEBUG is not set
# CONFIG_CFG80211_DEFAULT_PS is not set
# CONFIG_CFG80211_DEBUGFS is not set
# CONFIG_CFG80211_INTERNAL_REGDB is not set
CONFIG_CFG80211_WEXT=y
# CONFIG_WIRELESS_EXT_SYSFS is not set
CONFIG_LIB80211=m
CONFIG_LIB80211_CRYPT_WEP=m
CONFIG_LIB80211_CRYPT_CCMP=m
CONFIG_LIB80211_CRYPT_TKIP=m
# CONFIG_LIB80211_DEBUG is not set
CONFIG_MAC80211=m
CONFIG_MAC80211_HAS_RC=y
# CONFIG_MAC80211_RC_PID is not set
CONFIG_MAC80211_RC_MINSTREL=y
# CONFIG_MAC80211_RC_DEFAULT_PID is not set
CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT="minstrel"
# CONFIG_MAC80211_MESH is not set
# CONFIG_MAC80211_LEDS is not set
# CONFIG_MAC80211_DEBUGFS is not set
# CONFIG_MAC80211_DEBUG_MENU is not set
# CONFIG_WIMAX is not set
CONFIG_RFKILL=y
CONFIG_RFKILL_PM=y
# CONFIG_RFKILL_INPUT is not set
# CONFIG_NET_9P is not set
# CONFIG_CAIF is not set
#
# Device Drivers
#
Full .config file attached below.
I have tried converting RFKILL to a module, in order to enable CONFIG_RFKILL_INPUT to yes but the compile completely fails when this is set.
I have added WIRELESS_COMPAT details in the Kconfig file but this did not help and I am now lost as to how to troubleshoot this?
Anyone have any idea on what might be missing?
Click to expand...
Click to collapse
Are you installing the kernel and modules, or just the modules? If you are just installing the modules, are you using an IDENTICAL version of gcc, with nothing changed between N<=>M<=>Y except for your rt2x00 module in the .config?
useful information would be:
Your kernel version string from the phone: uname -a
A diff of the base .config and the new .config: diff -ubw orig.config new.config
A diff of the phone's working .config and your .config.
You can generally get the .config your running kernel was compiled with from /proc/config.gz on the device. You would then need to gunzip that and compare it to your .config with the diff command above.
s0be said:
Are you installing the kernel and modules, or just the modules? If you are just installing the modules, are you using an IDENTICAL version of gcc, with nothing changed between N<=>M<=>Y except for your rt2x00 module in the .config?
useful information would be:
Your kernel version string from the phone: uname -a
A diff of the base .config and the new .config: diff -ubw orig.config new.config
A diff of the phone's working .config and your .config.
You can generally get the .config your running kernel was compiled with from /proc/config.gz on the device. You would then need to gunzip that and compare it to your .config with the diff command above.
Click to expand...
Click to collapse
Unfortunately /proc/config.gz support is not configured in the samsung kernel by default therefore the file is not present. uname gives 2.6.35.7-I9100XXKH3-CL479037
And I have tried the recommended codesourcery cross compiler and one other variant of this and the results are the same.
it's a stock rom with an insecure kernel (basically a repack of the stock kernel) to allow rooting from what I can gather.
I have tried many configuration of build from the default .config and just building the top dependancy module from the default config
In this case the top of the tree is CFG80211
(rt2x00usb depends on rt2x00lib, depends upon mac80211, mac8211 depends upon cfg80211 and cfg80211 depends upon rfkill. There are also some dependencies on kernel crypto libraries which I am unclear about but should be in the kernel build)
I have found it makes no difference at all if I build lots of modules at once or just the very bare CFG80211.ko with as few options as possible. The failures are the same trying to insert cfg80211.ko. as it is whether I use busybox insmod, standard insmod or insmod from within a chroot. (in the searches I read modules can behave differently with busybox)
the only changes I made from the samsung default config is switching some debugging options off as per this thread http://forum.xda-developers.com/showthread.php?t=1123643
other than that it is a stock samsung default config for a 2.6.25.7 kernel build, as distributed in the samsung source code.
I haven't had the nerve to install the fully built kernel because the phone is a key tool for me reflashing a kernel is kind of a last resort
The attached rar file includes the default config (c1_rev02_premium_defconfig) the config used (.config) the output of diff -uwb between the two (differences.txt) and the two modules built ntfs.ko and cfg80211.ko.
file reveal ELF 32-bit LSB relocatable, ARM, version 1 (SYSV), not stripped on both modules. (done chroot)
I use ntfs.ko as a control since it's a small module and in this build it inserts just fine. cfg80211.ko fails with the same message and dmesg info mentioned in the first post.
As I previously mentioned I did try modifying the RFKILL sections to be built as a module but when this is attempt the kernel build fails completely with the error:-
Code:
ERROR: "s3c_gpio_slp_cfgpin" [arch/arm/mach-s5pv310/c1-rfkill.ko] undefined!
ERROR: "s3c_gpio_slp_setpull_updown" [arch/arm/mach-s5pv310/c1-rfkill.ko] undefined!
WARNING: modpost: Found 1 section mismatch(es).
To see full details build your kernel with:
Thanks for looking at this for me
Do you have a link to your kernel tree? I'd suspect that CFG80211_WEXT being enabled makes some changes in the WEXT functions that get compiled in kernel. With CONFIG_WEXT_* being =Y, your enableing CFG80211_WEXT probably made things not agree. Also, I believe the rt2x00 driver is a mac80211 one, so you'll likely need that too.
In summary, you'll very likely have to use your own kernel to get this going. At least loading the ntfs.ko answers that it's not a toolchain/source tree issue.
curioct said:
I use ntfs.ko as a control since it's a small module and in this build it inserts just fine. cfg80211.ko fails with the same message and dmesg info mentioned in the first post.
As I previously mentioned I did try modifying the RFKILL sections to be built as a module but when this is attempt the kernel build fails completely with the error:-
Code:
ERROR: "s3c_gpio_slp_cfgpin" [arch/arm/mach-s5pv310/c1-rfkill.ko] undefined!
ERROR: "s3c_gpio_slp_setpull_updown" [arch/arm/mach-s5pv310/c1-rfkill.ko] undefined!
WARNING: modpost: Found 1 section mismatch(es).
To see full details build your kernel with:
Click to expand...
Click to collapse
This error is due to another missing dependency (and the lack of proper dependency definitions in KCONFIG). You need to do:
egrep "s3c_gpio_slp_" -rsn
to find where those functions are defined, and find out why they're not being compiled. It's quite likely something like enabling rfkill for your arch/tree pulled in that c1-rfkill file (is your board a c1?) which is either not for your actual device, or dependent on something else being enabled. This is wholly based on previous experience with HTC kernel trees, where files from other Boards seemed to tag along.
I have no samsung hardware (although the GSII is on the list of what I'm considering ;-) )
s0be said:
Do you have a link to your kernel tree? I'd suspect that CFG80211_WEXT being enabled makes some changes in the WEXT functions that get compiled in kernel. With CONFIG_WEXT_* being =Y, your enableing CFG80211_WEXT probably made things not agree. Also, I believe the rt2x00 driver is a mac80211 one, so you'll likely need that too.
In summary, you'll very likely have to use your own kernel to get this going. At least loading the ntfs.ko answers that it's not a toolchain/source tree issue.
Click to expand...
Click to collapse
I am aware I'll need other modules but they all come back to dependancy on CFG80211 so I am concentrating my efforts around that.
The link to the kernel tree is
git://opensource.samsung.com/p_497
but I have also used :-
https://github.com/GalaxySII/samsung-kernel-galaxysii
with the exact same results.
The config_wext elements are listed under the bluetooth elements, but I am firstly concerned that disabling these elements with adversely effect the standard wifi comms. which would not be acceptable even if I could package and install a fully kernel build. (which I can probably do enough research, on this site, to work out eventually, although I admit to some trepidation about this).
curioct said:
I am aware I'll need other modules but they all come back to dependancy on CFG80211 so I am concentrating my efforts around that.
The link to the kernel tree is
git://opensource.samsung.com/p_497
but I have also used :-
https://github.com/GalaxySII/samsung-kernel-galaxysii
with the exact same results.
The config_wext elements are listed under the bluetooth elements, but I am firstly concerned that disabling these elements with adversely effect the standard wifi comms. which would not be acceptable even if I could package and install a fully kernel build. (which I can probably do enough research, on this site, to work out eventually, although I admit to some trepidation about this).
Click to expand...
Click to collapse
Ok, per:
https://github.com/GalaxySII/samsun...gt-i9100-gingerbread/net/wireless/wext-core.c
Lines: 434, 548, and 613, 653
Your kernel will have to be replaced to have cfg80211, mac80211, and rt2x00 working. There is no way around this, as that code is compiled into the kernel, and cfg80211 and mac80211 depend on those function doing more than your kernel does. There's no way around it. That's only analyzing the wext-core... there may be other differences.
s0be said:
Ok, per:
https://github.com/GalaxySII/samsun...gt-i9100-gingerbread/net/wireless/wext-core.c
Lines: 434, 548, and 613, 653
Your kernel will have to be replaced to have cfg80211, mac80211, and rt2x00 working. There is no way around this, as that code is compiled into the kernel, and cfg80211 and mac80211 depend on those function doing more than your kernel does. There's no way around it. That's only analyzing the wext-core... there may be other differences.
Click to expand...
Click to collapse
thanks for a definitive answer
I guess I need to go away and learn about kernel packaging and the bootloader stuff cant afford to brick my phone regularly trying this stuff and must keep CWM alive
Thanks for your help
Is the hardware capable? If so, where do we start?
Just found this:
ed.slatt said:
I believe /proc/config shows options used to compile the linux kernel. I appended references to OTG in /proc/config to this post. "# CONFIG_USB_OTG is not set" suggests otg support has not been compiled into the kernel but "CONFIG_USB_OTG_UTILS=y" makes me think there is a chance. Perhaps some insmod command will load the appropriate module. It’s probably worthwhile to determine what these OTG flags really mean. I’ll try to look into that in the next couple of days.
I would prefer to not recompile the kernel because this device is my everyday phone and I would be in trouble without it. Furthermore, I believe not all hardware supports OTG in the first place and I haven't yet seen a declaration that this device does support it.
Does anybody know what USB chipset is used in the htc incredible 4g lte and whether it supports OTG or USB host mode?
#
# Miscellaneous USB options
#
# CONFIG_USB_DEVICEFS is not set
CONFIG_USB_DEVICE_CLASS=y
# CONFIG_USB_DYNAMIC_MINORS is not set
CONFIG_USB_SUSPEND=y
# CONFIG_USB_OTG is not set
# CONFIG_USB_OTG_WHITELIST is not set
# CONFIG_USB_OTG_BLACKLIST_HUB is not set
# CONFIG_USB_MON is not set
# CONFIG_USB_WUSB is not set
# CONFIG_USB_WUSB_CBAF is not set
.
.
.
#
# OTG and related infrastructure
#
CONFIG_USB_OTG_UTILS=y
# CONFIG_USB_OTG_WAKELOCK is not set
# CONFIG_USB_GPIO_VBUS is not set
# CONFIG_USB_ULPI is not set
# CONFIG_USB_MSM_OTG_72K is not set
# CONFIG_NOP_USB_XCEIV is not set
CONFIG_USB_MSM_OTG=y
# CONFIG_USB_MSM_ACA is not set
CONFIG_MMC=y
# CONFIG_MMC_DEBUG is not set
CONFIG_MMC_PERF_PROFILING=y
CONFIG_MMC_UNSAFE_RESUME=y
# CONFIG_MMC_CLKGATE is not set
# CONFIG_MMC_EMBEDDED_SDIO is not set
CONFIG_MMC_PARANOID_SD_INIT=y
Click to expand...
Click to collapse
jtdogblue said:
Is the hardware capable? If so, where do we start?
Just found this:
Click to expand...
Click to collapse
It was unanswered in that thread because no one knew. No need to start a new thread. Also, this is the wrong forum for a question, that's why we have the Q&A forum.
Congrats to you for getting the S-OFF phone on eBay, though, since we're already in the wrong place.
Hi Everyone,
Hope I can find some help here. I have gotten after lots of trial and error to run Moo2 on dosbox turbo.
However there is no sound. I tried playing with the settings to no avail. I hope someone can help or at least point me in the right direction because I have run out of searches and options. I'll post my config file. Thanks in advance. Let me know if anyone needs any more information.
[dosbox]
memsize=8
machine=svga_s3
[render]
frameskip=2
[cpu]
core=dynamic
cputype=auto
cycles=max
cycleup=500
cycledown=500
[sblaster]
sbtype=sb16
mixer=true
oplmode=auto
oplemu=fast
oplrate=22050
[mixer]
blocksize=1024
prebuffer=15
rate=22050
[midi]
mpu401=none
mididevice=none
mt32.thread=on
mt32.verbose=off
[speaker]
pcspeaker=false
pcrate=8000
tandy=off
disney=false
# To enable wizardry speaker fix add the line wizpopfix=6 or wizpopfix=7 respectively, below pcspeaker=true in the config file
#wizpopfix=6
[joystick]
joysticktype=2axis
timed=true
[ipx]
ipx=false
[gus]
gus=false
[dos]
# xms -- Enable XMS support.
# ems -- Enable EMS support.
# umb -- Enable UMB support.
# keyboardlayout -- Language code of the keyboard layout (or none).
xms=true
ems=true
umb=true
keyboardlayout=auto
[pci]
# Experimental Voodoo/Glide emulation:
# auto -- experimental (alpha quality) voodoo/glide emulation. Requires very fast device and will not work with GPU rendering.
# false -- disable experimental voodoo/glide emulation.
voodoo=auto
[autoexec]
@Echo off
REM Before editing this dosbox.conf, please click MANUAL MODE under DosBox Settings preference if you plan to use a custom config.
REM Otherwise, DosBox Turbo will overwrite your config file on startup.
ECHO DosBox Turbo for Android
mount c: /mnt/sdcard
c:
Service codes:
* # 0 * # Basic tests of devices in the device.*(Mandatory when buying!)*
* 7353 # Another menu with tests.*(Mandatory when buying!)*
* # 06 # IMEI.*
* # 0228 # Network information, full battery information.*
* # 0283 # Data connection test (Loopback Test).*
* # 1111 # FTA SW Version.*
* # 1234 # Firmware version (AP, CP, CSC).*
* # 2222 # Information on the revision of iron.*
* # 2663 # Information about the firmware of touch input devices.*
* # 22558463 # Reset talk time.*
* # 34971539 # Information about camera modules and updating their firmware.*
* # 7284 # UART and USB modes of operation (in modem or multimedia mode).*
* # 9090 # Service Mode.*
* # 9900 # Dump of system data (kernel logs, etc.).
* # 0011 # NET Monitor.*
* 0283 # Convenient microphone test, and headset microphone test.*
* # 34971539 # Information about camera modules and updating their firmware.*
* # 2767 * 2878 # SoftReset.*The settings will be reset to the factory settings, but the data will be saved.*
* # 2767 * 3855 # HardReset.*Restoring the system factory settings, clears all system information, installed programs, contacts, SMS.*Data on memory cards and SIM is not deleted.*
* # 87976633 # FactoryReset.*The same HardReset without any questions.*
* # 12580 * 369 # Production date.*
Thanks for the info.
Though code *7353# does not work on my device.
i just got a factory unlocked s10 plus and none of the hidden codes work?im on Pie 9, verizon sim.i have walked into best buy and tried some codes hidden secret menu and it did work on there s10 plus.
SpanKyM3 said:
i just got a factory unlocked s10 plus and none of the hidden codes work?im on Pie 9, verizon sim.i have walked into best buy and tried some codes hidden secret menu and it did work on there s10 plus.
Click to expand...
Click to collapse
cuz vzw blocks hiddenmenu/keystr to an extent.. u need system privs to enable them which will allow more but even then its only capable of whats allowed and ot varies by carrier and is dependent on whats allowed.. theres a keystrings.dat file in each carriers csc directory but its encryoted so u cant see exactly what keystrings are available.