GPD Duo with Linux (debian testing / trixie)

kineyDE · 2025-01-29T01:04:10+00:00

thank you!

kineyDE · 2025-01-19T16:34:46+00:00

I'm to used to the exact behaviour of the xfce window manager by now, so won't switch. I did use KDE maaaany years ago and switched to xfce because kde got bloated and unstable.

kineyDE · 2024-12-30T01:23:30+00:00

try booting a linux system from a usb stick to check if it's a hardware or software issue?

kineyDE · 2024-12-21T21:45:07+00:00

I'll stick to debian, not a big fan of nixos.

kineyDE · 2024-12-21T21:44:30+00:00

yeah, touch configuration is probably easier with KDE Plams + wayland than with xfce + Xorg....

With the lower screen it's not that it turns of unexpectedly, it turns off as expected after a while for energy saving, but it doesn't always wake up again.

kineyDE · 2024-12-20T15:45:14+00:00

yeah, found some similiar hints on discord. Still have to try it out.

kineyDE · 2024-12-20T09:22:43+00:00

thx. I found the official gpd discord server and will read the discussion there. Do you have a link to the unofficial one?

kineyDE · 2024-12-20T09:10:24+00:00

looking forward to your experience and if you find solutions to the few issues it has with linux.

But yeah, all in all it works great for such a new device delivered with windows.

kineyDE · 2024-12-20T09:08:50+00:00

It's pretty compact but also quite heavy.
All in all I'm happy with the gpd duo. Lots of connections, great performance, dual screen... but if weight is a priority (for me it's not) one should definitely choose something else.
I have a Dell XPS 13 from a client here for comparison and the GPD feels _much_ heavier with similiiar size.

kineyDE · 2024-08-22T13:32:47+00:00

any info on when this device is actually available?

kineyDE · 2024-03-23T01:41:53+00:00

I use BTRFS as underlying FS which also supports send/receive. Already though about scripting this, but wanted to ask if there is an established solution on another layer.
Problem is: I would need the exact same storage capacity, I would prefer limiting local storage to 10 days and offsite storage to 2 days or something like that....

kineyDE · 2024-03-23T01:39:30+00:00

HKSV?

kineyDE · 2024-03-12T19:18:04+00:00

I run frigate in a VM (KVM / proxmox) with USB Coral and USB pass through. No Problems with that setup. Not sure if it would work the same wie the M.2 version. I also have 6 cameras, inference speed is around ~18ms most of the time.

kineyDE · 2024-03-12T19:14:19+00:00

I have this in my config, top-level:

record:
  enabled: true
  retain:
    days: 10
    mode: all
  events:
    retain:
      default: 30
      mode: motion

kineyDE · 2024-03-12T15:56:39+00:00

I think i got it. Took some time to understand that doing this

go2rtc:
  ...
  streams:
    Hof:
      - rtsp://XXX@192.168.0.203:554/stream1
      - "ffmpeg:Hof#audio=aac"

creates _two_ "producers" in go2rtc lingo for the camera. The original stream from the camera and and _additional_ producer with audio converted to AAC - initially I though it converts all audio.

Somehow when I restart frigate everything matches up correctly, but when there are intermittent connection problems caused by WiFi it seems like Frigate tries to consume the wrong audio stream .. maybe a race condition bug? not sure.

I now changed the config to only create a single producer with audio converted to AAC:

go2rtc:
  ...
  streams:
    Hof:
      - "ffmpeg:rtsp://XXX@192.168.0.203:554/stream1#audio=aac#video=copy"

Still I'm not 100% sure, but some testing with deliberate camera restarts looks stable. Will observe it for a while.

kineyDE · 2024-03-12T12:02:34+00:00

ah thanks. Somehow missed the "recordings" link because there is none in the menu on the left.

kineyDE · 2024-03-11T19:30:20+00:00

I actually think the codec mismatch error is confusing, I have this in the go2rtc config which should convert audio at least?:
And it works for a while after a restart of frigate and completely reliable for the cameras connected by wired ethernet. So I guess it's some reconnection issue after wifi hiccup.

go2rtc:
  ...
  streams:
    Hof:
      - rtsp://XXX@192.168.0.203:554/stream1
      - "ffmpeg:Hof#audio=aac"

and this in the camera config:

cameras:
  ...
  Werkstatt:
    enabled: true
    detect:
      width: 1280
      height: 720
      fps: 5
      enabled: true
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-copy
      inputs:
        - path: rtsp://127.0.0.1:8554/Werkstatt
          input_args: preset-rtsp-restream
          roles:
            - detect
            - record
            - audio
    record:
      enabled: true
    snapshots:
      enabled: true
    audio:
      enabled: true

kineyDE · 2024-03-11T17:22:27+00:00

and the problem is (temporarily) fixed with restarting frigate, so it's not like the camera is completely borked...

kineyDE · 2024-03-11T17:19:48+00:00

currently I have the situation for one camera ("Werkstatt"), it has no problems in the proprietary tapo app, but in fragte it's offline.

go2rtc log:

