Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
Hello again, 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'm getting. 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 > it > 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 > is > that one entry that I'm still getting. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
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 it 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 is that one entry that I'm still getting. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
On Sat, 2020-01-11 at 09:52 -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. > I meant to say something about this output below. This is what I get now after installing firmware-*-nonfree The other thing I want to mention is that the output below actually does I think show nonfree firmware. If I understand correctly I think everything after Calling hook intel_microcode is all nonfree software. Various intel, amd, nvidia packages of which some are definitely in the debian stretch firmware-*-nonfree packages... > 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. > > One thing of note here is that when I man update-initramfs, what > comes > back is the manpage for live-update-initramfs. This live-update- > initramfs manpage doesn't give much info. I actually got more info > when > I ran update-initramfs with no arguments, from there I saw the -v > option so I tried that. > > Interestingly, that verbose output from update-initramfs -uv (below) > doesn't contain the words nonfree or non-free anywhere. > >live-update-initramfs is a wrapper replacing the update- > initramfs command provided by the initramfs-tools package. > > > > 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'll see if there's a more conclusive way to know this than the > output > of -uv. > > > > > Thanks! > glad to help :) > > > > Here's the output from update-initramfs -uv in case it's interesting. > Sorry it's ~ 1500 lines. > > Available versions: 4.19.0-6-amd64 > 4.9.0-11-amd64 > Keeping /boot/initrd.img-4.19.0-6-amd64.dpkg-bak > update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64 > Copying module directory kernel/drivers/usb/host > (excluding hwa-hc.ko sl811_cs.ko sl811-hcd.ko u132-hcd.ko whci- > hcd.ko) > Adding module /lib/modules/4.19.0-6- > amd64/kernel/drivers/usb/common/usb-common.ko > Adding module /lib/modules/4.19.0-6- > amd64/kernel/drivers/usb/core/usbcore.ko > Adding module /lib/modules/4.19.0-6- > amd64/kernel/drivers/usb/host/ehci- > hcd.ko > Adding module /lib/modules/4.19.0-6- > amd64/kernel/drivers/usb/host/ohci- > hcd.ko > Adding module /lib/modules/4.19.0-6- > amd64/kernel/drivers/usb/host/ohci- > pci.ko > Adding module /lib/modules/4.19.0-6- > amd64/kernel/drivers/usb/host/xhci- > hcd.ko > Adding module /lib/modules/4.19.0-6- > amd64/kernel/drivers/usb/host/ehci- > pci.ko > Adding module /lib/modules/4.19.0-6- > amd64/kernel/drivers/usb/host/uhci- > hcd.ko > Adding module /lib/modules/4.19.0-6- > amd64/kernel/drivers/usb/host/xhci- > pci.ko > Copying module directory kernel/drivers/input/keyboard > Adding module /lib/modules/4.19.0-6- > amd64/kernel/drivers/input/keyboard/stowaway.ko > Adding module /lib/modules/4.19.0-6- > amd64/kernel/drivers/input/matrix- > keymap.ko > Adding module /lib/modules/4.19.0-6- > amd64/kernel/drivers/input/keyboard/max7359_keypad.ko > Adding module /lib/modules/4.19.0-6- > amd64/kernel/drivers/input/keyboard/qt2160.ko > Adding module /lib/modules/4.19.0-6- > amd64/kernel/drivers/input/keyboard/newtonkbd.ko > Adding module /lib/modules/4.19.0-6- > amd64/kernel/drivers/input/keyboard/adp5588-keys.ko > Adding module /lib/modules/4.19.0-6- > amd64/kernel/drivers/input/keyboard/gpio_keys.ko > Adding module /lib/modules/4.19.0-6- > amd64/kernel/drivers/input/keyboard/sunkbd.ko > Adding module /lib/modules/4.19.0-6- > amd64/kernel/drivers/input/keyboard/lkkbd.ko > Adding module /lib/modules/4.19.0-6- > amd64/kernel
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
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. 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. One thing of note here is that when I man update-initramfs, what comes back is the manpage for live-update-initramfs. This live-update- initramfs manpage doesn't give much info. I actually got more info when I ran update-initramfs with no arguments, from there I saw the -v option so I tried that. Interestingly, that verbose output from update-initramfs -uv (below) doesn't contain the words nonfree or non-free anywhere. live-update-initramfs is a wrapper replacing the update- initramfs command provided by the initramfs-tools package. > > 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'll see if there's a more conclusive way to know this than the output of -uv. > > > Thanks! glad to help :) Here's the output from update-initramfs -uv in case it's interesting. Sorry it's ~ 1500 lines. Available versions: 4.19.0-6-amd64 4.9.0-11-amd64 Keeping /boot/initrd.img-4.19.0-6-amd64.dpkg-bak update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64 Copying module directory kernel/drivers/usb/host (excluding hwa-hc.ko sl811_cs.ko sl811-hcd.ko u132-hcd.ko whci-hcd.ko) Adding module /lib/modules/4.19.0-6- amd64/kernel/drivers/usb/common/usb-common.ko Adding module /lib/modules/4.19.0-6- amd64/kernel/drivers/usb/core/usbcore.ko Adding module /lib/modules/4.19.0-6-amd64/kernel/drivers/usb/host/ehci- hcd.ko Adding module /lib/modules/4.19.0-6-amd64/kernel/drivers/usb/host/ohci- hcd.ko Adding module /lib/modules/4.19.0-6-amd64/kernel/drivers/usb/host/ohci- pci.ko Adding module /lib/modules/4.19.0-6-amd64/kernel/drivers/usb/host/xhci- hcd.ko Adding module /lib/modules/4.19.0-6-amd64/kernel/drivers/usb/host/ehci- pci.ko Adding module /lib/modules/4.19.0-6-amd64/kernel/drivers/usb/host/uhci- hcd.ko Adding module /lib/modules/4.19.0-6-amd64/kernel/drivers/usb/host/xhci- pci.ko Copying module directory kernel/drivers/input/keyboard Adding module /lib/modules/4.19.0-6- amd64/kernel/drivers/input/keyboard/stowaway.ko Adding module /lib/modules/4.19.0-6-amd64/kernel/drivers/input/matrix- keymap.ko Adding module /lib/modules/4.19.0-6- amd64/kernel/drivers/input/keyboard/max7359_keypad.ko Adding module /lib/modules/4.19.0-6- amd64/kernel/drivers/input/keyboard/qt2160.ko Adding module /lib/modules/4.19.0-6- amd64/kernel/drivers/input/keyboard/newtonkbd.ko Adding module /lib/modules/4.19.0-6- amd64/kernel/drivers/input/keyboard/adp5588-keys.ko Adding module /lib/modules/4.19.0-6- amd64/kernel/drivers/input/keyboard/gpio_keys.ko Adding module /lib/modules/4.19.0-6- amd64/kernel/drivers/input/keyboard/sunkbd.ko Adding module /lib/modules/4.19.0-6- amd64/kernel/drivers/input/keyboard/lkkbd.ko Adding module /lib/modules/4.19.0-6- amd64/kernel/drivers/input/keyboard/xtkbd.ko Adding module /lib/modules/4.19.0-6- amd64/kernel/drivers/input/keyboard/opencores-kbd.ko Adding module /lib/modules/4.19.0-6- amd64/kernel/drivers/input/keyboard/lm8323.ko Copying module directory kernel/drivers/hid (excluding hid-*ff.ko hid-a4tech.ko hid-cypress.ko hid-dr.ko hid- elecom.ko hid-gyration.ko hid-icade.ko hid-kensington.ko hid-kye.ko hid-lcpower.ko hid-magicmouse.ko hid-multitouch.ko hid-ntrig.ko hid- petalynx.ko hid-picolcd.ko hid-pl.ko hid-ps3remote.ko hid-quanta.ko hid-roccat-ko*.ko hid-roccat-pyra.ko hid-saitek.ko hid-sensor-hub.ko hid-sony.ko hid-speedlink.ko hid-tivo.ko hid-twinhan.ko hid-uclogic.ko hid-wacom.ko hid-waltop.ko hid-wiimote.ko hid-zydacron.ko) Adding module /lib/modules/4.19.0-6-amd64/kernel/drivers/hid/h
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
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. 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). Thanks! ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
> On Fri, 2020-01-10 at 11:25 +0100, Svante Signell via Dng wrote: > > On Thu, 2020-01-09 at 16:17 -0700, 'smee via Dng wrote: > > > Actually, after apt remove *nonfree (and a reboot for good > > > measure), > > > update-initramfs -u still comes back with the same exact output > > > including that last line... > > > > I think your problems are with the new (beowulf) image. It is not > > using any non- > > free parts (or does it?). Did you boot with the old (ascii) kernel > > and tried > > update-initramfs -u? > > > > On my images I only have firmware-linux-free installed, dpkg -l | > > grep firmware. > > > I just ran update-initramfs -u on my ascii install (on which I also > removed *nonfree yesterday) and I'm still getting the same message. > IIRC, I ran the same command yesterday before ever removing anything > and was seeing the same results. > > I can double-check that later today by installing ascii fresh and > seewhat I get. > > 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. 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. > > ___ > > Dng mailing list > > Dng@lists.dyne.org > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
I just ran update-initramfs -u on my ascii install (on which I also removed *nonfree yesterday) and I'm still getting the same message. IIRC, I ran the same command yesterday before ever removing anything and was seeing the same results. I can double-check that later today by installing ascii fresh and seewhat I get. On Fri, 2020-01-10 at 11:25 +0100, Svante Signell via Dng wrote: > On Thu, 2020-01-09 at 16:17 -0700, 'smee via Dng wrote: > > Actually, after apt remove *nonfree (and a reboot for good > > measure), > > update-initramfs -u still comes back with the same exact output > > including that last line... > > I think your problems are with the new (beowulf) image. It is not > using any non- > free parts (or does it?). Did you boot with the old (ascii) kernel > and tried > update-initramfs -u? > > On my images I only have firmware-linux-free installed, dpkg -l | > grep firmware. > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
On 1/9/20 3:40 PM, 'smee via Dng wrote: > > Correct, I can add it and try reinstall but just trying to figure out > why firmeware-misc-nonfree and firmware-linux-nonfree are there. If the > simplest answer is just that I must have installed them myself, I can > accept that, but I don't think they're there by default, and according > to this excersize seem to require me to enable the non-free > repository... > Sorry I'm tuning into this late. No, you didn't install those non-free packages on your system. I am the one who did that. The live isos have non-free firmware installed but do not have contrib and non-free in sources.list. They also have a script to remove all the non-free packages that are installed. That script is in /usr/local/bin/remove-non-free-firmware in the desktop-live and /root/remove-firmware.sh in the minimal live. After running that script and removing all the non-free firmware, you might decide that you needed one of those packages. They are included in the desktop-live iso. (They're in /firmware on the media.) That's done in case you delete your only means of getting online to get your wireless driver. fsmithred ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
On Thu, 2020-01-09 at 16:17 -0700, 'smee via Dng wrote: > Actually, after apt remove *nonfree (and a reboot for good measure), > update-initramfs -u still comes back with the same exact output > including that last line... I think your problems are with the new (beowulf) image. It is not using any non- free parts (or does it?). Did you boot with the old (ascii) kernel and tried update-initramfs -u? On my images I only have firmware-linux-free installed, dpkg -l | grep firmware. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
On Thu, 2020-01-09 at 17:30 -0700, 'smee via Dng wrote: > But, right there on that same page, where it lists ascii, why does it > not list the new policy? > > Also, can you point me to where ascii's policy on nonfree software? A > web search for 'devuan ascii non-free programs' doesn't reveal > anything > relevant... Sorry I found it right in the release notes. I just need to be more diligent is all. Sorry to derail the conversation, but it was a revelation for me. Thanks for pointing that out ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
But, right there on that same page, where it lists ascii, why does it not list the new policy? Also, can you point me to where ascii's policy on nonfree software? A web search for 'devuan ascii non-free programs' doesn't reveal anything relevant... On Thu, 2020-01-09 at 17:27 -0700, 'smee via Dng wrote: > Sorry that was in Jessie. I guess I never saw the one for ascii. > > On Thu, 2020-01-09 at 17:24 -0700, 'smee via Dng wrote: > > But what about this... out of date? Can't be mis-interpreting > > it...that > > really implies that any default install of Devuan should not have > > nonfree software, and that it takes extra steps to get nonfree > > software. This feels like kind of a big deal to be honest. > > > > > > "All software shipped with Devuan in the main component is free > > software. But if needed, non-free software is also available. Just > > add > > the non-free and contrib component to the appropriate line(s) in > > /etc/apt/sources'list like this: ..." > > > > https://devuan.org/get-devuan > > > > > > On Thu, 2020-01-09 at 18:10 -0600, goli...@devuan.org wrote: > > > On 2020-01-09 15:28, 'smee via Dng wrote: > > > > Actually, when you run the ascii live installer, both of those > > > > programs > > > > are present. > > > > > > > > Should that be the case? I thought devuan include nothing > > > > nonfree > > > > by > > > > default... > > > > > > > > > > Official policy in ascii: > > > > > > Installer isos: If you would like to select an alternate > > > bootloader > > > (lilo) or exclude non-free firmware, you must select one of the > > > Expert > > > install options. > > > > > > live isos: Firmware files are available and automatically > > > installed > > > if > > > needed. > > > > > > golinux > > > > > > ___ > > > Dng mailing list > > > Dng@lists.dyne.org > > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > > > > ___ > > Dng mailing list > > Dng@lists.dyne.org > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
Sorry that was in Jessie. I guess I never saw the one for ascii. On Thu, 2020-01-09 at 17:24 -0700, 'smee via Dng wrote: > But what about this... out of date? Can't be mis-interpreting > it...that > really implies that any default install of Devuan should not have > nonfree software, and that it takes extra steps to get nonfree > software. This feels like kind of a big deal to be honest. > > > "All software shipped with Devuan in the main component is free > software. But if needed, non-free software is also available. Just > add > the non-free and contrib component to the appropriate line(s) in > /etc/apt/sources'list like this: ..." > > https://devuan.org/get-devuan > > > On Thu, 2020-01-09 at 18:10 -0600, goli...@devuan.org wrote: > > On 2020-01-09 15:28, 'smee via Dng wrote: > > > Actually, when you run the ascii live installer, both of those > > > programs > > > are present. > > > > > > Should that be the case? I thought devuan include nothing nonfree > > > by > > > default... > > > > > > > Official policy in ascii: > > > > Installer isos: If you would like to select an alternate > > bootloader > > (lilo) or exclude non-free firmware, you must select one of the > > Expert > > install options. > > > > live isos: Firmware files are available and automatically installed > > if > > needed. > > > > golinux > > > > ___ > > Dng mailing list > > Dng@lists.dyne.org > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
But what about this... out of date? Can't be mis-interpreting it...that really implies that any default install of Devuan should not have nonfree software, and that it takes extra steps to get nonfree software. This feels like kind of a big deal to be honest. "All software shipped with Devuan in the main component is free software. But if needed, non-free software is also available. Just add the non-free and contrib component to the appropriate line(s) in /etc/apt/sources'list like this: ..." https://devuan.org/get-devuan On Thu, 2020-01-09 at 18:10 -0600, goli...@devuan.org wrote: > On 2020-01-09 15:28, 'smee via Dng wrote: > > Actually, when you run the ascii live installer, both of those > > programs > > are present. > > > > Should that be the case? I thought devuan include nothing nonfree > > by > > default... > > > > Official policy in ascii: > > Installer isos: If you would like to select an alternate bootloader > (lilo) or exclude non-free firmware, you must select one of the > Expert > install options. > > live isos: Firmware files are available and automatically installed > if > needed. > > golinux > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
On 2020-01-09 15:28, 'smee via Dng wrote: Actually, when you run the ascii live installer, both of those programs are present. Should that be the case? I thought devuan include nothing nonfree by default... Official policy in ascii: Installer isos: If you would like to select an alternate bootloader (lilo) or exclude non-free firmware, you must select one of the Expert install options. live isos: Firmware files are available and automatically installed if needed. golinux ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
I think I see what you're saying, that the intel and amd programs weren't necessarily part of firmware-linux-nonfree or the other, but that that they just got caught in my command because they have nonfree in their filenames. The only thing I know for sure is that I didn't install any of them manually. On Thu, 2020-01-09 at 16:39 -0700, 'smee via Dng wrote: > It seems like it did that, tried to remove a number of packages that > aren't installed, but also found those intel and amd programs, and > removed those. Seems to have accomplished exactly what I needed... > > On Thu, 2020-01-09 at 18:36 -0500, Hendrik Boom wrote: > > On Thu, Jan 09, 2020 at 02:34:34PM -0700, 'smee via Dng wrote: > > > Below is the output from apt remove *nonfree. > > > > It looks as if this command removed, or tried to remove, all > > packages > > whose name > > ended in "nonfree". > > > > But wouldn't it look for files whose names ended in "nonfree" and > > try > > to remove > > packages that have the same name as those files? > > > > -- hendrik > > > > > On both machines it looks pretty much identical. On both > > > machines, > > > it > > > mentions the following: > > > > > > The following packages were automatically installed and are no > > > longer > > > required: > > > amd64-microcode intel-microcode iucode-tool > > > > > > > > > This makes me think they were the programs that needed it. > > > Unfortunately I'm not ME free, and I don't trust intel (or amd) > > > so > > > I > > > worry that this nonfree software already did it's dirty work to > > > enable > > > intel or amd spying. > > > > > > aptitude why firmware-linux-nonfree > > > W: Package firmware-misc-nonfree had been marked to reinstall, > > > but > > > the > > > file for the current installed version 20161130-3 is not > > > available > > > Manually installed, current version 20161130-3, priority optional > > > No dependencies require to install firmware-linux-nonfree > > > root@dooby1:/# aptitude why firmware-misc-nonfree > > > W: Package firmware-misc-nonfree had been marked to reinstall, > > > but > > > the > > > file for the current installed version 20161130-3 is not > > > available > > > i firmware-linux-nonfree Depends firmware-misc-nonfree (= > > > 20161130-3) > > > root@dooby1:/# vi /etc/apt/sources.list > > > root@dooby1:/# history|grep nonfree > > > 496 apt list firmware-misc-nonfree > > > 497 history|grep firmeware-misc-nonfree > > > 498 apt show firmware-misc-nonfree > > > 499 apt --fix-broken install firmware-misc-nonfree > > > 510 apt-cache policy firmware-misc-nonfree > > > 511 aptitude why firmware-misc-nonfree > > > 512 aptitude reinstall firmware-misc-nonfree > > > 515 apt show firmware-linux-nonfree > > > 516 aptitude why firmware-linux-nonfree > > > 517 aptitude why firmware-misc-nonfree > > > 519 history|grep nonfree > > > root@dooby1:/# apt remove *nonfree > > > Reading package lists... Done > > > Building dependency tree > > > Reading state information... Done > > > Note, selecting 'predictprotein-nonfree' for glob '*nonfree' > > > Note, selecting 'context-nonfree' for glob '*nonfree' > > > Note, selecting 'netpbm-nonfree' for glob '*nonfree' > > > Note, selecting 'context-doc-nonfree' for glob '*nonfree' > > > Note, selecting 'flashplugin-nonfree' for glob '*nonfree' > > > Note, selecting 'unace-nonfree' for glob '*nonfree' > > > Note, selecting 'texinfo-doc-nonfree' for glob '*nonfree' > > > Note, selecting 'firmware-linux-nonfree' for glob '*nonfree' > > > Note, selecting 'unrar-nonfree' for glob '*nonfree' > > > Note, selecting 'filters-nonfree' for glob '*nonfree' > > > Note, selecting 'firmware-misc-nonfree' for glob '*nonfree' > > > Package 'context-nonfree' is not installed, so not removed > > > Package 'context-doc-nonfree' is not installed, so not removed > > > Package 'filters-nonfree' is not installed, so not removed > > > Package 'texinfo-doc-nonfree' is not installed, so not removed > > > Package 'flashplugin-nonfree' is not installed, so not removed > > > Package 'netpbm-nonfree' is not installed, so not removed > > > Package 'unace-nonfree' is not installed, so not removed > > > Package 'predictprotein-nonfree' is not installed, so not removed > > > Package 'unrar-nonfree' is not installed, so not removed > > > The following packages were automatically installed and are no > > > longer > > > required: > > > amd64-microcode intel-microcode iucode-tool > > > Use 'apt autoremove' to remove them. > > > The following packages will be REMOVED: > > > firmware-linux-nonfree firmware-misc-nonfree > > > 0 upgraded, 0 newly installed, 2 to remove and 34 not upgraded. > > > After this operation, 8,174 kB disk space will be freed. > > > > > > > > > > > > On Thu, 2020-01-09 at 14:28 -0700, 'smee via Dng wrote: > > > > Actually, when you run the ascii live installer, both of those > > > > programs > > > > are present. > > > > > > > > Should that be the case? I thought devuan inclu
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
It seems like it did that, tried to remove a number of packages that aren't installed, but also found those intel and amd programs, and removed those. Seems to have accomplished exactly what I needed... On Thu, 2020-01-09 at 18:36 -0500, Hendrik Boom wrote: > On Thu, Jan 09, 2020 at 02:34:34PM -0700, 'smee via Dng wrote: > > Below is the output from apt remove *nonfree. > > It looks as if this command removed, or tried to remove, all packages > whose name > ended in "nonfree". > > But wouldn't it look for files whose names ended in "nonfree" and try > to remove > packages that have the same name as those files? > > -- hendrik > > > On both machines it looks pretty much identical. On both machines, > > it > > mentions the following: > > > > The following packages were automatically installed and are no > > longer > > required: > > amd64-microcode intel-microcode iucode-tool > > > > > > This makes me think they were the programs that needed it. > > Unfortunately I'm not ME free, and I don't trust intel (or amd) so > > I > > worry that this nonfree software already did it's dirty work to > > enable > > intel or amd spying. > > > > aptitude why firmware-linux-nonfree > > W: Package firmware-misc-nonfree had been marked to reinstall, but > > the > > file for the current installed version 20161130-3 is not available > > Manually installed, current version 20161130-3, priority optional > > No dependencies require to install firmware-linux-nonfree > > root@dooby1:/# aptitude why firmware-misc-nonfree > > W: Package firmware-misc-nonfree had been marked to reinstall, but > > the > > file for the current installed version 20161130-3 is not available > > i firmware-linux-nonfree Depends firmware-misc-nonfree (= > > 20161130-3) > > root@dooby1:/# vi /etc/apt/sources.list > > root@dooby1:/# history|grep nonfree > > 496 apt list firmware-misc-nonfree > > 497 history|grep firmeware-misc-nonfree > > 498 apt show firmware-misc-nonfree > > 499 apt --fix-broken install firmware-misc-nonfree > > 510 apt-cache policy firmware-misc-nonfree > > 511 aptitude why firmware-misc-nonfree > > 512 aptitude reinstall firmware-misc-nonfree > > 515 apt show firmware-linux-nonfree > > 516 aptitude why firmware-linux-nonfree > > 517 aptitude why firmware-misc-nonfree > > 519 history|grep nonfree > > root@dooby1:/# apt remove *nonfree > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > Note, selecting 'predictprotein-nonfree' for glob '*nonfree' > > Note, selecting 'context-nonfree' for glob '*nonfree' > > Note, selecting 'netpbm-nonfree' for glob '*nonfree' > > Note, selecting 'context-doc-nonfree' for glob '*nonfree' > > Note, selecting 'flashplugin-nonfree' for glob '*nonfree' > > Note, selecting 'unace-nonfree' for glob '*nonfree' > > Note, selecting 'texinfo-doc-nonfree' for glob '*nonfree' > > Note, selecting 'firmware-linux-nonfree' for glob '*nonfree' > > Note, selecting 'unrar-nonfree' for glob '*nonfree' > > Note, selecting 'filters-nonfree' for glob '*nonfree' > > Note, selecting 'firmware-misc-nonfree' for glob '*nonfree' > > Package 'context-nonfree' is not installed, so not removed > > Package 'context-doc-nonfree' is not installed, so not removed > > Package 'filters-nonfree' is not installed, so not removed > > Package 'texinfo-doc-nonfree' is not installed, so not removed > > Package 'flashplugin-nonfree' is not installed, so not removed > > Package 'netpbm-nonfree' is not installed, so not removed > > Package 'unace-nonfree' is not installed, so not removed > > Package 'predictprotein-nonfree' is not installed, so not removed > > Package 'unrar-nonfree' is not installed, so not removed > > The following packages were automatically installed and are no > > longer > > required: > > amd64-microcode intel-microcode iucode-tool > > Use 'apt autoremove' to remove them. > > The following packages will be REMOVED: > > firmware-linux-nonfree firmware-misc-nonfree > > 0 upgraded, 0 newly installed, 2 to remove and 34 not upgraded. > > After this operation, 8,174 kB disk space will be freed. > > > > > > > > On Thu, 2020-01-09 at 14:28 -0700, 'smee via Dng wrote: > > > Actually, when you run the ascii live installer, both of those > > > programs > > > are present. > > > > > > Should that be the case? I thought devuan include nothing nonfree > > > by > > > default...I have to make it part of my routine to remove them > > > then > > > from > > > every devuan install. > > > That's a surprising find. :( > > > > > > > > > > > > On Thu, 2020-01-09 at 14:21 -0700, 'smee via Dng wrote: > > > > I just checked another machine that is still running ascii, on > > > > which > > > > I > > > > would never have installed anything nonfree, or via wget or > > > > dpkg, > > > > and > > > > yet both firmware-linux-nonfree and firmware-misc-nonfree are > > > > there. > > > > > > > > I'm going to try a fresh install of ascii and see i
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
On Thu, Jan 09, 2020 at 02:34:34PM -0700, 'smee via Dng wrote: > Below is the output from apt remove *nonfree. It looks as if this command removed, or tried to remove, all packages whose name ended in "nonfree". But wouldn't it look for files whose names ended in "nonfree" and try to remove packages that have the same name as those files? -- hendrik > > On both machines it looks pretty much identical. On both machines, it > mentions the following: > > The following packages were automatically installed and are no longer > required: > amd64-microcode intel-microcode iucode-tool > > > This makes me think they were the programs that needed it. > Unfortunately I'm not ME free, and I don't trust intel (or amd) so I > worry that this nonfree software already did it's dirty work to enable > intel or amd spying. > > aptitude why firmware-linux-nonfree > W: Package firmware-misc-nonfree had been marked to reinstall, but the > file for the current installed version 20161130-3 is not available > Manually installed, current version 20161130-3, priority optional > No dependencies require to install firmware-linux-nonfree > root@dooby1:/# aptitude why firmware-misc-nonfree > W: Package firmware-misc-nonfree had been marked to reinstall, but the > file for the current installed version 20161130-3 is not available > i firmware-linux-nonfree Depends firmware-misc-nonfree (= 20161130-3) > root@dooby1:/# vi /etc/apt/sources.list > root@dooby1:/# history|grep nonfree > 496 apt list firmware-misc-nonfree > 497 history|grep firmeware-misc-nonfree > 498 apt show firmware-misc-nonfree > 499 apt --fix-broken install firmware-misc-nonfree > 510 apt-cache policy firmware-misc-nonfree > 511 aptitude why firmware-misc-nonfree > 512 aptitude reinstall firmware-misc-nonfree > 515 apt show firmware-linux-nonfree > 516 aptitude why firmware-linux-nonfree > 517 aptitude why firmware-misc-nonfree > 519 history|grep nonfree > root@dooby1:/# apt remove *nonfree > Reading package lists... Done > Building dependency tree > Reading state information... Done > Note, selecting 'predictprotein-nonfree' for glob '*nonfree' > Note, selecting 'context-nonfree' for glob '*nonfree' > Note, selecting 'netpbm-nonfree' for glob '*nonfree' > Note, selecting 'context-doc-nonfree' for glob '*nonfree' > Note, selecting 'flashplugin-nonfree' for glob '*nonfree' > Note, selecting 'unace-nonfree' for glob '*nonfree' > Note, selecting 'texinfo-doc-nonfree' for glob '*nonfree' > Note, selecting 'firmware-linux-nonfree' for glob '*nonfree' > Note, selecting 'unrar-nonfree' for glob '*nonfree' > Note, selecting 'filters-nonfree' for glob '*nonfree' > Note, selecting 'firmware-misc-nonfree' for glob '*nonfree' > Package 'context-nonfree' is not installed, so not removed > Package 'context-doc-nonfree' is not installed, so not removed > Package 'filters-nonfree' is not installed, so not removed > Package 'texinfo-doc-nonfree' is not installed, so not removed > Package 'flashplugin-nonfree' is not installed, so not removed > Package 'netpbm-nonfree' is not installed, so not removed > Package 'unace-nonfree' is not installed, so not removed > Package 'predictprotein-nonfree' is not installed, so not removed > Package 'unrar-nonfree' is not installed, so not removed > The following packages were automatically installed and are no longer > required: > amd64-microcode intel-microcode iucode-tool > Use 'apt autoremove' to remove them. > The following packages will be REMOVED: > firmware-linux-nonfree firmware-misc-nonfree > 0 upgraded, 0 newly installed, 2 to remove and 34 not upgraded. > After this operation, 8,174 kB disk space will be freed. > > > > On Thu, 2020-01-09 at 14:28 -0700, 'smee via Dng wrote: > > Actually, when you run the ascii live installer, both of those > > programs > > are present. > > > > Should that be the case? I thought devuan include nothing nonfree by > > default...I have to make it part of my routine to remove them then > > from > > every devuan install. > > That's a surprising find. :( > > > > > > > > On Thu, 2020-01-09 at 14:21 -0700, 'smee via Dng wrote: > > > I just checked another machine that is still running ascii, on > > > which > > > I > > > would never have installed anything nonfree, or via wget or dpkg, > > > and > > > yet both firmware-linux-nonfree and firmware-misc-nonfree are > > > there. > > > > > > I'm going to try a fresh install of ascii and see if they're there. > > > I > > > suspect they won't be, which will mean one of the few programs I > > > run > > > on > > > that machine would be at fault, so that should make it easier to > > > narrow > > > down. This is pretty odd though. > > > > > > > > > > > > On Thu, 2020-01-09 at 14:00 -0700, 'smee via Dng wrote: > > > > Well I'll just remove the damn things and see if nothing blows up > > > > :) > > > > > > > > > > > > > > > > > > > > On Thu, 2020-01-09 at 21:55 +0100, Antony Stone wrote: > > > > > > So
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
Actually, after apt remove *nonfree (and a reboot for good measure), update-initramfs -u still comes back with the same exact output including that last line... On Thu, 2020-01-09 at 23:13 +0100, Svante Signell via Dng wrote: > On Thu, 2020-01-09 at 14:34 -0700, 'smee via Dng wrote: > > Below is the output from apt remove *nonfree. > > > > On both machines it looks pretty much identical. On both machines, > > it > > mentions the following: > > > > The following packages were automatically installed and are no > > longer > > required: > > amd64-microcode intel-microcode iucode-tool > > To summarize: Your problems were not due to eudev, right? > Can you create the initrd file w/o problems now? > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
On Thu, 2020-01-09 at 14:34 -0700, 'smee via Dng wrote: > Below is the output from apt remove *nonfree. > > On both machines it looks pretty much identical. On both machines, it > mentions the following: > > The following packages were automatically installed and are no longer > required: > amd64-microcode intel-microcode iucode-tool To summarize: Your problems were not due to eudev, right? Can you create the initrd file w/o problems now? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
Below is the output from apt remove *nonfree. On both machines it looks pretty much identical. On both machines, it mentions the following: The following packages were automatically installed and are no longer required: amd64-microcode intel-microcode iucode-tool This makes me think they were the programs that needed it. Unfortunately I'm not ME free, and I don't trust intel (or amd) so I worry that this nonfree software already did it's dirty work to enable intel or amd spying. aptitude why firmware-linux-nonfree W: Package firmware-misc-nonfree had been marked to reinstall, but the file for the current installed version 20161130-3 is not available Manually installed, current version 20161130-3, priority optional No dependencies require to install firmware-linux-nonfree root@dooby1:/# aptitude why firmware-misc-nonfree W: Package firmware-misc-nonfree had been marked to reinstall, but the file for the current installed version 20161130-3 is not available i firmware-linux-nonfree Depends firmware-misc-nonfree (= 20161130-3) root@dooby1:/# vi /etc/apt/sources.list root@dooby1:/# history|grep nonfree 496 apt list firmware-misc-nonfree 497 history|grep firmeware-misc-nonfree 498 apt show firmware-misc-nonfree 499 apt --fix-broken install firmware-misc-nonfree 510 apt-cache policy firmware-misc-nonfree 511 aptitude why firmware-misc-nonfree 512 aptitude reinstall firmware-misc-nonfree 515 apt show firmware-linux-nonfree 516 aptitude why firmware-linux-nonfree 517 aptitude why firmware-misc-nonfree 519 history|grep nonfree root@dooby1:/# apt remove *nonfree Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'predictprotein-nonfree' for glob '*nonfree' Note, selecting 'context-nonfree' for glob '*nonfree' Note, selecting 'netpbm-nonfree' for glob '*nonfree' Note, selecting 'context-doc-nonfree' for glob '*nonfree' Note, selecting 'flashplugin-nonfree' for glob '*nonfree' Note, selecting 'unace-nonfree' for glob '*nonfree' Note, selecting 'texinfo-doc-nonfree' for glob '*nonfree' Note, selecting 'firmware-linux-nonfree' for glob '*nonfree' Note, selecting 'unrar-nonfree' for glob '*nonfree' Note, selecting 'filters-nonfree' for glob '*nonfree' Note, selecting 'firmware-misc-nonfree' for glob '*nonfree' Package 'context-nonfree' is not installed, so not removed Package 'context-doc-nonfree' is not installed, so not removed Package 'filters-nonfree' is not installed, so not removed Package 'texinfo-doc-nonfree' is not installed, so not removed Package 'flashplugin-nonfree' is not installed, so not removed Package 'netpbm-nonfree' is not installed, so not removed Package 'unace-nonfree' is not installed, so not removed Package 'predictprotein-nonfree' is not installed, so not removed Package 'unrar-nonfree' is not installed, so not removed The following packages were automatically installed and are no longer required: amd64-microcode intel-microcode iucode-tool Use 'apt autoremove' to remove them. The following packages will be REMOVED: firmware-linux-nonfree firmware-misc-nonfree 0 upgraded, 0 newly installed, 2 to remove and 34 not upgraded. After this operation, 8,174 kB disk space will be freed. On Thu, 2020-01-09 at 14:28 -0700, 'smee via Dng wrote: > Actually, when you run the ascii live installer, both of those > programs > are present. > > Should that be the case? I thought devuan include nothing nonfree by > default...I have to make it part of my routine to remove them then > from > every devuan install. > That's a surprising find. :( > > > > On Thu, 2020-01-09 at 14:21 -0700, 'smee via Dng wrote: > > I just checked another machine that is still running ascii, on > > which > > I > > would never have installed anything nonfree, or via wget or dpkg, > > and > > yet both firmware-linux-nonfree and firmware-misc-nonfree are > > there. > > > > I'm going to try a fresh install of ascii and see if they're there. > > I > > suspect they won't be, which will mean one of the few programs I > > run > > on > > that machine would be at fault, so that should make it easier to > > narrow > > down. This is pretty odd though. > > > > > > > > On Thu, 2020-01-09 at 14:00 -0700, 'smee via Dng wrote: > > > Well I'll just remove the damn things and see if nothing blows up > > > :) > > > > > > > > > > > > > > > On Thu, 2020-01-09 at 21:55 +0100, Antony Stone wrote: > > > > > Sorry if we're getting off track here but I honestly don't > > > > > recall > > > > > installing anything nonfree on this machine. > > > > > > > > We may never get to the bottom of this mystery :) > > > > > > ___ > > > Dng mailing list > > > Dng@lists.dyne.org > > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > > > > ___ > > Dng mailing list > > Dng@lists.dyne.org > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > >
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
Actually, when you run the ascii live installer, both of those programs are present. Should that be the case? I thought devuan include nothing nonfree by default...I have to make it part of my routine to remove them then from every devuan install. That's a surprising find. :( On Thu, 2020-01-09 at 14:21 -0700, 'smee via Dng wrote: > I just checked another machine that is still running ascii, on which > I > would never have installed anything nonfree, or via wget or dpkg, and > yet both firmware-linux-nonfree and firmware-misc-nonfree are there. > > I'm going to try a fresh install of ascii and see if they're there. I > suspect they won't be, which will mean one of the few programs I run > on > that machine would be at fault, so that should make it easier to > narrow > down. This is pretty odd though. > > > > On Thu, 2020-01-09 at 14:00 -0700, 'smee via Dng wrote: > > Well I'll just remove the damn things and see if nothing blows up > > :) > > > > > > > > > > On Thu, 2020-01-09 at 21:55 +0100, Antony Stone wrote: > > > > Sorry if we're getting off track here but I honestly don't > > > > recall > > > > installing anything nonfree on this machine. > > > > > > We may never get to the bottom of this mystery :) > > > > ___ > > Dng mailing list > > Dng@lists.dyne.org > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
I just checked another machine that is still running ascii, on which I would never have installed anything nonfree, or via wget or dpkg, and yet both firmware-linux-nonfree and firmware-misc-nonfree are there. I'm going to try a fresh install of ascii and see if they're there. I suspect they won't be, which will mean one of the few programs I run on that machine would be at fault, so that should make it easier to narrow down. This is pretty odd though. On Thu, 2020-01-09 at 14:00 -0700, 'smee via Dng wrote: > Well I'll just remove the damn things and see if nothing blows up :) > > > > > On Thu, 2020-01-09 at 21:55 +0100, Antony Stone wrote: > > > Sorry if we're getting off track here but I honestly don't recall > > > installing anything nonfree on this machine. > > > > We may never get to the bottom of this mystery :) > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
Well I'll just remove the damn things and see if nothing blows up :) On Thu, 2020-01-09 at 21:55 +0100, Antony Stone wrote: > > Sorry if we're getting off track here but I honestly don't recall > > installing anything nonfree on this machine. > > We may never get to the bottom of this mystery :) ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
On Thursday 09 January 2020 at 21:51:32, 'smee via Dng wrote: > Right, and as I mention apt says firmware-linux-nonfree was manually > installed, but I don't recall installing it. It says it isn't a > dependency for anything else, so it wasn't installed as a dependency > when I installed something else. Hm, odd. > In addition to my not remembering installing firmware-linux-nonfree, wouldn't > it have required me to add the non-free repository to have installed it in > the first place? I don't think there's another way of doing it (other than wget the .deb and then dpkg -i, but I think it's even more likely you'd remember doing that :) ) > Sorry if we're getting off track here but I honestly don't recall > installing anything nonfree on this machine. We may never get to the bottom of this mystery :) Antony. -- René Descartes walks in to a bar. The barman asks him "Do you want a drink?" Descartes says "I think not," and disappears. Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
Right, and as I mention apt says firmware-linux-nonfree was manually installed, but I don't recall installing it. It says it isn't a dependency for anything else, so it wasn't installed as a dependency when I installed something else. In addition to my not remembering installing firmware-linux-nonfree, wouldn't it have required me to add the non-free repository to have installed it in the first place? Sorry if we're getting off track here but I honestly don't recall installing anything nonfree on this machine. On Thu, 2020-01-09 at 21:43 +0100, Antony Stone wrote: > On Thursday 09 January 2020 at 21:40:16, 'smee via Dng wrote: > > > On Thu, 2020-01-09 at 21:29 +0100, Antony Stone wrote: > > > On Thursday 09 January 2020 at 21:25:51, 'smee via Dng wrote: > > > > "i firmware-linux-nonfree Depends firmware-misc-nonfree (= > > > > 20161130-3)" > > > > > > No, that's not itself :) Thats' "firmware-LINUX-nonfree" :) > > > > aah I see. apt shows firmware-linux-nonfree was manually installed, > > I > > don't recall ever installing it, in fact I thought I had > > successfully > > avoided installing anything nonfree in devuan on this machine. So I > > thought it must be a dependency itself, but aptitude why shows no > > dependencies. > > "i firmware-linux-nonfree Depends firmware-misc-nonfree" means that > firmware- > linux-nonfree is installed, and depends on firmware-misc-nonfree, > which is > therefore the reason why firmware-misc-nonfree is itself installed. > > It reduces the question instead to "why is firmware-linux-nonfree > installed?" > > > Antony. > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
On Thursday 09 January 2020 at 21:40:16, 'smee via Dng wrote: > On Thu, 2020-01-09 at 21:29 +0100, Antony Stone wrote: > > On Thursday 09 January 2020 at 21:25:51, 'smee via Dng wrote: > > > > > > "i firmware-linux-nonfree Depends firmware-misc-nonfree (= > > > 20161130-3)" > > > > No, that's not itself :) Thats' "firmware-LINUX-nonfree" :) > > aah I see. apt shows firmware-linux-nonfree was manually installed, I > don't recall ever installing it, in fact I thought I had successfully > avoided installing anything nonfree in devuan on this machine. So I > thought it must be a dependency itself, but aptitude why shows no > dependencies. "i firmware-linux-nonfree Depends firmware-misc-nonfree" means that firmware- linux-nonfree is installed, and depends on firmware-misc-nonfree, which is therefore the reason why firmware-misc-nonfree is itself installed. It reduces the question instead to "why is firmware-linux-nonfree installed?" Antony. -- +++ Divide By Cucumber Error. Please Reinstall Universe And Reboot +++ Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
On Thu, 2020-01-09 at 21:29 +0100, Antony Stone wrote: > On Thursday 09 January 2020 at 21:25:51, 'smee via Dng wrote: > > > > Does "aptitude why firmware-misc-nonfree" help? > > > > nothing other than itself listed after depends... > > > > "i firmware-linux-nonfree Depends firmware-misc-nonfree (= > > 20161130- > > 3)" > > No, that's not itself :) Thats' "firmware-LINUX-nonfree" :) aah I see. apt shows firmware-linux-nonfree was manually installed, I don't recall ever installing it, in fact I thought I had successfully avoided installing anything nonfree in devuan on this machine. So I thought it must be a dependency itself, but aptitude why shows no dependencies. > > > > How about "apt-cache policy firmware-misc-nonfree" > > > > firmware-misc-nonfree: > > Installed: 20161130-3 > > Candidate: 20161130-3 > > Version table: > > *** 20161130-3 100 > > 100 /var/lib/dpkg/status > > Okay, so you certainly have the latest installed. > > > > or "aptitude reinstall firmware-misc-nonfree"? > > > > oddly aptitude says it can't find a source for the package that I > > have > > installed. I assume aptitude uses /etc/apt/sources.list so it > > should > > point to beowulf repo's by default. > > This confirms that you don't have "non-free" in your sources.list > file: Correct, I can add it and try reinstall but just trying to figure out why firmeware-misc-nonfree and firmware-linux-nonfree are there. If the simplest answer is just that I must have installed them myself, I can accept that, but I don't think they're there by default, and according to this excersize seem to require me to enable the non-free repository... > > On Thursday 09 January 2020 at 21:24:51, Svante Signell via Dng > wrote: > > > Did you add non-free to your sources.list? > > deb http://deb.devuan.org/merged beowulf main non-free > > Regards, > > > Antony. > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
On Thursday 09 January 2020 at 21:25:51, 'smee via Dng wrote: > > Does "aptitude why firmware-misc-nonfree" help? > > nothing other than itself listed after depends... > > "i firmware-linux-nonfree Depends firmware-misc-nonfree (= 20161130- > 3)" No, that's not itself :) Thats' "firmware-LINUX-nonfree" :) > > How about "apt-cache policy firmware-misc-nonfree" > > firmware-misc-nonfree: > Installed: 20161130-3 > Candidate: 20161130-3 > Version table: > *** 20161130-3 100 > 100 /var/lib/dpkg/status Okay, so you certainly have the latest installed. > > or "aptitude reinstall firmware-misc-nonfree"? > > oddly aptitude says it can't find a source for the package that I have > installed. I assume aptitude uses /etc/apt/sources.list so it should > point to beowulf repo's by default. This confirms that you don't have "non-free" in your sources.list file: On Thursday 09 January 2020 at 21:24:51, Svante Signell via Dng wrote: > Did you add non-free to your sources.list? > deb http://deb.devuan.org/merged beowulf main non-free Regards, Antony. -- People who use Microsoft software should be certified. Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
> Does "aptitude why firmware-misc-nonfree" help? nothing other than itself listed after depends... "i firmware-linux-nonfree Depends firmware-misc-nonfree (= 20161130- 3)" > How about "apt-cache policy firmware-misc-nonfree" firmware-misc-nonfree: Installed: 20161130-3 Candidate: 20161130-3 Version table: *** 20161130-3 100 100 /var/lib/dpkg/status > or "aptitude reinstall firmware-misc-nonfree"? oddly aptitude says it can't find a source for the package that I have installed. I assume aptitude uses /etc/apt/sources.list so it should point to beowulf repo's by default. The following packages will be REINSTALLED: firmware-misc-nonfree 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 34 not upgraded. E: Can't find a source to download version '20161130-3' of 'firmware- misc-nonfree:amd64' After unpacking 0 B will be used. E: Can't find a source to download version '20161130-3' of 'firmware- misc-nonfree:amd64' E: Internal error: couldn't generate list of packages to download E: Perhaps the package lists are out of date, please try 'aptitude update' (or equivalent); otherwise some packages or versions are not available from the current repository sources On Thu, 2020-01-09 at 21:13 +0100, Antony Stone wrote: > On Thursday 09 January 2020 at 21:00:57, 'smee via Dng wrote: > > > apt show showed that firmware-misc-nonfree was not installed > > manually. > > > > > I tried a apt --fix-broken install firmware-misc-nonfree but that > > didn't do anything except mark it as manually installed. > > How about "apt-cache policy firmware-misc-nonfree" or "aptitude > reinstall > firmware-misc-nonfree"? > > > Antony. > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
On Thu, 2020-01-09 at 13:00 -0700, 'smee via Dng wrote: > apt show showed that firmware-misc-nonfree was not installed manually. > > I tried a apt --fix-broken install firmware-misc-nonfree but that > didn't do anything except mark it as manually installed. > Did you add non-free to your sources.list? deb http://deb.devuan.org/merged beowulf main non-free ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
Rebooted without problems. grep'd /var/log for eudev and nothing alarming or new came back. Also grep'd dmesg for eudev, again nothing alarming. Should I look anywhere else? I did a find for eudev.log on / and didn't find anything. On Thu, 2020-01-09 at 13:00 -0700, 'smee wrote: > apt show showed that firmware-misc-nonfree was not installed > manually. > > I tried a apt --fix-broken install firmware-misc-nonfree but that > didn't do anything except mark it as manually installed. > > > > On Thu, 2020-01-09 at 12:57 -0700, 'smee via Dng wrote: > > Is firmware-misc-nonfree a dependency for something? I don't recall > > installing it manually and didn't think it would be there by > > default. > > Apt doesn't say auto or manual, but it is installed. Maybe needs an > > update... > > > > On Thu, 2020-01-09 at 20:38 +0100, Svante Signell via Dng wrote: > > > On Thu, 2020-01-09 at 20:32 +0100, Svante Signell wrote: > > > > ... > > > > > update-initramfs: deferring update (trigger activated) > > > > > Processing triggers for man-db (2.8.5-2) ... > > > > > Processing triggers for libc-bin (2.28-10) ... > > > > > Processing triggers for initramfs-tools (0.133+deb10u1) ... > > > > > update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64 > > > > > W: Possible missing firmware > > > > > /lib/firmware/nvidia/gp107/sec2/sig.bin > > > > > for module nouveau > > > > ... > > > > > > Did you install the firmware for the new kernel? Seems to be the > > > package > > > firmware-misc-nonfree you need. > > > > > > ___ > > > Dng mailing list > > > Dng@lists.dyne.org > > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > > > > ___ > > Dng mailing list > > Dng@lists.dyne.org > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
On Thursday 09 January 2020 at 21:00:57, 'smee via Dng wrote: > apt show showed that firmware-misc-nonfree was not installed manually. Does "aptitude why firmware-misc-nonfree" help? > I tried a apt --fix-broken install firmware-misc-nonfree but that > didn't do anything except mark it as manually installed. How about "apt-cache policy firmware-misc-nonfree" or "aptitude reinstall firmware-misc-nonfree"? Antony. -- Tinned food was developed for the British Navy in 1813. The tin opener was not invented until 1858. Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
apt show showed that firmware-misc-nonfree was not installed manually. I tried a apt --fix-broken install firmware-misc-nonfree but that didn't do anything except mark it as manually installed. On Thu, 2020-01-09 at 12:57 -0700, 'smee via Dng wrote: > Is firmware-misc-nonfree a dependency for something? I don't recall > installing it manually and didn't think it would be there by default. > Apt doesn't say auto or manual, but it is installed. Maybe needs an > update... > > On Thu, 2020-01-09 at 20:38 +0100, Svante Signell via Dng wrote: > > On Thu, 2020-01-09 at 20:32 +0100, Svante Signell wrote: > > > ... > > > > update-initramfs: deferring update (trigger activated) > > > > Processing triggers for man-db (2.8.5-2) ... > > > > Processing triggers for libc-bin (2.28-10) ... > > > > Processing triggers for initramfs-tools (0.133+deb10u1) ... > > > > update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64 > > > > W: Possible missing firmware > > > > /lib/firmware/nvidia/gp107/sec2/sig.bin > > > > for module nouveau > > > ... > > > > Did you install the firmware for the new kernel? Seems to be the > > package > > firmware-misc-nonfree you need. > > > > ___ > > Dng mailing list > > Dng@lists.dyne.org > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
Is firmware-misc-nonfree a dependency for something? I don't recall installing it manually and didn't think it would be there by default. Apt doesn't say auto or manual, but it is installed. Maybe needs an update... On Thu, 2020-01-09 at 20:38 +0100, Svante Signell via Dng wrote: > On Thu, 2020-01-09 at 20:32 +0100, Svante Signell wrote: > > ... > > > update-initramfs: deferring update (trigger activated) > > > Processing triggers for man-db (2.8.5-2) ... > > > Processing triggers for libc-bin (2.28-10) ... > > > Processing triggers for initramfs-tools (0.133+deb10u1) ... > > > update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64 > > > W: Possible missing firmware > > > /lib/firmware/nvidia/gp107/sec2/sig.bin > > > for module nouveau > > ... > > Did you install the firmware for the new kernel? Seems to be the > package > firmware-misc-nonfree you need. > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
Just tried update-initramfs -u and got all that same output, ending
again with that same line, so update-initramfs is what's throwing that
line:
live-boot: core filesystems devices utils udev blockdev dns.
On Thu, 2020-01-09 at 20:32 +0100, Svante Signell via Dng wrote:
> On Thu, 2020-01-09 at 11:31 -0700, 'smee via Dng wrote:
> > Here is the output from apt when I upgraded. Various repeating
> > messages
> > about missing firmware.
> > I haven't rebooted yet, or done anything else really. Slightly
> > worried
> > I'll lose graphics when I reboot because of the message.
> ...
> > Reading state information... Done
> > The following packages will be upgraded:
> > eudev libeudev1
> > 2 upgraded, 0 newly installed, 0 to remove and 34 not upgraded.
> > Need to get 1,163 kB of archives.
> > After this operation, 173 kB of additional disk space will be used.
> > Get:1 http://pkgmaster.devuan.org/devuan unstable/main amd64 eudev
> > amd64 3.2.9-2 [1,068 kB]
> > Get:2 http://pkgmaster.devuan.org/devuan unstable/main amd64
> > libeudev1
> > amd64 3.2.9-2 [95.2 kB]
> ...
> > update-initramfs: deferring update (trigger activated)
> > Processing triggers for man-db (2.8.5-2) ...
> > Processing triggers for libc-bin (2.28-10) ...
> > Processing triggers for initramfs-tools (0.133+deb10u1) ...
> > update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64
> > W: Possible missing firmware
> > /lib/firmware/nvidia/gp107/sec2/sig.bin
> > for module nouveau
> ...
>
> This is a due to the execution of update-initramfs creating
> initrd.img-... This
> is the last comment issued when upgrading, and happens with all
> eudev/udev
> upgrades. From eudev.postinst:
> update_initramfs() {
> [ -x /usr/sbin/update-initramfs -a -e /etc/initramfs-
> tools/initramfs.conf ] \
> || return 0
> update-initramfs -u
> }
>
> configure)
> ...
> update_initramfs
> ;;
>
> Have you tried to manually run update-initramfs -u? Or downgraded to
> 3.2.7-6?
>
> > live-boot: core filesystems devices utils udev blockdev dns.
>
> Where does this come from?
>
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
On Thu, 2020-01-09 at 20:32 +0100, Svante Signell wrote: > > ... > > update-initramfs: deferring update (trigger activated) > > Processing triggers for man-db (2.8.5-2) ... > > Processing triggers for libc-bin (2.28-10) ... > > Processing triggers for initramfs-tools (0.133+deb10u1) ... > > update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64 > > W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/sig.bin > > for module nouveau > ... Did you install the firmware for the new kernel? Seems to be the package firmware-misc-nonfree you need. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
On Thu, 2020-01-09 at 11:31 -0700, 'smee via Dng wrote:
> Here is the output from apt when I upgraded. Various repeating messages
> about missing firmware.
> I haven't rebooted yet, or done anything else really. Slightly worried
> I'll lose graphics when I reboot because of the message.
...
> Reading state information... Done
> The following packages will be upgraded:
> eudev libeudev1
> 2 upgraded, 0 newly installed, 0 to remove and 34 not upgraded.
> Need to get 1,163 kB of archives.
> After this operation, 173 kB of additional disk space will be used.
> Get:1 http://pkgmaster.devuan.org/devuan unstable/main amd64 eudev
> amd64 3.2.9-2 [1,068 kB]
> Get:2 http://pkgmaster.devuan.org/devuan unstable/main amd64 libeudev1
> amd64 3.2.9-2 [95.2 kB]
...
> update-initramfs: deferring update (trigger activated)
> Processing triggers for man-db (2.8.5-2) ...
> Processing triggers for libc-bin (2.28-10) ...
> Processing triggers for initramfs-tools (0.133+deb10u1) ...
> update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64
> W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/sig.bin
> for module nouveau
...
This is a due to the execution of update-initramfs creating initrd.img-... This
is the last comment issued when upgrading, and happens with all eudev/udev
upgrades. From eudev.postinst:
update_initramfs() {
[ -x /usr/sbin/update-initramfs -a -e /etc/initramfs-tools/initramfs.conf ] \
|| return 0
update-initramfs -u
}
configure)
...
update_initramfs
;;
Have you tried to manually run update-initramfs -u? Or downgraded to 3.2.7-6?
> live-boot: core filesystems devices utils udev blockdev dns.
Where does this come from?
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
Here is the output from apt when I upgraded. Various repeating messages about missing firmware. I haven't rebooted yet, or done anything else really. Slightly worried I'll lose graphics when I reboot because of the message. Reading state information... Done The following packages will be upgraded: eudev libeudev1 2 upgraded, 0 newly installed, 0 to remove and 34 not upgraded. Need to get 1,163 kB of archives. After this operation, 173 kB of additional disk space will be used. Get:1 http://pkgmaster.devuan.org/devuan unstable/main amd64 eudev amd64 3.2.9-2 [1,068 kB] Get:2 http://pkgmaster.devuan.org/devuan unstable/main amd64 libeudev1 amd64 3.2.9-2 [95.2 kB] Fetched 1,163 kB in 3s (409 kB/s) Reading changelogs... Done (Reading database ... 172005 files and directories currently installed.) Preparing to unpack .../eudev_3.2.9-2_amd64.deb ... dpkg-query: package 'udev' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. Unpacking eudev (3.2.9-2) over (3.2.7-6) ... Preparing to unpack .../libeudev1_3.2.9-2_amd64.deb ... Unpacking libeudev1:amd64 (3.2.9-2) over (3.2.7-6) ... Setting up libeudev1:amd64 (3.2.9-2) ... Setting up eudev (3.2.9-2) ... Installing new version of config file /etc/init.d/eudev ... [ ok ] Stopping hot-plug events dispatcher: udevd. [ ok ] Starting hot-plug events dispatcher: udevd. *** Warning: eudev will default to the older network interface names, such as eth0 or wlan0. If you use the new names, such as enp0s3, you will need to add the following to the boot command: net.ifnames=1 update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.8.5-2) ... Processing triggers for libc-bin (2.28-10) ... Processing triggers for initramfs-tools (0.133+deb10u1) ... update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64 W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/acr/unload_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/acr/bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable! (PATH error)
On Thu, 2020-01-09 at 12:38 -0300, Gastón via Dng wrote: > On Thu, Jan 09, 2020 at 12:13:10PM +0100, Svante Signell via Dng wrote: > > Hello, ... > > Steps to test: > > You can also use country codes: e.g. http://de.deb.devuan.org... > > /etc/init.d/sources.list > This path should be: /etc/apt/sources.list Thank for finding the typo. What about your upgrade results? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable! (PATH error)
On Thu, Jan 09, 2020 at 12:13:10PM +0100, Svante Signell via Dng wrote:
> Hello,
>
> We are currently working on updating eudev from 3.2.7 to 3.2.9 for Beowulf.
> Current version in Beowulf/testing is now 3.2.7-6, and the latest 3.2.9-2
> version is in Ceres/unstable. In order to find out any remaining bugs, please
> test and report back any success/problems/bugs with that version.
>
> One issue is already known (and is a Debian bug too, even at udev-244-3):
> /etc/init.d/{udev,eudev} {start|stop|restart|reload|force-reload|status}
> udev does not support containers, not started ... (warning).
>
> Steps to test:
> You can also use country codes: e.g. http://de.deb.devuan.org...
> /etc/init.d/sources.list
This path should be: /etc/apt/sources.list
> # ascii
> deb http://deb.devuan.org/merged ascii main
>
> # beowulf
> deb http://deb.devuan.org/merged beowulf main
>
> # unstable
> deb http://deb.devuan.org/devuan unstable main
>
> apt-get -t beowulf upgrade
> apt-get -t beowulf dist-upgrade
>
> apt-get install -t unstable eudev libeudev1
>
>
>
>
> Thanks!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!
Hello,
We are currently working on updating eudev from 3.2.7 to 3.2.9 for Beowulf.
Current version in Beowulf/testing is now 3.2.7-6, and the latest 3.2.9-2
version is in Ceres/unstable. In order to find out any remaining bugs, please
test and report back any success/problems/bugs with that version.
One issue is already known (and is a Debian bug too, even at udev-244-3):
/etc/init.d/{udev,eudev} {start|stop|restart|reload|force-reload|status}
udev does not support containers, not started ... (warning).
Steps to test:
You can also use country codes: e.g. http://de.deb.devuan.org...
/etc/init.d/sources.list
# ascii
deb http://deb.devuan.org/merged ascii main
# beowulf
deb http://deb.devuan.org/merged beowulf main
# unstable
deb http://deb.devuan.org/devuan unstable main
apt-get -t beowulf upgrade
apt-get -t beowulf dist-upgrade
apt-get install -t unstable eudev libeudev1
Thanks!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
