Why don't you need to update drivers? (Or do you?)
Why one does not need to update Linux drivers? Is it due to the open source community building good drivers before they are submitted to the kernel, or do driver updates occur when I do normal system updates or something?
linux kernel drivers upgrade
edited 57 mins ago
Rui F Ribeiro
41.5k1483140
asked May 22 '12 at 21:21
camilla.greercamilla.greer
316513
add a comment |
Why one does not need to update Linux drivers? Is it due to the open source community building good drivers before they are submitted to the kernel, or do driver updates occur when I do normal system updates or something?
linux kernel drivers upgrade
edited 57 mins ago
Rui F Ribeiro
41.5k1483140
asked May 22 '12 at 21:21
camilla.greercamilla.greer
316513
8
The whole idea that you need to regularly update drives is a bit annoying in the first place. If you don't count updates related to security issues/bugs, then why should you need to update your drivers? If your hardware doesn't change, why would you need to change the software that facilitates your interaction with it.
– Zoredache
May 22 '12 at 23:56
Follow you constructor's updates, if there's a security fix, update. If you find a fault and it's fixed, update. It's a PITA but it's the best way to do it. Organisation becomes critical at this point. Or you can just ignore this problem and never update your drivers.
– Aki
May 23 '12 at 6:40
@zoredache Well then why do Windows drivers need updating all the time? Your comment about the static nature of hardware arms to apply there as well.
– camilla.greer
May 23 '12 at 22:03
@rob.g.greer, I would argue that it often doesn't need to be updated. The only driver I do update is for my video card, and that is these days the video card 'driver' is that because these days it released with a ton of other software that is less stable and is frequently updated to be optimized with newly released games and so on.
– Zoredache
May 23 '12 at 22:09
add a comment |
Why one does not need to update Linux drivers? Is it due to the open source community building good drivers before they are submitted to the kernel, or do driver updates occur when I do normal system updates or something?
linux kernel drivers upgrade
edited 57 mins ago
Rui F Ribeiro
41.5k1483140
asked May 22 '12 at 21:21
camilla.greercamilla.greer
316513
Why one does not need to update Linux drivers? Is it due to the open source community building good drivers before they are submitted to the kernel, or do driver updates occur when I do normal system updates or something?
linux kernel drivers upgrade
linux kernel drivers upgrade
edited 57 mins ago
Rui F Ribeiro
41.5k1483140
asked May 22 '12 at 21:21
camilla.greercamilla.greer
316513
edited 57 mins ago
Rui F Ribeiro
41.5k1483140
asked May 22 '12 at 21:21
camilla.greercamilla.greer
316513
edited 57 mins ago
Rui F Ribeiro
41.5k1483140
edited 57 mins ago
Rui F Ribeiro
41.5k1483140
edited 57 mins ago
Rui F Ribeiro
41.5k1483140
41.5k1483140
asked May 22 '12 at 21:21
camilla.greercamilla.greer
316513
asked May 22 '12 at 21:21
camilla.greercamilla.greer
316513
asked May 22 '12 at 21:21
camilla.greercamilla.greer
316513
316513
8
The whole idea that you need to regularly update drives is a bit annoying in the first place. If you don't count updates related to security issues/bugs, then why should you need to update your drivers? If your hardware doesn't change, why would you need to change the software that facilitates your interaction with it.
– Zoredache
May 22 '12 at 23:56
Follow you constructor's updates, if there's a security fix, update. If you find a fault and it's fixed, update. It's a PITA but it's the best way to do it. Organisation becomes critical at this point. Or you can just ignore this problem and never update your drivers.
– Aki
May 23 '12 at 6:40
@zoredache Well then why do Windows drivers need updating all the time? Your comment about the static nature of hardware arms to apply there as well.
– camilla.greer
May 23 '12 at 22:03
@rob.g.greer, I would argue that it often doesn't need to be updated. The only driver I do update is for my video card, and that is these days the video card 'driver' is that because these days it released with a ton of other software that is less stable and is frequently updated to be optimized with newly released games and so on.
– Zoredache
May 23 '12 at 22:09
add a comment |
8
The whole idea that you need to regularly update drives is a bit annoying in the first place. If you don't count updates related to security issues/bugs, then why should you need to update your drivers? If your hardware doesn't change, why would you need to change the software that facilitates your interaction with it.
– Zoredache
May 22 '12 at 23:56
Follow you constructor's updates, if there's a security fix, update. If you find a fault and it's fixed, update. It's a PITA but it's the best way to do it. Organisation becomes critical at this point. Or you can just ignore this problem and never update your drivers.
– Aki
May 23 '12 at 6:40
@zoredache Well then why do Windows drivers need updating all the time? Your comment about the static nature of hardware arms to apply there as well.
– camilla.greer
May 23 '12 at 22:03
@rob.g.greer, I would argue that it often doesn't need to be updated. The only driver I do update is for my video card, and that is these days the video card 'driver' is that because these days it released with a ton of other software that is less stable and is frequently updated to be optimized with newly released games and so on.
– Zoredache
May 23 '12 at 22:09
8
8
The whole idea that you need to regularly update drives is a bit annoying in the first place. If you don't count updates related to security issues/bugs, then why should you need to update your drivers? If your hardware doesn't change, why would you need to change the software that facilitates your interaction with it.
– Zoredache
May 22 '12 at 23:56
The whole idea that you need to regularly update drives is a bit annoying in the first place. If you don't count updates related to security issues/bugs, then why should you need to update your drivers? If your hardware doesn't change, why would you need to change the software that facilitates your interaction with it.
– Zoredache
May 22 '12 at 23:56
Follow you constructor's updates, if there's a security fix, update. If you find a fault and it's fixed, update. It's a PITA but it's the best way to do it. Organisation becomes critical at this point. Or you can just ignore this problem and never update your drivers.
– Aki
May 23 '12 at 6:40
Follow you constructor's updates, if there's a security fix, update. If you find a fault and it's fixed, update. It's a PITA but it's the best way to do it. Organisation becomes critical at this point. Or you can just ignore this problem and never update your drivers.
– Aki
May 23 '12 at 6:40
@zoredache Well then why do Windows drivers need updating all the time? Your comment about the static nature of hardware arms to apply there as well.
– camilla.greer
May 23 '12 at 22:03
@zoredache Well then why do Windows drivers need updating all the time? Your comment about the static nature of hardware arms to apply there as well.
– camilla.greer
May 23 '12 at 22:03
@rob.g.greer, I would argue that it often doesn't need to be updated. The only driver I do update is for my video card, and that is these days the video card 'driver' is that because these days it released with a ton of other software that is less stable and is frequently updated to be optimized with newly released games and so on.
– Zoredache
May 23 '12 at 22:09
@rob.g.greer, I would argue that it often doesn't need to be updated. The only driver I do update is for my video card, and that is these days the video card 'driver' is that because these days it released with a ton of other software that is less stable and is frequently updated to be optimized with newly released games and so on.
– Zoredache
May 23 '12 at 22:09
add a comment |
3 Answers
3
active
oldest
votes
Driver updates occur when the kernel is updated, with each version of a new kernel new features (and bugs :) in drivers are introduced and bugs are fixed. You can read the kernel's changelog if you want to see what changed, e.g. for kernel 3.3.7, also posts in the Linux Kernel Mailing List, e.g. Linux 3.4 released. KernelNewbies also provides information on those new features in an easier way to read than the changelog (e.g. kernel 3.4).
If you use "out-of-tree" drivers (e.g. binary blobs, like nVidia/ATI), then those drivers will obviously not be updated with the kernel; it's up to their developers to release new versions that work with newer kernels, and up to you (or to your distro's repositories) to upgrade them.
answered May 22 '12 at 21:35
RenanRenan
14.6k65578
For other systems, it occurs when you update the whole system (re-install).
– Aki
May 23 '12 at 6:39
1
Just to note that KernelNewbies's release pages are very nice to know what changed, see: 3.4, 3.3, 3.2, etc...
– mmoya
May 23 '12 at 7:04
KernelNewbies is pretty neat.
– Renan
May 23 '12 at 13:18
Stupid question: Does linux (kernel) have all the drivers within? I mean, say I use x driver for my sound chip, do people with different sound chips still get the driver in their kernel despite they don't use x sound chip?
– şaloma
Jun 24 '14 at 4:53
add a comment |
There are two types of drivers in distributions: compiled in kernel (and/or distributed in the same package) and distributed as kernel modules in separate packages. Most distributions when you perform system update updates all of the installed packages including packaged kernel modules and kernel itself, so whole update process is invisible to user.
answered May 22 '12 at 21:35
pbmpbm
17.2k52847
add a comment |
The "normal" drivers are being taken care of by the normal operating-system upgrades. During minor release updates the version of the drivers may change a bit.
For firmware of your hardware-eqipment (BIOS, RAID-Controller, harddisks, backplane, fibre-channel-cards, network-cards) you have to take care yourselv.
This mostly applies to servers. On PCs - upgrade if you need a feature or a bug-fix (normally BIOS).
Somewhere in between are Intel-CPU-microcode-updates. They are normally applied by the BIOS, but can also be applied by the operating system (microcode_ctl is one of the services doing such a thing). The microcode in the OS is normally being updated during minor release changes.
But: You can also go directly to Intel, download the tar-file and place it onto linux - then you will have the newest available version (again - if you need it).
answered May 23 '12 at 19:24
NilsNils
12.7k73670
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f39182%2fwhy-dont-you-need-to-update-drivers-or-do-you%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Driver updates occur when the kernel is updated, with each version of a new kernel new features (and bugs :) in drivers are introduced and bugs are fixed. You can read the kernel's changelog if you want to see what changed, e.g. for kernel 3.3.7, also posts in the Linux Kernel Mailing List, e.g. Linux 3.4 released. KernelNewbies also provides information on those new features in an easier way to read than the changelog (e.g. kernel 3.4).
If you use "out-of-tree" drivers (e.g. binary blobs, like nVidia/ATI), then those drivers will obviously not be updated with the kernel; it's up to their developers to release new versions that work with newer kernels, and up to you (or to your distro's repositories) to upgrade them.
answered May 22 '12 at 21:35
RenanRenan
14.6k65578
For other systems, it occurs when you update the whole system (re-install).
– Aki
May 23 '12 at 6:39
1
Just to note that KernelNewbies's release pages are very nice to know what changed, see: 3.4, 3.3, 3.2, etc...
– mmoya
May 23 '12 at 7:04
KernelNewbies is pretty neat.
– Renan
May 23 '12 at 13:18
Stupid question: Does linux (kernel) have all the drivers within? I mean, say I use x driver for my sound chip, do people with different sound chips still get the driver in their kernel despite they don't use x sound chip?
– şaloma
Jun 24 '14 at 4:53
add a comment |
Driver updates occur when the kernel is updated, with each version of a new kernel new features (and bugs :) in drivers are introduced and bugs are fixed. You can read the kernel's changelog if you want to see what changed, e.g. for kernel 3.3.7, also posts in the Linux Kernel Mailing List, e.g. Linux 3.4 released. KernelNewbies also provides information on those new features in an easier way to read than the changelog (e.g. kernel 3.4).
If you use "out-of-tree" drivers (e.g. binary blobs, like nVidia/ATI), then those drivers will obviously not be updated with the kernel; it's up to their developers to release new versions that work with newer kernels, and up to you (or to your distro's repositories) to upgrade them.
answered May 22 '12 at 21:35
RenanRenan
14.6k65578
For other systems, it occurs when you update the whole system (re-install).
– Aki
May 23 '12 at 6:39
1
Just to note that KernelNewbies's release pages are very nice to know what changed, see: 3.4, 3.3, 3.2, etc...
– mmoya
May 23 '12 at 7:04
KernelNewbies is pretty neat.
– Renan
May 23 '12 at 13:18
Stupid question: Does linux (kernel) have all the drivers within? I mean, say I use x driver for my sound chip, do people with different sound chips still get the driver in their kernel despite they don't use x sound chip?
– şaloma
Jun 24 '14 at 4:53
add a comment |
Driver updates occur when the kernel is updated, with each version of a new kernel new features (and bugs :) in drivers are introduced and bugs are fixed. You can read the kernel's changelog if you want to see what changed, e.g. for kernel 3.3.7, also posts in the Linux Kernel Mailing List, e.g. Linux 3.4 released. KernelNewbies also provides information on those new features in an easier way to read than the changelog (e.g. kernel 3.4).
If you use "out-of-tree" drivers (e.g. binary blobs, like nVidia/ATI), then those drivers will obviously not be updated with the kernel; it's up to their developers to release new versions that work with newer kernels, and up to you (or to your distro's repositories) to upgrade them.
answered May 22 '12 at 21:35
RenanRenan
14.6k65578
Driver updates occur when the kernel is updated, with each version of a new kernel new features (and bugs :) in drivers are introduced and bugs are fixed. You can read the kernel's changelog if you want to see what changed, e.g. for kernel 3.3.7, also posts in the Linux Kernel Mailing List, e.g. Linux 3.4 released. KernelNewbies also provides information on those new features in an easier way to read than the changelog (e.g. kernel 3.4).
If you use "out-of-tree" drivers (e.g. binary blobs, like nVidia/ATI), then those drivers will obviously not be updated with the kernel; it's up to their developers to release new versions that work with newer kernels, and up to you (or to your distro's repositories) to upgrade them.
answered May 22 '12 at 21:35
RenanRenan
14.6k65578
edited May 23 '12 at 11:16
answered May 22 '12 at 21:35
RenanRenan
14.6k65578
answered May 22 '12 at 21:35
RenanRenan
14.6k65578
answered May 22 '12 at 21:35
RenanRenan
14.6k65578
14.6k65578
For other systems, it occurs when you update the whole system (re-install).
– Aki
May 23 '12 at 6:39
1
Just to note that KernelNewbies's release pages are very nice to know what changed, see: 3.4, 3.3, 3.2, etc...
– mmoya
May 23 '12 at 7:04
KernelNewbies is pretty neat.
– Renan
May 23 '12 at 13:18
Stupid question: Does linux (kernel) have all the drivers within? I mean, say I use x driver for my sound chip, do people with different sound chips still get the driver in their kernel despite they don't use x sound chip?
– şaloma
Jun 24 '14 at 4:53
add a comment |
For other systems, it occurs when you update the whole system (re-install).
– Aki
May 23 '12 at 6:39
1
Just to note that KernelNewbies's release pages are very nice to know what changed, see: 3.4, 3.3, 3.2, etc...
– mmoya
May 23 '12 at 7:04
KernelNewbies is pretty neat.
– Renan
May 23 '12 at 13:18
Stupid question: Does linux (kernel) have all the drivers within? I mean, say I use x driver for my sound chip, do people with different sound chips still get the driver in their kernel despite they don't use x sound chip?
– şaloma
Jun 24 '14 at 4:53
For other systems, it occurs when you update the whole system (re-install).
– Aki
May 23 '12 at 6:39
For other systems, it occurs when you update the whole system (re-install).
– Aki
May 23 '12 at 6:39
1
1
Just to note that KernelNewbies's release pages are very nice to know what changed, see: 3.4, 3.3, 3.2, etc...
– mmoya
May 23 '12 at 7:04
Just to note that KernelNewbies's release pages are very nice to know what changed, see: 3.4, 3.3, 3.2, etc...
– mmoya
May 23 '12 at 7:04
KernelNewbies is pretty neat.
– Renan
May 23 '12 at 13:18
KernelNewbies is pretty neat.
– Renan
May 23 '12 at 13:18
Stupid question: Does linux (kernel) have all the drivers within? I mean, say I use x driver for my sound chip, do people with different sound chips still get the driver in their kernel despite they don't use x sound chip?
– şaloma
Jun 24 '14 at 4:53
Stupid question: Does linux (kernel) have all the drivers within? I mean, say I use x driver for my sound chip, do people with different sound chips still get the driver in their kernel despite they don't use x sound chip?
– şaloma
Jun 24 '14 at 4:53
add a comment |
There are two types of drivers in distributions: compiled in kernel (and/or distributed in the same package) and distributed as kernel modules in separate packages. Most distributions when you perform system update updates all of the installed packages including packaged kernel modules and kernel itself, so whole update process is invisible to user.
answered May 22 '12 at 21:35
pbmpbm
17.2k52847
add a comment |
There are two types of drivers in distributions: compiled in kernel (and/or distributed in the same package) and distributed as kernel modules in separate packages. Most distributions when you perform system update updates all of the installed packages including packaged kernel modules and kernel itself, so whole update process is invisible to user.
answered May 22 '12 at 21:35
pbmpbm
17.2k52847
add a comment |
There are two types of drivers in distributions: compiled in kernel (and/or distributed in the same package) and distributed as kernel modules in separate packages. Most distributions when you perform system update updates all of the installed packages including packaged kernel modules and kernel itself, so whole update process is invisible to user.
answered May 22 '12 at 21:35
pbmpbm
17.2k52847
There are two types of drivers in distributions: compiled in kernel (and/or distributed in the same package) and distributed as kernel modules in separate packages. Most distributions when you perform system update updates all of the installed packages including packaged kernel modules and kernel itself, so whole update process is invisible to user.
answered May 22 '12 at 21:35
pbmpbm
17.2k52847
answered May 22 '12 at 21:35
pbmpbm
17.2k52847
answered May 22 '12 at 21:35
pbmpbm
17.2k52847
answered May 22 '12 at 21:35
pbmpbm
17.2k52847
17.2k52847
add a comment |
add a comment |
The "normal" drivers are being taken care of by the normal operating-system upgrades. During minor release updates the version of the drivers may change a bit.
For firmware of your hardware-eqipment (BIOS, RAID-Controller, harddisks, backplane, fibre-channel-cards, network-cards) you have to take care yourselv.
This mostly applies to servers. On PCs - upgrade if you need a feature or a bug-fix (normally BIOS).
Somewhere in between are Intel-CPU-microcode-updates. They are normally applied by the BIOS, but can also be applied by the operating system (microcode_ctl is one of the services doing such a thing). The microcode in the OS is normally being updated during minor release changes.
But: You can also go directly to Intel, download the tar-file and place it onto linux - then you will have the newest available version (again - if you need it).
answered May 23 '12 at 19:24
NilsNils
12.7k73670
add a comment |
The "normal" drivers are being taken care of by the normal operating-system upgrades. During minor release updates the version of the drivers may change a bit.
For firmware of your hardware-eqipment (BIOS, RAID-Controller, harddisks, backplane, fibre-channel-cards, network-cards) you have to take care yourselv.
This mostly applies to servers. On PCs - upgrade if you need a feature or a bug-fix (normally BIOS).
Somewhere in between are Intel-CPU-microcode-updates. They are normally applied by the BIOS, but can also be applied by the operating system (microcode_ctl is one of the services doing such a thing). The microcode in the OS is normally being updated during minor release changes.
But: You can also go directly to Intel, download the tar-file and place it onto linux - then you will have the newest available version (again - if you need it).
answered May 23 '12 at 19:24
NilsNils
12.7k73670
add a comment |
The "normal" drivers are being taken care of by the normal operating-system upgrades. During minor release updates the version of the drivers may change a bit.
For firmware of your hardware-eqipment (BIOS, RAID-Controller, harddisks, backplane, fibre-channel-cards, network-cards) you have to take care yourselv.
This mostly applies to servers. On PCs - upgrade if you need a feature or a bug-fix (normally BIOS).
Somewhere in between are Intel-CPU-microcode-updates. They are normally applied by the BIOS, but can also be applied by the operating system (microcode_ctl is one of the services doing such a thing). The microcode in the OS is normally being updated during minor release changes.
But: You can also go directly to Intel, download the tar-file and place it onto linux - then you will have the newest available version (again - if you need it).
answered May 23 '12 at 19:24
NilsNils
12.7k73670
The "normal" drivers are being taken care of by the normal operating-system upgrades. During minor release updates the version of the drivers may change a bit.
For firmware of your hardware-eqipment (BIOS, RAID-Controller, harddisks, backplane, fibre-channel-cards, network-cards) you have to take care yourselv.
This mostly applies to servers. On PCs - upgrade if you need a feature or a bug-fix (normally BIOS).
Somewhere in between are Intel-CPU-microcode-updates. They are normally applied by the BIOS, but can also be applied by the operating system (microcode_ctl is one of the services doing such a thing). The microcode in the OS is normally being updated during minor release changes.
But: You can also go directly to Intel, download the tar-file and place it onto linux - then you will have the newest available version (again - if you need it).
answered May 23 '12 at 19:24
NilsNils
12.7k73670
answered May 23 '12 at 19:24
NilsNils
12.7k73670
answered May 23 '12 at 19:24
NilsNils
12.7k73670
answered May 23 '12 at 19:24
NilsNils
12.7k73670
12.7k73670
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f39182%2fwhy-dont-you-need-to-update-drivers-or-do-you%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
8
The whole idea that you need to regularly update drives is a bit annoying in the first place. If you don't count updates related to security issues/bugs, then why should you need to update your drivers? If your hardware doesn't change, why would you need to change the software that facilitates your interaction with it.
– Zoredache
May 22 '12 at 23:56
Follow you constructor's updates, if there's a security fix, update. If you find a fault and it's fixed, update. It's a PITA but it's the best way to do it. Organisation becomes critical at this point. Or you can just ignore this problem and never update your drivers.
– Aki
May 23 '12 at 6:40
@zoredache Well then why do Windows drivers need updating all the time? Your comment about the static nature of hardware arms to apply there as well.
– camilla.greer
May 23 '12 at 22:03
@rob.g.greer, I would argue that it often doesn't need to be updated. The only driver I do update is for my video card, and that is these days the video card 'driver' is that because these days it released with a ton of other software that is less stable and is frequently updated to be optimized with newly released games and so on.
– Zoredache
May 23 '12 at 22:09