System76 Driver

System76 Driver 2.0.9: 2.0: None This is an inactive milestone System76 Driver 2.0.8: 2.0: None 2007-08-31: System76 Driver 2.0.8 adds support for new System76 computer models and intr. System76 Driver 2.0.5: 2.0: None 2007-06-21. System76 laptops are custom-built to run Linux flawlessly with the latest technology and super fast solid state storage.

Installation

The System76 Oryx Pro comes with two NVMe M.2 slots, as well as space for a 2.5' SSD/HDD. Booting from NVMe requires the use of EFI, while booting over SATA/AHCI does not. Typically EFI would be a safe-to-use method for this laptop overall.

Drivers

The System76 Oryx Pro has customized utilities and daemons that assist with running the Oryx Pro nicely under Linux. This includes driver (graphical, io, fan) configuration, firmware updates, and LED control.

System76 produces a distribution called Pop OS! which they install on their machines. This guide is meant to align drivers and graphical configurations with the style that Pop OS! chooses, which seems to be best for these configurations.

The collection of drivers can be found in the AUR.

system76-driver^AUR

system76-dkms^AUR

system76-io-dkms^AUR

system76-firmware-daemon^AUR

system76-power^AUR

There are also -git versions of many of these packages, if you wish to stay bleeding edge.

Graphical

This system comes complete with an integrated (intel) and discrete (NVIDIA) graphics card. The external ports (DP over Mini-DP, DP over USB-C, HDMI) are tied to the discrete nvidia card. Some users have reported getting this to work right with Bumblebee.

System76 Acpi Driver

When in doubt, remove bumblebee and install NVIDIA proprietary drivers.

Your mileage may vary if you are using a more complete DE like GNOME; this has only been tested with i3-wm.

Audio

Audio seems to work out of the box with a USB headset, however, it does not relay audio to the onboard speaker. This section needs to be feature complete with workarounds for any issues.

Suspend/Hibernate

Out of the box, Arch Linux does not resume a previously suspended or hibernated session. This section needs to be feature complete with workarounds for any issues.

Common Issues

system76-firmware: EFI mount point not found

If using the new (replacement) EFI mount point /efi, ensure you have the mount present in etc/fstab. You may find the appropriate device to mount by using a combination of lsblk and fdisk -l.

After mounting the device, system76-firmware-daemon^AUR must be built from source (root not required) and modified to include `/efi` as a valid EFI mount point.

After building and installing the modified system76-firmware from source, system76-firmware-cli maybe run to schedule a firmware update: Drivers waters.

With grub

After scheduling a firmware update, ensure that GRUB is set to use the EFI partition like so:

Restart to trigger the firmware update.

Xorg fails to start with 'No devices detected'

Trendnet support drivers. If you find (normally after an update & restart) that launching X (via startx or otherwise) does not work, you may confirm that the nvidia device is installed and working by doing the following:

Confirm the error in ~/.local/share/xorg/Xorg.0.log. The nvidia kernel module should successfully load. You may also confirm the error with dmesg or journalctl.

Check whether both integrated and discrete graphics cards are available:

If you do not see the second entry (or some similar NVIDIA card), make sure the card has been turned on by system76-power^AUR (use --help to explore options):

Check whether the discrete NVIDIA graphics card is powered on using system76-power^AUR:

To power the discrete NVIDIA graphics card on, supply 'on' as an argument (i.e. system76-power graphics power on). After doing so and querying again, you should see:

Pci Controller Driver Windows 10

Once the card is powered on, it should show up in the output of lspci, and be detectable by Xorg, given that the appropriate NVIDIA driver is installed.

System76 ME Firmware Updates Plan

Update: We've been getting a lot of great feedback from people on HackerNews and Reddit. Here are answers to a few common questions:

• The System76 Firmware Update Tool is Open Source and located at https://github.com/system76/firmware-update
  
• The github repo includes the architectural and security details
  
• Users are prompted to update firmware. A change log is included. Updates are not initiated without user action.

Proprietary code always makes life harder and Intel's Management Engine (ME) firmware is a particularly challenging chunk of secretive software. Thanks to issues identified by external security researchers, Intel initiated an audit of its ME firmware and discovered multiple critical vulnerabilities as described in SA-00086.

Separately, researchers at Positive Technologies discovered an undocumented High Assurance Platform (HAP) settings in Intel ME firmware. HAP was developed by the NSA for secure computing. Setting the 'reserve_hap' bit to 1 disables the ME.

In July of this year we began a project to automatically deliver firmware to System76 laptops similar to the way software is currently delivered through the operating system. We began testing the system in production on August 4th. Now it's very near ready for laptop customers. For desktops, System76 will work on automated firmware delivery as part of our internal desktop design and manufacturing project.

