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 related but this is a troublesome MacBookPro10,1 with regard to hibernating so it my be unrelated. Thanks for any suggestions Andrew Processing triggers for initramfs-tools (0.133) ... update-initramfs: Generating /boot/initrd.img-4.19.0-2-amd64 W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/unload_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/bl.bin for module nouveau
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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914517 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
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 harddisk when mount file > system. Try running this command as root: update-initramfs -u -k 4.19.0-2-amd64 Does that print any error or warning messages? If not, does that fix the problem (i.e. can you then reboot into the new kernel version)? If that doesn't work: - Select the "recovery mode" entry for 4.19 on the boot menu, and take a picture of the output. - Run this command as root: mkinitramfs -v -o $(mktemp) 4.19.0-2-amd64 > mkinitramfs.log 2>&1 - Reply with the picture and mkinitramfs.log as attachments. Ben. -- Ben Hutchings Knowledge is power. France is bacon. signature.asc Description: This is a digitally signed message part
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 SSD?) Added tag(s) moreinfo. -- 922028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922028 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
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 assistance. -- 922488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
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 assistance. -- 886485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886485 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
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 claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 918330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: linux Version: 4.9.144-1 Severity: serious Justification: FTBFS Control: tags -1 + ftbfs Control: affects -1 + release.debian.org For tracking: linux/4.9.144-1 FTBFS on mips, mips64el and mipsel due to ABI changes: https://buildd.debian.org/status/fetch.php?pkg=linux=mips=4.9.144-1=1546583519=0 https://buildd.debian.org/status/fetch.php?pkg=linux=mips64el=4.9.144-1=1546593472=0 https://buildd.debian.org/status/fetch.php?pkg=linux=mipsel=4.9.144-1=1546592923=0 Regards, Salvatore --- End Message --- --- Begin Message --- Version: 4.9.144-2 Fixed by "[mips*] inst: Avoid ABI change in 4.9.136 (fixes FTBFS)". Ben. -- Ben Hutchings Knowledge is power. France is bacon. signature.asc Description: This is a digitally signed message part --- End Message ---
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 Powering Off to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 712953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sysvinit Version: 2.88dsf-41 Severity: normal Dear Maintainer, When I attempt to power off the machine (either logging out of gnome3, or via shutdown now typed in at a terminal) the system goes through the shutdown sequence (it does seem to pause after telling all processes to terminate and then reports that some processes are still running). It finally reports it is about to power off. But the computer then restarts and reboots. If I load up Debian Wheezy and shut that down, the computer powers off properly. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sysvinit depends on: ii debianutils 4.3.4 ii initscripts 2.88dsf-41 ii libc6 2.17-5 ii libselinux1 2.1.13-2 ii libsepol1 2.1.9-2 ii sysv-rc 2.88dsf-41 ii sysvinit-utils 2.88dsf-41 sysvinit recommends no packages. sysvinit suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- On Sat, 2019-03-09 at 07:35 +, Alan Chandler wrote: > On 09/03/2019 2:41 am, Ben Hutchings wrote: > > Control: tag -1 moreinfo > > > > On Fri, 21 Jun 2013 09:13:19 +0100 "Alan Chandler" < > > a...@chandlerfamily.org.uk> wrote: > > > Package: sysvinit > > > Version: 2.88dsf-41 > > > Severity: normal > > > > > > Dear Maintainer, > > > > > > When I attempt to power off the machine (either logging out of gnome3, or > > > via shutdown now typed in at a terminal) > > > the system goes through the shutdown sequence (it does seem to pause > > > after telling all processes to terminate and > > > then reports that some processes are still running). It finally reports > > > it is about to power off. > > > > > > But the computer then restarts and reboots. > > > > > > If I load up Debian Wheezy and shut that down, the computer powers off > > > properly. > > Sorry this report took so long to get assigned properly. Is this still > > happening in a current Debian version? > > > > Ben. > > > > This was 6 years ago. I don't have the problem now. Therefore I'm closing this report. Ben. -- Ben Hutchings Knowledge is power. France is bacon. signature.asc Description: This is a digitally signed message part --- End Message ---
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 that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 918188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: linux Version: 4.9.144-1 Severity: serious Justification: FTBFS For tracking the issue: 4.9.144-1 FTBFS on arm64: > LD vmlinux.o > MODPOST vmlinux.o > GEN .version > CHK include/generated/compile.h > UPD include/generated/compile.h > CC init/version.o > LD init/built-in.o > ./drivers/firmware/efi/libstub/lib.a(arm64-stub.stub.o): In function > `handle_kernel_image': > ./debian/build/build_arm64_none_arm64/./drivers/firmware/efi/libstub/arm64-stub.c:63: > undefined reference to `__efistub__GLOBAL_OFFSET_TABLE_' > ld: ./drivers/firmware/efi/libstub/lib.a(arm64-stub.stub.o): relocation > R_AARCH64_ADR_PREL_PG_HI21 against external symbol > `__efistub__GLOBAL_OFFSET_TABLE_' can not be used when making a shared > object; recompile with -fPIC > /<>/Makefile:1010: recipe for target 'vmlinux' failed > make[5]: *** [vmlinux] Error 1 > Makefile:152: recipe for target 'sub-make' failed > make[4]: *** [sub-make] Error 2 > Makefile:24: recipe for target '__sub-make' failed > make[3]: *** [__sub-make] Error 2 > make[3]: Leaving directory > '/<>/debian/build/build_arm64_none_arm64' > debian/rules.real:190: recipe for target > 'debian/stamps/build_arm64_none_arm64' failed > make[2]: *** [debian/stamps/build_arm64_none_arm64] Error 2 > make[2]: Leaving directory '/<>' > debian/rules.gen:400: recipe for target 'build-arch_arm64_none_arm64_real' > failed > make[1]: *** [build-arch_arm64_none_arm64_real] Error 2 > make[1]: Leaving directory '/<>' > debian/rules:41: recipe for target 'build-arch' failed > make: *** [build-arch] Error 2 > dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 https://buildd.debian.org/status/fetch.php?pkg=linux=arm64=4.9.144-1=1546572157=0 (different issue than #914556). Regards, Salvatore --- End Message --- --- Begin Message --- Version: 4.9.144-2 Fixed by "efi/libstub: Unify command line param parsing". Ben. -- Ben Hutchings Knowledge is power. France is bacon. signature.asc Description: This is a digitally signed message part --- End Message ---
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 src:debian-installer from the stretch > > branch, which has s-p-u enabled, would fetch the fixed kernel and a > > couple of its udebs, at build time; the resulting netboot images > > wouldn't know about s-p-u though at run time, and would try to load > > udebs from stretch. > > [...] > > Why is that a problem? The only change made in 4.9.144-3.1 is in the > kernel image, and the module udebs don't have versioned dependencies. However, as an additional data point, the kernel currently sat in NEW and destined for stable has an ABI bump. If that's accepted, then I assume things will "just work" in the meantime as the old binary packages will hang around until they're decrufted, but it's worth bearing in mind. Regards, Adam
