Related
SetCPU 2.0.2 now has perflock disabler support for HTC-kernel 2.6.32.15 which is needed to underclock the CPU because HTC don't want us to mess with the CPU clockspeed on stock kernel. This feature is fine and I use it with JuiceDefender to lock my device to 245 MHz on standby to get slightly more juice. The only drawback is that SetCPU doesn't allow to disable perflock automatically on boot. I found it annoying to disable perflock everytime I reboot, therefore I checked out how SetCPU disables perflock. SetCPU comes with a kernel module that disables the perflock when loaded (it seems to hook into the perflock_notifier_call of the perflock module and resets the settings). I managed to load this module on startup of the device so I can use it with JuiceDefender even without SetCPU installed or enabling it after every reboot. It works great...
SetCPU is a brilliant app like its author coolbho3000 (thank you!).
For this reason I don't post the kernel modules or an update.zip, but share this knowledge in a very loose howto.
So basically this is what to do:
1. Extract the kernel module perflock_disable3215.ko from SetCPU.
Use apktool or just unzip to extract it from the apk.
2. Hexedit the module to change the vermagic string.
The vermagic string have to match the kernel you use. Otherwise, it won't load.
Check the other modules for the correct vermagic.
3. In recovery mode push the module to /system/lib/modules
Maybe you should change the permissions to match the other modules.
4. Load the kernel module with insmod.
For the module to work you have to provide the perflock_notifier_call_addr parameter.
You can get it from /proc/kallsyms. It's a mermory address something like "c443223". Load the kernel module like this:
insmod /system/lib/modules/perflock_disable3215.ko perflock_notifier_call_addr=0xc443223
5. Check if kernel module is loaded.
If insmod doesn't report any errors, check with lsmod if the module is loaded.
If insmod reports errors, you most likely messed up the module while changing the vermagic.
6. Check if perflock is disabled in SetCPU.
If the module is working you should be able to underclock the CPU in SetCPU.
7. Hack a init script to load the module on boot.
The script should rgep the perflock_notifier_call_addr and load module with the correct parameter.
That's it!
If it works for you, buy SetCPU on market!
have fun...
Fantastic,
but a little bit more complicated.
I think you definitely should attach update.zip. But still useful information.
Edit:
Sorry, LeeDroid's mod already has this module. Hypothetically you don't have to change anything regarding that module.
Here is update zip for STOCK ROOTED FROYO ROM. This update will flash modified boot.img (it is necessary, because stock rom at default doesn't execute scripts from /init.d folder during boot..)
Hi,
Anyone who did the update zip for Eclair could upload, please? Would really apreciate.
robto said:
Hi,
Anyone who did the update zip for Eclair could upload, please? Would really apreciate.
Click to expand...
Click to collapse
Has anyone used the update.zip that can confirm it works
There are custom kernel for the Desire Eclair ROMs that aren't perflocked. On what ROMs / devices are you guys?
Ignore....
Hey all,
That procedure seems way too complicated for me
So far, I was using pinky's rom which comes with permanent perflock disabled. I just switched to LeeDroid's rom which doesn't seem to have this feature.
Would there be an easy way to have this done? (like flashing a zip?)
Cheers
http://dl.dropbox.com/u/31174/android/perflock-disabler-2.6.32.15-gf9c0527-signed.zip
ranwej said:
Here is update zip for STOCK ROOTED FROYO ROM. This update will flash modified boot.img (it is necessary, because stock rom at default doesn't execute scripts from /init.d folder during boot..)
Click to expand...
Click to collapse
What's exactly in that boot.img? Could you please post some kind of release notes? I don't like (nor should anyone flash) unknown binaries. Thanks
FloHimself said:
http://dl.dropbox.com/u/31174/android/perflock-disabler-2.6.32.15-gf9c0527-signed.zip
Click to expand...
Click to collapse
Will this work on a stock Froyo (ie HTC) rooted ROM?
EDIT: Did a nandroid and flashed it. Doesn't seem to work... Maybe the stock ROM isn't running the init script as mentioned previously?
FloHimself said:
There are custom kernel for the Desire Eclair ROMs that aren't perflocked. On what ROMs / devices are you guys?
Click to expand...
Click to collapse
HTC Legend with rooted Eclair 2.05.405.2, kernel version 2.6.29-5f084974.
Psych0Chimp said:
Will this work on a stock Froyo (ie HTC) rooted ROM?
EDIT: Did a nandroid and flashed it. Doesn't seem to work... Maybe the stock ROM isn't running the init script as mentioned previously?
Click to expand...
Click to collapse
yes I am just looking for the same to use with the stock HTC kernel ...its on my stock rooted 2.2 Froyo
Psych0Chimp said:
Will this work on a stock Froyo (ie HTC) rooted ROM?
EDIT: Did a nandroid and flashed it. Doesn't seem to work... Maybe the stock ROM isn't running the init script as mentioned previously?
Click to expand...
Click to collapse
playya said:
yes I am just looking for the same to use with the stock HTC kernel ...its on my stock rooted 2.2 Froyo
Click to expand...
Click to collapse
Have you tried the update zip from post 4?
robto said:
HTC Legend with rooted Eclair 2.05.405.2, kernel version 2.6.29-5f084974.
Click to expand...
Click to collapse
This is the .29 kernel and needs the other module from SetCPU...
perflock_disable is now under GPL and source is available upon request...
All kernel modules are automatically under the GPL if they are distributed. It's a legal requirement.
New perflock_disable update.zip for 2.6.32.15-gf9c0527
New signed update.zip to disable perflock for the stock 2.6.32.15-gf9c0527 kernel image:
Mirror: trisk.acm.jhu.edu/perflock_disable-2.6.32.15-gf9c0527-20100831.zip
I updated the init script to handle errors:
Code:
#!/system/bin/sh
#
# Load perflock_disable for htc-kernel
addr=`awk '$3 == "perflock_notifier_call" { print "0x"$1; }' /proc/kallsyms`
if [ -n "$addr" ]; then
insmod /system/lib/modules/perflock_disable3215.ko "perflock_notifier_call_addr=$addr"
if [ $? -eq 0 ]; then
echo "+++ perflock disabled"
exit 0
fi
fi
echo "+++ perflock could not be disabled"
I'll try to obtain the source for perlock_disable, since the author has offered (and is required to) to provide it on request.
teppic74 said:
All kernel modules are automatically under the GPL if they are distributed. It's a legal requirement.
Click to expand...
Click to collapse
Really? Since when? Why then ATI and nVIDIA offer their parts of modules under proprietary licence?
I'm seriously confused about CIFS...
I'm new to Android, so i'm not sure what tools to use to accomplish certain tasks.
Here's my drama, I'm running TNT lite 3.1.4, i can see the CIFS.co file in the system folders, I set cifs up to use insmod and pointed it at the right path.
I can set up the share but no matter what i do i get a message that says "mounting has failed with an error Mount: no such device".
My shares are hosted on win7 x64 machines and a few Server 2008R2 boxes. If i use ES File Explorer i can see all drives (C$, etc) and explicitly naemd shares (Videos, Documents) but i can only successfully access explicitly named shares (with correct UID/PWD)
The same shares (User, Video, etc) accessed via CIFS yeilds that above error message...
I'm out of ideas. I believe others have this working...any thoughts?
-C
Darkeyce said:
I'm seriously confused about CIFS...
I'm new to Android, so i'm not sure what tools to use to accomplish certain tasks.
Here's my drama, I'm running TNT lite 3.1.4, i can see the CIFS.co file in the system folders, I set cifs up to use insmod and pointed it at the right path.
I can set up the share but no matter what i do i get a message that says "mounting has failed with an error Mount: no such device".
My shares are hosted on win7 x64 machines and a few Server 2008R2 boxes. If i use ES File Explorer i can see all drives (C$, etc) and explicitly naemd shares (Videos, Documents) but i can only successfully access explicitly named shares (with correct UID/PWD)
The same shares (User, Video, etc) accessed via CIFS yeilds that above error message...
I'm out of ideas. I believe others have this working...any thoughts?
-C
Click to expand...
Click to collapse
As much as things change around here I may be wrong but I don't think Roebeet put the Cifs kernel into TnTLite. I think that is one of the things he left for the user to patch. There is a Cifs kernel patch for TnTLite in one of these threads that will likely fix what you have going on.. It acts just like that when it is not there... You are using something like CIFS manager to set things up right?
The CIFS module doesn't work with the default TnT kernel - I added it just so the user had it available to them in case they added a customized kernel that could use it.
You should consider it unusable OOTB.
In case you search and don't find it....
http://forum.xda-developers.com/showthread.php?t=889088
Sprdtyf350 said:
In case you search and don't find it....
http://forum.xda-developers.com/showthread.php?t=889088
Click to expand...
Click to collapse
Sprdtyf350 said:
As much as things change around here I may be wrong but I don't think Roebeet put the Cifs kernel into TnTLite. I think that is one of the things he left for the user to patch. There is a Cifs kernel patch for TnTLite in one of these threads that will likely fix what you have going on.. It acts just like that when it is not there... You are using something like CIFS manager to set things up right?
Click to expand...
Click to collapse
I feel kinda dumb now...i saw the thread with the patch but assumed it was only for full STOCK TNT, then when i saw the CIFS.KO file in the TNTlite folders i thought it was active.
I'll try the 3389 CIFS patch on TNT lite (which is what i think is being suggested) and i should be good to go.
thanks all.
Darkeyce said:
I feel kinda dumb now...i saw the thread with the patch but assumed it was only for full STOCK TNT, then when i saw the CIFS.KO file in the TNTlite folders i thought it was active.
I'll try the 3389 CIFS patch on TNT lite (which is what i think is being suggested) and i should be good to go.
thanks all.
Click to expand...
Click to collapse
Yep.. The latest TnTLite is built from 3389 so the TnT patch will do the trick...
The kernel I posted for TnTL has CIFS built in, thus the kernel module roebeet include is not required. Grab CIFSManager and use UMASK=0755 as the option.
]
vsc said:
The kernel I posted for TnTL has CIFS built in, thus the kernel module roebeet include is not required. Grab CIFSManager and use UMASK=0755 as the option.
]
Click to expand...
Click to collapse
Is that the same as this one?
http://forum.xda-developers.com/showthread.php?t=889088
I don't want to lead anyone on a goose chase if there is a specific TnTLite build... If it is in the middle of the big thread then maybe you could put it somewhere more obvious maybe? I seem to remember post 195 from somewhere?
Hi!
I would like to establish a Cisco IPSEC-connection with my Xoom, using get-a-robot-vpnc. The problem is that I'm missing a tun-kernel-module and can't find one for the xoom on the web
Does anyone have one for the Xoom WiFi only running 3.2 (Build HTJ85B) with stock kernel?
Thanks!
McDV
Pulled this out of the EU32Update file, not sure if its what youre looking for??
Questions and requests belong in Q&A. Thread moved.
tonyb15re said:
Pulled this out of the EU32Update file, not sure if its what youre looking for??
Click to expand...
Click to collapse
Thanks, I tried this but it looks like it's only for that ROM.
Maybe someone else has a tun-kernel-module for the stock 3.2?!
Greetings
McDV
yup, I'd like to see this too..
Just instal tiamat kernel 2.1 it contains tun.ko and several other modules.
http://forum.xda-developers.com/showthread.php?t=1200063
also you need to use this modified vpn connections
http://forum.xda-developers.com/showpost.php?p=12124163&postcount=23
Here is tun.ko for 3.2 stock.
wonderful! many, many thanks.
hi,
Will this work on 3.2.1? I copied it /system/lib/modules but when I try to openvpn I get cannot allocate tun/tap dev dynamically.
Is this just a bad file for 3.2.1 or am I missing something else?
I did install busybox and openvpn.
Thanks,
Your tun.ko kernel module needs to be compiled specifically against your kernel source. I don't work with stock anymore, however the developer kernel now floating on xda have this module specifically rolled into their kernels. You would have to root however to install these kernels.
Thanks Kevdog..
I searched and i couldn't find any for 3.2.1. I am the rooted stock 3.2.1 already downloaded from xda. Just need to tun.ko for 3.2.1.
If u know where to find, please send me the link.
Thanks.
Ok 3.2.1 -- Stock or Rooted? What kernel are you running?
I got my rom from this thread
http://forum.xda-developers.com/showthread.php?t=1278214
Thanks,
Ok -- I know this is a lot of work, however I tried it myself and I'm not sure if the rom you linked to is corrupted or my download process failed. (***Rant -- why all the developers who put out files don't match the file to an md5 sum so us users can verify the integrity of the dowload -- I'll never know!!), but I can't seem to extract your system.img. You'll need a tool such as unyaffs to unpack the system.img and then search around in the modules folder until you find the tun.ko. Or you could just flash a Tiamat 3.2.1 kernel which has these modules built in!!
I checked checksum and it was correct before I installed it. Not sure what u mean, I thought this rom doesn't have it period.
I also tried to use tiamat 2.2 which says its for 3.2 but it got stuck at boot for 30 minutes at the honeycomb screen. I thought maybe tiamat ker
Net doesn't support 3.2.1 yet.
http://forum.xda-developers.com/showthread.php?t=1200063
As far as i know this is latest. Doesn't mention 3.2.1. Didn't work for me.
I don't want to go to tiamat rom to avoid a full rebuild.
Hi,
Usually on linux, there is a kernel loading modules at boot-time framework, cf. modules.conf.
No longer present in android.
When typing lsmod, there is two modules loaded by default : tntfs, and bcm4329 (and voodoo_sound
if you have it).
I'm trying to figure out what is the standard procedure on android : I've noticed on the
init.rc that the tntfs.ko is loaded, but can't figure out when bcm4329.ko is loaded.
Any idea ?
Moreover, I know that voodoo controller is able to load his own kernel module (voodoo-sound)
at boot-time. Anyone knows how the voodoo dev did that ?
My current idea is to modify init.rc to source a new file - let's say init.rc.local - to keep my custom mod. It'll
allow minimal changes when updating+root : just copy the init.rc.local and change the init.rc...
Sounds like we're recreating linux boot framework. lol.
This is something I've done on the HTC Incredible and the Droid 1 in the past, but in honeycomb, this is different, not very obvious yet:
Rather than try to emulate whatever Redhat or Ubuntu has done, which usually doesn't work, I either would use the line where tntfs.ko is insmod'd in /init.ventana.rc (sorry, think that's the filename), and add in the modules you want to add right there. Make sure to save the original file so you'll have a shot at fixing it if you make a mess.
The other thing is just to find some developer that appears to know what they're doing, and download their ROM, like Roach. I just downloaded his prime 1.6 ROM and unpacked it, then noticed immediately that he's got this in there:
/system/etc/init.d/01init{stuff},
Well that seems pretty important, so I did a grep 'init.d' * -R from the / level, and could only see little of importance, not any shell file like initrc pointing to it, just that busybox is linked to it, etc.
I figured it's worth a shot to create the same file structure on the stock ROM (/system/etc/init.d/0X{name} and see if it executes :: Start it with the usual #!/system/bin/sh
# load some modules
/system/bin/inmod /system/lib/modules/cifs.ko (or whatever)
and see what happened, if anything.
Better yet, I'd just send a message to Roach or some other ROM developer and ask.
Good luck -
altsyst said:
Hi,
Usually on linux, there is a kernel loading modules at boot-time framework, cf. modules.conf.
No longer present in android.
When typing lsmod, there is two modules loaded by default : tntfs, and bcm4329 (and voodoo_sound
if you have it).
I'm trying to figure out what is the standard procedure on android : I've noticed on the
init.rc that the tntfs.ko is loaded, but can't figure out when bcm4329.ko is loaded.
Any idea ?
Moreover, I know that voodoo controller is able to load his own kernel module (voodoo-sound)
at boot-time. Anyone knows how the voodoo dev did that ?
My current idea is to modify init.rc to source a new file - let's say init.rc.local - to keep my custom mod. It'll
allow minimal changes when updating+root : just copy the init.rc.local and change the init.rc...
Sounds like we're recreating linux boot framework. lol.
Click to expand...
Click to collapse
Tested.
Does not work, because modified room probably calling busybox run-parts.
Anyway I've found a hack, I'm posting it on general section.
I am trying to compile a custom kernel,
I succeed to build one but I can't boot him, when I load the kernel I go in to boot loop
I haven't made any real changes to this kernel I really just downloaded the source and compile it
The version match its a GB kernel 2.6.35.7 I disabled the lag fix, still it goes to boot loop.
any ideas?
What source code did you try to use to build this kernel? Links would be awesome.
Well I tried this two
Code:
github.com/Krylon360/SGS4G_Kernel_GB
opensource.samsung.com/index.jsp (SGH-T959V-TMB_GB_Opensource.zip)
I did
make clean && make mrproper
make vibrantplus_rev00_defconfig
make -j8
and then I loaded the kernel via heimdall
Building the stock kernel
I have run in to a similar problem. One issue I had to get past is the stock rom source does not have have the initramfs included. It is needed so the kernel can boot into a file system before it can start loading loadable modules and mount the rom filesystem.
I have been able to get an initramfs by extracting it from the original rom, The issue I have is it is loading all modules, but the rom devices will not mount as the /dev directory is empty and the mount needs them to mount the file systems.
This may be off topic for this forum. If you want to PM me, I'm willing to let you know what I have found out.
Tom
You should keep discussing it here since it does pertain to the phone and it'll be useful for future reference
Sent from my SGH-T959V using XDA App
Agree with FB.
I have ran into the same problem. I was unable to find a way to get it beyond boot loop so I scratched the project. I am definitely curious on how to get this working.
FBis251 said:
You should keep discussing it here since it does pertain to the phone and it'll be useful for future reference
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
DISCLAIMER
I am NOT a kernel developer, just a programmer that has done linux programming before, and is trying to understand and build the kernel.
I will share what I have found out through my attempts to build the stock rom as delivered from Samsung.
I have searched XDA and Googled the web in search of the answers I need with some success as well as dead ends. I am not looking to have the answers handed to me on a silver plate, but a few hints or links to point me in the right direction is helpful.
To start:
Recommended Hardware needed:
Search the XDA for AdamOutler threads on building the serial interface via the USB. Highly recommended reading as it helps to see what the kernel is doing when it is in the bootloop. All the important parts was purchased from his recommended supplier(s). Thanks AdamOutler for the information!
What I know about the samsung kernel source as delivered:
1) if you follow the readme in the kernel, it will build cleanly. However, it will NOT run, it will bootloop!!
2) If you intend to only build the stock kernel, I recommend making sure you are starting with a stock build installed on the phone. I suggest the same release version you are trying to build.
3) After you build the kernel and load it ( the zImage file is loaded via Heimdall ) the first problem I ran into was the initramfs. It is not included in the source and must be created from scratch or obtained from another kernel.
4) Once the initramfs is being built and included in the kernel, the next problem is the driver modules that are included, have to have the same version as the kernel. You will need to figure out the version by the kernel debug messages on the serial/usb interface mentioned above. Once the versions match, the kernel will load them.
This is where I am stopped... once the drivers are loaded, the init scripts mount the file systems. This does not happen with my kernel. I am still investigating this. I think it has to do with the /dev files for the mount points not being created/missing. I have not found the piece of info yet points me to the solution. Most of the links I have found pertain to linux on an x86/64 platform. I have found little on embedded linux and how it works.
That is all I have in a nutshell. Feel free to comment and ask questions. Remember to search! Use different forms of your search terms, use different working. I like to use the 'yippy.com' search engine as it places the results in categories.
Good luck!
Tom
logan123 said:
Well I tried this two
Code:
github.com/Krylon360/SGS4G_Kernel_GB
opensource.samsung.com/index.jsp (SGH-T959V-TMB_GB_Opensource.zip)
I did
make clean && make mrproper
make vibrantplus_rev00_defconfig
make -j8
and then I loaded the kernel via heimdall
Click to expand...
Click to collapse
Krylon's tree is stock, no changes.
It has all the problems I fixed in my tree.
I have a lot of uncommitted changes, but you can find my work at: https://github.com/bhundven/
Regardless of me being on xda or not, I am still working on sgs4g.
bhundven said:
Krylon's tree is stock, no changes.
It has all the problems I fixed in my tree.
I have a lot of uncommitted changes, but you can find my work at: https://github.com/bhundven/
Regardless of me being on xda or not, I am still working on sgs4g.
Click to expand...
Click to collapse
Aww hell bhundven! Refreshing to see you stop by!
Thank you everyone
mccabet, You actually saved me some time because those were my next two step
I was looking for the initramfs and I didn't find it...
Could you please share your?
I do not have my initramfs file available to me at work. So here is the info I used to get my copy. You will need an original rom release ( I used the heimdall one-click from bhundven ) to extract the zImage file from.
Here is the link to info on how extract your own initramfs from a kernel image (zImage):
http://forum.xda-developers.com/wiki/index.php?title=Extract_initramfs_from_zImage
I used the improved script mentioned at the bottom of the page from:
https://github.com/mistadman/Extract-Kernel-Initramfs
After getting your initramfs, you will need to modify your vibrantplus_rev00_defconfig file and change the following parameter to point to your initramfs you extracted:
CONFIG_INITRAMFS_SOURCE="/path/to/initramfs"
Hope that helps.
Tom
Ok it seems like I was able to boot the kernel, no more boot loops thank to the initramfs but
The system isn't loading, it get stuck on the "Galaxy S 4G" page.
and when I load recovery it gives me lots of error so as
E:Can't mount /cache/recovery/log
E:failed to mount /cache (No such file or directory)
it goes on and on but its all the same...
logan123 said:
Ok it seems like I was able to boot the kernel, no more boot loops thank to the initramfs but
The system isn't loading, it get stuck on the "Galaxy S 4G" page.
and when I load recovery it gives me lots of error so as
E:Can't mount /cache/recovery/log
E:failed to mount /cache (No such file or directory)
it goes on and on but its all the same...
Click to expand...
Click to collapse
I may be off-base, but do you know if /cache and the other file systems were the Samsung rfs filesystem or the ext4 filesystem? Standard recovery can't mount ext4 & if your kernel doesn't support it, then it won't be able to mount them, either.
I thought so too so I removed the lag-fix and return to rfs
but this is neither because apparently there are no stl devices :\
I pulled out the recovery log
Code:
http://pastebin.com/hDCNbdne
Code:
failed to mount '/dev/block/stl11' '/cache'(rfs) -> No such device
Now I feel like an idiot because I can't seem to find what is it in the kernel config
moreover I tired to pull a config from a working kernel and I basically got the same errors
Any ideas?
Well the solution is simple, apparently version magic didn't load the kernel modules
for rfs_fat and fsr_stl...(you get the point)
now I can't to find way to compile them it seems as if someone removed them from the kernel tree and I can't load them either
I tired several modules from different kernel well all result in failure.
so any ideas?
logan123 said:
Well the solution is simple, apparently version magic didn't load the kernel modules
for rfs_fat and fsr_stl...(you get the point)
now I can't to find way to compile them it seems as if someone removed them from the kernel tree and I can't load them either
I tired several modules from different kernel well all result in failure.
so any ideas?
Click to expand...
Click to collapse
I wish had some, man. I've never compiled a kernel for Android. At least, not yet. However the moduel code should be somewhere in the kernel tree. I believe Android is a layer on top of the Linux kernel so the source may be there.
I'm still reading about and learning the platform side of Android. Hopefully one of the devs around can provide some solid guidance.
Ok no offence but this kernel is worthless
even if I load the modules into the kernel I get a errors because of the unknown symbols
bahh any ideas anyone?
stephen_w said:
I wish had some, man. I've never compiled a kernel for Android. At least, not yet. However the moduel code should be somewhere in the kernel tree. I believe Android is a layer on top of the Linux kernel so the source may be there.
I'm still reading about and learning the platform side of Android. Hopefully one of the devs around can provide some solid guidance.
Click to expand...
Click to collapse
That is as far as I have gotten. The drivers for the RFS ( drivers/tfsr ) are not loading and therefore the /dev mount points do not exist. The default build config flags ( CONFIG_RFS_FSR=m and CONFIG_RFS_FSR_STL=m ) are to build the module as a loadable module. I have tried to build the module with no success. Still investigating when I have the time. I was even thinking of looking at the Epic 4G MTD build and trying that. The problem there is if I can not solve this problem, I probably solve it by trying the MTD conversion. ( Except to brick it.)
if one of you kernel devs gets a bootable MTD kernel hit me up... I got a rom that needs some mtd loving
RaverX3X said:
if one of you kernel devs gets a bootable MTD kernel hit me up... I got a rom that needs some mtd loving
Click to expand...
Click to collapse
I do not claim to be a kernel developer. I am trying to understand and build the base kernel. If you can help me get past this, that would be great! I need to take baby steps before I can start walking. Once I get the build to work and boot completely, I'm game to go further, but have to get to a working base before we can continue. I understand the more experienced developers don't want to be bothered. I understand they have other jobs, and families. So do I. They became as great as they are, through hard work, experience and asking the right people the right questions. Asking the right question also applies to Google. The query only returns the matches to your query. Change a few words, get different results.
I'm not looking for someone to hold my hand, I want to learn by doing, not having it done for me. Just point be to the bread crumb trail, and I will follow.
Right now, I am at a stand still until I figure out why it is not loading the tfsr module. If that is even the problem.
If I make any progress, I'll post it here for all. If I am wrong, please correct me so we all don't go down the wrong path.
Thank you for listening.
Tom