Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

CUDA on Windows Subsystem for Linux 2

devblogs.nvidia.com

Post reply on HN
Print view View original

181–190 of 221 posts

Re: CUDA on Windows Subsystem for Linux 2

#181

Post by noir_lord »

anaisbetts wrote: post #21

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…

> (aka the Wayland Nightmare and DPI issues everywhere)

The picture is more mixed than you present.

I use Fedora at 2560x1440@14" and 2 by 3840x2160@27 and the dpi thing isn't an issue, set your font scaling to 1.5 and that's about all you need to do.

I dual boot windows and fedora (for gaming in the former and dev in the latter) and Windows 10 is by far more unpleasant to deal with, updates that tie your machine up for significant time, drivers are still "track down random binary from random vendor site and hope it works" vs "sudo dnf update" is (for me) no comparison at all.

Into the territory of personal preference, Cinnamon is a better desktop on than Windows - it's more responsive, more cohesive, closer to the classic WIMP interfaces I prefer.

As for wayland, I don't use it yet, I will when it's been stable for a year or two.

Re: CUDA on Windows Subsystem for Linux 2

#182

Post by SXX »

bzb3 wrote: post #114
SXX wrote: post #50

Earlier quoted context omitted.

WSL2 and all these features don't have anything to do with open source either. It's basically a shim for communication of two proprietary bits of software on both sides. Fortunately all these graphics and compute shims will never get merged into upstream kernel so they'll be second-class citizens like forever. Dave Airlie who is maintainer of Linux graphics subsystem will never allow to merge it since it's can only b…

It's incredible that people like you are bitter because others are given a choice and they don't choose what you would want them to. And all in the name of freedom, no less.

I have no bitterness here, just facts. It's important to understand that none of these WSL features has anything to do with open source. It's exactly your standard "extend" stage.

See: proprietary hypervisor runs OS with a patched non-upstreamable Linux kernel and then there is proprietary userspace drivers and libraries that able to talk to their proprietary parts inside Windows.

Can any of it be used with different hypervisor? No.

Can it be used with open source drivers? Again, nope.

Re: CUDA on Windows Subsystem for Linux 2

#183

Post by jchw »

tjoff wrote: post #172
jchw wrote: post #166

Earlier quoted context omitted.

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 c…

It came out harsh, sorry. But it is more like asking for a 33cl beverage but getting 35cl. There are tons of issues with a computer spuriously going to sleep. Network connectivity dies for one, as well as lots of minor quirks such as music stops etc. Having control of that is quite essential. Being forced to manually sleep despite ones preferences is not a major issue. It is a sub-second operation that comes with lot…

On the flip side, a laptop failing to go to sleep can be a fire hazard or at least permanently damage your laptop, depending on where it’s stored. This killed one of my X1 carbons.

Re: CUDA on Windows Subsystem for Linux 2

#184

Post by RMPR »

jfim wrote: post #95
jchw wrote: post #87

Earlier quoted context omitted.

> (aka the Wayland Nightmare and DPI issues everywhere) It’s more of a pick-one. Wayland has pretty good per monitor scaling; your X11 apps will be blurry but that’s about all I’ve experienced. The Windows DPI nightmare long surpassed it anyways. On a typical Wayland desktop the usual biggest problem is the DPI being set wrong for a monitor. Even on X11 the worst you get is applications that don’t scale correctly. On…

> 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.

Exactly what GP was saying

>the Windows desktop gets a free pass because everyone has internalized the ways that it sucks.

Re: CUDA on Windows Subsystem for Linux 2

#185

Post by RMPR »

tjoff wrote: post #165
jchw wrote: 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.

>the Windows desktop gets a free pass because everyone has internalized the ways that it sucks.

Re: CUDA on Windows Subsystem for Linux 2

#186

Post by calaphos »

noir_lord wrote: post #181
anaisbetts wrote: post #21

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…

> (aka the Wayland Nightmare and DPI issues everywhere) The picture is more mixed than you present. I use Fedora at 2560x1440@14" and 2 by 3840x2160@27 and the dpi thing isn't an issue, set your font scaling to 1.5 and that's about all you need to do. I dual boot windows and fedora (for gaming in the former and dev in the latter) and Windows 10 is by far more unpleasant to deal with, updates that tie your machine up…

In my experience high DPI actually works somewhat decently and those fractional stuff can be fixed with don't scaling. At least if you only use one monitor. I personally have two I would use with 1.25x and no scaling which is just not possible with the x11 model.

Additionally having two monitors completely breaks vsync with very ugly tearing lines.

And Wayland on Nvidia has been very unsuccessful for me. Even when I got it to run the performance in e.g. firefox was absolutely terrible. Sadly Wayland is necessary if you want hardware video decoding.

Re: CUDA on Windows Subsystem for Linux 2

#187

Post by tjoff »

jchw wrote: post #183
tjoff wrote: post #172

Earlier quoted context omitted.

It came out harsh, sorry. But it is more like asking for a 33cl beverage but getting 35cl. There are tons of issues with a computer spuriously going to sleep. Network connectivity dies for one, as well as lots of minor quirks such as music stops etc. Having control of that is quite essential. Being forced to manually sleep despite ones preferences is not a major issue. It is a sub-second operation that comes with lot…

On the flip side, a laptop failing to go to sleep can be a fire hazard or at least permanently damage your laptop, depending on where it’s stored. This killed one of my X1 carbons.

Exactly, I see that as yet another benefit of being explicit about it.

Re: CUDA on Windows Subsystem for Linux 2

#188

Post by tjoff »

RMPR wrote: post #185
tjoff wrote: post #165

Earlier quoted context omitted.

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.

>the Windows desktop gets a free pass because everyone has internalized the ways that it sucks.

I don't use windows on my laptop, I also don't have external displays connected to it. Yet turning off auto-sleep is a no-brainer.

Re: CUDA on Windows Subsystem for Linux 2

#189

Post by deno »

riquito wrote: post #131
deno wrote: post #46

Earlier quoted context omitted.

VSCode works just fine with hidpi on Linux. It’s just an Electron app after all, and Chromium has had hidpi support since forever.

? there's an enormous effort to fix the blurry chromium on wayland (and by extension electron and vscode), codenamed ozone, and vscode make me painfully aware of it every day. Afaik there's no official vscode build on ozone. https://bugs.chromium.org/p/chromium/issues/detail?id=578890

That’s an effort to have Chromium work natively on Wayland. It works just fine on X.org and even under Wayland with XWayland if you use something like ChromeOS’s Sommelier or just set window.zoomLevel/--force-dpi-something=2 (and not have XWayland windows scaled).

Re: CUDA on Windows Subsystem for Linux 2

#190

Post by SXX »

MikusR wrote: post #151
SXX wrote: post #50

Earlier quoted context omitted.

WSL2 and all these features don't have anything to do with open source either. It's basically a shim for communication of two proprietary bits of software on both sides. Fortunately all these graphics and compute shims will never get merged into upstream kernel so they'll be second-class citizens like forever. Dave Airlie who is maintainer of Linux graphics subsystem will never allow to merge it since it's can only b…

So Linux graphics subsystem has only support for MIAOW GPU?

The only proprietary part in AMD and Intel graphics stack is GPU firmware. Both companies have few closed-source components that might work on top of the same open-source kernel drivers, but they all have open source alternatives.
Post reply on HN