From: <cas...@gm...> - 2012-02-01 05:46:12
|
Hello James, Were you able to test your image? I am still relatively new to O.E. and Bitbake and trying to transition from the novice who has to ask for help for every problem, to the seasoned user who can solve the problems that arise independently. That being the case I have read both the O.E. and Bitbake manuals but I'm still at a lost when it comes to determining what your recommended fix does. Namely what does the Insane_skip command do, what do the various -es# tags mean and lastly how did you know these steps were needed to solve the problem. If you can spare the time I would greatly appreciate your feedback. Casey Sent from my Verizon Wireless BlackBerry -----Original Message----- From: JamesAng <ang...@gm...> Date: Tue, 31 Jan 2012 01:21:23 To: <gum...@li...> Reply-To: "General mailing list for gumstix users." <gum...@li...> Subject: Re: [Gumstix-users] Building Sakoman's GNOME-R13 image Hi Casey, Casey St.Fleur wrote > > Hello James, > > It turns out I needed to be more careful when I was following Theo's > previous recommendation. So first I copied the recipes from OE > powervr-drivers into Steve's powervr-drivers folder. Next I renamed > libgles-omap3_4.05.00.03.bb to __libgles-omap3_4.05.00.03.bb so > bitbake would use the older version of libgles since the newer one is > not found in the OE powervr-driver folder. That seem to solve the > problem. Just as aside I am using Ubuntu 10.04 32 bit and was making > Steve's console image, not sure if that makes a difference. > > Hope this helps, > Casey St.Fleur > Ok, I managed to successfully compile Steve's image without any error but YET TO TEST IT. 1) I modified and replaced the related recipes & files for libgles-omap3 and omap3_sgx_modules from git.angstrom-distribution.org. 2) Manually hack the GNU_HASH section of the libgles-omap3.inc file and reading the entire file and saw that there is this section of lines about GNU_HASH errors. I just duplicate 4 blocks of the same INSANE_SKIP_ lines and append -es3, -es5, -es6 and -es8 to each entry in each block. (This refers back to see 4 similar errors for each binary in the log) Don't ask me why some are "ldflags" while others are "ldflags dev-so". I would like to know the answer to this question too. (^^) #HACK! These are binaries, so we can't guarantee that LDFLAGS match :( INSANE_SKIP_${PN} = "ldflags dev-so" INSANE_SKIP_${PN}-blitwsegl = "ldflags" INSANE_SKIP_${PN}-flipwsegl = "ldflags" INSANE_SKIP_${PN}-frontwsegl = "ldflags" INSANE_SKIP_${PN}-linuxfbwsegl = "ldflags" INSANE_SKIP_${PN}-x11wsegl = "ldflags dev-so" INSANE_SKIP_${PN}-driwsegl = "ldflags dev-so" INSANE_SKIP_${PN}-tests = "ldflags" INSANE_SKIP_xserver-kdrive-powervrsgx = "ldflags" INSANE_SKIP_${PN}-es3 = "ldflags dev-so" INSANE_SKIP_${PN}-blitwsegl-es3 = "ldflags" INSANE_SKIP_${PN}-flipwsegl-es3 = "ldflags" INSANE_SKIP_${PN}-frontwsegl-es3 = "ldflags" INSANE_SKIP_${PN}-linuxfbwsegl-es3 = "ldflags" INSANE_SKIP_${PN}-x11wsegl-es3 = "ldflags dev-so" INSANE_SKIP_${PN}-driwsegl-es3 = "ldflags dev-so" INSANE_SKIP_${PN}-tests-es3 = "ldflags" INSANE_SKIP_xserver-kdrive-powervrsgx-es3 = "ldflags" INSANE_SKIP_${PN}-es5 = "ldflags dev-so" INSANE_SKIP_${PN}-blitwsegl-es5 = "ldflags" INSANE_SKIP_${PN}-flipwsegl-es5 = "ldflags" INSANE_SKIP_${PN}-frontwsegl-es5 = "ldflags" INSANE_SKIP_${PN}-linuxfbwsegl-es5 = "ldflags" INSANE_SKIP_${PN}-x11wsegl-es5 = "ldflags dev-so" INSANE_SKIP_${PN}-driwsegl-es5 = "ldflags dev-so" INSANE_SKIP_${PN}-tests-es5 = "ldflags" INSANE_SKIP_xserver-kdrive-powervrsgx-es5 = "ldflags" INSANE_SKIP_${PN}-es6 = "ldflags dev-so" INSANE_SKIP_${PN}-blitwsegl-es6 = "ldflags" INSANE_SKIP_${PN}-flipwsegl-es6 = "ldflags" INSANE_SKIP_${PN}-frontwsegl-es6 = "ldflags" INSANE_SKIP_${PN}-linuxfbwsegl-es6 = "ldflags" INSANE_SKIP_${PN}-x11wsegl-es6 = "ldflags dev-so" INSANE_SKIP_${PN}-driwsegl-es6 = "ldflags dev-so" INSANE_SKIP_${PN}-tests-es6 = "ldflags" INSANE_SKIP_xserver-kdrive-powervrsgx-es6 = "ldflags" INSANE_SKIP_${PN}-es8 = "ldflags dev-so" INSANE_SKIP_${PN}-blitwsegl-es8 = "ldflags" INSANE_SKIP_${PN}-flipwsegl-es8 = "ldflags" INSANE_SKIP_${PN}-frontwsegl-es8 = "ldflags" INSANE_SKIP_${PN}-linuxfbwsegl-es8 = "ldflags" INSANE_SKIP_${PN}-x11wsegl-es8 = "ldflags dev-so" INSANE_SKIP_${PN}-driwsegl-es8 = "ldflags dev-so" INSANE_SKIP_${PN}-tests-es8 = "ldflags" INSANE_SKIP_xserver-kdrive-powervrsgx-es8 = "ldflags" 3) After which, I cleaned the affected files "bitbake -c clean libgles-omap3 virtual/libx11 libxau libxdmcp omap3-sgx-modules virtual/kernel" 4) Finally, bitbake the entire image "bitbake -k sakoman-gnome-image" I'll try booting the new image and see if it works next day. Cross my fingers tight! James. -- View this message in context: http://gumstix.8.n6.nabble.com/Building-Sakoman-s-GNOME-R13-image-tp642656p4352892.html Sent from the Gumstix mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: JamesAng <ang...@gm...> - 2012-02-02 02:22:16
|
Hi Casey, Casey St.Fleur wrote > > Hello James, > > Were you able to test your image? > Nope, planning to do it over the next few day as I've other tasks at hand. Casey St.Fleur wrote > > I am still relatively new to O.E. and Bitbake and trying to transition > from the novice who has to ask for help for every problem, to the seasoned > user who can solve the problems that arise independently. > I'm walking the same road as you are! (^^) Casey St.Fleur wrote > > That being the case I have read both the O.E. and Bitbake manuals but I'm > still at a lost when it comes to determining what your recommended fix > does. Namely what does the Insane_skip command do, > I tried searching for more details to these parameters and examples/case studies but it's limited and sparse.. I would love to understand more about these too if you found any materials to share with me. Casey St.Fleur wrote > > what do the various -es# tags mean and lastly how did you know these steps > were needed to solve the problem. If you can spare the time I would > greatly appreciate your feedback. > I looked at the error log file and comb through into each recipes to see if there are anything that causes it. I just happen to see a section of lines in the .inc file that said something about GNU_HASH hack and the insane_skip* parameters. X-ref to the error message and the diff-file against the previous version, it affected those -es* files and I just duplicated a section of it for each of these -es* file in the insane_skip parameter. More of a logical try-and-error method. I can't give a correct answer as I'm still learning too. Maybe other oe-developers can share some insight to this. BTW, the compilation was done on a Ubuntu 10.10 32-bit VM machine as I'm getting other nonsense errors on Ubuntu 11.XX 32 & 64 bits. James. -- View this message in context: http://gumstix.8.n6.nabble.com/Building-Sakoman-s-GNOME-R13-image-tp642656p4357951.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Casey St.F. <cas...@gm...> - 2012-01-30 15:21:56
|
Hello James, It turns out I needed to be more careful when I was following Theo's previous recommendation. So first I copied the recipes from OE powervr-drivers into Steve's powervr-drivers folder. Next I renamed libgles-omap3_4.05.00.03.bb to __libgles-omap3_4.05.00.03.bb so bitbake would use the older version of libgles since the newer one is not found in the OE powervr-driver folder. That seem to solve the problem. Just as aside I am using Ubuntu 10.04 32 bit and was making Steve's console image, not sure if that makes a difference. Hope this helps, Casey St.Fleur On Mon, Jan 30, 2012 at 8:58 AM, Nader Rahimizad <na...@ra...> wrote: > Don't know. I gave up and went with the other distribution for oe-core > > -- > View this message in context: http://gumstix.8.n6.nabble.com/Building-Sakoman-s-GNOME-R13-image-tp642656p4350713.html > Sent from the Gumstix mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Try before you buy = See our experts in action! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-dev2 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: JamesAng <ang...@gm...> - 2012-01-31 09:21:34
|
Hi Casey, Casey St.Fleur wrote > > Hello James, > > It turns out I needed to be more careful when I was following Theo's > previous recommendation. So first I copied the recipes from OE > powervr-drivers into Steve's powervr-drivers folder. Next I renamed > libgles-omap3_4.05.00.03.bb to __libgles-omap3_4.05.00.03.bb so > bitbake would use the older version of libgles since the newer one is > not found in the OE powervr-driver folder. That seem to solve the > problem. Just as aside I am using Ubuntu 10.04 32 bit and was making > Steve's console image, not sure if that makes a difference. > > Hope this helps, > Casey St.Fleur > Ok, I managed to successfully compile Steve's image without any error but YET TO TEST IT. 1) I modified and replaced the related recipes & files for libgles-omap3 and omap3_sgx_modules from git.angstrom-distribution.org. 2) Manually hack the GNU_HASH section of the libgles-omap3.inc file and reading the entire file and saw that there is this section of lines about GNU_HASH errors. I just duplicate 4 blocks of the same INSANE_SKIP_ lines and append -es3, -es5, -es6 and -es8 to each entry in each block. (This refers back to see 4 similar errors for each binary in the log) Don't ask me why some are "ldflags" while others are "ldflags dev-so". I would like to know the answer to this question too. (^^) #HACK! These are binaries, so we can't guarantee that LDFLAGS match :( INSANE_SKIP_${PN} = "ldflags dev-so" INSANE_SKIP_${PN}-blitwsegl = "ldflags" INSANE_SKIP_${PN}-flipwsegl = "ldflags" INSANE_SKIP_${PN}-frontwsegl = "ldflags" INSANE_SKIP_${PN}-linuxfbwsegl = "ldflags" INSANE_SKIP_${PN}-x11wsegl = "ldflags dev-so" INSANE_SKIP_${PN}-driwsegl = "ldflags dev-so" INSANE_SKIP_${PN}-tests = "ldflags" INSANE_SKIP_xserver-kdrive-powervrsgx = "ldflags" INSANE_SKIP_${PN}-es3 = "ldflags dev-so" INSANE_SKIP_${PN}-blitwsegl-es3 = "ldflags" INSANE_SKIP_${PN}-flipwsegl-es3 = "ldflags" INSANE_SKIP_${PN}-frontwsegl-es3 = "ldflags" INSANE_SKIP_${PN}-linuxfbwsegl-es3 = "ldflags" INSANE_SKIP_${PN}-x11wsegl-es3 = "ldflags dev-so" INSANE_SKIP_${PN}-driwsegl-es3 = "ldflags dev-so" INSANE_SKIP_${PN}-tests-es3 = "ldflags" INSANE_SKIP_xserver-kdrive-powervrsgx-es3 = "ldflags" INSANE_SKIP_${PN}-es5 = "ldflags dev-so" INSANE_SKIP_${PN}-blitwsegl-es5 = "ldflags" INSANE_SKIP_${PN}-flipwsegl-es5 = "ldflags" INSANE_SKIP_${PN}-frontwsegl-es5 = "ldflags" INSANE_SKIP_${PN}-linuxfbwsegl-es5 = "ldflags" INSANE_SKIP_${PN}-x11wsegl-es5 = "ldflags dev-so" INSANE_SKIP_${PN}-driwsegl-es5 = "ldflags dev-so" INSANE_SKIP_${PN}-tests-es5 = "ldflags" INSANE_SKIP_xserver-kdrive-powervrsgx-es5 = "ldflags" INSANE_SKIP_${PN}-es6 = "ldflags dev-so" INSANE_SKIP_${PN}-blitwsegl-es6 = "ldflags" INSANE_SKIP_${PN}-flipwsegl-es6 = "ldflags" INSANE_SKIP_${PN}-frontwsegl-es6 = "ldflags" INSANE_SKIP_${PN}-linuxfbwsegl-es6 = "ldflags" INSANE_SKIP_${PN}-x11wsegl-es6 = "ldflags dev-so" INSANE_SKIP_${PN}-driwsegl-es6 = "ldflags dev-so" INSANE_SKIP_${PN}-tests-es6 = "ldflags" INSANE_SKIP_xserver-kdrive-powervrsgx-es6 = "ldflags" INSANE_SKIP_${PN}-es8 = "ldflags dev-so" INSANE_SKIP_${PN}-blitwsegl-es8 = "ldflags" INSANE_SKIP_${PN}-flipwsegl-es8 = "ldflags" INSANE_SKIP_${PN}-frontwsegl-es8 = "ldflags" INSANE_SKIP_${PN}-linuxfbwsegl-es8 = "ldflags" INSANE_SKIP_${PN}-x11wsegl-es8 = "ldflags dev-so" INSANE_SKIP_${PN}-driwsegl-es8 = "ldflags dev-so" INSANE_SKIP_${PN}-tests-es8 = "ldflags" INSANE_SKIP_xserver-kdrive-powervrsgx-es8 = "ldflags" 3) After which, I cleaned the affected files "bitbake -c clean libgles-omap3 virtual/libx11 libxau libxdmcp omap3-sgx-modules virtual/kernel" 4) Finally, bitbake the entire image "bitbake -k sakoman-gnome-image" I'll try booting the new image and see if it works next day. Cross my fingers tight! James. -- View this message in context: http://gumstix.8.n6.nabble.com/Building-Sakoman-s-GNOME-R13-image-tp642656p4352892.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Theodore Morichau-B. <t.b...@gm...> - 2012-01-30 10:24:32
|
Hey guys, just a quick thought over the top of my head. Sometimes it seems bitbake has some issues with parallel builds (PARALLEL_MAKE="jX"). Usually when there's some files not found during compile like in this case, I rerun the recipe without any parallel option and it goes through correctly (you can then reenable the parallel build to continue with the rest of the image). Hope this helps, Theo 2012/1/29 JamesAng <ang...@gm...> > Hi Casey, > > Casey St.Fleur wrote > > > > Hello again, > > > > So my installation worked for a several minutes before I received > > another error. > > below is what I believe to be the problem but attached is the actual > > log file. Just so that everyone knows, I copied the powervr-drivers > > recipes from the gumstix-oe to Sakoman powervr-drivers recipe folder. > > Secondly I did a bitbake clean on the three dependencies of > > libgles-omap3, virtual/libx11, libxau, and libxdmcp . > > > > cp: cannot stat > > > `/home/uav/overo-le/tmp/work/armv7a-angstrom-linux-gnueabi/libgles-omap3-4.05.00.03-r16/Graphics_SDK_4_05_00_03/gfx_rel_es2.x/lib*1.6.16.4117': > > No such file or directory > > > > Casey > > > > Any luck progressing from there? > > I tried re-building from scratch using Ubuntu 10.10 32-bit Host on a VM but > still gets the same errors. > > I wonder how Steve managed to get pass all that to complete his build in > his > machine.. > > James. > > -- > View this message in context: > http://gumstix.8.n6.nabble.com/Building-Sakoman-s-GNOME-R13-image-tp642656p4349910.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Try before you buy = See our experts in action! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-dev2 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Nader R. <na...@ra...> - 2012-01-30 13:58:26
|
Don't know. I gave up and went with the other distribution for oe-core -- View this message in context: http://gumstix.8.n6.nabble.com/Building-Sakoman-s-GNOME-R13-image-tp642656p4350713.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: JamesAng <ang...@gm...> - 2012-01-30 07:48:19
|
Hi Casey, Casey St.Fleur wrote > > Hello again, > > So my installation worked for a several minutes before I received > another error. > below is what I believe to be the problem but attached is the actual > log file. Just so that everyone knows, I copied the powervr-drivers > recipes from the gumstix-oe to Sakoman powervr-drivers recipe folder. > Secondly I did a bitbake clean on the three dependencies of > libgles-omap3, virtual/libx11, libxau, and libxdmcp . > > cp: cannot stat > `/home/uav/overo-le/tmp/work/armv7a-angstrom-linux-gnueabi/libgles-omap3-4.05.00.03-r16/Graphics_SDK_4_05_00_03/gfx_rel_es2.x/lib*1.6.16.4117': > No such file or directory > > Casey > Any luck progressing from there? I tried re-building from scratch using Ubuntu 10.10 32-bit Host on a VM but still gets the same errors. I wonder how Steve managed to get pass all that to complete his build in his machine.. James. -- View this message in context: http://gumstix.8.n6.nabble.com/Building-Sakoman-s-GNOME-R13-image-tp642656p4349910.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dan N. <Dan...@ro...> - 2012-01-30 08:00:41
|
I'm trying to estimate maximum power consumption for the Overo FE COM. I've found TI's power spreadsheet for the OMAP3530. I've configured everything to maximum and come up with 2536 mW. I have to admit that I'm not sure on all the settings in the spreadsheet. As for the rest of the COM, Bluetooth? Wifi? Can someone give me these figures? And for RAM and FLASH? Anything else? Thanks Dan |
From: Neil M. <ne...@gu...> - 2011-11-29 00:14:01
|
Hi James, > With your new v3.0 kernel, the Caspa's wiki is no longer relevant. You are right.. the instructions provided on the wiki pertain to the 2.6.34 kernel only. The latest images have a working driver but, last I checked, no user space support other than yavta. If you find any information that might help other users, feel free to add to the wiki. - Neil |
From: James <ang...@gm...> - 2011-11-29 01:53:19
|
Hi Neil, On Tue, Nov 29, 2011 at 8:13 AM, Neil MacMunn <ne...@gu...> wrote: > Hi James, > > > With your new v3.0 kernel, the Caspa's wiki is no longer relevant. > > You are right.. the instructions provided on the wiki pertain to the > 2.6.34 kernel only. > > The latest images have a working driver but, last I checked, no user > space support other than yavta. If you find any information that might > help other users, feel free to add to the wiki. > > - > Neil > > Sure do! There is another thread in the forum regarding some success via modifying the v4l2src. I've yet to test it out. Currently, there is a lot of omap3isp & media fixes submitted and I wonder where to get hold of the (near) up-to-date kernel? thinking to use linux-omap recipe but it is stuck at v2.6.39 in OE with a bunch of patches. This is because I encountered some stack error on omap3isp when using MPlayer to try out the streaming capture using Steve's kernel. Want to verify if the same error appears on the (near) up-to-date kernel, if possible. What will be your view? -- Regards, James |