Hello world ! 8)
I mannaged to mount my complete shares on my windows Network to SD-Card ...
I'm using CM6 RC1 and i can simply do a :
modprobe cifs
mount -t cifs //192.168.0.X/share /sdcard/smbshare -o username=XXX,password=YYY
on Computer (PC-here 192.158.0.X) you have to make a share with the name "share" - on SDCARD in your android you have to make a directory with the name smbshare - the dir you are going to mount the PC-Share into)
magicly my sdcard is now a 1,5 Terabyte hdd ... 8)
No more streaming clients are need - just access MP3/DivX/MKV/PDF/etc.
WITHOUT DOWNLOADING TO SDCARD FIRST ...!
(watched a DivX movie directly with Rock-Player 5 minutes ago ... no copy to SDCARD nessasary)
Problem : after a reboot everything is gone ... 8) ... no automatic rermount - no difference between different WLAN-Routers
I am not firm enough on linux to write a script and do the neccasary things to get some logic behind this feature.
It would be wonderful if someone can programm a gui which fires up the nessasary mount when connecting to a wlan - differing between different wlans (networks) with different ressources.
shelling arround is not the best way for android users - something GUI like (e.g. Astro with SMB Modul - but mounting the share instead of copying to sdcard) would give everyone direct access to every file on the network without the nessasary streaming.
Even VPNing to the share should be possible ... giving direct access without streaming servers like ORK/etc.
Good idea ? please add some comments ...
************************************************************
************************************************************
Edit :
A small GUI frontend for managing CIFS shares is available in the following thread:
http://forum.xda-developers.com/showthread.php?t=756158
Let the show beginn !
Very good idea.
I'll take a look into it. Maybe after the weekend. We'll see..
That sounds f**** great! 8)
Thanks for the positive reply!
Sent from my Desire using XDA App
fogbav you can use GScripts for have a link to a script that do this command for you, and have differents scripts for do the same on different WLan.
Code:
#!/bin/bash
MY_USERNAME="your_user_name_here"
MY_PASSWORD="your_password_here"
modprobe cifs
mount -t cifs //192.168.0.X/share /sdcard/smbshare -o username=${MY_USERNAME},password=${MY_PASSWORD}
Wow ... that looks promising ... will test soon.
Thank you very much for the script !
Edit : Works like hell ... thank you ! Now let's see if beidl can do some magic tricks with "usability" and "different WLAN/Shares" logic.
Thank you all ...
What firmwares are you guys using? I'm on LeeDroid 1.6 and seems like cifs is not present for me after doing 'lsmod'. Thanks.
Cyanogen. 6 RC1. So it is Froyo...
Sent from my Desire using XDA App
If someone can provide me a cifs.ko module working with the official HTC Froyo (kernel version 2.6.32.15) then I can start working on a GUI.
I honestly don't want to go back to CM until it's problems are solved and 720p is working.
beidl said:
If someone can provide me a cifs.ko module working with the official HTC Froyo (kernel version 2.6.32.15) then I can start working on a GUI.
I honestly don't want to go back to CM until it's problems are solved and 720p is working.
Click to expand...
Click to collapse
Isn't the kernel source needed to compile a module for that specific kernel?
martino2k6 said:
Isn't the kernel source needed to compile a module for that specific kernel?
Click to expand...
Click to collapse
Well, it depends. One of the today released ROMs has a tun and ext4 module included, still we don't have HTCs new kernel sources. The thing is that I'm sure someone here on xda has access to the private HTC repositories. I remember the old days of the G1 community when someone gave "cyrowski" (old G1 dev) a dump of HTCs private git repository.
But I guess I'll most probably try the newest CM nightly anyways. So then I can also try to write a nice little GUI.
If you can get this working on roms with no cifs in app form it will be epic. I'll be more than happy to be a tester.
Had the above script workin fine in Adams OD 3.02 but had to go back to DeFrost without cifs (I think, didn't work anyway). I miss being able to stream EVERYTHING.
You can dooooo iiiiiiit!
Sent from my HTC Desire using XDA App
Sorry if this is a nooby question. Which ROM should i try this on and what should i enter the commands in?
I am happy to test this as it looks promising.
Thanks.
Bump......
Hi... i think you have to use a non stocked rom compiled with kernel from source code like cm6 opendesire. Stock roms dont have cifs function even new 2.2 official build doesnt have it until source is released by HTC.
Sent from my HTC Desire using XDA App
So do i enter the code in a terminal app?
ukmaddnes1 said:
So do i enter the code in a terminal app?
Click to expand...
Click to collapse
Yes.
(too short blah blah blah)
i get an error with modprobe that file or directory does not exist
su
modeprobe cifs
if this gives an error ... it seems there is no CIFS modul in your rom ... use CM6 ...
again error....it seems that i don't have the module installed........can anyone upload the module and tell me where to put it ???? i mean into what folder it should be
are there any guides on adding cifs into an existing rom/kernel? dont mind doing the work, just have no idea where to start atm.
Hello,
I had a tun.ko working with FROYO, but this tun.ko module doesn't work with Gingerbread 2.3.4 anymore.
Where can I find a new tun.ko module for Gingerbread 2.3.4 (XXJVP) ?
Thanks in advice
Use Darky's rom (10.1). Works great with OpenVPN.
Check load tun kernel module using insmod
Location is /lib/modules/tun.ko
Binary is installed to /system/xbin/openvpn
Hi,
thanks for this info, but currently I'm happy with my flashed/configured phone.
Is it possible, that you or someone else post tun.ko here ?
xdadev_user said:
Hi,
thanks for this info, but currently I'm happy with my flashed/configured phone.
Is it possible, that you or someone else post tun.ko here ?
Click to expand...
Click to collapse
Don't have time right now, but I'll try to compile it for JVP tomorrow.
Sent from my GT-I9100 using Tapatalk
don't know if it works, but this is the one extracted from latest darky's rom kernel.
I'm still on 2.2.1, but you may try it and post some feedback..
xdadev_user said:
Hi,
thanks for this info, but currently I'm happy with my flashed/configured phone.
Is it possible, that you or someone else post tun.ko here ?
Click to expand...
Click to collapse
I had a quick look, and as far as I can tell tun.ko should not be required as it should be built into the kernel in Gingerbread (that is, if you are not using a custom kernel). At least it is enabled in the kernel config that comes with the sources, can't confirm if it's actually enabled in the shipped kernel, but it should be.
@captive
thanks for this tun.ko, but it doens't work.
Code:
insmode tun.ko
invalid module format. Maybe this module is for 2.3.3.
@jps1974
lsmod shows me no tun device
Or can someone explain me how I can build my tun.ko ?
xdadev_user said:
@captive
thanks for this tun.ko, but it doens't work.
Code:
insmode tun.ko
invalid module format. Maybe this module is for 2.3.3.
@jps1974
lsmod shows me no tun device
Or can someone explain me how I can build my tun.ko ?
Click to expand...
Click to collapse
That's because it's not a kernel module but built into the kernel instead. So whatever you're trying to do should, from what I understand, work without having to load any module. Anyway, here's a tun.ko that you can try.
my question was stupid
thanks @jps1974,
but with your tun.ko I got the same error message
invalid module format
Click to expand...
Click to collapse
Any idea, what I'm doing wrong ? With Froyo I had no problem.
A module must only be compiled for correct kernel version 2.6.35.7, or?
My Basisbandversion: I9000XXJVP
Kernel-Version: 2.6.35.7-I9000XXJVO-CL182937
Buildnumber: GINGERBREAD.XXJVP
sorry for my dump question, but i´ve never heard about tun.ko
can someone tell me what the **** that is ?
xdadev_user said:
thanks @jps1974,
but with your tun.ko I got the same error message
Any idea, what I'm doing wrong ? With Froyo I had no problem.
A module must only be compiled for correct kernel version 2.6.35.7, or?
My Basisbandversion: I9000XXJVP
Kernel-Version: 2.6.35.7-I9000XXJVO-CL182937
Buildnumber: GINGERBREAD.XXJVP
Click to expand...
Click to collapse
Oh, so you have a JVP firmware with a JVO kernel - you neglected to mention that
Try the attached file.
The module must be compiled using the exact same source code that was used to build the kernel, and also in this case the version string (2.6.35.7-I9000XXJVO-CL182937 ...) must match exactly the kernel. I believe this is because the kernel is compiled without module versioning support, someone please correct me if I'm wrong.
Did you really need the tun.ko? I think thats compiled in the kernel and you don´t need that any more. I have vpncwidget for my vpn connection to my fritzbox.
Hi,
thanks @jps1974,
but with your tun.ko I got the same error message :-(
But I thínk Woddi123 and you jps1974 (mentioned before) are right.
I still have a /dev/tun device. So maybe I really don't need a tun.ko anymore.
Edit: Yes vpnc works. Sorry for this confusions.
Hi hackers,
i know about the common method described by chulri, to compile custom kernels and it works well.
Anyway for kernel only experiments this way is little too bloated.
EDIT3:
So here's my standalone toolchain for archos (build with modified buildroot system for 32Bit linux OS):
arm-archos GCC4.4.1 for ARM uClinux (uClibc C library 0.9.30 with Archos specific tweaks and bugfixes)
http://dl.dropbox.com/u/8815400/arm-archos.tar.gz
EDIT5:
The toolchain does not work on a 64Bit OS.
I'll post a link for the 64Bit version soon.
Only for reference:
There are a lot of external solutions to be found in the web.
E.g. there are different flavoured toolchains based on gcc 4.4.1 from Mentor Graphics (formerly known as Codesourcery):
Sourcery G++ Lite 2010q1-188 for ARM EABI (Newlib C library 1.17.0)
Sourcery G++ Lite 2010q1-189 for ARM uClinux (uClibc C library 0.9.30)
Sourcery G++ Lite 2010q1-202 for ARM GNU/Linux (GNU C library 2.11)
So if i restrict my activities on kernel compilation all three should do the job.
I made a custom kernel using the above mentioned GNU C toolchain, all compiles fine, but did not test it yet.
This is next... i need to find an easy way to test my tweaked kernels.
So far i would recommend UrukDroid running and use the recovery menu to exchange the kernel & ramdisk.
Any comments are welcome.
Unfortunately our devices use also some binary only kernel modules which are not supported by this method:
hmditx.ko (though marked as GPL, we got no sources)
hdmicec.ko (same here)
UPDATE: Sources had been published by Archos at gitorious.
nwolc.ko (proprietary module from NXP)
BTW, someone should contact the author Andre Lepine to hand out the GPL'ed source code
If i got it right, all custom kernels had been build using the buildroot system because of these.
AFAIK using another toolchain would result in a completely different system map and prevent the modules to load.
Anyway if we exclude HDMI and tweak some start scripts to prevent the modules to get loaded, we'll be fine.
Would be nice to start some discussion up here or leave a comment.
I'd also like to get some tricks form the cracks
EDIT:
Sure there's also Ti's wireless driver package which has to be integrated to compile tiwlan_drv.ko.
Need to do some research to find the correct package.
Any hints are welcome!
EDIT2:
Anyone tried to compile a gen8 kernel using the new gen9 kernel source?
Everything seems to be there...
EDIT4:
See above! The toolchain works very nice.
It had been specially compiled for external use and in the meantime it was tested on many different hosts.
Instructions how to install and use it could be found here:
http://forum.xda-developers.com/showpost.php?p=19134490&postcount=8
Thanks a lot for your attention!
Regards,
scholbert
One question: What's so much better about that toolchain to throw away the Archos-compatible toolchain and deal with the hassle of excluding features to build compatible binaries? I guess I didn't get the point
chulri said:
One question: What's so much better about that toolchain to throw away the Archos-compatible toolchain and deal with the hassle of excluding features to build compatible binaries? I guess I didn't get the point
Click to expand...
Click to collapse
Like i tried to point out:
Anyway for kernel only experiments this way is little too bloated.
Click to expand...
Click to collapse
A neat little cross toolchain environment would be enough for kernel experiments.
I'm working on different platforms e.g. old Debian 4.0 workstation, Netbook with UNR 11 but limited space, other linux machines i don't like to run entire process.
You need a lot of disk space and time (at least first time to build the whole environment).
The other thing is that everything is built into the buildroot structure, you could barely locate the toolchain itself...
Sure your right, if you say everthing works out of the box, but i don't like all these automated procedures, to build my own kernel.
In fact that's just it and i wonder if there's another way.
Just kernel source + cross-toolchain...
Apart from that, the toolchain Sourcery G++ Lite 2010q1-189 for ARM uClinux (uClibc C library 0.9.30) is very close to the Archos one.
BTW, anyone tried to tweak the Archos build script to built the toolchain for external use?
Cheers,
scholbert
scholbert said:
So if i restrict my activities on kernel compilation all three should do the job.
I made a custom kernel using the above mentioned GNU C toolchain, all compiles fine, but did not test it yet.
Click to expand...
Click to collapse
Hi Scholbert!
I've been doing the same for my kernels, it compiles and runs fine, wifi loads without any particular tweak with the original Archos compiled module, but I didn't check hdmi as I don't have cable for it. I'm using a cm7 toolchain to build it (arm-eabi-4.4.3) though.
scholbert said:
This is next... i need to find an easy way to test my tweaked kernels.
So far i would recommend UrukDroid running and use the recovery menu to exchange the kernel & ramdisk.
Click to expand...
Click to collapse
My setup is a bit different since I patched bootloader: I have my "stable" build on normal boot (/rawfs/init) and my dev build on sde (/rawfs/custom), and I flash my kernel directly from my stable build without going through recovery.
I just do adb push kernel and initrd, then directly on device a "kd_flasher -k kernel -i initrd", and I reboot from normal to sde with a "reboot_into sde". It's really quick this way, I just have a script on my linux box to do all this.
I believe you can do the same without patched bootloader with a temproot on secure archos build.
scholbert said:
EDIT2:
Anyone tried to compile a gen8 kernel using the new gen9 kernel source?
Everything seems to be there...
Click to expand...
Click to collapse
Yes, I'm playing with it. I don't know what device you have, but mine (A70S) was not finished in Archos sources: board-archos-a70s is almost empty, panel wasn't finished... I add stuff slowly (still learning Omap, I know Qualcomm better), my kernel boots, I currently have framebuffer, internal mmc and usb working.
Hi letama!
letama said:
I've been doing the same for my kernels, it compiles and runs fine, wifi loads without any particular tweak with the original Archos compiled module, but I didn't check hdmi as I don't have cable for it. I'm using a cm7 toolchain to build it (arm-eabi-4.4.3) though.
Click to expand...
Click to collapse
Cool that's nice information.
Interesting that the tiwlan_drv.ko loads without problems.
Just to start an experiment, i started to shrink down the buildroot setup from Archos and built the gcc 4.4.1 toolchain only.
But it's not finished yet...
letama said:
My setup is a bit different since I patched bootloader: I have my "stable" build on normal boot (/rawfs/init) and my dev build on sde (/rawfs/custom), and I flash my kernel directly from my stable build without going through recovery.
Click to expand...
Click to collapse
O.k. i see, sounds like a clean environment this way.
In fact there's no need for this sqashfs thing anymore...
I already got the SDE's avboot version installed. This version is little bigger in size and obviously got some add-on's.
The same byte signature could be found here, so i guess the hack would match this avboot version as well.
Maybe i give it a try.
letama said:
I just do adb push kernel and initrd, then directly on device a "kd_flasher -k kernel -i initrd", and I reboot from normal to sde with a "reboot_into sde". It's really quick this way, I just have a script on my linux box to do all this.
Click to expand...
Click to collapse
Cool, sounds like a nice development platform this way.
letama said:
I believe you can do the same without patched bootloader with a temproot on secure archos build.
Click to expand...
Click to collapse
Mmmh i thought about using it from UrukDroid...
Anyway, the way you do it sounds more elegant.
letama said:
Yes, I'm playing with it. I don't know what device you have, but mine (A70S) was not finished in Archos sources: board-archos-a70s is almost empty, panel wasn't finished... I add stuff slowly (still learning Omap, I know Qualcomm better), my kernel boots, I currently have framebuffer, internal mmc and usb working.
Click to expand...
Click to collapse
I got an A101... looks little better here, but i did not compile the kernel yet.
Anyway, would be nice to have a complete kernel (incl. wireless and HDMI base code) in the end which compiles fine with latest gcc and runs out of the box
Thanks a lot for your extensive reply!!!
Regards,
scholbert
scholbert said:
I already good the SDE's avboot version installed. This version is little bigger in size and obviously got some add-on's.
The same byte signature could be found here, so i guess the hack would match this avboot version as well.
Maybe i give it a try.
Click to expand...
Click to collapse
Yes, it's the same signature, I verified it with IDA before installing sde, only location differs. You should be fine as long as you don't have multiple matches. If you want my code to patch it, let me know... You'd have to adapt the offsets but it would be probably safer than doing it manually.
Regarding kernel development, I forgot one big advantage to have patched bootloaders: ram_console! I built my "stable" and "dev" kernels with it, so I just have to make my dev kernel to crash to reboot and get the full dmesg with "cat /proc/last_kmsg" even if framebuffer or usb don't work .
scholbert said:
I got an A101... looks little better here, but i did not compile the kernel yet.
Anyway, would be nice to have a complete kernel (incl. wireless and HDMI base code) in the end which compiles fine with latest gcc and runs out of the box
Click to expand...
Click to collapse
Yes, gen9 sources look better for A101, I took them as base for my A70 and it's almost ok. I took away hdmi as it seems a bit too hackish, I'll see later . I also had some issue with gp timers that wouldn't use 32K clock, I'd be curious to see a dmesg on a gen9 tablet.
Right now I'm fighting with usb that kills video driver looonng way to go before having a fully functional kernel.
letama said:
Yes, it's the same signature, I verified it with IDA before installing sde, only location differs. You should be fine as long as you don't have multiple matches. If you want my code to patch it, let me know... You'd have to adapt the offsets but it would be probably safer than doing it manually.
Click to expand...
Click to collapse
Thanks for offering your tool.
Guess it's the same you once posted in that thread about changing bootlogo.
I had a look at the soruces once.
Anyway i already prepared a patched bootblock. Did not re-write it yet
Time is lacking...
letama said:
Regarding kernel development, I forgot one big advantage to have patched bootloaders: ram_console! I built my "stable" and "dev" kernels with it, so I just have to make my dev kernel to crash to reboot and get the full dmesg with "cat /proc/last_kmsg" even if framebuffer or usb don't work .
Click to expand...
Click to collapse
Yupp that's nice... have you seen my UART hack?
letama said:
Yes, gen9 sources look better for A101, I took them as base for my A70 and it's almost ok. I took away hdmi as it seems a bit too hackish, I'll see later . I also had some issue with gp timers that wouldn't use 32K clock, I'd be curious to see a dmesg on a gen9 tablet.
Right now I'm fighting with usb that kills video driver looonng way to go before having a fully functional kernel.
Click to expand...
Click to collapse
Guess i will try to compile this kernel soon.
No time for that right now.
Made some efforts to built special toolchain.
See the upcoming post...
Big thanks for participating!!!
Regards,
scholbert
Ready to use Archos specific toolchain
Hi again,
three simple steps to build UrukDroid custom kernel/modules:
1. Grab my customized toolchain and install it (see first post).
The toolchain is configured to work on mostly any 32Bit linux host (min. libc 2.3.6, should work down to Debian 4.0, Ubuntu 8.04 and similar).
The toolchain must be extracted and placed at /opt on your host machine (x86).
To run it as a user you might change the properties for /opt directory to match the user's rights.
You also could extract the archive as root and run:
chown -R 1000:1000 /opt/arm-archos
To make it more comfortable:
Modify user's .bashrc file to include the path to the toolchain:
export PATH=$PATH:/opt/arm-archos/usr/bin
2. Grab UrukDroid kernel sources and compile.
UrukDroid kernel sources could be found here:
http://sauron.pourix.com/UrukDroid/UrukDroid-1.5/UrukDroid-1.5.1-kernelsrc.tar.bz2
You might extract the sources anywhere you like.
After this has been done, step into the kernel source root directory.
Modify Makefile to use the Archos toolchain (line 199):
Code:
...
# Alternatively CROSS_COMPILE can be set in the environment.
# Default value for CROSS_COMPILE is not to prefix executables
# Note: Some architectures assign CROSS_COMPILE in their arch/*/Makefile
export KBUILD_BUILDHOST := $(SUBARCH)
ARCH ?= $(SUBARCH)
CROSS_COMPILE ?= arm-linux-uclibcgnueabi-
...
cp linux.config .config
make oldconfig
make zImage
make modules
make modules_install INSTALL_MOD_PATH=/my_kernel/modules/
3. Transfer the binaries to your Archos device.
Right now there's no need to exchange the kernel, because we use $auron's base setup for the kernel.
Place your custom modules at /lib/modules
TBC
scholbert
scholbert said:
Thanks for offering your tool.
Guess it's the same you once posted in that thread about changing bootlogo.
I had a look at the soruces once.
Anyway i already prepared a patched bootblock. Did not re-write it yet
Time is lacking...
Click to expand...
Click to collapse
Yes, it's roughly the same code. You did patch both location ?
scholbert said:
Yupp that's nice... have you seen my UART hack?
Click to expand...
Click to collapse
Yes, saw it, it would be very nice to have console on serial, but I don't want to open my A70 yet as it's still has warranty running. I may try that if I can find parts and if I get a gen9 as "main".
scholbert said:
Guess i will try to compile this kernel soon.
No time for that right now.
Click to expand...
Click to collapse
Great! Let me know if you have something, I'd be very interested in a dmesg.
I somehow "fixed" my video driver problem (well, not really fixed, adding traces made it go away ), now I'm trying to get SurfaceFlinger works. Sgx driver doesn't seem to play nice with .29 userspace binaries, I'm not sure I'd be able to go much further without new binaries.
scholbert said:
Made some efforts to built special toolchain.
See the upcoming post...
Click to expand...
Click to collapse
Nice! I'll try to take a look at it when I find some time.
Hey letama,
sorry for the delay...
letama said:
Yes, it's roughly the same code. You did patch both location ?
Click to expand...
Click to collapse
Yepp, both locations are patched.
As we already pointed out, there the rawfs header contains some checksums and avboot is the first file in there.
What do you think, if i manually change some bytes in avboot and leave the checksum untouched, will there be any problems?
letama said:
Yes, saw it, it would be very nice to have console on serial, but I don't want to open my A70 yet as it's still has warranty running. I may try that if I can find parts and if I get a gen9 as "main".
Click to expand...
Click to collapse
O.k. if there's warranty on your device, i totally agree.
letama said:
Great! Let me know if you have something, I'd be very interested in a dmesg.
Click to expand...
Click to collapse
Need more time
letama said:
I somehow "fixed" my video driver problem (well, not really fixed, adding traces made it go away ), now I'm trying to get SurfaceFlinger works. Sgx driver doesn't seem to play nice with .29 userspace binaries, I'm not sure I'd be able to go much further without new binaries.
Click to expand...
Click to collapse
Yeah guess there are some changes in the drivers API.
letama said:
Nice! I'll try to take a look at it when I find some time.
Click to expand...
Click to collapse
So far i tested it, the toolchain works out very nice.
Concerning kernel compilation:
It seems the binaries are quite well optimized in size. No problems so far.
I found out that in stock ROM they used some strip command to make the modules even smaller.
Anyway won't speed things up significantly i guess...
Concerning userland apps:
Though my genereated uClibc is little bigger in size, i noticed no problems so far. A binary comparison between the libaries (stock vs mine), shows little differences though.
Anyway, would be nice if people use it and report...
Have a nice day!
scholbert
Hi Scholbert!
scholbert said:
sorry for the delay...
Click to expand...
Click to collapse
No problem, I'm also busy as hell...
scholbert said:
Yepp, both locations are patched.
As we already pointed out, there the rawfs header contains some checksums and avboot is the first file in there.
What do you think, if i manually change some bytes in avboot and leave the checksum untouched, will there be any problems?
Click to expand...
Click to collapse
Well, I didn't touch checksums either, and it seems they're not checked anywhere else, so you should be good. As long as you patched both location before reboot, you should be ok.
scholbert said:
Yeah guess there are some changes in the drivers API.
Click to expand...
Click to collapse
I made some progress there, I took LG P970 3D binaries with driver source code from their cm7 kernel (they also have a 2.6.35) and I was able to boot up to launcher. I had to fiddle a bit with audio runtime as phone audio won't work, but low level audio driver is working too. Next step is touchscreen... And probably doing a proper cm7 build, I'm running a frankenstein mix of cm7 for nook tablet
scholbert said:
So far i tested it, the toolchain works out very nice.
Click to expand...
Click to collapse
I tried it briefly yesterday as I borked my kernel config at some point and it was crashing my usual toolchain, it doesn't run on my comp: "error while loading shared libraries: libmpfr.so.1: wrong ELF class: ELFCLASS64". Ubuntu 11.10 64 bits...
Best,
LeTama
letama said:
Well, I didn't touch checksums either, and it seems they're not checked anywhere else, so you should be good. As long as you patched both location before reboot, you should be ok.
Click to expand...
Click to collapse
Yeah guessed so... the russian guy who first tried this hack also never mentioned anything like this. So it'll be safe then.
letama said:
I made some progress there, I took LG P970 3D binaries with driver source code from their cm7 kernel (they also have a 2.6.35) and I was able to boot up to launcher. I had to fiddle a bit with audio runtime as phone audio won't work, but low level audio driver is working too. Next step is touchscreen... And probably doing a proper cm7 build, I'm running a frankenstein mix of cm7 for nook tablet
Click to expand...
Click to collapse
Wow sounds pretty like a "frankengenius" software design.
Good work!
Have you seen that Archos released part of the hdmi code as external driver code. So the kernel is even more open now (speaking of 2.6.29).
Sometimes their cooperation is very nice.
About two weeks ago i contact the author at NXP, then last week i wrote to Archos and on thursday they released it. Not bad...
Anyway they ought to release the source, even without mentioning it.
It's just GPL code.
letama said:
I tried it briefly yesterday as I borked my kernel config at some point and it was crashing my usual toolchain, it doesn't run on my comp: "error while loading shared libraries: libmpfr.so.1: wrong ELF class: ELFCLASS64". Ubuntu 11.10 64 bits...
Click to expand...
Click to collapse
Sure the toolchain is compiled for 32Bit systems, forgot to mention this.
So it will never work on a 64Bit system.... sorry
Cheers,
scholbert
scholbert said:
Have you seen that Archos released part of the hdmi code as external driver code. So the kernel is even more open now (speaking of 2.6.29).
Click to expand...
Click to collapse
Didn't see it, very nice! HDMI is a low on my priority list, but it's good to have source code, it will help porting it. Even though my efforts on this kernel will slow a bit as I purchased today a gen9 and ICS source code is out .
At first glance, boot process and layout looks very similar to our gen8, same rawfs, a custom file that would indicate that we should get SDE, so far so good. Need to spend some quality time with hex editor and IDA now .
Damn work, I need 72 hours days!
scholbert said:
Sure the toolchain is compiled for 32Bit systems, forgot to mention this.
So it will never work on a 64Bit system.... sorry
Click to expand...
Click to collapse
No problem, just wanted to give a bit of feedback.
@letama:
Wouldn't it be alot more productive for you and us if you would somehow join your affort with the guys from openaos?
cm7 and then cm9 would be here faster the more experienced devs are helping.
fzelle said:
@letama:
Wouldn't it be alot more productive for you and us if you would somehow join your affort with the guys from openaos?
cm7 and then cm9 would be here faster the more experienced devs are helping.
Click to expand...
Click to collapse
Hi fzelle,
Well, I'm only learning slowly, they're far more experienced than me on Archos. My main goal is to understand omap platform, that's why I'm toying with the 2.6.35 kernel. Cm7 is only a convenient for way me to make sure the kernel behaves well. I don't seek a perfect cm7/archos experience for all devices as they do, but if at some point I learned enough, I may try to help if I can.
LeTama
CM7 for Archos atm is based on the 2.6.29 kernel delivered from Archos, so your kernel is far more advanced.
And if you got 2.6.35 to work properly, the guys over at openaos would probably be happy to use that.
fzelle said:
CM7 for Archos atm is based on the 2.6.29 kernel delivered from Archos, so your kernel is far more advanced.
And if you got 2.6.35 to work properly, the guys over at openaos would probably be happy to use that.
Click to expand...
Click to collapse
Yes, 2.6.35 should match better gingerbread code. If I can go somewhere, I'll share it. Currently, I'm far from that, still having troubles with usb and a big piece will be power management. We'll see, but I'm a bit out of free time.
Hey letama,
i guess fzelle is right.
AFAIK, the openaos developers concentrate on the Android part for gen8. As stated they still use 2.6.29 and this no problem so far.
But a kernel project might run in parallel.
Would be nice to get the new kernel working at least for A70 and A101.
I started a build for A101 (...and still compiling), maybe we could share our .config file
EDIT: Aaaaaargh, still fighting with the kernel config/compile errors.
Wifi/BT framework issue.... RFKILL_STATE_UNBLOCKED etc. seems not to be implemented anymore...
letama said:
I made some progress there, I took LG P970 3D binaries with driver source code from their cm7 kernel (they also have a 2.6.35) and I was able to boot up to launcher. I had to fiddle a bit with audio runtime as phone audio won't work, but low level audio driver is working too. Next step is touchscreen... And probably doing a proper cm7 build, I'm running a frankenstein mix of cm7 for nook tablet
Click to expand...
Click to collapse
The SGX part is an open issue i guess, but there's some support form Ti as well. E.g.: https://gforge.ti.com/gf/project/openmax/frs/
Remember the Beagleboard-XM is very similar to what we got on our devices.
Also Zoom3 platform, so maybe their repository is a good starting point for these addon's as well.
In fact using the OMAP might be a benefit in general, because there are so many opensource projects covering this architecture
Happy hacking!
scholbert
Hi Scholbert,
scholbert said:
i guess fzelle is right.
AFAIK, the openaos developers concentrate on the Android part for gen8. As stated they still use 2.6.29 and this no problem so far.
But a kernel project might run in parallel.
Would be nice to get the new kernel working at least for A70 and A101.
Click to expand...
Click to collapse
Agreed! It would be nice if we could develop both A70 and A101 in parallel, sharing will speed things up.
scholbert said:
I started a build for A101 (...and still compiling), maybe we could share our .config file
Click to expand...
Click to collapse
I attached my current one, I added one config option that you don't have, CONFIG_MUSB_ERRATA_445, you can remove the line. I'm not sure I have the config right, but it boots and has quite a lot of stuff working. You need to re-add A10IT board though.
scholbert said:
The SGX part is an open issue i guess, but there's some support form Ti as well. E.g.: https://gforge.ti.com/gf/project/openmax/frs/
Click to expand...
Click to collapse
Well, for me it's no longer an issue, I think what I did is the best we can do until we can get a hand on Archos binaries for 3630. The issue is that you have to have proprietary binaries, they must match driver version, and the binaries I have from P920 works fine even though maybe not as recent as Archos ones. There is no open source implementation afaik. OpenMax is only for video codec, not 3D.
scholbert said:
Happy hacking!
Click to expand...
Click to collapse
Thanks, you too! You have a mission now! Let's get this kernel running on A101
Hi letama!
letama said:
Agreed! It would be nice if we could develop both A70 and A101 in parallel, sharing will speed things up.
Click to expand...
Click to collapse
To be honest i meant developing openaos and kernel in parallel. Who ever does it
Anyway, as i wrote it... i started to play around with the new kernel.
It's hard for me these days to find some time for hacking and i'm not a genius in modifying kernel drivers and stuff.
So in fact i don't know how far i will get things rollin'
letama said:
I attached my current one, I added one config option that you don't have, CONFIG_MUSB_ERRATA_445, you can remove the line. I'm not sure I have the config right, but it boots and has quite a lot of stuff working. You need to re-add A10IT board though.
Click to expand...
Click to collapse
Thanks a lot. I will compare your config with my setup.
Already found some missing parts in the board file...
letama said:
Well, for me it's no longer an issue, I think what I did is the best we can do until we can get a hand on Archos binaries for 3630. The issue is that you have to have proprietary binaries, they must match driver version, and the binaries I have from P920 works fine even though maybe not as recent as Archos ones. There is no open source implementation afaik. OpenMax is only for video codec, not 3D.
Click to expand...
Click to collapse
Ah i see, so i'll take a look at the binaries.
I guess you meant P970, as stated earlier.
letama said:
Thanks, you too! You have a mission now! Let's get this kernel running on A101
Click to expand...
Click to collapse
Haha, as stated above... nice mission anyway
BTW, did you see there are some nice projects at gitorious.
A 2.6.37 kernel port for A43 and A101 had also been started already.
I had a short look at some parts... don't know about the exact state of the code.
Let's stay in touch!
Best regards,
scholbert
Edit: these are useful for stock 3.1 and should not be used with my kernel. See my kernel post for current capabilities etc.
Please use this thread to post kernel modules for the Samsung Galaxy 8.9
The kernel modules I post are compiled from the model 7310 WiFi-only kernel source released by Samsung for kernel 2.6.36.3 and Android 3.1. I do not know if they will work on any other model besides the 7310, but you are free to try.
You must have root access and mount "system" as read/write.
Create a folder called "modules" inside of /system/lib and copy the kernel module (.ko) into "modules"
cifs.ko - to mount shares from Windows, Linux and Mac
-View attachment 7310_cifs.ko.zip
-Unzip cifs.ko and verify with SHA1 65c5cc08ee5a4878fc99060885ecaefd6961a9f
-CifsManager from the Android Market works well. Goto "Settings..." and check both "Load cifs module" and "Load va insmod". The default path will be as shown (/system/lib/modules/cifs.ko)
View attachment other_7310_modules.zip
nls_utf8.ko 3b066984e0dca109df4fe234ea7b91f396448e58
option.ko f46babd6a030bc536869915961971bd110efb3b8
tun.ko 826b5b40749bfbd8978eee4e65838380bd614364
usb_wwan.ko cd76f800e39ce0883feb6a093242757e0a15d829
View attachment ntfs.ko.zip
ntfs.ko ee47d0f110aca30db79accbbc0058292491372a4
Please give "thanks" if this was helpful. If you are looking for a common module, please make a request and I will see what I can do. I have a regular job and a family, so I can't promise how long it will take or that it will work since I may not have the hardware to test it.
Thanks motley. A tip for other noobs like me: don't download through Tapatalk.
Sent from my GT-P7310 using Tapatalk
this is great, thanks for working on the tab 8.9. i think many of us 8.9 owners are a little sad we have so little development going on.
thanks , it works both on stock rom and overcome's rom, well done !!
Hi _motley,
do you know how to mount modules for east asian character folder ?
it seems involved with nls_utf8 module , i'm using cifs mgr...
batch load both cifs.ko and nls_utf8.ko from CIFS mgr , not work,
but western character works normally.
Alternatively , I use script to insmod , then works fine,
anyway , it works , thank you a lot.
Hi
Thanks a lot !
Any chance to get the NTFS Module as well ?
Thanks for testing, glad to hear cifs is working.
kevinchg, not sure on your mounting issue when also loading nls_utf8.ko, I don't currently have a way to test it, but I would make sure that you have your path's and options setup correctly in cifsmanager. Don't quote me, but I think you need to separate the two module paths by a semi-colon and I believe you also need to specify the option "iocharset=utf8" (or something like this) within your share configuration.
fishton, the NTFS module has been added. Let me know if it works for you. Can't believe I left this one out...would like to use it myself.
Thanks ! Will test it tonight and let you know if it works
I'm curious why you guys need the modules. As far as I can tell, they were built into the kernel on my 8.9 tab. I had no problem mounting cifs/ntfs shares and didn't need anything to do so.
phonic said:
I'm curious why you guys need the modules. As far as I can tell, they were built into the kernel on my 8.9 tab. I had no problem mounting cifs/ntfs shares and didn't need anything to do so.
Click to expand...
Click to collapse
Which model do you have? Perhaps you are mounting network drives with ES File Explorer or something like that that has SMB built-in? Neither the config from /proc/config.gz or the defconfig from the kernel source I downloaded from Samsung have any of these options built into the kernel. I definitely can't mount using cifsmanager without loading the cifs.ko module.
For NTFS, we are talking about mounting NTFS hard drives via USB. Haven't tried that yet...perhaps the other gentleman will report back if he tries.
Hi
I tried your NTFS Module yesterday and have been able to load the module. But unfortunately, I haven t been able to find the proper command for mounting my disk.
Could you advice me ?
Thanks !
fishton said:
Hi
I tried your NTFS Module yesterday and have been able to load the module. But unfortunately, I haven t been able to find the proper command for mounting my disk.
Could you advice me ?
Thanks !
Click to expand...
Click to collapse
Give this app a try and see if it works. I'll try to play around with this myself when I find some time.
https://market.android.com/details?id=au.dach.drivemount
Also, see this:
http://forum.xda-developers.com/showthread.php?t=1131924
Already tried both, no luck with it
Hi
Many thanks for your v2 kernel all smooth for me with OVC 2.1
I'm looking at for a working cifs.ko. The one given here never worked for me (exec format error) with previous kernel and the v2.
Any chance to get one to test from your v2 kernel build?
Thanks again.
Sent from my GT-P7310 using xda premium
questionmark said:
Hi
Many thanks for your v2 kernel all smooth for me with OVC 2.1
I'm looking at for a working cifs.ko. The one given here never worked for me (exec format error) with previous kernel and the v2.
Any chance to get one to test from your v2 kernel build?
Thanks again.
Sent from my GT-P7310 using xda premium
Click to expand...
Click to collapse
With the latest versions of my kernel, you don't need any modules...it's built right into the kernel. Only the stock kernel and the first alpha release of my kernel needed modules.
_motley said:
With the latest versions of my kernel, you don't need any modules...it's built right into the kernel. Only the stock kernel and the first alpha release of my kernel needed modules.
Click to expand...
Click to collapse
ho...!
Indeed used cifsmanager and got my share name wrong...
Thanks
Sent from my GT-P7310 using xda premium