All of this has culminated in the System76 plan to address Intel's November 20th vulnerability announcement and our ability to respond to future firmware update needs.

• System76 will automatically deliver updated firmware with a disabled ME on Intel 6th, 7th, and 8th Gen laptops. The ME provides no functionality for System76 laptop customers and is safe to disable.
• The roll out will occur over time and customers will be notified by email prior to delivery
• You must run Ubuntu 16.04 LTS, Ubuntu 17.04, Ubuntu 17.10, Pop!_OS 17.10, or an Ubuntu derivative and have the System76 driver installed to receive the latest firmware and disabled ME on laptops*
• System76 will investigate producing a distro-agnostic command line firmware install tool. Follow us on your preferred social network for updates.
• System76 will not disable the ME on desktops but will provide updated ME firmware
• Desktop customers will receive instructions for updating the ME via email as they are available

Drivers

The System76 Oryx Pro has customized utilities and daemons that assist with running the Oryx Pro nicely under Linux. This includes driver (graphical, io, fan) configuration, firmware updates, and LED control.

System76 produces a distribution called Pop OS! which they install on their machines. This guide is meant to align drivers and graphical configurations with the style that Pop OS! chooses, which seems to be best for these configurations.

The collection of drivers can be found in the AUR.

system76-driver^AUR

system76-dkms^AUR

system76-io-dkms^AUR

system76-firmware-daemon^AUR

system76-power^AUR

There are also -git versions of many of these packages, if you wish to stay bleeding edge.

Graphical

This system comes complete with an integrated (intel) and discrete (NVIDIA) graphics card. The external ports (DP over Mini-DP, DP over USB-C, HDMI) are tied to the discrete nvidia card. Some users have reported getting this to work right with Bumblebee.

System76 Acpi Driver

When in doubt, remove bumblebee and install NVIDIA proprietary drivers.

Your mileage may vary if you are using a more complete DE like GNOME; this has only been tested with i3-wm.

Audio

Audio seems to work out of the box with a USB headset, however, it does not relay audio to the onboard speaker. This section needs to be feature complete with workarounds for any issues.

Suspend/Hibernate

Out of the box, Arch Linux does not resume a previously suspended or hibernated session. This section needs to be feature complete with workarounds for any issues.

Common Issues

system76-firmware: EFI mount point not found

If using the new (replacement) EFI mount point /efi, ensure you have the mount present in etc/fstab. You may find the appropriate device to mount by using a combination of lsblk and fdisk -l.

After mounting the device, system76-firmware-daemon^AUR must be built from source (root not required) and modified to include `/efi` as a valid EFI mount point.

After building and installing the modified system76-firmware from source, system76-firmware-cli maybe run to schedule a firmware update: Drivers waters.

With grub

After scheduling a firmware update, ensure that GRUB is set to use the EFI partition like so:

Restart to trigger the firmware update.

Xorg fails to start with 'No devices detected'

Trendnet support drivers. If you find (normally after an update & restart) that launching X (via startx or otherwise) does not work, you may confirm that the nvidia device is installed and working by doing the following:

Confirm the error in ~/.local/share/xorg/Xorg.0.log. The nvidia kernel module should successfully load. You may also confirm the error with dmesg or journalctl.

Check whether both integrated and discrete graphics cards are available:

If you do not see the second entry (or some similar NVIDIA card), make sure the card has been turned on by system76-power^AUR (use --help to explore options):

Check whether the discrete NVIDIA graphics card is powered on using system76-power^AUR:

To power the discrete NVIDIA graphics card on, supply 'on' as an argument (i.e. system76-power graphics power on). After doing so and querying again, you should see:

Pci Controller Driver Windows 10

Once the card is powered on, it should show up in the output of lspci, and be detectable by Xorg, given that the appropriate NVIDIA driver is installed.

System76 ME Firmware Updates Plan

Update: We've been getting a lot of great feedback from people on HackerNews and Reddit. Here are answers to a few common questions:

• The System76 Firmware Update Tool is Open Source and located at https://github.com/system76/firmware-update
  
• The github repo includes the architectural and security details
  
• Users are prompted to update firmware. A change log is included. Updates are not initiated without user action.

Proprietary code always makes life harder and Intel's Management Engine (ME) firmware is a particularly challenging chunk of secretive software. Thanks to issues identified by external security researchers, Intel initiated an audit of its ME firmware and discovered multiple critical vulnerabilities as described in SA-00086.

