thor2002ro

Members
  • Content Count

    48
  • Joined

  • Last visited

Community Reputation

13 Good

About thor2002ro

  • Rank
    Newbie

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. No don't update the md driver is different... But its safe it's just that the kernel will be replaced with stock
  2. I will update it when I get some time but currently a little swamped at work the current kernel works great at the moment so not in any hurry I didn't observe any issues with the current build on my server
  3. As I remember the 5700xt reset issue is with non referance/founder edition cards doesn't matter what kernel version are you on.....
  4. Sorry to hear that.... My vega 56 has been great.... With the reset module apart from not being able to reboot a vm... I need to shut it down and start it up again if I need to reboot
  5. sounds weird.... don't know about plex... I use jellyfin and emby.... I have a GTX970(primary) and a Vega56 I use nvidia for transcoding and can start vm with it no issue... I don't need to shutdown any docker container.... or prepare it in any way.... and after the VM is stopped the driver resumes.... when VM is started the docker container trascodes with CPU.... when the GPU is available again it switches back to gpu on the next transcode When transcoding usually power state should be P2 .... and P0 when idle in power saving.... Also starting and sto
  6. I wouldn't .... if they changed the version of the md driver ....but on the other hand it wont explode....it wont start the array that's it...
  7. glad you fixed it.... I really need to make a plugin like install method.... to make stuff easier.... PS: after some testing it seams amdgpu driver doesn't need to be blacklisted if you use AMD GPU for VM passthrough to windows VM, works great.... but not so great with linux VM crashes the driver....
  8. dono what to say.... maybe it was a flash write error .... try to overwrite the files again and be sure to safely remove the flash stick and try again....
  9. no..... you dont need the original files ..... but the kernel you are loading seams to be 5.9.4 not 5.10rc4..... so the bzimage is not the right one for sure....
  10. you need to update the hole thing not just the packages.... the packages are tied to the kernel.... bzimage and bzmodules
  11. release 5.10rc4-20201118 update to 5.10rc4 nvidia driver update 455.45.01 fixed nvidia docker corsair power supply kernel driver Add RCEC handling to PCI/AER v11 add support for virtio-mem: Big Block Mode (BBM) update ntfs3 driver v12 updated bzfirmware(get last from 5.9.1-20201026 release) removed all old AMD GPU reset quirks add support for new AMD GPU reset module vendor_reset(auto resets all AMD GPUS when it needs to please dont run any other reset methods, to use add in /config/go file "modprobe vendor_reset") supports: AMD | Polaris 10 | AMD | Polari