LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 07-29-2011, 07:46 PM   #1
vivanguarda
Member
 
Registered: Sep 2008
Location: RJ-Brazil
Distribution: Slackware
Posts: 166

Rep: Reputation: 4
Ethernet Problem After Reboot


Good Evening, slackers!!!

I tryed a lot of searching, but I'm going back here for helping.

I am having problem to connect 13.37 system using a via-rhine NIC.

At first, it is pinging normal and connecting too, but after reboot it broke down. I did a static ip config and several ways to correct it, using netconfig, manual procedures for eth0 and netmask up, editions in /etc/udev/rules.d/70-persistent-net.rules (name) and a /etc/rc.d/rc.local entry using command /etc/rc.d/rc.inet1 eth0_restart. But, unfortunately it is not function.


1)Is Leet using hal or udev to maintain ethernet config?
2)I note an MacAddres diference, so 70-persistent-net.rules has a "00:17:31:d2:ea:ue number and ifconfig -a output is 00:17:31: D2:EA:UE. Then, can MAC case sensitive register be a ethernet problem ?

Any idea?

Last edited by vivanguarda; 07-30-2011 at 07:13 AM.
 
Old 07-31-2011, 05:48 AM   #2
kikinovak
Senior Member
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: Slackware, Slackware64
Posts: 1,736

Rep: Reputation: 834Reputation: 834Reputation: 834Reputation: 834Reputation: 834Reputation: 834Reputation: 834
Just an idea. Check your switch if you have one, or check the one that comes with your DSL routerbox. Malfunctioning switches have the nasty tendency to appear to continue to work sometimes and can drive you crazy.
 
Old 07-31-2011, 06:05 AM   #3
eSelix
Senior Member
 
Registered: Oct 2009
Location: Wroclaw, Poland
Distribution: Arch, Kubuntu
Posts: 1,223

Rep: Reputation: 307Reputation: 307Reputation: 307Reputation: 307
Quote:
Originally Posted by vivanguarda View Post
2)I note an MacAddres diference, so 70-persistent-net.rules has a "00:17:31:d2:ea:ue number and ifconfig -a output is 00:17:31: D2:EA:UE. Then, can MAC case sensitive register be a ethernet problem ?
Case characters has no meaning, but "UE" in your MAC is incorrect number. You can use only these 0123456789ABCDEF.

Last edited by eSelix; 07-31-2011 at 06:07 AM.
 
Old 07-31-2011, 09:09 AM   #4
vivanguarda
Member
 
Registered: Sep 2008
Location: RJ-Brazil
Distribution: Slackware
Posts: 166

Original Poster
Rep: Reputation: 4
Thanks, my dear!!

In fact, I tested MAC in another system and occured the same. Then doubt about MAC and case sensitive is over.

# vi 70-persistent-net.rules

# PCI device 0x1106:0x3065 (via-rhine)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:17:31:d2:db:5c", AT
TR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"


#ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:17:31: D2: DB:5C

Now, I am looking for another possibility and I agreed hardware problem and tested switch and cable before. It is ok! Then,if I reboot ifconfig -a output show eth0 but no ip. What is this?
 
Old 08-02-2011, 05:42 PM   #5
vivanguarda
Member
 
Registered: Sep 2008
Location: RJ-Brazil
Distribution: Slackware
Posts: 166

Original Poster
Rep: Reputation: 4
Sorry a double post, but it's very curious.
I am having problem using 13.37 system yet. But in a 13.1 it is ok.
Using 13.37 if I try ping my gateway there is: network is unreachable output.If I ping 127.0.0.1 it is ok . A little bit info output about the problem.


root@maq1:/home/normal# ping 201.37.x.xxx
connect: Network is unreachable


#depmode -a occurs without output

#lsmod
Module Size Used by
vboxnetadp 6727 0
...
via_rhine 17845 0
mii 3334 1 via_rhine
ipv6 236629 14


