Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[Software] Bullseye 11 keeps network disconnect upon each reboot

Linux Kernel, Network, and Services configuration.
Post Reply
Message
Author
User avatar
nikobit
Posts: 123
Joined: 2009-02-08 19:40
Location: Moscow, Russia
Has thanked: 5 times
Contact:

[Software] Bullseye 11 keeps network disconnect upon each reboot

#1 Post by nikobit »

I did installed Bullseye just the other day on top of the previously set double boot system with Win/GNULinux. The whole installation took less than 15 minutes using non-free hardware GRUB installation USB .iso file. Network was identified smoothlessly and the whole process was complete in no time. Right after finish I could login into it and started to transfer my backuped /home files. In the middle of software restoration I had to reboot the machine and my Network Manager have indicated the internet connection loss with constant attempt to re-connect which was failing each time. Nevermind the amount of search made over internet I couldn't re-connect to internet and decided just to install the whole OS anew as it was fresh installed just a couple hours back. While going through installation process there was a Network interfaces identification process. Second time it didn't succeeded to identify Network Interfaces on 'auto'. I did installation cancel and booted into another Win OS. It could successfully connec to internet and identify the wired connection with no problem.Then I rebooted into installation USB and repeated Bullseye install process over again. After successful network interface connection the installation was completed OK. I have logined to my new Bullseye OS with no problem and started to restore backups. On setting up 'sudo' I had to reboot the machine and voila - the Network Manager has infinite loop of network connection tries with no luck again! To solve this strange behaivior I did reboot into Win OS with network card check. Everything was OK. Booting back into Bullseye I had my network back running fine! My sole suspicion concerns domain server setup during installation. Is it OK to name my domain server as 'local'? What should I do to avoid loosing network Manager internet wired connection over and over again? Most of my details are given in signature just for the reference.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  • OS: Debian 11 bullseye
  • Kernel: x86_64 Linux 5.10.0-19-amd64
  • Shell: bash
  • DE: GNOME 3.38.4
  • CPU: Intel Core i7-4790 @ 8x 4GHz
  • GPU: NVE4
  • RAM: 2384MiB / 15925MiB
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

User avatar
sunrat
Administrator
Administrator
Posts: 6412
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 116 times
Been thanked: 462 times

Re: [Software] Bullseye 11 keeps network disconnect upon each reboot

#2 Post by sunrat »

Network device info? Any error messages in journalctl?

Code: Select all

lspci -knn |grep -A3 -i net
journalctl -b -p3
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

User avatar
nikobit
Posts: 123
Joined: 2009-02-08 19:40
Location: Moscow, Russia
Has thanked: 5 times
Contact:

Re: [Software] Bullseye 11 keeps network disconnect upon each reboot

#3 Post by nikobit »

sunrat wrote: 2022-12-03 12:54 Network device info? Any error messages in journalctl?

Code: Select all

lspci -knn |grep -A3 -i net
journalctl -b -p3

Code: Select all

$ lspci -knn |grep -A3 -i net
02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03)
	Subsystem: Dell BCM4352 802.11ac Wireless Network Adapter [1028:0017]
	Kernel driver in use: bcma-pci-bridge
	Kernel modules: bcma
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
	Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1028:05d7]
	Kernel driver in use: r8169
	Kernel modules: r8169
and

Code: Select all

$ journalctl -b -p3
Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal' can see all messages.
      Pass -q to turn off this notice.
-- Journal begins at Sat 2022-12-03 10:19:37 MSK, ends at Sat 2022-12-03 15:59:31 MSK. --
Dec 03 13:34:02 sheldon pipewire[1671]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name '>
Dec 03 13:34:03 sheldon systemd[1656]: Failed to start Application launched by gnome-session-binary.
I seat here afraid to move and loose connection again :roll:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  • OS: Debian 11 bullseye
  • Kernel: x86_64 Linux 5.10.0-19-amd64
  • Shell: bash
  • DE: GNOME 3.38.4
  • CPU: Intel Core i7-4790 @ 8x 4GHz
  • GPU: NVE4
  • RAM: 2384MiB / 15925MiB
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

User avatar
nikobit
Posts: 123
Joined: 2009-02-08 19:40
Location: Moscow, Russia
Has thanked: 5 times
Contact:

Re: [Software] Bullseye 11 keeps network disconnect upon each reboot

#4 Post by nikobit »

One more try within root:

Code: Select all

