Re: dmesg messages

[Bruce D Lightner]

Same issue here...

.
.
.
[Mon Jun 10 05:52:00 2013] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 2 to 2
[Mon Jun 10 05:52:10 2013] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 2 to 2
[Mon Jun 10 05:52:20 2013] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 2 to 2
[Mon Jun 10 05:52:30 2013] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 2 to 2
[Mon Jun 10 05:52:41 2013] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 2 to 2
.
.
.

No HDMI monitor plugged in. Fills up the system logs with trash and therefore pushes out other significant log information.

Another example of why Angstrom on the Beagle Bone Black is not ready for prime time.

[Gerald Coley]

Then stop using it. There are other more robust offerings out there..

Gerald

--
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.
 
 

--

Gerald

 

ger...@beagleboard.org

g-co...@ti.com

http://beagleboard.org/

http://circuitco.com/support/

[Bruce D Lightner]

Gerald,

And your "other more robust offerings" recommendations include what?

Best regards,

Bruce

[Gerald Coley]

Ubuntu.is one.Go back to a 3.2 Kernel offering is another.

Gerald

--
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.
 
 

[Bruce D Lightner]

Gerald,

Thank you for the recommendations.  I really do want to make my two Beaglebone Black PCBs work for my application.  Maybe I just need to wait a few months for the dust to settle? :-)

(1) How do I find the "3.2 Kernel"?  And, most importantly, will key components like "opkg" even work properly after installing same?  My recent experience with BBB Angstrom indicates that downloading packages after "opkg update" tended to give me stuff that did not "play well together" with a "mismatched" kernel version.  I do not want to enter the equivalent of MS Windows "DLL Hell". :-)

(2) As for Ubuntu, the reason I am back fighting with: (1) Angstrom on the BBB hardware, (2) the poorly documented "connman", and (3) the seemingly flaky USB Wifi firmware is that adding peripherals (such as additional serial ports) to the BBB OS seems to be impossible without Angstrom because the required Device Tree Compiler (dtc) does not work under Ubuntu on BBB.

Best regards,

Bruce

P.S. - Sorry to hit you with this on Monday morning...but no one has answered the original week-old posting.  All the silly "drm" log messages are getting in the way of my hardware/firmware stability testing.

[Gerald Coley]

Dust to settle? well, as the HW guy I have lung issues because there always seem to be dust! I hope we can get these issues put to bed. It is driving me crazy!

As to the 3.2, TI is about to release their SDK for the BBB on 3.2. And as it has no HDMI support currently, it should work for you.

As to USB, yes there are issues there. As I said TI is working a solution, and we just need to figure out how to make it the most important thing in the universe!

DT was definitely a big pill to swallow for us when TI backed out. We are working around the clock to know these issues fixed. But, we do rely on community patches to help on these as well.

Gerald

--
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.
 
 

[Robert Nelson]

On Mon, Jun 10, 2013 at 9:02 AM, Bruce D Lightner <bdlig...@gmail.com> wrote:
> Gerald,
>
> Thank you for the recommendations. I really do want to make my two
> Beaglebone Black PCBs work for my application. Maybe I just need to wait a
> few months for the dust to settle? :-)
>
> (1) How do I find the "3.2 Kernel"? And, most importantly, will key
> components like "opkg" even work properly after installing same? My recent
> experience with BBB Angstrom indicates that downloading packages after "opkg
> update" tended to give me stuff that did not "play well together" with a
> "mismatched" kernel version. I do not want to enter the equivalent of MS
> Windows "DLL Hell". :-)
>
> (2) As for Ubuntu, the reason I am back fighting with: (1) Angstrom on the
> BBB hardware, (2) the poorly documented "connman", and (3) the seemingly
> flaky USB Wifi firmware is that adding peripherals (such as additional
> serial ports) to the BBB OS seems to be impossible without Angstrom because
> the required Device Tree Compiler (dtc) does not work under Ubuntu on BBB.

so... Why don't you just build dtc, with the angstrom patch on ubuntu?

Oh, you want someone to do it for you:

wget -c https://raw.github.com/RobertCNelson/tools/master/pkgs/dtc.sh
chmod +x dtc.sh
./dtc.sh

done..

Regards,

--
Robert Nelson
http://www.rcn-ee.com/

[Bruce D Lightner]

