SeoulPlaya

Members
  • Posts

    17
  • Joined

  • Last visited

Converted

  • Gender
    Male
  • Location
    Canada

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

SeoulPlaya's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Hi, Just a quick question. I think I know the answer but want to make sure. I do not have a graphics card in my Unraid server. When setting up the Macinabox, I can get everything working except sound. I have the graphics card set to VNC as I read using the IGPU for my intel proc isn't reliable. Does that mean I cannot use the integrated audio? I tried setting the sound to Intel Cannon Lake PCH but it gives me 'Please ensure all devices within the iommu_group are bound to their vfio bus driver' when I try to start the VM. I also made sure all the customized edits to the xml are put back in after doing this. If I remove the sound card to none, and update (with customized xml edits) the VM boots and everything works via splashtop except sound. I tried to look it up but couldn't find any answers to this. Thank you for any assistance.
  2. So I rebooted my server today and before i did that, your question regarding the VMs using the iGPU made me think that was the cause. I changed the video to VNC for my VM and then rebooted the server. Everything came up including my plex! So it definitely had something to do with both the VM and the Plex having the iGPU passthrough. I had plex for auto start and the vm to stop so not sure why it caused an issue, but that's fine.
  3. Will try those suggestions. I can't reboot it right now but will try again later. Yes I have 1 VM using the iGPU but it is off and hasn't been on in awhile. I was just testing some things with it. Will post diagnostics log after reboot and before I try anything as well.
  4. I rebooted my server. The array came up but plex docker would not start. Plex log shows: Critical: libusb_init failed Using Putty, entered ls -al /dev/dri. Output was: No such file or directory. Stopped array. Re-entered ls -al /dev/dri. Output showed the directory and contents. Started array. Re-entered command. Same output again, and my plex docker auto started. I've attached screenshots of both my go file and the putty. Not sure what is going on but maybe it's my go file.
  5. Ok. Will post these once I have a chance to reboot the server. Right now this is the content of my go file. #!/bin/bash #Setup drivers for hardware transcoding in Plex modprobe i915 chmod -R 777 /dev/dri # Start the Management Utility /usr/local/sbin/emhttp & Here is the output of the command but this is after I made the change of course. I will find time today to reboot the server and try again. Sorry for the delay in posts. It's been busy with the present climate of the world these days. Thanks for your help!
  6. I actually have the chmod command in my go file. I don't think that the directory isn't there on bootup, it's that there are no permissions to the directory on bootup, unless I stop the array first and reapply the chmod command on the directory. I guess my chmod command isn't applying for whatever reason. I typed it, and not copy and paste so I'm sure it's correct. Oh well, it's not a huge deal, but was hoping someone might know why that is. Also, using an iGPU, sorry forgot to mention that.
  7. Hey. Sorry to bother everyone with this but I noticed something weird and perhaps there is a simple answer I'm not seeing. While I have my plex now working, if I reboot my URAID system, I need to reapply the permissions to the /dev/dri directory otherwise my Plex won't start. I also cannot apply the permissions unless the array is stopped. If the array is started, the directory is not found. If I have to do this everytime, then I will but it's a pain lol. Is this expected behavior? (I'm guessing no, since comments before said nobody had to stop the array to apply permissions to the /dev/dri directory). Anyways, thanks for any input you may have.
  8. Honestly, I don't recall reading that either. But I just tried to stop the array and then cd /dev/dri and then it was there! Started the array tried again and it was gone. So then I thought it's definitely a permission issue so then I did the steps I outlined and it worked. Thankfully lol.
  9. WOW. I got it lol. Man my linux skills are terrible. Thank you for everyone helping me! I was finally able to get this by doing the following (in case someone as bad as me needs help lol) I'm not sure I needed to update to 6.9.0-beta1 since perhaps the key to this whole thing was doing these commands when the array was stopped, but I'm just making mention that I did upgrade to this version due to my specs ( 9th gen processor). Edit the /boot/config/go to add: #!/bin/bash #Setup drivers for hardware transcoding in Plex modprobe i915 chmod -R 777 /dev/dri # Start the Management Utility /usr/local/sbin/emhttp & Also append the /boot/syslinux/syslinux.cfg file to add 'append initrd=/bzroot i915.alpha_support=1' Note: there is a line break in between the chmod and the # Start line in the go file. Not sure if this matters but I just am writing what exactly I have setup. Reboot the server and make sure your array does not auto start! SSH into your server and enter 'modprobe i915' and then enter 'chmod -R 777 /dev/dri' then reboot the server again. In hindsight I guess I only needed the modprobe i915 in my go file and not the chmod since it appears it didn't provide the proper permissions. Once the server boots, start the array and edit the plex docker in the extra parameters to add --device=/dev/dri I'm sure that somewhere in the many guides it states that the array must be stopped so you can view the directory in a console, so you can make the appropriate permission changes but I don't recall seeing it. It's probably my fault though 😛
  10. I have that I think? I assume you mean in the /coot/config/go file? #!/bin/bash #Setup drivers for hardware transcoding in Plex modprobe i915 chmod -R 777 /dev/dri # Start the Management Utility /usr/local/sbin/emhttp &
  11. Wow. At wits end on this. Updated to 6.9-beta 1 (kernel 5.5.8). Rebooted. Double checked Primary Video set to Onboard. Checked and no /dev/dri. Saw @Squid's post and said ok that's what I'm missing. Added the alpha_support=1 to the /boot/syslinux/syslinux.cfg file. For reference this is what it looks like: default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append initrd=/bzroot i915.alpha_support=1 label Unraid OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui label Unraid OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Unraid OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest Rebooted and still no directory. I think the computer gods want me to buy a nvidia card or something lol.
  12. @Hoopster No there is no /dev/dri directory. I am loading the beta as I type this lol.
  13. @alturismo Thx I will give it a shot. Hopefully this will fix it up.
  14. Oh wow. I'm on 6.8.3 with the linux kernel 4.19.xxx. Maybe that's it? That would suck lol. I just chose the latest stable version i think. So you have it working with UHD 630 GPU... When I try it on Putty SSH to my UNRAID server and type 'modprobe i915' and hit enter, it just goes to the next line as if it completed. No errors anyways.