Wifi isn't identified for Ampak AP6212

Bug #1705921 reported by Nir schwartz
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less:
file.io/PkdSHh
---
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: i386
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA:
 country IL: DFS-ETSI
  (2402 - 2482 @ 40), (N/A, 20), (N/A)
  (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR
  (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS
CurrentDesktop: XFCE
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241
InstallationDate: Installed on 2017-04-06 (108 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
MachineType: Insyde BayTrail
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-27-generic N/A
 linux-backports-modules-4.10.0-27-generic N/A
 linux-firmware 1.157.11
RfKill:
 1: phy1: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: xenial
Uname: Linux 4.10.0-27-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/29/2014
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: DSO.00
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name
dmi.board.vendor: Type2 - Board Manufacturer
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: BayTrail
dmi.product.version: Type1 - TBD by OEM
dmi.sys.vendor: Insyde

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1705921/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Paul White (paulw2u)
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1705921

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Nir schwartz (eyenir) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected xenial
description: updated
Revision history for this message
Nir schwartz (eyenir) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Nir schwartz (eyenir) wrote : IwConfig.txt

apport information

Revision history for this message
Nir schwartz (eyenir) wrote : JournalErrors.txt

apport information

Revision history for this message
Nir schwartz (eyenir) wrote : Lspci.txt

apport information

Revision history for this message
Nir schwartz (eyenir) wrote : Lsusb.txt

apport information

Revision history for this message
Nir schwartz (eyenir) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Nir schwartz (eyenir) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Nir schwartz (eyenir) wrote : ProcEnviron.txt

apport information

Revision history for this message
Nir schwartz (eyenir) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Nir schwartz (eyenir) wrote : ProcModules.txt

apport information

Revision history for this message
Nir schwartz (eyenir) wrote : PulseList.txt

apport information

Revision history for this message
Nir schwartz (eyenir) wrote : UdevDb.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Nir schwartz (eyenir) wrote : WifiSyslog.txt

apport information

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc2

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
importance: Undecided → Medium
Nir schwartz (eyenir)
tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Revision history for this message
Nir schwartz (eyenir) wrote :

My architecture is i386 and not amd64. Do you have the kernel for my architecture?

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

i386 variant: http://people.canonical.com/~khfeng/lp1705921/i386/

Please note that i386 support on Ubuntu will be dropped eventually.

Revision history for this message
Nir schwartz (eyenir) wrote :

Still no connection.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please attach output of dmesg.

Revision history for this message
Nir schwartz (eyenir) wrote :

Attached.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Hmm, can you find the relevant part?
The message "Baytrail Audio Port: ASoC: no backend DAIs enabled for Baytrail Audio Port" flooded over the dmesg, so we don't know what really happened on ath9k.

Revision history for this message
Nir schwartz (eyenir) wrote :

Removed the alsa problem.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

There are too much messages are being snipped.
Please provide dmesg from beginning at boot: `journalctl -b -k`.
Also, please provide both message from the kernel I built and from mainline 4.12.

Revision history for this message
Nir schwartz (eyenir) wrote :

My mainline is 4.10. Is it o.k?

Revision history for this message
Nir schwartz (eyenir) wrote :

KHF

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

This is super weird - no ath9k messages in both dmesg.

Revision history for this message
Nir schwartz (eyenir) wrote : Re: [Bug 1705921] Re: Wifi isn't identified for Ampak AP6212
Download full text (3.2 KiB)

Yes. I think ath9k relates to an external wireless card I plugged to upload
these logs. What about brcmfmac? It does appear and allegedly it has to
correspond to the Ampak ap6212 (e.g.
http://linux-sunxi.org/Wifi#Ampak_Devices).

On Fri, Jul 28, 2017 at 10:21 AM Kai-Heng Feng <email address hidden>
wrote:

> This is super weird - no ath9k messages in both dmesg.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1705921
>
> Title:
> Wifi isn't identified for Ampak AP6212
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak
> AP6212 card (neither for wifi nor for bluetooth). Here is the output of
> dmesg |less:
> file.io/PkdSHh
> ---
> ApportVersion: 2.20.1-0ubuntu2.9
> Architecture: i386
> AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
> '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c',
> '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
> CRDA:
> country IL: DFS-ETSI
> (2402 - 2482 @ 40), (N/A, 20), (N/A)
> (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR
> (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS
> CurrentDesktop: XFCE
> DistroRelease: Ubuntu 16.04
> HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241
> InstallationDate: Installed on 2017-04-06 (108 days ago)
> InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386
> (20160719)
> MachineType: Insyde BayTrail
> Package: linux (not installed)
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic
> root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7
> ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
> RelatedPackageVersions:
> linux-restricted-modules-4.10.0-27-generic N/A
> linux-backports-modules-4.10.0-27-generic N/A
> linux-firmware 1.157.11
> RfKill:
> 1: phy1: Wireless LAN
> Soft blocked: no
> Hard blocked: no
> Tags: xenial
> Uname: Linux 4.10.0-27-generic i686
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> _MarkForUpload: True
> dmi.bios.date: 10/29/2014
> dmi.bios.vendor: INSYDE Corp.
> dmi.bios.version: DSO.00
> dmi.board.asset.tag: Type2 - Board Asset Tag
> dmi.board.name: Type2 - Board Product Name
> dmi.board.vendor: Type2 - Board Manufacturer
> dmi.board.version: Type2 - Board Version
> dmi.chassis.asset.tag: Chassis Asset Tag
> dmi.chassis.type: 10
> dmi.chassis.vendor: Chassis Manufacturer
> dmi.chassis.version: Chassis Version
> dmi.modalias:
> dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
> dmi.product.name: BayTrail
> dmi.product.version: Type1 - TBD by OEM
> dmi.sys.vendor: Insyde
>
> To manage notificat...

Read more...

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Hmm, so I was debugging the ath9k issue all the time.

Revision history for this message
Nir schwartz (eyenir) wrote :

Sorry for that. Do you have any idea about the brcmfmac?

On Fri, Jul 28, 2017 at 11:51 AM Kai-Heng Feng <email address hidden>
wrote:

> Hmm, so I was debugging the ath9k issue all the time.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1705921
>
> Title:
> Wifi isn't identified for Ampak AP6212
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak
> AP6212 card (neither for wifi nor for bluetooth). Here is the output of
> dmesg |less:
> file.io/PkdSHh
> ---
> ApportVersion: 2.20.1-0ubuntu2.9
> Architecture: i386
> AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
> '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c',
> '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
> CRDA:
> country IL: DFS-ETSI
> (2402 - 2482 @ 40), (N/A, 20), (N/A)
> (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR
> (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS
> CurrentDesktop: XFCE
> DistroRelease: Ubuntu 16.04
> HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241
> InstallationDate: Installed on 2017-04-06 (108 days ago)
> InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386
> (20160719)
> MachineType: Insyde BayTrail
> Package: linux (not installed)
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic
> root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7
> ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
> RelatedPackageVersions:
> linux-restricted-modules-4.10.0-27-generic N/A
> linux-backports-modules-4.10.0-27-generic N/A
> linux-firmware 1.157.11
> RfKill:
> 1: phy1: Wireless LAN
> Soft blocked: no
> Hard blocked: no
> Tags: xenial
> Uname: Linux 4.10.0-27-generic i686
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> _MarkForUpload: True
> dmi.bios.date: 10/29/2014
> dmi.bios.vendor: INSYDE Corp.
> dmi.bios.version: DSO.00
> dmi.board.asset.tag: Type2 - Board Asset Tag
> dmi.board.name: Type2 - Board Product Name
> dmi.board.vendor: Type2 - Board Manufacturer
> dmi.board.version: Type2 - Board Version
> dmi.chassis.asset.tag: Chassis Asset Tag
> dmi.chassis.type: 10
> dmi.chassis.vendor: Chassis Manufacturer
> dmi.chassis.version: Chassis Version
> dmi.modalias:
> dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
> dmi.product.name: BayTrail
> dmi.product.version: Type1 - TBD by OEM
> dmi.sys.vendor: Insyde
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+subscriptions
>

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Use 4.13-rc2 and boot with kernel parameter "brcmfmac.debug=1FFFFE". Attach the dmesg afterwards.

Revision history for this message
Nir schwartz (eyenir) wrote :

I didn't put the parameter in brackets. Hope it's fine.

Revision history for this message
Nir schwartz (eyenir) wrote :
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Tons of unrelated messages...

Revision history for this message
Nir schwartz (eyenir) wrote :

Checked it once again. The moment I add this parameter to the kernel it gives only the audio message. When I boot I get `1FFFFE is invalid for parameter debug`. Maybe it's related?

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Oops, it should be "0x1FFFFE" instead. Sorry.

Revision history for this message
Nir schwartz (eyenir) wrote :

I still get only the silly Audio Port error. Is there a way I can tell
dmesg to ignore it?

On Wed, Aug 2, 2017 at 10:31 AM Kai-Heng Feng <email address hidden>
wrote:

> Oops, it should be "0x1FFFFE" instead. Sorry.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1705921
>
> Title:
> Wifi isn't identified for Ampak AP6212
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak
> AP6212 card (neither for wifi nor for bluetooth). Here is the output of
> dmesg |less:
> file.io/PkdSHh
> ---
> ApportVersion: 2.20.1-0ubuntu2.9
> Architecture: i386
> AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
> '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c',
> '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
> CRDA:
> country IL: DFS-ETSI
> (2402 - 2482 @ 40), (N/A, 20), (N/A)
> (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR
> (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS
> CurrentDesktop: XFCE
> DistroRelease: Ubuntu 16.04
> HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241
> InstallationDate: Installed on 2017-04-06 (108 days ago)
> InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386
> (20160719)
> MachineType: Insyde BayTrail
> Package: linux (not installed)
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic
> root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7
> ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
> RelatedPackageVersions:
> linux-restricted-modules-4.10.0-27-generic N/A
> linux-backports-modules-4.10.0-27-generic N/A
> linux-firmware 1.157.11
> RfKill:
> 1: phy1: Wireless LAN
> Soft blocked: no
> Hard blocked: no
> Tags: xenial
> Uname: Linux 4.10.0-27-generic i686
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> _MarkForUpload: True
> dmi.bios.date: 10/29/2014
> dmi.bios.vendor: INSYDE Corp.
> dmi.bios.version: DSO.00
> dmi.board.asset.tag: Type2 - Board Asset Tag
> dmi.board.name: Type2 - Board Product Name
> dmi.board.vendor: Type2 - Board Manufacturer
> dmi.board.version: Type2 - Board Version
> dmi.chassis.asset.tag: Chassis Asset Tag
> dmi.chassis.type: 10
> dmi.chassis.vendor: Chassis Manufacturer
> dmi.chassis.version: Chassis Version
> dmi.modalias:
> dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
> dmi.product.name: BayTrail
> dmi.product.version: Type1 - TBD by OEM
> dmi.sys.vendor: Insyde
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+subscriptions
>

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

You can blacklist your audio kernel module.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.