I'm following Amazon's guide to connect a Raspberry Pi W to their Kinesis Video Streams service from the link below:
https://s3-us-west-2.amazonaws.com/kinesis-video-streaming/kinesis-video-raspberry-pi-getting-started.pdf
However, when I run the sample application using this command:
./kinesis-video-demo
The console outputs the following and ends the process:
Begin streaming video...
INFO - Initializing curl.
Illegal instruction
I believe the application ends due to an openssl error which is a dependency for the "kinesis-video-demo" app. The openssl github page says that an "illegal instruction" may occur from the no-sse2 parameter when installing openssl as seen in the 'INSTALL' file from their github page.
https://github.com/openssl/openssl
Is there a certain way I need to install openssl on a Raspberry Pi W for this application to work?
I had got this same issue. However, after changing to Raspberry Pi 3 model B, it is working good.
Related
I am using IOT grengrass to deploy lamda function for my IOT core device - Raspberry Pi 3. I have completed all the necessary steps regarding the same. While starting Daemon from raspbery pi 3 and deploying from AWS greengrass console (using group V1), i am getting this below error,
"Deployment 6cc8251b-f006-44f6-bebc-050da8d84bd7 of type NewDeployment for group 4fd1b5be-8b43-4734-a805-266d7482b81a failed error: process start failed: failed to run container sandbox: container_linux.go:380: starting container process caused: exec: "/lambda/greengrassSystemComponents": stat /lambda/greengrassSystemComponents: no such file or directory"
I using AWS IOTfor first time, so not sure why this error is comimg. Please help me.
Thanks
I'm not using NixOS but I wrote a flake that I'm using to generate a dev shell to build a Rust project (this is essentially just the audio example from the Bevy repository). My issue is that I encounter the following error when attempting to run the project in the dev shell:
$ nix --extra-experimental-features nix-command --extra-experimental-features flakes develop
bash-4.4$ cargo run
Finished dev [unoptimized + debuginfo] target(s) in 6.62s
Running `target/debug/audio`
ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: NoDevice', /home/a/.cargo/registry/src/github.com-1ecc6299db9ec823/bevy_audio
-0.5.0/src/audio_output.rs:22:67
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
bash-4.4
One of the dependencies of the project is the Bevy crate which requires ALSA, so I'm assuming the issue is because the ALSA package exposed by the dev shell is probably misconfigured. I use PipeWire on my actual system (I think it also uses ALSA as a backend) and I tried adding ALSA and PipeWire as one of the buildInputs for the flake, but I'm not sure how I'm supposed to configure these within the dev shell. According to this issue on the Bevy repository, the usual fix for this issue, at least for Arch-based distros, is to install the pipewire-alsa package. I'm not sure what the equivalent of doing that is in the context of a Nix dev shell is though, since there is no pipewire-alsa package in nixpkgs that I can add to my flake. So with that said, how should I go about configuring ALSA or PipeWire in the dev shell?
I've been writing some kernel module recently. For some modules everytime i insert them or remove them a huge kernel trace is shown on screen. The errors are somewhat like
ERROR: Bad EIP value.
or
ModuleName is tainted.
What does this imply. Any help is appreciated.
The Extended Instruction Pointer exists in x86 processors, but is somehow related to a missing WiFi driver, it seems:
Yesterday I could not reach this site and read your reactions, so I
experimented with several Linux versions: Xubuntu, Slacko-Puppy 5,4
Firefox ,Puppy Akita Beta and LinuxMintMaya. And with all the same
result, i.e. no result,
But in the last install - LinuxMintMaya - I discovered the problem,
which is be found here: http://www.linuxmint.com/rel_maya.php It
tells:
Boot hangs on systems using b43 wireless cards
So after entering this command
Code: sudo apt-get install firmware-b43-installer
LinuxMintMaya works.
To boot, the Mint page says:
An upstream issue in the kernel prevents Linux Mint 13 from booting on
computers with b43 wireless cards. If you're in this situation, try
the following:
To boot the live DVD, choose the "Compatibility mode" or add the
following kernel argument to the boot options: b43.blacklist=yes
Install Linux Mint on the hard drive If not present already, in Grub,
modify the boot options to add: b43.blacklist=yes Install the b43
firmware on the system
While there's no official support for Meteor.js on ARM architectures, I'm disappointed that my (new and lovely) Chromebook can't run Meteor within Unity (ubuntu 12.04 LTS) chroot via crouton - http://goo.gl/ilSFSz
I've tried the suggestions for the Raspberry Pi ARM here - https://github.com/meteor/meteor/issues/442 - and for the most part, I'm using node v0.8.24 outlined here - https://github.com/meteor/meteor/blob/devel/scripts/generate-dev-bundle.sh - and the latest error I received was a Assertion Error: Unsupported architecture when building mongodb here, line 298 in ../mongo/src/third_party/v8/SConscript:
processor = env[PROCESSOR_ARCHITECTURE]
And ARMv71 isn't listed, so I wondered if anyone has found a way to get Meteor.js to run natively on their armv71 chromebook? I would prefer not to use cloud9 or nitrous.io, or amazon ec2 to do meteor development on the Chromebook. Thanks in advance.
If you know sh or bash you could try modifying the meteor install script for the ARM architecture.
As I know from other users, our meteor universal arm fork should work for you.
https://github.com/4commerce-technologies-AG/meteor
Cheers
Tom
I am new to blackberry development and ran into this problem several times and cannot find a solution.
When I try to run an empty cascades project just with a simple HelloWorld label I get the following error
Deployment Failed: Info: Sending request: Install and Launch
Info: Action: Install and Launch
Info: Debug native: on
Info: File size: 190910
Info: Installing com.example.HelloWorld.testDev__HelloWorld7d1bfe91...
Info: Processing 190910 bytes
I'm using Momentics, VMware running BB10 Dev Alpha Sim and followed all the instructions here. http://developer.blackberry.com/cascades/documentation/getting_started/setting_up.html
I made sure my build config is set to Simulator-Debug and not even the example projects are able to run on the simulator.
Edit: I am not sure if this bit of info helps but when I try to run the application, the Progress hangs at 91% before the error dialog appears.
May be you are not setting the development Mode (like current Development Mode Simulator or Device) . I also getting the issue that Project Compile but not able to run on virtual Machine , today I sort the issue . check out the link http://supportforums.blackberry.com/t5/Native-Development/BB10-Native-Cascades-SDK-not-connecting-to-Alpha-BB10-simulator/td-p/1719865/page/5