As of 2020, the only thing that works for me is:
sudo ifdown --force wlan0
sudo ifup wlan0
Tested it in the following way:
Edit network ssid and psk in /etc/wpa_supplicant/wpa_supplicant.conf
Followed by sudo ifdown --force wlan0
Followed by sudo ifup wlan0
The tests were carried out on Buster-lite.
It has been tested atleast 5 to 7 times with time ...
OpenWrt is a OS/tools that you can write on the SD-Card and run on your raspberry pi. In this link, you can find the image file and some explanation.
It's easy to configure the OpenWrt. All you need is configure the eth0 or br0 (by default) as the WAN port and connect your modem port (internet) then share it by wlan0.
It can be your simple firewall ...
As far as I know specificaton of netboot is to use the tftp (Trivial File Transfer Protocol) in general to get the boot image from what server ever. Usually you install a tftp server for it but it may be possible that a server application encapsulated this protocol and you don't have to install a tftp server. An example of such a program is dnsmasq.
I ran into this problem recently, and it turns out the issue was that I was only sudo-ing one of the chained commands I was using.
I was using sudo apt-get update && apt-get install -y libssl-dev libffi-dev python3-dev build-essential
But I should have been using sudo apt-get update && sudo apt-get install -y libssl-dev libffi-dev python3-...
I just wanted to say a big THANK YOU to Andy Johnson and his Single/Dual link DVI-D suggestion.
My PI4 would never connect to a Sony SDM monitor despite all config files changes I could find on forums. After ordering a new HDMI/DVI cable SINGLE LINK, it worked immediately like a charm.
O help, just found out here what went wrong.
I've been having trouble with this too.
The answer was inside this command:
sudo wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant.conf -iwlan0 -d
I had placed the ssid and psk names between ' 'signs like ssid='my-network-ssid'
Changing it to "my-network-ssid" made it work right away.
And besides: raspi-...
Just some general information first to understand the different setups. In the first setup you have an access point on the RasPi with interface wlan0 that can other devices connect by WiFi. The wired interface eth0 is connected as uplink to the internet router, no matter if it also has an access point. That isn't used in this case.
The RasPi is an access ...
budgie-desktop is available from the default Raspbian repository. This means it should be installable without worrying about dependencies about other needed packages. This is why we use the package manager environment (apt, apt-get, dpkg etc.). If you look at the description of the package you will find:
rpi ~$ apt show budgie-desktop
--- snip ---
You are using Raspbian. It does not support NetworkManager. At a first glance at the log it seems that default dhcpcd networking is fighting against NetworkManager. Maybe the Home Assistant installation isn't compatible with Raspbian and break its networking. Disable NetworkManager and look if it fix the problem.
One idea is to handle transitions on the server. Give your clients a single endless video stream to play, and push data from different files in that stream. That's how info-beamer seems to work. I think VLC should be able to push a complete playlist to an HTTP stream as well, but I haven't tried it myself.
Of course, streaming only works while you're online....
Kernel logs (dmesg) are a good place to start if you suspect a hardware problem. For WiFi connectivity issues, running wpa_supplicant manually with -d and -f options is quite helpful too.
There are tons of scripts already written (example) which periodically check for network status and force a reconnection if an anomaly is detected.
Looking at the log you ...
1. DHCP: Use Static IP:MAC Address Mapping
If your Pi is not maintaining a persistent IP address, you can create a static IP:MAC address mapping on the DHCP Server (probably your router). Then, every time the router see's your Pi's MAC address, it will assign the same IP.
2. DHCP: Wrong IP Pool being used by DHCP Server
If your Pi is being ...
Kazam is another great screen recorder. It's graphical, easy to use, and has a ton of features.
To install it:
1) Open a terminal (click on the raspberry icon in the task bar, go down to Accessories, and then click on Terminal)
2) Type in sudo apt-get update then sudo apt-get install kazam
3) To run it, you can launch it from the taskbar (you'll find it ...
recordMyDesktop is here for you. It captures what you are watching on the screen and also saves all audio input/output.
You can use it by the terminal and also it has a GUI like the image below:
sudo apt-get update
Install the package:
sudo apt-get install recordmydesktop
The first step (which in retrospect didn't help) is to configure your bootloader with POWER_OFF_ON_HALT=0 and WAKE_ON_GPIO=1 (I think the latter forces the former). Your RPi will never be fully shut down in this way, but it won't power down during a reboot either.
The next thing you could try is updating the bootloader with sudo rpi-eeprom-update, and ...
I want to record audio from either the OS or a specific program.
You can store all speaker output by this procedure.
Install these packages:
sudo apt-get install pulseaudio-utils lame
Search for your speakers and tap into your speaker's monitor stream:
pacmd list-sinks | grep -e 'name:' -e 'index' -e 'Speakers'
Find the monitor stream by:
One possible problem may be the DHCP client. It will always get an ip address and network configuration (DNS server, gateway, default route etc.) on boot up. When the lease has expired the DHCP client may have a problem to renew it. If it cannot renew its ip addres then it will configure a link-local ip address 169.254.197.68/16 which does not fit to you ...
Developer of RaspAP here. The project does not lock the file system or interfere with other services. I installed mosquitto after RaspAP, enabled the service and rebooted. Confirmed it's active and listening on port 1883:
sudo netstat -ltnp | grep -w ':1883'
tcp6 0 0 :::1883 LISTEN 405/mosquitto
Check the output of mount -l and ...
I resolved. First i connect my device ( pc or mobile device ) at my VPN and i connect with tor. In this case, all my tor request will be stored into packets of VPN tunnel and will be exit on the TOR network
I was successful adding a line like this to my /boot/config.txt:
# increase power for display
Please see Video options in config.txt - Raspberry Pi Documentation.
You need to reboot after that change.
Usually the entry point to your private network is the public ip address of your internet router with port forwarding. From the private network out to the internet there is a Network Address Translation on the internet router used so all external destination devices (e.g. web server) only see this public ip address as source ip address no matter what client ...
I resolved the problem. It was a misconfigured /etc/fstab file. For whatever reason, the pi refuses to boot when there is an error in this file. I was able to repair the problem by mounting the SD card on a different Linux machine and edit /etc/fstab there. I only managed to figure it out by borrowing a monitor and seeing the messages displayed during ...
I use rtorrent as a non-interactive tool. I just copy *.torrent files into a directory and rtorrent automtically picks them up for download/upload.
I use tmux and rtorrent (not screen) on Ubuntu 19.10 (if that matters)
The chromium-browser layer and the problem I was having where the taskbar didn't pop up from below because the windows covered it. I just edited the openbox config file (see source on how)
<application name="panel" type="dock">
<application name="panel" type="dock">
This is a combination of M. Rostami's answer and my reflections on his answer, which I found cumbersome to add as comments.
NB: Your question shows you know how to find your public IP address and the internal address of your Pi. I've included directions here in the hope that they will help others.
On your Pi, set up SSH on the default port number, port 22....
Port forwarded ~ 21 both TCP and UDP
It's actually forward packets to port number 21 which is the default port of FTP. You must change it to port number 22 on your router/switch.
If you are stubborn about changing the default port of SSH which is 22 to another port number, take note that you can set the SSH default port to 21 but the FTP client would be ...
You can install it manually by:
dpkg -i php7.4_7.4.1-1_all.deb
It gives you a lot of dependencies which you must install before this package. It's the hardest method. Look at the second method which is much easier.
Ensure your ...
You can set a special SSID (WiFi network) to the wpa_supplicant.conf:
Add these details of your SSID to that config file like:
You can find more about it here.
I do not want to edit wpa_supplicant.conf every time it discover
Provided that the SSH server at the PI is actually configured to listen on port 21 instead of the default 22, and that the network public IP address doesn't change.
Then you should just SSH to the public IP address of your network.
>ssh 188.8.131.52 21
login the same way as you do when only using the local (home) network.
Using no-ip or dydns can help ...
Here's a TESTED and WORKING specimen config from my MikroTik router that you can use as a model for your own router.
chain=dstnat action=dst-nat to-addresses=192.168.0.6 to-ports=21 protocol=tcp in-interface=ether1-Gateway dst-port=60000 log=no log-prefix=""
"ether1-Gateway" is my connection to Internet
"dst-port=60000" is an ...
First the ssh port is usually port 22 but it can be changed and secondly you only need tcp not udp. Another issue that can crop up is ensuring the pi will accept connections on port 22 from outside your LAN which can be achieved using UFW https://wiki.ubuntu.com/UncomplicatedFirewall
Make sure you set a strong password or better still use SSH keys as you ...
It was the Pimoroni OTG cable that had been damaged....two of the pins inside the larger socket had been dislodged when i changed the keyboard to a wireless keyboard ....dongle thingy just before the very first boot of the zero. Hope this helps someone else to avoid the frustration.
You can get the serial number with:
rpi ~$ cat /sys/firmware/devicetree/base/serial-number
So the command to call chromium on the command line with serial number resulted in:
rpi ~$ chromium-browser --incognito --noerrdialogs http://url.com?sn=$(cat /sys/firmware/devicetree/base/serial-number)
You can install Screen Configuration with sudo apt install -y arandr.
What you really want to do is see what you uninstalled. Easy: This command shows you what is in the apt-get log file:
Still missing something? You can quickly compare what your desktop looks like vs default Raspbian using my vdesktop tool. Essentially it ...
if you are running a Raspbian Buster image it is easy to find the version in the image of the new 64 bit /boot/kernel8.img. You can just use:
rpi ~$ strings /boot/kernel8.img | grep 'Linux version'
Linux version 4.19.93-v8+ (dom@buildbot) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9)) #1290 SMP PREEMPT Fri Jan 10 16:51:04 GMT 2020
Do NOT attempt to load ANY modules.
Add dtparam=watchdog=on to config.txt and Device Tree will load the module.
NOTE you also need to enable the watchdog service.
I found that the issue is the .asoundrc file that I setup for the pi user, to define the default ALSA devices for input and output. The .asoundrc definition I used to use for previous versions of Raspbian is:
For 0-10V DC Dimming, 0V does not equate to 0 light output. The dimming ballast or drivers are rated for a 10-100% or 1-100% dimming range. To turn the fixture completely off, you also need a relay that kills power to the driver or ballast at the bottom end of the 0-10V range.
If you are unable to see video signal and unable to connect RPi4 via VNC and SSH, I would try to connect the SD card to computer and reset /boot/config.txt back to default or use second SD card with default OS and screen settings to see if that help to make RPi booting and sending a video signal.
Regarding 4K (UHD) not working, check the following things:
Still the same result, but the SD card partition changed when I check it in my PC.
I am not entirely sure what u mean but I think you mean that the micro sd's files or format have changed if so I suggest you check out https://www.raspberrypi.org/documentation/installation/noobs.md and if you find some iso of noobs or raspian you can see https:/...
You didn't run this command by root user. Therefore, this user doesn't have any access to update the repository list.
Try these commands:
sudo apt-get update
Or, run it directly as root user:
Then, fire apt-get update.
Always have multiple known good quality power supplies, and good cables (high current rated, and preferably short) , and try several of them first.
Also know that power supplies which worked perfectly for year(s) can an do go bad -- they still look like they work in majority in cases, but at higher load their voltage drops below 4.75V even for a shor time, ...
It is possible that your SD Card gets weak over a long time. The problem is that SD Cards doesn't report read/write errors to the operating system. It could be that you can flash it but then it looses some bits and bytes after some days possibly still the same weak cells so the symptoms are always the same. You should consider to use a new SD Card.
The network configuration is configured in /etc/dhcpcd.conf. Just add a line at the end of this file:
This is only an example. Of course you have to use the ip address of your gateway. This will permanently save the gateway address.
But this is only a workaround. Usually the gateway/router address is gotten from the DHCP server ...