root@maq1:/home/normal# dmesg
[ 0.235872] pci 0000:00:13.0: PCI bridge to [bus 04-04]
[ 0.236004] pci 0000:00:13.0: bridge window [io 0xf000-0x0000] (disabled)
[ 0.236009] pci 0000:00:13.0: bridge window [mem 0xfbf00000-0xfbffffff]
[ 0.236015] pci 0000:00:13.0: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[ 0.236080] pci 0000:00:13.1: PCI bridge to [bus 05-05] (subtractive decode)
[ 0.236179] pci 0000:00:13.1: bridge window [io 0xf000-0x0000] (disabled)
[ 0.236184] pci 0000:00:13.1: bridge window [mem 0xfff00000-0x000fffff] (disabled)
[ 0.236190] pci 0000:00:13.1: bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
[ 0.236194] pci 0000:00:13.1: bridge window [io 0x0000-0xffff] (subtractive decode)
[ 0.236197] pci 0000:00:13.1: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
[ 0.236201] pci 0000:00:13.1: bridge window [mem 0x20000000-0xffffffff] (subtractive decode)
[ 0.236224] pci_bus 0000:00: on NUMA node 0
[ 0.236228] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 0.236382] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P7._PRT]
[ 0.236412] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0PA._PRT]
[ 0.236498] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
[ 0.236529] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NBPG._PRT]
[ 0.236566] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NBP0._PRT]
[ 0.249347] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 10 11 12 14 15)
[ 0.250064] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
[ 0.250769] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 *4 5 6 7 10 11 12 14 15)
[ 0.251468] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 10 11 12 14 15)
[ 0.252187] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[ 0.253043] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[ 0.253884] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[ 0.254707] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *10 11 12 14 15)
[ 0.255411] HEST: Table is not found!

...
[ 0.310611] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.310711] pci 0000:00:00.0: MSI quirk detected; MSI disabled
[ 0.310827] pci 0000:00:01.0: disabling DAC on VIA PCI bridge
[ 0.310925] pci 0000:00:02.0: MSI quirk detected; subordinate MSI disabled

...

[ 4.192627] via-rhine.c:v1.10-LK1.4.3 2007-03-06 Written by Donald Becker
[ 4.192784] via-rhine 0000:00:12.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
[ 4.202762] rtc_cmos 00:02: RTC can wake from S4
[ 4.203527] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
[ 4.203661] rtc0: alarms up to one year, y3k, 114 bytes nvram
[ 4.204425] eth0: VIA Rhine II at 0xf8fff800, 00:11:d8:01:23:45, IRQ 23.
[ 4.205234] eth0: MII PHY found at address 1, status 0x786d advertising 01e1
...

[ 11.692128] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
[ 13.986540] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[ 15.200684] NET: Registered protocol family 10
[ 15.200937] lo: Disabled Privacy Extensions
[ 25.938014] eth0: no IPv6 routers present
[ 46.132279] vboxdrv: Found 1 processor cores.
[ 46.135986] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
[ 46.135991] vboxdrv: Successfully loaded version 4.0.8_OSE (interface 0x00180000).
[ 55.690230] start_kdeinit (2089): /proc/2089/oom_adj is deprecated, please use /proc/2089/oom_score_adj instead




I remember that at recently 13.1 install was made using a pci-nomsi feature ins this motherboard and 13.37 needn't it. System was installed in another board and then channged to it, in spite of being te same model asus a8v-mx.

Are there anything else to troubleshotting to correct it?

Last edited by vivanguarda; 08-02-2011 at 06:05 PM.
 
Old 08-03-2011, 08:21 AM   #6
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,292
Blog Entries: 3

Rep: Reputation: 1447Reputation: 1447Reputation: 1447Reputation: 1447Reputation: 1447Reputation: 1447Reputation: 1447Reputation: 1447Reputation: 1447Reputation: 1447
Hi,

First I suggest that you learn to use vbcode tags to encase you long lists/data. The # (code) and Quote are at the top of the reply window. By using the tags your posts will be cleaner therefore easier to read.

