←back to thread

Snapdragon X2 Elite ARM Laptop CPU

(www.qualcomm.com)
163 points wmf | 4 comments | 24 Sep 25 22:01 UTC | HN request time: 0s | source
Show context
jasoneckert ◴[24 Sep 25 22:44 UTC] No.45366812[source]▶
As someone who has used the Snapdragon X Elite (12 core Oryon) Dev Kit as a daily driver for the past year, I find this exciting. The X Elite performance still blows my mind today - so the new X2 Elite with 18 cores is likely going to be even more impressive from a performance perspective!

I can't speak to the battery life, however, since it is dismal on my Dev Kit ;-)

replies(3): >>45366858 #>>45368580 #>>45369882 #
typpilol ◴[24 Sep 25 22:50 UTC] No.45366858[source]▶
How's the compatibility? Are there any apps that don't work that are critical?
replies(5): >>45366894 #>>45366902 #>>45367015 #>>45368499 #>>45372732 #
electroly ◴[24 Sep 25 23:09 UTC] No.45367015[source]▶
Surface Pro 11 owner here. SQL Server won't install on ARM without hacks. Hyper-V does not support nested virtualization on ARM. Most games are broken with unplayable graphical glitches with Qualcomm video drivers, but fortunately not all. Most Windows recovery tools do not support ARM: no Media Creation Tool, no Installation Assistant, and recovery drives created on x64 machines aren't compatible [EDIT: see reply, I might be mistaken on this]. Creation of a recovery drive for a Snapdragon-based Surface (which you have to do from a working Snapdragon-based Surface) requires typing your serial code into a Microsoft website, then downloading a .zip of drivers that you manually overwrite onto the recovery media that Windows 11 creates for you.

Day-to-day, it's all fine, but I may be returning to x64 next time around. I'm not sure that I'm receiving an offsetting benefit for these downsides. Battery life isn't something that matters for me.

replies(5): >>45367050 #>>45367155 #>>45368372 #>>45369055 #>>45374304 #
1. throw37272835 ◴[25 Sep 25 01:46 UTC] No.45368372{3}[source]▶
Does Remote Desktop into the Surface work well?

When I'm home, I often just remote desktop into my laptop.

I'm wondering if remoting into ARM Windows is as good?

replies(2): >>45368758 #>>45368973 #
2. mcbridematt ◴[25 Sep 25 02:48 UTC] No.45368758[source]▶
I have a similar Windows Arm64 machine (Lenovo "IdeaPad 5 Slim"), RDP into it works OK.

There is one issue I ran into that I haven't on my (self-built) Windows desktops: when Windows Hello (fingerprint lock) is enabled, and neither machine is on a Windows domain, the RDP client will just refuse to authenticate.

I had to use a trick to "cache" the password on the "server" end first, see https://superuser.com/questions/1715525/how-to-login-windows...

3. dboreham ◴[25 Sep 25 03:26 UTC] No.45368973[source]▶
Yes everything in user space works as expected. Note that NT has supported non-x86 processors since 1992.
replies(1): >>45370475 #
4. steve1977 ◴[25 Sep 25 08:21 UTC] No.45370475[source]▶
According to some accounts, the name NT even was a reference to the Intel i860, which was the original target processor.