Hi Hugh,
Thank you for your response and excuse for insufficient info...
I'll add next details in your text.
Regards,
jh
------------ Původní zpráva ------------
Od: D. Hugh Redelmeier <hugh(a)mimosa.com>
Předmět: Re: LAN Card doesn't activate
Datum: 11.1.2010 02:10:49
----------------------------------------
| From: j.halifax . <j.halifax(a)seznam.cz>
| Doesn't anybody know why my LAN Cards don't get active after rebooting
| despite of having the check-box for automated activation checked?
|
| After every reboot I have to open Network option in System->Admin menu
| and activate cards manual way.
You haven't told us much about your setup.
Yes, sorry, I believed that it is
some basic mistake I have done.
Assuming you are using Fedora, what version are you using?
uname -r tells me
2.6.31.9-174.fc12.x86_64
Why do you say "cards"? How many do you have? In how many systems?
I
have 3 cards to Internet DSL and 2 different networks
Are your cards managed by Network Manager, or by the old fashioned
system-config-network etc. scripts? I find that the two systems can
interfere.
I don't use Network manager, LAN devices are configured as it
follows:
eth0 Link encap:Ethernet HWaddr 00:1B:11:B1:5D:0D
inet addr:195.39.130.92 Bcast:195.39.130.255 Mask:255.255.255.0
inet6 addr: fe80::21b:11ff:feb1:5d0d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:247782 errors:0 dropped:0 overruns:0 frame:0
TX packets:211249 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:156440806 (149.1 MiB) TX bytes:50247350 (47.9 MiB)
Interrupt:21 Base address:0xca00
"cat /etc/sysconfig/networking/devices/ifcfg-eth0" gives:
# VIA Technologies, Inc. VT6105/VT6106S [Rhine-III]
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=none
TYPE=Ethernet
NM_CONTROLLED=no
IPV6INIT=no
USERCTL=no
NAME="System eth0"
UUID=5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03
HWADDR=00:1b:11:b1:5d:0d
PEERROUTES=yes
IPADDR=195.39.130.92
NETMASK=255.255.255.0
GATEWAY=195.39.130.89
DNS2=195.226.224.72
DNS1=195.226.224.74
eth2 Link encap:Ethernet HWaddr 00:19:5B:38:B7:36
inet addr:10.255.250.37 Bcast:10.255.250.255 Mask:255.255.255.0
inet6 addr: fe80::219:5bff:fe38:b736/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:761309 errors:0 dropped:0 overruns:0 frame:0
TX packets:195979 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:84964475 (81.0 MiB) TX bytes:148972906 (142.0 MiB)
Interrupt:22 Base address:0xa900
"cat /etc/sysconfig/networking/devices/ifcfg-eth2" gives:
DEVICE=eth2
BOOTPROTO=none
NETMASK=255.255.255.0
TYPE=Ethernet
HWADDR=00:19:5b:38:b7:36
IPADDR=10.255.250.37
NM_CONTROLLED=no
IPV6INIT=no
ONBOOT=yes
USERCTL=no
DNS2=195.226.224.72
DNS1=195.226.224.74
GATEWAY=195.39.130.89
MTU=1500
eth3 Link encap:Ethernet HWaddr 00:1B:11:B1:1C:D4
inet addr:172.16.110.3 Bcast:172.16.110.255 Mask:255.255.255.0
inet6 addr: fe80::21b:11ff:feb1:1cd4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:47237 errors:0 dropped:0 overruns:0 frame:0
TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4589511 (4.3 MiB) TX bytes:3610 (3.5 KiB)
Interrupt:18 Base address:0x6800
"cat /etc/sysconfig/networking/devices/ifcfg-eth3" gives me:
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
DEVICE=eth3
BOOTPROTO=none
NETMASK=255.255.255.0
TYPE=Ethernet
HWADDR=00:1b:11:b1:1c:d4
IPADDR=172.16.110.3
NM_CONTROLLED=no
IPV6INIT=no
ONBOOT=yes
USERCTL=no
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:11088 errors:0 dropped:0 overruns:0 frame:0
TX packets:11088 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:942300 (920.2 KiB) TX bytes:942300 (920.2 KiB)
On three notebooks, I use Network Manager: it is better at handling
changes in connectivity.
For some reason, the notebook running Fedora 11 and the one running
Fedora 12 don't automatically connect to the wired network: I have to
poke the NetworkManager icon to get a menu and select from that menu
the wired interface. For wireless, that would make sense, but for
wired that seems silly: after all I wired the connection.
Isn't it similar to
my problems?
Does this correspond to what you are experiencing?
I guess that it does. :(