so... Why don't you just build dtc, with the angstrom patch on ubuntu?

Oh, you want someone to do it for you:

wget -c https://raw.github.com/RobertCNelson/tools/master/pkgs/dtc.sh
chmod +x dtc.sh
./dtc.sh

Robert,

Thanks for the link.  Have you actually made that work?

I started down that path but quickly came to the conclusion that I might need to build the Linux kernel used in the Ubuntu release (i.e., the one that seemed to work so well on the BBB hardware).  I looked like "dtc" had "hooks" into the kernel...much like a kernel module does.

Do you think that I can work with this BBB Ubuntu release?

  BBB-eMMC-flasher-ubuntu-13.04-2013-05-29.img.xz

Best regards,

Bruce

[Robert Nelson]

That 'image' has a kernel installed in it that was 'built' before i
patched the device-tree-compiler binary in all my arm schroot's.

So, you'll still have to rebuild... Which actually isn't that hard,
once you just let my script built it for you...

[Bruce D Lightner]

Gerald,

On Monday, June 10, 2013 7:14:40 AM UTC-7, Gerald wrote:

Dust to settle? well, as the HW guy I have lung issues because there always seem to be dust! I hope we can get these issues put to bed. It is driving me crazy!

As to the 3.2, TI is about to release their SDK for the BBB on 3.2. And as it has no HDMI support currently, it should work for you.

Yeah!  I don't want/need a $200+ HDMI monitor connected to my $40 embedded hardware! :-)

As to USB, yes there are issues there. As I said TI is working a solution, and we just need to figure out how to make it the most important thing in the universe!

Whatever I can do to help "make that sew"---I'm your man! :-)

TI marketing needs to pay attention.  It seems to me that the excellent TI ARM silicon used in the Beaglebone Black is getting a huge "black eye" because of the many firmware issues with the BBB "Raspberry Pi killer".  I was immediately drawn to the BBB hardware and was excited to get something working.  Embedded Linux is the future and TI needs to be in the game.  My experiences with the BBB software has been less than stellar.  I cannot recommend embedded Linux on TI hardware at this point in time.  Out-of-the-box the simplest of things did not work as expected.  Is it hardware or is it firmware?  It really doesn't matter---I need to deliver results.

DT was definitely a big pill to swallow for us when TI backed out. We are working around the clock to know these issues fixed. But, we do rely on community patches to help on these as well.

As it stands, what one has to do to enable a simple second UART port is truly amazing to me.  I really do not like "trolling the Internet" for the information that I need---hoping that some poor fool took the time to share their "discoveries".  It seems to me that a simple "man page" or a cookbook "How To" document is the standard for this sort of thing.

Best regards,

Bruce

[Gerald Coley]

Black eyes may be the case. But, we are way out in front of TI on the 3.8+ kernel support. We have 6,200 developers out there, some of which help with patches and fixes, and others who just complain. So we will take the black eyes for those people that do not understand SW and what the BeagleBone Black and the BeagleBaord.org community is all about. I recall that the Pi had some rough SW times as well in the beginning. I have not had a chance to track their 3.8 kernel offering and how it is going. It is the nature of the community boards.

If you want solid and stable SW, then go buy a TI EVM and work with the 3.2 kernel.

Gerald

--

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.
 
 

[William Hermans]

Seriously for $45 the amount of hardware you get is enough. Then on top of that you have people like RCN who spend time writing excellent instructions / scripts to set everything up for you. Who also are willing to answer any question you have about the software seemingly no matter how silly the question may be ( and yeah I've asked a couple of silly questions myself ).

It amazes me how much people complain about dirt "cheap" (read inexpensive not shoddy ) hardware, and lack of software compatibility where there is a lot of it already out there. Why on earth would you jump into buying hardware as such if you were not willing to do some of the work yourself ?

There are already lots of platforms out there that are supposed to work right out of the box, and all of them cost multiples of what it takes to buy a beagleboard black. Knock yourself out. Or, you could do something crazy / unheard of like googling once in a while in an attempt to help yourself. Even crazier still, you might even consider blogging about how you made something work . . .

gimme gimme gimme

Here endith the rant.

[Bruce D Lightner]

William Hermans,

Stop being such a jerk.  (Oh no!  Now I've started another "flame war" :-)  BRING IT ON!

The bottom line is that both the Angstrom and Ubuntu Beaglebone Black releases simply are not stable and therefore not useful, except maybe for BBB kernel development.

BeagleBoard.Org takes my money and ships me something they KNOW does not work properly---and no one knows when/if it ever will?

Yes, I expected at the very least that the BBB PCB that I received would work as documented "out-of-the-box".  It did not.

For example:

(1) SSH did not work (a "zero-length" key file that took hours to diagnose)

(2) On my Windows 7 PC the virtual COM port (via the USB connection) did not have a "getty" running on it!

(3) Using "opkg update" followed by "opkg upgrade", as advised, hosed everything and required a re-install via SDCard

Later I've learned that USB WiFi does not work---lost connections and kernel panics.  (This fact seems to be a BIG SECRET!)

BTW: Adafruit, who makes money selling BBB PCBs and USB WiFi dongles, claims that all is well on this front!!?

USB DMA to support USB Webcams causes kernel panics.

Investing hours installing BBB Ubuntu and testing the above (as advised) did not help.  Still not stable.

Bottom Line: The BeableBOne Black (BBB) is not ready for "prime time".

When the "emperor has no clothes" someone needs to point that out. :-)  And, that would be ME!

Yes, lots of people are working real hard on this for no pay.  But, in the mean time people are being sold otherwise fine hardware that may never work because the software may never get completed.

Best regards,

Bruce "gimme gimme gimme" Lightner
Ex-BeagleBOne Black User

P.S.- Flame away William...

[Robert Nelson]

On Mon, Jun 10, 2013 at 5:31 PM, Bruce D Lightner <bdlig...@gmail.com> wrote:
> William Hermans,
>
> Stop being such a jerk. (Oh no! Now I've started another "flame war" :-)
> BRING IT ON!
>
> The bottom line is that both the Angstrom and Ubuntu Beaglebone Black
> releases simply are not stable and therefore not useful, except maybe for
> BBB kernel development.

Really? I don't remember advertising my ubuntu release's as stable?
Hence why i push out bi-weekly/monthly 'snapshots' of ubuntu/debian
images.

>
> BeagleBoard.Org takes my money and ships me something they KNOW does not
> work properly---and no one knows when/if it ever will?
>
> Yes, I expected at the very least that the BBB PCB that I received would
> work as documented "out-of-the-box". It did not.
>
> For example:
>
> (1) SSH did not work (a "zero-length" key file that took hours to diagnose)
>
> (2) On my Windows 7 PC the virtual COM port (via the USB connection) did not
> have a "getty" running on it!

Ahh, this "usb-serial" connection was from "physical" hardware that
existed on the original beaglebone... It was removed on the black and
replaced with 5 pin header. (thank the gods!).

> (3) Using "opkg update" followed by "opkg upgrade", as advised, hosed
> everything and required a re-install via SDCard
>
> Later I've learned that USB WiFi does not work---lost connections and kernel
> panics. (This fact seems to be a BIG SECRET!)

My I ask, which USB WiFi chipset? Unless it's an Atheros/Qualcomm
chipset, in my experience they are all pretty much crap on arm...

By chance was it this one?
http://www.adafruit.com/products/814#Technical Details
RTl8192cu

I have 5 different usb modules with that chipset, one kinda works..
Stay away from them when using a pure mainline.. The ONLY way anyone
has got them to work, is rebuild the kernel against the manufacture's
rtl8192 driver, which a few people have documented.

>
> BTW: Adafruit, who makes money selling BBB PCBs and USB WiFi dongles, claims
> that all is well on this front!!?
>
> USB DMA to support USB Webcams causes kernel panics.

Hence why it's disabled in my 3.8 tree..

> Investing hours installing BBB Ubuntu and testing the above (as advised) did
> not help. Still not stable.

Sorry, I was gone on business last week, but I don't remember any bug
reports before i purged my email to catchup on things... Do you have
any beagleboard google group links?

>
> Bottom Line: The BeableBOne Black (BBB) is not ready for "prime time".
>
> When the "emperor has no clothes" someone needs to point that out. :-) And,
> that would be ME!
>
> Yes, lots of people are working real hard on this for no pay. But, in the
> mean time people are being sold otherwise fine hardware that may never work
> because the software may never get completed.
>
> Best regards,
>
> Bruce "gimme gimme gimme" Lightner
> Ex-BeagleBOne Black User
>
> P.S.- Flame away William...

[William Hermans]

Gerald, Robert C Nelson, Koen, Panto, and the countless others I have not named here. Thank you very much for the time you have put into this hardware, and software.

It may not be 100% perfect, but the hardware, and software has lots of potential( in most cases it is fine), and certainly it is keeping me engaged.

Bruce, I am sure you will get very far with that mentality. Just be aware that it is really simple to add a spam filter to just about any email client. So there will be no flame war. Have a nice day.

[craig.m...@gmail.com]

Edit
  /media/BEAGLEBONE/uEnv.txt
and change
  drm.debug=7
to either of these two,
  drm.debug=3
  drm.debug=11
This is a bit mask.  The "4" value produces the plentiful HDM connector messages, so by subtracting 7-4=3 you remove the offending messages.

Craig

On Wednesday, June 5, 2013 2:30:03 AM UTC-4, tvv...@gmail.com wrote:

Hi

I have BBB with Angstrom 2013-05-27. After dmesg I get:

[ 72.936416] gen_ndis_query_resp: RNDIS_OID_GEN_RCV_NO_BUFFER
[ 72.940091] gadget: rndis reqa1.01 v0000 i0000 l4096
[ 72.940361] gadget: rndis req21.00 v0000 i0000 l36
[ 72.944095] gadget: rndis reqa1.01 v0000 i0000 l4096
[ 72.944390] gadget: rndis req21.00 v0000 i0000 l36
[ 72.948090] gadget: rndis reqa1.01 v0000 i0000 l4096
[ 72.948374] gadget: rndis req21.00 v0000 i0000 l36
[ 72.948412] gen_ndis_query_resp: RNDIS_OID_GEN_RCV_NO_BUFFER
[ 72.952062] gadget: rndis reqa1.01 v0000 i0000 l4096
[ 72.952189] gadget: rndis req21.00 v0000 i0000 l36
[ 72.956092] gadget: rndis reqa1.01 v0000 i0000 l4096
[ 80.906804] [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 2 to 2

Every 10 sec  [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 2 to 2.

Is it notmal?

[smith.wi...@gmail.com]

On Saturday, July 20, 2013 4:01:55 PM UTC-4, craig.m...@gmail.com wrote:

Edit
  /media/BEAGLEBONE/uEnv.txt
and change
  drm.debug=7
to either of these two,
  drm.debug=3
  drm.debug=11
This is a bit mask.  The "4" value produces the plentiful HDM connector messages, so by subtracting 7-4=3 you remove the offending messages.

Thank you ... those messages in dmesg were getting annoying! 

-W.

[daen...@yahoo.com]

Not doing it for me. Tried both on a fresh install of 2013-09-04 image.

Hate to think of it as eating up the limited amount of flash storage.

On Saturday, July 20, 2013 4:01:55 PM UTC-4, craig.m...@gmail.com wrote:

[craig.m...@gmail.com]

I've found that in more recent releases the BEAGLEBONE partition is not mounted by default. 

In case it's not, you should mount it first,
   mount /dev/mmcblk0p1 /media/BEAGLEBONE
before trying to edit the uEnv.txt file.

[Fred Wright]

What I found in mine, with the 2013-09-04 image that it came with, is that:

1) The partition is mounted, but it's mounted on "/media/BEAGLEBONE_".  The non-underscore mount point is present but unused.

2) Changing the value worked, but only after a reboot.

One does of course wonder why it considers reporting status *non-changes* to be useful, even with the bit set. :-)

[ChuckM]

On Monday, June 10, 2013 7:28:45 AM UTC-7, RobertCNelson wrote:

so... Why don't you just build dtc, with the angstrom patch on ubuntu?

Oh, you want someone to do it for you:

wget -c https://raw.github.com/RobertCNelson/tools/master/pkgs/dtc.sh
chmod +x dtc.sh
./dtc.sh

done..

Robert, thank you so much for that hint. I had spent much of the day trying to find the specific patches to the dtc repo to create the Angstrom version. While the capability to do plugins is Angstrom specific at the moment this seems to have wider applicability. Given that this version identifies as 1.4 is this something that is working its way upstream? 

--Chuck