Recent content by rjcab

  1. R

    CTX with no particular conf and USB

    I tried to start from the beginning: I plug the key: [253457.618475] usb 1-3.1: new full-speed USB device number 55 using xhci_hcd [253457.758345] usb 1-3.1: New USB device found, idVendor=067b, idProduct=2303, bcdDevice= 4.00 [253457.758359] usb 1-3.1: New USB device strings: Mfr=1, Product=2...
  2. R

    CTX with no particular conf and USB

    Thanks for your time. In my case only the serial will make the difference: root@pve:/mnt# udevadm info --name=/dev/bus/usb/001/049 --attribute-walk Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all...
  3. R

    CTX with no particular conf and USB

    Ok, I got it: on my CTX: My script try to open the device but I got an error: . It works with a VM hosted on Proxmox. root@nad:/dev/bus/usb/001# python3 /root/nad-rs232-rest/nad-rs232-rest.py 2025-10-08 10:14:15,727 - INFO - Starting mqtt thread 2025-10-08 10:14:15,730 - DEBUG - [MQTT]...
  4. R

    CTX with no particular conf and USB

    sorry, I am lost. My objective is to have my USB device attached to my container. So for this, we can not use the UI because only for VM. We need to custom the /etc/pve/lxc/109.conf right ?
  5. R

    CTX with no particular conf and USB

    Thanks for the prompt reply: so I understand that the path must be /dev/xxx but I don't know it as it is not configured yet in the CTX till the start of the CTX ? e
  6. R

    CTX with no particular conf and USB

    Hello, Here below my conf of my ctx: root@pve:~# cat /etc/pve/lxc/109.conf #lxc.cgroup.devices.allow%3A c 189%3A43 rwm #lxc.mount.entry%3A /dev/bus/usb/001/043 dev/ttyUSB1 none bind,optional,create=file arch: amd64 cores: 1 features: nesting=1 hostname: nad memory: 512 net0...
  7. R

    Backup File

    you are right, thx a lot
  8. R

    Backup File

    Hello. I Have Proxmox 8.4 and I tried to find my backup config file: root@pve:~# root@pve:~# cat /etc/pve/vzdump.cron # cluster wide vzdump cron schedule # Automatically generated file - do not edit PATH="/usr/sbin:/usr/bin:/sbin:/bin" root@pve:~# But where is my below conf so : Thanks...
  9. R

    Desperate with Proxmox 8.4 and GPU Passthrough Geforce GTX1650

    it works with that: /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on iommu=pt pcie_aspm=off pcie_port_pm=off"
  10. R

    Why blacklist doesn't work

    for people who may have the samie issue, it works with that: /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on iommu=pt pcie_aspm=off pcie_port_pm=off" /etc/modprobe.d/vfio.conf options vfio-pci ids=10de:10fa,10de:1f82 disable_vga=1 /etc/modules vfio vfio_iommu_type1 vfio_pci...
  11. R

    Why blacklist doesn't work

    I've seen that for this case vendor-reset is needed. My kernel, 6.14.8-3-bpo12-pve doesn't have the vendor-reset compatible?
  12. R

    Why blacklist doesn't work

    It sounds better: [ 6042.826109] vfio-pci 0000:01:00.0: vgaarb: deactivate vga console [ 6042.826121] vfio-pci 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+mem [ 6044.812982] vfio-pci 0000:01:00.0: not ready 1023ms after resume; waiting [ 6045.895526]...
  13. R

    Why blacklist doesn't work

    Thanks I can remove it. So even with kernel 6.14, I have to modify /proc/cmdline even if I already edit grub as below: root@pve:/mnt/diskint# cat /etc/default/grub # If you change this file or any /etc/default/grub.d/*.cfg file, # run 'update-grub' afterwards to update /boot/grub/grub.cfg. #...
  14. R

    Why blacklist doesn't work

    I've been told that if you boot with efi don't need to fill /proc/cmdline ? since pve 8.0 :-/ root@pve:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.14.8-2-pve root=/dev/mapper/pve-root ro quiet intel_iommu=on root@pve:~#
  15. R

    Why blacklist doesn't work

    Yes, I've done but it seems ok: