Yes, exactly the same software on both BBB. 2015-03-15 1:11 GMT+00:00 Gerald Coley <ger...@beagleboard.org>:
> So you have one board that works and another that does not work with the > same exact software? > Gerald > > On Sat, Mar 14, 2015 at 11:43 AM, Upol Ryskulova <upo...@gmail.com> wrote: > >> Hello Gerald, >> I faced with the same problem as Glenn >> "I appear to be getting is that during the initial boot, I get the >> BeagleBone logo appear in the top left of the screen. This also changes >> size depending on what resolution I set in uEnv.txt .After this image >> disappears and a little more time has passed, I get "No Signal" on my 32" >> TV or "Power Saving Mode HDMI" on my LG Flatron L246WH 24" Monitor." said >> above. Except I have different LCD Screen. My parse-edid edid >> >> parse-edid: parse-edid version 2.0.0 >> parse-edid: EDID checksum passed. >> >> # EDID version 1 revision 3 >> Section "Monitor" >> # Block type: 2:0 3:ff >> # Block type: 2:0 3:fc >> Identifier "Philips 226V4" >> VendorName "PHL" >> ModelName "Philips 226V4" >> # Block type: 2:0 3:ff >> # Block type: 2:0 3:fc >> # Block type: 2:0 3:fd >> HorizSync 30-83 >> VertRefresh 56-76 >> # Max dot clock (video bandwidth) 170 MHz >> # DPMS capabilities: Active off:yes Suspend:no Standby:no >> >> Mode "1920x1080" # vfreq 60.000Hz, hfreq 67.500kHz >> DotClock 148.500000 >> HTimings 1920 2008 2052 2200 >> VTimings 1080 1084 1089 1125 >> Flags "+HSync" "+VSync" >> EndMode >> # Block type: 2:0 3:ff >> # Block type: 2:0 3:fc >> # Block type: 2:0 3:fd >> EndSection >> >> I did try to give defaul screen resolution in uEnv.txt as Glenn said. But >> it is just changing the size of the debian logo for 2-3 seconds and then >> screen turning to black again. I upgraded to linux 3.8.13-bone70 today from >> linux 3.8.13-bone41 just downloaded it ran ./install-me.sh then rebooted. I >> am working with two beaglebone black boards right now. One is perfectly >> running with lcd screen and hdmi cable without any modification to uEnv.xt >> file or something else. Both BBB boards have same kernel and os versions. I >> appreciate all your advice and help. >> >> Upol >> >> >> >> 29 Aralık 2013 Pazar 22:28:57 UTC+2 tarihinde Gerald yazdı: >>> >>> I assume you followed all the instructions on the Wiki, so I guess the >>> board is bad. I would to an RMA request. >>> >>> Gerald >>> >>> >>> >>> On Sat, Dec 28, 2013 at 10:57 AM, <aeh...@gmail.com> wrote: >>> >>>> Hi Gerald! I have the same problem as the people on here. Did an MMC >>>> reflash to latest software and thought maybe it is a faulty HDMI cable. I >>>> have since received a dragon board with the same micro hdmi connector as >>>> the beaglebone. Dragonboard HDMI works fine, BeagleBone does not. >>>> Any ideas? >>>> Thanks, Alex >>>> >>>> >>>> On Tuesday, May 7, 2013 7:06:19 AM UTC-7, ghalf...@googlemail.com >>>> wrote: >>>> >>>>> I've just received a BeagleBone Black, but I can't get the HDMI output >>>>> to work for love nor money. I'm using a known-good micro-HDMI to HDMI >>>>> adapter, and I've tried connecting it to a 1280x1024 monitor via a HDMI to >>>>> DVI-D cable and to a 1080p TV using a straight HDMI cable. The TV knows >>>>> there's something there (it disables inputs that are inactive, and it >>>>> allows me to select the HDMI input to which the BeagleBone is connected) >>>>> but says "No Signal," whereas the monitor just says "No Signal." >>>>> >>>>> I've tried both the preinstalled Angstrom Linux and the console >>>>> version of Ubuntu 13.04 - no dice with either. I've got a proper >>>>> micro-HDMI >>>>> to HDMI cable arriving tomorrow, just in case there's something the >>>>> BeagleBone Black doesn't like about the adapter I'm using (although I >>>>> tested it on a Nokia 808 PureView, and it worked fine.) >>>>> >>>>> Anybody any ideas what might be preventing the BeagleBone Black from >>>>> bringing up a display? I can see nothing in the kernel logs that sheds any >>>>> light on the matter. It sees the virtual HDMI cape in Slot 6 and appears >>>>> to >>>>> load the firmware cape-boneblack-hdmi-00A0.dtbo fine. >>>>> >>>> -- >>>> For more options, visit http://beagleboard.org/discuss >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "BeagleBoard" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to beagleboard...@googlegroups.com. >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>> >>> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to beagleboard+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Gerald > > ger...@beagleboard.org > http://beagleboard.org/ > http://circuitco.com/support/ > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/0fMTXLPuGS4/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
