I've got a Buster box (10.2) and I'm investigating some system freezes. While going through that, I think I'm not getting the OOM output in the syslog. For instance, running
tail /dev/zero which is known to trigger it, the only output I get is in the SSH shell:
tail: memory exhausted
(zsh). But nothing is mentioned in the dmesg (or journalctl fwiw) outputs, whereas on my Arch box the very same command does indeed result in a dmesg line. Why is that? Is perhaps some setting missing?
my aim is to use my Raspberry Pi 4 as a music box with Spotify. I have installed Vivaldi Browser and it already starts automatically when I start my Raspberry, but still, Spotify is not the standard page when I open it.
I have chosen the way to add a vivaldi.desktop file in /etc/xdg/autostart with this content:
[Desktop Entry]
Type=Application
Name=Vivaldi
Comment=Vivaldi with Spotify
NoDisplay=false
Exec=vivaldi
It works so far, but I would need more parameters under Exec to:
Would be happy if anyone can help me. Thanks!
Maria
I've got a RPi 3b+, usually I do a backup of the SD card to my Mac using sudo dd bs=4m if=/dev/rdisk2 of=raspbian.img, which creates an image file of the whole card. The RPi SD card used to be 16gb, but as that card crashed I restored a previous backup to a spare 64gb card I had laying around.
If I run the same command for backups now though, dd naturally wants to create a 64gb image file. But since the card only contains 16gb of stuff, I'd like to only backup the part that's being used. Otherwise it won't fit on to a new 16gb later (also I don't have that much hdd space available on my Mac).
It seems the SD card has 2 partitons, boot (46mb) and the actual RPi linux partition 15.9gb). Is there a way to only backup these two partitions and disregard the 48gb of unused / unpartitioned space? The result needs to be a single image file (to be used with Etcher for restoration).
I'm using Raspbian Buster and I'm using my Raspberry Pi headlessly. After I log in to SSH when I use a new OS image, I always change the password from the default one. Now, when I change my password, everything works successfully but the password doesn't really change, so I have to use raspbian when I SSH in next time, even when I've changed the password to something else. How do I change my password so it's recognised?
I just done a fresh install of buster on a 3b+ on my home network. The box has been working fine for years running wheezy. Box isn't connected by ethernet.
Trying to set up Localisation prefs and the Wifi Country is greyed out and the Network icon on the top-right of desktop says no interfaces found.
Have tried setting the country name in raspi-config options but get an error saying N2 error.
Have tried:
nano /etc/wpa_supplicant/wpa_supplicant.conf
and edited to read:
country=GB
_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
network={
ssid="<network_ssid>"
psk="<network_password>"
}
but still can't find wifi networks or change Wifi country in preferences.
Anyone help? Thanks
I just bought a wifi dongle: TP-Link TL-WN823N, because it was supposed to work out of the box with the rasberry.
So, I have tried raspbian and now I am trying with OSMC.
First of all, if the raspberry is turned on and I connect the dongle it reboots. But it seems that is ok. So, here we are ok.
But then, booting the RPi with the dongle connected to the USB I got no wifi.
(Note: all the output is the same for my actual os (OSMC) than for the raspbian)
$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
Then, I just check connected usbs:
$ lsusb
Bus 001 Device 005: ID 2357:0109
Bus 001 Device 004: ID 046d:c534 Logitech, Inc.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp. LAN9500 Ethernet 10/100 Adapter / SMSC9512/9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I know that the guy with no name: Bus 001 Device 005: ID 2357:0109 it is the wifi dongle. But I have no clue how to make it recognize.
I tried this: https://github.com/pvaret/rtl8192cu-fixes
But it doesn't work.
I'm struggling to this topic for a while.
Enviroment:
If I try to import RPi.GPIO from GPIOi receive the message No module named GPIO. So, how can I include this package, or is there a known better concept? During the development process I wanna use some unit tests to keep a good quality of my code.
It would be nice to be able to use raspberry wifi to receive ESP-NOW messages directly and eliminate another ESP-to-PI device to manage.
I think this is where @ Alexandr Zarubkin was going but I don't have the "status" here to ask/comment on his post: https://iot.stackexchange.com/questions/2345/802-11-action-frames-send-and-receive-in-software
I am new to Raspberry Pi and Linux. I followed all the setup guides and have a 4" touchscreen with a case. I downloaded MPI4008-4.0inch-2019-07-10-raspbian-buster.img and flashed it to SD. I had to add wpa_supplicant.conf to the boot so it would connect to wifi on startup. Everything worked fine and wifi came up. Used rasp-config to set local and changed the password, rebooted everything fine wifi came up. Next steps update and upgrade. I used sudo apt update then sudo apt upgrade. No problems on the update but some errors on upgrade, so I did sudo apt upgrade -f. It finish no errors so rebooted now it comes up but no wifi try ethernet cable no connection. I have read many posts and tried almost everything I could find but no internet. When I try rpi-update I get:
curl: (7) Failed to connect to raw.githubusercontent.com port 443: Connection timed out !!! Failed to download update for rpi-update! !!! Make sure you have ca-certificates installed and that the time is set correctly
Update: I downloaded 2019-09-26-raspbian-buster.img and flashed it to SD. I ran update and upgrade with no errors. After reboot no wifi when the cursor is over the double red x icon it says: dhcpcd not running.
I tried to manually start dhcpcd by using sudo dhcpcd interface the output was: main: control_open: connection refused interface: interface not found or invalid dhcpcd exited
pi@raspberrypi:~ $ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet6 2601:340:c580:a350::2f6a prefixlen 128 scopeid 0x0<global>
inet6 2601:340:c580:a350:e3a6:f851:b5c:c7d5 prefixlen 64 scopeid 0x0<global>
inet6 fe80::69d2:1aa8:83f1:5e1f prefixlen 64 scopeid 0x20<link>
ether dc:a6:32:37:e4:ce txqueuelen 1000 (Ethernet)
RX packets 76 bytes 29184 (28.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 29 bytes 3793 (3.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether dc:a6:32:37:e4:cf txqueuelen 1000 (Ethernet)
RX packets 16 bytes 5284 (5.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 19 bytes 2860 (2.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
pi@raspberrypi:~ $ sudo cat /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=US
network={
ssid="snip"
psk="snip"
key_mgmt=WPA-PSK
}
I am not using rpi-update anymore. Not sure how to enable the wifi. The gui has a double red x icon and I get "dhcpcd not running" when you hover on it and nothing to select when you try clicking it. When using raspi-config I get the message "could not communicate with wpa_supplicant." So how else can I enable wifi?
pi@raspberrypi:~ $ sudo iwlist wlan0 scan
wlan0 Interface doesn't support scanning : Network is down
I tried sudo ifup wlan0 did not work got an "unknown interface wlan0." So tried sudo ip link wlan0 up it did not connect to wifi but, was able to scan wlan0.
pi@raspberrypi:~ $ sudo iwlist wlan0 scan
wlan0 Scan completed :
Cell 01 - Address: BC:64:4B:AF:49:07
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=70/70 Signal level=-26 dBm
Encryption key:on
ESSID:"snip"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=0000000000000000
Extra: Last beacon: 40ms ago
IE: Unknown: 000846616E647769636B
IE: Unknown: 010882848B968C129824
IE: Unknown: 030106
IE: Unknown: 0706555320010B1E
IE: Unknown: 2A0100
IE: Unknown: 3204B048606C
IE: Unknown: 460571D000000C
IE: Unknown: 2D1AAD011BFFFFFF00000000000000000001000000000406E6470D00
IE: Unknown: 3D1606000500000000000000000000000000000000000000
IE: Unknown: 7F080000070200000040
IE: Unknown: DD180050F2020101840003A4000027A4000042435E0062322F00
IE: Unknown: DD0900037F01010000FF7F
IE: Unknown: DD9F0050F204104A0001101044000102103B0001031047001099A5D5D6BFEF5491AFB2B571720D3D201021001C41746865726F7320436F6D6D756E69636174696F6E732C20496E632E102300044150787810240008415078782D7878781042001253657269616C204E756D62657220486572651054000800060050F20400011011000941746865726F734150100800020004103C0001021049000600372A000120
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
Cell 02 - Address: BC:64:4B:AF:49:08
Channel:36
Frequency:5.18 GHz (Channel 36)
Quality=70/70 Signal level=-34 dBm
Encryption key:on
ESSID:"snip"
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=0000000000000000
Extra: Last beacon: 40ms ago
IE: Unknown: 000846616E647769636B
IE: Unknown: 01088C129824B048606C
IE: Unknown: 030124
IE: Unknown: 074C55532024011E28011E2C011E30011E3401183801183C01184001186401186801186C01187001187401187801187C01188001188401188801188C011895011E99011E9D011EA1011EA5011E00
IE: Unknown: 200103
IE: Unknown: 460571D000000C
IE: Unknown: 2D1AEF091BFFFFFF0000000000000000000100000000000000000000
IE: Unknown: 3D1624050400000000000000000000000000000000000000
IE: Unknown: 7F080000070200000040
IE: Unknown: BF0CB2018033EAFF0000EAFF0000
IE: Unknown: C005012A00FCFF
IE: Unknown: C30402C4C4C4
IE: Unknown: DD180050F2020101840003A4000027A4000042435E0062322F00
IE: Unknown: DD0900037F01010000FF7F
IE: Unknown: DD9F0050F204104A0001101044000102103B0001031047001099A5D5D6BFEF5491AFB2B571720D3D201021001C41746865726F7320436F6D6D756E69636174696F6E732C20496E632E102300044150787810240008415078782D7878781042001253657269616C204E756D62657220486572651054000800060050F20400011011000941746865726F734150100800020004103C0001021049000600372A000120
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
Cell 03 - Address: BE:64:4B:AF:49:07
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=70/70 Signal level=-27 dBm
Encryption key:on
ESSID:""
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=0000000000000000
Extra: Last beacon: 40ms ago
IE: Unknown: 0000
IE: Unknown: 010882848B968C129824
IE: Unknown: 030106
IE: Unknown: 050400010000
IE: Unknown: 0706555320010B1E
IE: Unknown: 2A0100
IE: Unknown: 3204B048606C
IE: Unknown: 2D1AAD011BFFFFFF00000000000000000001000000000406E6470D00
IE: Unknown: 3D1606000500000000000000000000000000000000000000
IE: Unknown: 7F080000000200000040
IE: Unknown: DD180050F2020101840003A4000027A4000042435E0062322F00
IE: Unknown: DD0900037F01010000FF7F
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
Cell 04 - Address: FE:64:4B:AF:49:07
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=70/70 Signal level=-25 dBm
Encryption key:on
ESSID:""
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=0000000000000000
Extra: Last beacon: 40ms ago
IE: Unknown: 0000
IE: Unknown: 010882848B968C129824
IE: Unknown: 030106
IE: Unknown: 050400010000
IE: Unknown: 0706555320010B1E
IE: Unknown: 2A0100
IE: Unknown: 3204B048606C
IE: Unknown: 2D1AAD011BFFFFFF00000000000000000001000000000406E6470D00
IE: Unknown: 3D1606000500000000000000000000000000000000000000
IE: Unknown: 7F080000000200000040
IE: Unknown: DD180050F2020101840003A4000027A4000042435E0062322F00
IE: Unknown: DD0900037F01010000FF7F
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : 802.1x
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : 802.1x
Now when I do ifconfig wlan0:
pi@raspberrypi:~ $ ifconfig wlan0
wlan0: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether dc:a6:32:37:e4:cf txqueuelen 1000 (Ethernet)
RX packets 8 bytes 3133 (3.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 21 bytes 2908 (2.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
I have tried many times and many things still no wifi after doing updates. I reflashed the sd many times and still get the same problem.
This is what I get after update: Double red x icon, dhcpcd not running. There are no networks to chose from.
pi@raspberrypi:~ $ sudo cat /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=US
network={
ssid="Snip"
psk="snip"
}
pi@raspberrypi:~ $ ifconfig wlan0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether dc:a6:32:37:e4:cf txqueuelen 1000 (Ethernet)
RX packets 458 bytes 72723 (71.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 22 bytes 3267 (3.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
pi@raspberrypi:~ $ sudo iwlist wlan0 scan
wlan0 Interface doesn't support scanning: Network is down
pi@raspberrypi:~ $ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether dc:a6:32:37:e4:ce txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
pi@raspberrypi:~ $ ifconfig wlan0
wlan0: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether dc:a6:32:37:e4:cf txqueuelen 1000 (Ethernet)
RX packets 8 bytes 1097 (1.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 23 bytes 3461 (3.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
pi@raspberrypi:~ $ iwconfig
wlan0 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
eth0 no wireless extensions.
lo no wireless extensions.
pi@raspberrypi:~ $ sudo wpa_cli -i wlan0 reconfigura
Failed to connect to non-global ctrl_ifname: wlan0 error: No such file or directory
What can I do to get wifi?
pi@raspberrypi:~ $ sudo systemctl status dhcpcd.service
● dhcpcd.service - dhcpcd on all interfaces
Loaded: loaded (/lib/systemd/system/dhcpcd.service; enabled; vendor preset: e
Active: failed (Result: signal) since Sat 2020-01-18 03:07:53 EST; 1min 40s a
Process: 396 ExecStart=/usr/lib/dhcpcd5/dhcpcd -q -b (code=exited, status=0/SU
Main PID: 429 (code=killed, signal=SEGV)
Jan 18 03:07:48 raspberrypi dhcpcd[429]: wlan0: REPLY6 received from fe80::be64:4bff:feaf:490a
Jan 18 03:07:48 raspberrypi dhcpcd[429]: wlan0: adding address 2601:340:c580:a350::31e5/128
Jan 18 03:07:48 raspberrypi dhcpcd[429]: wlan0: renew in 302400, rebind in 483840, expire in 604800 seconds
Jan 18 03:07:52 raspberrypi dhcpcd[429]: wlan0: leased 169.254.1.165 for infinity
Jan 18 03:07:52 raspberrypi dhcpcd[429]: wlan0: adding route to 169.254.1.0/24
Jan 18 03:07:52 raspberrypi dhcpcd[429]: wlan0: adding default route via 169.254.1.64
Jan 18 03:07:52 raspberrypi dhcpcd[429]: wlan0: deleting route to 169.254.1.0/24
Jan 18 03:07:52 raspberrypi dhcpcd[429]: wlan0: deleting default route via 169.254.1.64
Jan 18 03:07:52 raspberrypi systemd[1]: dhcpcd.service: Main process exited, code=killed, status=11/SEGV
Jan 18 03:07:53 raspberrypi systemd[1]: dhcpcd.service: Failed with result 'signal'.
lines 1-16/16 (END)
******* FRESH DOWNLOAD *******
raspi-config to setup wifi and rebooted. sudo apt update, it worked fine. 166 files to upgrade.sudo apt full-grade had to run it twice it errored the first time.raspi-configNetwork Options get message Could not communicate with wpa_supplicant.pi@raspberrypi:~ $ sudo cat /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=US
network={
ssid="********"
psk="************"
key_mgmt=WPA-PSK
}
I also did the same steps above without using the LCD-Screen drivers and get the same end result no wifi. I have read the foundation guidelines but cannot find what to do next. Everything on the web seems several years old.
pi@raspberrypi:~ $ sudo iwlist wlan0 scan
wlan0 Interface dosen't support scanning : Network is down
***** journalctl -b command used !!!!message was in red *****
Jan 22 14:41:50 raspberrypi kernel: brcmfmac: F1 signature read @0x18000000=0x15264345
!!!!Jan 22 14:41:50 raspberrypi kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
Jan 22 14:41:50 raspberrypi kernel: usbcore: registered new interface driver brcmfmac
!!!!Jan 22 14:41:51 raspberrypi kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
!!!!Jan 22 14:41:51 raspberrypi kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
Jan 22 14:41:51 raspberrypi systemd-udevd[166]: Using default interface naming scheme 'v240'.
Jan 22 14:41:59 raspberrypi systemd[1]: Starting Bluetooth service...
Jan 22 14:41:59 raspberrypi systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
Jan 22 14:41:59 raspberrypi systemd[1]: Started Update UTMP about System Runlevel Changes.
Jan 22 14:41:59 raspberrypi bluetoothd[753]: Bluetooth daemon 5.50
Jan 22 14:41:59 raspberrypi systemd[1]: Started Bluetooth service.
Jan 22 14:41:59 raspberrypi systemd[1]: Started Raspberry Pi bluetooth helper.
Jan 22 14:41:59 raspberrypi bluetoothd[753]: Starting SDP server
Jan 22 14:41:59 raspberrypi systemd[1]: Started BluezALSA proxy.
Jan 22 14:41:59 raspberrypi systemd[1]: Reached target Bluetooth.
Jan 22 14:41:59 raspberrypi systemd[1]: Startup finished in 2.663s (kernel) + 13.368s (userspace) = 16.031s.
Jan 22 14:41:59 raspberrypi kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jan 22 14:41:59 raspberrypi kernel: Bluetooth: BNEP filters: protocol multicast
Jan 22 14:41:59 raspberrypi kernel: Bluetooth: BNEP socket layer initialized
Jan 22 14:41:59 raspberrypi bluetoothd[753]: Bluetooth management interface 1.14 initialized
Jan 22 14:41:59 raspberrypi dbus-daemon[360]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested b
!!!!Jan 22 14:41:59 raspberrypi bluetoothd[753]: Sap driver initialization failed.
Jan 22 14:41:59 raspberrypi kernel: Bluetooth: BNEP socket layer initialized
Jan 22 14:41:59 raspberrypi bluetoothd[753]: Bluetooth management interface 1.14 initialized
Jan 22 14:41:59 raspberrypi dbus-daemon[360]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested b
!!!!Jan 22 14:41:59 raspberrypi bluetoothd[753]: Sap driver initialization failed.
!!!!Jan 22 14:41:59 raspberrypi bluetoothd[753]: sap-server: Operation not permitted (1)
Jan 22 14:41:59 raspberrypi systemd[1]: bthelper@hci0.service: Succeeded.
Jan 22 14:42:00 raspberrypi bluetoothd[753]: Endpoint registered: sender=:1.19 path=/org/bluez/hci0/A2DP/SBC/Source/1
Jan 22 14:42:00 raspberrypi bluetoothd[753]: Endpoint registered: sender=:1.19 path=/org/bluez/hci0/A2DP/SBC/Source/2
Jan 22 14:42:00 raspberrypi systemd[1]: Starting Hostname Service...
Jan 22 14:42:00 raspberrypi kernel: Bluetooth: RFCOMM TTY layer initialized
Jan 22 14:42:00 raspberrypi kernel: Bluetooth: RFCOMM socket layer initialized
Jan 22 14:42:00 raspberrypi kernel: Bluetooth: RFCOMM ver 1.11
!!!!Jan 22 14:42:00 raspberrypi bluetoothd[753]: Failed to set privacy: Rejected (0x0b)
Jan 22 14:42:00 raspberrypi dhcpcd[431]: wlan0: soliciting an IPv6 router
Jan 22 14:42:00 raspberrypi dbus-daemon[360]: [system] Successfully activated service 'org.freedesktop.hostname1'
Jan 22 14:42:00 raspberrypi systemd[1]: Started Hostname Service.
Jan 22 14:42:00 raspberrypi dhcpcd[431]: wlan0: rebinding lease of 169.254.1.165
Jan 22 14:42:00 raspberrypi dhcpcd[431]: wlan0: probing address 169.254.1.165/24
Jan 22 14:42:01 raspberrypi dhcpcd[431]: wlan0: Router Advertisement from fe80::be64:4bff:feaf:490a
Jan 22 14:42:01 raspberrypi kernel: ICMPv6: process `dhcpcd' is using deprecated sysctl (syscall) net.ipv6.neigh.wlan0.retrans_time - use net.ipv6.neigh.wlan0.retrans_time_ms in
Jan 22 14:42:01 raspberrypi dhcpcd[431]: wlan0: adding address 2601:340:c580:a350:db34:3209:afe4:db0c/64
Jan 22 14:42:01 raspberrypi avahi-daemon[350]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::bcd6:d0ae:a078:5763.
Jan 22 14:42:01 raspberrypi avahi-daemon[350]: Joining mDNS multicast group on interface wlan0.IPv6 with address 2601:340:c580:a350:db34:3209:afe4:db0c.
Jan 22 14:42:01 raspberrypi avahi-daemon[350]: Registering new address record for 2601:340:c580:a350:db34:3209:afe4:db0c on wlan0.*.
Jan 22 14:42:01 raspberrypi dhcpcd[431]: wlan0: adding route to 2601:340:c580:a350::/64
Jan 22 14:42:01 raspberrypi avahi-daemon[350]: Withdrawing address record for fe80::bcd6:d0ae:a078:5763 on wlan0.
Jan 22 14:42:01 raspberrypi dhcpcd[431]: wlan0: confirming prior DHCPv6 lease
Jan 22 14:42:01 raspberrypi dhcpcd[431]: wlan0: adding default route via fe80::be64:4bff:feaf:490a
Jan 22 14:42:02 raspberrypi dhcpcd[431]: wlan0: REPLY6 received from fe80::be64:4bff:feaf:490a
Jan 22 14:42:02 raspberrypi dhcpcd[431]: wlan0: adding address 2601:340:c580:a350::dd95/128
Jan 22 14:42:02 raspberrypi dhcpcd[431]: wlan0: renew in 302400, rebind in 483840, expire in 604800 seconds
Jan 22 14:42:02 raspberrypi avahi-daemon[350]: Registering new address record for 2601:340:c580:a350::dd95 on wlan0.*.
Jan 22 14:42:04 raspberrypi systemd[1]: systemd-rfkill.service: Succeeded.
Jan 22 14:42:05 raspberrypi dhcpcd[431]: wlan0: leased 169.254.1.165 for infinity
Jan 22 14:42:05 raspberrypi avahi-daemon[350]: Joining mDNS multicast group on interface wlan0.IPv4 with address 169.254.1.165.
Jan 22 14:42:05 raspberrypi avahi-daemon[350]: New relevant interface wlan0.IPv4 for mDNS.
Jan 22 14:42:05 raspberrypi avahi-daemon[350]: Registering new address record for 169.254.1.165 on wlan0.IPv4.
Jan 22 14:42:05 raspberrypi dhcpcd[431]: wlan0: adding route to 169.254.1.0/24
Jan 22 14:42:05 raspberrypi dhcpcd[431]: wlan0: adding default route via 169.254.1.64
Jan 22 14:42:05 raspberrypi avahi-daemon[350]: Withdrawing address record for 169.254.1.165 on wlan0.
Jan 22 14:42:05 raspberrypi avahi-daemon[350]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 169.254.1.165.
Jan 22 14:42:05 raspberrypi avahi-daemon[350]: Interface wlan0.IPv4 no longer relevant for mDNS.
Jan 22 14:42:05 raspberrypi dhcpcd[431]: wlan0: deleting route to 169.254.1.0/24
Jan 22 14:42:05 raspberrypi dhcpcd[431]: wlan0: deleting default route via 169.254.1.64
Jan 22 14:42:05 raspberrypi systemd[1]: dhcpcd.service: Main process exited, code=killed, status=11/SEGV
Jan 22 14:42:06 raspberrypi avahi-daemon[350]: Interface wlan0.IPv6 no longer relevant for mDNS.
Jan 22 14:42:06 raspberrypi avahi-daemon[350]: Leaving mDNS multicast group on interface wlan0.IPv6 with address 2601:340:c580:a350:db34:3209:afe4:db0c.
Jan 22 14:42:06 raspberrypi avahi-daemon[350]: Withdrawing address record for 2601:340:c580:a350::dd95 on wlan0.
Jan 22 14:42:06 raspberrypi avahi-daemon[350]: Withdrawing address record for 2601:340:c580:a350:db34:3209:afe4:db0c on wlan0.
Jan 22 14:42:06 raspberrypi systemd[1]: dhcpcd.service: Failed with result 'signal'.
Jan 22 14:42:22 raspberrypi systemd[1]: systemd-fsckd.service: Succeeded.
My setup PI 3B+ OS : Raspian
Trying to connect the pi headless using my laptop. Both Pi and Laptop are connected to same wireless router.
Added the below config in wpa_supplicant.conf with correct credentials
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=<Insert country code here>
network={
ssid="<Name of your WiFi>"
psk="<Password for your WiFi>"
}
Also added ssh file to boot folder fo SD card.
On bootup can see Pi is connected to Wifi, router lists the Pi with IP address(192.168.0.101) When I try to ping the Pi from Laptop using this IP, get below error
Pinging 192.168.0.101 with 32 bytes of data:
Reply from 192.168.0.104: Destination host unreachable.
please help in setting the Pi in headless mode correctly. Thanks
I know this isn't really a raspberry pi question but there isn't an orange pi stack exchange community and its pretty close. So anyway, I'm a total NOOB with orange pi and raspberry pi.
I have never owned or used either, but I'd like to get started. I am trying to build a NAS(Network Attached Storage) to back up a few computers. The only reason I picked orange pi is that its a little cheaper, but if you think that it would be worth the extra few dollars to use a raspberry pi I will consider it.
All the cheaper raspberry pis don't have ethernet though, and even the cheapest orange pi does. I was planning on using the orange pi zero NAS Expansion Board, which has 1 SATA and 1 MSATA port. I would like to use at least 2 if not 3 or more SATA drives that I have lying around.
Is there any way to do this with the Orange Pi? I think I saw somewhere that I cant use a SATA port multiplier like this:
Is that true? I was also thinking of using an MSATA to SATA adapter like this:
So that I can use both the SATA and MSATA connectors, but that still only gives me 2 SATA connectors. The SATA and MSATA connectors on the expansion board are both connected through USB and they disable the onboard USB ports.
Would it be better to just use a USB to SATA adaptor instead of the expansion board? Would one with multiple SATA ports work? What would be the best solution?
Also, what would the best OS for this setup? Something like NAS4FREE or FreeNAS? Or would a normal OS like Linux or ubuntu be better?
Thanks!
I am trying to send a message to my TTN application using ABP encryption mechanism through RN2483 LoRaWAN microchip and Raspberry Pi 3. In this case, I am using ArduPi extension board and enable UART and then raise GPIO4 (as HIGH) to make the processes successful. However, command line reference mentioned that how to transmit command which include both mac and radio command
# at page 22-23
mac tx <type> <port> <hex_data>
# at page 45-46
radio tx <hex_data>
mac pause and mac resume has been executed before each radio commands. The device has successfully joined with the ABP configuration on the TTN. The mac and radio commands is giving the expected response as mentioned in the command reference. By the way, TTN doesn't get any message from LoRaWAN module.
I can receive a stream from the raspberry using mplayer and netcat.
On the raspberry: raspivid -t 999999 -o - | nc [ip address] 5001
On Windows: nc -L -p 5001 | mplayer -fps 31 -cache 1024 -
So far so good, but now I can get mplayer, in my C# form, to work but don't know how to tell it to receive a stream from my local network.
Has anyone tried this CAN board? It uses the Microchip MCP2515, but I don't see any docs or sample apps.
Qunqi MCP2515 Controller Bus Module TJA1050 Receiver SPI Protocol for Arduino SCM 51
also here:
D33 MCP2515 CAN Bus Module TJA1050 Receiver SPI Protocol
I've also been a board called NiRen that appears to be identical to these.
If you stacked 4 Raspberry Pi's, as you would a regular cluster computer, can the HDMIs of each Raspberry Pi be assigned to separate AV outputs or are there any programs, that do this for you. For example, say you have 2 TVs and both are connected to the Raspberry Pi cluster by 2 separate HDMI cables. They are connected to 2 different Raspberry Pi's in the cluster. Neither one is the controller Raspberry Pi. One person wants to watch CCTV and the other wants to listen to music on the media center. Using just the controller Raspberry Pi and Raspbian, can you send 2 different HDMI outputs to the 2 TVs. The outcome is shown in the diagram below:
I am new to raspberry pi, and to linux. When I am trying to follow tutorials online, they sometimes require me to change /boot/config.txt. I am using the Jessie Version or Raspbian. (I am trying to change the file on the pi itself.) Whenever I try to save my edits, however, I get an error saying "Can't open file to write." How can I edit config.txt?
I'd like to use my raspberry pi as media renderer so I can select playlists on my control point to play music from the media server. I've found some questions to gmediarender but no direct answer how to install it. How can I do that in an easy way?
I have a Raspberry Pi Zero and I am using the Adafruit I2S MEMS Microphone together with the ADAFRUIT I2S 3W CLASS D AMPLIFIER BREAKOUT - MAX98357A.
I did follow the two respective tutorials and I got both the mic and the speaker working. However, I do need to disable the microphone or the amp + speaker won't work.
There seems to be a conflict regarding the I2S bus.
According to this forum post it can be done.
Update:
I have the following /etc/modules:
i2c-dev
snd-bcm2835
my_loader
The /boot/config.txt looks like so:
# ...
dtparam=i2s=on
# ...
dtparam=audio=on
dtoverlay=hifiberry-dac
dtoverlay=i2s-mmap
This is what I see in dmesg when I have both the mic and the amplifier enabled:
[ 13.039895] asoc-simple-card asoc-simple-card.0: snd-soc-dummy-dai <-> 20203000.i2s mapping ok
[ 13.660674] bcm2835-i2s 20203000.i2s: Trying to bind component to card "snd_rpi_hifiberry_dac" but is already bound to card "snd_rpi_simple_card"
[ 13.660700] snd-hifiberry-dac soc:sound: ASoC: failed to instantiate card -19
[13.661278] snd-hifiberry-dac soc:sound: snd_soc_register_card() failed: -19
The two adafruit tutorials for the mic and the amp are conflicting. The mic tutorial tells me to enable the snd-bcm2835 module:
Add
snd-bcm2835on its own line, to the modules file as shown below
While the amp tutorial tells me to disable the module:
However, if you see the following line:
snd_bcm2835Put a
#in front of it
Please note the different typing using both a dash and an underscore snd_bcm2835 vs. snd-bcm2835.
Most desktop computers come with metal cases, which have a side-effect of blocking the radiofrequency emissions or electromagnetic radiation which is produced by the internal electronics.
Back when people still had analog televisions, I noticed that running a computer with no case or with an open case would cause interference with TV signals, visible as a noisy picture.
I have a Raspberry Pi sitting in a typical clear plastic case, which runs all the time. I'm wondering how much it is radiating in the RF spectrum. Is this a problem for any applications? How does it compare to a WiFi hotspot?
I connected my Pi Zero to my PC ( Linux LMDE 3 Cindy) via USB port successfully, SO i want to connect to internet via my laptop which is connected to internet by its WIFI.
I found this instruction or this question via raspberrypi.stackexchange but those are working for window or MAC OS,but i don't find it for Linux!!!!
SO i need the similar instruction for enabling sharing my internet via USB enp0s20f0u1 device (PI Zero) in Linux. for example in windows we need to :
In the WiFi Properties window, click on the “Sharing” tab : similar to this photo:
So in Linux version what is the similar instruction to doing this?
Thanks a lot.
