Does not look like it has all the necessary IP info in there. Plus I believe you in the “IPADDR=” section you should have an ip like 192.168.2.X not /24 the X representing and available IP on your network.
On 12/31/2012 11:26 AM, joescott4t wrote:
>
> jburgeson;2514653 Wrote:
>> I changed the network setup method to Traditional with ifup. That let me
>> use YaST2 to edit network settings. I also disabled IPv6, since I know
>> my ISP does not support it. Then the connection showed as
>> “Ethernet Network Card DHCP eth0” but still didn’t work, so I rebooted
>> with the installed version (not Live CD).
>>
>>
>>
>>>
> Code:
> --------------------
> > >
> > BOOTPROTO=‘static’
> > BROADCAST=’’
> > ETHTOOL_OPTIONS=’’
> > IPADDR=‘192.168.2.0/24’
> > MTU=’’
> > NAME=‘191 Gigabit Ethernet Adapter’
> > NETMASK=’’
> > NETWORK=’’
> > REMOTE_IPADDR=’’
> > STARTMODE=‘auto’
> > USERCONTROL=‘no’
> > PREFIXLEN=‘24’
> >
> --------------------
>>>
>>
>>
>>
>>>
> Code:
> --------------------
> > >
> > 00:04.0 Ethernet controller [0200]: Silicon Integrated Systems [SiS] 191 Gigabit Ethernet Adapter [1039:0191] (rev 02)
> >
> --------------------
>>>
>
> Does not look like it has all the necessary IP info in there. Plus I
> believe you in the “IPADDR=” section you should have an ip like
> 192.168.2.X not /24 the X representing and available IP on your network.
Your problem is that you are trying to assign the IP address 192.168.2.0 to the
interface. Addresses ending in .0 and .255 are special and cannot be used for
real devices. If you change that IPADDR line to “IPADDR=192.168.2.99/24”, it
should be OK as long as 99 is not used by some other device in your network.
For someone with limited network experience, dynamic IP addresses using DHCP are
always easier and safer than a static IP. Similarly, using NetworkManager is
easier than ifup as NM gets all the bits right.
> > BOOTPROTO=‘static’
> > BROADCAST=‘’
> > ETHTOOL_OPTIONS=‘’
> > IPADDR=‘192.168.2.0/24’
> > MTU=‘’
> > NAME=‘191 Gigabit Ethernet Adapter’
> > NETMASK=‘’
> > NETWORK=‘’
> > REMOTE_IPADDR=‘’
> > STARTMODE=‘auto’
> > USERCONTROL=‘no’
> > PREFIXLEN=‘24’
> >
> --------------------
>
> Does not look like it has all the necessary IP info in there. Plus I
> believe you in the “IPADDR=” section you should have an ip like
> 192.168.2.X not /24 the X representing and available IP on your network.
Your problem is that you are trying to assign the IP address 192.168.2.0 to the
interface. Addresses ending in .0 and .255 are special and cannot be used for
real devices. If you change that IPADDR line to “IPADDR=192.168.2.99/24”, it
should be OK as long as 99 is not used by some other device in your network./QUOTE}
IPADDR='192.168.2.99/24'
but it still doesn’t work.
For someone with limited network experience, dynamic IP addresses using DHCP are
always easier and safer than a static IP. Similarly, using NetworkManager is
easier than ifup as NM gets all the bits right.
You’re preaching to the choir, but NM didn’t get it right. I’m willing to start over scratch with the install DVD and see if it works this time.
I have tried to follow the instructions given here.
https://forums.opensuse.org/archives/sf-archives/archives-network-internet/344160-sis191-ethernet-controller-total-noob-linux.html
There were a couple of minor differences
- In step one, the file sis190.c is buried a little deeper.
- In step 3 the new line number is 1633, and the C++ code has changed a little but I changed the ids* to 0x0968. Perhaps I should have just changed the order of the terms in the array.*
But the real problem is in step 8 when I try to “make .config” the error message “command not found” comes up. Then I try to add it with zypper, but since I have no network connectivity that failed.
Are there any other suggestions?
You shouldn’t need to be compiling the sis190 driver. The kernel includes this driver already.
# modinfo sis190
filename: /lib/modules/3.4.11-2.16-desktop/kernel/drivers/net/ethernet/sis/sis190.ko
license: GPL
version: 1.4
author: K.M. Liu <kmliu@sis.com>, Ueimor <romieu@fr.zoreil.com>
description: SiS sis190/191 Gigabit Ethernet driver
srcversion: A2D900ABFB9B60771BE5E26
alias: pci:v00001039d00000191sv*sd*bc*sc*i*
alias: pci:v00001039d00000190sv*sd*bc*sc*i*
depends:
intree: Y
vermagic: 3.4.11-2.16-desktop SMP preempt mod_unload modversions
parm: rx_copybreak:Copy breakpoint for copy-only-tiny-frames (int)
parm: debug:Debug verbosity level (0=none, ..., 16=all) (int)
You can test whether it is loaded already
lsmod |grep sis
Just head back to YasT>> Network Devices >> Network Settings (and choose whether you want to use ‘Traditional ifup’ or network manager). Follow Larry’s advice and use DHCP preferably.
This guide may be helpful to you:
You’re right.
lsmod |grep sis
sis 190 26347 0
sata_sis 12700 3
pata_sis 14449 1 sata_sis
Just head back to YasT>> Network Devices >> Network Settings (and choose whether you want to use ‘Traditional ifup’ or network manager). Follow Larry’s advice and use DHCP preferably.
I started over reinstalling from the DVD using Network Manager and DHCP. It doesn’t work. This is what I see from the desktop widget.
Networking Interface Connections
Type: Wired Internet Wired connection 1
Connection State: Not connected
IP Address: No IP address
Connection Speed: 100 MBit/s
System Name: eth0
MAC Address: 00:1B:FC:F2:1F:18
Driver: sis190
Traffic
0.70
0.35
0.00
This guide may be helpful to you: openSUSE 12.2: Chapter 13. Basic Networking
I’ve read this twice already, but am not familiar enough with networking to know which options to change from the default.
Let’s confirm that you are configured to use the network manager. What is returned from
cat /etc/sysconfig/network/config |grep NETWORK
Which desktop environment are you using (Gnome, KDE,…)?
There should be an ‘Auto eth0’ connection available to connect with. It is set to activate by default.
If you choose to try ‘Traditional Method with ifup’ again, then you simply configure your wired ethernet interface (under ‘Overview’), and choose DHCP. Your /etc/sysconfig/network/ifcfg-eth0 should look something like this
BOOTPROTO='dhcp4'
STARTMODE='auto'
KDE, but I would switch if it would help solve the problem.
There should be an ‘Auto eth0’ connection available to connect with. It is set to activate by default.
In YaST2 - Network Settings, Overview it shows
Name = 191 Gigabit Ethernet Adapter, IP Address = DHCP, Device = eth0
If you choose to try ‘Traditional Method with ifup’ again, then you simply configure your wired ethernet interface (under ‘Overview’), and choose DHCP. Your /etc/sysconfig/network/ifcfg-eth0 should look something like this
BOOTPROTO='dhcp4' STARTMODE='auto'
I changed it back to ‘Traditional Method with ifup’ in the Global Options tab. Then at the bottom it shows
[FONT=arial]191 Gigabit Ethernet Adapter[/FONT]MAC : 00:1b:fc:f2:1f:18
**BusID : **0000:00:04.0
- Device Name: eth0
- Started automatically at boot
[FONT=arial]* IP address assigned using DHCP
[/FONT]The file /etc/sysconfi/network/ifcfg-eth0 looks like this.
BOOTPROTO='dhcp'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR=''
MTU=''
NAME='191 Gigabit Ethernet Adapter'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
USERCONTROL='no'
Changing BOOTPROTO to ‘dhcp4’ has no effect that I can see.
Changing IPADDR to ‘192.168.2.99/24’ has no effect that I can see.
With the ‘traditional ifup’ and DHCP config, try the following:
Open a terminal for monitoring, and do
sudo tail -f /var/log/messages
Open a second terminal and type
sudo /sbin/dhclient eth0
You should see output similar to
Jan 7 08:07:34 linux-akl avahi-daemon[678]: Withdrawing address record for 192.168.1.4 on eth0.
Jan 7 08:07:34 linux-akl avahi-daemon[678]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.4.
Jan 7 08:07:34 linux-akl avahi-daemon[678]: Interface eth0.IPv4 no longer relevant for mDNS.
Jan 7 08:07:40 linux-akl avahi-daemon[678]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.4.
Jan 7 08:07:40 linux-akl avahi-daemon[678]: New relevant interface eth0.IPv4 for mDNS.
Jan 7 08:07:40 linux-akl avahi-daemon[678]: Registering new address record for 192.168.1.4 on eth0.IPv4.
If this doesn’t work, then I would be looking at your cabling, and router config that you’re attached to.
I know that the cabling and the router are not the problem because I have checked them with two laptops. I’ve disabled the wireless and plugged in the ethernet cable, then verified that I have an internet connection.
ls: cannot access /var/run/netconfig//etho00/: No such file or directory
This doesn’t makes sense. It should be eth0, not eth00. Check that you haven’t made a typo.
Then the following three lines repeat every 20 seconds. dhcpcd[1930]: eth0: timed out dhcpcd[1930]: eth0: trying to use old lease in '/var/lib/dhcpcd/dhcpcd-eth0.info' dhcpcd[1930]: eth0: broadcasting for a lease
Not sure what is going wrong here.
Try
sudo /sbin/ifdown eth0
then
sudo /sbin/ifup eth0
Check status with
ip address
If no joy, show us the output of
sudo cat /etc/sysconfig/network/ifcfg-eth0
to confirm configuration again
You are correct. It was a typo. Sorry about that. I’ve corrected it above.
You recommended that I try this.
sudo /sbin/ifdown eth0
eth0 device: Silicon Integrated Systems [SiS] 191 Gigabit Ethernet Adapter (rev 02)
then this
sudo /sbin/ifup eth0
eth0 device: Silicon Integrated Systems [SiS] 191 Gigabit Ethernet Adapter (rev 02)
Starting DHCP4 client on eth0. . . . . . . .
eth0 DHCP4 continues in background
Followed by checking status with
ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:1b:fc:f2:1f:18 brd ff:ff:ff:ff:ff:ff
inet 192.168.2.99/24 brd 192.168.2.255 scope global eth0
Since no joy, here is the output you requested in order to confirm the configuration again.
sudo cat /etc/sysconfig/network/ifcfg-eth0
BOOTPROTO='dhcp'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='192.168.2.99/24'
MTU=''
NAME='191 Gigabit Ethernet Adapter'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
USERCONTROL='no'
BOOTPROTO='dhcp'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='192.168.2.99/24'
MTU=''
NAME='191 Gigabit Ethernet Adapter'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
USERCONTROL='no'
The IPADDR entry should be empty since you’re using DHCP
BOOTPROTO='dhcp'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR=''
MTU=''
NAME='191 Gigabit Ethernet Adapter'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
USERCONTROL='no'
On 2013-01-07 03:06, jburgeson wrote:
> Followed by checking status with
>
> Code:
> --------------------
> ip address
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
> link/ether 00:1b:fc:f2:1f:18 brd ff:ff:ff:ff:ff:ff
> inet 192.168.2.99/24 brd 192.168.2.255 scope global eth0
>
> --------------------
>
>
> Since no joy, here is the output you requested in order to confirm the
> configuration again.
To me, the output seems to be of success. What is the problem?
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
I changed the IPADDR entry to be empty, then repeated the steps from before.
BOOTPROTO='dhcp'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR=''
MTU=''
NAME='191 Gigabit Ethernet Adapter'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
USERCONTROL='no'
[/QUOTE]
All of them came back the same except that ‘ip address’ only has two lines for eth0.
ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:1b:fc:f2:1f:18 brd ff:ff:ff:ff:ff:ff
The problem is that I still have no internet connection.
Okay, try a static configuration. I’m making an assumption that the 192.168.2.99 is a valid host address for your network
BOOTPROTO='static'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='192.168.2.99/24'
MTU=''
NAME='191 Gigabit Ethernet Adapter'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
USERCONTROL='no'
The restart your network
sudo /sbin/rcnetwork restart
You should at the very least be able to ping your NIC and the gatway
ping 192.168.2.99
ping 192.168.2.1
Report back.
I’m skeptical, because my ISP claims that dynamic is required, but at this point I’ll try most anything.
BOOTPROTO='static'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='192.168.2.99/24'
MTU=''
NAME='191 Gigabit Ethernet Adapter'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
USERCONTROL='no'
Changed and restarted.
sudo /sbin/rcnetwork restart
redirecting to systemctl
You should at the very least be able to ping your NIC and the gatway
ping 192.168.2.99
PING 192.168.2.99 (192.168.2.99) 56(84) bytes of data
64 bytes from 192.168.2.99; icmp_seq=1 ttl=64 time=0.073 ms
64 bytes from 192.168.2.99; icmp_seq=2 ttl=64 time=0.054 ms
64 bytes from 192.168.2.99; icmp_seq=3 ttl=64 time=0.052 ms
64 bytes from 192.168.2.99; icmp_seq=4 ttl=64 time=0.048 ms
64 bytes from 192.168.2.99; icmp_seq=5 ttl=64 time=0.054 ms
64 bytes from 192.168.2.99; icmp_seq=6 ttl=64 time=0.051 ms
64 bytes from 192.168.2.99; icmp_seq=7 ttl=64 time=0.054 ms
64 bytes from 192.168.2.99; icmp_seq=8 ttl=64 time=0.049 ms
64 bytes from 192.168.2.99; icmp_seq=9 ttl=64 time=0.048 ms
...and so on...
ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56 (84) bytes of data.
From 192.168.2.99 icmp_seq=1 Destination Host Unreachable
From 192.168.2.99 icmp_seq=2 Destination Host Unreachable
From 192.168.2.99 icmp_seq=3 Destination Host Unreachable
From 192.168.2.99 icmp_seq=4 Destination Host Unreachable
From 192.168.2.99 icmp_seq=5 Destination Host Unreachable
From 192.168.2.99 icmp_seq=6 Destination Host Unreachable
From 192.168.2.99 icmp_seq=7 Destination Host Unreachable
From 192.168.2.99 icmp_seq=8 Destination Host Unreachable
From 192.168.2.99 icmp_seq=9 Destination Host Unreachable
...and so on...
Report back.
There it is.
I want to be sure that you should be connecting to a 192.168.2.x network. When your windows computer is connected, what IP address is it using? Lets, check if you have the right network…
ipconfig /all
I wonder if your router is authenticating by MAC address or similar? Maybe you need to access your router web config from windows machine to check…
This is what I got when I plugged the ethernet cable into the laptop, but did not disable the wireless. The name of the laptop is MSH-JBURGES-LPT and it belongs to USD #266. The Lease Obtained time of the Ethernet adapter Local Area Connection is when I plugged the cable into the laptop.
Windows IP Configuration
Host Name . . . . . . . . . . . . : MSH-JBURGES-LPT
Primary Dns Suffix . . . . . . . : mhs.usd266.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mhs.usd266.com
Belkin
Belkin
usd266.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : Belkin
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controller
Physical Address. . . . . . . . . : 00-1C-23-58-6B-3D
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
Lease Obtained. . . . . . . . . . : Sunday, January 06, 2013 10:38:34 PM
Lease Expires . . . . . . . . . . : Monday, January 18, 2038 9:14:07 PM
Ethernet adapter Wireless Network Connection:
Connection-specific DNS Suffix . : Belkin
Description . . . . . . . . . . . : Intel(R) Wireless WiFi Link 4965AGN
Physical Address. . . . . . . . . : 00-1F-3B-CC-02-47
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
Lease Obtained. . . . . . . . . . : Sunday, January 06, 2013 8:23:24 PM
Lease Expires . . . . . . . . . . : Monday, January 18, 2038 9:14:07 PM
Okay, I suggest you restart your router. Completely remove the power for 30 seconds and restart. Then see if you can connect via DHCP again.