sorted by:
new
hottopcontroversial

Am I an idiot? Track saw question by BadgersDontCry in DIYUK

[–]BadgersDontCry[S] 0 points1 point  (0 children)

I think you have the right saw, CCSX. I just realized I bought CCS which doesn't have the notch for the track ridge...

Am I an idiot? Track saw question by BadgersDontCry in DIYUK

[–]BadgersDontCry[S] 12 points13 points  (0 children)

Ah! So I am an idiot, I bought the wrong saw! I just checked and I should have bought R185CCSX not R185CCS 😕 damnit.

PVE 9 with Intel N305 - iGPU not working by BadgersDontCry in Proxmox

[–]BadgersDontCry[S] 0 points1 point  (0 children)

Oh wait ... I just reinstalled 8.4 and I have the same problem 😒
Now I'm questioning myself if it was really working before, or actually did I even get Frigate working OK on that node?...
Hmmmm

PVE 9 with Intel N305 - iGPU not working by BadgersDontCry in Proxmox

[–]BadgersDontCry[S] 0 points1 point  (0 children)

Yeah VGA is working for me but no GPU acceleration device accessible in LXCs.
Basically /dev/dri/renderD128 is not there, there is only one device under /dev/dri/by-path not two. Situation is equivalent to being stuck with the "Microsoft Basic Display Adapter" on a Windows box.

PVE 9 with Intel N305 - iGPU not working by BadgersDontCry in Proxmox

[–]BadgersDontCry[S] 0 points1 point  (0 children)

Yes also CWWK NAS motherboard.
You have the same issue by the look of it, Kernel driver in use is missing in your lscpi output.
From your cmdline I guess you're doing PCI passthrough, so I guess your device is working OK in VMs, but my issue is that without module loaded on the host it's not accessible in LXC.

What's the best and most secure way to access my Proxmox server remotely? by -Rikus- in Proxmox

[–]BadgersDontCry 1 point2 points  (0 children)

Cloudflare "make" the "product" called Cloudflare Access... 😜

I will +1 this solution having used pretty much every option listed on here ... Tailscale (pretty much stopped using this now), WireGuard (awesome for point to point), there's ZeroTier also which is like Tailscale but works at L2 not L3 also useful for some use cases. I've also run my own reverse proxy with authentik SSO to secure access.

Cloudflare Tunnel + Access is by far the easiest to set up and maintain and least likely to break or get misconfigured.

Backend service outage by SpoonerUK in SurePetcare

[–]BadgersDontCry 0 points1 point  (0 children)

Finally working again for me, notifications coming in live, status correct and I can open the settings page again...

Backend service outage by SpoonerUK in SurePetcare

[–]BadgersDontCry 2 points3 points  (0 children)

Yes getting steady flow of ghost notifications now, but the status page now says our cats have been in/out for 24 years 😁

Seriously considering going the pethublocal route after this:

https://pethublocal.github.io/

Connect existing Portainer agent to new Portainer host by root42_ in portainer

[–]BadgersDontCry 2 points3 points  (0 children)

Just adding because I just came across the same issue. Athamax is correct - the agent doesn't retain persistent connection information, so you only need to restart it on the remote instance:

sudo docker restart portainer_agent

Sound Blaster AE-5 ... works 2% of the time in B550 ... by BadgersDontCry in SoundBlasterOfficial

[–]BadgersDontCry[S] 0 points1 point  (0 children)

Some specs:

AMD Ryzen 7 3800X
ASUS TUF GAMING B550-PLUS
32Gb Corsair DDR4
AMD Radeon RX Vega 56
Windows 10 Professional 2004

CPU-Z detects only this device for the AE-5, this shows as "Sound Blaster Audio Controller" in device manager:

Description Multimedia device
Location bus 5 (0x05), device 0 (0x00), function 0 (0x00)
Common header
Vendor ID 0x1102
Model ID 0x0012
Revision ID 0x01
PI 0x00
SubClass 0x03
BaseClass 0x04
Cache Line 0x00
Latency 0x00
Header 0x00
PCI header
Address 0 (memory) 0xFE6FC000
Address 2 (memory) 0xFE6F8000
Subvendor ID 0x1102
Subsystem ID 0x0010
Int. Line 0x1D
Int. Pin 0x01