snoodwattle

Try humming it in the Google or Sound Hound app. They work pretty well.

This resembles the old revision of the DreamDumper64

https://dreamcraftindustries.com/collections/n64

The new revision has an integrated RP2040

It’s CentOS 7.x

Nice work!

Out of curiosity, what repairs did the CRT need?

Obligatory safety disclaimer for people who want to repair old TVs: Messing with some of those electronics can be very dangerous.

Click the Fabien link, not the OS News one

I don’t have any content blockers. For fun I tried Desktop view, RSS reader, and an archive.is crawl but it looks the same: http://archive.today/8EaKt

Maybe it’s a region thing

Edit: Ohhh click the Fabien link, not the OS News one

Where’s the rest of the article? I only see these the paragraphs:

One of the remarkable characteristics of the Super Nintendo was the ability for game cartridges (cart) to pack more than instructions and assets into ROM chips. If we open and look at the PCBs, we can find inside things like the CIC copy protection chip, SRAM, and even “enhancement processors”.

↫ Fabien Sanglard

When I was a child and teenager in the ’90s, the capabilities of the SNES cartridge were a bit of a legend. We’d talk about what certain games would use which additional processors and chips in the cartridge, right or wrong, often boasting about the games we owned, and talking down the games we didn’t. Much of it was probably nonsense, but there’s some good memories there.

We’re decades deep into the internet age now, and all the mysteries of the SNES cartridge can just be looked up on Wikipedia and endless numbers of other websites. The mystery’s all gone, but at least now we can accurately marvel at just how versatile the SNES really was.

deleted by creator

Open source or proprietary drivers?

What GPU?

Some versions of Clip Studio look supported: https://appdb.winehq.org/objectManager.php?sClass=application&iId=15102

But Toon Boom Storyboard isn’t listed (unless it is part of Studio): https://www.winehq.org/search?q=Toon+boom

Running in a Virtual Box Windows VM may be the quickest path to success.

You could also check the symlinks for the device in the sysfs. The word after “drivers” below for a given network interface (eth0 below) is usually the name of the driver (cpsw below):

$ ls -l /sys/class/net/eth0/device/driver   
lrwxrwxrwx 1 root root 0 Aug  9 10:41 /sys/class/net/eth0/device/driver -> ../../../../bus/platform/drivers/cpsw

Or run lsmod and see if anything jumps out.

Either way, once you find the driver name, run modinfo to get version and other information about specific drivers.

Edit: formatting

2