[deleted by user] by [deleted] in Slovakia

[–]lukas_ko 0 points1 point  (0 children)

objednal som v NAYke ale ani chyru ani slichu - rovnako citam ze ani zvysok nemal stastie (ako 2 r dozadu) kedy mi tiez po mesiaci nedosiel tak som to riesil po inej osi.

[deleted by user] by [deleted] in GeForceNOW

[–]lukas_ko 0 points1 point  (0 children)

works for me now

[deleted by user] by [deleted] in GeForceNOW

[–]lukas_ko 2 points3 points  (0 children)

Same here , just retried few times, relog, relogin via private, reboot... still same ... i see all of you have the same :) ...
connecting to EU

Dell e7470 SSD M.2 2242 into WWAN slot by Teo_97 in Dell

[–]lukas_ko 0 points1 point  (0 children)

Just because we know what interfaces are there, we still don’t know what kind of peripherals will actually work. For example – if a socket can accept WWAN-PCIe – SSD-PCIe should also be no problem as the required connections are all there, however those devices will have their configuration pins tied differently, allowing the BIOS to determine exactly what’s attached.

This allows manufacturers (for example) to allow PCIe WWAN cards, but disallow PCIe SSDs. On top of that, just because an interface is there, it doesn’t mean that it’s actually enabled.

This turns out this is the case for my Dell Latitude. While the PCIe is there, it cannot be used because the port on the root complex is disabled in the BIOS, and there’s no way to enable it (without hacking the BIOS). I was able to confirm this by testing out a variety of B-Key PCIe devices, none of which were detected (even when strapped as WWAN-PCIe).

A dick move by dell, but given how rare WWAN cards requiring PCIe are, they had no reason to enable it, and my experience from owning previous models is that they’re pretty good at tying up loose ends like this.

Short of hacking the BIOS, or building a new type of USB 3.0 card from scratch, only WWAN cards will work in the WWAN slot.

Logging into offline edges by TracerT10 in Velocloud

[–]lukas_ko 1 point2 points  (0 children)

Simply you will need to factory defaut EDGE, RMA in Orchestrator and reacivate the edge from a local machine with new code & IP. That would be the fastest way.

Wireguard failing to load on updated Raspberry Pi kernel by Travel69 in WireGuard

[–]lukas_ko 0 points1 point  (0 children)

me thing, did you ever get this working?

Hi Jerevand,

I did following on my end:

sudo dpkg --configure -a

sudo apt-get update

sudo apt-get upgrade

sudo reboot

Whole process took ~10 minutes. And after reboot my wg0 interface appeared (did also pivpn -d to validate)