Bug#959706: auto-apt-proxy: Lacking _apt_proxy._tcp SRV dns record support for version 11

2020-05-04 Thread Markus Lindberg
Package: auto-apt-proxy Version: 11 Severity: normal Dear Maintainer, Version 11 of does not support the _apt_proxy._tcp SRV dns record feature which version 12 does. Version 12 is only available for testing and unstable would it be possible to deploy version 12 for stable as well or patch the

Bug#941122:

2020-02-09 Thread Markus Lindberg
linux-image-5.3.0-0.bpo.2-amd64 seems to be working which is available via buster-backports. I tried suspending a laptop and waking it up and no latency is produced while running a ping against another node on my LAN. -- Markus

Bug#941122:

2020-01-08 Thread Markus Lindberg
linux-image-5.3.0-0.bpo.2-amd64 seems to be working which is available via buster-backports. I tried suspending a laptop and waking it up and no latency is produced while running a ping against another node on my LAN. -- Markus

Bug#941122: e1000e is slow for I219-LM (rev 11)

2019-10-10 Thread Markus Lindberg
Interestingly linux-image-4.19.0-6-amd64 is working perfectly while linux-image-5.2.0-0.bpo.3-amd64 does not. -- Markus

Bug#941122: e1000e is slooow for I219-LM

2019-10-09 Thread Markus Lindberg
def4ec6dce39 ("e1000e: PCIm function state support") would be in 5.3-rc1 and above and was not backported. If you test the package from experimental, is the issue gone? If you cherry-pick this commit on top is the issue gone? I tried installing the linux-image-5.3.0-trunk-amd64 package from exp

Bug#941720: linux-headers-4.19.0-0.bpo.6-amd64 depends on linux-headers-4.19.0-0.bpo.6-common=4.19.67-2+deb10u1~bpo9+1 but only linux-headers-4.19.0-0.bpo.6-amd64=4.19.67-2~bpo9+1 is available

2019-10-08 Thread Markus Lindberg
I remeber that I saw linux-headers-4.19.0-0.bpo.6-common=4.19.67-2+deb10u1~bpo9+1 in the archive yesterday... Maybe I'm hallucinating :-) Something changed again and now that version is available again. So if it stays available I guess we can consider this bug resolved. -- Markus

Bug#941720: linux-headers-4.19.0-0.bpo.6-amd64 depends on linux-headers-4.19.0-0.bpo.6-common=4.19.67-2+deb10u1~bpo9+1 but only linux-headers-4.19.0-0.bpo.6-amd64=4.19.67-2~bpo9+1 is available

2019-10-07 Thread Markus Lindberg
I though I saw the correct version of the linux-headers-4.19.0-0.bpo.6-common package in the archive yesterday but it seems that it was rolled back? linux-headers-4.19.0-0.bpo.6-amd64 still depends on linux-headers-4.19.0-0.bpo.6-common=4.19.67-2+deb10u1~bpo9+1 but only linux-headers-4.19.0-0.bpo.

Bug#941720: linux-headers-4.19.0-0.bpo.6-amd64 depends on linux-headers-4.19.0-0.bpo.6-common=4.19.67-2+deb10u1~bpo9+1 but only linux-headers-4.19.0-0.bpo.6-amd64=4.19.67-2~bpo9+1 is available.

2019-10-04 Thread Markus Lindberg
Package: linux-headers-4.19.0-0.bpo.6-amd64 Version: 4.19.67-2~bpo9+1 Severity: important Dear Maintainer, I tried to install the linux-headers-4.19.0-0.bpo.6-amd64 package via stretch-backports but I was met with a unmet dependency. $ sudo apt install linux-headers-4.19.0-0.bpo.6-amd64 Reading

Bug#930447: nvidia-detect: [PATCH] Add option to only output package name if possible

2019-06-12 Thread Markus Lindberg
Package: nvidia-detect Version: 390.116-1 Severity: wishlist Dear Maintainer, The reason why I want to implement this option is to make it easier to parse the output if wanted. This is quite a big diff since it's was tricky to adapt the new option while not changing to much. Please let me know i

Bug#910087: nvidia-kernel-dkms: nvidia kernel module does not build against 4.18 kernel

