.I have been trying to get my tablet wits a81e uses a omap3 chipset to load a module. it uses Android 2.2 and the uname -r on the unit is 2.6.32 instead of 2.6.32.9 like the other modules droid_22 and milestone leak that are supplied. i am trying to compile the module and when it creates it it appears to be based on the overclock-mod.c file instead of the overclock.c file. Is there somthing special I should be doing?
I am using ubuntu and the google ndk. I compile and I end up with the .ko file which will load. There are no kern messages other than the kernel is tained. If I run strings overclock.ko I only can basically see the .modinfo from the file.
I have worked on this forever....Can you give any suggestions?
TY
Bruce
Hi all,
there's some fantastic stuff on your forum and I would like to thank you all for work being done here!
Now, to my point. I need kernel source (or update.zip or zImage or boot.img or whatever ) that can support systemd so I can run Fedora 17 arm on my Toshiba Folio 100.
I tried using kernel 3.1 form DerArtem (the guy who has done amazing work with folio) but it has no framebuffer console. I tried adding support for this myself (following this guide: kernel.org/doc/Documentation/fb/fbcon.txt) but it didn't work. There's no surprise there as I am newbie when it comes to compiling kernel and changing its options.
I succeeded in starting Fedora 12 arm with older kernel using this guide (lguegan.free.fr/article.php3?id_article=29) which is inspired by you guys. It worked all right, but I didn't want to go deeper with it because F12 arm didn't have LibreOffice (or OpenOffice) in its repos and Fedora 17 did. Also, Fedora 17 has core support for multi-touch - apps do need to implement this feature though, but the funcionality is there.
And if there is someone who can help me, I can point you in a few directions:
Kernel source for 3.1: github.com/DerArtem/android_kernel_toshiba_betelgeuse
Fedora 17 arm rootfs: fr2.rpmfind.net/linux/fedora-secondary/releases/17/Images/
I am not sure which image you should use SFP or HFP as I don't know what kind of floating point Folio uses.
I am making boot.img with this command:
Code:
#mkbootimg --kernel arch/arm/boot/zImage --cmdline "[email protected] [email protected] vmalloc=192M video=tegrafb usbcore.old_scheme_first=1 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 root=/dev/mmcblk1p1 init=/sbin/init usb-storage.delay_use=0 rootdelay=10" -o boot.img --ramdisk boot.img-ramdisk.gz
maybe there is something wrong right there, but I don't know what half of these kernel parameters do
Also, maybe I am using wrong config file: arch/arm/configs/tegra_betelgeuse_android_defconfig, please do correct me.
Now that I think, I just need config file for this 3.1 kernel, so basicaly that's the help I need.
Thanks in advance and again thank you for all the good stuff here
Momcilo
Hmmm interesting project. Mabey some day you can tell us how you got Fedora 12 to work. I saw that DerArtem is working on a kernel over on his github page: https://github.com/DerArtem/, mabey it will work with your build?
Did you also read through the linux post in the general section? (link)
Hi friend!
Well, getting Fedora 12 arm to work was fairly easy. Just flashed with kernel from that page you posted and copied Fedora 12 rootfs to an mmc and it booted with console. X was not even installed in rootfs so before I tried to make it work I realized that there was no office for that version of Fedora arm so I dropped it.
Reason I can't use kernel from that page you posted is: it's too old. Fedora 17 uses systemd which requires newer kernel. That's why I came here, to try and contact DerArtem to see if his new kernel 3 for Folio could be configured to boot up other OSes, because I tried reconfiguring myself but got stuck.
Thanks for your interest in this
Its been a while since i build my own kernel, but it seems to me that you need to have a F17 build system and then build the kernel with the config for the Folio 100 (Fedora arm Kernel building)
I'm currently trying to get Archlinux working on my folio (Still i know).
I don't have problem building a kernel. It builds just fine, and I do get zImage and I can flash my Folio with it and it boots up. Only problem I have at the moment is that I can't seem to get framebuffer console working so I can debug booting Fedora from MMC.
and then build the kernel with the config for the Folio 100
Click to expand...
Click to collapse
Yeah, that's what I am missing
The config for the kernel is in:
arch/arm/configs/tegra_betelgeuse_android_defconfig
You will have to enable the framebuffer console as it is disabled it the kernel.
Hi DerArtem,
thanks for taking time to look at my work.
I think there was a mistake in my earlier efforts that I didn't realize, because now I did it from start and framebuffer works like a charm. I also added support for systemd (devtmpfs, cgroups, etc...) and now my Fedora 17 arm boots to console.
I am so happy right now I can't even try to debug why X doesn't work, but I'll get there.
If I make this work completely I will make a guide and post it here.
Thanks guys!
May I suggest u post your issues here, perhaps we can help you with these ?
thanks
P.S. Fedora is not really my distribution of choice(prefer debian or arch), but nevertheless make it working is a great advance
Thanks sader0!
I will need help with this.
Here are the logs:
dmesg - dm.txt
lsusb - lsusb.txt
/var/log/messages - messages.txt
Xorg -configure - Xorg.0.txt
lspci - doesn't produce anything.
And another thing, I didn't copy anything from kernel tree after compiling. I noticed during kernel build that something compiles as module but I had trouble finding any modules.
Is there anything I should copy to filesystem from kernel tree?
Best regards,
Momcilo.
Hello. I am trying to compile and boot a Cyanogenmod-7 kernel for the HTC Desire HD. My first attempt was from a Debian chroot running on the phone. I managed to compile the kernel, but was unable to boot it. For testing, I unpacked boot.img, and repacked it with the original files and kernel, and was able to boot that... this confirmed the problem was the kernel, and nothing else. I believe I tried the Kali- and Cyanogenmod-msm7x30 sources.
Realizing that compiling on the phone was impractical, I decided to buy a Trim Slice embedded system (an A9 cpu, 1gb memory, 500gb storage). I also realize that Android kernels are cross compiled, but I preferred native architecture because there are some advantages (regression tests). This Trim Slice runs Ubuntu Natty, with GCC Linaro 4.5.2.
I can not cross compile from my workstation because it is OpenBSD, and does not do such things.
Now, more carefully, I downloaded the Cyangenmod 7 kernel sources, with the same git pull version as the shipped kernel. /proc/config.gz and cyanogen_msm7230_defconfig are identical. I made no changes to the config. I used 'make CROSS_COMPILE='. I compiled mkbootimg natively, and did flash_image on the phone, rebooted, and same thing... the HTC screen for infinity.
So then I built GNU Patch-2.7 statically linked (it's a balance between a complex program and a simple program), and copied it to the phone, and './patch --version' works fine. So my compiler is fine... it is compiling for the correct platform.
What could be going wrong with my kernels? Is my GCC version to blame?.. /proc/version says the phone's kernel was built with gcc-4.4.3.
Is there a boot loader that can turn my phone's usb port into a serial port/console so I can see what is going on?
Hi all,
I begin with compilation and development with kernel for mobiles devices and specially with touchpad.
I tried to use my touchpad like a "micro" server (like i could do with raspberry pi), then i installed ubuntu 12.10 with this topic:
http://forum.xda-developers.com/showthread.php?t=1304475
I installed ubuntu 12.10 and use CalcProgrammer1 kernel (uImage.Ubuntu), it works great for what i want to do...
But now i would add cifs support because the kernel doesn't support it..
I tried to recompile Bodden sources but, the touchscreen support and freedreno drivers isn't supported...
Then, i tried a last thing: compile Bodden sources, make modules, cifs.ko
Now, i have cifs.ko but, when i try to load it with CalcProgrammer1 kernel with insmod, il load successfully (i see it with lsmod) but when i try to mount anything with "mount.cifs" or "mount -t cifs" i will crash and reboot directly after i enter the password...
My knowledge isn't very good with that, and i don't know if i can compile cifs.ko with bodden source, use CalcProgrammer1 kernel and load cifs.ko with insmod..
Thank you very much :highfive:
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.