Recent searches

No recent searches

Search options

Only available when logged in.
shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

255
active users

shakedown.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.3

#driver

0 posts0 participants0 posts today
Replied in thread
Kevin Karhan :verified:

@em_7dice +9001%

The only issues I had on #Linux fit on one hand and are solely the manufacturers being dicks:

#gma500#poulsbo#us15w
Daniel

In early 2024, Robert Smith used his DaynaPORT driver to create a SANA II driver for the Amiga based on Lukas F. Hartmann's MNT ZZ9000 network driver and using the BlueScsi v2 WIFI version to enable the Amiga to access the Internet.

Now, with version 1.0 of BlueSCSIUI, he has released a user interface for BlueSCSI for AmigaOS 2.0 and higher that supports configuration and diagnosis of the DynaPORT driver.

amiga-news.de/en/news/AN-2025-

www.amiga-news.deamiga-news.de - User interface for BlueSCSI on Amiga: BlueSCSIUI V1.0
#Amiga#driver#Wifi
TomAoki

Review D50697 for -devel versions of #nvidia #GPU #driver sets (latest NFB 575.64) on #FreeBSD now landed on main branch of #ports tree as commit c7cde11f842b33bb36b85b91400bec795430c421.

From now on, whichever the newer version of NFB (New Feature Branch) and Production branch is tracked on -devel branch. Beta Branch is not planned to be tracked, and just being a trigger to preparing for upcoming NFB or Production Branch.

Note that as I'm not an insider of nvidia, I cannot start investigating until nvidia releases new driver sets.

Replied in thread
*
Kevin Karhan :verified:

@BenBen @fabiscafe @okapi @chesheer I don't deny this to be a problem, far from it.

  • In an ideal world, stuff would be portable enough that the underlying init (and Userland in general) as well as Kernel didn't matter and merely be a different config file.

In reality, a substantial part of #Gnome devs (or at least contributors) are paid by the 3 major #Linux distros (#RHEL, #SLED, #Ubuntu) and whilst not being antragonistic towards #BSD|s don't get employed to enshure it runs on #FreeBSD, but that it runs better on the distro their employer is selling…

  • And given that these projects don't have infinite resources and espechally maintainers I don't blame them to redelegate a lot of work to #SystemD instead of reimplementing something themselves.

OFC it's saddening in regards to non-Linux #Unix-esque OSes, but given self-amplifying network effects both the murder of #OpenSolaris at the hands of #Oracle (with @EUCommission and #FTC as enablers!) and @iXsystems ditching #FreeBSD in #trueNAS alongside regressing #driver support for hardware outside of Linux, #macOS and #Windows, it's not a good time for these projects.

  • Which is bad because BSDs and other OSes force Linux to innovate and ' get gud '!
TomAoki

Updates for x11/nvidia-driver and friends to 570.153.02 on #FreeBSD landed on main (aka latest) branch of #ports tree.
cgit.freebsd.org/ports/commit/

And following 2 commits updates x11/nvidia-settings and x11/nvidia-xconfig
cgit.freebsd.org/ports/commit/

cgit.freebsd.org/ports/commit/
althogh no significant updates are listed after previous updates to them.
This is done to narrow down time window when any problem happenes in the future. Maybe the same would be done for future Production Branches.

cgit.freebsd.orgports - FreeBSD ports tree
#nvidia#driver
C.

This report about #Wacom graphics tablets is disturbing for a couple of reasons.

1. They are surveilling users of their #tablet - a human-interface device analogous to a mouse or trackball - recording every application you open, or when you switch between windows of different applications. They are collecting this data via a trip through Google Analytics, aka Spyware Central. There is no possible way to justify collection of this particular data; it is none of their damn business how long you have your drawing program focused before switching to your browser and back again. The author notes their privacy policy really doesn't describe this collection of data correctly, so there really can't be informed consent in the first place.

2. Why on earth is it possible in #Apple #OSX / #MacOS for a USB human interface device driver to capture this information in the first place? Apple shares a big slice of the blame here - this should just simply not be possible for the driver to collect in the first place. Having such a driver allowed to place outgoing HTTP requests is also a big "WTF are they thinking?" moment.

robertheaton.com/2020/02/05/wa

Robert HeatonWacom drawing tablets track the name of every application that you open | Robert HeatonI have a Wacom drawing tablet. I use it to draw cover illustrations for my blog posts, such as this one.
#google#GoogleAnalytics#spyware
Replied in thread
Kevin Karhan :verified:

@wolf480pl So yeah, I think that everything has compromises to some extent.

  • I'm shure #OpenBSD could even up their #security if they were willing to break #POSIX and #compatibility in general for their distro, but that'll only introduce more headaches and pain along the way.

I chose #Linux as basis for @OS1337 because it solves the #driver problem for me and I know it. I'm just complete shit with #NetBSD which may arguably be the better option targeting low-end systems, but that'll again result in more pain and frustration getting other #apps ported over when I can't just say: "Target linux-#i486 and statically compile in all your dependencies" to any 3rd party as starting point.

TrendingLive feeds
About