You say that a static IP was tested. Please try this setup for a static IP. Do as root from cli;
Code:
 ~#ifconfig -a                                        #get recognized devices
 ~#ifconfig eth0 192.168.0.10              #set to a available IP
 ~#route add default gw 192.168.0.1 #set to your gateway
 ~#route -n                                           #show the route table
 ~#ifconfig eth0 up                              #should be up already
 ~#ping 192.168.0.1                              #ping your gateway
 ~#ping 74.125.225.50                          #google.com IP
 ~#ping google.com                              #test DNS, if fail then                                                         
                                                                #check /etc/resolv.conf
You should have your '/etc/resolv.conf' setup with your 'ISP DNS' nameservers.
Code:
 sample '/etc/resolv.conf';
 search 192.168.0.1      
 
 nameserver xxx.xxx.xxx.xxx   #ISP DSN 'replace xxx.xxx.xxx.xxx
                           #with IP from your ISP
 nameserver 4.2.2.1                   #Verizon third level DNS
 nameserver 4.2.2.2
 nameserver 4.2.2.3
 nameserver 4.2.2.4
You really do not need all the third level DNS but choose one in addition to your ISP DNS.

If the above doesn't work then please provide the output for '/etc/rc.d/rc.inet1.conf', 'ifconfig','ifconfig -a' and 'route -n'. Be sure to have the '/etc/resolv.conf' setup properly. Please remember to use the vbcode tags.

HTH!
 
Old 08-03-2011, 10:54 PM   #7
vivanguarda
Member
 
Registered: Sep 2008
Location: RJ-Brazil
Distribution: Slackware
Posts: 166

Original Poster
Rep: Reputation: 4
ISP informs two nameserver 201.17.0.14 and 201.17.0.15. It is always used in /etc/resolv.conf, but in this case is lost also after reboot.

I don't understand about third level nameserver! Is it a better configuration for /etc/resolv.conf?

I will post '/etc/rc.d/rc.inet1.conf', 'ifconfig','ifconfig -a' and 'route -n' ouput on Friday!

Thanks about quote advice!
 
Old 08-03-2011, 11:20 PM   #8
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, FreeBSD 10.0
Posts: 3,415
Blog Entries: 15

Rep: Reputation: 965Reputation: 965Reputation: 965Reputation: 965Reputation: 965Reputation: 965Reputation: 965Reputation: 965
The kernel module for the VIA-Rhine NIC should load on boot. If it isn't you might have a bad Network Controller or a failing one.

You shouldn't also be having to mess too much with your network address allocation settings if you are using DHCP. Try running "netconfig" and reset the addressing to DCHP and your network as Home. Also, see if WICD is connecting as well if you are using it as the network configuration daemon.

Pinging 127.0.0.1 is the loopback/localhost address to see if the OS's DCHP is working. That's not going to tell you if your network is actually up.

Also check your cables and see if they are working as well. If you can ping your router/switch try pinging it's address (example: 192.168.1.1) and see if it responds, if not your router might be down. Try a 30/30/30 reset if needed. Check it with "ifconfig" to make sure you are getting the default gateway address. If you can access the router/switch's configuration page or script, try to see if you can access a website. If you can not connect you might have a problem with either your service or your line (this will have to be professionally diagnosed).

Also check and see if DNS is being resolved as well. If you have problems with your ISPs DNS, try the Google Public DNS servers:

8.8.8.8 and 8.8.4.4

and reboot your router.
 
Old 08-04-2011, 02:22 PM   #9
vivanguarda
Member
 
Registered: Sep 2008
Location: RJ-Brazil
Distribution: Slackware
Posts: 166

Original Poster
Rep: Reputation: 4
If you can not connect you might have a problem with either your service or your line (this will have to be professionally diagnosed).

1)In this network there are another 13.1 system machines, then I think router and ISP aren´t fault.


You shouldn't also be having to mess too much with your network address allocation settings if you are using DHCP. Try running "netconfig" and reset the addressing to DCHP and your network as Home. Also, see if WICD is connecting as well if you are using it as the network configuration daemon

2)In the past, I installed system in a hd and an Asus A8V-MX motherboard. Network step was made of using DHCP whose funcion was perfect. Now this problem occurs when I change hd for another motherboard in a same model A8V-MX. But I will try DHCP in this complete set.

Last edited by vivanguarda; 08-04-2011 at 02:26 PM.
 
Old 08-17-2011, 09:01 PM   #10
vivanguarda
Member
 
Registered: Sep 2008
Location: RJ-Brazil
Distribution: Slackware
Posts: 166

Original Poster
Rep: Reputation: 4
This is the problematic procedure output. If I run /etc/rc.d/rc.inet1 start system is ok. But, after reboot issue appears again.

1)I don't understand Verizon third level DNS, is it a way to maintain dns after reboot?

2)How can I fill /etc/resolv.conf if I use 201.17.0.14 (main) and 201.17.0.15 (secondary)dns?

3)Is this a correct resolv.conf using a Verizon third level DNS?
search 201.37.1.xxx (local IP)

nameserver 201.17.0.14 (main ISP dns )
nameserver 201.17.1.15 (secondary ISP dns)
nameserver 4.2.2.1 #Verizon third level DNS



Code:
#uname -r
Linux maq1 2.6.37.6-smp

#ifconfig –a

eth0      Link encap:Ethernet  HWaddr 00:08:54:31:54:D5
          inet6 addr: fe80::208:54ff:fe31:54d5/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:240 (240.0 b)  TX bytes:8006 (7.8 Kb)
          Interrupt:16 Base address:0xd800

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:16436  Metric:1
          RX packets:60 errors:0 dropped:0 overruns:0 frame:0
          TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4592 (4.4 Kb)  TX bytes:4592 (4.4 Kb


# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo


# /etc/rc.d/rc.inet1.conf
#
# This file contains the configuration settings for network interfaces.
# If USE_DHCP[interface] is set to "yes", this overrides any other settings.
# If you don't have an interface, leave the settings null ("").

# You can configure network interfaces other than eth0,eth1... by setting
# IFNAME[interface] to the interface's name. If IFNAME[interface] is unset
# or empty, it is assumed you're configuring eth<interface>.

# Several other parameters are available, the end of this file contains a
# comprehensive set of examples.

# =============================================================================

# Config information for eth0:
IPADDR[0]="201.37.1.105"
NETMASK[0]="255.255.255.0"
USE_DHCP[0]=""
DHCP_HOSTNAME[0]=""

# Config information for eth1:
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]=""
DHCP_HOSTNAME[1]=""

# Config information for eth2:
IPADDR[2]=""
ETMASK[2]=""
USE_DHCP[2]=""
DHCP_HOSTNAME[2]=""

# Config information for eth3:
IPADDR[3]=""
NETMASK[3]=""
USE_DHCP[3]=""
DHCP_HOSTNAME[3]=""

# Default gateway IP address:
GATEWAY="201.37.1.100"

# Change this to "yes" for debugging output to stdout.  Unfortunately,
# /sbin/hotplug seems to disable stdout so you'll only see debugging output
# when rc.inet1 is called directly.
DEBUG_ETH_UP="no"

## Example config information for wlan0.  Uncomment the lines you need and fill
## in your info.  (You may not need all of #DHCP_HOSTNAME[4]="icculus-wireless"
#DHCP_KEEPRESOLV[4]="yes"
#DHCP_KEEPNTP[4]="yes"
#DHCP_KEEPGW[4]="yes"
#DHCP_IPADDR[4]=""
#WLAN_ESSID[4]=BARRIER05
#WLAN_MODE[4]=Managed
##WLAN_RATE[4]="54M auto"
##WLAN_CHANNEL[4]="auto"
##WLAN_KEY[4]="D5AD1F04ACF048EC2D0B1C80C7"
##WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=96389dc66eaf7e6efd5b5523ae43c
7925ff4df2f8b7099495192d44a774fda16"
#WLAN_WPA[4]="wpa_supplicant"
#WLAN_WPADRIVER[4]="ndiswrapper"