2018-10-03 Thread Markus Lindberg
On Tue, 02 Oct 2018 16:28:14 +0100 Luca Boccassi wrote: > On Tue, 2018-10-02 at 15:23 +0000, Markus Lindberg wrote: > > On Tue, 02 Oct 2018 at 16:10 +0100, Luca Boccassi wrote: > > > 4.18 is not the kernel from Stretch. Either downgrade the kernel, > > > or > > &

Bug#910087: nvidia-kernel-dkms: nvidia kernel module does not build against 4.18 kernel

2018-10-02 Thread Markus Lindberg
On Tue, 02 Oct 2018 at 16:10 +0100, Luca Boccassi wrote: > 4.18 is not the kernel from Stretch. Either downgrade the kernel, or > upgrade the drivers to backports. Is installing nvidia-driver from stretch and the kernel from stretch-backports not supported? If I install the kernel from stretch-ba

Bug#910087: nvidia-kernel-dkms: nvidia kernel module does not build against 4.18 kernel

2018-10-02 Thread Markus Lindberg
Package: nvidia-kernel-dkms Version: 384.130-1 Severity: normal Dear Maintainer,    * What led up to the situation? I tried to install the nvidia-driver package.    * What exactly did you do (or not do) that was effective (or ineffective)? I ran the following command to install the nvidi

Bug#895819: [qnapomv.maxwellpreston.com] linux-headers-4.15.0-0.bpo.2-amd64: header package depends on version of linux-compiler-gcc-6-x86 not available in stretch backports

2018-04-19 Thread Markus Lindberg
On Mon, 16 Apr 2018 15:27:15 +0100 Ben Hutchings wrote: > The dependencies are all there. You need to use: > > # apt-get install -t stretch-backports linux-headers-4.15.0-0.bpo.2-amd64 > > Ben. > > -- > Ben Hutchings > Kids! Bringing about Armageddon can be dangerous. Do not attempt it > in your o

Bug#860897: dmidecode output information twice

2017-06-02 Thread Markus Lindberg
Hi Jörg, The 3.1 version you sent me are working perfectly. I don't experience any doubled output from the `dmidecode` command. Here is a transcript: # dpkg -l|grep "dmidecode" ii dmidecode 3.1-1amd64 SMBIOS/DMI table decoder # dmidecode -s bios-vend

Bug#837155: /usr/share/unattended-upgrades/unattended-upgrade-shutdown: may delay shutdown for 10 minutes if /var is already unmounted

2017-05-12 Thread Markus Lindberg
I also want to confirm that this fix works for me. It looks like the Ubuntu folks have the same fix in place. [1] [1] https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600 -- Markus

Bug#860897: dmidecode output information twice

2017-04-21 Thread Markus Lindberg
Package: dmidecode Version: 3.0-2~bpo8+1 When I invoke `dmidecode -s` and any viable argument I get the information output to me twice. Here is a transcript: # dmidecode -s bios-vendor American Megatrends Inc. American Megatrends Inc. # dmidecode -s processor-manufacturer Intel(R) Corporation

Bug#855024: Install nvidia-driver package from jessie-backports using different methods

2017-03-27 Thread Markus Lindberg
Could anyone at least point me in the right direction? -- Markus On Mon, 13 Feb 2017 11:50:40 + Luca Boccassi wrote: > Control: retitle -1 apt-get install / does not fetch dependencies from > Control: reassign -1 apt 1.0.9.8.4 > > On Mon, 2017-02-13 at 12:13 +0100, Mar

Bug#855024: Install nvidia-driver package from jessie-backports using different methods

2017-02-13 Thread Markus Lindberg
Package: nvidia-driver Version: 375.26-1~bpo8+1 I have tried two different methods to install the 'nvidia-driver' package from the 'jessie-backports' repository using 'apt-get' and only one method succeeds. As far as I know you can install a package from 'jessie-backports' by using two differe

Bug#838739: linux-image-amd64: meta depends on image not available

2016-09-27 Thread Markus Lindberg
' and 'linux-headers-amd64' we can see that the package's they depend on shows up as "Package not available". https://packages.debian.org/jessie-backports/linux-headers-amd64 https://packages.debian.org/jessie-backports/linux-image-amd64 Best regards Markus Lindberg