дек 03 17:29:41 sheldon kernel: DMAR: DRHD: handling fault status reg 2
дек 03 17:29:41 sheldon kernel: DMAR: [DMA Read] Request device [01:00.0] PASID ffffffff fault addr 0 [fault reason 06] PTE Read access is not set
дек 03 17:29:41 sheldon kernel: bcma: Unsupported SPROM revision: 11
дек 03 17:29:41 sheldon kernel: bcma-pci-bridge 0000:02:00.0: bus0: No SPROM available
дек 03 17:29:42 sheldon kernel: b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 12, Type 11 (AC), Revision 1)
дек 03 17:29:42 sheldon kernel: bluetooth hci0: firmware: failed to load brcm/BCM20702A1-413c-8143.hcd (-2)
дек 03 17:29:42 sheldon kernel: firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
дек 03 17:29:42 sheldon kernel: bluetooth hci0: firmware: failed to load brcm/BCM-413c-8143.hcd (-2)
дек 03 17:29:42 sheldon kernel: Bluetooth: hci0: BCM: firmware Patch file not found, tried:
дек 03 17:29:42 sheldon kernel: Bluetooth: hci0: BCM: 'brcm/BCM20702A1-413c-8143.hcd'
дек 03 17:29:42 sheldon kernel: Bluetooth: hci0: BCM: 'brcm/BCM-413c-8143.hcd'
дек 03 17:29:57 sheldon bluetoothd[705]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
дек 03 17:29:57 sheldon bluetoothd[705]: sap-server: Operation not permitted (1)
дек 03 17:29:57 sheldon dhclient[838]: Failed to get interface index: No such device
дек 03 17:29:57 sheldon dhclient[838]: 
дек 03 17:29:57 sheldon dhclient[838]: If you think you have received this message due to a bug rather
дек 03 17:29:57 sheldon dhclient[838]: than a configuration issue please read the section on submitting
дек 03 17:29:57 sheldon dhclient[838]: bugs on either our web page at www.isc.org or in the README file
дек 03 17:29:57 sheldon dhclient[838]: before submitting a bug.  These pages explain the proper
дек 03 17:29:57 sheldon dhclient[838]: process and the information we find helpful for debugging.
дек 03 17:29:57 sheldon dhclient[838]: 
дек 03 17:29:57 sheldon dhclient[838]: exiting.
дек 03 17:29:57 sheldon systemd[1]: Failed to start Raise network interfaces.
дек 03 17:29:57 sheldon pipewire[950]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
дек 03 17:29:58 sheldon kernel: nouveau 0000:01:00.0: firmware: failed to load nouveau/nve4_fuc084 (-2)
дек 03 17:29:58 sheldon kernel: nouveau 0000:01:00.0: firmware: failed to load nouveau/nve4_fuc084d (-2)
дек 03 17:29:58 sheldon kernel: nouveau 0000:01:00.0: msvld: unable to load firmware data
дек 03 17:29:58 sheldon kernel: nouveau 0000:01:00.0: msvld: init failed, -19
дек 03 17:30:25 sheldon gdm-password][1703]: gkr-pam: unable to locate daemon control file
дек 03 17:30:25 sheldon pipewire[1723]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
дек 03 17:30:26 sheldon bluetoothd[705]: src/profile.c:ext_start_servers() RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)
дек 03 17:30:26 sheldon bluetoothd[705]: src/profile.c:ext_start_servers() RFCOMM server failed for Headset unit: rfcomm_bind: Address already in use (98)
дек 03 17:30:28 sheldon kernel: nouveau 0000:01:00.0: firmware: failed to load nouveau/nve4_fuc084 (-2)
дек 03 17:30:28 sheldon kernel: nouveau 0000:01:00.0: firmware: failed to load nouveau/nve4_fuc084d (-2)
дек 03 17:30:28 sheldon kernel: nouveau 0000:01:00.0: msvld: unable to load firmware data
дек 03 17:30:28 sheldon kernel: nouveau 0000:01:00.0: msvld: init failed, -19
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  • OS: Debian 11 bullseye
  • Kernel: x86_64 Linux 5.10.0-19-amd64
  • Shell: bash
  • DE: GNOME 3.38.4
  • CPU: Intel Core i7-4790 @ 8x 4GHz
  • GPU: NVE4
  • RAM: 2384MiB / 15925MiB
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

User avatar
nikobit
Posts: 123
Joined: 2009-02-08 19:40
Location: Moscow, Russia
Has thanked: 5 times
Contact:

Re: [Software] Bullseye 11 keeps network disconnect upon each reboot

#5 Post by nikobit »

Well, for last couple of days there were no wired network losses. Until third day. Job is not done. Topic might be be continued with only question: what the heck has happened? Why network card should get lost in the middle of installation? And now it gets lost during normal reboot! I'm not discussing WiFi Broadcom above. It's out of discussion. But what happened to wired Realtek?

