Re: Kernel for Spectre and Meltdown

Hello, On Thu, Feb 01, 2018 at 11:53:36AM +, Michael Fothergill wrote: > Thus for anyone in the entire world who is new to linux,the most > efficient route at present could well be to install Fedora and be > stable and spectre protected out of the box rather than taking on > the indefatigable

Re: Undentified issue with primus or bumblebee.

OP wrote directly to me, sending back to list in case it helps others. 2018-02-01 3:38 GMT+01:00 tv.debian wrote: On 01/02/2018 01:38, Attilio Giuseppe Carolillo wrote: I use Debian "Buster" on a laptop Lenovo G580 (Geforce 635M). I updated the primus package 2015XXYY-6 but i didn't solved an

Re: minissdpd failure in update

On 02/01/2018 03:57 PM, Sven Hartge wrote: Sven Joachim wrote: On 2018-02-01 19:55 +0100, Sven Hartge wrote: Frank M wrote: Feb 01 13:39:07 franklin minissdpd[9152]: Error: please specify LAN network interface by name instead of IPv4 address : 0.0.0.0 Feb 01 13:39:07 franklin minissdpd[915

Re: Got tired of waiting for suspend/resume (something like that)

Curt wrote: > Still, I'm uncertain what goes into /etc/fstab. >/dev/mapper/swap none swap sw 0 0 > ? Yes, this is correct. With crypted-swap you need to use the device mapper device, because the UUID changes on every boot, as you discovered. (Which is the point of having a freshly encrypte

Re: minissdpd failure in update

Sven Joachim wrote: > On 2018-02-01 19:55 +0100, Sven Hartge wrote: >> Frank M wrote: >>> Feb 01 13:39:07 franklin minissdpd[9152]: Error: please specify LAN >>> network interface by name instead of IPv4 address : 0.0.0.0 >>> Feb 01 13:39:07 franklin minissdpd[9152]: can't parse "0.0.0.0" as a

Re: Got tired of waiting for suspend/resume (something like that)

On 2018-02-01, Nicolas George wrote: > >> Unfortunately my crypttab (which I've never touched or looked at) >> reveals the following: >> # >> cryptswap1 /dev/sda5 /dev/urandom swap,cipher=3Daes-cbc-essiv:sha256 >> Which is dangerous because that dev/sda5 gets wiped out at every

Re: minissdpd failure in update

On Thu, Feb 01, 2018 at 07:55:53PM +0100, Sven Hartge wrote: Your configuration is broken/wrong. You need to edit /etc/default/minissdpd and put the correct IP or device name into the variable "MiniSSDPd_INTERFACE_ADDRESS". Umm, no. It is expected that a debian package will not self destruct on

Re: minissdpd failure in update

On 2018-02-01 19:55 +0100, Sven Hartge wrote: > Frank M wrote: > >> Feb 01 13:39:07 franklin minissdpd[9152]: Error: please specify LAN >> network interface by name instead of IPv4 address : 0.0.0.0 >> Feb 01 13:39:07 franklin minissdpd[9152]: can't parse "0.0.0.0" as a >> valid address or inte

Re: Got tired of waiting for suspend/resume (something like that)

Curt (2018-02-01): > Unfortunately my crypttab (which I've never touched or looked at) > reveals the following: > > # > cryptswap1 /dev/sda5 /dev/urandom swap,cipher=aes-cbc-essiv:sha256 > > Which is dangerous because that dev/sda5 gets wiped out at every > (re)boot. The danger

Re: minissdpd failure in update

Frank M wrote: > Feb 01 13:39:07 franklin minissdpd[9152]: Error: please specify LAN > network interface by name instead of IPv4 address : 0.0.0.0 > Feb 01 13:39:07 franklin minissdpd[9152]: can't parse "0.0.0.0" as a > valid address or interface name Your configuration is broken/wrong. You ne

Re: Got tired of waiting for suspend/resume (something like that)

David Wright (2018-02-01): > Vaguely Thanks. > Later the page goes on to describe suspend/resume but not with > a random key. Some people might see that as a challenge, others > as an opportunity. I make no judgment of such people. The whole point of using an ephemeral key is to make the content

minissdpd failure in update

Updating my Sid installation this morning. Setting up minissdpd (1.5.20161216-1) ... Installing new version of config file /etc/init.d/minissdpd ... Job for minissdpd.service failed because the control process exited with error code. See "systemctl status minissdpd.service" and "journalctl -xe

Re: getting the right and complete firmware

On Thu, Feb 01, 2018 at 07:24:56PM +0100, Anil Duggirala wrote: > > ~$ apt-file search firmware-5.bin > > firmware-atheros: /lib/firmware/ath10k/QCA4019/hw1.0/firmware-5.bin > > For some reason I am not able to run that command, even as root. apt-file is not installed by default. It's a separate

Re: getting the right and complete firmware

> ~$ apt-file search firmware-5.bin > firmware-atheros: /lib/firmware/ath10k/QCA4019/hw1.0/firmware-5.bin For some reason I am not able to run that command, even as root. And that file is different to the one I am missing (th10k/QCA6174/hw3.0/firmware-5.bin) right? > > Then query the APT databas

Re: getting the right and complete firmware

> On an unmodified stretch (yours is unmodified, isn't it) > >  /sbin/modinfo ath10k_pci > > does not list any of these files in the firmware lines. So why should > the kernel want any of them? > I believe I have done a standard stretch install, yet /sbin/modinfo ath10k_pci : filename:   /l

Re: Network setup by installer

[Some rampant snipping, I'm afraid. Hope that is ok.] On Thu 01 Feb 2018 at 09:41:36 -0600, David Wright wrote: > On Thu 01 Feb 2018 at 10:55:35 (+), Brian wrote: > > > > > > Intended to do what? > > > > To leave the user without network connectivity after first boot? There > > are at leas

Re: Got tired of waiting for suspend/resume (something like that)

Curt wrote: > Unfortunately my crypttab (which I've never touched or looked at) > reveals the following: > > #               > cryptswap1 /dev/sda5 /dev/urandom swap,cipher=aes-cbc-essiv:sha256 > > Which is dangerous because that dev/sda5 gets wiped out at every > (re)boot. > > curty@einstei

Re: Got tired of waiting for suspend/resume (something like that)

On Thu 01 Feb 2018 at 17:48:18 (+0100), Nicolas George wrote: > David Wright (2018-02-01): > > That assumes it's stable. The OP said it's not. I'm making no judgment > > on the matter. > > The OP described the use of an ephemeral key to encrypt the swap. Are > you familiar with that practice? Vag

Re: Got tired of waiting for suspend/resume (something like that)

On 2018-02-01, Curt wrote: > On 2018-02-01, Nicolas George wrote: >> >> >> David Wright (2018-02-01): >>> As far as finding the swap partition with fstab, ISTR a workaround. >>> Without the details, you make the swap partition with a tiny >>> filesystem in it, which gives it a stable UUID and LAB

Re: Got tired of waiting for suspend/resume (something like that)

On 2018-02-01, Nicolas George wrote: > > > David Wright (2018-02-01): >> As far as finding the swap partition with fstab, ISTR a workaround. >> Without the details, you make the swap partition with a tiny >> filesystem in it, which gives it a stable UUID and LABEL. You then >> specify an offset in

Re: Got tired of waiting for suspend/resume (something like that)

David Wright (2018-02-01): > That assumes it's stable. The OP said it's not. I'm making no judgment > on the matter. The OP described the use of an ephemeral key to encrypt the swap. Are you familiar with that practice? If not, better acknowledge it and let the conversation pass by you. > The con

Re: Got tired of waiting for suspend/resume (something like that)

On Thu 01 Feb 2018 at 17:15:40 (+0100), Nicolas George wrote: > David Wright (2018-02-01): > > As far as finding the swap partition with fstab, ISTR a workaround. > > Without the details, you make the swap partition with a tiny > > filesystem in it, which gives it a stable UUID and LABEL. You then

Re: Got tired of waiting for suspend/resume (something like that)

David Wright (2018-02-01): > As far as finding the swap partition with fstab, ISTR a workaround. > Without the details, you make the swap partition with a tiny > filesystem in it, which gives it a stable UUID and LABEL. You then > specify an offset in every reference to its use, which skips over >

Re: Got tired of waiting for suspend/resume (something like that)

On Thu 01 Feb 2018 at 15:05:10 (+), Curt wrote: > On 2018-02-01, David Wright wrote: > >> > >> Sorry but where does that leave > >> > >> /etc/initramfs-tools/conf.d/resume > >> > >> > >> ??? > >> > >> Also 'RESUME=none'? > > > > Yes; but AIUI the important one is the one in the initramfs

Re: Network setup by installer

On Thu 01 Feb 2018 at 10:55:35 (+), Brian wrote: > On Wed 31 Jan 2018 at 20:05:17 -0600, David Wright wrote: > > > On Wed 31 Jan 2018 at 23:13:52 (+), Brian wrote: > > > On Wed 31 Jan 2018 at 12:29:38 -0600, David Wright wrote: > > > > > > > On Fri 19 Jan 2018 at 19:09:27 (+), Brian w

Re: Got tired of waiting for suspend/resume (something like that)

On 2018-02-01, David Wright wrote: >> >> Sorry but where does that leave >> >> /etc/initramfs-tools/conf.d/resume >> >> >> ??? >> >> Also 'RESUME=none'? > > Yes; but AIUI the important one is the one in the initramfs as that's > the one that gets looked at when you turn the computer on. Wel

Re: systemd 237-1: problem starting dnsmasq

On Wednesday, 31 January 2018 21:12:37 CET Stefan Pietsch wrote: > Jan 31 20:58:11 debiansid systemd[1]: dnsmasq.service: Permission denied > while opening PID file or unsafe symlink chain: /run/dnsmasq/dnsmasq.pid May be apparmor blocked this request. Can you check your kernel logs ? HTH --

Re: Debian Stretch: Problems with installation - computer froze

I experienced this today (Fed 1, 2018)

Re: Got tired of waiting for suspend/resume (something like that)

On Thu 01 Feb 2018 at 13:11:20 (+), Curt wrote: > On 2018-02-01, Curt wrote: > >> > >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D885160 > > > > Your very own bug report. > > > >> It includes an easy workaround: include "RESUME=none" in > >> /etc/initramfs-tools/initramfs.conf. > > >

Re: Got tired of waiting for suspend/resume (something like that)

On 2018-02-01, Curt wrote: > On 2018-02-01, Curt wrote: >> On 2018-02-01, Curt wrote: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D885160 >>> >>> Your very own bug report. >>> It includes an easy workaround: include "RESUME=none" in /etc/initramfs-tools/initramfs.conf.

Re: Got tired of waiting for suspend/resume (something like that)

On 2018-02-01, Curt wrote: > On 2018-02-01, Curt wrote: >>> >>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D885160 >> >> Your very own bug report. >> >>> It includes an easy workaround: include "RESUME=none" in >>> /etc/initramfs-tools/initramfs.conf. >> > > Sorry but where does that leav

Re: Got tired of waiting for suspend/resume (something like that)

On 2018-02-01, Curt wrote: >> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D885160 > > Your very own bug report. > >> It includes an easy workaround: include "RESUME=none" in >> /etc/initramfs-tools/initramfs.conf. > Sorry but where does that leave /etc/initramfs-tools/conf.d/resume

Re: Got tired of waiting for suspend/resume (something like that)

On 2018-02-01, Nicolas George wrote: > > Curt (2018-02-01): >> It's something like "Tired of waiting for resume/suspend." > >> cryptsetup: WARNING: target cryptswap1 has a random key, skipped > > See this bug report: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D885160 Your very own bu

Re: Got tired of waiting for suspend/resume (something like that)

Curt (2018-02-01): > It's something like "Tired of waiting for resume/suspend." > cryptsetup: WARNING: target cryptswap1 has a random key, skipped See this bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885160 It includes an easy workaround: include "RESUME=none" in /etc/initram

Got tired of waiting for suspend/resume (something like that)

I've upgraded from Wheezy to Jessie and from Jessie to Stretch, which is a stretch, where I am currently residing (switched to the devil systemd, too). Unfamiliar with systemd commands, etc, I can't seem to find for the moment the exact message (after a minor delay) at boot which brings me here (

Re: Kernel for Spectre and Meltdown

On 30 January 2018 at 13:22, Greg Wooledge wrote: > On Tue, Jan 30, 2018 at 12:13:47PM +0100, Michael Lange wrote: > > Michael Fothergill wrote: > > > The response from Greg was the following: > > > > > > On Thu, Jan 25, 2018 at 12:36:46PM +, Michael Fothergill wrote: > > > > ​If I become si

Re: Network setup by installer

On Wed 31 Jan 2018 at 20:05:17 -0600, David Wright wrote: > On Wed 31 Jan 2018 at 23:13:52 (+), Brian wrote: > > On Wed 31 Jan 2018 at 12:29:38 -0600, David Wright wrote: > > > > > On Fri 19 Jan 2018 at 19:09:27 (+), Brian wrote: > > > > On Sat 20 Jan 2018 at 03:25:00 +0900, Mark Fletcher