hypevhs
hypevhs
I'm on stable right now, virtualization and module loading are OK. I will post again when beta channel is installed. In the meantime: ## Cave, Stable Channel - **Platform:** 9901.77.0...
I was worried it was going to ask me to powerwash when moving to beta, I guess not. ## Cave, beta channel [//]: # (Version 63.0.3239.50 Official Build beta 64-bit)...
## Cave, developer channel - **Platform:** 10134.0.0 (Official Build) dev-channel cave - **Firmware:** same as above - **Build Date:** Thursday, November 16, 2017 ``` chronos@localhost / $ uname -a Linux...
It boots fine after running this command: ``` chronos@localhost / $ sudo change-kernel-flags -f "lsm.module_locking=0" Password: /tmp/change-kernel-flags.xtT.4 make_dev_ssd.sh: INFO: Saving Kernel B config to /tmp/change-kernel-flags.xtT.4 make_dev_ssd.sh: INFO: (Kernels have not...
Just in case you needed additional proof, I ran `sudo change-kernel-flags -f "disablevmx=off"`, rebooted, and immediately got stuck in the boot loop again. Great work isolating the issue! If there...
The bug seems to have been fixed and merged into 4.14. Now I have to wait until they cherry pick it onto 3.18, and then it makes it into a...
Dev channel recently updated from 3.18.0-16503-ge33b03ba1f58-dirty to 3.18.0-16977-gc20001a59640 It's a huge update and mentions "vmx" in git show. I'd love to test it (and the kernel param that disables kaiser)...
If the output already exists in the store, running this will build just one time, even though it displays "(round 1/4)". ```zsh nix build '.#somepkg' --no-link --rebuild --repeat 3 ```...
I just put `BUNDLE_FORCE_RUBY_PLATFORM = "true";` in my call to mkShell. I had `x86_64-linux` in my Gemfile.lock `PLATFORMS` and it wouldn't work correctly until I removed that file then re-ran...
@lajp That is cool. AFAICT your method isn't hacky at all, since the torrent-selection arg `-t` does almost the same thing [here](https://github.com/lajp/transmission-remote-rename/blob/27697d1d85fb448852e964acfc97576560bbeac4/utils/remote.c#L2349). I would however advocate for a path length...