Live data from Hacker News

CUDA on Windows Subsystem for Linux 2

devblogs.nvidia.com

161–170 of 221 posts

Re: CUDA on Windows Subsystem for Linux 2

#161

Too bad you need wsl2, i hate running hyperv and the apps that dont play nice with it.

Which apps are broken for you? We’ve been working with VMware and Google to ensure their apps well with Hyper-V, but I know there are still some gaps.

The new release of VMware Workstation now works with Hyper-V as its hypervisor but a bunch of people (and I'm one of them) have experienced massive, unacceptable performance regressions for VM guests. I had to disable Hyper-V and hence stop using WSL2 until it's resolved. If the performance issues are intrinsic this will probably be a permanent showstopper for people who rely on VMware or Virtual Box. Hopefully this gets sorted out one way or another.

Re: CUDA on Windows Subsystem for Linux 2

#162

Earlier quoted context omitted.

Just to add to this: Linux is happy to work in whatever way is convenient to you. WSL2 is case and point here. Windows is less flexible. If I can get everything I want out of one environment (stable gui, business software, and a native-like linux shell), that will save me the hassle of multiple machines, traditional VMs, or dual booting. I don't think we will see the Linux Subsystem for Windows 2 ever. I also am not…

The Linux Subsystem for Windows 1, on the other hand, is called Wine and works impressively well. Better than WSL1 did, at any rate.

Surely wine is a windows subsystem for linux?

absolutely _nothing_ about the subsystem made by microsoft is "for linux".

I also still dont understand what you get for paying for a windows licence to run linux except more overhead and a total lack of a package manager.

Re: CUDA on Windows Subsystem for Linux 2

#163
post #108

Earlier quoted context omitted.

I'm exactly the audience Microsoft is winning over. For the last 3-5 years, I've been an avid Mac user. The primary reason has always been the familiarity of the terminal. Now, Apple is making a lot of hardware decisions that I don't like. Having used WSL daily for several months now, it's the game changer. My next laptop will probably be a PC, and I can only say this because of WSL.

Your next laptop will be a personal computer?

Apple spent a lot of money selling the idea the Mac was totally different to the PC:

https://www.youtube.com/watch?v=0eEG5LVXdKo

Re: CUDA on Windows Subsystem for Linux 2

#164
post #141
post #59

Earlier quoted context omitted.

Why would it matter if it's upstream? Upstreaming something like this is not really useful to anyone but Microsoft; it is still something that is inextricably tied to Windows and WSL. The point is not "extinguishing" Linux per se, it's achieving enough lock-in that only Linux that Microsoft customers can use is WSL.

WSL is not a Linux. It is a Windows subsystem for running Linux userlands. (Almost as if the WSL name isn't totally nonsense!) The "default" is Ubuntu. But Debian is supported, OpenSUSE is supported, Kali is supported. Unsupported but available, you can get Alpine, CentOS, Fedora, Arch, lots of distros.

You could say that WSL is not a GNU/Linux. But since WSL comes with its own kernel, part of it is definitely a Microsoft-extended flavor of the Linux kernel.

Even if this driver went upstream, it wouldn't be any less tied to the WSL virtualization platform.

Re: CUDA on Windows Subsystem for Linux 2

#165
post #132
post #95

Earlier quoted context omitted.

> And that’s not all. I close my laptop lid when my laptop is docked. Windows helpfully sleeps the laptop even though external monitors, a mouse, and a keyboard are connected. There is no fix. Right click the battery icon in the system tray > Power Options > Choose what closing the lid does > Do nothing.

Of course, then lid close will never work as intended. What I want is for lid close to sleep IFF no external monitors are connected, regardless of whether the machine is on AC power or not. Thank you for the suggestion, and in my actual solution, I basically programmatically switch this setting on and off based on whether or not external monitors are connected.

As it should not. Need to move the laptop into another room? Better not close the lid!

Just disable it and actively sleep when you do want to sleep. This is the most sensible way even if you never have any external monitors attached.

Re: CUDA on Windows Subsystem for Linux 2

#166
post #165
post #132

Earlier quoted context omitted.

Of course, then lid close will never work as intended. What I want is for lid close to sleep IFF no external monitors are connected, regardless of whether the machine is on AC power or not. Thank you for the suggestion, and in my actual solution, I basically programmatically switch this setting on and off based on whether or not external monitors are connected.

As it should not. Need to move the laptop into another room? Better not close the lid! Just disable it and actively sleep when you do want to sleep. This is the most sensible way even if you never have any external monitors attached.

What the hell. It’s one thing to say you prefer nothing to happen on lid close. That’s cool. I don’t want that. This is like saying, “I would like a mocha” and having the barista say “Wrong, you want an iced coffee.” No, I do want my laptop to sleep on lid close, just not when it’s docked. This is clearly not much to ask for considering Linux and macOS do it just fine by default and I can still disable sleep on lid close if I want to.

Why is it better for Windows to do this wrong? It is clearly a side effect of the fact that the Power Policy system only differentiates between AC and DC and no other conditions.

What happens when I move rooms? Well, I only have one docking setup. But also, it is not a problem if my laptop spuriously goes to sleep. (My solution does not automatically sleep the laptop when it is undocked, either, so this is also still not an issue.)

Re: CUDA on Windows Subsystem for Linux 2

#167
post #113

Earlier quoted context omitted.

WSL2 came out (in non-preview version) last month and is a vital improvement. Windows Terminal is still pre-1.0 as is the CUDA and DirectX on Linux stuff. Then give it a bit of time to percolate through, technically and socially.

> Windows Terminal is still pre-1.0 Windows Terminal 1.0 has been out for a bit, the current version is 1.0.1401.0 [0] [0]: https://github.com/microsoft/terminal/releases/tag/v1.0.1401...

I guess the writing’s on the wall now. The latest lines of Apple products have been all been disappointing to me: laptops and phones without ports, keyboards that break, silly gimmicks all about — and a smartwatch that I developed a skin rash from so bad I still have it now, four months after having stopped using the watch.

CUDA was always the big thing for me, I use CUDA and develop with it — AMD and Apple have missed their shot on this, in an absolutely massive way. Alienate developers with centralized app stores and huge fees, then alienate researchers by picking a fight with the biggest name in the GPU industry while providing no alternative. Silly.

I haven’t used Windows in years and it will be so so bittersweet the day I boot it up on a Dell laptop again.

Re: CUDA on Windows Subsystem for Linux 2

#169
post #65

Pity. CUDA was/is proof positive that Linux on the desktop is perfectly feasible and that you can use it to both do a UI and do meaningful computation on the same machine without getting tied down into all kinds of licensing schemes. Opening this further up to Windows gives fewer people a really good reason to try out Linux as their daily driver. I personally don't get why any developer would prefer Windows over Linu…

> I personally don't get why any developer would prefer Windows over Linux Because windows now literally has all the stuff Linux has plus a lot more. The only reason for a well paid developer to prefer linux over windows for a desktop OS is that you don't need any of the extra stuff (a decent desktop experience, hardware support and a commercial end user software eco system) or that you have some fundamental objectio…

>The only reason for a well paid developer to prefer linux over windows for a desktop OS is that you don't need any of the extra stuff (a decent desktop experience, hardware support and a commercial end user software eco system) or that you have some fundamental objections concerning Microsoft's business practices. These are good reasons, but experience shows that most people don't care enough about things like privacy to give up convenience or shiny things.

Sometimes it is simply the problem of linux being utterly broken. Linux users wonder why people won't adopt linux, and it is because it is full of problems. I spent a full day this week trying to get an internet connection for my linux desktop working (sans ethernet cable) and was unable to. USB tethering was broken for unfixable reasons and wifi adapters are a nightmare with linux. So that drove me back to windows, I tried WSL, and now I probably just won't ever bother trying to run linux on desktop again. I didn't want to tinker with my software, I wanted to do my personal projects. Windows at least lets me get the job done.

Re: CUDA on Windows Subsystem for Linux 2

#170

Having set this up, this is going to be absolutely huge for ML. A lot of nonsense is getting cut down by this: 1. You don't have to install special CUDA-specific drivers that are behind the normal gaming drivers anymore. You'll soon be able to just use the Regular nVidia Drivers (and even now, all you need to do is install a Beta driver version). That's huge for someone just starting out, they don't have to have "the…

> without the technical issues of Desktop Linux (aka the Wayland Nightmare) Nobody is forced to use Wayland. It’s still quite experimental, I think only Gnome enables it by default.

I've been using Gnome+Wayland for over a year and been quite happy with it
Post reply on HN