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
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
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
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
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
> 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
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
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
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
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
>
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
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
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
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
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
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
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
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
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:
>
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
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,
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
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
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
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
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
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
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'
> 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:
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
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
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
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
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,
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
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.
...
>
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
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:
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
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
40 matches
Mail list logo