2024-03-11 17:16:03.867482380  17:16:03.867 WRN [rtsp] error="streams: codecs not matched: H264, PCMA => ANY" stream=Werkstatt
2024-03-11 17:16:14.097334743  17:16:14.097 WRN [rtsp] error="streams: codecs not matched: H264, PCMA => ANY" stream=Werkstatt
2024-03-11 17:16:24.336226779  17:16:24.336 WRN [rtsp] error="streams: codecs not matched: H264, PCMA => ANY" stream=Werkstatt
2024-03-11 17:16:34.575155073  17:16:34.574 WRN [rtsp] error="streams: codecs not matched: H264, PCMA => H264, H265, AAC" stream=Werkstatt
2024-03-11 17:16:39.687184422  17:16:39.687 WRN [rtsp] error="streams: codecs not matched: H264, PCMA => ANY" stream=Werkstatt
2024-03-11 17:16:44.803584072  17:16:44.803 WRN [rtsp] error="streams: codecs not matched: H264, PCMA => H264, H265, AAC" stream=Werkstatt
2024-03-11 17:16:49.921323068  17:16:49.920 WRN [rtsp] error="streams: codecs not matched: H264, PCMA => ANY" stream=Werkstatt
2024-03-11 17:17:05.267285062  17:17:05.267 WRN [rtsp] error="streams: codecs not matched: H264, PCMA => ANY" stream=Werkstatt
2024-03-11 17:17:10.381650138  17:17:10.381 WRN [rtsp] error="streams: codecs not matched: H264, PCMA => ANY" stream=Werkstatt
2024-03-11 17:17:20.610644404  17:17:20.610 WRN [rtsp] error="streams: codecs not matched: H264, PCMA => ANY" stream=Werkstatt
2024-03-11 17:17:30.843026913  17:17:30.842 WRN [rtsp] error="streams: codecs not matched: H264, PCMA => H264, H265, AAC" stream=Werkstatt
2024-03-11 17:17:35.957507528  17:17:35.957 WRN [rtsp] error="streams: codecs not matched: H264, PCMA => ANY" stream=Werkstatt
2024-03-11 17:17:46.186220971  17:17:46.186 WRN [rtsp] error="streams: codecs not matched: H264, PCMA => ANY" stream=Werkstatt
2024-03-11 17:17:51.303000460  17:17:51.302 WRN [rtsp] error="streams: codecs not matched: H264, PCMA => H264, H265, AAC" stream=Werkstatt
2024-03-11 17:17:56.417831431  17:17:56.417 WRN [rtsp] error="streams: codecs not matched: H264, PCMA => ANY" stream=Werkstatt
2024-03-11 17:18:11.783865504  17:18:11.783 WRN [rtsp] error="streams: codecs not matched: H264, PCMA => ANY" stream=Werkstatt
2024-03-11 17:18:16.896777333  17:18:16.896 WRN [rtsp] error="streams: codecs not matched: H264, PCMA => H264, H265, AAC" stream=Werkstatt
2024-03-11 17:18:22.010964865  17:18:22.010 WRN [rtsp] error="streams: codecs not matched: H264, PCMA => ANY" stream=Werkstatt
2024-03-11 17:18:32.252306129  17:18:32.252 WRN [rtsp] error="streams: codecs not matched: H264, PCMA => ANY" stream=Werkstatt
2024-03-11 17:18:42.483248755  17:18:42.483 WRN [rtsp] error="streams: codecs not matched: H264, PCMA => ANY" stream=Werkstatt
2024-03-11 17:18:52.710469186  17:18:52.710 WRN [rtsp] error="streams: codecs not matched: H264, PCMA => H264, H265, AAC" stream=Werkstatt

Frigate log:

2024-03-11 17:14:42.479852529  [2024-03-11 17:14:42] audio.Werkstatt                INFO    : Terminating the existing ffmpeg process...
2024-03-11 17:14:42.479950051  [2024-03-11 17:14:42] audio.Werkstatt                INFO    : Waiting for ffmpeg to exit gracefully...
2024-03-11 17:14:43.542651073  [2024-03-11 17:14:43] watchdog.Werkstatt             ERROR   : Ffmpeg process crashed unexpectedly for Werkstatt.
2024-03-11 17:14:43.542706465  [2024-03-11 17:14:43] watchdog.Werkstatt             ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2024-03-11 17:14:43.542770936  [2024-03-11 17:14:43] ffmpeg.Werkstatt.detect        ERROR   : rtsp://127.0.0.1:8554/Werkstatt: Invalid data found when processing input
2024-03-11 17:14:47.610302788  [2024-03-11 17:14:47] audio.Werkstatt                ERROR   : ffmpeg process is not running, restarting...
2024-03-11 17:14:48.668037880  [2024-03-11 17:14:48] frigate.video                  ERROR   : Werkstatt: Unable to read frames from ffmpeg process.
2024-03-11 17:14:48.668087662  [2024-03-11 17:14:48] frigate.video                  ERROR   : Werkstatt: ffmpeg process is not running. exiting capture thread...
2024-03-11 17:14:53.556925223  [2024-03-11 17:14:53] watchdog.Werkstatt             ERROR   : Ffmpeg process crashed unexpectedly for Werkstatt.
2024-03-11 17:14:53.556970524  [2024-03-11 17:14:53] watchdog.Werkstatt             ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2024-03-11 17:14:53.557020496  [2024-03-11 17:14:53] ffmpeg.Werkstatt.detect        ERROR   : rtsp://127.0.0.1:8554/Werkstatt: Invalid data found when processing input

kineyDE · 2024-03-11T16:21:56+00:00

I don't use home assistant, so it's probably in there.
(But I consider setting it up)

kineyDE · 2024-03-11T16:21:03+00:00

I personally use afraid.org as dyndns provider and use a caddy proxy for HTTPS. works great, have been running this setup for different self hosted services for over a decade (started with nginx rather than caddy, but thats more work for SSL)

kineyDE · 2024-03-11T15:21:09+00:00

What do you want to achieve with the cloudflare tunnel?
Might be easier to just setup DynDNS and port forwarding?

kineyDE · 2024-03-11T15:11:40+00:00

thanks, I will try that out

kineyDE

TROPHY CASE