eth0 will not start

trashbird1240 · 07-12-2007, 04:57 AM

Okay, I feel like I've tried everything: I've just upgraded to Slackware 12 and my ethernet interface will not start at boot. I've configured rc.inet1.conf with the ip address, I've tried it with "USE_DHCP" equal to YES and NO or ""; I blacklisted ipv6, as I was getting "No IPV6 routers present"; I can get it going using dhclient or dhcpcd. I've commented and uncommented the line for the card in /etc/udev/rules.d/network-rules. I had to add "/sbin/modprobe e100" to rc.modules to get it recognized. That was all I had to do in Slackware 11.

The card is an intel e100.

If you need more info, go ahead and ask. I need any help I can get.

Thanks,
Joel

rylan76 · 07-12-2007, 10:19 AM

Not sure if this will help, but I got my unsupported NIC (at least, unsupported by the stock Fedora Core 6 distro) going in Linux by doing the following.

1. Downloaded the NIC driver from RealTek (for the RealTek 8168B Gigabit Ethernet NIC)
2. Compiled the NIC driver against my kernel source. I have a self-compiled 2.6.18.1 kernel - you'll need your kernel source tree configured and available to be able to compile a NIC driver (as far as I know)
3. Ok, then I had a nic_driver.ko (kernel module) file.
4. To make it start at boot, I put the following into my /etc/rc.local - not sure if it works the same way in Slackware but this script (in FC6) is run every time the system starts:

insmod ./home/rylan/network_driver/r1000_v1.05/src/r1000.ko speed=100 duplex=1 autoneg=1

/sbin/ifconfig eth0 169.254.255.20 netmask 255.255.255.0 broadcast 169.254.255.255 txqueuelen 2000 up

route add default gw 169.254.255.100 eth0

(putting the insmod... line automatically made my NIC be eth0 - not sure how that works...)

This made my box have the IP 169.254.255.20, with my DSL router configured as default gateway 169.254.255.100. (You might, or might not need the txqueuelen parameter... not sure)

I. e. I think it is (once again) some of the automagics on your new Slackware distro that has gone haywire. I've run into lots of automagics problems before, and I've always solved them by bypassing the automagical stuff and doing stuff manually and by hand... maybe this is part of your problem?

raska · 07-12-2007, 10:37 AM

Quote:

Originally Posted by trashbird1240

....
The card is an intel e100

If you need more info, go ahead and ask. I need any help I can get.

Thanks,
Joel

I discovered upon my first boot on Slackware 12 that the e100 driver is blacklisted in the /etc/modprobe.d/blacklist file so it doesn't load when booting up. Just comment the blacklist line:

Code:

# Alternate Intel EtherExpress Pro/100 support driver.  List it
# here so it won't conflict with an already-loaded eepro100 module.
###blacklist e100

Hope this actually helps you

onebuck · 07-12-2007, 11:10 AM

Quote:

Originally Posted by trashbird1240

Okay, I feel like I've tried everything: I've just upgraded to Slackware 12 and my ethernet interface will not start at boot. I've configured rc.inet1.conf with the ip address, I've tried it with "USE_DHCP" equal to YES and NO or ""; I blacklisted ipv6, as I was getting "No IPV6 routers present"; I can get it going using dhclient or dhcpcd. I've commented and uncommented the line for the card in /etc/udev/rules.d/network-rules. I had to add "/sbin/modprobe e100" to rc.modules to get it recognized. That was all I had to do in Slackware 11.

The card is an intel e100.

If you need more info, go ahead and ask. I need any help I can get.

Thanks,
Joel

Hi,

You upgraded the system? Not a fresh install.

The errors for IPV6 can be ignored for now. Just telling you no 'IPV6'.

What kernel are you using? From cli 'uname -a' will get you the kernel version.
Post your '/etc/rc.d/rc.inet1.conf'.

For the '2.6.21.5-smp #1 SMP' kernel the module '/lib/modules/2.6.21.5-smp/kernel/drivers/e100.ko' can be loaded via /etc/rc.d/rc.modules.

