Type in nvcc –version from your Jetson Nano terminal is the sure way.
If the nvcc is missing, it could mean that the jetson-toolkit were not installed, or the binaries was not added to your session.
The commands to reassociate.
Continue readingAfter forcing the Jetson OS (based on the ubuntu 18.04) to have Python 3.8 running. After having the JetPack 4.6.3 installed in the Jetson Nano Jetson OS.
When attempting to install TensorFlow 2+ manually in the Jetson Nano based on Official TensorFlow for Jetson Nano! – Jetson & Embedded Systems / Jetson Nano – NVIDIA Developer Forums
Or running the pip3 install command:
sudo pip3 install --pre --extra-index-url https://developer.download.nvidia.com/compute/redist/jp/v46 tensorflowAfter a long time installing all the dependency for TensorFlow. A dreaded error message will occur.
ERROR: Failed to build installable wheels for some pyproject.toml based projects (h5py)
To understand the error, scroll up to read what are the error.
Continue readingPart number used for the board in the seeed reComputer J1020 connecting to the nVidia Jetson SODIMM module is reComputer J202 – Carrier Board for Jetson Xavier NX/Nano/TX2 NX.
Based on the spec sheet in the web site above, the J202 carrier board. Can be used to host the Jetson Xavier NX, Jetson Nano and Jetson TX2 NX.
Other than the Jetson Nano, any other Jetson module that is compatible with the J202 carrier board will requires a heatsink with active fan.
Recommended heatsink with active fan Manufacturer Part Number (MPN)s are as follows:
ATS-NVA-2781-C1-R0
114992687
Adding SSD into will requires M.2 nvme into the reComputer J1020, this post is based on Memory Expansion | Seeed Studio Wiki
The documentation is a bit vague on the NVMe SSD to be used other than very basic instructions. However, in my attempt it is smooth.
The SSD that was chosen as the expansion storage is the Kingston NV2 PCIe NVMe M.2 500GB. The J1020 requires the SSD to be M key.
For the folks that are impatient, the POC of DeepSeek is here KarMeng / deepseek-simple / localdev — Bitbucket
Continue readingThis post is based on reference to Use instance metadata to manage your EC2 instance – Amazon Elastic Compute Cloud
Metadata is a powerful tool for AWS users. It allows users to make query of data describing EC2 instances, and making a self reference API call.
By default any linux AMI will have curl build in, hence using of metadata will be simplified.
One of the best test case is automating input into shell script that will requires a lot of user prompt is automating or at least make configuration of setting up openvpn using AWS Lightsail easier.
!#/bin/bash
sudo chmod 777 ./openvpn-install.sh
sudo ./openvpn-install.sh << INPUT
y
1
1
11
n
n
client
1
INPUT
sudo cp /root/client.ovpn /home/ubuntu
sudo chmod 777 /home/ubuntu/client.ovpnAbove shell script will cause the openvpn-install.sh to fail in AWS, as the script does not provide public and local ip of the instance.
Below script are including the AWS Metadata
!#/bin/bash
TOKEN=`curl -X PUT "http://169.254.169.254/latest/api/token" -H "X-aws-ec2-metadata-token-ttl-seconds: 21600"`
PUBLICIP=`curl -X GET "http://169.254.169.254/latest/meta-data/public-ipv4" -H "X-aws-ec2-metadata-token: $TOKEN"`
LOCALIP=`curl -X GET "http://169.254.169.254/latest/meta-data/local-ipv4" -H "X-aws-ec2-metadata-token: $TOKEN"`
sudo chmod 777 ./openvpn-install.sh
sudo ./openvpn-install.sh << INPUT
$LOCALIP
$PUBLICIP
y
1
1
11
n
n
client
1
INPUT
sudo cp /root/client.ovpn /home/ubuntu
sudo chmod 777 /home/ubuntu/client.ovpnBy adding the metadata the ovpn file will be populated with correct IP.
AWS Metadata allow automation to be made simpler by running scripts that requires self-reference metadata to configure newly booted up EC2 instance(s).
This post is based on terraform tutorial Build infrastructure | Terraform | HashiCorp Developer
Make sure AWSCli being installed and configured correctly (aws configure). Make sure IAM user are configured with AWS role, AWS Access key ID and AWS Secret Access Key.
Use the ami catalog, to determine the ami ID, then after make necessary changes run the init
To solve this VPC and subnet needs to be created first.
Make small change to the EC2 instance of terraform file.
Rerun the terraform init, terraform plan, terraform validate before rerunning terraform apply, then type yes.
To clean up the experiment to avoid paying more, start by destroying the instance then the VPC.
Terraform code is available at https://bitbucket.org/KarMeng/terraform_aws
All the experience in this post is based on Install Terraform | Terraform | HashiCorp Developer
Feels like running ansible but simpler, as the tutorial of quickstart runs on docker engine.
Further confirmation running browser to browse the site.
Have added changes to incorporate both generating AWStats logs and starting up AWStats service in a single docker compose file at KarMeng / docker_awstats — Bitbucket
This is an easy and simple example that beginners can use to generate web statistics using AWStats.
Required softwares:
Hashicorp Vagrant 2.4.1
Oracle VirtualBox 7.0.14
The first error that will be face on get go is the error “kibana Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap” and exiting error “dependency failed to start: container docker-es03-1 exited (137)”.
Searching mentioned error on google or the internet will yield result that advice swap memory and memory limit hit.
Continue reading