Tyler, This mailing list is the correct one for Angstrom user specific questions as you mention -- however, many many people use Angstrom with the Beagleboard as Koen and others have put significant work towards its compatibility there -- hence my suggestion of the google-group.
Regarding your error message -- the charset it mentions is typically a module. It can be compiled into the kernel, however. Perhaps the previous kernels were compiled with iso8859 support and the latest was not? I cannot directly check for you as I build my own custom configuration of angstrom using open-embedded (something you might like to look into if you want more control over what goes in!) and thus my configuration is quite different to the demo images. Open-embedded is not for the faint of heart, but it is incredibly powerful once you get it working! ~Akram Hameed -----Original Message----- From: angstrom-distro-users-boun...@linuxtogo.org [mailto:angstrom-distro-users-boun...@linuxtogo.org] On Behalf Of Tyler W. Wilson Sent: 29. June 2009 09:41 To: angstrom-distro-users@linuxtogo.org Subject: Re: [Angstrom-distro-users] Issues with demo/beagleboard directory Akram, First, thank you for the quick response. I posted initially since I was talking about files put on the angstrom-distribution.org site. Thank you for the link to the Google groups discussion. I actually had not seen that before. I had seen the Google files section, which appeared to be older and not applicable (they list many of the files for RevC BB, but I have a Rev B7). The mixing of versions is what I expected, but I thought I would double-check. BTW, you say 2.6.29 works better for you. Does this work for you?: mount /dev/mmcblk0p1 /mnt/fat I get this: r...@beagleboard:~# mount /dev/mmcblk0p1 /mnt/fat [ 84.209808] FAT: IO charset iso8859-1 not found mount: wrong fs type, bad option, bad superblock on /dev/mmcblk0p1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so If I use 2.6.28 or 2.6.27 the mounting works fine. Hints? I will be moving over to the Google groups list now... Thank you, Tyler On 6/28/2009 6:16 PM, Akram Hameed wrote: > Hi Tyler, > > Mixing and matching rootfs with different kernel versions may work -- > but is not really recommended. > > Regarding which kernel to use; 2.6.28 works well for most things, but > 2.6.29 (for me at least) solved some nasty disk IO issues. To get more > beagle specific support, I suggest you visit the Beagleboard google > group if you have not already: > http://groups.google.com/group/beagleboard > > Note on your question 5: yes, you just untar in the root and it should > place modules in the correct location. Be sure to preserve permissions > on the files or things could get tricky ;) > > ~Akram Hameed > > -----Original Message----- > From: angstrom-distro-users-boun...@linuxtogo.org > [mailto:angstrom-distro-users-boun...@linuxtogo.org] On Behalf Of Tyler > W. Wilson > Sent: 29. June 2009 01:21 > To: angstrom-distro-users@linuxtogo.org > Subject: [Angstrom-distro-users] Issues with demo/beagleboard directory > > First, I understand these may not be official builds here - > http://www.angstrom-distribution.org/demo/beagleboard/ - but I do have > some questions regarding them. > > 1. While following these instructions - > http://elinux.org/BeagleBoardNAND - I ran into an issue where kernel > 2.6.29 (uImage 2.6.29-r37) could not mount the FAT partition on my SD > Card. Said something about bad ID or something. I can reload and get the > > proper error if need be. > > 2. I then tried kernel 2.6.28, but it would always fail when trying to > transfer the root fs, with an ECC error and then a segfault. > > 3. I then tried 2.6.27 and this worked to get the root fs installed to > mtd4 in NAND. Which leads me to the next issue/question: > > 4. There is only one rootfs image in the demo folder, which appears to > be made for a 2.6.29 kernel. But I am currently running the uImage, > which is 2.6.28. I am no kernel expert, but I expect this to cause some > mismatch issues. Should there be a rootfs for each uImage in the demo > folder? > > 5. Finally, I notice there are module-XXX-beagleboard.tgz files that > match the uImage kernel files. Is there is a description of how to > install these? I am assuming that I just untar them into the root > /lib/modules folder where ever I am running from. Is that right? > > Perhaps somebody could add a couple notes to the README.txt that is in > the same folder, so save some of us some issues. > > Thank you, > Tyler > > > > _______________________________________________ > Angstrom-distro-users mailing list > Angstrom-distro-users@linuxtogo.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-user > s > > _______________________________________________ > Angstrom-distro-users mailing list > Angstrom-distro-users@linuxtogo.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-user s > _______________________________________________ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-user s _______________________________________________ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
