Actually I use the 184.108.40.206 kernel and jpmatrix's customization tarballrootfs for my debian network programs.
I was very happy to use the debian network diagnostic software on my zaurus. Unfortunately, there is only one option to load this kernel: uboot. The debian system on the zaurus has a lot of interesting packages and works stable - and - veeeeeeery slow. The consequence is, that if i want to use a pim-application or want to play with multimedia i have to use the cacko-rom/pdaxrom/weexpc. So, for now i use debian on a sl-c3200 and cacko on a sl-c1000. ---> I need a dualbooting environment!
For dualbooting i need the sharp bootloader. So i decided to use the actual 220.127.116.11 kernel with iptables included.
This kernel works perfectly on both zaurus. Dualbooting with a sharp-zImage did work, too. But there is be a problem with wireless cf-cards!: Activating any wireless cf-card in 18.104.22.168 ends in error messages and finally in a kernel panic. - bump! -
ifconfig wlan0 up --> kernel panic
Driver-changes from hostap too orinocco and blacklisting didnt help. Moreover, the zaurus has problems with ipv6 loading while booting. So far i have still no wireless cf-card working on the 22.214.171.124 kernel. To my suprise, the critical flashing of any wlan cf-card with new firmware works perfect.
I dont know if there is a general network-problem on the new kernel, hope, somebody can help me to get any wireless cf-card working on the new kernel.