Hi,
After a recent installation and update I am having problems connecting to the internet even after following the steps in “http://opensuse.swerdna.org/susenic.html, Configure a network card in Suse/openSUSE…” It doesn’t always connect when I boot and there is no connection icon on the panel nor the KDE desktop. Can someone assist me with this problem? All help will be appreciated.
You installed? Was this a new clean install.
Was /home from a previous install?
You managed to update though?
Seems from the reference you gave that (like me) you’re using the “traditional method with ifup” in Yast.
You said “and there is no connection icon on … the KDE desktop”. What do you mean “connection icon”? I’ve not seen an icon on my KDE desktop associated with my cable broadband nor my earlier adsl broadband. Maybe you’re not using cable or adsl. So please clarify.
Hi - thanks for the quick replies. This was a re-installation after I became unable to boot the previous one. It is located on an external hard drive. The internal drive is full.
It has Win 7, Ubuntu, Mint, & PCLinuxOS. I was unable to boot it after I deleted an adjacent partition that was a failed Arch Linux installation. The previous desktop was gnome. As for the reference to a “connection icon”, that may be the wrong wording. I usually see a symbol on the desktop that shows whether I have a network connection or not. I’m typing this on the pclos and it has a black circle in the lower rt. corner of the bottom panel that has a red X if not connected and a green check mark if it is connected. That is what I was looking for or something similar. Here is a copy of “fdisk -l”:
[root@localhost ~]# fdisk -l
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x28000000Device Boot Start End Blocks Id System
/dev/sda1 * 2048 206847 102400 7 HPFS/NTFS
/dev/sda2 206848 205152255 102472704 7 HPFS/NTFS
/dev/sda3 205163341 625141759 209989209+ 5 Extended
/dev/sda5 205163343 250039439 22438048+ 83 Linux
/dev/sda6 250039503 258219359 4089928+ 82 Linux swap / Solaris
/dev/sda7 258219423 386890559 64335568+ 83 Linux
/dev/sda8 386891776 425953279 19530752 83 Linux
/dev/sda9 425955328 504078335 39061504 83 Linux
/dev/sda10 504080384 620107775 58013696 83 Linux
/dev/sda11 620109824 625141759 2515968 82 Linux swap / SolarisDisk /dev/sdb: 500.1 GB, 500107861504 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773167 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000c1471Device Boot Start End Blocks Id System
/dev/sdb1 * 63 208844 104391 7 HPFS/NTFS
/dev/sdb2 208896 27054079 13422592 83 Linux
/dev/sdb3 27054080 114430994 43688457+ 83 Linux
[root@localhost ~]#
Thanks for your assistance. Also, I lost internet connection after 70+ updates and re-booting.
I’m not sure what fdisk has to do with your network?
I’d be more interested in the repos you have:
zypper lr -d
Did the updates you did last have network updates
/var/log/zypp/history
If you followed 'http://opensuse.swerdna.org/susenic.html, then you used the manual configuration of the nic, rather than a networkmanager. The icon lower right of the screen is an applet for networkmanager. In your case there shouldn’t be one because you’re not using a networkmanager.
So the lack of an icon is a red herring, forget about it.
Now back to the intermittent connection. Can you describe this a little more than “doesn’t always connect when I boot”. Does that mean it drops in and out every few minutes after you boot. Or sometimes you get a connection that completely stays until you reboot and other times is completely absent until you reboot. Or you can get to some websites but not to others. Or, …?
Also, is your network interface a wireless device or a wired ethernet device, and what is it, make and model?
Hi,
Here is the output of “zypper lr -d”:
dhcppc0:~ # zypper lr -d
| Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
–±---------------------------------±---------------------------------±--------±--------±---------±-------±-----------------------------------------------------------------------±-------
1 | Updates-for-openSUSE-11.4-11.4-0 | Updates for openSUSE 11.4 11.4-0 | Yes | Yes | 99 | rpm-md | Index of /update/11.4 |
2 | openSUSE-11.4-11.4-0 | openSUSE-11.4-11.4-0 | Yes | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/ata-TSSTcorp_DVD+_-RW_TS-H653B,/dev/sr0 |
3 | repo-debug | openSUSE-11.4-Debug | No | Yes | 99 | NONE | Index of /debug/distribution/11.4/repo/oss |
4 | repo-debug-update | openSUSE-11.4-Update-Debug | No | Yes | 99 | NONE | Index of /debug/update/11.4 |
5 | repo-non-oss | openSUSE-11.4-Non-Oss | Yes | Yes | 99 | yast2 | Index of /distribution/11.4/repo/non-oss |
6 | repo-oss | openSUSE-11.4-Oss | Yes | Yes | 99 | yast2 | Index of /distribution/11.4/repo/oss |
7 | repo-source | openSUSE-11.4-Source | No | Yes | 99 | NONE | Index of /source/distribution/11.4/repo/oss |
Many of the updates were "/etc/sysconfig/ … I didn’t post them here because there were 2,425 lines of code (/var/log/zypp/history ). I didn’t know if “fdisk -l” would be relevant or not. Today I booted into Suse using Super Grub Disk and my Ethernet connection was made automatically. I have a wired eth0 connection via a ZyXEL P-600 Series Router that was bought through my ISP.
I sure appreciate the attention you all have given to this matter. Thank you.
When you have a time the internet seems off
Try logging in to the router
Report back
And please report back what you get when you run these commands:
Hi,
Here are the results of the four commands you requested:
dhcppc0:~ # /sbin/lspci -nn | grep thernet
00:19.0 Ethernet controller [0200]: Intel Corporation 82562V-2 10/100 Network Connection [8086:10c0] (rev 02)
dhcppc0:~ # cat /etc/sysconfig/network/routes
cat: /etc/sysconfig/network/routes: No such file or directory
dhcppc0:~ # cat /etc/sysconfig/network/config | grep DNS_STATIC_SERVERS
NETCONFIG_DNS_STATIC_SERVERS=""
dhcppc0:~ # /usr/sbin/hwinfo --netcard | grep Driver
Driver: “e1000e”
Driver Modules: “e1000e”
Driver Info #0:
Driver Status: e1000e is active
Driver Activation Cmd: “modprobe e1000e”
I hope this might shed some light on my problem. Also how would I log-in to the router. I can actually see if Ethernet is connected or not by observing if it’s light is on. Thanks again for your help.
I’m trying to discover if the fault is in the kernel/network-card processes or in the network-card/wiring process.
The first thing to try: when the light is not on after a reboot, wiggle the ethernet cable in the socket and see if it comes on. And, swap out the cable, try another. If these don’t define the problem, then proceed with the rest, below.
You did not answer one of my questions, so I’ll ask it a different way, twice:
These are two questions, please answer them both.
Also, please run this command in two instances, once when the connection is not working and once when the connection is working:
/usr/sbin/hwinfo --netcard | grep Driver; /sbin/ifconfig | grep Bcast
Please post two results, one for each case.
Is this a Dell? If it is, then what model? If not, then what is it?
Is this a laptop or a desktop computer?
Hi,
I rebooted and the light came on and stayed on. Rebooted again and light comes on briefly during the boot menu process then went off. The boot splash screen goes on and off a couple of times. It starts with the horizontal line moving briefly, then blank for a second, then line gets about halfway under gecko, then blank for a second, then line completes it’s path. I wiggle the ethernet cable connection with no change. I then disconnected and reconnected and the light came on. I’m using a Dell Inspiron 530S Desktop. The ethernet cable is less than three months old. One time I went into Yast > Network Devices and deselected ipv6 and rebooted and had a connection. When I rechecked Network Devices ipv6 was automatically selected again. I then deselected it and saved. On reboot there was no connection. Following is the output of the requested commands:
dhcppc0:~ # /usr/sbin/hwinfo --netcard | grep Driver; /sbin/ifconfig | grep Bcast
Driver: “e1000e”
Driver Modules: “e1000e”
Driver Info #0:
Driver Status: e1000e is active
Driver Activation Cmd: “modprobe e1000e”
inet addr:192.168.1.33 Bcast:192.168.1.255 Mask:255.255.255.0
dhcppc0:~ # /usr/sbin/hwinfo --netcard | grep Driver; /sbin/ifconfig | grep Bcast
Driver: “e1000e”
Driver Modules: “e1000e”
Driver Info #0:
Driver Status: e1000e is active
Driver Activation Cmd: “modprobe e1000e”
inet addr:192.168.1.33 Bcast:192.168.1.255 Mask:255.255.255.0
The output was the same. Thanks for your help.
Hi,
Today I discovered a convoluted method to connect to the internet. I found that if I follow this procedure I’ll connect every time (so far): YaST > Network Devices > Network Settings > Global Options > IPv6 Protocol Settings > Disable (this gives a Warning: “To apply this change a reboot is needed”) Click OK on the Warning > Reboot. I discovered that if I disable IPv6 and select OK on the Network Settings form (which apparently saves the disabling of IPv6) and then reboot, there is no connection. Is there any way to get around this complicated method. Where is IPv4?
I tried to understand what you penned above. But struggle with it.
Try adding this to the boot argument: ipv6.disable=1
Hi,
I have decided to use Network Manager instead of ifup method. The “help” dialog for the Network Settings form says to use the traditional ifup method if not using a desktop (Gnome or KDE). I am using the KDE Desktop. Thank you very much for your assistance.
Kind regards,
Glen