Return-path: Received: from mail-wg0-f50.google.com ([74.125.82.50]:61613 "EHLO mail-wg0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752057AbbAOVAx convert rfc822-to-8bit (ORCPT ); Thu, 15 Jan 2015 16:00:53 -0500 Received: by mail-wg0-f50.google.com with SMTP id a1so17226766wgh.9 for ; Thu, 15 Jan 2015 13:00:52 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <54B82598.9060403@erley.org> References: <54B82598.9060403@erley.org> From: Mike Purvis Date: Thu, 15 Jan 2015 16:00:32 -0500 Message-ID: (sfid-20150115_220057_447157_468DE39B) Subject: Re: Delivery Status Notification (Failure) To: Pat Erley Cc: linux-wireless@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi Pat, It's a good guess, but I don't think that's the case, in part because the 6235 is a 2x2 MIMO module— the antennas are MAIN/AUX, not WIFI/BT. I actually did encounter an Azurewave module which was set up that way, and both portions came up on the Gigabyte motherboard— I would have kept using that module, but there was a supply availability issue, the wifi performance was very poor, and I was interested in using a MIMO part. On 15 January 2015 at 15:39, Pat Erley wrote: > 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 >> >