BTW, do a 'ls -al /etc/rc.d' to make sure the links are correct for the '/etc/rc.d/rc.modules'.

I would setup a static IP first, 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 208.69.32.130               #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.

If the static IP works then you can edit the '/etc/rc.d/rc.inet1.conf' file, after you save it. Then be sure to restart inet as root by '/etc/rc.d/rc.inet1 restart'.

If you want dhcp then use the /etc/rc.d/rc.inet1.conf' option 'USE_DHCP[0]="Y"', note the device [0]. Set that to your device within the proper stanza of the file.

trashbird1240 · 07-12-2007, 01:49 PM

Quote:

Originally Posted by onebuck

Hi,

You upgraded the system? Not a fresh install.

Correct. I got a bit confused about what to do with the *.new config files; is it possible that in trying to merge them I screwed up both the old and new config files?

Quote:

The errors for IPV6 can be ignored for now. Just telling you no 'IPV6'.

Correct; I no longer get the IPV6 error, but I also still don't get the network.

Quote:

What kernel are you using? From cli 'uname -a' will get you the kernel version.

I'm using 2.6.21.5-smp

Quote:

Post your '/etc/rc.d/rc.inet1.conf'.

I will If I'm still having these problems after trying everything else. All I've done is fill in the ip address that DHCP gives me every time (it's the same every time).

Quote:

For the '2.6.21.5-smp #1 SMP' kernel the module '/lib/modules/2.6.21.5-smp/kernel/drivers/e100.ko' can be loaded via /etc/rc.d/rc.modules.

Done. I remembered that I had to do this when we switched getting wireless from our landlord to our own cable router.

Quote:

BTW, do a 'ls -al /etc/rc.d' to make sure the links are correct for the '/etc/rc.d/rc.modules'.

Yes, at first I thought it was just that I still had the hugesmp.s kernel image installed. I re-installed the generic kernel; do I need to reinstall the modules package? Would that help? I've had to add the module to the rc.module-2.6.21.5-smp file.

Quote:

You should have your '/etc/resolv.conf' setup with your 'ISP DNS' nameservers.

This is a prime culprit: I had forgotten about resolv.conf; but I did netconfig and it was still the same old story (though it didn't "probe" the network card like it used to).

Quote:

If you want dhcp then use the /etc/rc.d/rc.inet1.conf' option 'USE_DHCP[0]="Y"', note the device [0]. Set that to your device within the proper stanza of the file.

That's the thing: there's no need for me to use DHCP, but it's the only thing that will jumpstart the connection. My concern is if my wife has to restart the computer during the day; you know, I could just put "dhcpcd" in rc.local, but that's a work-around; it wasn't needed before.

@rylan76: thanks for your help, but I'm pretty sure this is a slackware11->12 upgrade problem.

@raska: yeah, I thought that was funny! I removed the blacklist for e100 (that is commented it) when I went in to blacklist ipv6.

Thanks, this is all very helpful. I'm going to start with resolv.conf as soon as I get home.

Joel

onebuck · 07-12-2007, 08:24 PM

Quote:

Originally Posted by trashbird1240

Correct. I got a bit confused about what to do with the *.new config files; is it possible that in trying to merge them I screwed up both the old and new config files?

Correct; I no longer get the IPV6 error, but I also still don't get the network.

I'm using 2.6.21.5-smp

I will If I'm still having these problems after trying everything else. All I've done is fill in the ip address that DHCP gives me every time (it's the same every time).

Done. I remembered that I had to do this when we switched getting wireless from our landlord to our own cable router.

Yes, at first I thought it was just that I still had the hugesmp.s kernel image installed. I re-installed the generic kernel; do I need to reinstall the modules package? Would that help? I've had to add the module to the rc.module-2.6.21.5-smp file.

This is a prime culprit: I had forgotten about resolv.conf; but I did netconfig and it was still the same old story (though it didn't "probe" the network card like it used to).

That's the thing: there's no need for me to use DHCP, but it's the only thing that will jumpstart the connection. My concern is if my wife has to restart the computer during the day; you know, I could just put "dhcpcd" in rc.local, but that's a work-around; it wasn't needed before.

@rylan76: thanks for your help, but I'm pretty sure this is a slackware11->12 upgrade problem.

@raska: yeah, I thought that was funny! I removed the blacklist for e100 (that is commented it) when I went in to blacklist ipv6.

Thanks, this is all very helpful. I'm going to start with resolv.conf as soon as I get home.

Joel

Hi,

Post the '/etc/rc.d/rc.inet1.conf' file, if you have something you don't want someone to see then block it. In this file there is nothing that effects your security wise except the keys.

Just block those by 'XXX " them out.

No it is not dhcp that will jump start, use a static IP.

I would setup a static IP first, 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 208.69.32.130               #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. After you find that the static works then use the information to edit or generate a new /etc/rc.d/rc.inet1.conf.

You can restart init via the '/etc/rc.d/rc.inet1 restart' issue.

BTW, blacklisting IPV6 will not solve this problem. The error message just states no route for 'IPV6', if there were then the 'IPV6' would load. This can be ignored!

Make certain that the module for your device is loaded via the 'lsmod command, do a 'man lsmod' to get a understanding for the command. As said, just load the module via '/etc/rc.d/rc.module' by uncommenting a module line or include a 'modprobe <device>' if the driver is not already compiled in.

Quote:

@rylan76: thanks for your help, but I'm pretty sure this is a slackware11->12 upgrade problem.

This is not a Slackware upgrade problem but a user that failed to follow the proper upgrade methods. You either missed something or didn't follow the instructions or failed to read all the documentation.

You shoudld read the Slackware 12.0 CHANGES_AND_HINTS.TXT, UPGRADE.TXT and RELEASE_NOTES!

trashbird1240 · 07-13-2007, 05:03 AM

Quote:

Originally Posted by onebuck

This is not a Slackware upgrade problem but a user that failed to follow the proper upgrade methods. You either missed something or didn't follow the instructions or failed to read all the documentation.

You shoudld read the Slackware 12.0 CHANGES_AND_HINTS.TXT, UPGRADE.TXT and RELEASE_NOTES!

Okay, let's establish a few things:

I did everything that you suggested already -- with the exception of posting rc.inet1.conf because I was at work, rather than at home where the file was located

I've also done a few other things, like adjusting udev rules and blacklisting and un-blacklisting things.

I really appreciate your help.

I read all those documents. I read them several times a day for three days before doing the upgrade. Is there something else I should have read?

I'm not using Fedora. I would count "user that failed to follow the upgrade procedures" as an "upgrade issue" --- meaning I upgraded and created this issue for myself. I'm not "blaming" anybody for this.

I know the card is working, I can get it to work using dhcpcd. Putting "YES" in the "USE_DHCP" field has no effect.

Here I am using your method to set up a static ip:

Code:

/home/joel Super-User>ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:12:3F:A2:2E:1D  
          inet addr:209.6.178.201  Bcast:255.255.255.255  Mask:255.255.255.0
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:283465 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1501 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:19045534 (18.1 MiB)  TX bytes:256244 (250.2 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:986 errors:0 dropped:0 overruns:0 frame:0
          TX packets:986 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:263386 (257.2 KiB)  TX bytes:263386 (257.2 KiB)

That's the output of ifconfig when the card is working, now I'll disable it using rc.inet1 restart:

Code:

/home/joel Super-User>/etc/rc.d/rc.inet1 restart
/home/joel Super-User>ifconfig   
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:986 errors:0 dropped:0 overruns:0 frame:0
          TX packets:986 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:263386 (257.2 KiB)  TX bytes:263386 (257.2 KiB)

/home/joel Super-User>ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:12:3F:A2:2E:1D  
          inet addr:209.6.178.201  Bcast:255.255.255.255  Mask:255.255.255.0
          BROADCAST NOTRAILERS MULTICAST  MTU:1500  Metric:1
          RX packets:283573 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1501 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:19052656 (18.1 MiB)  TX bytes:256244 (250.2 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:986 errors:0 dropped:0 overruns:0 frame:0
          TX packets:986 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:263386 (257.2 KiB)  TX bytes:263386 (257.2 KiB)

/home/joel Super-User>ifconfig eth0 209.6.178.201
/home/joel Super-User>route add default gw 10.16.0.1
SIOCADDRT: No such process
/home/joel Super-User>route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
209.6.178.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
/home/joel Super-User>route add default gw 201.6.178.1
SIOCADDRT: No such process
/home/joel Super-User>ifconfig eth0 up
/home/joel Super-User>ping 
Usage: ping [-LRUbdfnqrvVaA] [-c count] [-i interval] [-w deadline]
            [-p pattern] [-s packetsize] [-t ttl] [-I interface or address]
            [-M mtu discovery hint] [-S sndbuf]
            [ -T timestamp option ] [ -Q tos ] [hop1 ...] destination
/home/joel Super-User>ping 201.6.178.1
connect: Network is unreachable
/home/joel Super-User>ping google.com
ping: unknown host google.com
/home/joel Super-User>ping 208.69.32.130
connect: Network is unreachable
/home/joel Super-User>route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
209.6.178.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
/home/joel Super-User>

Here's my rc.inet1.conf:

Code:

# /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]=""
NETMASK[0]=""
USE_DHCP[0]="YES"
DHCP_HOSTNAME[0]=""

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

# Config information for eth2:
IPADDR[2]=""
NETMASK[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=""

# 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 these 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"
#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]="AuthMode=WPAPSK EncrypType=TKIP WPAPSK=7B1ABEEB5D197741923ED26727569C365E31212096A0EAFAD563B268BAD01CAF TxRate=0"
#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_ parameter
                                # defined in rc.wireless.conf, by prepending
                                # 'WLAN_' to the parameter's name. Useful for
                                # those with multiple wireless interfaces.
#WLAN_IWPRIV[4]="AuthMode=WPAPSK EncrypType=TKIP WPAPSK=thekey TxRate=0"
                                # 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 (space-separated, see the
                                # example).

Pretty exciting, eh? I've also tried this variant:

Code:

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

I have

Code:

/sbin/modprobe e100

in my rc.modules. That was all that was required before to get the connection going.

Code:

.-(~)---------------------------------------------------------------(joel@edna)-
`--> dmesg|grep e100
PCI: Firmware left 0000:03:08.0 e100 interrupts enabled, disabling
e100: Intel(R) PRO/100 Network Driver, 3.5.17-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
e100: eth0: e100_probe: addr 0xefbfb000, irq 17, MAC addr 00:12:3F:A2:2E:1D
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
.-(~)---------------------------------------------------------------(joel@edna)-
`-->

Okay, just as I was pasting that in, I noticed the word "disabling" at the top. Is that important?

There was also a note in UPGRADE.TXT about the udev rules needing to have numerical prefixes, so I changed /etc/udev/rules.d/network-devices.rules to /etc/udev/rules.d/75-network-devices.rules. Here's the current version:

Code:

.-(~)---------------------------------------------------------------(joel@edna)-
`--> cat /etc/udev/rules.d/75-network-devices.rules
# Local network rules to name your network cards.
# These rules were generated by nethelper.sh, but you can
# customize them.  By default, all rules are commented out.
# You will need to uncomment and edit them as needed.
# (If, for example, your machine has more than one network
# card and you need to be sure they will always be given
# the same name, like eth0, based on the MAC address)
#
# If you delete this file, /lib/udev/nethelper.sh will try to
# generate it again the next time udev is started.

#KERNEL=="rausb?", SYSFS{address}=="00:00:00:00:00:00", NAME="rausb0"
#KERNEL=="rausb?", SYSFS{address}=="00:11:50:a4:da:4c", NAME="rausb1"
#KERNEL=="cipsec?", SYSFS{address}=="00:0b:fc:f8:01:8f", NAME="cipsec0"
#KERNEL=="eth?", SYSFS{address}=="80:a2:00:12:2e:1d:3f:00", NAME="eth0"
# the line below was originally called eth1, joel changed to eth0
# based on the HWAddr field of ifconfig; 7-10-2007; 21:29
KERNEL=="eth?", ATTR{address}=="00:12:3f:a2:2e:1d", NAME="eth0"

Now, I never did anything with udev before, I didn't even know it was there, but I figured since I read it in UPGRADE.TXT, that it might be important, so I followed the instructions there. Now, I'll further note that this is a copy of an old file; it was not automatically generated "on first boot" as UPGRADE.TXT indicates.

Now, what did I miss?

Joel

erklaerbaer · 07-13-2007, 05:55 AM

USE_DHCP[0]="YES" -> USE_DHCP[0]="yes"

you really should read the documentation

trashbird1240 · 07-13-2007, 07:52 AM

Hi,

Thanks, changing "YES" to lowercase worked. I had tried that before and it had no effect. That was probably before I re-installed the kernel.

This raises the question of why I need to use DHCP, and why setting the static IP failed. I had a static IP set before and it worked fine. Maybe I'll mess with it some more now that I know how to get it to work. I want to upgrade my workplace machine, too, so I want to get this all right first.

Thanks for pointing out that I need to read documentation. I read a lot of documentation before I post my questions, as well as looking at other forums for potential solutions from people who've already run into difficulty. Where would you have suggested I looked to find the answer to this question? I read a lot of stuff, but that doesn't matter if I was reading the wrong stuff. Please point me in the right direction.

Thanks again for all your help.

Joel

onebuck · 07-13-2007, 07:59 AM

Hi,
Yours;

Code:

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

Should be;

Code:

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

Not to be smart but you should read the docs for understanding not just preview.

trashbird1240 · 07-13-2007, 08:14 AM

Okay, thanks for your suggestion on setting up the static IP. I'll see if it works after I get home tonight.

Quote:

Originally Posted by onebuck

Hi,

Not to be smart but you should read the docs for understanding not just preview.

To be stupid, then? Which documentation?

Joel

erklaerbaer · 07-13-2007, 09:59 AM

Quote:

I had tried that before and it had no effect.

hmm

Quote:

If USE_DHCP[interface] is set to "yes",

that's in the head of rc.inet1.conf
and

Quote:

if [ "${USE_DHCP[$i]}" = "yes" ]; then

is in rc.inet1 itself. as you can see it's a simple comparison.

the rc scripts are (almost) plain english, so if they don't work as expected, take a look.
"use the source, luke"

don't worry though. simple errors like these are sometimes the hardest to spot.

raska · 07-13-2007, 10:12 AM

Quote:

Originally Posted by trashbird1240

...

Code:

.-(~)---------------------------------------------------------------(joel@edna)-
`--> dmesg|grep e100
PCI: Firmware left 0000:03:08.0 e100 interrupts enabled, disabling
e100: Intel(R) PRO/100 Network Driver, 3.5.17-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
e100: eth0: e100_probe: addr 0xefbfb000, irq 17, MAC addr 00:12:3F:A2:2E:1D
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
.-(~)---------------------------------------------------------------(joel@edna)-
`-->

Okay, just as I was pasting that in, I noticed the word "disabling" at the top. Is that important?...

I just came in a little late on this thread now, I just wanted to say that it looks like the disabling notice is not important, I also have it on this machine (office) and the network card works just fine:

Code:

salvador@it009sam:~$ dmesg |grep e100
PCI: Firmware left 0000:06:08.0 e100 interrupts enabled, disabling
e100: Intel(R) PRO/100 Network Driver, 3.5.17-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
e100: eth0: e100_probe: addr 0xfe401000, irq 21, MAC addr 00:16:76:06:F1:75
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex

So everything is working fine now, right Joel?

trashbird1240 · 07-13-2007, 11:33 AM

Yeah, it's solved. Thank you to everybody for weighing in.

I definitely agree that simple errors are the hardest to spot, especially when it comes to spelling. That's the dull other edge of the double-edged sword of text-based configuration. I'm grateful for the sharper side (it's way better than clicking through endless dialog boxes).

My main concern now is getting it to work with the static ip since (a) that's what I've got and (b) that's what I've got at work.

Thanks again,
Joel

onebuck · 07-13-2007, 11:11 PM

Hi,

What problems are you having with the static IP setup?