## Some examples of additional network parameters that you can use.
## Config information for wlan0:
#IFNAME[4]="wlan0"              # Use a different interface name nstead of
                                # the default 'eth4'
#HWADDR[4]="00:01:23:45:67:89"  # Overrule the card's hardware MAC address
#MTU[4]=""                      # The default MTU is 1500, but you might need
                                # 1360 when you use NAT'ed IPSec traffic.
#DHCP_KEEPRESOLV[4]="yes"       # If you dont want /etc/resolv.conf overwritten
#DHCP_KEEPNTP[4]="yes"          # If you don't want ntp.conf overwritten
#DHCP_KEEPGW[4]="yes"           # If you don't want the DHCP server to change
                                # your default gateway
#DHCP_IPADDR[4]=""              # Request a specific IP address from the DHCP
                                # server
#WLAN_ESSID[4]=DARKSTAR         # Here, you can override _any_ parameterthese for your wireless network)
#IFNAME[4]="wlan0"
#IPADDR[4]=""
#NETMASK[4]=""
#USE_DHCP[4]="yes"
#DHCP_HOSTNAME[4]="icculus-wireless"
#DHCP_KEEPRESOLV[4]="yes"
#DHCP_KEEPNTP[4]="yes"#DHCP_KEEPGW[4]="yes"           # If you don't want the DHCP server to change
                                # your default gateway
#DHCP_IPADDR[4]=""              # Request a specific IP address from the DHCP
                                # server
#WLAN_ESSID[4]=DARKSTAR         # Here, you can override _any_ parameter
                                # defined in rc.wireless.conf, by prepending
                                # 'WLAN_' to the parameter's name. Useful for
                                # those with multiple wireless interfaces.
#WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=thekey"
                                # Some drivers require a private ioctl to be
                                # set through the iwpriv command. If more than
                                # one is required, you can place them in the
                                # IWPRIV parameter (separated with the pipe (|)
                                # character, see the example).


#vi /etc/resolv.conf
# Generated by NetworkManager
~
~

Last edited by vivanguarda; 08-19-2011 at 05:56 PM.
 
Old 08-22-2011, 02:33 PM   #11
vivanguarda
Member
 
Registered: Sep 2008
Location: RJ-Brazil
Distribution: Slackware
Posts: 166

Original Poster
Rep: Reputation: 4
I am realizing a slower connetion, but finally that problem is over!!!

I edited /etc/resolv.conf using the same ISP nameserver, but I did

# chattr -i /etc/resolv.conf

to prevent changes. By the way, networkmanager app was operating, but I didn't whether install it. I think it was started by rc.local input. Then was bingo!!!

chmod -x /etc/rc.d/rc.networkmanager

Important urls readings:
http://www.linuxquestions.org/questi...mputer-893058/
http://linuxmanpages.com/man5/resolv.conf.5.php
http://www.linuxquestions.org/questi...oblems-803523/

Thanks a lot!!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Ethernet controller missing after reboot _sluimers_ Linux - Networking 1 06-12-2011 01:34 AM
Fedora 14 - Ethernet interface does not get activated upon reboot Sreeram B S Linux - Networking 12 06-07-2011 02:08 PM
Problem with Linux reboot and connection via Ethernet port. linuxa Linux - Newbie 1 07-06-2010 07:39 AM
2.6.x kernel debugging over ethernet (without serial connection) and reboot anitemp Linux - Kernel 2 02-25-2009 07:23 PM
changing ethernet mac address and retaining the same after reboot guy24x Linux - Hardware 3 02-06-2009 06:51 AM


All times are GMT -5. The time now is 11:47 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration