@cbxbiker, Yes, of course, you are right as I now see. I should have thought a bit longer as booting the kernel halted after loading it and never got to do anything after. Silly really.

I have now loaded your 3.9.2 kernels for an eSata and a SDHC based Sheevaplugs and they work. It still seems a shame that different .dtb files are needed depending on whether a disk or SDHC is used to boot from. Despite these working, I will still try rolling my own so I understand what is going on - plus I will need bit bashed 1-Wire on my Guruplugs in the not too far distant future.

A nice, easy to read tutorial on .dtb would be welcome (though I havn't looked at the devicetree.org site lately). Onward and upward!

Well I tried the precompiled 3.9.2 kernel on my compiler/test eSata Sheevaplug using the script but my system did not boot. It loaded the uImage but then failed to load. I am pretty sure that the problem is that I am using EXT4 on root (/dev/sda1) and by default, I see that EXT4 is not set up either as a module or builtin.

Therefore, I am starting to build a 3.9.2 kernel with Device Tree from scratch! Its edukayshun innit!

@cbxbiker Many thanks for that.  I'll have a tinker later when I get a couple of hours.

I had a look at your site and see there are many patches that I had not seen previously so there is some 'reading' I have to do. Keep up the good work!

I still need to get to grips with Device Trees for my own satisfaction (its the old geek in me I guess) and other embedded hardware I wish to develop.

Yes the same uImage. I really do not want to use different kernel variants for my Sheevaplugs depending on the type of storage used. The built xilka kernels (at least the last time I looked at the xilka .config files) still treated eSata as a module and thus would not boot from disk as I want.

Although I havn't checked yet, yes, I think my problem is  use of .dtb (flattened device tree) files for hardware in the new kernel. Taking the .config (/proc/config.gz) file from an older kernel, not using fdt, will try and use the old style hardware setup. As the SDIO is (I think) now set up in fdt, there plainly is an incompatability. With eSata, it does not seem to matter. Obviously this is something I will have to check. As I also want to get newer kernels for Tonidoplug2 (Topkick) and previously had no success with the fdt version, I will have to see how these work in 3.9+. I will also try and understand the use of fdt in u-boot and kernel as documentation is a bit scattered in my opinion.

I have also compiled 3.9.1 for my sheevaplugs with mixed results. Three of my Sheevaplugs use eSata to boot from and 3.9.1 works fine. However I tried the same kernel on a SD card based Sheevaplug and that failed when setting up the sdio subsytem. If I had known, I should have saved the console output but I needed to return the 'plug to service ASAP so reverted to an older kernel. I did notice that the console output differed around the sdio setup between 3.6.10 and 3.9.1. I am using a newer u-boot (2012-??) than stock. I don't think Sheevaplugs use flattened device tree yet (though it seems that Guruplugs may do so). I used the cbxbiker patches (3) and used 'make oldconfig' taking the current '/proc/config.gz' as a base.

So from my limited knowledge, I would say there is a problem with the Marvell sdio in the 3.9+ kernels and looking at the kernel changelogs, plainly there are changes afoot in that area. I think someone has to get the right combination of configuration, modules and possibly code changes in the sdio area to get Sheevaplugs working with 3.9+ kernels.

I may be wrong, but with a 2.6.30 kernel, I think the size limit is 2.2TB. Is this possibly a cause?

I am currently working on FusionPBX as a GUI front end to Freeswitch configuration.

I would not recommend using the FusionPBX/Freeswitch installation shell file 'install_fusionpbx.sh' as indicated in the wiki as it makes quite a lot of assumptions. However looking at the script does help set up things. I am using mysql so I was initially having problems because I had not installed php5-mysql.

Converting from hand crafted .xml configuration files to mysql database is not straightforward. Esentially, FusionPBX sets up the mysql database with default values and that WILL clobber freeswitch's .xml configuration files, so be sure to take an up to date copy of your /usr/local/freeswitch/conf directory. It will be needed to examine your working variables and writing them into the database. I also use Webmin to manually change the mysql Fusionpbx database tables where that is more appropriate.

A very tedious procedure but when done, FusionPBX will make Freeswitch easier to manage and it is a great pity there is not a simple way to provide custom data into the fusionpbx database.

I have compiled and am using the DENX u-boot for Sheevaplug and Guruplugs. The version I compiled was u-boot-2011.06 and I do not recall patching anything as the variants already have a config file for them. I also confirm that the environmemt variables have moved as above post and modifying the fw_env.config file as above fixes the problem. Note that arcNumber becomes machid and is in hexadecimal rather than decimal.

This is my first post on this forum though not particularly new to Sheevaplugs etc.

I also am running Freeswitch on a Sheevaplug for my home PBX. I origonally compiled version 1.0.4 but I think I am now running 1.0.8. I am using Debian Wheezy with a kernel 3.0.3. I natively compiled with the latest gcc available at the time. The setup has been reliable apart from the sheevaplug PSU failure. I am registered with two SIP providers but my ADSL broadband bandwidth is not good enough to give high quality speech (a rural area). There are 5 SIP phones, a PAP2T, a D-Link VTA box origonlly locked to Vonage but now unlocked to work with the 'plug PBX, an SPA3102 for PSTN access. I have 5 SIP phones attached. At present, I am using SIP protocols so speech uses the Sheevaplug rather than RTP for direct phone to phone connections. As there is only two users here at home, the number of calls is not a problem at present.

initially i did have a compilation error which was due to C type casting that I think was in module 'sofia_mod.c' though it is quite a while since I compiled so I can't be 100% sure.

I would certainly recommend the freeswitch book which is plugged on the freeswitch site. I have made some comments on the NewIT site about Freeswitch also.

There are many bells and whistles I hope to implement though time is a problem! I have recently been exploring the FusionPBX GUI for Freeswitch though my previous experience with FusionPBX wiped out my Freeswitch configuration which I had to regenerate from scratch. I now back up the config before meddling with freeswitch.

I have the feeling there is a Freeswitch repository at 'dotweb.org' but I havn't yet investigated. In any case, that may be for Intel hardware. The FusionPBX site has some installation scripts for both Freeswitch and FusionPBX but they are quite complex and I have not tried anything yet. I need to try these out on a non-live sheevaplug.

Have fun anyway.