Help !!! Im Fed up - Network died

English Network/Internet
1

Hi everyone im completely dessperate by now afther downloading and installing different version of linux i finally found one that istalls namely (opensuse11) but installing it over and over is really getting to me now. Here is the deal i bought a new motherboard a gigabyte GA-ep45-dq6 the one with the 4 gigabit rtl8111 network adapters onboard

After installing the network works and i have internet but then one reboot and its dead. Now not i tried a more than one suggestion listed on the forum and none of them are working for me even downloaded the ones of realtek’s site but as a linux noob im totally stumped i follow the instructions for compiling the thing but just keeps getting errors. I tried everything and some of the commands listed dont work for me …

Pleeaasse someone help im sick of vista and want something new and due to the excelent support i want it to be opensuse but without internet its useless to me.

Thank you for listening to all my rantings :’(

2

Hi,

If you want someone here to help you, you will have to be more specific about the problem scenario:

  1. How do you get out to the Internet? Directly? Via a gateway device? Is the troubled system located in a local network?
    Please provide details.

  2. How does your computer nic interface get its Ip stack data?
    Statically? Dinamically from a DHCP device in your local network?

  3. Have you enabled the firewall feature of the system?

Now, reboot your Open Suse 11 system, get a command line prompt, and run the next commands:

  1. ifconfig -a

Tell us wich one of them is the one your system uses to go the Internet. Once you have identified the name corresponding to the nic, get also the content of the file /etc/sysconfig/network/ifcfg-<name>
For example, if you see if the list a logical device name like eth0, then you get the file /etc/sysconfig/network/ifcfg-eth0

  1. route

  2. cat /etc/resolv.conf

  3. Get also the ouput of lspci and lsmod.
    lspci will let you identify your nic vendor and lsmod will list all the kernel modules loaded, among them, the one corresponding to it.

Regards.

3

On Thu, 14 Aug 2008 16:46:03 GMT
Osculim <Osculim@no-mx.forums.opensuse.org> wrote:

>
> Hi everyone im completely dessperate by now afther downloading and
> installing different version of linux i finally found one that istalls
> namely (opensuse11) but installing it over and over is really getting
> to me now. Here is the deal i bought a new motherboard a gigabyte
> GA-ep45-dq6 the one with the 4 gigabit rtl8111 network adapters onboard
>
>
> After installing the network works and i have internet but then one
> reboot and its dead. Now not i tried a more than one suggestion listed
> on the forum and none of them are working for me even downloaded the
> ones of realtek’s site but as a linux noob im totally stumped i follow
> the instructions for compiling the thing but just keeps getting errors.
> I tried everything and some of the commands listed dont work for me …
>
>
> Pleeaasse someone help im sick of vista and want something new and due
> to the excelent support i want it to be opensuse but without internet
> its useless to me.
>
> Thank you for listening to all my rantings :’(
>
>

Rantings are good… even better when they’re done like you just did…
“Please help” is always a good way to start! {Smile}

Let me start with… NICE motherboard! Good choice!

Ok, so it works (worked?!) until you rebooted. That means the network DOES
work, just isn’t right now.

Would you be willing to provide some information and try some commands? I
know you’ve tried before … so I apologize if I go over something that’s
been covered previously. Remember that sometimes it just takes a fresh
perspective on things…

I am guessing you’re connecting through the rtl8111/rtl8168 ethernet.
(guessing! not assuming! don’t go there! {Grin} )

With the system booted, please provide the output for the following commands:

(as root) (in a terminal, console, konsole…)

ifconfig -a

route -n

The first should list several devices, eth0, lo, maybe more if you have other
network devices (wireless or bluetooth maybe).

The second should list the devices, their address masks and the default
gateway. It’s the gateway we’re really interested in, but everything is
important.

Some other questions:

How did you set up the network in yast -> network settings?

Did it see the rtl8111/8168 device? Did it say “dhcp” after it?

In the yast → network settings → global (tab)…

Are you using ‘network-manager mode’ or ‘traditional mode’. Please select
‘traditional mode’, save and restart the computer. This is often the cause
of many ‘won’t connect on reboot’ issues.

In the global tab, you may also wish to disable IPV6, as it does give a small
speed improvement. You will certainly have to reboot if you change that.

If you’ll answer these questions and try those commands, we’ll see where to
go to next.

Loni

–
L R Nix
lornix@lornix.com

4

sorry im a complete noob ive tried running ifconfig - a and route command and get a “command not found message” not found. im using dsl no firewall. Just installed another network card and immediately the internet is working again it seems its the onboard card thats causing the problem according to another post there are problems with the specific model and can be fixed using the driver from realtek but i havent got a clue how to install it. I did try the readme but those steps dont work. Thanx for the replies so far.

5

Thank you for the replies so far. Yes i went the yast route to setup the network dhcp also tried fixed ip ifconfig and route command gives a “command not found” What i did now is to disable the onboard network cards (all 4 of em) and plugged in a 10/100 40buck cheepo card and it works ill reboot and disable the cheap one and enable the onboard ones and do the lsmod and ispci commands and list them here for you EDIT: Sorry yes in global settings i tried both those settings you mentioned

6

On Thu, 14 Aug 2008 19:46:03 GMT
Osculim <Osculim@no-mx.forums.opensuse.org> wrote:

>
> Thank you for the replies so far. Yes i went the yast route to setup the
> network dhcp also tried fixed ip ifconfig and route command gives a
> “command not found” What i did now is to disable the onboard network
> cards (all 4 of em) and plugged in a 10/100 40buck cheepo card and it
> works ill reboot and disable the cheap one and enable the onboard ones
> and do the lsmod and ispci commands and list them here for you
>
>

did you run those commands as ROOT?!? It was (rather plainly) indicated to
run those commands as the user root. You’ve dealt with other responses which
told you the same thing, including how to become or log in as root.

su - root
<give root’s password>

and then the commands…

But if you’ve found another solution, great. enjoy. No need to supply the
information.

Loni

–
L R Nix
lornix@lornix.com
{Grrr}

7

sorry for posting another repeat to my own question but it seems im unable to edit the post again. here is the lsmod info you requested

osculim@linux-hyfz:~> lsmod
Module Size Used by
ip6t_LOG 23428 7
xt_tcpudp 19584 2
xt_pkttype 18304 3
ipt_LOG 22788 8
xt_limit 19076 15
binfmt_misc 28040 1
snd_pcm_oss 64256 0
snd_mixer_oss 33408 1 snd_pcm_oss
snd_seq 73664 0
snd_seq_device 25100 1 snd_seq
nls_utf8 18432 1
nvidia 7148480 24
ip6t_REJECT 21376 3
nf_conntrack_ipv6 33528 4
ipt_REJECT 20352 3
xt_state 18944 8
iptable_mangle 19712 0
iptable_nat 23688 0
nf_nat 35736 1 iptable_nat
iptable_filter 19840 1
ip6table_mangle 19584 0
nf_conntrack_netbios_ns 19200 0
nf_conntrack_ipv4 27652 7 iptable_nat,nf_nat
nf_conntrack 79188 6 nf_conntrack_ipv6,xt_state,iptable_nat,nf_nat,nf_conntrack_netbios_ns,nf_conntrack_ipv4
ip_tables 30224 3 iptable_mangle,iptable_nat,iptable_filter
cpufreq_conservative 24456 0
cpufreq_userspace 22660 0
cpufreq_powersave 18176 0
acpi_cpufreq 26380 0
speedstep_lib 21508 0
ip6table_filter 19712 1
ip6_tables 31376 3 ip6t_LOG,ip6table_mangle,ip6table_filter
x_tables 33668 11 ip6t_LOG,xt_tcpudp,xt_pkttype,ipt_LOG,xt_limit,ip6t_REJECT,ipt_REJECT,xt_state,iptable_nat,ip_tables,ip6_tables
ipv6 281064 17 ip6t_REJECT,nf_conntrack_ipv6,ip6table_mangle
microcode 30608 0
firmware_class 25984 1 microcode
fuse 66332 3
loop 35332 0
dm_mod 78676 0
joydev 28224 0
snd_hda_intel 386588 3
snd_pcm 100100 2 snd_pcm_oss,snd_hda_intel
usbhid 60260 0
snd_timer 40712 2 snd_seq,snd_pcm
i2c_i801 26128 0
hid 53708 1 usbhid
snd_page_alloc 27400 2 snd_hda_intel,snd_pcm
snd_hwdep 26372 1 snd_hda_intel
agpgart 50868 1 nvidia
ohci1394 48432 0
snd 79544 14 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_pcm,snd_timer,snd_hwdep
r8169 47748 0
sr_mod 33320 1
ieee1394 107016 1 ohci1394
ff_memless 21896 1 usbhid
serio_raw 23428 0
rtc_cmos 27168 0
button 25360 0
i2c_core 41108 2 nvidia,i2c_i801
rtc_core 37148 1 rtc_cmos
cdrom 50588 1 sr_mod
rtc_lib 19328 1 rtc_core
soundcore 24264 1 snd
sg 52020 0
sd_mod 45208 6
ehci_hcd 52492 0
uhci_hcd 40848 0
usbcore 164812 4 usbhid,ehci_hcd,uhci_hcd
edd 26440 0
ext3 155912 3
mbcache 25348 1 ext3
jbd 73504 1 ext3
fan 22660 0
ahci 46216 5
pata_jmicron 22400 0
libata 176604 2 ahci,pata_jmicron
scsi_mod 168436 4 sr_mod,sg,sd_mod,libata
dock 27536 1 libata
thermal 40348 0
processor 67504 4 acpi_cpufreq,thermal

osculim@dhcppc3:~> lspci
bash: lspci: command not found
osculim@dhcppc3:~> cat /etc/resolv.conf

BEGIN INFO

Modified_by: dhcpcd

Backup: /etc/resolv.conf.saved.by.dhcpcd.eth2

Process: dhcpcd

Process_id: 2479

Script: /sbin/modify_resolvconf

Saveto:

Info: This is a temporary resolv.conf created by service dhcpcd.

The previous file has been saved and will be restored later.

If you don’t like your resolv.conf to be changed, you

can set MODIFY_{RESOLV,NAMED}_CONF_DYNAMICALLY=no. This

variables are placed in /etc/sysconfig/network/config.

You can also configure service dhcpcd not to modify it.

If you don’t like dhcpcd to change your nameserver

settings

then either set DHCLIENT_MODIFY_RESOLV_CONF=no

in /etc/sysconfig/network/dhcp, or

set MODIFY_RESOLV_CONF_DYNAMICALLY=no in

/etc/sysconfig/network/config or (manually) use dhcpcd

with -R. If you only want to keep your searchlist, set

DHCLIENT_KEEP_SEARCHLIST=yes in /etc/sysconfig/network/dhcp or

(manually) use the -K option.

END INFO

domain site

nameserver 10.0.0.2

hope this info helps. None of the rest of the commands wanted to work for me

8

>>How did you set up the network in yast -> network settings?

>>Did it see the rtl8111/8168 device? Did it say “dhcp” after it?

>>In the yast → network settings → global (tab)…

>>Are you using ‘network-manager mode’ or ‘traditional mode’. Please select
>>‘traditional mode’, save and restart the computer. This is often the
>>cause of many ‘won’t connect on reboot’ issues.

Before you do anything else I would strongly advise trying the above again
if you have not done so already. After you have set the mode to
traditional, be sure to go back through all of the configuration screens.
Reset the IP/Mask/Gateway/DNS settings. Save the setting off and then
reboot. Once you have rebooted test again if it still doesn’t work, go
back into the settings and check that they are still set. If not, set them
again. Sometimes when you switch from Network Managaer to the traditional
(ifup) it loses the settings any you have to hammer on it to get it to
stick. I really wish they would remaster the OS11 disks with ifup
defaulted or network manager fixed, it’s getting to be ridiculous the
number of new users getting snagged on something that is fundamentally
needed.

9

Hi,

Still some of the information I suggested missed. Nevertheless, I can see from the lsmod dump in your latest post that the ethernet module loaded is Realtek r8169:

…
snd 79544 14 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,s nd_hda_intel,snd_pcm,snd_timer,snd_hwdep
r8169 47748 0
sr_mod 33320 1
ieee1394 107016 1 ohci1394
…

Well, bad news, that driver is known to be eventually acting up.
That rules out likely Ip configuration issues.

As you have pointed out, the suggested circumvention is grasping the vendor version, not the included in the Open Suse distro, build it up and installing in your system.
In order to do that you will have to get the code tarball, install the kernel headers (probably also the kernel package) from the official Open Suse source repositories and build the kernel module according to the instructions provided by the vendor.

There are some post in this forum that deals with the same problem. However, keep in mind that the vendor driver is not part of the Open Suse distro and probably never be.
So, you will be on your own with that driver.

Regards.

10

Well i got it working with the help of all you guys /gals seems to be the driver. Finally got the one installed from realtek’s site and it works just a shame i will have to use the old card each time the kernel is updated

Thanx all for the assistance :slight_smile:

11

On Fri, 15 Aug 2008 05:26:03 GMT
Osculim <Osculim@no-mx.forums.opensuse.org> wrote:

>
> Well i got it working with the help of all you guys /gals seems to be
> the driver. Finally got the one installed from realtek’s site and it
> works just a shame i will have to use the old card each time the kernel
> is updated
>
> Thanx all for the assistance :slight_smile:
>
>

{Grin} Well, if you don’t delete the files used to install the working
driver… then every time the kernel updates, you only need to quickly
reinstall the new driver, rmmod the icky driver, modprobe the new driver…
and you’re back up!

Yeah yeah, easier said than done maybe… but that’s how I used to handle the
madwifi drivers long ago.

Loni

–
L R Nix
lornix@lornix.com

12

On Fri, 15 Aug 2008 06:13:41 GMT
L R Nix <lornix@lornix.com> wrote:

> On Fri, 15 Aug 2008 05:26:03 GMT
> Osculim <Osculim@no-mx.forums.opensuse.org> wrote:
>
> >
> > Well i got it working with the help of all you guys /gals seems to be
> > the driver. Finally got the one installed from realtek’s site and it
> > works just a shame i will have to use the old card each time the kernel
> > is updated
> >
> > Thanx all for the assistance :slight_smile:
> >
> >
>
> {Grin} Well, if you don’t delete the files used to install the working
> driver… then every time the kernel updates, you only need to quickly
> reinstall the new driver, rmmod the icky driver, modprobe the new driver…
> and you’re back up!
>
> Yeah yeah, easier said than done maybe… but that’s how I used to handle
> the madwifi drivers long ago.
>
> Loni
>

Darn it! I always think of something else to say… (and don’t anyone say…
“you can edit your posts…”… I’m not using the web-based forum interface).

If you blacklist the icky driver, it won’t even load when the new kernel
boots. So after recompiling the realtek driver, install it, modprobe it…
and you’re up!!

Really… last thought… that’s it… no more… pressing send…

–
L R Nix
lornix@lornix.com