**** BEGIN LOGGING AT Sat Oct 04 03:00:01 2014 Oct 04 11:34:44 i got some trouble when i am going to change my HDMI display resolution Oct 04 11:35:12 Can u please answer me ?? Oct 04 11:35:47 Hi, are there any plans to make BBB with more RAM ? Oct 04 12:46:47 <_av500_> no Oct 04 12:47:01 <_av500_> none that we know off Oct 04 12:47:05 <_av500_> of* Oct 04 13:57:40 Hello! Oct 04 14:04:17 I'm trying to use NFS with my BBB without success. I've got a "Unable to mount root fs via NFS" error message before a kernel panic. I also have a "Please append a correct root= boot option" message. Oct 04 14:04:36 This is weird as I gave root=/dev/nfs Oct 04 14:04:54 By the way, I observed that there is no "nfs" file in /dev Oct 04 14:04:59 Is this normal? Oct 04 14:05:13 I made the image on my own with buildroot Oct 04 14:06:26 Here is the line I gave to u-boot : setenv bootargs root=/dev/nfs nfsroot=192.168.1.4:/serv/bbb-rootfs rw ip=dhcp console=ttyO0,115200n8 Oct 04 14:34:10 might anyone have experience installing osmo-trx on BBB? everything installed fine but when i run it, it says: terminate called after throwing an instance of 'std::bad_alloc'....any ideas? Oct 04 16:41:09 <_av500_> gdb is an idea Oct 04 16:44:15 Somebody to help? Oct 04 16:44:41 I'm able to mount a NFS on my computer but I can't proceed with the target Oct 04 16:44:59 It seems to be a common issue but I didn't find any solution on the internet Oct 04 16:45:27 Does someone can help? Oct 04 16:45:33 It's driving me crazy! Oct 04 17:01:13 [ 8.034871] bootserver=192.168.1.1, rootserver=192.168.1.4, rootpath= Oct 04 17:01:20 I am unable to flash debian onto my Beaglebon black.. it begins to flash then ends with 2 leds lit... any ideas what may be the issue? Oct 04 17:05:08 Most recently, when flashing all 4 LEDs will begin to blink in unison, and then shut off. Upon removing the SD card and plugging it back in.. nothing happens, it is dead. Please help Oct 04 17:05:30 When flashing, this is what I am reading from the debug.. Starting kernel ... Uncompressing Linux... done, booting the kernel. [ 0.378527] omap2_mbox_probe: platform not supported [ 0.533177] tps65217-bl tps65217-bl: no platform data provided [ 0.596932] bone-capemgr bone_capemgr.9: slot #0: No cape found [ 0.634040] bone-capemgr bone_capemgr.9: slot #1: No cape found [ 0.671148] bone-capemgr bone_capemgr.9: slot #2: Oct 04 17:07:02 beaglebone login: [ 38.316112] libphy: PHY 4a101000.mdio:01 not found [ 38.321179] net eth0: phy 4a101000.mdio:01 not found on slave 1 [ 120.526713] INFO: task kworker/u:1:21 blocked for more than 60 seconds. [ 120.533886] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 120.542333] Kernel panic - not syncing: hung_task: blocked tasks [ 120.548755] [] (unwind_backtrace+0x1/0x9c) from [ Hi! I'm trying to compile a neon assembly file and call it from my c++ program. I'm getting illegal instruction or segmentation fault depending on how I configure the gcc&gas command line. Do anyone here know a simple getting started example or something to help me get the basics settings right? Oct 04 17:50:17 how do you call the assembler file? Oct 04 17:50:51 I call it from my c++ program. Oct 04 17:51:15 It is declared as extern "C" in the cpp file. The asm file exposes a .global function-name Oct 04 17:51:38 <_av500_> gdb? Oct 04 17:52:25 gdb only shows the address it fails on, which is in the middle of an assembly instruction in my assembly code. Oct 04 17:53:45 Im using these g++ compiler settings -march=armv7-a -mfloat-abi=hard -mcpu=cortex-a8 -mfpu=neon for my beaglebone black. Oct 04 17:55:09 also for gas i use -mfpu=neon Oct 04 17:55:52 So if anyone have a working super simple example I would really appreciate it! Oct 04 18:05:27 matnler are you sure your asm code is correct? Oct 04 18:05:45 No. Oct 04 18:05:59 mantler and you could try to inline the asm code for now Oct 04 18:06:08 Well, the code yes. but not the stuff before like settings. Oct 04 18:07:39 <_av500_> and it fails on a neon instruction? Oct 04 18:07:50 <_av500_> you can still see where it fails and why Oct 04 18:08:55 No, it fails on, as it seems, any instruction. Oct 04 18:10:04 I have tried a function with only a single instruction "bx lr" //return from function Oct 04 18:10:16 That fails to. Oct 04 18:10:34 So thats why I'm thinking it is my compiler settings for g++ and gas. Oct 04 18:10:46 http://www.ibiblio.org/gferg/ldp/GCC-Inline-Assembly-HOWTO.html Oct 04 18:12:15 i have tried the inline assembly and I have successfully compiled and run code with that. Now I want to get not inline to work also. Oct 04 18:13:10 okay Oct 04 18:14:52 <_av500_> http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0203j/Chdebdjg.html Oct 04 18:15:43 <_av500_> has examples Oct 04 18:17:33 Thanks. Oct 04 18:19:00 hm page 4-13 yes Oct 04 18:20:33 Sadly, that is using the armasm and not gas. Oct 04 18:43:45 might anyone have experience installing osmo-trx on BBB? everything installed fine but when i run it, it says: terminate called after throwing an instance of 'std::bad_alloc'....any ideas? Oct 04 19:13:01 <_av500_> gdb is an idea Oct 04 19:18:52 _av500_: not quite sure how to diagnose it with gdb Oct 04 19:19:57 <_av500_> find out where it crashes Oct 04 19:20:02 <_av500_> and why Oct 04 19:20:33 <_av500_> no? Oct 04 19:38:48 run it with gdb, when it crashes, type i s Oct 04 19:38:56 and hope it was built with symbols Oct 04 19:59:48 mantler: gas documentation should be pretty easy to find. there are tons of examples Oct 04 20:03:29 http://www.element14.com/community/community/designcenter/single-board-computers/next-gen_beaglebone/blog/2013/06/01/bbb-neon-and-making-tintin-bigger Oct 04 20:03:38 this one has inline assembly with c Oct 04 20:04:21 with c++, it shoudn't change the inline syntax atleast. Oct 04 20:05:55 i wonder if there is performance overhead when calling arm assembly from c++....never profiled that. Oct 04 20:06:26 whenver i coded c++, it is for opengl stuff, so, no idea. Oct 04 20:27:52 nyt-: hm, so i see libraries from libc and libstdc++....http://pastebin.com/9nFdGbZG Oct 04 20:32:57 top Oct 04 20:40:52 hitlin37: I wish there was lots of examples... Inline works for me, but not pure assembler files. Thats why I think it is a compiler flag missmatch or something. Oct 04 20:54:16 Yes! It works! Oct 04 20:54:50 There was some kind of missmatch with the compiler directives... Oct 04 20:55:23 Now there are so many I have to start removing them one by one to find the one that made it work. Oct 05 00:33:49 I am new to BBB and have a little Linux experimentation under my belt. I have figured out (from much Google work!) how to automatically mount my 8gb microSD card on bootup. I plan on using this storage for programming resources (files, pictures, etc.) as I go. My question is this: Is there a normal convention as to WHERE to mount this mass storage so that it will be Oct 05 00:33:49 available to all users? (I have 2 logins: root, and my normal non-root). Thanks! Oct 05 00:38:22 Not really, though subdirectories under either /mnt or /media are common. if the data on the card will be volatile, one could mount it at /scratch. As for all user being able to access that, that is more of an issue in setting the permissions correctly than any mountpoint in the file tree. Oct 05 00:47:46 ^ bingo. Ubuntu itself usually typically automounts under /media/ Oct 05 00:47:59 when I hand-mount things, I do it in /mnt Oct 05 00:49:24 If it will indeed be used for program files, it may make more sense to move the user directories to it, and mount it at /home. Oct 05 00:55:00 "Media" does seem to be a logical place. Thanks! Oct 05 00:56:08 /media is "media" in the sense of storage media, not in terms of entertainment, though one could see where the confusion may lie. Oct 05 00:56:30 That is how I understood it Oct 05 00:57:05 Ah, yes, I see now your comment did not contain the word "not". My mistake. Oct 05 01:19:26 Ok, I modified the "auto mount" to load it at "/media/microSD". From "root" I can read/right/execute the card. But, for some reason, I can't change the permissions to allow my non-root login to "write" (i.e. add new directories) to the directory. I have tried: "chmod +w microSD" and "chmod 777 microSD" and neither will allow a non-user to add to or change the directory. Am Oct 05 01:19:26 I missing something? Oct 05 01:22:17 Sorry, I meant "Neither will allow a non-ROOT to add..." Oct 05 01:27:43 You need to have a umask (and maybe a gmask) on the actual mount as options. Oct 05 01:30:04 kewvoq: well, either there's some memory/stack overflow issues, or there are no symbols in that app to debug Oct 05 01:30:09 kewvoq: compile with debugging symbols Oct 05 01:31:54 agmlego: Huh? When I do "mount --help" I don't see "umask" or "gmask" options. Oct 05 02:27:31 PGBeagle: Are you mounting manually, or using fstab? Oct 05 02:28:36 Also, the abbreviated usage page tools print in response to -h,--help is generally not the full story; that is what you get from manpages and infopages. Oct 05 02:30:42 agmlego: I have a mount script that says: "mount /dev/mmcblk0p1 /media/microSD" and I have it run in the bootup sequence. Oct 05 02:32:33 ... Oct 05 02:32:41 That would be the wrong way to go about that. Oct 05 02:33:01 I suggest reaqding up on the fstab file in /etc Oct 05 02:34:46 agmlego: Ok, thanks! Will do more research. Now I have another path to discovery! Oct 05 02:35:07 Yup. ;-P **** ENDING LOGGING AT Sun Oct 05 03:00:01 2014