lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 11 Dec 2018 12:38:05 -0600
From:   Bjorn Helgaas <helgaas@...nel.org>
To:     "Grumbach, Emmanuel" <emmanuel.grumbach@...el.com>
Cc:     "bjorn@...gaas.com" <bjorn@...gaas.com>,
        "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
        "Mertarg10@...il.com" <Mertarg10@...il.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Fran RR <fjrr87@...look.com>
Subject: Re: Fwd: [Bug 201647] New: Intel Wireless card 3165 does not get
 detected but bluetooth works

On Tue, Dec 11, 2018 at 06:31:47PM +0000, Grumbach, Emmanuel wrote:
> > On Tue, Dec 11, 2018 at 04:32:25PM +0000, Grumbach, Emmanuel wrote:
> > > > On Tue, Dec 11, 2018 at 06:35:20AM +0000, Grumbach, Emmanuel wrote:
> > > > > > > > > https://bugzilla.kernel.org/show_bug.cgi?id=201647
> > > >
> > > > > FWIW: I saw another problem like this with a 9650 device.
> > > >
> > > > Do you have a pointer to any info about this 9650 issue?  Maybe that
> > > > would have a clue.
> > >
> > > I added him here so that you can ask whatever you like :) The story is
> > > the same. I am attaching a picture I got from the reporter.
> > > I can confirm that this device ID / subdevice ID is supported by the linux
> > driver.
> > 
> > Was there a resolution, i.e., if somebody figured out how to make the
> > 9650 wifi work, maybe a similar solution would work for the 3165?
> 
> Unfortunately not, I am stuck there at the exact same point.
> No Wifi device shows up in lspci...

Is there a public spec?  My patience for reverse engineering things
that are documented somewhere that I'm not allowed to see is pretty
limited.  Presumably *you* should be able to see the spec, since this
is an Intel device and you have an @intel.com address?

>From what we can tell so far, I don't *think* this is a PCI issue.  If
the device doesn't respond to a PCI config access, the PCI core can't
really be expected to do anything about it.

Bjorn

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