README.md 3.29 KB
Newer Older
1
2
fwupd
=====
3
[![Build Status](https://travis-ci.org/hughsie/fwupd.png?branch=master)](https://travis-ci.org/hughsie/fwupd)
4
[![Coverity Scan Build Status](https://scan.coverity.com/projects/10744/badge.svg)](https://scan.coverity.com/projects/10744)
5

6
This project aims to make updating firmware on Linux automatic, safe and reliable.
7

Zander's avatar
Zander committed
8
Additional information is available at the website: https://fwupd.org
9

10
11
## Compiling

12
The most up to date compilation instructions are available in the [Wiki](https://github.com/hughsie/fwupd/wiki/Compilation)
13

14
15
16
LVFS
----
This project is configured by default to download firmware from the [Linux Vendor
17
Firmware Service (LVFS)](https://fwupd.org/).
18

19
20
This service is available to all OEMs and firmware creators who would like to make
their firmware available to Linux users.
21

22
You can find more information about the technical details of creating a firmware
Zander's avatar
Zander committed
23
capsule in the hardware vendors section of the [fwupd website](https://fwupd.org).
24

25
26
27
28
Basic usage flow (command line)
------------------------------

If you have a device with firmware supported by fwupd, this is how you will check
29
for updates and apply them using fwupd's command line tools.
30

31
`# fwupdmgr get-devices`
32
33
34

This will display all devices detected by fwupd.

35
`# fwupdmgr refresh`
36
37
38

This will download the latest metadata from LVFS.

39
`# fwupdmgr get-updates`
40
41
42

If updates are available for any devices on the system, they'll be displayed.

43
`# fwupdmgr update`
44
45
46

This will download and apply all updates for your system.

47
48
* Updates that can be applied live will be done immediately.
* Updates that run at bootup will be staged for the next reboot.
49

50
You can find more information about the update workflow in the end
Zander's avatar
Zander committed
51
users section of the [fwupd website](https://fwupd.org).
52

53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
Reporting status
---------------

fwupd will encourage users to report both successful and failed updates back
to LVFS.  This is an optional feature, but encouraged as it provides valuable
feedback to LVFS administrators and OEM developers regarding firmware update
process efficacy.

The privacy policy regarding this data can be viewed on the [fwupd website](https://fwupd.org/privacy).

To report the status of an update run:

`# fwupdmgr report-history`

To clear the local history of updates:

`# fwupdmgr clear-history`

 Only updates that were distributed from the LVFS will be reported to the LVFS.

73
74
75
Other frontends
-------------------

76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
 1. [GNOME Software](https://wiki.gnome.org/Apps/Software) is the graphical
 frontend available. When compiled with firmware support, it will check for
 updates periodically and automatically download firmware in the background.
 After the firmware has been downloaded a popup will be displayed in Gnome
 Software to perform the update.

2. [KDE Discover](https://userbase.kde.org/Discover) is the software centre,
 generally bundled with KDE Plasma. With the release of
 [KDE Plasma 5.14](https://www.kde.org/announcements/plasma-5.14.0.php),
 a new fwupd backend has been implemented in KDE Discover for firmware updates.
 These firmware updates are shown with other system updates.

3. [Wyse Cloud Client Manager (CCM)](http://www.dell.com/us/business/p/wyse-cloud-client-manager/pd)
 A software suite available on Dell IoT gateways with built-in fwupd support.
 The remote administration interface can be used to download and deploy firmware
 updates.