CentOS freezes when wifi connect to wlan

Issues related to hardware problems
Post Reply
Davpek
Posts: 4
Joined: 2018/06/28 21:01:06

CentOS freezes when wifi connect to wlan

Post by Davpek » 2018/06/29 20:57:29

Hello togheter!

First things first. I´m a typical Windows user and I startet using Linux 7 days ago. I solved a couple of problems so far,... for example (converting Windows from MBR to GPT, changing Bootloader defaults and entrys,...and so an).

I have one more problem. Since the first time (at installation) my computer freezes when I have pluged in my pci express wifi card. (TP-Link TL-WN881ND with a RTL8192EE chip). To find the reason why the installation stops and the computer freezes took me hours,... :oops:

Now the situation is:

When I have pluged in my pci express card, I can boot my CentOS 7 but after he tries to connect over the wifi card he freezes. The wifi card is working, because if Iam fast enough I can see all available wlan´s.

I tried to turn of the card over the console: "nmcli radio wifi off" Then everything is fine! Centos is working well,...!
I tried to install elrepo with:

rpm --import https://www.elrepo.org/RPM-GPG-KEY-elrepo.org
rpm -Uvh http://www.elrepo.org/elrepo-release-7. ... noarch.rpm
yum install kmod-r8168 -y
reboot

with kmod-r8168 the installation is working
with kmod-rtl8192cu, kmod-r8192ce, kmod-r8192cu I got the errormessage: no package found,...

And I need help, because do not know what to do next. Is there anybody who can help?

Thanks a lot sofar!

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: CentOS freezes when wifi connect to wlan

Post by TrevorH » 2018/06/29 21:39:17

What is the output from lspci -nn | grep -i net so we can see the exact pci vendor/device id.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

Davpek
Posts: 4
Joined: 2018/06/28 21:01:06

Re: CentOS freezes when wifi connect to wlan

Post by Davpek » 2018/06/30 08:13:48

Hello,

the output is:

1e:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8192EE PCIe Wireless Network Adapter [10ec:818b]
1f:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 11)

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: CentOS freezes when wifi connect to wlan

Post by TrevorH » 2018/06/30 08:56:37

That adapter should be supported by the in-kernel rtl8192ee module.

When it "freezes", what are the symptoms? Are the keyboard LEDs flashing? Is there any information logged in /var/log/messages?
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

Davpek
Posts: 4
Joined: 2018/06/28 21:01:06

Re: CentOS freezes when wifi connect to wlan

Post by Davpek » 2018/06/30 15:34:56

I tried to analyse the behaviour:

1.) turning on the radio over console
2.) Checking out available wlans and I also had the time to choose the right one
3.) while setting my wlan password, my computer rebooted
4.) After reboot I tried to login an after login befor even the desktop view is already loaded he logged me off
5.) I tried a second time to login,...an he rebooted,...
and so on...
After I unplugged the wifi card,....everything is all right.

The behaviour is not always similar. Last couple time U got a black screen an nothing even happens.

I found a view messages which could maybe help?


