Yes - same problem here; I just added the echo $SLOTS script to
/etc/profile to walk around all this.
--
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
Hy,
I´m having a very similar problem. I am using the current version of ubuntu
for BBB (Ubuntu 14.04 LTS (GNU/Linux 3.8.13-bone47 armv7l)) and tried to a
device tree overlay with this guide for the exact same cape:
I think sudo -S command might work too, but have not tested this myself
yet.
On Fri, Apr 25, 2014 at 4:51 AM, Charles Steinkuehler
char...@steinkuehler.net wrote:
On 4/25/2014 5:37 AM, Andreas Tauböck wrote:
and I get a permission denied when i want to add it manually with:
On Mon, Nov 18, 2013 at 1:21 AM, Jesper We jes...@seventhwave.se wrote:
I tried to replace qemu 1.5 with a locally built qemu 1.6.1, and run
build_image.sh.
This gives me:
Cloning into '/opt/boot-scripts'...
qemu: Unsupported syscall: 374
remote: Counting objects: 65, done.
remote:
Robert, after much headscratching at the various Angstrom download and
instruction pages, which seem to be in various stages of bit-rot, I
switched my attention to your stuff, which seems a lot more well maintained.
I'm now using omap-image-builder to create an image. I have chosen to work
On Sun, Nov 17, 2013 at 9:43 AM, Jesper We jes...@seventhwave.se wrote:
Robert, after much headscratching at the various Angstrom download and
instruction pages, which seem to be in various stages of bit-rot, I switched
my attention to your stuff, which seems a lot more well maintained.
I'm
Staring a bit more at the build logs I think I see an error from the
build_image.sh run that could be causing this.
Towards the end, qemu crashes while doing something with the boot scrips,
see log excerpt below.
I'm running Ubuntu 13.10 with version QEMU emulator version 1.5.0 (Debian
Actually, staring a bit more at the build logs I see an error from the
build_image.sh run that causes both my problems.
Towards the end, in chroot.sh/startup_script(), qemu segfaults while git
clone-ing the boot scrips, see log excerpt below.
I'm running Ubuntu 13.10 with version QEMU emulator
I just read this thread and thought wow, this is the same set of
experiences I've had over the last couple months.
OK, I have read this
threadhttps://groups.google.com/forum/#%21msg/beagleboard/Iem_mHknIUM/buwAqagYukwJtwice
now, and I still fail to see any real solution in between the
Really :-) ? This is all it takes to make it work as advertised? Makes me
wonder why that is not in the default distribution...
On Friday, November 15, 2013 8:56:01 PM UTC, RobertCNelson wrote:
You can also just disable the kernel config switch for building
firmware inside the kernel. Then
Yes it seems lots of people are in the same situation. OK, so despite all
the halabaloo about Device Tree Overlays you still need to build a custom
kernel to add a new cape at boot, is that so?
I kind of thought the whole point was getting rid of that ;-)
--
For more options, visit
On 11/15/2013 07:08 AM, Jesper We wrote:
Yes it seems lots of people are in the same situation. OK, so despite
all the halabaloo about Device Tree Overlays you still need to build a
custom kernel to add a new cape at boot, is that so?
I kind of thought the whole point was getting rid of that
OK, I bit the bullet and went through the custom kernel build process.
Put my .dts in kernel/firmware/capes/ and added it to the
kernel/firmware/MakefileDTO
...and so it works.
Conclusion: The reason the Circuitco Capes work is that they are already
compiled into the standard distribution.
The
On Fri, Nov 15, 2013 at 2:52 PM, Jesper We jes...@seventhwave.se wrote:
OK, I bit the bullet and went through the custom kernel build process.
Put my .dts in kernel/firmware/capes/ and added it to the
kernel/firmware/MakefileDTO
...and so it works.
Conclusion: The reason the Circuitco Capes
14 matches
Mail list logo
