I am offering a 25$ bounty to whoever can compile the adreno drivers for the huawei U8150. The device has a msm7225 which includes the Adreno 200 but no drivers have been written for it. I am including the kernel source and the Adreno driver source as well as the specs.
Phone Huawei U8150 Ideos
cpu msm7225 overclocked to 600 mhz in factory
256 mb of ram
froyo 2.2.1
.32 kernel
Kernel source (Please compile with the overclock frequency unlocked using the documentation that is included in the text file with this source) http://www.mediafire.com/?s2djub4571hjs
Adreno Source from GIT https://www.codeaurora.org/gitweb/qu...oid-msm-2.6.32
Thanks and I will be sharing this work with the rest of the U8150 users when it is completed! Starting with my build. Good luck and thank you!
Nice
Sent from my Desire HD using XDA Premium App
Found this in the android kernel source for my mobile. It's the Galaxy ace which also has an Adreno200.
Maybe it is of use to you.
The kernel module source for the gpu is attached.
That does help but I have no idea how to compile that driver, let alone how to tell the kernel to initialize it. That is why I am asking for someone to compile the kernel with the driver.
I will try to compile them for you, no guarantees It creates a xxxx.ko module so you can insmod xxxx.ko into your kernel.
Sounds great, I appreciate the effort. So in the kernel I just type Insmod in the init file? I have an extracted boot.img of my kernel but thats about the best I can do atm.
I downloaded the source and discovered that the MSM Ardeno drivers are already included in your kernel source. You just have to turn them on in the kernel makemenuconfig.
I compiled the 3d driver for your kernel source(2.6.32, critical only works for this kernel version). Now copy extracted file to your sdcard and try:
* insmod msm_kgsl.ko
in adb or terminal.
Don't know if it works, can't test it. I guess you just have to try and see. And hope you don't get a kernel panic.
I got a no such directory error when I tried to install it.
I copied the ko file to the root of my SD, went to my terminal on my phone and typed SU > cd sdcard and then insmod msm_kgsl.ko
Hmm that's weird, should work. Try and copy to a different path.
Are you sure your kernel version is 2.6.32?
It is indeed a .32 kernel. I am going to try baking the .ko file into my rom, as well as the kernel if I can figure out how.
I just opened the rom in my kitchen and saw that bash support wasn't enabled. I guess that would explain why I couldn't even get my odex script to work. Enabling bash and going to try again.
did you get the adreno to work? i have a similar problem with a XT300 from Motorola, the hardware is there but it's not functional...
If you eventually gonna compile your own kernel, you can build the drivers in the kernel yourself. This are the settings I copied from my own phone's kernel settings.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You find these settings under Device Drivers --> Graphics Support.
PS. Set the buildoptions for the driver to a * instead of M to include them natively in you kernel
PPS. You can instantly set all the correct settings for your device by issuing this command: make hw_msm7x25_defconfig (Huwai devices with MSM 7225 processor)
cant do insmod msm_kgsl.ko from anywhere ..
insmod: init_module 'msm_kgls.ko' failed (no such file or dir...)
tried sdcard, /system/lib/modules, various random plases. same thing.
Can anyone try: busybox insmod msm_kgls.ko
Busybox insmod gives more debugging data. Also try adding -v to be verbose and -p to test if the module can be inserted
I added busybox support to my build and when I typed busybox insmod -f -v msm_kgsl.ko I got can't insert msm_kgsl.ko : unknown symbol in module or invalid parameter. I am really hoping you might be able to compile a kernel for us with it already enabled so I can just throw it in the build. I can test a compiled kernel but I am not having any luck adding it through insmod.
It almost seems as if there is something wrong with that module.
I'm interested in that module for the XT300/Spice.
My kernel is the 2.6.29, 2.1-update1...
How do I compile the module ? What do I need?
Thanks for any help.
Is there possibility that these devices are made from chips with faulty gpu part?
Doubtful that there was any bad parts. Anyways, I am getting conflicting information as to whether it is an adreno 130 or adreno 200 inside of it. I read in the kernel mentions of msm7225 and other parts say 7201a.
Wouldn't it just be enough to get the libGLES and maybe gralloc files from another hardware, like htc buzz, which has the msm7225/adreno200 integration?
I tried it, but quadrant is not showing qcom as the renderer. I had to create the egl.cfg, which was not present. Perhaps it's not loading the egl.cfg:
0 0 android
0 1 qcom
with the files:
egl/libGLES_android.so
egl/libGLES_qcom.so(from htc buzz)
hw/gralloc.msm7k.so(from htc buzz)
hw/gralloc.default.so(from htc buzz)
On neocore the score is 3FPS...
EDIT:
CRAP, flashed the libEGL.so from htc buzz, stuck in bootloop... great, will try to recover =/
Related
I built a cm-kernel from Cyanogen's git repository for you to use. For now it is just a boot.img and wlan.ko, but I am going to make an update.zip for you as soon as I have time
Thanks to: cyanogen, rikupw, bcrook and Radix
This boot.img is only tested on CyanogenMod 4.1.11.1 and might work with older versions. But not on non-CyanogenMod roms!
I've also made some instructions for you to use if you want to build your own kernel: http://ostebaronen.dk/?p=210
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Get the two files here:
BFS-300:
http://ostebaronen.dk/android/cm-kernel-2.6.29-bfs300/boot.img
http://ostebaronen.dk/android/cm-kernel-2.6.29-bfs300/wlan.ko
BFS-302:
http://ostebaronen.dk/android/cm-kernel-2.6.29-bfs302/boot.img
http://ostebaronen.dk/android/cm-kernel-2.6.29-bfs302/wlan.ko
To put it on your phone do as follows.
Code:
adb shell mount -o rw,remount /system
adb push wlan.ko /system/lib/modules
adb push boot.img /sdcard
adb shell
cat /dev/zero > /dev/mtd/mtd2
ignore no space left error.
flash_image boot /sdcard/boot.img
ignore read all-zero errors.
DISCLAIMER: I take no responsibility of bricking your phone, remember always to do nandroid backups! I will try to answer questions you ask here, off-topic questions will be ignored.
Lemme know if you need any help making a kernel update.zip. I would be happy to help out.
Oste
Thanks again! worked 100% well for me
i thing this kernel work for 32b
Very nice information. How about a guide for the pre build?
eViL D: said:
Very nice information. How about a guide for the pre build?
Click to expand...
Click to collapse
What do you mean, for making the boot.img?
I've found out compcache doesn't work, going to look at it.
Or wait, module works fine if I load it myself. So compcache can be enabled with.
Code:
modprobe ramzswap
/system/bin/rzscontrol /dev/block/ramzswap0 --init
swapon /dev/block/ramzswap0
Strange though, because the a2sd script should do this for us...
I know why compcache isn't working for you
Kernel versions and modules are intrinsicly linked by 'uname -r'
Cyanogen's kernel uses 2.6.29-cm41 and you've changed the name with yours to be different - so it's not going to load the modules automagically.
Those modules are slightly hidden from view too - they're in modules.sqf which is a squash4 volume that is mounted on boot.
Good job on documenting the git commands to track cyanogen's builds tho - this is what I need!
cat: write error: No space left on device
????
kchau said:
cat: write error: No space left on device
????
Click to expand...
Click to collapse
i get the same thing
i skipped cat zero
and it hangs at the mytouch screen:
K:\>adb logcat
I//system/bin/sh( 51): /system/bin/sh: Can't open /system/bin/a2sd
I/logwrapper( 51): /system/bin/sh terminated by exit(2)
on dwangs 1.6 rom, never had a2sd to begin with
OK, going to rebuild it for you with the correct uname. Lets see if that solves the modules problems, after that I will look at putting it inside a update.zip. bcrook gave me some guidance so it should be fairly easy
Updated kernel recompiled with the correct uname!
kchau said:
cat: write error: No space left on device
????
Click to expand...
Click to collapse
This is because cat continues filling the device with zeroes until the device is full. So you are ought to get the error No worries. Though this command is not necessary, but good to do since you are sure that nothing is left on it.
OK, for some reason no matter what I do on my phone it will not activate compcache automatically. I tried wiping and installing stock cm4.1.11.1 it didn't work there aswell. So I am sure it is not the kernels fault.
Could someone please confirm compcache is working for them?
will i still have the same a2sd hang on the mytouch screen now?
kchau said:
will i still have the same a2sd hang on the mytouch screen now?
Click to expand...
Click to collapse
What do you mean?
UPDATE:
Ok compcache is working. It seems the a2sd script does not like it when you dont have partitioned your SDcard. If you need help setting it up, ask away!
So what is the difference between the BFS in this kernel & the BFS is cm4.1.11.1? Is this one faster?
Edit: You just stated compcache is working if the sdcard is partitioned... so if we are already partitioned, we shouldn't have any problems, correct? Or do we have to reformat?
Cheesebaron said:
What do you mean?
UPDATE:
Ok compcache is working. It seems the a2sd script does not like it when you dont have partitioned your SDcard. If you need help setting it up, ask away!
Click to expand...
Click to collapse
when im on dwangs rom, it hangs at the mytouch screen, and adb logcat has this message
K:\>adb logcat
I//system/bin/sh( 51): /system/bin/sh: Can't open /system/bin/a2sd
I/logwrapper( 51): /system/bin/sh terminated by exit(2)
i dont think dwang's rom is a rom with a2sd, and i dont have it partitioned in my sd either.
however, when im on 4.0.4, and still dont have a partitioned sdcard, everything works fine
Hi folks,
Im trying to configure the openvpn connection on this phone.
Specification:
- Alcatel One Touch 918D -2CALDE1-S40, Capacitive Screen, CPU: MT6573, ARMv6 Processor 668.46MHz.
- Android 2.3.5, Build Number V23AAE0 (ALPS.GB.JRD2.SP.V1.22), Linux Version 2.6.35.7([email protected])(gcc version 4.4.3(GCC)#1 PREMPT tue Dec 20 12:06:52 CTS 2011
I have rooted successfully this device.
Then I installed this app Tun.ko and tryied to install tun.ko
http: //dariuszmarek.da.funpic.de/Alcatel-918D/Tun.ko-Installer.png
and it semms to be successfull
http: //dariuszmarek.da.funpic.de/Alcatel-918D/Tun.ko-Installer2.png
I checked in terminal and tun.ko is loaded.
http: //dariuszmarek.da.funpic.de/Alcatel-918D/Tun.ko-loaded-terminal.png
After starting the connection via 'openvpn settings' the phone makes rebooting.
After that i copied this tun.ko to /system/lib/modules/tun.ko and cofigured this in advanced settings in 'openvpn settings'.
But the same issue... :-(
the device boots after the start of vpn connection...
can enybody help?
Thank you!
can please share your tun.ko? will try it on my device.
Install the Tun.ko App from Market and install the tun.ko modul for your device. I have shared them.
what happened flipee?any luck with this app?
Same tun.ko issue among MT6573 phones
I have a similar MT6573 phone, and loaded its corresponding module from Tun.ko Installer.
Same reboot issue upon connecting to OpenVPN. I guess we're all in the same boat here. Let me know if you guys have found a solution for your phone. Thanks!
dm.homelinux.com said:
Hi folks,
Im trying to configure the openvpn connection on this phone.
Specification:
- Alcatel One Touch 918D -2CALDE1-S40, Capacitive Screen, CPU: MT6573, ARMv6 Processor 668.46MHz.
- Android 2.3.5, Build Number V23AAE0 (ALPS.GB.JRD2.SP.V1.22), Linux Version 2.6.35.7([email protected])(gcc version 4.4.3(GCC)#1 PREMPT tue Dec 20 12:06:52 CTS 2011
I have rooted successfully this device.
Then I installed this app Tun.ko and tryied to install tun.ko
http: //dariuszmarek.da.funpic.de/Alcatel-918D/Tun.ko-Installer.png
and it semms to be successfull
http: //dariuszmarek.da.funpic.de/Alcatel-918D/Tun.ko-Installer2.png
I checked in terminal and tun.ko is loaded.
http: //dariuszmarek.da.funpic.de/Alcatel-918D/Tun.ko-loaded-terminal.png
After starting the connection via 'openvpn settings' the phone makes rebooting.
After that i copied this tun.ko to /system/lib/modules/tun.ko and cofigured this in advanced settings in 'openvpn settings'.
But the same issue... :-(
the device boots after the start of vpn connection...
can enybody help?
Thank you!
Click to expand...
Click to collapse
Can you tell me how you have rooted this phone?
I've buyed yesterday and i don't know how rooting
I have an OT 918D.
When I load the tun.ko and I use it with Anyconnect, I have the same issue.
My phone reboot.
Have you find a solution ?
we are on the same boat.. i need the droidvpn badly, but it would reboot everytime i would try to connect it on my phone.. maybe if we have a custom kernel for our device..
guys, you can use my ported mod to load tun.ko for your Alcatel...no need custom kernel... in fact, all mt6573 can use it too... :good:
Copy the following file with any root explorer to its respective folder, reboot & start your OpenVPN, DroidVPN, AnyConnect & etc...
scriptz folder -> sdcard
tun.ko -> /system/lib/modules/
xlog.sh -> /system/etc/
if you want, you can head over here to thank banjo0917 as this tun.ko is compile by him... Kudos to banjo...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
* For DroidVPN, just copy tun.ko to SdCard & it'll work...no need for above mod...
yuweng said:
guys, you can use my ported mod to load tun.ko for your Alcatel...no need custom kernel... in fact, all mt6573 can use it too... :good:
Copy the following file with any root explorer to its respective folder, reboot & start your OpenVPN, DroidVPN, AnyConnect & etc...
scriptz folder -> sdcard
tun.ko -> /system/lib/modules/
xlog.sh -> /system/etc/
if you want, you can head over here to thank banjo0917 as this tun.ko is compile by him... Kudos to banjo...
* For DroidVPN, just copy tun.ko to SdCard & it'll work...no need for above mod...
Click to expand...
Click to collapse
I can not believe it. Works like a charm with Alcatel ROM. THANK YOU!
I have managed to successfully cross-compile GNU Nano editor 2.2.6 to run on Android and decided to share it here.
Please note that you need to set up terminfo (if your ROM doesn't have it already), by running:
Code:
export TERMINFO=/system/etc/terminfo
export TERM=linux
Unfortunately, it doesn't fully work through adb shell due to the fact that [enter]-key can't be used (this is a bug of adb shell).
It works flawlessly over ssh, although.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: Fully working version is here.
You will need this patch to fix the enter key:
https://github.com/Evervolv/android...b568f0b417c1fe3fe8597c600bdbcda4837013f.patch
Great! Thanks for the information. :good:
As soon as I have time for that I will apply the patch and release a new binary.
bgcngm said:
Great! Thanks for the information. :good:
As soon as I have time for that I will apply the patch and release a new binary.
Click to expand...
Click to collapse
You are welcome.
I guess you will like this patch too:
http://www.faircode.eu/freexperia/update/terminfo.patch
(I have composed it for CM9, but I guess you known how to modify it, when needed)
Edit: use git apply instead of patch
how do i install this in my phone?
ARM cross-compiling how-to
Assuming a toolchain is already present on the build environment, here are the instructions on how to cross-compile Nano 2.2.6 for ARM devices:
Set the path to C compiler:
Code:
export CC=~/toolchain/bin/arm-none-linux-gnueabi-gcc
After you have unpacked the sources change to the source directory:
Code:
cd nano-2.2.6
Now configure the source:
Code:
./configure --host=arm-none-linux-gnueabi
To compile the sources (statically) type this:
Code:
make LDFLAGS=--static
Here is the fully working version of Nano 2.2.6 for Android (without the [enter]-key bug). Enjoy. :victory:
Great job!
I went ahead and packaged this in a flashable zip for people, it also adds a script to /sbin so you can (temporarily) use nano from the recovery console in AROMA Filemanager during that recovery session.
http://forum.xda-developers.com/showpost.php?p=47402916&postcount=133
Good idea! Thank you.
@bgcngm Any way to fix the output when used through AROMA Filemanager's Terminal Console? Scrolling borks things.
Mention me back when you get the chance.
bgcngm said:
I have managed to successfully cross-compile GNU Nano editor 2.2.6 to run on Android and decided to share it here.
Please note that you need to set up terminfo (if your ROM doesn't have it already), by running:
Code:
export TERMINFO=/system/etc/terminfo
export TERM=linux
Unfortunately, it doesn't fully work through adb shell due to the fact that [enter]-key can't be used (this is a bug of adb shell).
It works flawlessly over ssh, although.
EDIT: Fully working version is here.
Click to expand...
Click to collapse
How do I exit Nano in the android Terminal emulator
Edit: I found out hacker's keyboard's ctrl key helps with this problem
If anyone has this issue, let me help out:
In Windows, running nano and vim through ADB returns weird characters on the terminal, and you need ansicon.
Or better use ConEmu.
That's right. It is documented on the internet, that Ansicon is a requirement for Windows if you use command prompt. As you say, better go with a good terminal emulator.
@bgcngm will u update it to v2.4.2 plz?
Just tried to install through CWM on Cyanogenmod 10.1 Unofficial for Samsung Infuse, and got "installation aborted." Any idea what my problem might be?
The .zip that is available is not to be installed from recovery and that's why you are not able to do it.
osm0sis said:
@bgcngm Any way to fix the output when used through AROMA Filemanager's Terminal Console? Scrolling borks things.
Click to expand...
Click to collapse
bgcngm said:
The .zip that is available is not to be installed from recovery and that's why you are not able to do it.
Click to expand...
Click to collapse
Fixed both of these issues and compiled nano 2.5.0.
http://forum.xda-developers.com/showthread.php?p=64247691#post64247691
If you are a termux user and want to install a nano or vi or any other binaries of termux in Andriod su mode. Here is the link to Termux superuser.
Give it a star if it was helpful !!!
bgcngm said:
ARM cross-compiling how-to
Assuming a toolchain is already present on the build environment, here are the instructions on how to cross-compile Nano 2.2.6 for ARM devices:
Set the path to C compiler:
Code:
export CC=~/toolchain/bin/arm-none-linux-gnueabi-gcc
After you have unpacked the sources change to the source directory:
Code:
cd nano-2.2.6
Now configure the source:
Code:
./configure --host=arm-none-linux-gnueabi
To compile the sources (statically) type this:
Code:
make LDFLAGS=--static
Click to expand...
Click to collapse
How to do this on termux? @bgcngm I got the latest 6.4 tarball.
I've followed the steps from http://forum.xda-developers.com/showthread.php?t=1299962 basically, and crosscompiled glibc and some basic GNU tools, to run natively on the Note 2.
Now, I'm running into some problems, which I need help with from crosscompiling gurus...
Basically, what I did:
- Setup crosstool-ng on the PC.
- Downloaded the Note 2 source from Samsung.
- Got include/drm/exynos_drm.h elsewhere on the web, as it was bombing without it, and for some reason, it's not in Samsung sources.
- Built a crosscompiling toolchain. I set:
target architecture - arm
endianness - little
fpu - neon
instruction set mode - arm
eabi - enabled
vendor string - exynos
alias - arm-linux
os - linux
c library - glibc
threading - nptl
- With it, built glibc for the Note, built no prob. Built also GNU tar to start experimenting.
Now, I transfered glibc and the tar dirs to the Note.
As the author says at http://forum.xda-developers.com/showthread.php?t=1299962:
What I've found so far, the cross compiled executable (like simple Hello world), when dynamically linked, gives "no such file or directory" error when tried to be run at the device (WTF, right ). However, when when I do run it with the cross-compiled ld-linux.so (the linker of C library) it runs perfectly...
EUREKA! Found the solution! It's as simple as symbolically linking the library folder of your GlibC as /lib to root file system. You can edit ramdisk accordingly to do this process automatically.
Click to expand...
Click to collapse
Anyhow for me now, when I try to run the tar executable, I get:
Code:
No such file or directory
This even with the glibc lib dir symlinked to /lib, and/or setting LD_LIBRARY_PATH to the glibc lib dir.
file tar gives me:
ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 3.0.31, stripped
Click to expand...
Click to collapse
so all's looking right.
Why can't I get it to run?
This is proving to be a somewhat great course on crosscompiling for me.
So, messing with it, and making advances - was able to get the compiled executables to run after bindmounting arm-exynos-linux-gnueabi/sysroot/lib dir, which was built by the toolchain to the phone's /lib directory.
Now getting mixed errors and failures caused by ld etc when running GNU tools built against androids libc, so need to mess with terminal on the phone to get just the glibc to loaded on running, but it's progressing...
It seems I'll be able to do this.
Looking forward to that. Highly interested in php lighttpd mc busybox dropbear that kinda ****.
--
Sent from my N7100 with Perseus 25.4 Omega 5.0 and some stuff of Raubkatze
I'm almost there, I just need to crosscompile gcc and then I can build the necessary GNU tools natively.
I'm just figuring out how to crosscompile gcc, as it depends on mpc, gmp, and mpfr, and having no experience with crosstompiling I'm figuring out how to compile depends and link against them, whether they should be native or crosscompiled...
But I should be able to figure it out soon, very close now towards full working GNU tools on the Note 2.
OK, need help, have asked for it at http://stackoverflow.com/questions/...with-crosstool-ng-have-toolchain-which-archit also.
If anyone could assist, here goes:
I've built the crosscompiling toolchain with crosstools-ng.
I've cross compiled glibc, fine.
Have built a couple native arm (arm-exynos-linux-gnueabi) utils, like tar etc. and confirmed they work on the Android phone, when symlinking the built x-tools sysroot's lib directory to /lib on the android machine.
Now I need to build the native gcc, so I can develop on the machine. I'm having some philosophical problems with crosscompiling, as I'm relatively inexperienced in it.
I'd therefore like to ask how to proceed in steps exactly, as I've already spent two days with a trial-by-error approach, and so far no luck.
So: gcc depends on mpc, which depends on mpfr, which depends on gmp.
So, how do I proceed?
Which architecture deps do I build, with which host target and build options?
make a tools dir and build these deps there, so as not to mess with the functioning toolchain?
gmp (no host, build, target?)
mpfr (same?)
mpc (same?)
then gcc, how? --host=arm-exynos-linux-gnueabi --build=i686-build_pc-linux-gnu --target=arm-exynos-linux-gnueabi ?
Is this right, or am I messing up in some of the above steps?
Incidentally, I've followed this guide http://forum.xda-developers.com/showthread.php?t=1299962 to build the crosstool-ng toolchain, and it recommends compiling the native apps just with --host=arm...
I've been doing that, and they do work on the Android system, though it doesn't seem right to me, shouldn't it be --target=arm...?
nyarnon said:
Looking forward to that. Highly interested in php lighttpd mc busybox dropbear that kinda ****.
--
Sent from my N7100 with Perseus 25.4 Omega 5.0 and some stuff of Raubkatze
Click to expand...
Click to collapse
+1 ... I'm interested too, keep it up OP... So far I've only successfully build my own perl/libperl.so and runs great on my note2 from http://code.google.com/p/perldroid
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've proceeded further, have built glibc 2.14 for the N7100, works, compiled gcc and some utils. The problem for now is that there is a bug in glibc 2.14 making statically compiled binaries fail on dynamic calls to libraries... It should be fixed in glibc 2.16...
So am experimenting now, trying to figure out how to add the latest glibc version support to crosstool-ng... If anyone knows, chime in.
Hi all, i'm trying to push rtl8192cu.ko to an ODROID U2 running on CM10.2 (latest nightly) wich is based on kernel 3.0.52 in order to get my new wifi mini-dongle working.
i tried several already compiled modules pushing them in /system/lib/modules/ the module, set the right permissions then run: insmod /system/lib/modules/rtl8192cu.ko
but it fails with:
insmod: init_module '/system/lib/modules/rtl8192cu.ko' failed (Exec format error)
i then look at dmesg:
rtl8192cu: version magic '3.0.8+ SMP preempt mod_unload ARMv7 ' should be '3.0.51-g848f8be SMP preempt mod_unload ARMv7 p2v8 '
since i'm still a noob on this, any tip on how to compile this kernel module against the right kernel/arch would be very appreciated
Thanks in advice
same problem but now with wlan.ko
kuzkuz said:
insmod: init_module '/system/lib/modules/rtl8192cu.ko' failed (Exec format error)
rtl8192cu: version magic '3.0.8+ SMP preempt mod_unload ARMv7 ' should be '3.0.51-g848f8be SMP preempt mod_unload ARMv7 p2v8 '
Click to expand...
Click to collapse
Hi dude, first let me say my english is bad, and I'm NOOB
Well, I'm looking a solution for the same problem. In my searching I learn some thing about those errors but I'm not sure I'm still a noob and my english is bad so bad
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I'm not wrong, at that picture above you can see the chip that we (you and me) need fix.
I wasted hours to tried to fix that chip without success. But then at freaktab.com I found a tread that talks about that chip.
My tablet is:
5linx velocity Ver. 2 (US) but also named at china as Youzen Q8. (yeap I gues the original manufacturer is from china)
Android 4.1.1
kernel 3.0.8+
API LVL 16
CPU: rk3066 but not sure if is called armeabi-v7a or ARMv7
WiFi chip: Realtek 903 or if we follow DMESG is called RTL8188cu
------ So what I'm trying to say with that info ----
1. failed (Exec format error) <<< I guess is when you don't have all the permissions, or is bad copied, or bad compiled. (remember I'm still a noob).
2. version magic -------- ' should be ------ <<< I guess, is when you tried run a module that is not compiled for that version of cpu or kernel.
I have the same problem when I tried copy and run a different module ko that I downloaded or copied from other tablet.
Well, 5linx (US) does not support its customers, but the Chinese manufacturer Szuzone (youzen) does.
So, at freaktab.com I found that maybe the developers made a mistake. Someone there said, try to do this:
rename
8192cu.ko to rkwifi.ko
then run the module using insmod rkwifi.ko
ok, I tried that, but now I get another error with wlan.ko module.
wlan: Unknown symbol rockchip_wifi_init_module (err 0)
-- Some guys on freaktab.com say that process worked for them but not for me.
-- But now I noted that wlan.ko is detected when I use lsmod or dmesg. (remember, I executed rkwifi.ko)
So, what that means?
That process worked for me too? and now wlan.ko is bad?
----- Well anyway, dude try to do that, maybe work for you.
-- Another thing, at realtek website can be found the source code of that chip under (unix,linux) and is for Android 1.6~2.3 and 4.0~4.2 but I have no idea how to compile that driver, I just know I need android sdk or something like that.
-- If someone know how to compile the driver I guess would be better us, right?
I guess the things we need to check before copy and run a module is:
Module was compiled for the same OS version.
same Kernel version
same CPU
and same Wi-Fi chip.
If someone find something to me please feel free to tell me.
WarSxNes said:
Hi dude, first let me say my english is bad, and I'm NOOB
Well, I'm looking a solution for the same problem. In my searching I learn some thing about those errors but I'm not sure I'm still a noob and my english is bad so bad
If I'm not wrong, at that picture above you can see the chip that we (you and me) need fix.
I wasted hours to tried to fix that chip without success. But then at freaktab.com I found a tread that talks about that chip.
My tablet is:
5linx velocity Ver. 2 (US) but also named at china as Youzen Q8. (yeap I gues the original manufacturer is from china)
Android 4.1.1
kernel 3.0.8+
API LVL 16
CPU: rk3066 but not sure if is called armeabi-v7a or ARMv7
WiFi chip: Realtek 903 or if we follow DMESG is called RTL8188cu
------ So what I'm trying to say with that info ----
1. failed (Exec format error) <<< I guess is when you don't have all the permissions, or is bad copied, or bad compiled. (remember I'm still a noob).
2. version magic -------- ' should be ------ <<< I guess, is when you tried run a module that is not compiled for that version of cpu or kernel.
I have the same problem when I tried copy and run a different module ko that I downloaded or copied from other tablet.
Well, 5linx (US) does not support its customers, but the Chinese manufacturer Szuzone (youzen) does.
So, at freaktab.com I found that maybe the developers made a mistake. Someone there said, try to do this:
rename
8192cu.ko to rkwifi.ko
then run the module using insmod rkwifi.ko
ok, I tried that, but now I get another error with wlan.ko module.
wlan: Unknown symbol rockchip_wifi_init_module (err 0)
-- Some guys on freaktab.com say that process worked for them but not for me.
-- But now I noted that wlan.ko is detected when I use lsmod or dmesg. (remember, I executed rkwifi.ko)
So, what that means?
That process worked for me too? and now wlan.ko is bad?
----- Well anyway, dude try to do that, maybe work for you.
-- Another thing, at realtek website can be found the source code of that chip under (unix,linux) and is for Android 1.6~2.3 and 4.0~4.2 but I have no idea how to compile that driver, I just know I need android sdk or something like that.
-- If someone know how to compile the driver I guess would be better us, right?
I guess the things we need to check before copy and run a module is:
Module was compiled for the same OS version.
same Kernel version
same CPU
and same Wi-Fi chip.
If someone find something to me please feel free to tell me.
Click to expand...
Click to collapse
Hi, thanks for the response. I actually know that i did it wrong since i need to compile the drivers for the right kernel version. The problem is that i have no idea on how to compile only the kernel module mentioned instead of all the kernel (wich actually goes beyond my knowledge)