Author: 'smee Date: To: dng Subject: Re: [DNG] When upgrading to Beowulf please test and report issues
with eudev-3.2.9-2 from unstable!
I'm pretty sure this one can be closed.
I ran another test on another laptop and basically, after upgrading to
Beowulf, and confirming that firmware-misc/linux-nonfree were both
installed and seemingly in good shape, and not mucking around with
anything else, I ran update-initramfs (this is with eudev/libeudev1
version 3.2.7-6, the old one) and it produced a list of missing
firmware, albeit a shorter one than I got on my other machine becuase
this is a different model.
Next I updated eudev and libeudev to 3.2.9-2, ran update-initramfs
again, and got the same exact output.
I also ran it in verbose mode and confirmed it does include a bunch of
intel, amd, and various other nonfree code like my other machine. I've
got all that output if you want to see it for any reason.
So, being that the same messages appeared after the Beowulf upgrade,
but PRIOR to upgrading eudev/libeudev1, as appeared AFTER upgrading
eudev/libeudev to the unstable 3.2.9-2, it doesn't appear to be related
to eudev or libeudev.
I assume that all my mucking around removing *nonfree on the other
machine, and then reinstalling it may account for the remaining message
I guess that if I used the netinstall image I wouldn't have any issues.
I can test that if you'd like on one or both machines and report back.
On Mon, 2020-01-13 at 13:02 -0700, 'smee wrote: > On Sat, 2020-01-11 at 10:50 +0100, Svante Signell via Dng wrote:
> > On Fri, 2020-01-10 at 18:15 -0700, 'smee via Dng wrote:
> > > > On Fri, 2020-01-10 at 11:25 +0100, Svante Signell via Dng
> > > > wrote:
> > > I just installed a fresh ascii install, ran update-initramfs -u
> > > and
> > > had
> > > no errors (I did see the same last line that's mentioned). So I
> > > tried
> > > apt remover *nonfree, let that run, and tried again and it
> > > produces
> > > that set of errors when the nonfree firmware is not there.
> > Good!
> > > So, as you mentioned the errors happened after the upgrade to
> > > Beowulf.
> > > I'm going to assume that it was just because firmware-misc-
> > > nonfree
> > > was
> > > in a bad state after the upgrade and that a reinstall of both
> > > firmware-
> > > misc-nonfree and firmware-linux-nonfree would fix the issue
> > > there.
> > > I
> > > can test that if you'd like, by doing the reinstall and running
> > > update-
> > > initramfs -u again.
> > Yes, please do. Then we know if we can close this issue or not.
> After reinstalling firmware-misc-nonfree and firmware-linux-nonfree,
> there is now only one error below about some missing nvidia firmware.
> update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64
> W: Possible missing firmware
> /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau
> live-boot: core filesystems devices utils udev blockdev dns.
> > Note that you
> > can choose how to update and backup by editing: /etc/initramfs-
> > tools/update-
> > initramfs.conf. You also have a lot of options for updating, see
> > the
> > manpage for
> > update-initramfs.
> > If possible, do also try to find out if your new (beowulf) kernel
> > initrd(.img-
> > 4.19.0-6-amd64, or whatever) has firmware-*-nonfree or not. (Don't
> > know how
> > yet).
> I ran update-initramfs -uv to get some verbose output. Unfortunately
> spit out about 1500 lines, which is pasted here.
> https://pastebin.com/PXaJTxRx >
> The verbose output does seem to include a bunch of nonfree modules,
> including AMD, intel NVIDIA, so I think this is definitive evidence
> that the initramfs image should include the nonfree. The only thing
> that one entry that I'm still getting.
This message was posted to the following mailing lists: