search for: firmwares

Greetings everyone. I am experiencing the kworker issue where a kworker is using 100% of a given core. This behavior was only observed after having installed a new water cooler, to replace a cooler that had died. (Sealed closed loop device from Corsair) The processor is staying around 40 degrees celsius as reported by the MB UEFI interface. (ksysguard shows between 29 degrees and 30 degrees,

tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost head: 3d22d7c1190db3209b644b8a13a75a9802b4587f commit: b3a8771f409b74c42deee28aee3092fc5d2c8dab [22/23] fw_cfg: write vmcoreinfo details reproduce: # apt-get install sparse git checkout b3a8771f409b74c42deee28aee3092fc5d2c8dab make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__

Hi folks As mentioned in the subject, kernel-3.18.12-11 is missing firmware files required to run Broadcom/Qlogic network cards, driven by bnx2x driver. While in the source-rpm, there is a bnx2/bnx2x firmware tgz being applied during the rpm build, along with a patch adding these firmware files to firmware/Makefile, neither the tgz nor the patch contain the required firmware files. In 3.18,

Hi Alexandre, On 18 January 2016 at 06:07, Alexandre Courbot <acourbot at nvidia.com> wrote: > Add two functions nvkm_firmware_get() and nvkm_firmware_put() to load a > firmware file and free its resources, respectively. Since firmware files > are becoming a necessity for new GPUs, and their location has been > standardized to nvidia/chip/, this will prevent duplicate and >

Greetings again everyone. Can someone please respond to this? I am not sure what is causing this issue, however, others seem to have experienced it in the past. Could this be caused by the processor being damaged? Nothing has changed on the system, except for the heat warning shutoff when the water cooler died, and the system was not restarted until the new one was installed. Any input

...selection works - the 'efi' firmware is available The only behaviour change is that the default firmware may be a non-debug version, so we get no debug messages even when running in verbose mode. This most probably will need an addition in libvirt to select this feature among the available firmwares. Pino Toscano (4): launch: libvirt: parse firmware autoselection lib: uefi: reset out parameters earlier lib: allow to use libvirt firmware autoselection lib: uefi: use the efi libvirt firmware if available lib/appliance-uefi.c | 32 ++++++++++++++++++++++++++------ lib/guestfs-interna...

Hi all. As the subject has come up. Powerware ups may contain several cpu's and different firmware versions. Five of them is always ordered in a specific way. 1 control panel 2 inverter 3 rectifier 4 net interface card 5 display control So if a ups have a inverter cpu but not a control panel it sets the firmware revision to 00.00 to the control panel cpu, and get the version for the

This patchset centralizes the firmware-loading procedure to one set of functions instead of having each engine load its firmware as it pleases. This helps ensure that all firmware comes from the same place, namely nvidia/<chip>/. This changes where the firmware is fetched from for falcon/xtensa/bios, but these locations never seemed to have been official anyway. Also for most (all?) chips

I just downloaded the zip file from grandstreams website to upgrade my gxp2000 firmware from 1.0.0.3 to the latest but seems there are some files missing on the zip file... Anybody been able to upgrade their firmware? My website shows this files as missing: 201.133.125.152 - - [11/May/2005:16:47:16 -0500] "GET /firmware/ring1.bin HTTP/1.0" 200 12737 "-" "Grandstream

On Mon, Jul 6, 2015 at 8:43 PM, Johnny Hughes <johnny at centos.org> wrote: > On 07/05/2015 11:35 AM, T.Weyergraf wrote: >> Hi folks >> >> As mentioned in the subject, kernel-3.18.12-11 is missing firmware files >> required to run Broadcom/Qlogic network cards, driven by bnx2x driver. >> While in the source-rpm, there is a bnx2/bnx2x firmware tgz being

On Fri, Apr 3, 2020 at 1:21 PM Zeno Davatz <zdavatz at gmail.com> wrote: > > On Fri, Apr 3, 2020 at 6:59 PM Ilia Mirkin <imirkin at alum.mit.edu> wrote: > > > > Ben -- probably the ACR changes in 5.6 don't fall back nicely anymore > > when there's no firmware? The load shouldn't be failed, just GR > > disabled... > > > > Zeno -- if

On Fri, Apr 3, 2020 at 1:59 PM Zeno Davatz <zdavatz at gmail.com> wrote: > > On Fri, Apr 3, 2020 at 7:23 PM Ilia Mirkin <imirkin at alum.mit.edu> wrote: > > > > On Fri, Apr 3, 2020 at 1:21 PM Zeno Davatz <zdavatz at gmail.com> wrote: > > > > > > On Fri, Apr 3, 2020 at 6:59 PM Ilia Mirkin <imirkin at alum.mit.edu> wrote: > > >

CentOS Errata and Enhancement Advisory 2014:1269 Upstream details at : https://rhn.redhat.com/errata/RHEA-2014-1269.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 1d14a5fb5974bb26cbd68e03b614dba131dd84319e9b6233d08edb3a2badc0e2 iwl1000-firmware-39.31.5.1-35.el7_0.noarch.rpm

On Thu, Jan 21, 2016 at 8:41 PM, Emil Velikov <emil.l.velikov at gmail.com> wrote: > Hi Alexandre, > > On 18 January 2016 at 06:07, Alexandre Courbot <acourbot at nvidia.com> wrote: >> Add two functions nvkm_firmware_get() and nvkm_firmware_put() to load a >> firmware file and free its resources, respectively. Since firmware files >> are becoming a necessity

Hi everyone, I know, it's about f**king time and I apologize for the time it took us to finally put this together. m(__)m I have pushed two git branches which enable GM200 and GM204 (GM206 to follow soon) owners to finally load NVIDIA-provided signed firmware and start GR: - https://github.com/Gnurou/linux-firmware/tree/secboot contains the signed firmware for GM200 and GM204 (they are

This patch set mainly allows the user to build a seabios or rombios only version of hvmloader. In addition, when building a seabios only hvmloader, Option ROMs like vgabios and etherboot are no longer required, and therefore can be disabled from the build. Dependency on the bcc compiler can also be avoided the same way. v2: Separate patches for separate issues Introduced config option to

On 12 May 2015 at 19:04, Alexandre Courbot <gnurou at gmail.com> wrote: > Hi Ben, > > On Fri, May 1, 2015 at 8:01 AM, Ben Skeggs <skeggsb at gmail.com> wrote: >> On 13 April 2015 at 20:42, Alexandre Courbot <acourbot at nvidia.com> wrote: >>> Ben, I guess our main remaining concern with this patch is how it should >>> integrate wrt. the existing

... and demote non-conformant kernel-doc header. Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/nouveau/nvkm/core/firmware.c:71: warning: Function parameter or member 'subdev' not described in 'nvkm_firmware_get' drivers/gpu/drm/nouveau/nvkm/core/firmware.c:71: warning: Function parameter or member 'fwname' not described in 'nvkm_firmware_get'

Add two functions nvkm_firmware_get() and nvkm_firmware_put() to load a firmware file and free its resources, respectively. Since firmware files are becoming a necessity for new GPUs, and their location has been standardized to nvidia/chip/, this will prevent duplicate and error-prone name-generation code. Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> ---

On 19 June 2015 at 00:47, Alexandre Courbot <gnurou at gmail.com> wrote: > NVIDIA will officially start providing signed firmwares through > linux-firmware. Change the GR firmware lookup function to look them up > in addition to the extracted firmwares. I wonder if perhaps we should just replace the mechanism entirely, and remove the support for nouveau/fuc* as we add "official" support for NVIDIA's ucode....