Recent content by silverstone

  1. S

    Supported MediaTek WiFi Module not Showing in Proxmox lspci

    And as I said, most likely People around here will tell you that is a Feature and not a Bug ;) . Proxmox VE is not meant to be used with Wireless Interfaces as I said. It's in the Name ;). lsxxx as in "list" for xxx so to Speak ;). - ls lists Files - lspci lists PCI/PCIe Devices - lsusb...
  2. S

    Supported MediaTek WiFi Module not Showing in Proxmox lspci

    And if you bothered to have a look at the Manufacturer Website for that Adapter in the first Place, you would have your Answer clear as Day:
  3. S

    Supported MediaTek WiFi Module not Showing in Proxmox lspci

    Yeah, and there's your Answer: bus info: usb@2:1 The Adapter is getting detected as USB .... And maybe your "M.2" is just a stupid PCIe to USB3 Adapter/Chip and then a standard Mediatek USB Adapter. Try lsusb or lsusb -t instead then. Or maybe lspci -tv if you want to Troubleshoot which PCIe...
  4. S

    Supported MediaTek WiFi Module not Showing in Proxmox lspci

    Can you show lspci without grepping ? Same with dmesg to see if something weird is going on. Did you try installing manually the latest Firmware from the Git Kernel Repository into /lib/firmware/ ? Also try ifconfig -a and lshw -class net (you might need to install lshw and net-tools) EDIT 1...
  5. S

    [TUTORIAL] Virtual Pendrive on VM

    I just wanted to say Huge Thanks in particular to @PanWaclaw, @gfngfn256 and @Mirmanium. Indeed without using XHCI it took AGES to install Debian 12 on the USB Image. After switching to XHCI, it's super Fast ;). I tried to collect the Information and put it into a somewhat easy to use Script...
  6. S

    Supported MediaTek WiFi Module not Showing in Proxmox lspci

    No experience with that particular Adapter, but I had a few Issues of my own on some Rock 5B SBC with Mediatek USB WiFi Adapters. There I have the Fenvi which uses the mt7921au Driver (non-n) which is a USB-to-WiFi Adapter. First of all, did you rebuild the Initramfs and reboot after you...
  7. S

    Firefox - CTRL or SHIFT or ALT not working in Guest VM

    I tried on my Laptop. One VM didn't work no matter what I did. Rebooting seems to have fixed that Issue on the Laptop. All other VMs seems to work on the Laptop. On Librewolf on the Desktop everything is still broken. After Reboot, on Chromium on the Desktop (which I never use) it works OK...
  8. S

    Firefox - CTRL or SHIFT or ALT not working in Guest VM

    I tried Disabling U-Block Origin on Librewolf OR ResistFingerprinting (NOT both at the same Time). With everything Enabled I get lots of Errors in the Librewolf Console, but not sure what's causing them: TypeError: this is undefined bootstrap-legacy-autofill-overlay.js:6247:9...
  9. S

    Firefox - CTRL or SHIFT or ALT not working in Guest VM

    Running latest PVE, with or without ResistFingerprinting, on Librewolf and Chromium, noVNC still refuses to work :(. This was working until at least a few Weeks ago (I rarely use the Console if I can reach the VM by SSH).
  10. S

    Proxmox VE Detected as an IPv6 Router and Neighbor Discovery not working

    On one Linux Client, ip -6 neighbor lists the Proxmox VE Host(s) as Router, when they clearly are not: 2XXX:XXXX:XXXX:1::A:B dev eno1 lladdr 11:22:33:44:55:66 router REACHABLE Setting sysctl -w net.ipv6.conf.vmbr0.forwarding=0 on the Proxmox VE Host fixed that, but I wonder if that also caused...
  11. S

    [TUTORIAL] [High Availability] Watchdog reboots

    I'm a bit confused though ... https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_requirements_3 says (about HA): So it would appear it's not possible to enable HA with a Single / Standalone Node (well, it also doesn't make much sense to enable HA in such case obviously). Are you talking...
  12. S

    [TUTORIAL] [High Availability] Watchdog reboots

    First of all, thanks for your Efforts in shedding Light on this Topic. I currently rely on the Watchdog on some Raspberry Pi SBC in order to force a Reboot in case they freeze for whatever Reason. I was planning on doing the same with Proxmox VE (single Standalone Host, no HA) and to my...
  13. S

    ipcc_send_rec error on debian buster fresh install

    A few years later, but I also received that error Message but for a completely different Reason. In my Case, I did the setup from a Debian LiveUSB, debootstrap Debian Bookworm onto the SSD and, without rebooting (sigh :rolleyes: ), I also proceeded to install Proxmox VE and created a...
  14. S

    Improve write amplification?

    I did my own Test Script to try to see the Impacts of Write Amplification now that I plan on converting existing 8k volblocksize Virtual Disks into 16k volblocksize Virtual Disks. Repository and Script: https://github.com/luckylinux/proxmox-tools/blob/main/benchmark_write_amplification_guest.sh...
  15. S

    Can't remove old vm-disk "data set is busy"

    You are welcome :) . I also just adapted that line from something I found online. Cannot remember exactly where. I usually put a comment with the "Source" or "Reference" for it. Pretty sure I just googled linux kill/list processes running inside chroot online or something along those Lines...