linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pat Erley <pat-lkml@erley.org>
To: Mike Purvis <mpurvis@clearpathrobotics.com>,
	linux-wireless@vger.kernel.org
Subject: Re: Delivery Status Notification (Failure)
Date: Thu, 15 Jan 2015 14:39:52 -0600	[thread overview]
Message-ID: <54B82598.9060403@erley.org> (raw)
In-Reply-To: <CACsJT9M9LcHEuEa2mgAB2taYATZq4j_NeLq78w+=-VBvOw1NGw@mail.gmail.com>

On 01/15/2015 01:34 PM, Mike Purvis wrote:
> I'm having an issue with the Centrino Advanced-N 6235 module. I'm running
> Ubuntu Trusty, and I've tried both the 3.13 and 3.16 kernels. Haven't yet
> tried 3.18.
>
> What's weirdest about it is that the module actually works with full
> functionality on an Advantech AIMB-274 (Q87 chipset) with the described
> software configuration. However, when I plug the module into either a Gigabyte
> J1800N or an ASRock IMB-152 (J1900), I get no bluetooth— no hci0 device
> comes up at all in hciconfig dev or rfkill list.

I'd guess that the 6235 module has WLAN on the pci-e connector portion,
and Bluetooth on the USB portion.  Check the docs on the board you're
plugging it into, and I bet the mini-pcie connector doesn't have the
USB side wired up, or it's disabled in(or by) the bios?

>
> My sense is that the 6235 is a very popular module, and low-cost celeron
> motherboards are also pretty popular, so there must be others who have run
> into this. Maybe people just don't use bluetooth, or don't expect it to
> work on Linux?
>
> Anyhow, here is a gist with the dmesg boot log and lshw output:
>
> https://gist.github.com/mikepurvis/ee7bc8fb85ff7ae64a9d
>
> Looks like there's a crash in there related to intel integrated graphics—
> could this be a cause? This is a headless machine, so disabling graphics
> completely is on the table, if someone can suggest a good way to go
> about that. Any other ideas as to what's going on here?
>
> Thanks muchly.
>
>   --
> Mike Purvis | Clearpath Robotics, Inc.
> 1425 Strasburg Road, Unit 2A , Kitchener, Ontario, N2R 1H2
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


  reply	other threads:[~2015-01-15 20:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACsJT9OOBcYNhNG6=+Q2EE4VHEvJ8_rJ3fr6gb9_3P4KpPPX3g@mail.gmail.com>
     [not found] ` <f46d043c061e8dd5c9050cb5990c@google.com>
2015-01-15 19:34   ` Delivery Status Notification (Failure) Mike Purvis
2015-01-15 20:39     ` Pat Erley [this message]
2015-01-15 21:00       ` Mike Purvis
2015-01-15 21:07         ` Pat Erley
2015-01-15 21:13       ` Johannes Berg
2015-01-16 14:30         ` Mike Purvis
     [not found] <CAP1NbjmewVTQ6KbY7fkgdhJ6iMSg0tO9g1P6Usymi3EmfmVA8w@mail.gmail.com>
     [not found] ` <089e010d935cc850e4052a580ec2@google.com>
2016-01-27 22:25   ` André Vitor
     [not found] <AANLkTi=+0BOUaTs73jRMnJ=9qyNkqnBvMuKVTG4od9_+@mail.gmail.com>
     [not found] ` <0022152d6729673f6a0494b1f2e6@google.com>
2010-11-10 12:25   ` miloofr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54B82598.9060403@erley.org \
    --to=pat-lkml@erley.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mpurvis@clearpathrobotics.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).