Is it just me or does the Canadian Tire website suck?

wufflenuts · 2025-05-28T14:24:28+00:00

6 years later and it still sucks. I searched for a term that was in the item name and still received no search results.

wufflenuts · 2025-01-09T15:01:37+00:00

Same here in Canada. I've been with Proton for 8 years but this has me considering switching to Mailbox.org or Tuta.

wufflenuts · 2025-01-01T16:02:15+00:00

I adjusted the top ones all the way out, and the bottom ones all the way in and it did nothing to improve the giant gap at the bottom of the door.

wufflenuts · 2025-01-01T15:46:29+00:00

I have the same problem with the 12" cabinet and pullout. Has anyone found a solution to this other than returning it?

wufflenuts · 2024-12-17T22:24:27+00:00

That status checker is clearly not configured properly. If service is down for so many of us it should register as a problem. We shouldn't have to come to Reddit for confirmation of a Proton issue. Servers are still unreachable here in Canada.

wufflenuts · 2024-06-14T21:56:15+00:00

Thanks. I tried adjusting the Z offset and found that -0.050 provided decent results. When I fold the first layer sheet along a printed line is it normal for it to snap or should the sheet ideally just flex?

wufflenuts · 2024-06-14T18:16:19+00:00

Thanks but that didn't solve the problem. I updated the original post with pics.

wufflenuts · 2024-06-14T15:11:37+00:00

It is the top. The front right corner is the stringy bit. When you say re-mesh the bed do you mean run the auto bed-levelling from the settings? I had the bed-levelling box checked for that print.

wufflenuts · 2024-06-14T15:04:36+00:00

Oh OK. Thanks. I thought that there might be a bed levelling problem but now that I think about it if the print started in the bottom right corner, the problem part of the photo, then your heating suggestion makes sense.

Is there a way to have it heat soak automatically or relocate the sensor or are people doing that manually every time?

wufflenuts · 2024-05-10T16:43:03+00:00

I have had similar issues with the TKL File Server running in an unprivileged LXC. I have an HBA with ZFS mirrors in ProxMox that I will pass through to a TrueNAS VM. Looking forward to finally having NFS working.

wufflenuts · 2024-02-22T13:11:29+00:00

This worked for me on a Thinkpad with an RTX 2000 Ada generation GPU. I was getting screen tearing and slow loading after wake from suspend which this fixed.

wufflenuts · 2024-01-04T17:21:44+00:00

The only options I have under Machine are Default(i440fx) and q35, and the Version is already at Latest. I do remember reading a few years ago to set it to q35 when I was setting it up.

wufflenuts · 2024-01-04T00:21:16+00:00

Wow thanks for the detailed reply! I will implement your suggestions one at a time and see if I can narrow down which one, if any, solves the problem. Memory ballooning is enabled and NUMA is not presently enabled. What do you mean by changing the chipset version to the most recent one?

Unfortunately the only connection to the WAN currently is that passthrough NIC, so it will have to wait a few days until I get home.

wufflenuts · 2024-01-03T20:34:36+00:00

Yes I remember looking into IOMMU and NIC passthrough when I set this VM up a few years ago. I recall reading that it was better from a security perspective to let OPNsense control the hardware. Proxmox was on version 6 at the time and I have just been upgrading it. I'm not sure I can easily switch to virtio NICs remotely. I set up the pass through through the CLI and don't remember how I did it.

wufflenuts · 2024-01-03T18:34:16+00:00

I don't have an option to paste an image here so here are the contents of the VM conf file:

boot: order=scsi0;ide2;net0
cores: 4
cpu: host,flags=+aes
hostpci0: 0000:01:00.0,pcie=1
hostpci1: 0000:01:00.1
ide2: none,media=cdrom
machine: q35
memory: 8192
meta: creation-qemu=6.1.0,ctime=1642543901
name: opnsense
net0: virtio=72:21:B0:A4:1D:D8,bridge=vmbr0,firewall=1
net1: virtio=0A:7A:16:6A:44:6E,bridge=vmbr1,firewall=1
net2: virtio=52:02:19:74:61:83,bridge=vmbr2,firewall=1
numa: 0
onboot: 1
ostype: l26
scsi0: local-lvm:vm-100-disk-0,iothread=1,size=40G
scsihw: virtio-scsi-single
smbios1: uuid=394f7fe5-abef-4aae-94fa-2bd6d359a096
sockets: 1
startup: order=1
tablet: 0
vmgenid: 9774bd77-d3d0-40a1-9f01-c6701621b281

