[opensuse-factory] Opensuse Tumbleweed with recent updates fails to connect the Intel Dual Band Wireless-AS 8265 interface
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 https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi 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 :
wmic bios get biosversion 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 https://bugzilla.opensuse.org/show_bug.cgi?id=1065127, 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. With best regards: Bill -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Foolish Ewe <foolishewe@hotmail.com> [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 https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi 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 :
wmic bios get biosversion 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 https://bugzilla.opensuse.org/show_bug.cgi?id=1065127, 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 http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Patrick: Your reply to my other issue (plasma session hanging after boot) suggested removing /usr/lib/systemd/user/sockets.target.wants/dbus.socket, this appears to alleviate this problem. I think the symptom I was seeing might have been kde and/or authentication related. 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/dhclient-wlo1.pid -lf /var/lib/NetworkManager/dhclient-b4d631d7-4ed8-4b80-aaae-1f59e19b5e29-wlo1.lease -cf /var/lib/NetworkMana With best regards: Bill From: Patrick Shanahan <ptilopteri@gmail.com> on behalf of Patrick Shanahan <paka@opensuse.org> Sent: Sunday, October 29, 2017 9:27 PM To: opensuse-factory@opensuse.org Subject: Re: [opensuse-factory] Opensuse Tumbleweed with recent updates fails to connect the Intel Dual Band Wireless-AS 8265 interface * Foolish Ewe <foolishewe@hotmail.com> [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 https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi 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] wireless.wiki.kernel.org iwlwifi is the wireless driver for Intel's current wireless chips. For older chips, there are other drivers:
wmic bios get biosversion 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 https://bugzilla.opensuse.org/show_bug.cgi?id=1065127, 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 http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/29/2017 04:11 PM, Foolish Ewe wrote:
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 https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi 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 :
wmic bios get biosversion 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 https://bugzilla.opensuse.org/show_bug.cgi?id=1065127, 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.
The output of the dmesg command would be helpful. As the size of it will be quite large, redirect it to a file with 'dmesg > dmesg.txt', and post dmesg.txt to some pastebin site. It will also be useful to post the output of 'lspci -nn'. That will be small enough to post here, although you may heed to redirect it in order to make it available under Windows. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Larry: I can't rule out that there may be some authentication issues, the plasma login screen is somewhat troubling, there are times where I'm not able to log in on my initial attempt, the first time I enter a correct password it hangs (incorrect passwords prompt for a retry). In any case after a scare this morning I was able to log in as root through plasma and then my personal login worked after I logged out and logged back in, and now my network comes up. The following information is available (small inputs are in the message, larger ones pastebin): uname -a returned: Linux localhost.localdomain 4.13.8-1-default #1 SMP PREEMPT Wed Oct 18 09:53:30 UTC 2017 (569e26e) x86_64 x86_64 x86_64 GNU/Linux lspci -nn returned: 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:5914] (rev 08) 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:5917] (rev 07) 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08) 00:13.0 Non-VGA unclassified device [0000]: Intel Corporation Sunrise Point-LP Integrated Sensor Hub [8086:9d35] (rev 21) 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21) 00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 [8086:9d60] (rev 21) 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 [8086:9d10] (rev f1) 00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 [8086:9d14] (rev f1) 00:1c.6 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #7 [8086:9d16] (rev f1) 00:1c.7 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #8 [8086:9d17] (rev f1) 00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 [8086:9d18] (rev f1) 00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:9d4e] (rev 21) 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21) 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21) 01:00.0 3D controller [0302]: NVIDIA Corporation GP108M [GeForce MX150] [10de:1d10] (rev a1) 3b:00.0 Network controller [0280]: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78) 3c:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader [10ec:525a] (rev 01) 3d:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 [144d:a804] dmesg at https://pastebin.com/BHDNy7B6 lsmod at https://pastebin.com/HFAY1h9N full lspci at https://pastebin.com/ay50p2qa From: Larry Finger <larry.finger@gmail.com> on behalf of Larry Finger <Larry.Finger@lwfinger.net> Sent: Monday, October 30, 2017 2:18 AM To: Foolish Ewe; opensuse-factory@opensuse.org Subject: Re: [opensuse-factory] Opensuse Tumbleweed with recent updates fails to connect the Intel Dual Band Wireless-AS 8265 interface On 10/29/2017 04:11 PM, Foolish Ewe wrote:
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 https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi 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] wireless.wiki.kernel.org iwlwifi is the wireless driver for Intel's current wireless chips. For older chips, there are other drivers:
wmic bios get biosversion 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 https://bugzilla.opensuse.org/show_bug.cgi?id=1065127, 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.
The output of the dmesg command would be helpful. As the size of it will be quite large, redirect it to a file with 'dmesg > dmesg.txt', and post dmesg.txt to some pastebin site. It will also be useful to post the output of 'lspci -nn'. That will be small enough to post here, although you may heed to redirect it in order to make it available under Windows. Larry Thanks: Bill -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/31/2017 10:37 AM, Foolish Ewe wrote:
Hi Larry:
I can't rule out that there may be some authentication issues, the plasma login screen is somewhat troubling, there are times where I'm not able to log in on my initial attempt, the first time I enter a correct password it hangs (incorrect passwords prompt for a retry). In any case after a scare this morning I was able to log in as root through plasma and then my personal login worked after I logged out and logged back in, and now my network comes up.
The following information is available (small inputs are in the message, larger ones pastebin):
uname -a returned: Linux localhost.localdomain 4.13.8-1-default #1 SMP PREEMPT Wed Oct 18 09:53:30 UTC 2017 (569e26e) x86_64 x86_64 x86_64 GNU/Linux
If the network works after a login as root followed by a login with your personal account, then there is nothing wrong with the wireless NIC code. Unfortunately, I cannot duplicate your results. My Intel 7260 works correctly from boot. When the device is failing, I have another command for you to run. Do 'iw list' and post that output. Once you do your login as root, etc. and the network is working, run the same command and post that output as well. Perhaps something will change. One other thing to try is switch network control to wicked using YaST=>System=>Network Settings. After you exit back to YaST, repeat the sequence and go back to NetworkManager. Perhaps that will replace some setting that was wrong after the update. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Foolish Ewe -
Larry Finger -
Patrick Shanahan