❌

Normal view

Two variants of Nvidia's RTX Spark show up on Geekbench, revealing a cut-down 18-core model β€” Full 20-core beats most x86 mobile chips across multi-core and single-core tests

Two new Geekbench listings for Nvidia's upcoming RTX Spark laptop superchip have surfaced, confirming a second, cut-down SKU exists with 18 CPU cores, at least in the testing phases. Both parts score remarkably close to each other, posting impressive multi-core numbers, but their single-core performance isn't special. Still, these are preliminary results on unreleased hardware, so take these numbers with a grain of salt.

The model name for the 20-core (10+10) SKU was shown as "OEMQAJ 766_MIS Product Name DV" with its clocks reported at 4.0 GHz. This chip scored 2,570 points in the single-core test and 23,126 points in the multi-core test. The second listing showed up as "OEMQAJ OEMQAJ Product" with this SKU's 18 cores divided across 10+8 core clusters, clocked at 3.9 GHz. It scored 2,541 points in the single-core test, so within 1% of the 20-core part, while the multi-core was 21,776 points, which is about 6% faster than the full-fat chip.

RTX Spark Superchip Geekbench listing
20-core SKUWccftech
RTX Spark Superchip Geekbench listing
18-core SKUWccftech

When you compare these numbers to other Windows-running SoCs on the Geekbench database, these multi-core numbers are among the best. The Snapdragon X2 Elite Extreme currently holds the record for the highest multi-core score with 25,075 points, so both SKUs of the RTX Spark lose to it. But when we switch to the AMD AI Max+ 395, which scores 20,609 on average in the same test, even the 18-core Nvidia chip is 5.6% faster here, and the 20-core variant is about 12% faster.

Compared to Apple's lineup, the 20-core RTX Spark is 3.3% faster than the 14-core variant of the M3 Max, which scores 22,385 points in the multi-core bench. Considering that this is pre-release hardware with unoptimized drivers, we can expect it to even beat the maxed-out M4 Pro and the base M4 Max (which hover around 25,000 points) when it officially launches. Moreover, the 18-core SKU's 21,776 points are equal to, if not more than, the base M4 Pro, which also nets around 21,700 points in the multi-core test.

Multi-core peformance

SKU

Score

Difference

20-core RTX Spark

23,126

Baseline

18-core RTX Spark

21,776

-5.84%

Snapdragon X2 Elite (Extreme X2E-94-100)

25,075

+8.43%

Intel Core Ultra 9 275HX

20,783

-10.13%

AMD AI Max+ 395

20,609

-10.88%

Apple M3 Max (14-core)

22,385

-3.20%

Apple M4 Pro (14-core)

24,901

+7.68%

That being said, the swan song falls apart when we bring up the single-core numbers. Every Apple Silicon chip from the base M3 onwards beats the 2,570 points the 20-core RTX Spark achieved in this run. Only the M2 Max with its 2,477 points is bested by the Nvidia offering, and that too by just 3.75%. Apple's current-gen base M5 is a whopping 41% faster here. On the Windows side, the Snapdragon X2 Elite and X2 Elite Extreme score roughly 3,000 points, but AMD and Intel's top-end models take a beating.

The Ryzen AI Max+ 395 only achieves 2,429 points in the single-core test, making the 20-core RTX Spark 5.8% faster, and the 18-core variant 4.6% faster. The same goes for the Ryzen AI 9 HX 370 because its 2,432 points are within the margin of error of the Strix Halo chip. Intel's highest single-core score is achieved by the Core Ultra 9 275HX at 2,467 points, making it 3% slower than the 18-core RTX Spark and 4.2% slower than the 20-core SKU. However, Intel's actual fastest chip, the Core Ultra X9 388H, scores 2,767 points, making it about 7% faster than even the 20-core RTX Spark.

Single-core performance

SKU

Score

Difference

Apple M4 Pro (14-core)

3,315

+28.99%

Snapdragon X2 Elite (Extreme X2E-94-100)

3,051

+18.72%

Apple M3 Max (14-core)

2,841

+10.54%

20-core RTX Spark

2,570

Baseline

18-core RTX Spark

2,541

-1.13%

Intel Core Ultra 9 275HX

2,467

-4.01%

AMD AI Max+ 395

2,429

-5.49%

All in all, this is a much better showing for Nvidia's upcoming laptop Superchip than previous leaks. It's clear that driver optimization is slowly unlocking the full potential of the silicon, and by the time RTX Spark is in the hands of reviewers, we expect it to compete fiercely with every Windows machine. Nvidia is working hard to ensure a proper launch with a commitment to making DRM and anti-cheat work on day one.

Open-source stealth USB hides an encrypted partition behind an 8GB decoy drive β€” 'Phantom Drive' appears as a regular USB stick until you create a text file to unlock the hidden data

From the outside, the Phantom Drive, created by Rootkit Labs, appears like a boring old USB. It has that classic, cheap plastic-feeling look to it that would never make you second-guess its intention; when you plug it in, it shows up as just an 8GB drive. However, under the hood, the Phantomdrive is powered by a microSD card that only unlocks itself when you specifically create a new text file, after which it mounts the secret partition, which comes with AES-256 encryption. It's made for situations and places where you might be forced to reveal the contents of a storage device.

