Posted: Sat Dec 22, 2007 13:09 Post subject: Packages and more (my experiance with v24rc5)
Hi together,
I fiddle around with my IBM 8364 Netvista N2800 thin client and ddwrt v24rc5. Here are some hint's, what I get to work, and what makes problems:
- I didn't manipulate the CF cars layout of ddwrt, cause this is complicated and not update reliant. After a "nvram commit" part3 (/usr/local/) is ro remounted ...
- For my own software I plug in an USB Stick and uses that (only USB 1.1, but fast enough) This stick is mounted to /jffs via
Code:
rc_startup='if ! mount | grep -q " /jffs"; then
insmod sd_mod
fsck /dev/discs/disc2/part1
mount /dev/discs/disc2/part1 /jffs
fi
for i in /jffs/etc/init.d/S*; do
$i start 2>&1
done &'
- Most of the packages I use are from Openwrt kamikaze. Here is the ipkg.conf file:
- All configuration files are put to /jffs/etc and a start Skript in
/jffs/etc/init.d mounts them over the existing ones, e.g.
Code:
mount -o bind /jffs/etc/profile /etc/profile
mount -o bind /jffs/etc/ipkg.conf /etc/ipkg.conf
- All packages of Openwrt kamaikaze work well, I try xinetd, lsof, zile, joe, htop, strace, zip, unzip, e2fsprogs, mt-daapd (needs gdbm, howl, owl-mdnsresponder), gkrellmd, smartmontools
- Cross compiling was done on an ubuntu VMware system:
- On ubuntu install subversion, patch, g++, bison, .... (missing tools are checked by toolchain)
- Get toolchain:
Code:
svn co https://svn.openwrt.org/openwrt/trunk/
make menuconfig (choose target x86)
make
- Result isin trunk/staging_dir/toolchain-i386_gcc4.1.2
- ddwrt mkfs, fsck works well with the USB, but not on the IDE disc.
However the installed Openwrt tools do (see ticket 2846)
- Very poor performance of the IDE disc (see ticket 2847). It seems not to run in DMS mode. It's not a hardware issue, cause with FreeNAS on the CF card the disc is read with approx 25MB/s with only 15% total CPU usage.
I hope the performance issue will be fixd by the experts soon (openwrt kamikaze shows it too). And some of the above modifications will be imported into the release (e.g. one free part on CF, so the USB stick will not be necessary, or the ipkg modifications to use Openwrt packages).
Perhaps if this is of interest of more people, someone with wiki expreiance has time to put the info in it. Further if it's of interest I could provide the init scripts and the samba-3 binary tree.
Many thanks to all of the developers for this really amazing firmware.
Thanks for the excellent post wlanguy. This make it possible to run ddwrt and make use the power of x86 machine to the fullest. I knew sooner or later someone will crack this and there you are, sitting on it. Have you tried running apache+mysql+php? Hope the developer will add the mod as you said and spare us a free part from CF so no need for USB stick anymore. _________________ - adx -
No, I never try apache+mysql+php up to now. I the openwrt package repositoy only apache, php_pear and sqlite3 is available. However cross compiling apache, myql, php si due to the massive dependencies not really an easy job.
Mostly I'm missing the availability of the optware repository for x86 ...
[/quote]
No, I never try apache+mysql+php up to now. I the openwrt package repositoy only apache, php_pear and sqlite3 is available. However cross compiling apache, myql, php si due to the massive dependencies not really an easy job.
Mostly I'm missing the availability of the optware repository for x86 ...
[/quote]Use OpenWrt Kamikaze. The packages are no longer compatible with DD-WRT and if you mix binaries you'll run into even more problems then you try to fix.
Use OpenWrt Kamikaze. The packages are no longer compatible with DD-WRT and if you mix binaries you'll run into even more problems then you try to fix.
Please don't evangelize .... I've tried openwrt,and there are other problems. However the packages ARE binary compatible, belive me. The only problem are the kernel modules due to the different versions .....
I would appreciate when you are able to contribute to ddwrt in the future.
O.k. that's apoint. But it's easy fixable by installing the required uclibc in/jffs/lib and setting the LD_LIBRARY_PATH which is necessary for may packages and the optware nslu2 packages.
The most usefull approach in my opinion is to motivate the optware guys to cross compile for dd-wrt x86 in the same way as it's done for the mipsel packages.
Is there anybody out there who has good connections to the optware team?
1. What did you modify in the profile file? I get the impression you changed PATH to start with /jffs/bin
2.Explain why you need to cross-compile all the packages? Doesn't the openwrt x86 packages work ok with dd-wrt x86? I have the impression you only cross compiled optware packages or packages made for different CPUs.
3.If the openwrt packages work well, is there any preference between the 7.07 and the 7.09 x86 packages? _________________ We all face the choice between what is right and what is easy.
2.Explain why you need to cross-compile all the packages? Doesn't the openwrt x86 packages work ok with dd-wrt x86? I have the impression you only cross compiled optware packages or packages made for different CPUs.
I try to use the openwrt x86 packages when ever they run stabe. Cross compile was necessary for ntpd (to compile in raw dcf77 serial line receiver support) and samba, cause there is no V3 available. Up to now I didn't compile more packages. What I miss is cyrus, php, and dependencies to put my mail server (home one for family, which fetches mail from provider and has a squirrelmail web interface) on the thin client. At the moment it's running on a FreeBSD server, but it consumes too much power .....
So it would much help to have the optware packages compiled for ddwrt and x86. Then it's easier to keep the software stack independent from the base system and you don't be dependent from openwrt in any case.
Quote:
3.If the openwrt packages work well, is there any preference between the 7.07 and the 7.09 x86 packages?
Most of them seems to work well. I've had problems with nfs (user land server), cause portmap dies with segmentation fault in a really early state. strace cant help so far, even though LD_LIBRARY_PATH.
I used the newest ones first, cause the kernel versions differs least between 7.09. However all kamikaze kernel modules could not be used therefore. The 7.07 repository contains a lot of packages not yet available in the other ones. The 7.09 isn't really necessary for me at the moment. The top level package dir is the newest one, but the package versions are the same when they are also available in 7.07 and 7.09 so far I've checked this
that's possible, but at the moment I didn't have them available as ipkg .... I'm not familar with the format. For me it's enough to have them as a tarball, which I could unpack in /jffs.
Is there any update on this issue? It appears to be a fix for IPKG support. _________________ Q: How do I do ...? A: Read the tutorials or Search forums
alas no updates available. I stopp the project of enhancing the ddwrt-x86 machine and put FreeNAS on it, which is much better expendable for the things I want to do.
So I further go with dd-wrt on my asus wl-500gp.
What are especially you interested in?
Alas I still did not know how to upload the tarballs on the dd-wrt site. Perhaps someone could help?
