From: Bob C. <bco...@ve...> - 2011-07-11 00:31:18
|
How do I use the UBI images that are created when you build omap3-console-image from the overo-2011.03 branch? Are they replacements for MLO or the other 'traditional' files? Thanks Bob |
From: Bob C. <bco...@ve...> - 2011-07-11 02:28:16
|
I Googled and found a great how-to for UBI images on Steve Sakoman's site: http://www.sakoman.com/OMAP/how-to-write-an-ubifs-rootfs-image-to-nand.html?utm_source%3Dfeedburner%26utm_medium%3Dtwitter%26utm_campaign%3DFeed:+BeagleBoard+%28BeagleBoard.org%29 Bob On 7/10/11 8:31 PM, Bob Cochran wrote: > How do I use the UBI images that are created when you build > omap3-console-image from the overo-2011.03 branch? Are they replacements > for MLO or the other 'traditional' files? > > Thanks > > Bob > > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Steve S. <sa...@gm...> - 2011-07-11 02:38:52
|
On Sun, Jul 10, 2011 at 7:28 PM, Bob Cochran <bco...@ve...> wrote: > I Googled and found a great how-to for UBI images on Steve Sakoman's site: > > http://www.sakoman.com/OMAP/how-to-write-an-ubifs-rootfs-image-to-nand.html?utm_source%3Dfeedburner%26utm_medium%3Dtwitter%26utm_campaign%3DFeed:+BeagleBoard+%28BeagleBoard.org%29 Since Neil is providing a pre-made .ubi image you could use method two in that article and just skip the first few steps that create the .ubi image from a tarball. Basically you would just need to do the final ubiformat step. Steve |
From: JamesAng <ang...@gm...> - 2011-08-11 09:11:45
|
sakoman wrote: > > On Sun, Jul 10, 2011 at 7:28 PM, Bob Cochran <bco...@ve...> > wrote: >> I Googled and found a great how-to for UBI images on Steve Sakoman's >> site: >> >> http://www.sakoman.com/OMAP/how-to-write-an-ubifs-rootfs-image-to-nand.html?utm_source%3Dfeedburner%26utm_medium%3Dtwitter%26utm_campaign%3DFeed:+BeagleBoard+%28BeagleBoard.org%29 > > Since Neil is providing a pre-made .ubi image you could use method two > in that article and just skip the first few steps that create the .ubi > image from a tarball. > > Basically you would just need to do the final ubiformat step. > > Steve > Hi Steve, I was reading through your guide to making an ubifs image from rootfs tarball and a question comes to my mind regarding the additional module's tarball. Should the module's tarball also be extracted to the same rootfs before calling mkfs and ubinize? Or is it that the module's tarball is already in the rootfs tarball? Secondly, David mentioned that having the UBIFS_DEBUG's MSG_LVL=3 enabled will consume up the space in the gumstix in no timee. David Abdurachmanov wrote: > > ... > There is one more change to the steps, UBIFS_DEBUG with MSG_LVL=3 is > enabled, which very much eats your CPU (writing syslog) and kills Gumstix > in several minutes with "out of space" problem. > > But, I must say, it so much better comparing to JFFS2. > What is the solution to this and which step(s) in your guide should I modify and where in the BB's image recipe should it be stated too so that it is part of making the ubifs image via bitbake? Thanks in adv. James. -- View this message in context: http://old.nabble.com/UBI-Images-In-overo-2011.03-Git-Branch-Build-of-omap3-console-image-tp32034242p32240525.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: David A. <cy...@ho...> - 2011-08-11 09:59:48
|
Hi, CONFIG_UBIFS_FS_DEBUG_MSG_LVL is removed starting 2.6.39 kernel, I think. If you are using older kernel it still might be set to 3rd level. That was causing problems for my implementation as I remember. You always can change that in your kernel configuration. I would suggest using 2.6.39 + UBIFS memory leak fix kernel images for now. tar.gz and ubi images contains identical files and directory structures. BitBake is capable of preparing rootfs images in multiple file systems, but their content is identical. -david JamesAng wrote: > > > sakoman wrote: >> >> On Sun, Jul 10, 2011 at 7:28 PM, Bob Cochran <bco...@ve...> >> wrote: >>> I Googled and found a great how-to for UBI images on Steve Sakoman's >>> site: >>> >>> http://www.sakoman.com/OMAP/how-to-write-an-ubifs-rootfs-image-to-nand.html?utm_source%3Dfeedburner%26utm_medium%3Dtwitter%26utm_campaign%3DFeed:+BeagleBoard+%28BeagleBoard.org%29 >> >> Since Neil is providing a pre-made .ubi image you could use method two >> in that article and just skip the first few steps that create the .ubi >> image from a tarball. >> >> Basically you would just need to do the final ubiformat step. >> >> Steve >> > > Hi Steve, > > I was reading through your guide to making an ubifs image from rootfs > tarball and a question comes to my mind regarding the additional module's > tarball. > > Should the module's tarball also be extracted to the same rootfs before > calling mkfs and ubinize? > Or is it that the module's tarball is already in the rootfs tarball? > > Secondly, David mentioned that having the UBIFS_DEBUG's MSG_LVL=3 enabled > will consume up the space in the gumstix in no timee. > > > David Abdurachmanov wrote: >> >> ... >> There is one more change to the steps, UBIFS_DEBUG with MSG_LVL=3 is >> enabled, which very much eats your CPU (writing syslog) and kills Gumstix >> in several minutes with "out of space" problem. >> >> But, I must say, it so much better comparing to JFFS2. >> > > What is the solution to this and which step(s) in your guide should I > modify and where in the BB's image recipe should it be stated too so that > it is part of making the ubifs image via bitbake? > > Thanks in adv. > > James. > > > -- View this message in context: http://old.nabble.com/UBI-Images-In-overo-2011.03-Git-Branch-Build-of-omap3-console-image-tp32034242p32240808.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: JamesAng <ang...@gm...> - 2011-08-12 02:00:21
|
Hi David, Thanks for the insight. :) So I can simply ignore the modules-2.6.34-r102-overo.tgz file that was generated as part of the bitbake image in the deploy directory? I'm still using the 2.6.34-caspapx kernel as I need the mt9v032 driver as gumstix's v2.6.39 has not go on to support the camera a.t.m. As such, where is the CONFIG_UBIFS_FS_DEBUG_MSG_LVL and what value should I set to mitigate the problem? I'll be working out a Plan B to use either Pinchart's kernel or Linux-Omap's kernel once I've the time to move to 2.6.39 or above with the camera supported, if by then gumstix's kernel still could not support the camera. Thanks in adv. James. David Abdurachmanov wrote: > > Hi, > > CONFIG_UBIFS_FS_DEBUG_MSG_LVL is removed starting 2.6.39 kernel, I think. > If you are using older kernel it still might be set to 3rd level. That was > causing problems for my implementation as I remember. You always can > change that in your kernel configuration. I would suggest using 2.6.39 + > UBIFS memory leak fix kernel images for now. > > tar.gz and ubi images contains identical files and directory structures. > BitBake is capable of preparing rootfs images in multiple file systems, > but their content is identical. > > -david > > > JamesAng wrote: >> >> >> sakoman wrote: >>> >>> On Sun, Jul 10, 2011 at 7:28 PM, Bob Cochran <bco...@ve...> >>> wrote: >>>> I Googled and found a great how-to for UBI images on Steve Sakoman's >>>> site: >>>> >>>> http://www.sakoman.com/OMAP/how-to-write-an-ubifs-rootfs-image-to-nand.html?utm_source%3Dfeedburner%26utm_medium%3Dtwitter%26utm_campaign%3DFeed:+BeagleBoard+%28BeagleBoard.org%29 >>> >>> Since Neil is providing a pre-made .ubi image you could use method two >>> in that article and just skip the first few steps that create the .ubi >>> image from a tarball. >>> >>> Basically you would just need to do the final ubiformat step. >>> >>> Steve >>> >> >> Hi Steve, >> >> I was reading through your guide to making an ubifs image from rootfs >> tarball and a question comes to my mind regarding the additional module's >> tarball. >> >> Should the module's tarball also be extracted to the same rootfs before >> calling mkfs and ubinize? >> Or is it that the module's tarball is already in the rootfs tarball? >> >> Secondly, David mentioned that having the UBIFS_DEBUG's MSG_LVL=3 enabled >> will consume up the space in the gumstix in no timee. >> >> >> David Abdurachmanov wrote: >>> >>> ... >>> There is one more change to the steps, UBIFS_DEBUG with MSG_LVL=3 is >>> enabled, which very much eats your CPU (writing syslog) and kills >>> Gumstix in several minutes with "out of space" problem. >>> >>> But, I must say, it so much better comparing to JFFS2. >>> >> >> What is the solution to this and which step(s) in your guide should I >> modify and where in the BB's image recipe should it be stated too so that >> it is part of making the ubifs image via bitbake? >> >> Thanks in adv. >> >> James. >> >> >> > > -- View this message in context: http://old.nabble.com/UBI-Images-In-overo-2011.03-Git-Branch-Build-of-omap3-console-image-tp32034242p32246721.html Sent from the Gumstix mailing list archive at Nabble.com. |