On Fri, 2017-02-17 at 22:30 +0100, g...@gazeta.pl wrote:
> On 17.02.2017 02:57, Ben Hutchings wrote:
> > This seems to be a bug in the device tree for the TS419 - it doesn't
> > quite match the board code it replaced. Should be easy to fix.
>
> After applying patch, eth1 is recognized, but it
On 17.02.2017 02:57, Ben Hutchings wrote:
> This seems to be a bug in the device tree for the TS419 - it doesn't
> quite match the board code it replaced. Should be easy to fix.
After applying patch, eth1 is recognized, but it behaves strange. It
looks like it is using a correct MAC during DHCP
Control: tag -1 upstream patch moreinfo
On Mon, Feb 13, 2017 at 11:07:03AM +0100, g...@gazeta.pl wrote:
[...]
> Upgrading of existing Debian from Jessie to Stretch on QNAP TS-419pII
> device, then booting into new kernel
>
>* What was the outcome of this action?
>
> eth1 is no longer
Related case:
https://lists.debian.org/debian-arm/2016/08/msg00049.html
Package: src:linux
Version: 4.9.6-3
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where
appropriate ***
* What led up to the situation?
Upgrading of existing Debian from Jessie to Stretch on QNAP TS-419pII
device, then booting into new kernel
5 matches
Mail list logo
