From: Sven-Haegar Koch <haegar@sdinet.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Corentin Labbe <clabbe.montjoie@gmail.com>,
kvalo@kernel.org, linux-wireless@vger.kernel.org,
Linux-Kernel-Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: unknow Network controller: Intel Corporation Device 093c (rev 3a)
Date: Tue, 18 Feb 2025 11:36:22 +0100 (CET) [thread overview]
Message-ID: <8eb241a2-d8d7-f01c-c2ca-b615e8a1cc41@sdinet.de> (raw)
In-Reply-To: <6a5eb58c06cc1d5bdeb67fe877ef3a98520627ed.camel@sipsolutions.net>
On Tue, 18 Feb 2025, Johannes Berg wrote:
> On Mon, 2025-02-17 at 19:08 +0100, Corentin Labbe wrote:
> > The laptop is running Debian bookworm, and I tried to update pci.ids, no more information.
> >
> > lspci -vx give:
> > 03:00.0 Network controller: Intel Corporation Device 093c (rev 3a)
> > Subsystem: Intel Corporation Device 2181
>
> But that doesn't match at all, not even close.
>
> I cannot find any record for WiFi of these numbers, so either the device
> is not WiFi or is malfunctioning. You could try to open it up, take a
> picture so we can see what the WiFi NIC is, and also maybe re-seat the
> NIC while at is, occasionally that fixes such issues.
https://linux-hardware.org/?id=pci:8086-093c-8086-2181
Suggests it to be a "Intel Wireless Gigabit 17265", with no linux driver
existing for it.
c'ya
sven-haegar
--
Three may keep a secret, if two of them are dead.
- Ben F.
prev parent reply other threads:[~2025-02-18 10:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 18:08 unknow Network controller: Intel Corporation Device 093c (rev 3a) Corentin Labbe
2025-02-18 8:15 ` Johannes Berg
2025-02-18 10:36 ` Sven-Haegar Koch [this message]
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=8eb241a2-d8d7-f01c-c2ca-b615e8a1cc41@sdinet.de \
--to=haegar@sdinet.de \
--cc=clabbe.montjoie@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.