From: <cod...@gm...> - 2009-12-23 19:34:40
|
Hello, I've recently just gotten started in the world of OpenEmbedded and Gumstix Overo. I followed the "setting up a build environment" instructions on gumstix.net's documentation section, which created a bitbake environment with an org.openembedded.dev, user.collection, and other directories under overo-oe. I'm able to create my own recipes under user.collection/recipes and use that to create .ipk packages to install on Gumstix. However, I'm running into issues when I try to run bitbake on things like, say, u-boot. I get error messages saying it could not find ${GUMSTIXTOP}/com.gumstix.collection/... I don't even have a ${GUMSTIXTOP}, or com.gumstix.collection in my configuration. Is there more to setting up a build environment than just the 'setting up a build environment' section in the documentation? I saw a wiki page about buildroot, but that seemed like a completely different environment, separate from what goes into overo-oe. What am I missing? |
From: Nathan T. <nk...@gm...> - 2009-12-23 20:25:55
|
Check the steps again, I'm guessing you missed this one: $ cat ~/overo-oe/build/profile >> ~/.bashrc taken from this site: http://www.gumstix.net/Setup-and-Programming/view/Overo-Setup-and-Programming/Setting-up-a-build-environment/111.html You'll also need to close and reopen the terminal for those changes to take effect On Wed, Dec 23, 2009 at 2:27 PM, <cod...@gm...> wrote: > Hello, > > I've recently just gotten started in the world of OpenEmbedded and Gumstix > Overo. I followed the "setting up a build environment" instructions on > gumstix.net's documentation section, which created a bitbake environment > with an org.openembedded.dev, user.collection, and other directories under > overo-oe. I'm able to create my own recipes under user.collection/recipes > and use that to create .ipk packages to install on Gumstix. > > However, I'm running into issues when I try to run bitbake on things like, > say, u-boot. I get error messages saying it could not find > ${GUMSTIXTOP}/com.gumstix.collection/... I don't even have a ${GUMSTIXTOP}, > or com.gumstix.collection in my configuration. > > Is there more to setting up a build environment than just the 'setting up a > build environment' section in the documentation? I saw a wiki page about > buildroot, but that seemed like a completely different environment, separate > from what goes into overo-oe. > > What am I missing? > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Sufi, A. <asufi@Sarnoff.com> - 2009-12-23 20:55:50
|
Hi I updated my local repository yesterday by issuing a git pull and since then the desktop build shows a black screen following the angstrom status bar... Any hints? |
From: Steve S. <sa...@gm...> - 2009-12-23 21:27:10
|
On Wed, Dec 23, 2009 at 12:55 PM, Sufi, Azhar <as...@sa...> wrote: > I updated my local repository yesterday by issuing a git pull and since then > the desktop build shows a black screen following the angstrom status bar… > > Any hints? Yesterday's merge with upstream OE seems to have introduced a bug that prevents X11 from starting properly. I'm trying to track down the culprit and will push a fix as soon as I can find one! Sorry I didn't catch this before pushing the changes to the Overo branch :-( Steve > > > > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Sufi, A. <asufi@Sarnoff.com> - 2009-12-23 23:02:04
|
Hi Steve: Thanks. Is there a way to pull back to the 'working version' somehow? Thanks Azhar -----Original Message----- From: Steve Sakoman [mailto:sa...@gm...] Sent: Wednesday, December 23, 2009 4:27 PM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] black screen On Wed, Dec 23, 2009 at 12:55 PM, Sufi, Azhar <as...@sa...> wrote: > I updated my local repository yesterday by issuing a git pull and since then > the desktop build shows a black screen following the angstrom status bar... > > Any hints? Yesterday's merge with upstream OE seems to have introduced a bug that prevents X11 from starting properly. I'm trying to track down the culprit and will push a fix as soon as I can find one! Sorry I didn't catch this before pushing the changes to the Overo branch :-( Steve > > > > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Steve S. <sa...@gm...> - 2009-12-23 23:19:16
|
On Wed, Dec 23, 2009 at 3:01 PM, Sufi, Azhar <as...@sa...> wrote: > Hi Steve: > > Thanks. Is there a way to pull back to the 'working version' somehow? I just pushed some fixes for xorg. I have a build in progress to verify them, but you can do a git pull now to pick them up. If you want to go back in time -- do a git log to find the commit prior to yesterday's batch of xorg changes and then do a git checkout <commit id> I suspect, though, that just just doing a git pull will get you back in business. Steve > Thanks > Azhar > > > > -----Original Message----- > From: Steve Sakoman [mailto:sa...@gm...] > Sent: Wednesday, December 23, 2009 4:27 PM > To: General mailing list for gumstix users. > Subject: Re: [Gumstix-users] black screen > > On Wed, Dec 23, 2009 at 12:55 PM, Sufi, Azhar <as...@sa...> wrote: > >> I updated my local repository yesterday by issuing a git pull and since then >> the desktop build shows a black screen following the angstrom status bar... >> >> Any hints? > > Yesterday's merge with upstream OE seems to have introduced a bug that > prevents X11 from starting properly. > > I'm trying to track down the culprit and will push a fix as soon as I > can find one! > > Sorry I didn't catch this before pushing the changes to the Overo branch :-( > > Steve > >> >> >> >> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Sufi, A. <asufi@Sarnoff.com> - 2009-12-24 02:00:22
|
Hi Steve: I did a git pull and rebuilt the code but am still getting the black screen... -----Original Message----- From: Steve Sakoman [mailto:sa...@gm...] Sent: Wednesday, December 23, 2009 6:19 PM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] black screen On Wed, Dec 23, 2009 at 3:01 PM, Sufi, Azhar <as...@sa...> wrote: > Hi Steve: > > Thanks. Is there a way to pull back to the 'working version' somehow? I just pushed some fixes for xorg. I have a build in progress to verify them, but you can do a git pull now to pick them up. If you want to go back in time -- do a git log to find the commit prior to yesterday's batch of xorg changes and then do a git checkout <commit id> I suspect, though, that just just doing a git pull will get you back in business. Steve > Thanks > Azhar > > > > -----Original Message----- > From: Steve Sakoman [mailto:sa...@gm...] > Sent: Wednesday, December 23, 2009 4:27 PM > To: General mailing list for gumstix users. > Subject: Re: [Gumstix-users] black screen > > On Wed, Dec 23, 2009 at 12:55 PM, Sufi, Azhar <as...@sa...> wrote: > >> I updated my local repository yesterday by issuing a git pull and since then >> the desktop build shows a black screen following the angstrom status bar... >> >> Any hints? > > Yesterday's merge with upstream OE seems to have introduced a bug that > prevents X11 from starting properly. > > I'm trying to track down the culprit and will push a fix as soon as I > can find one! > > Sorry I didn't catch this before pushing the changes to the Overo branch :-( > > Steve > >> >> >> >> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Steve S. <sa...@gm...> - 2009-12-24 16:05:06
|
On Wed, Dec 23, 2009 at 6:00 PM, Sufi, Azhar <as...@sa...> wrote: > Hi Steve: > > I did a git pull and rebuilt the code but am still getting the black screen... I pushed a couple more changes. My test build worked. Hopefully yours will too! Steve > > > -----Original Message----- > From: Steve Sakoman [mailto:sa...@gm...] > Sent: Wednesday, December 23, 2009 6:19 PM > To: General mailing list for gumstix users. > Subject: Re: [Gumstix-users] black screen > > On Wed, Dec 23, 2009 at 3:01 PM, Sufi, Azhar <as...@sa...> wrote: >> Hi Steve: >> >> Thanks. Is there a way to pull back to the 'working version' somehow? > > I just pushed some fixes for xorg. I have a build in progress to > verify them, but you can do a git pull now to pick them up. > > If you want to go back in time -- do a git log to find the commit > prior to yesterday's batch of xorg changes and then do a git checkout > <commit id> > > I suspect, though, that just just doing a git pull will get you back > in business. > > Steve > > >> Thanks >> Azhar >> >> >> >> -----Original Message----- >> From: Steve Sakoman [mailto:sa...@gm...] >> Sent: Wednesday, December 23, 2009 4:27 PM >> To: General mailing list for gumstix users. >> Subject: Re: [Gumstix-users] black screen >> >> On Wed, Dec 23, 2009 at 12:55 PM, Sufi, Azhar <as...@sa...> wrote: >> >>> I updated my local repository yesterday by issuing a git pull and since then >>> the desktop build shows a black screen following the angstrom status bar... >>> >>> Any hints? >> >> Yesterday's merge with upstream OE seems to have introduced a bug that >> prevents X11 from starting properly. >> >> I'm trying to track down the culprit and will push a fix as soon as I >> can find one! >> >> Sorry I didn't catch this before pushing the changes to the Overo branch :-( >> >> Steve >> >>> >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.Net email is sponsored by the Verizon Developer Community >>> Take advantage of Verizon's best-in-class app development support >>> A streamlined, 14 day to market process makes app distribution fast and easy >>> Join now and get one step closer to millions of Verizon customers >>> http://p.sf.net/sfu/verizon-dev2dev >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Steve S. <sa...@gm...> - 2009-12-24 03:23:44
|
On Wed, Dec 23, 2009 at 6:00 PM, Sufi, Azhar <as...@sa...> wrote: > Hi Steve: > > I did a git pull and rebuilt the code but am still getting the black screen... I haven't had a chance to test my build yet. The previous build was failing with this error: /usr/bin/X: symbol lookup error: /usr/lib/xorg/modules/drivers/omapfb_drv.so: undefined symbol: LoaderRefSymLists And this commit attempts to fix that issue: http://www.sakoman.net/cgi-bin/gitweb.cgi?p=openembedded.git;a=commitdiff;h=ddcd0de3398b85cfedb959ca6d4e21e1cf6d6e18 Are you getting a different error? Steve > > > -----Original Message----- > From: Steve Sakoman [mailto:sa...@gm...] > Sent: Wednesday, December 23, 2009 6:19 PM > To: General mailing list for gumstix users. > Subject: Re: [Gumstix-users] black screen > > On Wed, Dec 23, 2009 at 3:01 PM, Sufi, Azhar <as...@sa...> wrote: >> Hi Steve: >> >> Thanks. Is there a way to pull back to the 'working version' somehow? > > I just pushed some fixes for xorg. I have a build in progress to > verify them, but you can do a git pull now to pick them up. > > If you want to go back in time -- do a git log to find the commit > prior to yesterday's batch of xorg changes and then do a git checkout > <commit id> > > I suspect, though, that just just doing a git pull will get you back > in business. > > Steve > > >> Thanks >> Azhar >> >> >> >> -----Original Message----- >> From: Steve Sakoman [mailto:sa...@gm...] >> Sent: Wednesday, December 23, 2009 4:27 PM >> To: General mailing list for gumstix users. >> Subject: Re: [Gumstix-users] black screen >> >> On Wed, Dec 23, 2009 at 12:55 PM, Sufi, Azhar <as...@sa...> wrote: >> >>> I updated my local repository yesterday by issuing a git pull and since then >>> the desktop build shows a black screen following the angstrom status bar... >>> >>> Any hints? >> >> Yesterday's merge with upstream OE seems to have introduced a bug that >> prevents X11 from starting properly. >> >> I'm trying to track down the culprit and will push a fix as soon as I >> can find one! >> >> Sorry I didn't catch this before pushing the changes to the Overo branch :-( >> >> Steve >> >>> >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.Net email is sponsored by the Verizon Developer Community >>> Take advantage of Verizon's best-in-class app development support >>> A streamlined, 14 day to market process makes app distribution fast and easy >>> Join now and get one step closer to millions of Verizon customers >>> http://p.sf.net/sfu/verizon-dev2dev >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Sufi, A. <asufi@Sarnoff.com> - 2009-12-24 03:30:35
|
OMAP3530-GP ES3.1, CPU-OPP2 L3-165MHz Gumstix Overo board + LPDDR/NAND I2C: ready DRAM: 256 MB NAND: 256 MiB *** Warning - bad CRC or NAND, using default environment In: serial Out: serial Err: serial Die ID #4b1200040000000004035c141800f005 Net: smc911x-0 Hit any key to stop autoboot: 0 mmc1 is available reading boot.scr ** Unable to read "boot.scr" from mmc 0:1 ** reading uImage 2725324 bytes read Booting from mmc ... ## Booting kernel from Legacy Image at 82000000 ... Image Name: Angstrom/2.6.29/overo Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2725260 Bytes = 2.6 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux............................................................. ................................................................................ ....................................... done, booting the kernel. Linux version 2.6.29-omap1 (asufi@asufi-laptop) (gcc version 4.3.3 (GCC) ) #1 Sa t Dec 12 23:32:16 EST 2009 CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c5387f CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: Gumstix Overo omapfb_early_vram, 12582912, 0x0 Memory policy: ECC disabled, Data cache writeback OMAP3430 ES3.1 SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000 Reserving 12582912 bytes SDRAM for VRAM Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024 Kernel command line: console=ttyS2,115200n8 vram=12M omapfb.mode=dvi:1024x768MR- 16@60 omapfb.debug=y omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait Clocking rate (Crystal/DPLL/ARM core): 26.0/331/500 MHz GPMC revision 5.0 IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts Total of 96 interrupts on 1 active controller OMAP34xx GPIO hardware version 2.5 PID hash table entries: 1024 (order: 10, 4096 bytes) OMAP clockevent source: GPTIMER1 at 32768 Hz Console: colour dummy device 80x30 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 128MB 128MB = 256MB total Memory: 241408KB available (4472K code, 532K data, 940K init) Calibrating delay loop... 499.92 BogoMIPS (lpj=1949696) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok net_namespace: 764 bytes regulator: core version 0.5 NET: Registered protocol family 16 Found NAND on CS0 Registering NAND on CS0 OMAP DMA hardware revision 4.0 bio: create slab <bio-0> at 0 OMAP DSS rev 2.0 OMAP DISPC rev 3.0 OMAP VENC rev 2 i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz twl4030: PIH (irq 7) chaining IRQs 368..375 twl4030: power (irq 373) chaining IRQs 376..383 twl4030: gpio (irq 368) chaining IRQs 384..401 regulator: VMMC1: 1850 <--> 3150 mV normal standby regulator: VUSB1V5: 1500 <--> 0 mV normal standby regulator: VUSB1V8: 1800 <--> 0 mV normal standby regulator: VUSB3V1: 3100 <--> 0 mV normal standby i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz SCSI subsystem initialized twl4030_usb twl4030_usb: Initialized TWL4030 USB module usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb Bluetooth: Core ver 2.14 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized cfg80211: Using static regulatory domain info cfg80211: Regulatory domain: US (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm) (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm) cfg80211: Calling CRDA for country: US musb_hdrc: version 6.0, musb-dma, host, debug=0 musb_hdrc: USB Host mode controller at d80ab000 using DMA, IRQ 92 musb_hdrc musb_hdrc: MUSB HDRC host driver musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1 usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: MUSB HDRC host driver usb usb1: Manufacturer: Linux 2.6.29-omap1 musb-hcd usb usb1: SerialNumber: musb_hdrc usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 4, 65536 bytes) TCP bind hash table entries: 8192 (order: 3, 32768 bytes) TCP: Hash tables configured (established 8192 bind 8192) TCP reno registered NET: Registered protocol family 1 VFS: Disk quotas dquot_6.5.2 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) JFFS2 version 2.2. (NAND) (SUMMARY) 2001-2006 Red Hat, Inc. msgmni has been set to 471 alg: No test for stdrng (krng) io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654 serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654 serial8250.0: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654 console [ttyS2] enabled brd: module loaded loop: module loaded usbcore: registered new interface driver asix usbcore: registered new interface driver cdc_ether i2c /dev entries driver Driver 'sd' needs updating - please use bus_type methods omap2-nand driver initializing NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB 1,8V 16-bi t) cmdlinepart partition parsing not available Creating 5 MTD partitions on "omap2-nand": 0x000000000000-0x000000080000 : "xloader" 0x000000080000-0x000000240000 : "uboot" 0x000000240000-0x000000280000 : "uboot environment" 0x000000280000-0x000000680000 : "linux" 0x000000680000-0x000010000000 : "rootfs" ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-omap ehci-omap.0: OMAP-EHCI Host Controller ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 2 ehci-omap ehci-omap.0: irq 77, io mem 0x48064800 ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00 usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb2: Product: OMAP-EHCI Host Controller usb usb2: Manufacturer: Linux 2.6.29-omap1 ehci_hcd usb usb2: SerialNumber: ehci-omap.0 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 3 ports detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. udc: OMAP UDC driver, version: 4 October 2004 (iso) (dma) mice: PS/2 mouse device common for all mice twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0 twl4030_rtc twl4030_rtc: Power up reset detected. twl4030_rtc twl4030_rtc: Enabling TWL4030-RTC. OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec Bluetooth: HCI UART driver ver 2.2 Bluetooth: HCI H4 protocol initialized Bluetooth: HCI BCSP protocol initialized Bluetooth: Broadcom Blutonium firmware driver ver 1.2 usbcore: registered new interface driver bcm203x Bluetooth: Digianswer Bluetooth USB driver ver 0.10 usbcore: registered new interface driver bpa10x mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock regulator: Unable to get requested regulator: vmmc_aux mmci-omap-hs mmci-omap-hs.1: Failed to get debounce clock regulator: Unable to get requested regulator: vmmc usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver Advanced Linux Sound Architecture Driver Version 1.0.18a. usbcore: registered new interface driver snd-usb-audio No device for DAI twl4030 No device for DAI omap-mcbsp-dai-0 No device for DAI omap-mcbsp-dai-1 No device for DAI omap-mcbsp-dai-2 No device for DAI omap-mcbsp-dai-3 No device for DAI omap-mcbsp-dai-4 overo SoC init TWL4030 Audio Codec init asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok ALSA device list: #0: overo (twl4030) oprofile: using arm/armv7 TCP cubic registered NET: Registered protocol family 17 NET: Registered protocol family 15 Bluetooth: L2CAP ver 2.11 Bluetooth: L2CAP socket layer initialized Bluetooth: SCO (Voice Link) ver 0.6 Bluetooth: SCO socket layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM ver 1.10 Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast Bluetooth: HIDP (Human Interface Emulation) ver 1.2 RPC: Registered udp transport module. RPC: Registered tcp transport module. ThumbEE CPU extension supported. Power Management for TI OMAP3. SmartReflex driver initialized VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1 mmc0: mmc_rescan - card ocr from io_op=0x00000000, err = -110 fbcvt: 1024x768@60: CVT Name - .786M3-R Console: switching to colour frame buffer device 128x48 clock: clksel_round_rate_div: dpll4_m4_ck target_rate 86400000 clock: new_div = 5, new_rate = 86400000 twl4030_rtc twl4030_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684 800) Waiting for root device /dev/mmcblk0p2... mmc0: host does not support reading read-only switch. assuming write-enable. mmc0: new high speed SDHC card at address 0001 mmcblk0: mmc0:0001 00000 7.60 GiB mmcblk0: p1 p2 mmc1: mmc_rescan - card ocr from io_op=0x90ff8000, err = 0 mmc1: new SDIO card at address 0001 kjournald starting. Commit interval 5 seconds EXT3-fs warning: mounting fs with errors, running e2fsck is recommended EXT3 FS on mmcblk0p2, internal journal EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) on device 179:2. Freeing init memory: 940K INIT: version 2.86 booting Please wait: booting... Starting udev udev: starting version 141 ads7846 spi1.0: touchscreen, irq 274 Remounting root file system... ads7846 spi1.0: no device detected, test read result was 0x00000000 lib80211: common routines for IEEE802.11 drivers libertas_sdio: Libertas SDIO driver libertas_sdio: Copyright Pierre Ossman libertas_sdio mmc1:0001:1: firmware: requesting sd8686_helper.bin NET: Registered protocol family 10 libertas_sdio mmc1:0001:1: firmware: requesting sd8686.bin Unknown HZ value! (68) Assume 100. ALSA: Restoring mixer settings... Configuring network interfaces... /usr/sbin/alsactl: parse:1639: Unable to open file '/usr/share/alsa/init/00main': No such file or directory /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #1 (No su ch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #10 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #11 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #12 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #20 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #21 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #22 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #23 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #24 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #25 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #26 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #27 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #28 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #31 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #32 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #33 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #35 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #37 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #38 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info libertas: 00:19:88:11 :e4:65, fw 9.70.3p24, cap 0x00000303 for control #39 (No such file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #40 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failedeth0 (libertas_sdio): not using net_d evice_ops yet to obtain info for control #41 (No such file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #42 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #43 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #44 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #45 (No s uch file or directory) /uslibertas: PREP_CMD: command 0x00a3 failed: 2 r/sbin/alsactl: set_control:1256: failed to obtain info for control #46 (No such file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info libertas: PREP_CMD: c ommand 0x00a3 failed: 2 for control #47 (No such file orlibertas: eth0: Marvell WLAN 802.11 adapter directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #48 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #49 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #50 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #51 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #52 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #53 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #54 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #55 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #56 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #57 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #58 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #59 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #60 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #61 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #62 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #63 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #64 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #65 udev: renamed network interface eth0 to wlan0 (No such file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #66 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #67 (No s uch file or directory) /usr/sbin/alsactl: set_control:1256: failed to obtain info for control #68 (No s uch file or directory) done. Starting portmap daemon: portmap. Unknown HZ value! (73) Assume 100. net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 Wed Dec 23 19:06:00 GMT 2009 Turning echo off on /dev/ttyS1 INIT: Entering runlevel: 5 Starting system message bus: dbus. Starting Hardware abstraction layer hald Starting OpenBSD Secure Shell server: sshd done. Starting advanced power management daemon: No APM support in kernel (failed.) Starting ntpd: done Starting Samba: smbd nmbd. Starting syslogd/klogd: done * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon [ ok ] Starting Bluetooth subsystem: CSR build ID 0x0C-0x5C Device setup complete ttyS1 bluetoothd hid2hci rfcomm. Waiting for connection on channel 1 Starting Network connection manager daemon: NetworkManager. Unknown HZ value! (75) Assume 100. /etc/rc5.d/S81cups: line 232: echo_success: not found cups: started scheduler. Starting GPE display manager: gpe-dm .-------. | | .-. | | |-----.-----.-----.| | .----..-----.-----. | | | __ | ---'| '--.| .-'| | | | | | | | |--- || --'| | | ' | | | | '---'---'--'--'--. |-----''----''--' '-----'-'-'-' -' | '---' The Angstrom Distribution overo ttyS2 Angstrom 2009.X-test-20091213 overo ttyS2 overo login: ADDRCONF(NETDEV_UP): wlan0: link is not ready The above is the output im getting... -----Original Message----- From: Steve Sakoman [mailto:sa...@gm...] Sent: Wednesday, December 23, 2009 10:24 PM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] black screen On Wed, Dec 23, 2009 at 6:00 PM, Sufi, Azhar <as...@sa...> wrote: > Hi Steve: > > I did a git pull and rebuilt the code but am still getting the black screen... I haven't had a chance to test my build yet. The previous build was failing with this error: /usr/bin/X: symbol lookup error: /usr/lib/xorg/modules/drivers/omapfb_drv.so: undefined symbol: LoaderRefSymLists And this commit attempts to fix that issue: http://www.sakoman.net/cgi-bin/gitweb.cgi?p=openembedded.git;a=commitdiff;h=ddcd0de3398b85cfedb959ca6d4e21e1cf6d6e18 Are you getting a different error? Steve > > > -----Original Message----- > From: Steve Sakoman [mailto:sa...@gm...] > Sent: Wednesday, December 23, 2009 6:19 PM > To: General mailing list for gumstix users. > Subject: Re: [Gumstix-users] black screen > > On Wed, Dec 23, 2009 at 3:01 PM, Sufi, Azhar <as...@sa...> wrote: >> Hi Steve: >> >> Thanks. Is there a way to pull back to the 'working version' somehow? > > I just pushed some fixes for xorg. I have a build in progress to > verify them, but you can do a git pull now to pick them up. > > If you want to go back in time -- do a git log to find the commit > prior to yesterday's batch of xorg changes and then do a git checkout > <commit id> > > I suspect, though, that just just doing a git pull will get you back > in business. > > Steve > > >> Thanks >> Azhar >> >> >> >> -----Original Message----- >> From: Steve Sakoman [mailto:sa...@gm...] >> Sent: Wednesday, December 23, 2009 4:27 PM >> To: General mailing list for gumstix users. >> Subject: Re: [Gumstix-users] black screen >> >> On Wed, Dec 23, 2009 at 12:55 PM, Sufi, Azhar <as...@sa...> wrote: >> >>> I updated my local repository yesterday by issuing a git pull and since then >>> the desktop build shows a black screen following the angstrom status bar... >>> >>> Any hints? >> >> Yesterday's merge with upstream OE seems to have introduced a bug that >> prevents X11 from starting properly. >> >> I'm trying to track down the culprit and will push a fix as soon as I >> can find one! >> >> Sorry I didn't catch this before pushing the changes to the Overo branch :-( >> >> Steve >> >>> >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.Net email is sponsored by the Verizon Developer Community >>> Take advantage of Verizon's best-in-class app development support >>> A streamlined, 14 day to market process makes app distribution fast and easy >>> Join now and get one step closer to millions of Verizon customers >>> http://p.sf.net/sfu/verizon-dev2dev >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Steve S. <sa...@gm...> - 2009-12-24 03:47:48
|
On Wed, Dec 23, 2009 at 7:30 PM, Sufi, Azhar <as...@sa...> wrote: > OMAP3530-GP ES3.1, CPU-OPP2 L3-165MHz > Gumstix Overo board + LPDDR/NAND <snip> > The above is the output im getting... The error doesn't show up in the boot log, you need to look in the log files in /var/logs/ Forget which one, I'm not near the Overo right now . . . Steve > -----Original Message----- > From: Steve Sakoman [mailto:sa...@gm...] > Sent: Wednesday, December 23, 2009 10:24 PM > To: General mailing list for gumstix users. > Subject: Re: [Gumstix-users] black screen > > On Wed, Dec 23, 2009 at 6:00 PM, Sufi, Azhar <as...@sa...> wrote: >> Hi Steve: >> >> I did a git pull and rebuilt the code but am still getting the black screen... > > I haven't had a chance to test my build yet. > > The previous build was failing with this error: > > /usr/bin/X: symbol lookup error: > /usr/lib/xorg/modules/drivers/omapfb_drv.so: undefined symbol: > LoaderRefSymLists > > And this commit attempts to fix that issue: > > http://www.sakoman.net/cgi-bin/gitweb.cgi?p=openembedded.git;a=commitdiff;h=ddcd0de3398b85cfedb959ca6d4e21e1cf6d6e18 > > Are you getting a different error? > > Steve > >> >> >> -----Original Message----- >> From: Steve Sakoman [mailto:sa...@gm...] >> Sent: Wednesday, December 23, 2009 6:19 PM >> To: General mailing list for gumstix users. >> Subject: Re: [Gumstix-users] black screen >> >> On Wed, Dec 23, 2009 at 3:01 PM, Sufi, Azhar <as...@sa...> wrote: >>> Hi Steve: >>> >>> Thanks. Is there a way to pull back to the 'working version' somehow? >> >> I just pushed some fixes for xorg. I have a build in progress to >> verify them, but you can do a git pull now to pick them up. >> >> If you want to go back in time -- do a git log to find the commit >> prior to yesterday's batch of xorg changes and then do a git checkout >> <commit id> >> >> I suspect, though, that just just doing a git pull will get you back >> in business. >> >> Steve >> >> >>> Thanks >>> Azhar >>> >>> >>> >>> -----Original Message----- >>> From: Steve Sakoman [mailto:sa...@gm...] >>> Sent: Wednesday, December 23, 2009 4:27 PM >>> To: General mailing list for gumstix users. >>> Subject: Re: [Gumstix-users] black screen >>> >>> On Wed, Dec 23, 2009 at 12:55 PM, Sufi, Azhar <as...@sa...> wrote: >>> >>>> I updated my local repository yesterday by issuing a git pull and since then >>>> the desktop build shows a black screen following the angstrom status bar... >>>> >>>> Any hints? >>> >>> Yesterday's merge with upstream OE seems to have introduced a bug that >>> prevents X11 from starting properly. >>> >>> I'm trying to track down the culprit and will push a fix as soon as I >>> can find one! >>> >>> Sorry I didn't catch this before pushing the changes to the Overo branch :-( >>> >>> Steve >>> >>>> >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> This SF.Net email is sponsored by the Verizon Developer Community >>>> Take advantage of Verizon's best-in-class app development support >>>> A streamlined, 14 day to market process makes app distribution fast and easy >>>> Join now and get one step closer to millions of Verizon customers >>>> http://p.sf.net/sfu/verizon-dev2dev >>>> _______________________________________________ >>>> gumstix-users mailing list >>>> gum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>> >>>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.Net email is sponsored by the Verizon Developer Community >>> Take advantage of Verizon's best-in-class app development support >>> A streamlined, 14 day to market process makes app distribution fast and easy >>> Join now and get one step closer to millions of Verizon customers >>> http://p.sf.net/sfu/verizon-dev2dev >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.Net email is sponsored by the Verizon Developer Community >>> Take advantage of Verizon's best-in-class app development support >>> A streamlined, 14 day to market process makes app distribution fast and easy >>> Join now and get one step closer to millions of Verizon customers >>> http://p.sf.net/sfu/verizon-dev2dev >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Sufi, A. <asufi@Sarnoff.com> - 2009-12-24 04:20:22
|
Here is some info: root@overo:/var/volatile/log# less Xorg.0.log | grep Warn (WW) Warning, couldn't open module glx (WW) Warning, couldn't open module freetype (WW) Warning, couldn't open module type1 (WW) Warning, couldn't open module record (WW) Warning, couldn't open module dri (WW) Warning, couldn't open module dri2 root@overo:/var/volatile/log# less Xorg.0.log | grep Failed (EE) Failed to load module "glx" (module does not exist, 0) (EE) Failed to load module "freetype" (module does not exist, 0) (EE) Failed to load module "type1" (module does not exist, 0) (EE) Failed to load module "record" (module does not exist, 0) (EE) Failed to load module "dri" (module does not exist, 0) (EE) Failed to load module "dri2" (module does not exist, 0) root@overo:/var/volatile/log# less Xorg.0.log | grep Error (WW) Error opening /sys/devices/platform/omapfb/ctrl/name: No such file or direc Tory -----Original Message----- From: Steve Sakoman [mailto:sa...@gm...] Sent: Wednesday, December 23, 2009 10:48 PM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] black screen On Wed, Dec 23, 2009 at 7:30 PM, Sufi, Azhar <as...@sa...> wrote: > OMAP3530-GP ES3.1, CPU-OPP2 L3-165MHz > Gumstix Overo board + LPDDR/NAND <snip> > The above is the output im getting... The error doesn't show up in the boot log, you need to look in the log files in /var/logs/ Forget which one, I'm not near the Overo right now . . . Steve > -----Original Message----- > From: Steve Sakoman [mailto:sa...@gm...] > Sent: Wednesday, December 23, 2009 10:24 PM > To: General mailing list for gumstix users. > Subject: Re: [Gumstix-users] black screen > > On Wed, Dec 23, 2009 at 6:00 PM, Sufi, Azhar <as...@sa...> wrote: >> Hi Steve: >> >> I did a git pull and rebuilt the code but am still getting the black screen... > > I haven't had a chance to test my build yet. > > The previous build was failing with this error: > > /usr/bin/X: symbol lookup error: > /usr/lib/xorg/modules/drivers/omapfb_drv.so: undefined symbol: > LoaderRefSymLists > > And this commit attempts to fix that issue: > > http://www.sakoman.net/cgi-bin/gitweb.cgi?p=openembedded.git;a=commitdiff;h=ddcd0de3398b85cfedb959ca6d4e21e1cf6d6e18 > > Are you getting a different error? > > Steve > >> >> >> -----Original Message----- >> From: Steve Sakoman [mailto:sa...@gm...] >> Sent: Wednesday, December 23, 2009 6:19 PM >> To: General mailing list for gumstix users. >> Subject: Re: [Gumstix-users] black screen >> >> On Wed, Dec 23, 2009 at 3:01 PM, Sufi, Azhar <as...@sa...> wrote: >>> Hi Steve: >>> >>> Thanks. Is there a way to pull back to the 'working version' somehow? >> >> I just pushed some fixes for xorg. I have a build in progress to >> verify them, but you can do a git pull now to pick them up. >> >> If you want to go back in time -- do a git log to find the commit >> prior to yesterday's batch of xorg changes and then do a git checkout >> <commit id> >> >> I suspect, though, that just just doing a git pull will get you back >> in business. >> >> Steve >> >> >>> Thanks >>> Azhar >>> >>> >>> >>> -----Original Message----- >>> From: Steve Sakoman [mailto:sa...@gm...] >>> Sent: Wednesday, December 23, 2009 4:27 PM >>> To: General mailing list for gumstix users. >>> Subject: Re: [Gumstix-users] black screen >>> >>> On Wed, Dec 23, 2009 at 12:55 PM, Sufi, Azhar <as...@sa...> wrote: >>> >>>> I updated my local repository yesterday by issuing a git pull and since then >>>> the desktop build shows a black screen following the angstrom status bar... >>>> >>>> Any hints? >>> >>> Yesterday's merge with upstream OE seems to have introduced a bug that >>> prevents X11 from starting properly. >>> >>> I'm trying to track down the culprit and will push a fix as soon as I >>> can find one! >>> >>> Sorry I didn't catch this before pushing the changes to the Overo branch :-( >>> >>> Steve >>> >>>> >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> This SF.Net email is sponsored by the Verizon Developer Community >>>> Take advantage of Verizon's best-in-class app development support >>>> A streamlined, 14 day to market process makes app distribution fast and easy >>>> Join now and get one step closer to millions of Verizon customers >>>> http://p.sf.net/sfu/verizon-dev2dev >>>> _______________________________________________ >>>> gumstix-users mailing list >>>> gum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>> >>>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.Net email is sponsored by the Verizon Developer Community >>> Take advantage of Verizon's best-in-class app development support >>> A streamlined, 14 day to market process makes app distribution fast and easy >>> Join now and get one step closer to millions of Verizon customers >>> http://p.sf.net/sfu/verizon-dev2dev >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.Net email is sponsored by the Verizon Developer Community >>> Take advantage of Verizon's best-in-class app development support >>> A streamlined, 14 day to market process makes app distribution fast and easy >>> Join now and get one step closer to millions of Verizon customers >>> http://p.sf.net/sfu/verizon-dev2dev >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: <cod...@gm...> - 2009-12-24 03:57:27
|
I actually didn't miss that step. After appending ~/.bashrc, I can either close/reopen the terminal, or source it via $ source ~/.bashrc If I echo $GUMSTIXTOP in the terminal, it returns nothing, and there is no com.gumstix.collection folder anywhere in the overo-oe tree as far as I can tell, but if I try to run $ bitbake u-boot It appears to be trying to build all of my ~/overo-oe/user.collection/recipes/ projects into an OS image or something? This is when it complains about not being able to include ${GUMSTIXTOP}/com.gumstix.collection/...path/to/some/file... I can't remember the rest, but my dev box is at a remote location right now. What about buildroot? Do I need to configure that? http://docwiki.gumstix.org/Buildroot On Wed, Dec 23, 2009 at 3:25 PM, Nathan Tyler <nk...@gm...> wrote: > Check the steps again, I'm guessing you missed this one: > > $ cat ~/overo-oe/build/profile >> ~/.bashrc > > taken from this site: > > http://www.gumstix.net/Setup-and-Programming/view/Overo-Setup-and-Programming/Setting-up-a-build-environment/111.html > > You'll also need to close and reopen the terminal for those changes to take > effect > > > On Wed, Dec 23, 2009 at 2:27 PM, <cod...@gm...> wrote: > >> Hello, >> >> I've recently just gotten started in the world of OpenEmbedded and Gumstix >> Overo. I followed the "setting up a build environment" instructions on >> gumstix.net's documentation section, which created a bitbake environment >> with an org.openembedded.dev, user.collection, and other directories under >> overo-oe. I'm able to create my own recipes under user.collection/recipes >> and use that to create .ipk packages to install on Gumstix. >> >> However, I'm running into issues when I try to run bitbake on things like, >> say, u-boot. I get error messages saying it could not find >> ${GUMSTIXTOP}/com.gumstix.collection/... I don't even have a ${GUMSTIXTOP}, >> or com.gumstix.collection in my configuration. >> >> Is there more to setting up a build environment than just the 'setting up >> a build environment' section in the documentation? I saw a wiki page about >> buildroot, but that seemed like a completely different environment, separate >> from what goes into overo-oe. >> >> What am I missing? >> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and >> easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Wayne C. <wc...@so...> - 2009-12-24 07:37:42
|
I'm new to Gumstix and OpenEmbedded to, but my build/profile sets OVEROTOP, not GUMSTIXTOP. I don't know when or where GUMSTIXTOP is set, but after changing OVEROTOP to match my directory path (it's initially "${HOME}/overo-oe"), I was able to complete a full build. --Wayne coderdrone wrote: > > I actually didn't miss that step. After appending ~/.bashrc, I can either > close/reopen the terminal, or source it via $ source ~/.bashrc > > If I echo $GUMSTIXTOP in the terminal, it returns nothing, and there is no > com.gumstix.collection folder anywhere in the overo-oe tree as far as I > can > tell, but if I try to run > > $ bitbake u-boot > > It appears to be trying to build all of my > ~/overo-oe/user.collection/recipes/ projects into an OS image or > something? > This is when it complains about not being able to include > ${GUMSTIXTOP}/com.gumstix.collection/...path/to/some/file... I can't > remember the rest, but my dev box is at a remote location right now. > ... > -- View this message in context: http://old.nabble.com/-Gumstix-Users--Clarification-on-Proper-Build-Environment-tp26906418p26911252.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Nathan T. <nk...@gm...> - 2009-12-24 16:52:38
|
Apologies, I have a Verdex so I know very little about the Overo side. I can tell you that the verdex config does have a GUMSTIXTOP, so maybe you're trying to build the Verdex UBoot, especially since I believe com.gumstix.collection is a folder in the Verdex build environment as well. On Thu, Dec 24, 2009 at 2:37 AM, Wayne Cannon <wc...@so...> wrote: > > I'm new to Gumstix and OpenEmbedded to, but my build/profile sets OVEROTOP, > not GUMSTIXTOP. I don't know when or where GUMSTIXTOP is set, but after > changing OVEROTOP to match my directory path (it's initially > "${HOME}/overo-oe"), I was able to complete a full build. > --Wayne > > > coderdrone wrote: > > > > I actually didn't miss that step. After appending ~/.bashrc, I can > either > > close/reopen the terminal, or source it via $ source ~/.bashrc > > > > If I echo $GUMSTIXTOP in the terminal, it returns nothing, and there is > no > > com.gumstix.collection folder anywhere in the overo-oe tree as far as I > > can > > tell, but if I try to run > > > > $ bitbake u-boot > > > > It appears to be trying to build all of my > > ~/overo-oe/user.collection/recipes/ projects into an OS image or > > something? > > This is when it complains about not being able to include > > ${GUMSTIXTOP}/com.gumstix.collection/...path/to/some/file... I can't > > remember the rest, but my dev box is at a remote location right now. > > ... > > > > -- > View this message in context: > http://old.nabble.com/-Gumstix-Users--Clarification-on-Proper-Build-Environment-tp26906418p26911252.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: <cod...@gm...> - 2009-12-28 20:26:13
|
My build environment is supposed to be overo. Following the 'setting up a build environment' instructions from gumstix.net's documentation, I get a ${HOME}/overo-oe directory tree like your environment does. I didn't update this, since OVEROTOP should be ok as it is set by default. When I wanted to rebuild u-boot, I did a "find . -name "overo.h"" in the overo-oe folder and modified the most likely overo.h file I could find. I believe it happened to be in the overo-oe/tmp/.../build/.../ or similar directory. My appologies as the build workstation is back at the office. After modifying it, I did a bitbake u-boot and got the error messages from my above emails about com.gumstix.collection. On Thu, Dec 24, 2009 at 2:37 AM, Wayne Cannon <wc...@so...> wrote: > > I'm new to Gumstix and OpenEmbedded to, but my build/profile sets OVEROTOP, > not GUMSTIXTOP. I don't know when or where GUMSTIXTOP is set, but after > changing OVEROTOP to match my directory path (it's initially > "${HOME}/overo-oe"), I was able to complete a full build. > --Wayne > > > coderdrone wrote: > > > > I actually didn't miss that step. After appending ~/.bashrc, I can > either > > close/reopen the terminal, or source it via $ source ~/.bashrc > > > > If I echo $GUMSTIXTOP in the terminal, it returns nothing, and there is > no > > com.gumstix.collection folder anywhere in the overo-oe tree as far as I > > can > > tell, but if I try to run > > > > $ bitbake u-boot > > > > It appears to be trying to build all of my > > ~/overo-oe/user.collection/recipes/ projects into an OS image or > > something? > > This is when it complains about not being able to include > > ${GUMSTIXTOP}/com.gumstix.collection/...path/to/some/file... I can't > > remember the rest, but my dev box is at a remote location right now. > > ... > > > > -- > View this message in context: > http://old.nabble.com/-Gumstix-Users--Clarification-on-Proper-Build-Environment-tp26906418p26911252.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: <cod...@gm...> - 2009-12-30 16:27:03
|
I believe I found the problem. One of the recipes in my user.collection/recipes folder had a .bb file with a dependency listed for ${GUMSTIXTOP}/com.gumstix.collection/... I removed that recipe since it was just a hello world app, and everything seems to build correctly. As for rebuilding u-boot itself, it appears the correct way to do that would be to run $ bitbake u-boot $ bitbake -c devshell u-boot Which gives you a development shell where you can modify u-boot as needed (e.g., adding pins to ./board/omap3/overo/overo.h), exit, and let bitbake finish. On Mon, Dec 28, 2009 at 3:25 PM, <cod...@gm...> wrote: > My build environment is supposed to be overo. Following the 'setting up a > build environment' instructions from gumstix.net's documentation, I get a > ${HOME}/overo-oe directory tree like your environment does. I didn't update > this, since OVEROTOP should be ok as it is set by default. > > When I wanted to rebuild u-boot, I did a "find . -name "overo.h"" in the > overo-oe folder and modified the most likely overo.h file I could find. I > believe it happened to be in the overo-oe/tmp/.../build/.../ or similar > directory. My appologies as the build workstation is back at the office. > > After modifying it, I did a bitbake u-boot and got the error messages from > my above emails about com.gumstix.collection. > > On Thu, Dec 24, 2009 at 2:37 AM, Wayne Cannon <wc...@so...> wrote: > >> >> I'm new to Gumstix and OpenEmbedded to, but my build/profile sets >> OVEROTOP, >> not GUMSTIXTOP. I don't know when or where GUMSTIXTOP is set, but after >> changing OVEROTOP to match my directory path (it's initially >> "${HOME}/overo-oe"), I was able to complete a full build. >> --Wayne >> >> >> coderdrone wrote: >> > >> > I actually didn't miss that step. After appending ~/.bashrc, I can >> either >> > close/reopen the terminal, or source it via $ source ~/.bashrc >> > >> > If I echo $GUMSTIXTOP in the terminal, it returns nothing, and there is >> no >> > com.gumstix.collection folder anywhere in the overo-oe tree as far as I >> > can >> > tell, but if I try to run >> > >> > $ bitbake u-boot >> > >> > It appears to be trying to build all of my >> > ~/overo-oe/user.collection/recipes/ projects into an OS image or >> > something? >> > This is when it complains about not being able to include >> > ${GUMSTIXTOP}/com.gumstix.collection/...path/to/some/file... I can't >> > remember the rest, but my dev box is at a remote location right now. >> > ... >> > >> >> -- >> View this message in context: >> http://old.nabble.com/-Gumstix-Users--Clarification-on-Proper-Build-Environment-tp26906418p26911252.html >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and >> easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > |