letrain

Members
  • Posts

    94
  • Joined

  • Last visited

Everything posted by letrain

  1. derp. haha yup. the post i linked didn't say anything about reboots. i got it sorted, edited my go file. thanks! hope it helps others. it is working for me currently.
  2. got it to work and persist. what i did. Edited /etc/slim.conf to my liking based on the information above. You do not need to copy an original (backup) as etc folder is dumped from ram on every reboot, and reloaded so any changes made to slim.conf do not persist, you can make one but save it somewhere else besides the etc folder if you feel safe having it around. then i moved a copy of slim.conf to the usb drive in a convenient folder. cp /etc/slim.conf /boot/config/slim.conf this created a copy that would not be changed after reboots. then i edited my go file to replace the one the system loads #blank monitor after 1 minute cp /boot/config/slim.conf /etc/slim.conf # Start the Management Utility /usr/local/sbin/emhttp & make sure it goes before emhttp it works just fine now.
  3. unless you found another solution.. currently it doesn't work. so tried reboot and slim is over written.
  4. anyway to "kill" slim and go back to cli without rebooting?
  5. it doesn't appear to get screen blanking to work for me.
  6. guessing its your docker i found on dockerhub/github? these variables work for that? tried your guide but it says "/usr/bin/samba.sh: line 160: $2: unbound variable" and the container won't start
  7. get anywhere with this? i'm interested as well.
  8. when i have the igpu-vf passed through it vm works fine via remote desktop. but when i change it back to VNC in the unraid GUI it never initializes the display. i've had these issues before after passing through a nvidia gpu as well. not sure why i can't go back to vnc after using passthrough on a prior vm boot.
  9. @zhtengwi'll be sad if this plugin dies. i've seen some forks on github, but not updated. i see its just some scripts, a page for sr-iov, and just updates the module for the kernel (i915.ko)?. i wonder if it would be possible to fork and just update the module, but i'm not familar with plugin creation, or if simply updated the module for 6.1.49 would be the only needed fix. added: it does appear that the i915.ko driver exists already. so would this plugin only need to install the conf file, add the page to emhttp, and patch libvirt.php? it appears the kernel module is the failure point, causing it to remove the conf files, and libvirt edit, but not emhttp edit. but this page is useless as it also removes the i915-sriov folder so the config will not stay. i'm not familar enough with scripting but could i just removed the kernel module part from the plugin script? or does this plugin include a different i915.ko driver? got this far.... its late an i'm past my knowledge. i915 0000:00:02.0: driver does not support SR-IOV configuration via sysfs
  10. don't bind to vfio. it creates the VF's then just add those on your vm template page, read a few posts prior this exact question has been asked. sr-iov is not VFIO. also until this is updated for 6.1.49 it will not create vf's
  11. thats what it did for me. looking at docker hub tag 27.0.1 and latest appear identical.
  12. So what the final solution here? Everything in the list needed? Custom kernel? Rom resize script? Everything works bare metal. But it won't work in the vm. Unraid 6.12.3 here, is 6.12.1 needed? Was there regression? Host BIOS Enable ReBAR support - Host BIOS Enable 4G Decoding - Enable & Boot Custom Kernel syslinux configuration (near beginning of this thread) - Boot Unraid in UEFI Mode - VM must use UEFI BIOS - VM must have the top line of XML from <domain type='kvm'> to: <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> - VM must have added the following (after the </device> line, before the </domain> line): <qemu:commandline> <qemu:arg value='-fw_cfg'/> <qemu:arg value='opt/ovmf/X-PciMmio64Mb,string=65536'/> </qemu:commandline>
  13. ok what did i do wrong? its enabled in bios. asrock calls it Clever access memory. it is on in the bios. the xml is edited. everything is on. i ran the user script.... and the vbios is up to date for the 3090.. @KptnKMan it works in bare metal..but i just can't get it to work in the VM.
  14. the script doesn't work anymore.... it is already bound to vfio. passthrough is working fine, but it keeps saying tat rombar is not enabled in bios so i figured getting the vbios might help it work better. oh well. "Okay dumping vbios file named GeForce RTX 3090 to the location /mnt/user/isos/vbios/ cat: rom: Input/output error Um.... somethings gone wrong and I couldn't dump the vbios for some reason Sometimes when this happens all we need to do to fix this is 'stub' or 'bind to the vfio' the gpu and reboot the server This can be done in Unraid 6.8.3 with the use of the vfio config plugin or if you are on Unraid 6.9 or above it can be done directly from the gui in Tools/System Devices .....So please do this and run the script again"
  15. how do i prevent remux from converting all my mkv files to mp4 first, is there a way to limit this to avi files only?
  16. thanks for the reply. it was worth a shot. i'll patiently wait. i've lived without it before, i can again. was using gvt-g, and now had sr-iov on new setup. i dont shut down often but i just upgraded my hardware and thought that might of been causing my unmounting during shutdown problem. or my boot usb was starting to go. tried several things and the update fixed my shutdown issue. its not often but reboots and shutdowns do occur.
  17. i'm was using the sr-iov plugin in unraid 6.12.2. i upgraded to 6.12.3 because i did have the docker unclean shutdown problem. no sr-iov doesn't work.. i found this in the logs. "Jul 15 12:17:33 Tower kernel: i915 0000:00:02.0: driver does not support SR-IOV configuration via sysfs" wondering if its a driver issue. thanks
  18. unraid 6.12.3 was just released. it broke sr-iov. worked fine in 6.12.2. 6.12.3 - "Docker This release resolves an issue where Docker does not properly stop when the array Stops, which can result in an unclean shutdown. If Docker containers have issues starting after a while, and you are running Plex, go to your Plex Docker container settings, switch to advanced view, and add this to the Extra Params: --no-healthcheck" I had the this problem with dockers and unclean shutdown, and disks not unmounting so upgraded. after upgrading sr-iov was missing. after trying to reinstall it this is the dialog. it appears in settings again, but as soon as i try to save config, and enable it doesn't work. thanks EDIT: found this in the logs "Jul 15 12:17:33 Tower kernel: i915 0000:00:02.0: driver does not support SR-IOV configuration via sysfs" not sure what happened between 6.12.2 and 6.12.3. its weird that sr-iov is in settings, but not on the plugin page. and "apps" still gives me the option to install, but fails.
  19. any luck getting time to work correctly?? its right on the time stamp but the images are way off. they are being written as 7pm being 00-00-00! when i change this in the config the docker won't even start.
  20. second this. i'm very interested in this setup as opposed to an HA setup with one wanip address.
  21. any luck figuring this out? it just started for me.