KDE connect with Raspberry Pi

Hi,

I can connect to my phone using KDE connect, I can also connect the phone and the Raspi. But Garuda does not detect the Raspi.

I don’t think it’s related to my network. Anyone using KDE connect on the Raspi successfully?

System:
Kernel: 6.6.1-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=f98349e3-8520-4d18-968f-b7d3b3f4b259 rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=f38c84c4-3b3e-4abc-afd9-6f44ced56afd loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: MAG B550 TOMAHAWK (MS-7C91) v: 2.0
serial: <superuser required> UEFI: American Megatrends LLC. v: A.A0
date: 05/26/2022
CPU:
Info: model: AMD Ryzen 5 5600G with Radeon Graphics bits: 64 type: MT MCP
arch: Zen 3 gen: 4 level: v3 note: check built: 2021-22
process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
microcode: 0xA50000D
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 981 high: 3909 min/max: 400/4464 scaling:
driver: amd-pstate-epp governor: performance cores: 1: 400 2: 400 3: 400
4: 400 5: 400 6: 3867 7: 400 8: 3909 9: 400 10: 400 11: 400 12: 400
bogomips: 93427
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
driver: amdgpu v: kernel arch: GCN-5 code: Vega process: GF 14nm
built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
speed: 16 GT/s ports: active: HDMI-A-1 empty: DP-1,DP-2 bus-ID: 30:00.0
chip-ID: 1002:1638 class-ID: 0300 temp: 37.0 C
Display: x11 server: X.Org v: 21.1.9 with: Xwayland v: 23.2.2
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 507x285mm (19.96x11.22")
s-diag: 582mm (22.9")
Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: Philips PHL 273V5
serial: <filter> built: 2016 res: 1920x1080 hz: 60 dpi: 82 gamma: 1.2
size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi x11:
drv: radeonsi inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.2.1-arch1.2
glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (renoir LLVM
16.0.6 DRM 3.54 6.6.1-zen1-1-zen) device-ID: 1002:1638 memory: 7.81 GiB
unified: no
API: Vulkan v: 1.3.269 layers: 13 device: 0 type: integrated-gpu name: AMD
Radeon Graphics (RADV RENOIR) driver: mesa radv v: 23.2.1-arch1.2
device-ID: 1002:1638 surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe
(LLVM 16.0.6 256 bits) driver: mesa llvmpipe v: 23.2.1-arch1.2 (LLVM
16.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
speed: 16 GT/s bus-ID: 30:00.1 chip-ID: 1002:1637 class-ID: 0403
Device-2: AMD Family 17h/19h HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s bus-ID: 30:00.6 chip-ID: 1022:15e3
class-ID: 0403
API: ALSA v: k6.6.1-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 0.3.84 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: e000 bus-ID: 22:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp34s0 state: down mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: d000 bus-ID: 2a:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp42s0 state: down mac: <filter>
Device-3: Qualcomm Atheros AR9271 802.11n driver: ath9k_htc type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:3 chip-ID: 0cf3:9271
class-ID: ff00 serial: <filter>
IF: wlp22s0f0u5 state: down mac: <filter>
Device-4: Qualcomm Atheros AR9271 802.11n driver: ath9k_htc type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-1.2:3
chip-ID: 0cf3:9271 class-ID: ff00 serial: <filter>
IF: wlp48s0f3u1u2 state: up mac: <filter>
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-6.3:17
chip-ID: 0a12:0001 class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 3 state: up address: <filter> bt-v: 4.0
lmp-v: 6 status: discoverable: no pairing: no class-ID: 7c0104
Drives:
Local Storage: total: 11.04 TiB used: 3.08 TiB (27.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 1B4QFXO7 temp: 37.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Kingchuxing model: 128GB
size: 119.24 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: A25E scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: Expansion Desk
size: 5.46 TiB block-size: physical: 4096 B logical: 512 B type: USB
rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter>
fw-rev: 0915 scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: Western Digital
model: WD50NDZW-11BCSS0 size: 4.55 TiB block-size: physical: 4096 B
logical: 512 B type: USB rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1
tech: HDD rpm: 4800 serial: <filter> fw-rev: 1034 scheme: GPT
ID-5: /dev/sdd maj-min: 8:48 model: MXT-USB Storage Device size: 7.5 GiB
block-size: physical: 512 B logical: 512 B type: USB rev: 2.0 spd: 480 Mb/s
lanes: 1 mode: 2.0 tech: N/A serial: <filter> fw-rev: 1501 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 104.05 GiB size: 104.05 GiB (100.00%)
used: 57.52 GiB (55.3%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 104.05 GiB size: 104.05 GiB (100.00%)
used: 57.52 GiB (55.3%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 104.05 GiB size: 104.05 GiB (100.00%)
used: 57.52 GiB (55.3%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 104.05 GiB size: 104.05 GiB (100.00%)
used: 57.52 GiB (55.3%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 39.06 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12 dev: /dev/zram0
ID-2: swap-2 type: partition size: 14.9 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sda3 maj-min: 8:3
Sensors:
System Temperatures: cpu: 45.0 C mobo: N/A gpu: amdgpu temp: 36.0 C
Fan Speeds (rpm): fan-1: 1444 fan-2: 0 fan-3: 0 fan-4: 0 fan-5: 0
fan-6: 748 fan-7: 1228 fan-8: 1324 fan-9: 0 fan-10: 0
Info:
Processes: 378 Uptime: 36m wakeups: 0 Memory: total: 40 GiB
available: 39.06 GiB used: 4.39 GiB (11.2%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
Packages: pm: guix-sys pkgs: 0 pm: guix-usr pkgs: 0 pm: nix-default pkgs: 0
pm: nix-sys pkgs: 0 pm: nix-usr pkgs: 0 pm: pacman pkgs: 2776 libs: 585
tools: octopi,paru,yay pm: rpm pkgs: 0 pm: flatpak pkgs: 0 Shell: fish
v: 3.6.1 default: Bash v: 5.2.15 running-in: konsole inxi: 3.3.31
Garuda (2.6.19-2):
System install date:     2022-10-03
Last full system update: 2023-11-15
Is partially upgraded:   No
Relevant software:       snapper NetworkManager mkinitcpio
Windows dual boot:       No/Undetected
Failed units:            fancontrol.service nmb.service

This is NOT simply about “unsupported hardware”:

Phone — Raspi: Works.
Phone — Garuda: Works.
Garuda — Raspi: Doen’t work.

I don’t think that’s even supposed to work…? I thought kde connect was used to sync messages, notifications and other phone utilities from your phone to desktop, i.e., phone app transfer’s phone data over the internet to your computer. But I don’t think the computer transfers anything back to the phone except media control.

Raspberry being a desktop itself I don’t see how they would connect with each other unless you somehow manage to run android’s kde connect on it to transmit data from raspbi to anything else. Even if it does connect I don’t see what it could possibly transmit.

I moved this to unsupported hardware because Garuda does not officially support the Raspi.

1 Like

Fascinating, how KDE Connect is still so underused, underdeveloped and not well known. It’s at least the best we have.

No, it’s also for file transfers. Why would a device not show up in the search just because it’s a PC or Raspi?

Anyways, I looked it up, and it was possible already six years ago, but other people report the same problems: Reddit - Dive into anything

Garuda is not on the Raspi, it’s on my PC. I want my PC to connect to the Raspi. It’s a problem of KDE Connect on my Garuda PC. The only thing that seems to work reliably on Linux to move files between systems.

All devices are on the same network, since the phone is the hotspot.

I know this is deviating from the topic but if it’s just for file transfers is it necessary to implement kde connect? Why bother with something that’s not working and not use something simpler instead? Files can be shared over bluetooth as well. → usb - Share files between 2 computers via bluetooth from terminal - Ask Ubuntu

or use something like megasync and it’s free 20gigs of storage to sync files between the two devices.

1 Like

https://userbase.kde.org/KDEConnect#I_have_two_devices_running_KDE_Connect_on_the_same_network,_but_they_can’t_see_each_other

4 Likes

Bluetooth isn’t that great either and it can have issues. In regards to other solutions, I don’t want to go through the internet for my computers at home. KDE Connect is on the way to become the standard for this.

This is possible, but not necessarily true. It depends on the configuration of the mobile device. Some hotspots intentionally isolate connected devices with subnetting, preventing them from communicating directly. Check your phone for advanced hotspot settings or features like “AP Isolation”, which may be preventing the two computers from seeing each other.

If you aren’t sure if they are on the same subnet or not, post the IP addresses and subnet masks of the devices into the thread.

5 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.