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

131–140 of 221 posts

Re: CUDA on Windows Subsystem for Linux 2

#131

Post by riquito »

deno wrote: post #46
cbhl wrote: post #31

Earlier quoted context omitted.

Xming on Windows isn't exactly a walk in the park either -- I'd still rather use the native, proprietary build of VSCode on a proprietary OS with the SSH extension if I'm on a high-DPI screen.

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

Re: CUDA on Windows Subsystem for Linux 2

#132

Post by jchw »

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.

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.

Re: CUDA on Windows Subsystem for Linux 2

#133

Post by mattkrause »

stephen_g wrote: post #125
ilyas121 wrote: post #120

Can someone explain to me the WSL acornym? Isn't WSL really a Linux subsystem for Windows? tiny pet peeve

Yeah, it's very confusing. I've heard it explained but I still think it doesn't really make sense. The core of the argument that I've heard is that Windows has multiple subsystems so they say it's a "Windows Subsystem", but the 'for' in "For Linux" still makes no sense. The arguments for not calling it something like "Linux Subsystem [for/on/in] Windows" don't seem to match up with the fact that there used to be a si…

Windows Subsystem for (running) Linux (programs).

Re: CUDA on Windows Subsystem for Linux 2

#134

Post by adolfojp »

anonymousDan wrote: post #12
benbristow wrote: post #9

Earlier quoted context omitted.

Does kind of feel that way. Having a full Windows Desktop with good graphics drivers and software like Microsoft Office, Photoshop, commercial games etc. and Linux for the programming/server-software side of things. I have literally no reason to dual-boot with Ubuntu anymore. WSL2 and Visual Studio Code fulfils all my Linux coding requirements. Maybe (probably?) a bad thing but it's damn convenient.

Yeah I just started using Windows 10/WSL yesterday and I have to say I'm impressed. Are there any downsides/painpoints I should be aware of?

Be aware of the fact that WSL 1 and 2 can coexist. Running wsl -l -v from PowerShell should tell you which distribution is using which subsystem. You can change between the two.

If you're using WSL 2 and you put your Linux files on the Windows filesystem IO performance becomes spectacularly awful. If you keep your Linux files on the Linux filesystem it works rather well.

Docker should be installed on the Windows side with Docker Desktop and then associated with your Linux machines under Docker Desktop settings. This makes it available on both Windows and Linux. If you install it directly on Linux it only becomes available on that Linux installation and you get no interoperability.

Systemd tools will yell at you. I encountered issues when running systemctl. There are some fixes but I don't know if they work because I'm lazy so I worked around the issue instead.

I don't know if accessing the Linux files from Windows breaks them. I'm using VSCode remote extensions instead of mounting \\wsl$ and accessing it directly.

Re: CUDA on Windows Subsystem for Linux 2

#135

Post by adolfojp »

ilyas121 wrote: post #120

Can someone explain to me the WSL acornym? Isn't WSL really a Linux subsystem for Windows? tiny pet peeve

It was a legal / trademark concern. Naming the thing Linux something something was deemed too risky so they went with Windows something something instead.

Re: CUDA on Windows Subsystem for Linux 2

#136

Post by SiebenHeaven »

jchw wrote: post #132
jfim wrote: 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.

I think there's an option in settings to select the primary display - if you set that to the external display, theoretically it should work. My laptop stops sleeping on lid close with this.

Re: CUDA on Windows Subsystem for Linux 2

#137

Post by mortehu »

patrec wrote: post #65
jacquesm wrote: post #10

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…

A couple of big things still missing with WSL:

Direct rendering for X. This means the maximum OpenGL version that can be supported with hardware acceleration is 1.4, so many modern X program don't work or will use software rendering.

Multi-monitor support. Under X, windows are by default positioned and sized by the window manager and it's hard for application developers to screw it up, but under Windows each application developer has to be careful to make their program work well on multiple monitors. This shows, and event some built-in Windows applications get confused by multiple monitors, usually by having an action performed on one monitor open a window on a different monitor.

Re: CUDA on Windows Subsystem for Linux 2

#138

Post by aspenmayer »

benbristow wrote: post #19
jacquesm wrote: post #10

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…

You can use those software repositories through WSL2, using apt as per usual. And Windows now has WinGet so you can install software just like you would with apt/yum/pacman etc. It's definitely not as robust - you can't uninstall stuff using WinGet but the concept is there.

There’s a rapidly growing third-party ecosystem growing around WinGet, as well. It’s promising. Here’s an example of a WinGet webgui thingy: winstall.[1][2]

Do you or wider HN users have any picks for WSL/2 and/or WinGet tools?

[1] https://winstall.app

[2] https://github.com/MehediH/winstall

Re: CUDA on Windows Subsystem for Linux 2

#139

Post by [deleted] »

SXX wrote: post #91
mycall wrote: post #76

Earlier quoted context omitted.

Is this the wrong repository for what you are referring to, as this appear open source? https://github.com/microsoft/WSL2-Linux-Kernel

This custom kernel only contain shim that needed to pass commands from proprietary component on Linux to proprietary drivers on Windows. When it's come to graphics drivers Linux upstream don't accept any code that can only be used for proprietary components. So all this Direct3D and CUDA shims never gonna be merged.

[deleted]

Re: CUDA on Windows Subsystem for Linux 2

#140

Post by ben-schaaf »

alerighi wrote: post #43
etaioinshrdlu wrote: post #13

Earlier quoted context omitted.

Well, CUDA is about the opposite of open source. It needs special hardware and a closed source driver. CUDA on Windows was already a big deal in engineering. Scientists and academics preferred Linux (and python, and docker) and Windows is playing catch up there to become compatible with the tools that have grown in popularity over the last 5 years. Personally, as an open source advocate, I think competition (even fro…

Also Linux is becoming the new Windows, and is one of the reason I stopped using it. What is the point of using a system that on every release is more and more bloated and full of crap that it breaks? Docker for example, I hate it, it serves no purpose beside wasting disk space and slowing down your machine. BTRFS is a bugged imitation of ZFS. Wayland not only is bugged but even does less things than Xorg. Most scien…

It's funny that you list docker and wayland as linux bloat that freebsd doesn't have, when docker works just fine on freebsd and wayland support is also in the works.

Personally I use Ubuntu as a daily driver. No docker unless you install it and comes with Xorg (as well as wayland, but you're not forced to use it).

Post reply on HN