Not only this, I agree with 2or0 that some of the packages and the scripts in the after installation tarball (now 1.1 ) are not suitable for the Angstrom kernels. And his X server is no longer Angstrom's as well. So YMMV.
Sorry for the confusion caused so far, because my 3200 is running the yonggun kernel so there is no way for me to check how the same things may work for the Angstrom kernel. I just started out naively presuming that it's the same, but that seems not to be the case.
If it turns out that the script works somehow or need some modification, please do!
Posting to the OESF wiki now ...
After
BigZ's flirtation with
cortez-debian, we got thrown out by the partitioner refusing to work, I'm back using Q17. I'm using the
poky 2.6.21 kernel and modules. The only glitch is, seems to be true for angstrom kernels too, is that I couldn't use the poky updater.sh. It didn't recognise my model (3200). So I used the updater.sh from bigbridge.
I'm into the 2nd script. By the way, with this kernel+module set, the eth2 bit doesn't work. What happens is that wlan0 works in the interfaces file but eth0 gets a mention at boot up! I also had to blacklist hostap before I could get a wifi connection working.
So there is a diversion from the normal run there.
When the 2nd script begins to run the applieddata repository comes up with error messages and 404s. I'll comment that line out of sources.list for now. The gnuab repository seems to be very alive!
I'm going to hold off on trying to run a gui until I'm sure that everything else is working as per the advertisements! In particular the touchscreen stuff.
Yesterday, after interfering with your scripts, I did get to a gui. But there was no response to the screen, even though the libs and apps you mention were present. I'm trying to be a very good boy and let your scripts run without my interference. I'll get a drink of tea and go for a walk after the 2nd script stops and I reboot. I'll post later on when I've tried a few experimental uses of the system.