Jump to content

craigr

Members
  • Content Count

    383
  • Joined

  • Last visited

Community Reputation

16 Good

About craigr

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • URL
    http://www.cir-engineering.com
  • Location
    Chicago USA
  • Personal Text
    Video Calibration Engineer

Recent Profile Visitors

1452 profile views
  1. So the simplest solution to solve my issue was to install two Logitech "unifying receivers." One is for the keyboard and is plugged into the VM USB controller. The other is for the mouse and is plugged into the unRAID USB controller and is passed through to the VM using evdev. This way the keyboard works inside Win10 as usual with all the hot keys, and the mouse can be used to wake the Win10 VM from sleep because of the evdev passthrough. ...added benefit was a good excuse to upgrade and buy a Logitech K800 keyboard Best, craigr
  2. dmacias just want to say thanks for your continued support of this app. I really appreciate it. Kind regards, craigr
  3. I'd also put in that I would love to use this with the iGPU in my E3-1275 v6 while running PLEX. I've used the two dockers available, but having the info right in the dashboard would be much nicer than running an entire additional docker just to get the info. Kind regards, craigr
  4. So changing the CPU caused the MB to also automatically change settings back to defaults in the BIOS. I just had to go back in and turn on my onboard graphics. The i915 and i965 both use the same module so that could never have been it. Best, craigr
  5. Looks like it uses the i965? I tried this: root@unRAID:~# modprobe i965 modprobe: FATAL: Module i965 not found in directory /lib/modules/4.19.107-Unraid root@unRAID:~# I checked and I don't even have a "lib" directory, just some other directories that start with lib. Do have the i965 driver in unRAID though.
  6. What CPU do you have? I just changed from an E3-1275 v5 to the same but v6. The v6 can hardware encode hvec. I am however now frustrated because with the new v6 CPU no /dev/dri folder is created after typing modprobe i915. I even tried modprobe -r i915 and then redid modprobe i915 with no lock. There is just no dri folder ever created. Does the v6 have something other than i915? Any thoughts as to how I can get this running with the E3-1275 v6? Thanks, craigr
  7. Does anyone know how to fix this? I have been all over the web and found numerous solutions all involving editing the registry and none have worked. I spent to many hours on this today and got nowhere. Any help would be welcome. Thanks and kind regards, craigr
  8. Yeah, but than I lose my evdev capabilities 😒 I never worried about it before, I probably shouldn't start now. It's just that the sleep button up there seems awful appealing to use now.
  9. So I have a lowly Logitech K270 keyboard, but it has some hotkeys across the top. I can't get them to work. Does anybody have any idea how this might be possible. I did install the Logitech PS2 driver, but that didn't change anything except that the device manager now reports the drivers are Logitech instead of Microsoft. Thanks, craigr
  10. Also, don't forget to turn "Link State Power Management" back on in the Windows 10 advanced power options settings. craigr
  11. No idea. I just did this today. I will have to test this though. I've got my UPS set to shutdown unRAID if I lose power for 10 seconds (it's not a big UPS and I have 22 drives). I don't know if unRAID would give Windows the default 60 seconds to shutdown gracefully or not. My guess is that it would try and shutdown windows gracefully, but I think that could be a problem because I don't want my UPS to have to work for an extra 60 seconds shutting down Windows. I also doubt Windows could wake from sleep and then shutdown in less than 60 seconds... than again, unRAID may not even know to wake a sleeping VM to shut it down gracefully 😬 I'd actually rather unRAID just yank Windows with a hard shutdown. The next time I have to power down the server I will pull the power on the UPS with Windows asleep and see what happens under controlled conditions. I'll report back with results. I know I am going to be doing some hardware changes next Tuesday or Wednesday so I'll find out then or before. Kind regards, craigr
  12. I know many people scoff at sleeping a VM, but I really want to put my Windows 10 VM's to sleep because they are constantly doing things in the background and utilizing a lot of CPU. It costs me about 50 watts to not sleep the VM and to me that is just a waste. The trouble has been how to wake them up easily without using another device. All you have to do to make the mouse and keyboard wake Windows from sleep is use evdev to pass them through instead of the Windows template. The easiest way to learn how to do this is to watch and mostly follow Spaceinvader's new tutorial on evdev: I'm sure he will fix it, but please note that Spaceinvader doesn't quite have the syntax correct in the qemu.conf. The correct syntax is in my post just below his in the linked thread. Once you get it right, your mouse and keyboard will be able to wake your Windows VM from sleep 🤩 Also, don't forget to turn "Link State Power Management" back on in the Advanced settings of the Windows 10 Power Options, otherwise your computer may just hard shutdown instead of sleep. I am finally happy! Best regards, craigr
  13. Question for you though. I did the "optional" virtio driver install for Windows 10 and then did install the virtio drivers and things were very snappy after that. However, I mucked about with my xml again after the fact, and am afraid that I may not have the virtio drivers installed properly now. Is there a way that I can verify that I have the virtio drivers installed in Windows 10 for my mouse and keyboard? I attached a grab of my device manager. For the keyboard and mouse the drivers both say Microsoft. Under "Human Interface Devices," are the VirtIO Input Drivers the actual virtio drivers for my moue and keyboard, or did I screw something up when I was later mucking about? The mouse and keyboard don't seem as snappy anymore compared to right after I installed their virtio drivers, but it could easily be my imagination. I have attached a copy of my current XML file as well. Kind regards, craigr current.xml
  14. I just used this tutorial SpaceInvader, thanks for another great one! I had just started looking at evdev as a means to use the mouse and keyboard to wake my Windows 10 VM up from sleep. I know a lot of people don't like to sleep their VM's, but I do to save electricity. And, the good news is that it works 🙂 You do have a couple errors in the tutorial syntax for the qemu.conf though. In the qemu.conf, you are missing a comma at the end of the line after "/dev/hpet", and you should not have a comma after the final device. This is what you have in your video and in your text instruction file: 3/. Next we need to add our input devices to the qemu conf file nano /etc/libvirt/qemu.conf use (ctrl _ ) to goto line 451 find this part #cgroup_device_acl = [ # "/dev/null", "/dev/full", "/dev/zero", # "/dev/random", "/dev/urandom", # "/dev/ptmx", "/dev/kvm", "/dev/kqemu", # "/dev/rtc","/dev/hpet" # ] Remove hashtags then add the parts in that you want to use cgroup_device_acl = [ "/dev/null", "/dev/full", "/dev/zero", "/dev/random", "/dev/urandom", "/dev/ptmx", "/dev/kvm", "/dev/kqemu", "/dev/rtc","/dev/hpet" "/dev/input/by-id/usb-Logitech_USB_Receiver-event-kbd", "/dev/input/by-id/usb-Logitech_USB_Receiver-if01-event-mouse", ] Instead, you should have: cgroup_device_acl = [ "/dev/null", "/dev/full", "/dev/zero", "/dev/random", "/dev/urandom", "/dev/ptmx", "/dev/kvm", "/dev/kqemu", "/dev/rtc","/dev/hpet", "/dev/input/by-id/usb-Logitech_USB_Receiver-event-kbd", "/dev/input/by-id/usb-Logitech_USB_Receiver-if01-event-mouse" ] So a comma after dev/hpet", and no comma after /usb-Logitech_USB_Receiver-if01-event-mouse". If you type it in according to your example, after the reboot you'll get a "Libvirt Service failed to start" and obviously no VM support... that's what happened to me until I corrected it. Anyway, your videos save me sooooo much time, so thanks again. I literally started looking at evdev yesterday evening and was like, "is it really worth learning all this just to get my VM to wake up." Then I quickly just happened to look at your channel, and your tutorial for exactly what I wanted to do was right on top. You're the best man! Kind regards, craigr
  15. So it turns out that it was the rom files from techpowerup.com that were not correct. I downloaded my own actual BIOS from the video card using the command prompt and the VM starts perfectly with my own rom file. Just goes to show, you can't always trust techpowerup even after removing the header. If anyone needs a rom file for an Inno3D GTX 1050 Ti 4 GB that will actually work, I have attached it here. Hope this helps someone else. Best, craigr Inno3D.GTX1050Ti.4096.(version_86.07.59.00.1B).rom