I’m running OS on an** ASUS G73Jh2 Intel i7 x86_64** laptop. I find that NetworkManager is unstable, and I want to switch back to a non-NetworkManager configuration; but when I run YaST to configure the network, switching it to wicked, YaST writes no configuration information for my network adapters. I have put off getting this working, hoping that after some new upgrade I will find that wicked configuration starts working, but with every reinstallation I have to endure NetworkManager.
I have no idea what information will be required to troubleshoot this; networking is probably my weakest area of understanding in Linux.
I tried to paste YaST’s Hardware Information output here, but that didn’t work.
Have you edited the configuration for the wireless device concerned?
YaST > System > Network Services > Overview, select the wireless device and ‘Edit’. Follow the prompts given…
You have not told us what you did. Or maybe you have.
After switching to “wicked”, you need to click on the “Overview” tab. That should list your devices. Then select a device, and click “Edit”. In most cases, selecting “Dynamic Address” and “DHCP” should be sufficient to finish the job. For WiFi, you also have to give the network name (SSID) and security information.
I guess you mean Network Settings. Yes, when I switch it from Network Manager to wicked and enter all of the information to configure e.g. eth0, then save, YaST appears to complete normally, but eth0 is not activated, and when I look in /etc/wicked there are no entries for eth0.
YaST’s network configurator worked fine until wicked replaced what worked in the past.
As I said, “YaST writes no configuration information for my network adapters.”
After switching to “wicked”, you need to click on the “Overview” tab. That should list your devices. Then select a device, and click “Edit”. In most cases, selecting “Dynamic Address” and “DHCP” should be sufficient to finish the job. For WiFi, you also have to give the network name (SSID) and security information.
And when I do that, nothing works, because YaST saves no information.
YaST’s network configurator worked fine until wicked replaced what worked in the past.
Ok, so we’re talking about a wired NIC here. So, what is reported by the following?
/usr/sbin/hwinfo --network
/sbin/ifconfig
Then run again with ‘-a’ option
/sbin/ifconfig -a
ls -l /etc/sysconfig/network/ifcfg*
If necessary copy/paste the output to a text file and transfer to an internet-connected machine with a memory stick to post here.
What happens when you do something like the following (with cable plugged in of course)
sudo ifup eth0
YaST saves configuration in /etc/sysconfig/network.
Here I have not ever got my hardwrie to work with wicked I just use Networkmanager. works fine with hard wired
You’re right. It’s been a while since I fiddled with this. After YaST has “saved” the information for eth0, in /etc/sysconfig/network/ifcfg-eth0 I find
BOOTPROTO='dhcp'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR=''
MTU=''
NAME=''
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
DHCLIENT_SET_DEFAULT_ROUTE='yes'
Okay, but not helpful, since wicked has never worked on my machine.
Oh, good; another command I can use to diagnose network stuff.
And, [and I really hate it when this happens] **it’s working now. :-p **Sorry to bother you all.
09:56:29,root@pinto.sixys.site
~
#/usr/sbin/hwinfo --network
50: None 00.0: 10700 Loopback
[Created at net.125]
Unique ID: ZsBS.GQNx7L4uPNA
SysFS ID: /class/net/lo
Hardware Class: network interface
Model: "Loopback network interface"
Device File: lo
Link detected: yes
Config Status: cfg=no, avail=yes, need=no, active=unknown
51: None 00.0: 10701 Ethernet
[Created at net.125]
Unique ID: usDW.ndpeucax6V1
Parent ID: rBUF.kuUQwhe27I2
SysFS ID: /class/net/eth0
SysFS Device Link: /devices/pci0000:00/0000:00:1c.5/0000:04:00.0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "atl1c"
Driver Modules: "atl1c"
Device File: eth0
HW Address: 20:cf:30:51:9a:4c
Link detected: yes
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #23 (Ethernet controller)
52: None 00.0: 10701 Ethernet
[Created at net.125]
Unique ID: uSCr.ndpeucax6V1
Parent ID: lfzD.zZFFdHenM61
SysFS ID: /class/net/wmx0
SysFS Device Link: /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "i2400m_usb"
Driver Modules: "i2400m_usb"
Device File: wmx0
HW Address: 64:d4:da:03:dc:8d
Link detected: no
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #39 (Ethernet controller)
53: None 00.0: 1070a WLAN
[Created at net.125]
Unique ID: AYEt.QXn1l67RSa1
Parent ID: y9sn.aBTWqi8jjd9
SysFS ID: /class/net/wlan0
SysFS Device Link: /devices/pci0000:00/0000:00:1c.1/0000:03:00.0
Hardware Class: network interface
Model: "WLAN network interface"
Driver: "iwlwifi"
Driver Modules: "iwlwifi"
Device File: wlan0
HW Address: 00:23:15:33:91:a0
Link detected: no
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #22 (Network controller)
/sbin/ifconfig
09:56:40,root@pinto.sixys.site
~
#/sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 20:CF:30:51:9A:4C
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::22cf:30ff:fe51:9a4c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:261706 errors:0 dropped:0 overruns:0 frame:0
TX packets:164564 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:331206486 (315.8 Mb) TX bytes:14996568 (14.3 Mb)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:89423 errors:0 dropped:0 overruns:0 frame:0
TX packets:89423 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:39146708 (37.3 Mb) TX bytes:39146708 (37.3 Mb)
Then run again with ‘-a’ option
/sbin/ifconfig -a
09:56:56,root@pinto.sixys.site
~
#/sbin/ifconfig -a
eth0 Link encap:Ethernet HWaddr 20:CF:30:51:9A:4C
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::22cf:30ff:fe51:9a4c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:261952 errors:0 dropped:0 overruns:0 frame:0
TX packets:164822 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:331389051 (316.0 Mb) TX bytes:15029172 (14.3 Mb)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:89795 errors:0 dropped:0 overruns:0 frame:0
TX packets:89795 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:39348403 (37.5 Mb) TX bytes:39348403 (37.5 Mb)
wlan0 Link encap:Ethernet HWaddr 00:23:15:33:91:A0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
wmx0 Link encap:Ethernet HWaddr 64:D4:DA:03:DC:8D
NOARP MTU:1400 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:20
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
ls -l /etc/sysconfig/network/ifcfg*
09:58:08,root@pinto.sixys.site
~
#ls -l /etc/sysconfig/network/ifcfg*
-rw-r--r-- 1 root root 163 Jun 13 09:56 /etc/sysconfig/network/ifcfg-eth0
-rw------- 1 root root 173 May 2 19:22 /etc/sysconfig/network/ifcfg-lo
-rw------- 1 root root 861 Jun 13 09:56 /etc/sysconfig/network/ifcfg-wlan0
-rw-r--r-- 1 root root 22K Sep 11 2015 /etc/sysconfig/network/ifcfg.template
If necessary copy/paste the output to a text file and transfer to an internet-connected machine with a memory stick to post here.
My point is to try NetworkManager if wicked does not work. As I said it has not worked here either I just us NM
Yep, commands and output give the best picture about where things are at and what might need to be done to resolve a particular issue. Glad to read that it is working now. The reason that I gave the last command was make sure that /etc/sysconfig/network/ifcfg-eth0 did exist which you now know was created/modified by YaST as expected.