Missing firmware files

After the latest upgrade of buster I get this list of missing files when it rebuilt my initramfs. The files are not in my current firmware-misc-nonfree 20190114-1 I don't know where they might be found - or how important they are. My suspend to ram is no longer working - I wondering if this is

Processed: severity of 914517 is important

Processing commands for cont...@bugs.debian.org: > severity 914517 important Bug #914517 [src:linux] linux-image-4.9.0-7-amd64: Boot fails unless nomodeset is set Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 914517:

Bug#922028: Can not start on Thinkpad X1 Carbon 5th (can not find its PCIe SSD?)

Control: severity -1 important Control: tag -1 moreinfo On Mon, 11 Feb 2019 20:25:04 +0800 gulfstream wrote: > Package: src:linux > Version: 4.19.16-1 > Severity: critical > > > Since I upgrade the kenel to 4.19, it does not work. For the version > 4.19.0.2-2, it may not find the PCIe SSD

Processed: Re: Can not start on Thinkpad X1 Carbon 5th (can not find its PCIe SSD?)

Processing control commands: > severity -1 important Bug #922028 [src:linux] Can not start on Thinkpad X1 Carbon 5th (can not find its PCIe SSD?) Severity set to 'important' from 'critical' > tag -1 moreinfo Bug #922028 [src:linux] Can not start on Thinkpad X1 Carbon 5th (can not find its PCIe

Processed: severity of 922488 is important

Processing commands for cont...@bugs.debian.org: > severity 922488 important Bug #922488 [src:linux] linux-image-4.9.0-8-amd64: Kernel panic in IPv6 stack after some hours of operation Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need

Processed: severity of 886485 is important

Processing commands for cont...@bugs.debian.org: > severity 886485 important Bug #886485 [src:linux] linux-image-4.9.0-5-686-pae: Hangs on boot at " node #0, CPUs:#1" Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need

Bug#918330: marked as done (linux: FTBFS on mips, mips64el and mipsel (ABI changes))

Your message dated Sat, 09 Mar 2019 14:15:30 + with message-id and subject line Re: linux: FTBFS on mips, mips64el and mipsel (ABI changes) has caused the Debian Bug report #918330, regarding linux: FTBFS on mips, mips64el and mipsel (ABI changes) to be marked as done. This means that you

Bug#712953: marked as done (sysvinit: System Restarts Instead of Powering Off)

Your message dated Sat, 09 Mar 2019 14:14:45 + with message-id <501e2213864a1bbd00835c87175a1eccb0c2ba9c.ca...@decadent.org.uk> and subject line Re: sysvinit: System Restarts Instead of Powering Off has caused the Debian Bug report #712953, regarding sysvinit: System Restarts Instead of

Bug#918188: marked as done (linux: FTBFS on arm64)

Your message dated Sat, 09 Mar 2019 14:14:02 + with message-id <3473ae1098aadc716e5f35d230268b2cf29bd79b.ca...@decadent.org.uk> and subject line Re: linux: FTBFS on arm64 has caused the Debian Bug report #918188, regarding linux: FTBFS on arm64 to be marked as done. This means that you claim

Re: Fixing stretch debian-installer on armhf

On Thu, 2019-03-07 at 22:01 +, Ben Hutchings wrote: > On Thu, 2019-03-07 at 14:39 +0100, Cyril Brulebois wrote: > [...] > > > * Rebuild the debian-installer images, pulling in updates from > > >   stretch-updates, leaving only armhf netboot targets broken.  > > > > Expanding a bit: rebuilding