Code: Select all

Link speed (Rx/Tx):	1000/1000 (Mbps)
Local channel IPv6:	fe90::3bfe:ad5a:6c91:1124%59
IPv4-address:	192.168.1.184
DNS-server IPv4:	192.168.1.1
Domain DNS:	local
Manufacturer:	Realtek
Description:	Realtek PCIe GBE Family Controller #2 #2
Driver ver:	10.1.505.2015
Physical address (MAC):	F8-BC-21-DC-5E-CD
Nothing was actually done to solve the topic though. Very strange as it decides to connect\not connect by itself...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  • OS: Debian 11 bullseye
  • Kernel: x86_64 Linux 5.10.0-19-amd64
  • Shell: bash
  • DE: GNOME 3.38.4
  • CPU: Intel Core i7-4790 @ 8x 4GHz
  • GPU: NVE4
  • RAM: 2384MiB / 15925MiB
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

User avatar
nikobit
Posts: 123
Joined: 2009-02-08 19:40
Location: Moscow, Russia
Has thanked: 5 times
Contact:

Re: [Software] Bullseye 11 keeps network disconnect upon each reboot

#6 Post by nikobit »

This time it was very strange loss of network. I could ping my router and nothing else! I tried to change DNS to some well known common servers, tried to switch on a flag at 'Use this connection only for resources on this network' and play with Proton 'Kill switch' settings. Latest was installed from here and has worked fine for last couple of weeks or so. Still the network loss is unpredictable and could be cured by reboot into second installed OS Windows and fingering additional settings as stated above.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  • OS: Debian 11 bullseye
  • Kernel: x86_64 Linux 5.10.0-19-amd64
  • Shell: bash
  • DE: GNOME 3.38.4
  • CPU: Intel Core i7-4790 @ 8x 4GHz
  • GPU: NVE4
  • RAM: 2384MiB / 15925MiB
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

User avatar
ticojohn
Posts: 1284
Joined: 2009-08-29 18:10
Location: Costa Rica
Has thanked: 21 times
Been thanked: 44 times

Re: [Software] Bullseye 11 keeps network disconnect upon each reboot

#7 Post by ticojohn »

My desktop system uses the same Realtek chip and I had similar problems with the r8169 driver. What I read was that the Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 chipset sets some flag such that on reboot the chipset is locked, or something like that. In order to fix the problem I use the r8168-dkms driver.

Code: Select all

john@debianA:~$ lspci -knn |grep -A3 -i net
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
	Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet [1458:e000]
	Kernel driver in use: r8168
	Kernel modules: r8168
Don't know if it will help, but it helped me. If you use it you find that every time there is a kernel upgrade the r8168-dkms driver has to be recompiled, but thankfully it does so automatically.

EDIT: By the way here is part of the driver description for the Synaptic Package Manager:

r8168 is the Linux device driver released by RealTek for their network
controllers with PCI-Express interface:
* 10/100/1000M Gigabit Ethernet: RTL8111B, RTL8111C, RTL8111D, RTL8111E,
RTL8111F, RTL8111G(S), RTL8111H(S), RTL8118(A)(S), RTL8119i, RTL8111L,
RTL8168B, RTL8168E, RTL8168H, RTL8111DP, RTL8111EP, RTL8111FP, RTL8411,
RTL8411B
I am not irrational, I'm just quantum probabilistic.

User avatar
nikobit
Posts: 123
Joined: 2009-02-08 19:40
Location: Moscow, Russia
Has thanked: 5 times
Contact:

Re: [Software] Bullseye 11 keeps network disconnect upon each reboot

#8 Post by nikobit »

In my case it's:

Code: Select all

kojibka@sheldon:~$ lspci -knn |grep -A3 -i net
02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03)
	Subsystem: Dell BCM4352 802.11ac Wireless Network Adapter [1028:0017]
	Kernel modules: bcma, wl
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
	Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1028:05d7]
	Kernel driver in use: r8169
	Kernel modules: r8169
Dell Wireless 1550 Wi-Fi has got major problem as it is not able to connect at all.
But the issue concerns Realtek Integrated Ethernet Controller RTL8111G and following your advice I will try to lean towards r8168-dkms.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  • OS: Debian 11 bullseye
  • Kernel: x86_64 Linux 5.10.0-19-amd64
  • Shell: bash
  • DE: GNOME 3.38.4
  • CPU: Intel Core i7-4790 @ 8x 4GHz
  • GPU: NVE4
  • RAM: 2384MiB / 15925MiB
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Post Reply