Separately, researchers at Positive Technologies discovered an undocumented High Assurance Platform (HAP) settings in Intel ME firmware. HAP was developed by the NSA for secure computing. Setting the 'reserve_hap' bit to 1 disables the ME.

In July of this year we began a project to automatically deliver firmware to System76 laptops similar to the way software is currently delivered through the operating system. We began testing the system in production on August 4th. Now it's very near ready for laptop customers. For desktops, System76 will work on automated firmware delivery as part of our internal desktop design and manufacturing project.

All of this has culminated in the System76 plan to address Intel's November 20th vulnerability announcement and our ability to respond to future firmware update needs.

• System76 will automatically deliver updated firmware with a disabled ME on Intel 6th, 7th, and 8th Gen laptops. The ME provides no functionality for System76 laptop customers and is safe to disable.
• The roll out will occur over time and customers will be notified by email prior to delivery
• You must run Ubuntu 16.04 LTS, Ubuntu 17.04, Ubuntu 17.10, Pop!_OS 17.10, or an Ubuntu derivative and have the System76 driver installed to receive the latest firmware and disabled ME on laptops*
• System76 will investigate producing a distro-agnostic command line firmware install tool. Follow us on your preferred social network for updates.
• System76 will not disable the ME on desktops but will provide updated ME firmware
• Desktop customers will receive instructions for updating the ME via email as they are available

There is a significant amount of testing and validation necessary before delivering the updated firmware and disabled ME. Disabling the ME will reduce future vulnerabilities and using our new firmware delivery infrastructure means future updates can roll out extremely fast and with a higher percentage of adoption (over listing affected models with links to firmware that most people don't install).

It is important to note, while we can currently disable the ME on laptops, Intel may change how the device functions in the future. We implore Intel to retain the ability for device manufactures and consumers to disable the ME.

* To install the system76-driver (for System76 hardware) on Ubuntu based distributions run the following commands

sudo apt-add-repository -y ppa:system76-dev/stable
sudo apt update
sudo apt install -y system76-driver

Our internal plan in detail with a list of affected products

System 76 Driver Updates

SA-00086 Vulnerability ME Update Project Plan

Laptops

System76 Drivers

Disable the ME on all affected laptops

• Test combined ME and firmware delivery in production
• Add UEFI check to driver before starting the firmware daemon
• Fix the remaining automated firmware delivery system bug 'Firmware, on occasion, doesn't install on ‘U' class products'
• Setup lab with all affected laptops
• Intel 6th Gen
• Bonobo (bonw11)
• Gazelle (gaze10)
• Gazelle (gaze11)
• Kudu (kudu2)
• Kudu (kudu3)
• Lemur (lemu6)
• Oryx (orxp1)
• Oryx (oryp2)
• Serval (serw9)
• Intel 7th Gen
• Bonobo (bonw12)
• Galago (galp2)
• Gazelle (gaze12)
• Kudu (kudu4)
• Lemur (lemu7)
• Oryx (oryp3)
• Serval (serw10)
• Intel 8th Gen
• Bonobo (bonw13)
• Galago (galp3)
• Lemur (lemu8)
• Serval (serw11)
• Procure latest ME's for affected models
• Set HAP bit to 1 on all ME's without Intel BootGuard
• Create Intel BootGuard firmware with HAP bit set to 1
• lemu6
• lemu7
• lemu8
• galp2
• galp3
• Add firmware with the new ME to the automated firmware delivery system
• Test delivery of the new ME and firmware to all models
• Confirm that ME is disabled on each model
• Draft email correspondence to customers
• Compile email list of affected lemu8 customers.
• Send email to lemu8 customers
• Send updated firmware and ME to lemu8 customers using automated delivery
• Work with the support team to evaluate any failures
• Based on those results, determine timing and delivery of the remaining firmware and update the project plan

System76 Drivers Windows

Ust pro ii port devices driver download. Desktops

System 76 Drivers Windows 10

Update all affected models with new ME firmware

• Create the 'firmware' github repo structure for storing desktop firmware
• Procure updated ME for all models
• Intel 6th Generation
• Meerkat (meer2)
• Ratel (ratp5)
• Sable (sabl6)
• Wild Dog (wilp12)
• Intel 7th Generation
• Leopard (leow8)
• Meerkat (meer3)
• Wild Dog (wilp13)
• If the ME also requires a BIOS update, create customized BIOS for each model.
• Add firmware to the 'firmware' github project https://github.com/system76/firmware-desktop
• Design desktop Guide page changes to include notification and firmware download
• Modify guides for affected desktops
• Draft email correspondence to customers
• Compile email list for all affected customers
• Send email notification