Jun 30 16:57:16 Davpek nm-dispatcher: req:3 'connectivity-change': start running ordered scripts...
Jun 30 16:57:16 Davpek nm-dispatcher: req:4 'hostname': start running ordered scripts...
Jun 30 16:57:17 Davpek NetworkManager[856]: <warn> [1530370637.0070] ifcfg-rh: loading "/etc/sysconfig/network-scripts/ifcfg-Herbi" fails: File '/etc/sysconfig/network-scripts/ifcfg-Herbi' had neither TYPE nor DEVICE keys.
Jun 30 16:57:17 Davpek network: Loopback-Schnittstelle hochfahren: [ OK ]
Jun 30 16:57:17 Davpek NetworkManager[856]: <warn> [1530370637.1690] ifcfg-rh: loading "/etc/sysconfig/network-scripts/ifcfg-Herbi" fails: File '/etc/sysconfig/network-scripts/ifcfg-Herbi' had neither TYPE nor DEVICE keys.
Jun 30 16:57:17 Davpek NetworkManager[856]: <warn> [1530370637.1919] ifcfg-rh: loading "/etc/sysconfig/network-scripts/ifcfg-Herbi" fails: File '/etc/sysconfig/network-scripts/ifcfg-Herbi' had neither TYPE nor DEVICE keys.
Jun 30 16:57:17 Davpek network: Schnittstelle Herbi hochfahren: ERROR : [/etc/sysconfig/network-scripts/ifup-eth] Gerät scheint zu fehlen, Initialisierung verzögert.
Jun 30 16:57:17 Davpek /etc/sysconfig/network-scripts/ifup-eth: Gerät scheint zu fehlen, Initialisierung verzögert.
Jun 30 16:57:17 Davpek network: [FEHLGESCHLAGEN]
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.2515] device (enp31s0): disconnecting connection 'enp31s0' for new activation request
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.2516] device (enp31s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed')
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.2518] manager: NetworkManager state is now DISCONNECTING
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.2590] device (enp31s0): disconnecting for new activation request.
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.2591] audit: op="connection-activate" uuid="11e93ddf-7642-43f4-b62d-06f062f07d98" name="enp31s0" pid=1223 uid=0 result="success"
Jun 30 16:57:17 Davpek nm-dispatcher: req:5 'connectivity-change': new request (4 scripts)
Jun 30 16:57:17 Davpek nm-dispatcher: req:5 'connectivity-change': start running ordered scripts...
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.2595] device (enp31s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.2702] dhcp4 (enp31s0): canceled DHCP transaction, DHCP client pid 998
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.2702] dhcp4 (enp31s0): state changed bound -> done
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.2789] manager: NetworkManager state is now DISCONNECTED
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.2790] policy: set-hostname: set hostname to 'localhost.localdomain' (no default device)
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.2791] device (enp31s0): Activation: starting connection 'enp31s0' (11e93ddf-7642-43f4-b62d-06f062f07d98)
Jun 30 16:57:17 Davpek nm-dispatcher: req:6 'down' [enp31s0]: new request (4 scripts)
Jun 30 16:57:17 Davpek systemd-hostnamed: Changed host name to 'localhost.localdomain'
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.2813] device (enp31s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.2814] manager: NetworkManager state is now CONNECTING
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.2820] device (enp31s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 30 16:57:17 Davpek nm-dispatcher: req:7 'hostname': new request (4 scripts)
Jun 30 16:57:17 Davpek chronyd[826]: Source 46.163.88.228 offline
Jun 30 16:57:17 Davpek chronyd[826]: Source 5.9.131.170 offline
Jun 30 16:57:17 Davpek chronyd[826]: Source 62.116.162.126 offline
Jun 30 16:57:17 Davpek chronyd[826]: Source 82.165.77.22 offline
Jun 30 16:57:17 Davpek nm-dispatcher: req:6 'down' [enp31s0]: start running ordered scripts...
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.2932] device (enp31s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.2935] dhcp4 (enp31s0): activation: beginning transaction (timeout in 45 seconds)
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.2956] dhcp4 (enp31s0): dhclient started with pid 1258
Jun 30 16:57:17 Davpek dhclient[1258]: DHCPREQUEST on enp31s0 to 255.255.255.255 port 67 (xid=0x742fcfb7)
Jun 30 16:57:17 Davpek nm-dispatcher: req:7 'hostname': start running ordered scripts...
Jun 30 16:57:17 Davpek abrtd: '/var/spool/abrt/xorg-2018-06-29-00:16:19-3232-1' is not a problem directory
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.5049] dhcp4 (enp31s0): state changed unknown -> bound
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.5060] device (enp31s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jun 30 16:57:17 Davpek dhclient[1258]: bound to 192.168.178.37 -- renewal in 1432 seconds.
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.5068] device (enp31s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.5071] device (enp31s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.5073] manager: NetworkManager state is now CONNECTED_LOCAL
Jun 30 16:57:17 Davpek network: Schnittstelle enp31s0 hochfahren: Verbindung wurde erfolgreich aktiviert (aktiver D-Bus-Pfad: /org/freedesktop/NetworkManager/ActiveConnection/2)
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.5152] manager: NetworkManager state is now CONNECTED_SITE
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.5152] policy: set 'enp31s0' (enp31s0) as default for IPv4 routing and DNS
Jun 30 16:57:17 Davpek NetworkManager[856]: <info> [1530370637.5213] device (enp31s0): Activation: successful, device activated.
Jun 30 16:57:17 Davpek network: [ OK ]
Jun 30 16:57:17 Davpek nm-dispatcher: req:9 'connectivity-change': new request (4 scripts)
Jun 30 16:57:17 Davpek nm-dispatcher: req:10 'hostname': new request (4 scripts)
Jun 30 16:57:17 Davpek systemd: network.service: control process exited, code=exited status=1
Jun 30 16:57:17 Davpek systemd: Failed to start LSB: Bring up/down networking.
Jun 30 16:57:17 Davpek systemd: Unit network.service entered failed state.
Jun 30 16:57:17 Davpek systemd: network.service failed.
Jun 30 16:57:17 Davpek systemd: Reached target Network.

Davpek
Posts: 4
Joined: 2018/06/28 21:01:06

Re: CentOS freezes when wifi connect to wlan

Post by Davpek » 2018/07/02 16:39:05

so,...my solution: I orderd a 25m lan cable!

Post Reply