Am 11.09.2017 um 21:41 schrieb Diego Roversi: > On Mon, 11 Sep 2017 19:36:46 +0200 > Oleksij Rempel <li...@rempel-privat.de> wrote: > >>> I didn't expected that a reboot was needed. I wonder if there is a way to >>> avoid to reboot. >> >> Suddenly not really. It is kind of compromise between bad and worse >> options. I hope it is not the worse one :) > > For me the bug can be closed, if it cannot be fixed. I have a suggestion: > could you explain the problem, so that the information is available to other > users? > > Thanks again, > Diego. >
There are fallowing issue which was needed to solve: - have tested "certified" binary firmware know to work (path 1) from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ - have different firmware versions on one system for regression testing (path 2). The reason: if firmware update will kill single usable netowrok interface it will be hard to roll back to working version. - have open source firmware compiled within debian build system (path 3) With kernel version v4.4 was added support for multiple firware paths in the ath9k-htc driver. One of paths was reserved for development FW version, which is not enabled by default. We have decided to use development FW name for debian package. In this case it will not conflict with stable/tested FW version. So the debian package is providing modprobe config which is setting use_dev_fw flag. To make this flag work, we need to reload ath9k-htc module or reboot the system. -- Regards, Oleksij
signature.asc
Description: OpenPGP digital signature