The Phantomdrive is built using the CH569 microcontroller that has a bunch of different hardware blocks β€” this project uses the USB3, SD/eMMC, and the AES block. There are no NAND chips directly onboard the custom PCB because of the ongoing component crisis. Instead, the Phantomdrive relies on a simple microSD card (that you provide; it doesn't come with one) for both its 8GB decoy partition and the hidden partition. The creator does say they'll make a version with eMMC modules once prices come down.

Of course, if someone were to open up the drive, they'd be able to physically rip the SD card out. However, it still wouldn't be a dead giveaway since many cheap USBs are powered by microSD cards, and SD card adapters are also a thing. Anyhow, the finished drive looks pretty simple from the inside; it comprises a USB port, two buck supplies, a button for firmware update, the microSD card, UART test points, and some support components. The custom firmware now comes into play.

The Phantomdrive
Rootkit Labs
The Phantomdrive
Rootkit Labs

The name of the game is interception. The firmware doesn't know it's being used to handle file transfers; it just reads raw packets of data being sent over the USB bus as is. It's coded to always look for a "password" string, so as soon as you create the unlock.txt file with "password:xyz" inside, it detects the "xyz" bit and copies it over to SRAM, while overwriting the raw data with a bunch of zeroes before it's written to the SD card. The operating system thinks it's created the new file, but the firmware intercepted it midway and sent essentially nothing to the physical storage cells.

The firmware uses the unique internal hardware ID of the microcontroller as the salt, combines it with the password you just typed, and runs the pair through PBKDF2-HMAC-SHA-256 hashes 100,000 times (you can also select 600,000 times) to create a key. Each run induces an intentional 2-3 second delay to deter brute-force attacks that would try to crack the password. The key is used to unlock and lock the hidden partition, and since it's tied to the silicon itself, putting the SD card into another Phantom Drive will not unlock it.

Unlocking the Phantomdrive's secret partition

(Image credit: Rootkit Labs)

Even if you try to access it directly through a microSD card slot, it will stay hidden, and the 8GB decoy will actually appear like a broken partition. The creator has also provided the option to recompile the firmware on your own to spoof specific vendor IDs, so that the USB appears like it's from different brands. You can make the Phantomdrive pretend to be a cheap 16GB Kingston Datatraveler at the hardware protocol level, at which point no scanning software will flag it as anything more than a cheap USB.

There are Linux-based C tools you can use in case of emergency, however, to recover your data, such as physical damage to the board. The transfer speeds are also very limited because the project is built over USB 2 β€” 20 MB/s reads and 9 MB/s writes in AES-CTR mode. The speeds fall to 10 MB/s reads and 6 MB/s writes in AES-XTS, but at least you have the freedom to choose between the two according to your needs.

You can buy the Phantomdrive from Rootkit Labs for $50, but you can also build your own, since this is an open-source project. The prebuilt device comes with two extra shells because the pins wear off and break quickly. Otherwise, the GitHub repo provides all the resources, including the PCB layout files and schematics, the BOM for every part, and the custom firmware, alongside its related tools.

The creator of Phantomdrive, Ryan Walker, explains the goal behind the project as both utilitarian and political. It's built using entirely open-source software and with inexpensive, easily accessible components. They wanted to create something that could "slip past authoritarian government representatives, corrupt police, and anyone else that doesn't respect basis encryption rights."

Modder turns Steam Controller trackpad haptics into stereo speakers with custom HID tool β€” Wired connection transmits 16-bit audio that sounds surprisingly full

Valve's second-gen Steam Controller has been a major hit with the community thanks to the company's open approach to its hardware. Modders have already used the haptic motors inside to move it across a desk and charge automatically, while others have built their own open-source pucks. Now, a new project from Pixel1011, called "Steam Haptics Player," can turn these motors into a stereo speaker capable of playing music both wired and wirelessly.

For context, the Steam Controller doesn't have a speaker; there are two linear actuators under each trackpad that vibrate to provide haptic feedback. Previous projects have leveraged these components to make the controller vibrate in a certain way. Since vibrations are the basis of sound, Valve itself built a secret easter egg into the controller that randomly makes it do a Wilhelm scream when dropped from certain heights.

Pixel 1011 discovered that the haptic motors inside can be targeted with low-level HID (Human Interface Device) feature commands using HIDAPI. As such, Steam Haptics Player takes an audio file, downsamples it through FFmpeg, splits it into chunks of a PCM stream, and sends those packets directly to the controller, bypassing high-level software like Steam Input. The controller's firmware then feeds this raw data to the motors, at which point they vibrate to produce sound.

Because of the DIY nature of this process, bandwidth is an issue, especially wirelessly, since the puck isn't designed to carry audio data over its radio signal. This means the audio has to be compressed, and there's a limit to the overall quality the motors can transmit β€” 8-bit 8kHz (ΞΌ-law) over the puck and 16-bit 8kHz PCM over a wire.

Still, the 16-bit audio is enough to produce a surprisingly loud and balanced result that can deceive you as if it's coming from a speaker. The video at the start features Pixel1011 playing the song "Want You Gone" from the end credits of Portal 2, and you can hear the quality for yourself. There's a genuine low-end that you would never expect from a jerry-rigged setup like this, even if it's sitting on top of a towel on a flat surface to give it its best chance.

The wireless audio quality is rough in comparison; it crackles and pops and even cuts off in between because of the bandwidth limitations. Pixel1011 is using 8-bit mu-law companding here, which actually offers dynamic range similar to 14-bit audio while keeping the byte footprint of an 8-bit stream. Even through this compression, the puck is struggling, but the fact that this is even possible is still very impressive, and perhaps there's room for improvement down the line.

You can try Steam Haptics Player yourself on your own second-gen Steam Controller with pretty much any audio file in any format. Just download the archive from the GitHub repo, install FFmpeg (for transcoding, if you don't have it already), and run the program via a PowerShell window in the original directory. Detailed steps are on the linked GitHub page, but we don't know how this affects the controller's battery life. Just don't go all out with your Spotify playlist on these haptic motors.

❌