Last night, several packages were updated on my ThinkPad E520. Today, I see I no longer have a network manager nor WiFi. Was there a package that might have caused this? Any idea on how I can restore network manager? tnx jk BTW, WiFi still works in Windows 10, so it's not a hardware issue.
Forgot to mention, this is on openSUSE 15.4. On 2023-01-10 14:33, James Knott wrote:
Last night, several packages were updated on my ThinkPad E520. Today, I see I no longer have a network manager nor WiFi. Was there a package that might have caused this? Any idea on how I can restore network manager?
tnx jk
BTW, WiFi still works in Windows 10, so it's not a hardware issue.
* James Knott <james.knott@jknott.net> [01-10-23 14:36]:
Forgot to mention, this is on openSUSE 15.4.
On 2023-01-10 14:33, James Knott wrote:
Last night, several packages were updated on my ThinkPad E520. Today, I see I no longer have a network manager nor WiFi. Was there a package that might have caused this? Any idea on how I can restore network manager?
tnx jk
BTW, WiFi still works in Windows 10, so it's not a hardware issue.
rpm -qa --last | grep <date of update> | sort will provide you with the updated packages that you might determine which affected your networking. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On 1/10/23 14:57, Patrick Shanahan wrote:
* James Knott<james.knott@jknott.net> [01-10-23 14:36]:
Forgot to mention, this is on openSUSE 15.4.
On 2023-01-10 14:33, James Knott wrote:
Last night, several packages were updated on my ThinkPad E520. Today, I see I no longer have a network manager nor WiFi. Was there a package that might have caused this? Any idea on how I can restore network manager?
tnx jk
BTW, WiFi still works in Windows 10, so it's not a hardware issue.
rpm -qa --last | grep <date of update> | sort
will provide you with the updated packages that you might determine which affected your networking.
Had the same issue recently, turned out to be an issue with Windows 10 fast boot. I turned off fast startup and my Wi-Fi was back in openSuse.
On 2023-01-10 15:00, Michael Harnden wrote:
Had the same issue recently, turned out to be an issue with Windows 10 fast boot. I turned off fast startup and my Wi-Fi was back in openSuse.
Fast boot isn't enabled. I turned it off years ago for other reasons. Also, I made a mistake. Network manager is there, but WiFi isn't listed. There should be several connections listed, as there is for Ethernet. If I go into settings, I can see the WiFi connections. So, it's just WiFi connections are not listed and WiFi does not automatically connect when there is no Ethernet connection and I can't connect manually.
On 10/01/2023 21:21, James Knott wrote:
On 2023-01-10 15:00, Michael Harnden wrote:
Had the same issue recently, turned out to be an issue with Windows 10 fast boot. I turned off fast startup and my Wi-Fi was back in openSuse.
Fast boot isn't enabled. I turned it off years ago for other reasons. Also, I made a mistake. Network manager is there, but WiFi isn't listed. There should be several connections listed, as there is for Ethernet. If I go into settings, I can see the WiFi connections.
So, it's just WiFi connections are not listed and WiFi does not automatically connect when there is no Ethernet connection and I can't connect manually.
Not sure if I follow correctly, but if you can see the wifi connections listed in KDE System Settings > Connections, and they're not showing up in the Network Manager system tray popup, might it be just that you've unticked the wireless box within that popup? And for the same reason, wifi wouldn't connect automatically if there's no ethernet. gumb
On 2023-01-10 16:31, gumb wrote:
Not sure if I follow correctly, but if you can see the wifi connections listed in KDE System Settings > Connections, and they're not showing up in the Network Manager system tray popup, might it be just that you've unticked the wireless box within that popup? And for the same reason, wifi wouldn't connect automatically if there's no ethernet.
Where is that button? I don't recall seeing it and don't see it now.
On 10/01/2023 22:38, James Knott wrote:
On 2023-01-10 16:31, gumb wrote:
Not sure if I follow correctly, but if you can see the wifi connections listed in KDE System Settings > Connections, and they're not showing up in the Network Manager system tray popup, might it be just that you've unticked the wireless box within that popup? And for the same reason, wifi wouldn't connect automatically if there's no ethernet.
Where is that button? I don't recall seeing it and don't see it now.
I think if you're not seeing it there must be something else amiss. When you click the standard 'Networks' popup in the system tray, underneath the word 'Networks' at the top of the popup I have a check box with a wifi symbol next to it. Next to that there's another one for airplane mode, and then a Hotspot button. All on Leap 15.4. Otherwise, in the list of wifi connections in System Settings, if you click on one, then look under the 'Wi-Fi' tab on the right pane, you don't by any chance have the Visibility check box ticked, making it a hidden network? Obviously you wouldn't have done that deliberately but maybe the config has somehow become corrupted.
On 2023-01-10 18:36, gumb wrote:
Where is that button? I don't recall seeing it and don't see it now.
I think if you're not seeing it there must be something else amiss. When you click the standard 'Networks' popup in the system tray, underneath the word 'Networks' at the top of the popup I have a check box with a wifi symbol next to it. Next to that there's another one for airplane mode, and then a Hotspot button. All on Leap 15.4.
Below "Networks", I see my first Ethernet connection, which is DHCP. Nothing else.
Otherwise, in the list of wifi connections in System Settings, if you click on one, then look under the 'Wi-Fi' tab on the right pane, you don't by any chance have the Visibility check box ticked, making it a hidden network? Obviously you wouldn't have done that deliberately but maybe the config has somehow become corrupted.
No, it's not checked.
On 2023-01-10 18:36, gumb wrote:
I think if you're not seeing it there must be something else amiss. When you click the standard 'Networks' popup in the system tray, underneath the word 'Networks' at the top of the popup I have a check box with a wifi symbol next to it. Next to that there's another one for airplane mode, and then a Hotspot button. All on Leap 15.4.
Otherwise, in the list of wifi connections in System Settings, if you click on one, then look under the 'Wi-Fi' tab on the right pane, you don't by any chance have the Visibility check box ticked, making it a hidden network? Obviously you wouldn't have done that deliberately but maybe the config has somehow become corrupted.
I think we may be heading in the wrong direction with Network Manager. As I mentioned in another note, the WiFi NIC doesn't even show up with ifconfig or ip commands, though it does if I boot a rescue system.
On Tue, 2023-01-10 at 19:11 -0500, James Knott wrote:
On 2023-01-10 18:36, gumb wrote:
I think if you're not seeing it there must be something else amiss. When you click the standard 'Networks' popup in the system tray, underneath the word 'Networks' at the top of the popup I have a check box with a wifi symbol next to it. Next to that there's another one for airplane mode, and then a Hotspot button. All on Leap 15.4.
Otherwise, in the list of wifi connections in System Settings, if you click on one, then look under the 'Wi-Fi' tab on the right pane, you don't by any chance have the Visibility check box ticked, making it a hidden network? Obviously you wouldn't have done that deliberately but maybe the config has somehow become corrupted.
I think we may be heading in the wrong direction with Network Manager. As I mentioned in another note, the WiFi NIC doesn't even show up with ifconfig or ip commands, though it does if I boot a rescue system.
That really reads like a missing driver; can you verify what driver is in use for the card when you boot a rescue system and ensure the non-rescue system has the same driver available and loaded? I was working w/ a new RTL8852au adapter last night and was sad to see NOTHING displayed for it via `ip a` until I google searched a few things based off the model name and happened upon Larry's work for that driver. Now things are working as they should after a few commands 👍️ -- ~ Scott Bradnick |- Windows Subsystem for Linux (WSL) Developer |-- Tumbleweed: |--- Dell Precision 5540 [NVIDIA Quadro T1000] (x86_64) |--- O-DROID H2+ [UHD Graphics 600] (x86_64) |--- IceWhale ZimaBoard 832 [Intel HD Graphics 500] (x86_64) |--- 2x Raspberry Pi 4 Model B Rev 1.2 (aarch64) |--- 1x Raspberry Pi 3 Model B Rev 1.2 (aarch64) |--- WinBook TW100 (x86_64) https://keys.openpgp.org/ :: DBC5AA9A2D2BAEBC
On 2023-01-10 19:22, Scott Bradnick wrote:
I think we may be heading in the wrong direction with Network Manager. As I mentioned in another note, the WiFi NIC doesn't even show up with ifconfig or ip commands, though it does if I boot a rescue system.
That really reads like a missing driver; can you verify what driver is in use for the card when you boot a rescue system and ensure the non-rescue system has the same driver available and loaded?
I was working w/ a new RTL8852au adapter last night and was sad to see NOTHING displayed for it via `ip a` until I google searched a few things based off the model name and happened upon Larry's work for that driver. Now things are working as they should after a few commands 👍️
It's a Realtek RTL8188CE. One thing I just noticed, under Drivers, "Active No" & "modprobe Yes".
On 2023-01-10 21:01, James Knott wrote:
I was working w/ a new RTL8852au adapter last night and was sad to see NOTHING displayed for it via `ip a` until I google searched a few things based off the model name and happened upon Larry's work for that driver. Now things are working as they should after a few commands 👍️
It's a Realtek RTL8188CE. One thing I just noticed, under Drivers, "Active No" & "modprobe Yes".
I just tried this: # lsmod|grep realtek realtek 36864 1 libphy 159744 3 r8169,mdio_devres,realtek It shows the Ethernet NIC, but not WiFi.
On Wed, 2023-01-11 at 10:23 -0500, James Knott wrote:
On 2023-01-10 21:01, James Knott wrote:
I was working w/ a new RTL8852au adapter last night and was sad to see NOTHING displayed for it via `ip a` until I google searched a few things based off the model name and happened upon Larry's work for that driver. Now things are working as they should after a few commands 👍️
It's a Realtek RTL8188CE. One thing I just noticed, under Drivers, "Active No" & "modprobe Yes".
I just tried this:
# lsmod|grep realtek realtek 36864 1 libphy 159744 3 r8169,mdio_devres,realtek
It shows the Ethernet NIC, but not WiFi.
I'm not sure that's the best method, which isn't your fault - it seems like driver names are only _known_ once you already know them. I'd suggest something like: `inix --network` or `inxi --network-advanced`. In my case it reports as rtl8852au but lsmod is valid for 8852au ; same goes for modinfo. Frustrating that you basically need to know the answer to find the answer 😑️. So if you can verify the driver in use under rescue, maybe you can probe the system to find out why it's not being loaded outside of rescue. I can't guarantee this is [any part of] your issue, but the fact that no device is even listed reeks of a missing/unloaded driver. -- ~ Scott Bradnick |- Windows Subsystem for Linux (WSL) Developer |-- Tumbleweed: |--- Dell Precision 5540 [NVIDIA Quadro T1000] (x86_64) |--- O-DROID H2+ [UHD Graphics 600] (x86_64) |--- IceWhale ZimaBoard 832 [Intel HD Graphics 500] (x86_64) |--- 2x Raspberry Pi 4 Model B Rev 1.2 (aarch64) |--- 1x Raspberry Pi 3 Model B Rev 1.2 (aarch64) |--- WinBook TW100 (x86_64) https://keys.openpgp.org/ :: DBC5AA9A2D2BAEBC
On 2023-01-11 11:23, Scott Bradnick wrote:
I'd suggest something like: `inix --network` or `inxi --network-advanced`. In my case it reports as rtl8852au but lsmod is valid for 8852au ; same goes for modinfo. Frustrating that you basically need to know the answer to find the answer 😑️. So if you can verify the driver in use under rescue, maybe you can probe the system to find out why it's not being loaded outside of rescue. #inxi --network-advanced Network: Device-1:Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver:r8169 IF:eth0 state:up speed:1000 Mbps duplex:full mac:f0:de:f1:8c:dc:99 Device-2:Realtek RTL8188CE 802.11b/g/n WiFi Adapter driver:N/A
That lsmod command should have included both network drivers, but only Ethernet appeared.
On 2023-01-11 18:52, James Knott wrote:
On 2023-01-11 11:23, Scott Bradnick wrote:
I'd suggest something like: `inix --network` or `inxi --network-advanced`. In my case it reports as rtl8852au but lsmod is valid for 8852au ; same goes for modinfo. Frustrating that you basically need to know the answer to find the answer 😑️. So if you can verify the driver in use under rescue, maybe you can probe the system to find out why it's not being loaded outside of rescue. #inxi --network-advanced Network: Device-1:Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver:r8169 IF:eth0 state:up speed:1000 Mbps duplex:full mac:f0:de:f1:8c:dc:99 Device-2:Realtek RTL8188CE 802.11b/g/n WiFi Adapter driver:N/A
That lsmod command should have included both network drivers, but only Ethernet appeared.
You can try that inxi command under the rescue system to find out the exact name of the wifi driver. The xfce rescue image, when installed on an USB stick, is r/w and you can install inxi on it if it is not already there. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2023-01-11 13:49, Carlos E. R. wrote:
You can try that inxi command under the rescue system to find out the exact name of the wifi driver.
The xfce rescue image, when installed on an USB stick, is r/w and you can install inxi on it if it is not already there.
I've been using the rescue system from the install USB stick. Inxi is not on it.
James Knott composed on 2023-01-11 14:03 (UTC-0500):
I've been using the rescue system from the install USB stick. Inxi is not on it.
The following will enable inxi use if the wired connection is up and DNS is working: md /usr/local/bin && cd /usr/local/bin && wget -O inxi smxi.org/inxi && chmod +x inxi https://smxi.org/docs/inxi-installation.htm#inxi-manual-install --no-check-certificate may needed as another wget option. Tested with current TW NET installer's rescue mode. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 2023-01-11 13:49, Carlos E. R. wrote:
You can try that inxi command under the rescue system to find out the exact name of the wifi driver.
The xfce rescue image, when installed on an USB stick, is r/w and you can install inxi on it if it is not already there.
I have a 15.0 rescue USB stick and added inxi to it. It shows the Wifi driver as rtl8192ce Network: Card-1: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: f0:de:f1:8c:dc:99 Card-2: Realtek RTL8188CE 802.11b/g/n WiFi Adapter driver: rtl8192ce IF: wlan1 state: down mac: 38:59:f9:e0:7d:5d
On 2023-01-11 20:35, James Knott wrote:
On 2023-01-11 13:49, Carlos E. R. wrote:
You can try that inxi command under the rescue system to find out the exact name of the wifi driver.
The xfce rescue image, when installed on an USB stick, is r/w and you can install inxi on it if it is not already there.
I have a 15.0 rescue USB stick and added inxi to it. It shows the Wifi driver as rtl8192ce
Network: Card-1: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller driver: r8169 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: f0:de:f1:8c:dc:99 Card-2: Realtek RTL8188CE 802.11b/g/n WiFi Adapter driver: rtl8192ce IF: wlan1 state: down mac: 38:59:f9:e0:7d:5d Ok, then you can try to modprobe that module in 15.4.
-- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2023-01-11 14:55, Carlos E. R. wrote:
Ok, then you can try to modprobe that module in 15.4.
#modprobe rtl8192ce modprobe: ERROR: module 'rtlwifi' is unsupported modprobe: ERROR: Use --allow-unsupported or set allow_unsupported_modules 1 in modprobe: ERROR: /etc/modprobe.d/10-unsupported-modules.conf modprobe: ERROR: could not insert 'rtl8192ce': Operation not permitted
On 2023-01-11 21:01, James Knott wrote:
On 2023-01-11 14:55, Carlos E. R. wrote:
Ok, then you can try to modprobe that module in 15.4.
#modprobe rtl8192ce modprobe: ERROR: module 'rtlwifi' is unsupported modprobe: ERROR: Use --allow-unsupported or set allow_unsupported_modules 1 in modprobe: ERROR: /etc/modprobe.d/10-unsupported-modules.conf modprobe: ERROR: could not insert 'rtl8192ce': Operation not permitted
Well, did you try --allow-unsupported ? -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
* James Knott <james.knott@jknott.net> [01-11-23 15:25]:
On 2023-01-11 15:05, Carlos E. R. wrote:
Well, did you try --allow-unsupported ?
That gets Wifi going, but it doesn't survive a reboot.
perhaps using yast, add to boot command line ???? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On 2023-01-11 16:24, Patrick Shanahan wrote:
That gets Wifi going, but it doesn't survive a reboot. perhaps using yast, add to boot command line ????
I was thinking about something like that, but would prefer to know what the problem is and fix it. If I have to resort to it, I suppose I could use the autostart in Desktop settings.
On Wed, 2023-01-11 at 16:33 -0500, James Knott wrote:
On 2023-01-11 16:24, Patrick Shanahan wrote:
That gets Wifi going, but it doesn't survive a reboot. perhaps using yast, add to boot command line ????
I was thinking about something like that, but would prefer to know what the problem is and fix it. If I have to resort to it, I suppose I could use the autostart in Desktop settings.
There's a good chance the system already told you what to do 😉️
modprobe: ERROR: Use --allow-unsupported or set allow_unsupported_modules 1 in modprobe: ERROR: /etc/modprobe.d/10-unsupported-modules.conf
So edit/add a /etc/modprobe.d/10-unsupported-modules.conf file and put "allow_unsupported_modules 1" inside it. -- ~ Scott Bradnick |- Windows Subsystem for Linux (WSL) Developer |-- Tumbleweed: |--- Dell Precision 5540 [NVIDIA Quadro T1000] (x86_64) |--- O-DROID H2+ [UHD Graphics 600] (x86_64) |--- IceWhale ZimaBoard 832 [Intel HD Graphics 500] (x86_64) |--- 2x Raspberry Pi 4 Model B Rev 1.2 (aarch64) |--- 1x Raspberry Pi 3 Model B Rev 1.2 (aarch64) |--- WinBook TW100 (x86_64) https://keys.openpgp.org/ :: DBC5AA9A2D2BAEBC
On 2023-01-11 16:37, Scott Bradnick wrote:
So edit/add a /etc/modprobe.d/10-unsupported-modules.conf file and put "allow_unsupported_modules 1" inside it.
That did it, but something weird happened. My desktop is dim. As the computer boots, the brightness is normal, then it gets dim before the desktop starts, to the point of being almost unusable. I wonder what changed to require adding that file.
On 2023-01-11 22:58, James Knott wrote:
On 2023-01-11 16:37, Scott Bradnick wrote:
So edit/add a /etc/modprobe.d/10-unsupported-modules.conf file and put "allow_unsupported_modules 1" inside it.
That did it, but something weird happened. My desktop is dim. As the computer boots, the brightness is normal, then it gets dim before the desktop starts, to the point of being almost unusable.
Maybe there is a way to allow unsupported for this module only. :-? Yes. Try a file like: /etc/modprobe.d/10-my-unsupported-modules.conf: options rtl8192ce allow_unsupported=1
I wonder what changed to require adding that file.
Ask in Bugzilla. Some decision was taken to no longer support that module for some reason. Why this happened in the middle of Leap 15.4 life. I grepped the mail lists since 2021-04 till now and there is no mention of rtl8192ce Google: https://wireless.wiki.kernel.org/en/users/drivers/rtl819x -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2023-01-11 17:43, Carlos E. R. wrote:
That did it, but something weird happened. My desktop is dim. As the computer boots, the brightness is normal, then it gets dim before the desktop starts, to the point of being almost unusable.
Maybe there is a way to allow unsupported for this module only. :-? Yes. Try a file like:
/etc/modprobe.d/10-my-unsupported-modules.conf:
options rtl8192ce allow_unsupported=1
The first one appears to work fine. As for the brightness, I had to use the keyboard buttons to bring it up again so all is fine. It makes me wonder when that setting is set, as changing it didn't appear to affect the screens before login and didn't affect Windows either.
On 2023-01-12 00:20, James Knott wrote:
On 2023-01-11 17:43, Carlos E. R. wrote:
That did it, but something weird happened. My desktop is dim. As the computer boots, the brightness is normal, then it gets dim before the desktop starts, to the point of being almost unusable.
Maybe there is a way to allow unsupported for this module only. :-? Yes. Try a file like:
/etc/modprobe.d/10-my-unsupported-modules.conf:
options rtl8192ce allow_unsupported=1
The first one appears to work fine. As for the brightness, I had to use the keyboard buttons to bring it up again so all is fine. It makes me wonder when that setting is set, as changing it didn't appear to affect the screens before login and didn't affect Windows either.
Then remember to use only: options rtl8192ce allow_unsupported=1 and delete the generic line: allow_unsupported_modules 1 -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 11.01.2023 20:52, James Knott wrote:
On 2023-01-11 11:23, Scott Bradnick wrote:
I'd suggest something like: `inix --network` or `inxi --network-advanced`. In my case it reports as rtl8852au but lsmod is valid for 8852au ; same goes for modinfo. Frustrating that you basically need to know the answer to find the answer 😑️. So if you can verify the driver in use under rescue, maybe you can probe the system to find out why it's not being loaded outside of rescue. #inxi --network-advanced Network: Device-1:Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver:r8169 IF:eth0 state:up speed:1000 Mbps duplex:full mac:f0:de:f1:8c:dc:99 Device-2:Realtek RTL8188CE 802.11b/g/n WiFi Adapter driver:N/A
That lsmod command should have included both network drivers, but only Ethernet appeared.
I wonder when you are going to finally show dmesg output. You seriously believe that repeatedly posting "it does not work, it does not work" is going anywhere?
On 2023-01-11 14:14, Andrei Borzenkov wrote:
I wonder when you are going to finally show dmesg output. You seriously believe that repeatedly posting "it does not work, it does not work" is going anywhere?
When I run dmesg and grep on the driver name, I get this for the Ethernet driver: E520:~ #dmesg|grep r8169 [ 8.191415] r81690000:02:00.0: can't disable ASPM; OS doesn't have ASPM control [ 8.202975] libphy: r8169: probed [ 8.203572] r81690000:02:00.0 eth0: RTL8168e/8111e, f0:de:f1:8c:dc:99, XID 2c2, IRQ 27 [ 8.203579] r81690000:02:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko] [ 10.956226] RTL8211DN Gigabit Ethernet r8169-0-200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-200:00, irq= As you can see, there is info on it. However, when I try for WiFi: #dmesg|grep 8192 [ 0.036668] setup_percpu: NR_CPUS:8192nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1 [ 0.038908] percpu: Embedded 63 pages/cpu s221184 r8192d28672 u262144 [ 0.038921] pcpu-alloc: s221184 r8192d28672 u262144 alloc=1*2097152 [ 0.141669] rcu: RCU restricting CPUs from NR_CPUS=8192to nr_cpu_ids=8. [ 0.827238] MPTCP token hash table entries: 8192(order: 5, 196608 bytes, linear) There doesn't appear to be anything related.
On Wed, 2023-01-11 at 14:42 -0500, James Knott wrote:
On 2023-01-11 14:14, Andrei Borzenkov wrote:
I wonder when you are going to finally show dmesg output. You seriously believe that repeatedly posting "it does not work, it does not work" is going anywhere?
When I run dmesg and grep on the driver name, I get this for the Ethernet driver:
E520:~ #dmesg|grep r8169 [ 8.191415] r81690000:02:00.0: can't disable ASPM; OS doesn't have ASPM control [ 8.202975] libphy: r8169: probed [ 8.203572] r81690000:02:00.0 eth0: RTL8168e/8111e, f0:de:f1:8c:dc:99, XID 2c2, IRQ 27 [ 8.203579] r81690000:02:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko] [ 10.956226] RTL8211DN Gigabit Ethernet r8169-0-200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-200:00, irq=
As you can see, there is info on it.
However, when I try for WiFi: #dmesg|grep 8192 [ 0.036668] setup_percpu: NR_CPUS:8192nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1 [ 0.038908] percpu: Embedded 63 pages/cpu s221184 r8192d28672 u262144 [ 0.038921] pcpu-alloc: s221184 r8192d28672 u262144 alloc=1*2097152 [ 0.141669] rcu: RCU restricting CPUs from NR_CPUS=8192to nr_cpu_ids=8. [ 0.827238] MPTCP token hash table entries: 8192(order: 5, 196608 bytes, linear)
There doesn't appear to be anything related.
Can you run: `sudo modinfo rtl8192ce` or `sudo modprobe rtl8192ce` and get any positive results? My system (which is TW), doesn't use that particular driver, but has: /usr/lib/modules/$(uname - r)/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8192ce/rtl8192ce.ko.zst So it should come from the kernel-default package; maybe there was some type of hiccup on an update? I do have to run `sudo depmod -a $(uname -r)` [initially] when I build the 8852au driver before the kernel will load it in. -- ~ Scott Bradnick |- Windows Subsystem for Linux (WSL) Developer |-- Tumbleweed: |--- Dell Precision 5540 [NVIDIA Quadro T1000] (x86_64) |--- O-DROID H2+ [UHD Graphics 600] (x86_64) |--- IceWhale ZimaBoard 832 [Intel HD Graphics 500] (x86_64) |--- 2x Raspberry Pi 4 Model B Rev 1.2 (aarch64) |--- 1x Raspberry Pi 3 Model B Rev 1.2 (aarch64) |--- WinBook TW100 (x86_64) https://keys.openpgp.org/ :: DBC5AA9A2D2BAEBC
On 2023-01-11 14:56, Scott Bradnick wrote:
Can you run: `sudo modinfo rtl8192ce` or `sudo modprobe rtl8192ce` and get any positive results? My system (which is TW), doesn't use that particular driver, but has: #modprobe rtl8192ce modprobe: ERROR: module 'rtlwifi' is unsupported modprobe: ERROR: Use --allow-unsupported or set allow_unsupported_modules 1 in modprobe: ERROR: /etc/modprobe.d/10-unsupported-modules.conf modprobe: ERROR: could not insert 'rtl8192ce': Operation not permitted
#modinfo rtl8192ce filename: /lib/modules/5.14.21-150400.24.38-default/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8192ce/rtl8 192ce.ko.zst firmware: rtlwifi/rtl8192cfwU_B.bin firmware: rtlwifi/rtl8192cfwU.bin firmware: rtlwifi/rtl8192cfw.bin description: Realtek 8192C/8188C 802.11n PCI wireless license: GPL author: Larry Finger <Larry.Finger@lwfinger.net> author: Realtek WlanFAE <wlanfae@realtek.com> author: lizhaoming <chaoming_li@realsil.com.cn> suserelease: SLE15-SP4 srcversion: 8E59884EB0C2C23602E4E3A alias: pci:v000010ECd00008176sv*sd*bc*sc*i* alias: pci:v000010ECd00008177sv*sd*bc*sc*i* alias: pci:v000010ECd00008178sv*sd*bc*sc*i* alias: pci:v000010ECd00008191sv*sd*bc*sc*i* depends: rtlwifi,rtl_pci,rtl8192c-common,mac80211 supported: no retpoline: Y intree: Y name: rtl8192ce vermagic: 5.14.21-150400.24.38-default SMP preempt mod_unload modversions sig_id: PKCS#7 signer: SUSE Linux Enterprise Secure Boot CA sig_key: ED:87:85:B7:8F:FC:12:7F sig_hashalgo: sha256 signature: 1E:21:57:07:26:11:B4:BD:4A:D4:F1:C9:0A:3E:B1:9E:FE:9D:12:24: 2B:68:02:C5:33:74:E9:EC:44:23:5D:81:F3:CE:24:93:D8:E3:08:B2: 62:DA:62:27:DA:F1:EA:A8:6A:43:F1:03:B7:7A:05:39:DA:9F:56:36: FB:1D:D2:62:F1:07:48:52:FA:21:20:1D:F2:EB:3C:F4:9C:4A:58:BB: AB:20:65:4D:8D:C1:70:26:49:94:8C:73:FE:7E:36:7C:7E:1D:16:4C: CB:58:13:A9:DA:42:0B:AC:15:CA:24:DE:B9:0E:D0:1F:73:9D:83:53: 09:A2:29:C7:02:1F:89:E4:69:18:DB:57:60:D5:B5:FB:AA:99:B0:54: 4B:A4:4C:9F:61:EF:14:57:D8:69:E1:13:6B:40:4F:44:7A:AA:AE:91: E2:26:C7:C4:F5:6F:63:46:F7:C2:A0:56:98:9F:4D:60:F3:E2:BC:C0: 76:E7:1D:9B:E5:D9:87:22:CE:6C:B1:BE:51:67:90:76:6A:71:1E:9F: A6:5F:47:44:9A:C7:AD:D1:D6:CA:5B:3B:F2:F9:F7:5B:51:0B:16:E8: C8:11:B2:A7:98:D6:DF:7B:20:28:D2:28:62:FE:73:D6:4D:85:CB:F4: 2B:A5:D5:FD:7B:F7:AF:5D:99:00:D8:1F:D2:7A:72:00 parm: swenc:Set to 1 for software crypto (default 0) (bool) parm: ips:Set to 0 to not use link power save (default 1) (bool) parm: swlps:Set to 1 to use SW control power save (default 0) (bool) parm: fwlps:Set to 1 to use FW control power save (default 1) (bool) parm: aspm:Set to 1 to enable ASPM (default 1) (int) parm: debug_level:Set debug level (0-5) (default 0) (int) parm: debug_mask:Set debug mask (default 0) (ullong)
On 2023-01-10 15:21, James Knott wrote:
Fast boot isn't enabled. I turned it off years ago for other reasons. Also, I made a mistake. Network manager is there, but WiFi isn't listed. There should be several connections listed, as there is for Ethernet. If I go into settings, I can see the WiFi connections.
One other thing I noticed. In the settings, if I right click on an Ethernet connection, I see an option to connect, but not on a WiFi one.
On 2023-01-10 16:42, James Knott wrote:
On 2023-01-10 15:21, James Knott wrote:
Fast boot isn't enabled. I turned it off years ago for other reasons. Also, I made a mistake. Network manager is there, but WiFi isn't listed. There should be several connections listed, as there is for Ethernet. If I go into settings, I can see the WiFi connections.
One other thing I noticed. In the settings, if I right click on an Ethernet connection, I see an option to connect, but not on a WiFi one.
Also ifconfig and ip don't list the WiFi NIC.
On 2023-01-10 16:45, James Knott wrote:
One other thing I noticed. In the settings, if I right click on an Ethernet connection, I see an option to connect, but not on a WiFi one.
Also ifconfig and ip don't list the WiFi NIC.
Booting into a 15.4 rescue shows the WiFi NIC, so it's something on the installed 15.4.
On 2023-01-10 14:57, Patrick Shanahan wrote:
rpm -qa --last | grep <date of update> | sort
will provide you with the updated packages that you might determine which affected your networking.
I don't see anything that might cause this.
rpm -qa --last|grep "Mon 09 Jan"|sort
bash-completion-2.7-150400.13.3.1.noarch Mon 09 Jan 2023 09:33:12 PM bash-completion-devel-2.7-150400.13.3.1.noarch Mon 09 Jan 2023 09:33:12 PM bash-completion-doc-2.7-150400.13.3.1.noarch Mon 09 Jan 2023 09:33:12 PM ca-certificates-mozilla-2.60-150200.27.1.noarch Mon 09 Jan 2023 09:33:12 PM cepces-0.3.4-150400.3.6.1.noarch Mon 09 Jan 2023 09:33:32 PM cepces-certmonger-0.3.4-150400.3.6.1.noarch Mon 09 Jan 2023 09:33:32 PM hwdata-0.365-150000.3.54.1.noarch Mon 09 Jan 2023 09:33:14 PM libfreebl3-3.85-lp154.4.3.x86_64 Mon 09 Jan 2023 09:33:11 PM libfreebl3-hmac-3.85-lp154.4.3.x86_64 Mon 09 Jan 2023 09:33:11 PM libksba8-1.3.5-150000.4.6.1.x86_64 Mon 09 Jan 2023 09:33:20 PM libLLVM9-32bit-9.0.1-150200.3.6.1.x86_64 Mon 09 Jan 2023 09:33:20 PM libLLVM9-9.0.1-150200.3.6.1.x86_64 Mon 09 Jan 2023 09:33:30 PM libsoftokn3-3.85-lp154.4.3.x86_64 Mon 09 Jan 2023 09:33:11 PM libsoftokn3-hmac-3.85-lp154.4.3.x86_64 Mon 09 Jan 2023 09:33:11 PM libtirpc3-1.2.6-150300.3.17.1.x86_64 Mon 09 Jan 2023 09:33:25 PM libtirpc3-32bit-1.2.6-150300.3.17.1.x86_64 Mon 09 Jan 2023 09:33:20 PM libtirpc-netconfig-1.2.6-150300.3.17.1.x86_64 Mon 09 Jan 2023 09:33:20 PM libxml2-2-2.9.14-150400.5.13.1.x86_64 Mon 09 Jan 2023 09:33:20 PM libxml2-2-32bit-2.9.14-150400.5.13.1.x86_64 Mon 09 Jan 2023 09:33:21 PM libxml2-tools-2.9.14-150400.5.13.1.x86_64 Mon 09 Jan 2023 09:33:25 PM login_defs-4.8.1-150400.10.3.1.noarch Mon 09 Jan 2023 09:33:21 PM python3-cepces-0.3.4-150400.3.6.1.noarch Mon 09 Jan 2023 09:33:21 PM shadow-4.8.1-150400.10.3.1.x86_64 Mon 09 Jan 2023 09:33:30 PM sqlite3-tcl-3.39.3-150000.3.20.1.x86_64 Mon 09 Jan 2023 09:33:21 PM suse-module-tools-15.4.15-150400.3.5.1.x86_64 Mon 09 Jan 2023 09:33:21 PM tcl-8.6.12-150300.14.6.1.x86_64 Mon 09 Jan 2023 09:33:32 PM timezone-2022g-150000.75.18.1.x86_64 Mon 09 Jan 2023 09:33:23 PM timezone-java-2022g-150000.75.18.1.noarch Mon 09 Jan 2023 09:33:23 PM xfsprogs-5.13.0-150400.3.3.1.x86_64 Mon 09 Jan 2023 09:33:24 PM yast2-country-4.4.13-150400.3.3.1.x86_64 Mon 09 Jan 2023 09:33:35 PM yast2-country-data-4.4.13-150400.3.3.1.x86_64 Mon 09 Jan 2023 09:33:24 PM yast2-online-update-4.4.4-150400.3.3.1.noarch Mon 09 Jan 2023 09:33:34 PM yast2-online-update-frontend-4.4.4-150400.3.3.1.noarch Mon 09 Jan 2023 09:33:34 PM yast2-packager-4.4.33-150400.3.7.2.x86_64 Mon 09 Jan 2023 09:33:33 PM yast2-pkg-bindings-4.4.5-150400.3.3.1.x86_64 Mon 09 Jan 2023 09:33:24 PM yast2-security-4.4.18-150400.3.13.1.noarch Mon 09 Jan 2023 09:33:24 PM yast2-update-4.4.8-150400.3.6.1.x86_64 Mon 09 Jan 2023 09:33:34 PM
James Knott composed on 2023-01-10 14:33 (UTC-0500):
Last night, several packages were updated on my ThinkPad E520. Today, I see I no longer have a network manager nor WiFi. Was there a package that might have caused this? Any idea on how I can restore network manager?
BTW, WiFi still works in Windows 10, so it's not a hardware issue.
Is all normal if you login as a virgin Plasma user or login as your normal user into an IceWM session? It was on my brother's server Sunday after an online 15.3 to 15.4 upgrade. His normal user login was useless. I fixed it by emptying his normal user's ~/.cache/ and deleting everything that hadn't been written to in the past 6 or 9 months in his normal user's ~/.config/. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
participants (8)
-
Andrei Borzenkov -
Carlos E. R. -
Felix Miata -
gumb -
James Knott -
Michael Harnden -
Patrick Shanahan -
Scott Bradnick