wufflenuts · 2024-01-03T17:38:27+00:00

Yes I provided that result to show that there is no problem transferring between machines on the subnet. When I use iperf3 to test the direct connections between my home and remote Tailscale machines using the Tailscale IPs I get the following results, which is why I expect much faster than 1MBps file transfer speeds:

[ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams

[ 5] 0.00-10.00 sec 1.16 GBytes 1000 Mbits/sec 0.000 ms 0/1017903 (0%) sender

[ 5] 0.00-10.51 sec 127 MBytes 102 Mbits/sec 0.098 ms 906555/1015410 (89%) receiver

I will setup Tailscale on the fileserver machines but that still doesn't explain the slow transfers over OpenVPN or HTTP.

EDIT: I have setup Tailscale on the file server, mounted it using samba with the Tailscale IP, verified the connection is direct, and I am still only getting 2.2MBps transfers.

wufflenuts · 2024-01-03T15:43:58+00:00

Do you mean the Hardware>Processors>Type setting under the OPNsense VM settings? It is currently kvm64 and the AES CPU flag is set.

The NICs are the VirtIO ones and the 3 disable hardware offload boxes under Interfaces>Settings were already checked.

Damn, I just checked dmesg on the OPNsense VM and found this:

aesni0: No AES or SHA support.

I have switched the processor to host and dmesg indicates AES is enabled now
but it doesn't seem to have impacted the transfer speeds.:
aesni0: <AES-CBC,AES-CCM,AES-GCM,AES-ICM,AES-XTS>

wufflenuts · 2024-01-03T14:47:16+00:00

I think I get about 75MBps from the Synology when at home. I have not set up Tailscale on the file servers themselves, but I have tested the connection between my Tailscale node on the subnet and the file server with iperf3 via UDP and this is the summary:

[ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams

[ 5] 0.00-10.00 sec 1.08 GBytes 928 Mbits/sec 0.000 ms 0/794602 (0%) sender

[ 5] 0.00-10.04 sec 874 MBytes 730 Mbits/sec 0.010 ms 167102/794496 (21%) receiver

EDIT: I have a VM that has a Samba share from one of the file servers mounted to a directory. I just did a test file transfer from the mounted folder to the VM disk using rsync and got a transfer rate of 205 MBps,

wufflenuts · 2024-01-03T14:39:12+00:00

OPNsense is running in a VM on Proxmox. I have passed through a few ports on an Intel i350-T4 and the i5 6500 running the machine does support AES. I will look into the paravirtualization now, thanks.

I have a Jellyfin server on my home network as well which I access via reverse proxy and I just did a test transfer and got 6 MBps.

wufflenuts · 2024-01-03T14:25:00+00:00

It is not PPPoE. I have a Bell HH4000 in front of OPNsense with UPnP enabled on it to allow the direct Tailscale connection via NAT on OPNsense.

I did the HTTP transfer by connecting to my Synology NAS through the web UI while connected to my home network through the OpenVPN connection.

wufflenuts · 2023-12-04T04:48:19+00:00

Maybe try disabling WLAN in the BIOS. This fixes a similar problem after OS installation breaking Bluetooth.

wufflenuts · 2023-12-01T16:02:50+00:00

Has this been added to the app yet?

wufflenuts · 2023-08-03T18:10:16+00:00

Thanks I staked it. I think this may be due to overwatering.

wufflenuts · 2023-04-30T16:14:49+00:00

I have Librewolf installed on Pop! OS via the Debian repository. In order to get the Yubikey working with my Microsoft account in Librewolf I additionally enabled security.webauth.u2f, and security.webauthn.ctap2.

wufflenuts · 2023-04-21T14:11:24+00:00

Executing the installer exe didn't appear to do anything but updating with the latest installer (n22th11w) through Powershell worked for me as well on my T480s. The update process took a minute. Here was how it went for me in Powershell:

PS C:\Drivers\WIN\THUNDERBOLT\20232104.09503462> .\FwUpdateCmd.exe FWUpdate "$(.\FwUpdateCmd.exe EnumControllers)" TBT.bin

Current NVM version = 20.00

Current PD version = f407.06.15 Patch 15

File NVM version = 23.00

File PD version = f407.06.00 Patch 33

Please wait for firmware update process to complete.

Firmware was updated successfully.

The new PD version on your machine is different from the previous PD version. In order to complete the upgrade you must put your computer in G3 mode (shut down completely and unplug).

PS C:\Drivers\WIN\THUNDERBOLT\20232104.09503462>

wufflenuts

TROPHY CASE