xccrev

Members
  • Posts

    19
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

xccrev's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Can also confirm this. Sent from my iPad using Tapatalk
  2. Are you passing any other pcie devices through? Like a USB card? I had a very similar experience to yours. Happens on reboot, shutdown; takes down the router and network. Vm and unraid eventually go unresponsive.My USB pcie card wasn't playing nicely when it got the signal to shut down. Took the USB card out it went away. Sent from my iPad using Tapatalk
  3. we are working on it. that's the next step for us too. Just to chime in, I'd also find a docker instance of this to be incredibly useful. Interested in seeing how things develop with this.
  4. I've had some pretty odd experiences with this card as well both on 6.1.9 and 6.2-23 beta. It behaved fine when I passed it through to a Windows VM for a long time. However, I made some system changes (I upgraded my GPU), and then it was causing massive system instability. System hangs, etc. I've been able to reliably pass in the card when there are no usb devices plugged in. But If I try to start the VM with usb devices plugged in, however, I have pretty disastrous results. There are times too when the card seems to be the cause of very high CPU utilization. I've tried stubbing the card out in the syslinux.cfg so that unraid doesn't address it...which didn't really work either. Kinda frustrating because there aren't any other recommended PCI usb cards for oculus.... and currently passing the oculus usb devices through the vm gui individually isn't working for me (I'm running the 6.2-23). I'd be interested in hearing your further experience with this card, and if it has been able to work consistently for you.
  5. To be frank, I haven't read the wiki, so I headed over to "lime-technology.com/wiki/index.php/Setting_up_CPU_and_board_temperature_sensing". The steps in the wiki after based on an older version. Nowadays the installation is more simplified. A short overview Step 1 - preparation Install the perl package, this is required to run the script "sensors-detect" in the background. Step 2 - detection Press the detect button to search and automatically fill in the required drivers or alternatively - if you know the name of the driver(s) - fill them in manually. Step 3 - saving and activation Press the save button to save and activate (load) the driver(s). This will create the fille /config/plugins/dynamix.system.temp/drivers.conf on your flash device. Step 4 - sensor assignment and display Use the dropdown menus under sensors to assign the appropriate sensor for CPU and motherboard readings. You may need to consult the user guide of your motherboard to find out which sensor needs to be selected here. Once a sensor selection is done, the corresponding item will be displayed in the footer at the right of the screen. Press apply to confirm your selection. This will create the fille /config/plugins/dynamix.system.temp/sensors.conf on your flash device. Done Note: to unassign or remove a sensor just unselect it from the dropdown menu. This will also allow to make new assignment (for example when the wrong sensor was chosen). Last but not least: see also the online help of system temp! Worked Beautifully . Thanks for the summary and help.
  6. So, I figured it out. I was following the instructions on the wiki religiously, so I put sensors.conf in /boot/config/plugins/dynamix/ After no dice trying a bunch of things, I took an educated guess or two. Seems, at least for my box, it wouldn't work until I put it in /boot/config/plugins/dynamix.system.temp/ Did I miss the docs on that? I admit I didn't read this entire thread. Or should the wiki be updated? Thanks bonenl and RobJ for the help.
  7. 1. 6.1.9 2. I did have an ad-blocker running. I've whitelisted the GUI, but haven't noticed anything different.
  8. Yep. I installed perl. Didn't use nerdpack though. Just downloaded it and installed using the installer described in the wiki. That & the detection script seemed to work just fine..
  9. Hmm. No dice. I'm set at real time updates. All the sensor fields are grayed out in the plugin...Is this expected?
  10. You didn't actually say what's not working. It all looks fine, from what I can see. What temps are you seeing on the Main page? Ah. Right. Yeah, I'm not seeing any temps on the main page. Or the dashboard. They're supposed to show up towards the bottom, if I'm not mistaken? The sensor command is working fine, but I can't seem to get the temps to pass through to the gui through the plugin.
  11. Can't seem to get this to work. In the plugin under drivers all I'm getting is the 'click detect', but it doesn't seem to do anything. I went through the sensor-detect script in order to get sensors working, and it seems to be outputting temps correctly... Any ideas? root@Tower:~# sensors -u acpitz-virtual-0 Adapter: Virtual device temp1: temp1_input: 27.800 temp1_crit: 105.000 temp2: temp2_input: 29.800 temp2_crit: 105.000 coretemp-isa-0000 Adapter: ISA adapter Physical id 0: temp1_input: 46.000 temp1_max: 80.000 temp1_crit: 100.000 temp1_crit_alarm: 0.000 Core 0: temp2_input: 46.000 temp2_max: 80.000 temp2_crit: 100.000 temp2_crit_alarm: 0.000 Core 1: temp3_input: 42.000 temp3_max: 80.000 temp3_crit: 100.000 temp3_crit_alarm: 0.000 Core 2: temp4_input: 44.000 temp4_max: 80.000 temp4_crit: 100.000 temp4_crit_alarm: 0.000 Core 3: temp5_input: 45.000 temp5_max: 80.000 temp5_crit: 100.000 temp5_crit_alarm: 0.000 nct6791-isa-0290 Adapter: ISA adapter in0: in0_input: 0.904 in0_min: 0.000 in0_max: 1.744 in0_alarm: 0.000 in0_beep: 0.000 in1: in1_input: 1.016 in1_min: 0.000 in1_max: 0.000 in1_alarm: 1.000 in1_beep: 0.000 in2: in2_input: 3.344 in2_min: 0.000 in2_max: 0.000 in2_alarm: 1.000 in2_beep: 0.000 in3: in3_input: 3.328 in3_min: 0.000 in3_max: 0.000 in3_alarm: 1.000 in3_beep: 0.000 in4: in4_input: 1.016 in4_min: 0.000 in4_max: 0.000 in4_alarm: 1.000 in4_beep: 0.000 in5: in5_input: 1.992 in5_min: 0.000 in5_max: 0.000 in5_alarm: 1.000 in5_beep: 0.000 in6: in6_input: 0.112 in6_min: 0.000 in6_max: 0.000 in6_alarm: 1.000 in6_beep: 0.000 in7: in7_input: 3.472 in7_min: 0.000 in7_max: 0.000 in7_alarm: 1.000 in7_beep: 0.000 in8: in8_input: 3.392 in8_min: 0.000 in8_max: 0.000 in8_alarm: 1.000 in8_beep: 0.000 in9: in9_input: 1.120 in9_min: 0.000 in9_max: 0.000 in9_alarm: 1.000 in9_beep: 0.000 in10: in10_input: 0.000 in10_min: 0.000 in10_max: 0.000 in10_alarm: 0.000 in10_beep: 0.000 in11: in11_input: 0.848 in11_min: 0.000 in11_max: 0.000 in11_alarm: 1.000 in11_beep: 0.000 in12: in12_input: 0.000 in12_min: 0.000 in12_max: 0.000 in12_alarm: 0.000 in12_beep: 0.000 in13: in13_input: 0.064 in13_min: 0.000 in13_max: 0.000 in13_alarm: 1.000 in13_beep: 0.000 in14: in14_input: 0.016 in14_min: 0.000 in14_max: 0.000 in14_alarm: 1.000 in14_beep: 0.000 fan1: fan1_input: 2890.000 fan1_min: 0.000 fan1_alarm: 0.000 fan1_beep: 0.000 fan1_pulses: 2.000 fan2: fan2_input: 1030.000 fan2_min: 0.000 fan2_alarm: 0.000 fan2_beep: 0.000 fan2_pulses: 2.000 fan3: fan3_input: 0.000 fan3_min: 0.000 fan3_alarm: 0.000 fan3_beep: 0.000 fan3_pulses: 2.000 fan4: fan4_input: 0.000 fan4_min: 0.000 fan4_alarm: 0.000 fan4_beep: 0.000 fan4_pulses: 2.000 fan5: fan5_input: 0.000 fan5_min: 0.000 fan5_alarm: 0.000 fan5_beep: 0.000 fan5_pulses: 2.000 fan6: fan6_input: 0.000 fan6_alarm: 0.000 fan6_pulses: 2.000 SYSTIN: temp1_input: 31.000 temp1_max: 0.000 temp1_max_hyst: 0.000 temp1_alarm: 1.000 temp1_type: 4.000 temp1_offset: 0.000 temp1_beep: 0.000 CPUTIN: temp2_input: 40.000 temp2_max: 80.000 temp2_max_hyst: 75.000 temp2_alarm: 0.000 temp2_type: 4.000 temp2_offset: 0.000 temp2_beep: 0.000 AUXTIN0: temp3_input: -128.000 temp3_type: 4.000 temp3_offset: 0.000 AUXTIN1: temp4_input: -128.000 temp4_type: 4.000 temp4_offset: 0.000 AUXTIN2: temp5_input: 34.000 temp5_type: 4.000 temp5_offset: 0.000 AUXTIN3: temp6_input: 127.000 temp6_type: 4.000 temp6_offset: 0.000 PECI Agent 0: temp7_input: 40.500 PCH_CHIP_CPU_MAX_TEMP: temp8_input: 0.000 PCH_CHIP_TEMP: temp9_input: 0.000 PCH_CPU_TEMP: temp10_input: 0.000 intrusion0: intrusion0_alarm: 1.000 intrusion0_beep: 0.000 intrusion1: intrusion1_alarm: 1.000 intrusion1_beep: 0.000 beep_enable: beep_enable: 0.000 I've got this for my sensors.conf # Sensor Configuration chip "nct6791-isa-0290" label temp1 "MB Temp" label temp2 "CPU Temp"
  12. I had some initial troubles with getting the SMB shares to stick in Windows 10. After scouring a few Windows forums, I found that switching to a non Microsoft account solved most of those problems. However, I too have been running into issues with playing games in Steam off of a mapped network share on my Windows 10 VM. I run into a similar problem, where the first part of certain games will load, but then when you try to launch them further, they crash. Haven't figured out how to get around that. I'll see if setting up a SMB user with the same credentials makes any difference and post back.
  13. I'm using a Windows 10 VM and this definitely did some wonders for me. Now, the USB 3.0 hard drive I have will mount without any complaints, whereas before it wasn't even showing up.