Mailinglist Archive: opensuse-factory (824 mails)

< Previous Next >
Re: [opensuse-factory] Opensuse Tumbleweed with recent updates fails to connect the Intel Dual Band Wireless-AS 8265 interface
Hi Patrick:

Your reply to my other issue (plasma session hanging after boot) suggested
removing /usr/lib/systemd/user/, this appears
to alleviate this problem.

I think the symptom I was seeing might have been kde and/or authentication
The good news is that I have networking in Linux and am posting from an
OpenSuse login session.

You asked:

what is the output of:
systemctl status network

I'm not sure if it matters given the previous good news, but here it is:

systemctl status network
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: disabled)
Active: active (running) since Sun 2017-10-29 16:04:14 PDT; 28min ago
Docs: man:NetworkManager(8)
Main PID: 1275 (NetworkManager)
Tasks: 4 (limit: 4915)
CGroup: /system.slice/NetworkManager.service
├─1275 /usr/sbin/NetworkManager --no-daemon
└─2641 /sbin/dhclient -d -q -sf /usr/lib/nm-dhcp-helper -pf
/var/run/ -lf
-cf /var/lib/NetworkMana

With best regards:


From: Patrick Shanahan <ptilopteri@xxxxxxxxx> on behalf of Patrick Shanahan
Sent: Sunday, October 29, 2017 9:27 PM
To: opensuse-factory@xxxxxxxxxxxx
Subject: Re: [opensuse-factory] Opensuse Tumbleweed with recent updates fails
to connect the Intel Dual Band Wireless-AS 8265 interface
* Foolish Ewe <foolishewe@xxxxxxxxxxx> [10-29-17 17:13]:
Hello All:

I have a new laptop, model  HP Spectre x360 Convertible 15-bl1XX which
initially worked with OpenSuse Tumble Weed but appears to have lost all
network support for its Intel Dual Band Wireless-AC 8265 network hardware. 
This issue is my most urgent current issue, since I need to make a decision
soon to keep or return this laptop.

Leap supported the network device out of the box but updates broke it.  I
checked and I see
that I need a Linux kernel version 4.6+ for this driver, but leap is
currently on the 4.4 kernel version, so I took a chance on tumbleweed.  I
had tumbleweed up and running with good network support for a few days this
week, then did a big update one or 2 days ago, the networking was working and
suddenly stopped.   The Networks manager daemons appear to be up and running
as per yast but the kde network manager client won't show me available
networks or allow me to log in at all, I just see a red icon in my task bar
and when I click on it I see the networking is enabled, but no list of access
points, and not prompt from kwallet to login to my router.  I can't easily
report diagnostics without network access, I'm quite sad about this.   As far
as I can tell I'm on the most recent bios :

en:users:drivers:iwlwifi [Linux Wireless]
iwlwifi is the wireless driver for Intel's current wireless chips. For older
chips, there are other drivers:

wmic bios get biosversion
{"HPQOEM - 1072009", "F.20", "American Megatrends - 5000C"}

If there is a specific set of logs that I should retrieve, I can try to boot
back into Linux, but until this is fixed, I can only access the internet via
Windows 10.

I looked in Bugzilla and the most closely related report appears to be,  but, unlike Bug
1065127 in my case I don't have an initial connection period before the drop.

Any guidance or help is appreciated.  On a side note, I'm a bit new to the
journalctl log access, so a little guidance on how to select any requested
logs would also be appreciated.

what is the output of:
  systemctl status network

(paka)Patrick Shanahan       Plainfield, Indiana, USA          @ptilopteri    openSUSE Community Member    facebook/ptilopteri
Registered Linux User #207535                    @
Photos:                paka @ IRCnet freenode
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >