you are viewing a single comment's thread
view the rest of the comments
[–] 132 points 5 days ago* (last edited 5 days ago) (16 children)

The kernel has a ton of optional modules that they'd be stupid to include them all. They certainly don't need support for an obscure Quebec companies GPUs that stopped producing in the 90s.

Its pretty standard operating to cut out any cruft you can, saves on storage, boot times, etc. This one was probably saving milliseconds and kilobytes, so presumably not much thought was given to disabling it, nor needed to reenable it.

  • source
  • parent
  • hideshow 16 child comments
  • [–] 97 points 5 days ago (6 children)

    Again?! An unwarranted attack by the anglophones against the Québécois GPU artisans!

    L’enterrement de cyber-crapaud!!

  • source
  • parent
  • hideshow 6 child comments
  • [–] 30 points 5 days ago (3 children)
  • [–] 23 points 5 days ago (3 children)

    The existence of it also adds another potential attack vector for hackers. It's unlikely that this would be a real problem, but any additional software is just another place that could be exploited.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 11 points 5 days ago (2 children)

    Thats a really good point, especially with the more obscure modules.

    It must be interesting for steam to develop a hackable device in a market that usually locks their hardware down so aggressively.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 5 days ago* (1 child)

    I mean just because steam doesn't mind you tinkering with their own hardware doesn't mean they should not try to secure the base system OS against outside intrusion (like a RAT entering in via an AUR installation using modules as an entry point)

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 5 days ago

    Yeah, sorry I meant more in the way that a user in a VM is a really different threat surface to a full root user.

    For sure both should apply security patches, and avoid malware, I'm just wondering even within that model what the differences are.

  • source
  • parent
  • [–] 5 points 5 days ago* (last edited 5 days ago) (1 child)

    The kernel has a ton of optional modules that they’d be stupid to include them all.

    True but part of Valve's marketing for Frame is the expansion slot, so at least peripherals compatible with ARM hardware were probably meant to be enabled and this was an oversight.

  • source
  • parent
  • hideshow 1 child comment
  • [–] -3 points 5 days ago (2 children)

    How unloaded kernel module can slow boot time?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 23 points 5 days ago

    Still needs to be read from disk/flash, for the kernel to know it exists. And more relevantly every module has a number of dependencies that will all contribute to size/boot times in their own way.

    Maybe even milliseconds is giving it too much, but bloat is really important especially near the release of new hardware.

    I imagine the last thing anyone was worried about in crunch time was if they enabled enough random hardware in their config file.

  • source
  • parent