Stretch: No wireless connection for kernel 4.14.0-0.bpo.2-am

[xanadu18]

Hello,

When I was using an 80211n wireless adapter, I was able to boot into the backport kernel 4.14.0-0.bpo.2-amd64.

However, when I install an 80211ac adapter such as Rosewill RNX-AC1900PCE adapter, which is a clone of TP-LINK T9E adapter to match my AC wireless router, I cannot boot into such kernel, since the adapter is not detected. I can only boot into an older kernel such as 4.9.0-5-amd64. I did install broadcom-wl-dkms in the older kernel.

Code: Select all

uname -r
4.9.0-5-amd64

Code: Select all

lspci -nnk

gives:

Code: Select all

2:00.0 Network controller [0280]: Broadcom Limited BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03)
        Subsystem: Broadcom Limited BCM4360 802.11ac Wireless Network Adapter [14e4:0619]
        Kernel driver in use: wl
        Kernel modules: bcma, wl

I would very much appreciate your suggestions.

[stevepusser]

Debian hasn't backported the upstream version yet that supports kernel 4.14 to stretch-backports. Someone needs to request that on their mailing list...just takes a few minutes to do, since I already did it for MX Linux. You need the -7 revision, not the -5.

Also ndiswrapper and virtual box need backports to build with the 4.14 kernel...and it has a missing dependency for the headers, libelf-dev, that these also need in order to build.

[xanadu18]

Hello stevepusser,

Thanks for your reply. I just upgraded to a new kernel 4.14.0-0.bpo.3-amd64. The upgrade went smoothly but I got the following in the terminal:

Code: Select all

Error! Bad return status for module build on kernel: 4.14.0-0.bpo.3-amd64 (x86_64)
Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log for more information.

Can you give me the link to the mailing list? Also another question:

Can I enable MX repo in the /etc/apt/sources.list as a temporary fix for broadcom-sta-dkms problem?

[stevepusser]

Hello stevepusser,

Thanks for your reply. I just upgraded to a new kernel 4.14.0-0.bpo.3-amd64. The upgrade went smoothly but I got the following in the terminal:

Code: Select all

Error! Bad return status for module build on kernel: 4.14.0-0.bpo.3-amd64 (x86_64)
Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log for more information.

Can you give me the link to the mailing list? Also another question:

Can I enable MX repo in the /etc/apt/sources.list as a temporary fix for broadcom-sta-dkms problem?

Yes, I sent emailed the list with your problem yesterday; no replies yet. https://lists.debian.org/debian-backpor ... reads.html

Yes, you can add the MX 17 repository to get the updated broadcom-sta packages. I build those particular packages in a generic Stretch pbuild environment, so they will be compatible.

[xanadu18]

Hello stevepusser,

The home page of MX Linux does not have any link to MX 17 repo, so I went to the link in your signature and copy the deb source for MX 16 repo but changed 16 to 17 before adding to my /etc/apt/sources.list file. After saving this file, and sudo apt-get update, this is what I got at the end:

Code: Select all

: The repository 'http://mxrepo.com/mx/repo mx17 Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch http://mxrepo.com/mx/repo/dists/mx17/main/binary-amd64/Packages  404  Not Found
E: Some index files failed to download. They have been ignored, or old ones used instead.

Any suggestions?

[xanadu18]

I finally am able to locate MX17 repo that's buried in MX Linux' wiki page (System Section).

I replaced "MX17" with "stretch" then saved the /etc/apt/sources.list file.

After apt-get updating and rebooting into kernel 4.14.0-0.bpo.3-amd64, I got wireless connection!

PROBLEM SOLVED! Thank you stevepusser!

[xanadu18]

Hi,

Wireless connection solved, but a different problem arose:

Code: Select all

sudo apt-get update && sudo apt-get upgrade

Code: Select all

...
Get:6 http://mxrepo.com/mx/repo stretch InRelease [8,130 B]              
Err:6 http://mxrepo.com/mx/repo stretch InRelease              
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D5A3F968F7CFCEED
Reading package lists... Done
W: GPG error: http://mxrepo.com/mx/repo stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D5A3F968F7CFCEED
E: The repository 'http://mxrepo.com/mx/repo stretch InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.

Any suggestions?

[stevepusser]

I would not go nuts and upgrade everything from the MX repository at once like you tried. Much better to do them one at a time.

But MX has a tool that works to find and install the missing keys most of the time... this one:

http://mxrepo.com/mx/repo/pool/main/c/checkaptgpg/

There is also the trick of inserting [trusted=yes] after the "deb" in the repo entry in your sources.list file to get rid of the need for keys altogether for that repo, but I don't recommend that.

[xanadu18]

Hello stevepusser,

At first the MX Tool in the link you gave requires installation of a package called "menu" to satisfy dependency requirements. After such installation, I still get the following:

Code: Select all

E: GPG error: http://mxrepo.com/mx/repo stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D5A3F968F7CFCEED
W: The repository 'http://mxrepo.com/mx/repo stretch InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.

For now, I just put a comment (#) sign in front of the MX repo deb before running "apt-get update".