RE: ethernet card not coming up on reboot
I have also noticed this issue, but if I have only once instance of the entry in rc.conf, everything works fine. Why not statically define the IP, though? That would be the best situation, IMHO. HTH Eric F Crist President AdTech Integrated Systems, Inc (612) 998-3588 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Luke Kearney Sent: Tuesday, May 25, 2004 11:42 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: ethernet card not coming up on reboot On Tue, 25 May 2004 17:58:04 -1000 [EMAIL PROTECTED] spake thus: Aloha I have a little annoyance on one of my boxes. The box has an Asus P4P800 mobo with a 2.6GHz P4 and 1GB of DDR-400 Ram. I have FreeBSD 5.2-RC1 loaded on a 120Gig SATA Hard disk. My ouput of uname -a: p4# uname -a FreeBSD p4.hawaii.rr.com 5.2-RC1 FreeBSD 5.2-RC1 #0: Sun Dec 7 22:15:14 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 The mobo has an onboard 3COM 3C940 Gbit LAN controller. This device is recognised during boot as sk0 and uses the SysKonnectPCI driver. The problem is that after a reboot a DHCP address is not assigned to sk0. Here is ifconfig -a after a reboot. p4# ifconfig -a sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::20c:6eff:fe91:dea6%sk0 prefixlen 64 scopeid 0x1 ether 00:0c:6e:91:de:a6 media: Ethernet autoselect (100baseTX full-duplex,flag0,flag1) status: active plip0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 Here is the output of resolv.conf and rc.conf p4# cat /etc/resolv.conf search hawaii.rr.com nameserver 24.25.227.66 nameserver 24.25.227.33 nameserver 24.25.227.64 p4# cat /etc/rc.conf # -- sysinstall generated deltas -- # Thu May 20 10:05:35 2004 # Created: Thu May 20 10:05:35 2004 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. hostname=p4.hawaii.rr.com ifconfig_sk0=DHCP linux_enable=YES nfs_client_enable=YES sshd_enable=YES usbd_enable=YES # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. # Enable network daemons for user convenience. # Created: Thu May 20 20:27:06 2004 # -- sysinstall generated deltas -- # Thu May 20 20:27:06 2004 ifconfig_sk0=DHCP hostname=p4.hawaii.rr.com # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. # Enable network daemons for user convenience. Notice that there is a second entry in rc.conf relating to sk0. If I enter /stand/sysinstall and choose configure then networking and then interfaces and then chooses DHCP, the fields are all populated with the correct information. I can then exit back to the # and when I then look at ifconfig -a I get some good stuff! p4# ifconfig -a sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::20c:6eff:fe91:dea6%sk0 prefixlen 64 scopeid 0x1 inet 192.168.1.103 netmask 0xff00 broadcast 192.168.1.255 ether 00:0c:6e:91:de:a6 media: Ethernet autoselect (100baseTX full-duplex,flag0,flag1) status: active plip0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 Notice I now have an inet line populated with an IP address. If I now look at rc.conf I get this p4# cat /etc/rc.conf # -- sysinstall generated deltas -- # Thu May 20 10:05:35 2004 # Created: Thu May 20 10:05:35 2004 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. hostname=p4.hawaii.rr.com ifconfig_sk0=DHCP linux_enable=YES nfs_client_enable=YES sshd_enable=YES usbd_enable=YES # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. # Enable network daemons for user convenience. # Created: Thu May 20 20:27:06 2004 # -- sysinstall generated deltas -- # Thu May 20 20:27:06 2004 ifconfig_sk0=DHCP hostname=p4.hawaii.rr.com # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. # Enable network daemons for user convenience. # Created: Tue May 25 16:17:31 2004 # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes
Re: RE: ethernet card not coming up on reboot
Aloha Eric and Luke I am aware that sysinstall will append to rc.conf. I went ahead and deleted all of the appends and rebooted. The ethernet did not come up on reboot. I had to use sysinstall to get an ip. And yes, it did append to rc.conf again. I will look into setting a static ip but I would like to know why this is happening. I have 3 other boxes that have FreeBSD on them and they don't have this problem. Robert - Original Message - From: Eric Crist [EMAIL PROTECTED] Date: Tuesday, May 25, 2004 7:30 pm Subject: RE: ethernet card not coming up on reboot I have also noticed this issue, but if I have only once instance of theentry in rc.conf, everything works fine. Why not statically define the IP, though? That would be the best situation, IMHO. HTH Eric F Crist President AdTech Integrated Systems, Inc (612) 998-3588 -Original Message- From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Luke Kearney Sent: Tuesday, May 25, 2004 11:42 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: ethernet card not coming up on reboot On Tue, 25 May 2004 17:58:04 -1000 [EMAIL PROTECTED] spake thus: Aloha I have a little annoyance on one of my boxes. The box has an Asus P4P800 mobo with a 2.6GHz P4 and 1GB of DDR-400 Ram. I have FreeBSD 5.2-RC1 loaded on a 120Gig SATA Hard disk. My ouput of uname -a: p4# uname -a FreeBSD p4.hawaii.rr.com 5.2-RC1 FreeBSD 5.2-RC1 #0: Sun Dec 7 22:15:14 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 The mobo has an onboard 3COM 3C940 Gbit LAN controller. This device is recognised during boot as sk0 and uses the SysKonnectPCI driver. The problem is that after a reboot a DHCP address is not assigned to sk0. Here is ifconfig -a after a reboot. p4# ifconfig -a sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::20c:6eff:fe91:dea6%sk0 prefixlen 64 scopeid 0x1 ether 00:0c:6e:91:de:a6 media: Ethernet autoselect (100baseTX full-duplex,flag0,flag1) status: active plip0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 Here is the output of resolv.conf and rc.conf p4# cat /etc/resolv.conf search hawaii.rr.com nameserver 24.25.227.66 nameserver 24.25.227.33 nameserver 24.25.227.64 p4# cat /etc/rc.conf # -- sysinstall generated deltas -- # Thu May 20 10:05:35 2004 # Created: Thu May 20 10:05:35 2004 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. hostname=p4.hawaii.rr.com ifconfig_sk0=DHCP linux_enable=YES nfs_client_enable=YES sshd_enable=YES usbd_enable=YES # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. # Enable network daemons for user convenience. # Created: Thu May 20 20:27:06 2004 # -- sysinstall generated deltas -- # Thu May 20 20:27:06 2004 ifconfig_sk0=DHCP hostname=p4.hawaii.rr.com # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. # Enable network daemons for user convenience. Notice that there is a second entry in rc.conf relating to sk0. If I enter /stand/sysinstall and choose configure then networking and then interfaces and then chooses DHCP, the fields are all populated with the correct information. I can then exit back to the # and when I then look at ifconfig -a I get some good stuff! p4# ifconfig -a sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::20c:6eff:fe91:dea6%sk0 prefixlen 64 scopeid 0x1 inet 192.168.1.103 netmask 0xff00 broadcast 192.168.1.255 ether 00:0c:6e:91:de:a6 media: Ethernet autoselect (100baseTX full-duplex,flag0,flag1) status: active plip0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 Notice I now have an inet line populated with an IP address. If I now look at rc.conf I get this p4# cat /etc/rc.conf # -- sysinstall generated deltas -- # Thu May 20 10:05:35 2004 # Created: Thu May 20 10:05:35 2004 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. hostname=p4.hawaii.rr.com ifconfig_sk0=DHCP linux_enable=YES nfs_client_enable=YES sshd_enable
Re: ethernet card not coming up on reboot
On Tue, 25 May 2004 20:00:12 -1000 [EMAIL PROTECTED] spake thus: Aloha Eric and Luke I am aware that sysinstall will append to rc.conf. I went ahead and deleted all of the appends and rebooted. The ethernet did not come up on reboot. I had to use sysinstall to get an ip. And yes, it did append to rc.conf again. I will look into setting a static ip but I would like to know why this is happening. I have 3 other boxes that have FreeBSD on them and they don't have this problem. Robert - Original Message - From: Eric Crist [EMAIL PROTECTED] Date: Tuesday, May 25, 2004 7:30 pm Subject: RE: ethernet card not coming up on reboot I have also noticed this issue, but if I have only once instance of theentry in rc.conf, everything works fine. Why not statically define the IP, though? That would be the best situation, IMHO. HTH Eric F Crist President AdTech Integrated Systems, Inc (612) 998-3588 -Original Message- From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Luke Kearney Sent: Tuesday, May 25, 2004 11:42 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: ethernet card not coming up on reboot On Tue, 25 May 2004 17:58:04 -1000 [EMAIL PROTECTED] spake thus: Aloha I have a little annoyance on one of my boxes. The box has an Asus P4P800 mobo with a 2.6GHz P4 and 1GB of DDR-400 Ram. I have FreeBSD 5.2-RC1 loaded on a 120Gig SATA Hard disk. My ouput of uname -a: p4# uname -a FreeBSD p4.hawaii.rr.com 5.2-RC1 FreeBSD 5.2-RC1 #0: Sun Dec 7 22:15:14 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 The mobo has an onboard 3COM 3C940 Gbit LAN controller. This device is recognised during boot as sk0 and uses the SysKonnectPCI driver. The problem is that after a reboot a DHCP address is not assigned to sk0. Here is ifconfig -a after a reboot. p4# ifconfig -a sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::20c:6eff:fe91:dea6%sk0 prefixlen 64 scopeid 0x1 ether 00:0c:6e:91:de:a6 media: Ethernet autoselect (100baseTX full-duplex,flag0,flag1) status: active plip0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 Here is the output of resolv.conf and rc.conf p4# cat /etc/resolv.conf search hawaii.rr.com nameserver 24.25.227.66 nameserver 24.25.227.33 nameserver 24.25.227.64 p4# cat /etc/rc.conf # -- sysinstall generated deltas -- # Thu May 20 10:05:35 2004 # Created: Thu May 20 10:05:35 2004 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. hostname=p4.hawaii.rr.com ifconfig_sk0=DHCP linux_enable=YES nfs_client_enable=YES sshd_enable=YES usbd_enable=YES # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. # Enable network daemons for user convenience. # Created: Thu May 20 20:27:06 2004 # -- sysinstall generated deltas -- # Thu May 20 20:27:06 2004 ifconfig_sk0=DHCP hostname=p4.hawaii.rr.com # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. # Enable network daemons for user convenience. Notice that there is a second entry in rc.conf relating to sk0. If I enter /stand/sysinstall and choose configure then networking and then interfaces and then chooses DHCP, the fields are all populated with the correct information. I can then exit back to the # and when I then look at ifconfig -a I get some good stuff! p4# ifconfig -a sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::20c:6eff:fe91:dea6%sk0 prefixlen 64 scopeid 0x1 inet 192.168.1.103 netmask 0xff00 broadcast 192.168.1.255 ether 00:0c:6e:91:de:a6 media: Ethernet autoselect (100baseTX full-duplex,flag0,flag1) status: active plip0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 Notice I now have an inet line populated with an IP address. If I now look at rc.conf I get this p4# cat /etc/rc.conf # -- sysinstall generated deltas -- # Thu May 20 10:05:35 2004 # Created: Thu May 20 10:05:35 2004 # Enable network daemons for user convenience. # Please make all changes
Re: ethernet card not coming up on reboot
Subject: Re: ethernet card not coming up on reboot On Tue, 25 May 2004 20:00:12 -1000 [EMAIL PROTECTED] spake thus: Aloha Eric and Luke I am aware that sysinstall will append to rc.conf. I went ahead and deleted all of the appends and rebooted. The ethernet did not come up on reboot. I had to use sysinstall to get an ip. And yes, it did append to rc.conf again. I will look into setting a static ip but I would like to know why this is happening. I have 3 other boxes that have FreeBSD on them and they don't have this problem. Robert - Original Message - SNIP On Tuesday, May 25, 2004 8:15 pm Luke Kearney [EMAIL PROTECTED] wrote: When you used /stand/sysinstall again did you reboot to get the IP or did you bring up the interface by hand? I am wondering if having only one config line in rc.conf gives you no IP upon boot whether or not having booted and go no address can you get one by using netstart or not? eg #sh /etc/netstart This should re-read your rc.conf file and execute the network related cmds. After sh /etc/netstart I get : hw.bus.devctl_disable: 1- 1 (then the lo0 printou) dhclient already running? (pid-221) and ifconfig -a unchanged. have to use sysinsstall. One more shot in the dark and believe me this is a shot in the dark, try changing the line in rc.conf to ifconfig_sk0=UP and then through rc.local run dhclient as a separate script. The net effect being that you start the interface before trying to get an IP as a separate process. I tried this but it didn't change anything...if I did it right? I edited rc.conf and changed the line [ifconfig_sk0=DHCP] to [ifconfig_sk0=UP] and created /usr/local/etc/rc.d/rc.local to read ifconfig_sk0=DHCP When I did this I could never i initialize DHCP. Even sysinstall failed. as a side note, during boot, the sequence delays for over a minute during starting DHClient. It can't initialize sk0 but sysinstall can. Go figure? Just out of curiousity, your other three machines that don't have this problem, are they all identical to the machine that does? Somehow I think they are probably all unique in which case we can continue to focus on the machine at hand. You are absolutely right! My other boxes are all frankenputers. Robert HTH LukeK -- Luke Kearney [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: ethernet card not coming up on reboot
Before you run the netstart command, you need to kill all processes named dhclient. You can accomplish this with a: #killall -9 dhclient And then, #sh /etc/netstart Eric F Crist President AdTech Integrated Systems, Inc (612) 998-3588 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 26, 2004 12:45 PM To: Luke Kearney Cc: Eric Crist; [EMAIL PROTECTED] Subject: Re: ethernet card not coming up on reboot Subject: Re: ethernet card not coming up on reboot On Tue, 25 May 2004 20:00:12 -1000 [EMAIL PROTECTED] spake thus: Aloha Eric and Luke I am aware that sysinstall will append to rc.conf. I went ahead and deleted all of the appends and rebooted. The ethernet did not come up on reboot. I had to use sysinstall to get an ip. And yes, it did append to rc.conf again. I will look into setting a static ip but I would like to know why this is happening. I have 3 other boxes that have FreeBSD on them and they don't have this problem. Robert - Original Message - SNIP On Tuesday, May 25, 2004 8:15 pm Luke Kearney [EMAIL PROTECTED] wrote: When you used /stand/sysinstall again did you reboot to get the IP or did you bring up the interface by hand? I am wondering if having only one config line in rc.conf gives you no IP upon boot whether or not having booted and go no address can you get one by using netstart or not? eg #sh /etc/netstart This should re-read your rc.conf file and execute the network related cmds. After sh /etc/netstart I get : hw.bus.devctl_disable: 1- 1 (then the lo0 printou) dhclient already running? (pid-221) and ifconfig -a unchanged. have to use sysinsstall. One more shot in the dark and believe me this is a shot in the dark, try changing the line in rc.conf to ifconfig_sk0=UP and then through rc.local run dhclient as a separate script. The net effect being that you start the interface before trying to get an IP as a separate process. I tried this but it didn't change anything...if I did it right? I edited rc.conf and changed the line [ifconfig_sk0=DHCP] to [ifconfig_sk0=UP] and created /usr/local/etc/rc.d/rc.local to read ifconfig_sk0=DHCP When I did this I could never i initialize DHCP. Even sysinstall failed. as a side note, during boot, the sequence delays for over a minute during starting DHClient. It can't initialize sk0 but sysinstall can. Go figure? Just out of curiousity, your other three machines that don't have this problem, are they all identical to the machine that does? Somehow I think they are probably all unique in which case we can continue to focus on the machine at hand. You are absolutely right! My other boxes are all frankenputers. Robert HTH LukeK -- Luke Kearney [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RE: ethernet card not coming up on reboot
Aloha and Mahalo Okay, that works. I dropped out of gnome and logged ina s root. I deleted all the append data in rc.conf and I deleted /usr/local/etc/rc.d/rc.local. I then rebooted. When I came back up ifconfig showed no ip address. I then did the killall -9 dhclient and the sh /etc/netstart. After that completed ifconfig showed the ip address. So, what's happening? Is there a sequence problem or do I need to have a script run to kill dhclient and then run netstart? Thanks for your time helping with this problem. Robert - Original Message - From: Eric Crist [EMAIL PROTECTED] Date: Wednesday, May 26, 2004 12:53 pm Subject: RE: ethernet card not coming up on reboot Before you run the netstart command, you need to kill all processes named dhclient. You can accomplish this with a: #killall -9 dhclient And then, #sh /etc/netstart Eric F Crist President AdTech Integrated Systems, Inc (612) 998-3588 -Original Message- From: [EMAIL PROTECTED] [EMAIL PROTECTED] Sent: Wednesday, May 26, 2004 12:45 PM To: Luke Kearney Cc: Eric Crist; [EMAIL PROTECTED] Subject: Re: ethernet card not coming up on reboot Subject: Re: ethernet card not coming up on reboot On Tue, 25 May 2004 20:00:12 -1000 [EMAIL PROTECTED] spake thus: Aloha Eric and Luke I am aware that sysinstall will append to rc.conf. I went ahead and deleted all of the appends and rebooted. The ethernet did not come up on reboot. I had to use sysinstall to get an ip. And yes, it did append to rc.conf again. I will look into setting a static ip but I would like to know why this is happening. I have 3 other boxes that have FreeBSD on them and they don't have this problem. Robert - Original Message - SNIP On Tuesday, May 25, 2004 8:15 pm Luke Kearney [EMAIL PROTECTED] wrote: When you used /stand/sysinstall again did you reboot to get the IP or did you bring up the interface by hand? I am wondering if having only one config line in rc.conf gives you no IP upon boot whether or not having booted and go no address can you get one by using netstart or not? eg #sh /etc/netstart This should re-read your rc.conf file and execute the network related cmds. After sh /etc/netstart I get : hw.bus.devctl_disable: 1- 1 (then the lo0 printou) dhclient already running? (pid-221) and ifconfig -a unchanged. have to use sysinsstall. One more shot in the dark and believe me this is a shot in the dark, try changing the line in rc.conf to ifconfig_sk0=UP and then through rc.local run dhclient as a separate script. The net effect being that you start the interface before trying to get an IP as a separate process. I tried this but it didn't change anything...if I did it right? I editedrc.conf and changed the line [ifconfig_sk0=DHCP] to [ifconfig_sk0=UP] and created /usr/local/etc/rc.d/rc.local to read ifconfig_sk0=DHCP When I did this I could never i initialize DHCP. Even sysinstall failed. as a side note, during boot, the sequence delays for over a minute during starting DHClient. It can't initialize sk0 but sysinstall can. Go figure? Just out of curiousity, your other three machines that don't have this problem, are they all identical to the machine that does? Somehow I think they are probably all unique in which case we can continue to focus on the machine at hand. You are absolutely right! My other boxes are all frankenputers. Robert HTH LukeK -- Luke Kearney [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ethernet card not coming up on reboot
Aloha I have a little annoyance on one of my boxes. The box has an Asus P4P800 mobo with a 2.6GHz P4 and 1GB of DDR-400 Ram. I have FreeBSD 5.2-RC1 loaded on a 120Gig SATA Hard disk. My ouput of uname -a: p4# uname -a FreeBSD p4.hawaii.rr.com 5.2-RC1 FreeBSD 5.2-RC1 #0: Sun Dec 7 22:15:14 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 The mobo has an onboard 3COM 3C940 Gbit LAN controller. This device is recognised during boot as sk0 and uses the SysKonnectPCI driver. The problem is that after a reboot a DHCP address is not assigned to sk0. Here is ifconfig -a after a reboot. p4# ifconfig -a sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::20c:6eff:fe91:dea6%sk0 prefixlen 64 scopeid 0x1 ether 00:0c:6e:91:de:a6 media: Ethernet autoselect (100baseTX full-duplex,flag0,flag1) status: active plip0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 Here is the output of resolv.conf and rc.conf p4# cat /etc/resolv.conf search hawaii.rr.com nameserver 24.25.227.66 nameserver 24.25.227.33 nameserver 24.25.227.64 p4# cat /etc/rc.conf # -- sysinstall generated deltas -- # Thu May 20 10:05:35 2004 # Created: Thu May 20 10:05:35 2004 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. hostname=p4.hawaii.rr.com ifconfig_sk0=DHCP linux_enable=YES nfs_client_enable=YES sshd_enable=YES usbd_enable=YES # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. # Enable network daemons for user convenience. # Created: Thu May 20 20:27:06 2004 # -- sysinstall generated deltas -- # Thu May 20 20:27:06 2004 ifconfig_sk0=DHCP hostname=p4.hawaii.rr.com # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. # Enable network daemons for user convenience. Notice that there is a second entry in rc.conf relating to sk0. If I enter /stand/sysinstall and choose configure then networking and then interfaces and then chooses DHCP, the fields are all populated with the correct information. I can then exit back to the # and when I then look at ifconfig -a I get some good stuff! p4# ifconfig -a sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::20c:6eff:fe91:dea6%sk0 prefixlen 64 scopeid 0x1 inet 192.168.1.103 netmask 0xff00 broadcast 192.168.1.255 ether 00:0c:6e:91:de:a6 media: Ethernet autoselect (100baseTX full-duplex,flag0,flag1) status: active plip0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 Notice I now have an inet line populated with an IP address. If I now look at rc.conf I get this p4# cat /etc/rc.conf # -- sysinstall generated deltas -- # Thu May 20 10:05:35 2004 # Created: Thu May 20 10:05:35 2004 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. hostname=p4.hawaii.rr.com ifconfig_sk0=DHCP linux_enable=YES nfs_client_enable=YES sshd_enable=YES usbd_enable=YES # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. # Enable network daemons for user convenience. # Created: Thu May 20 20:27:06 2004 # -- sysinstall generated deltas -- # Thu May 20 20:27:06 2004 ifconfig_sk0=DHCP hostname=p4.hawaii.rr.com # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. # Enable network daemons for user convenience. # Created: Tue May 25 16:17:31 2004 # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. # Enable network daemons for user convenience. # Created: Tue May 25 17:28:40 2004 # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. # Enable network daemons for user convenience. # Created: Tue May 25 17:31:13 2004 # -- sysinstall generated deltas -- # Tue May 25 17:31:13 2004 ifconfig_sk0=DHCP hostname=p4.hawaii.rr.com Still another entry for sk0!! As I stated at the begimming of this epic, this is merely an annoyance. I don't reboot all that often and when I do I usually log in as a normal user. Of course, at that time,
Re: ethernet card not coming up on reboot
On Tue, 25 May 2004 17:58:04 -1000 [EMAIL PROTECTED] spake thus: Aloha I have a little annoyance on one of my boxes. The box has an Asus P4P800 mobo with a 2.6GHz P4 and 1GB of DDR-400 Ram. I have FreeBSD 5.2-RC1 loaded on a 120Gig SATA Hard disk. My ouput of uname -a: p4# uname -a FreeBSD p4.hawaii.rr.com 5.2-RC1 FreeBSD 5.2-RC1 #0: Sun Dec 7 22:15:14 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 The mobo has an onboard 3COM 3C940 Gbit LAN controller. This device is recognised during boot as sk0 and uses the SysKonnectPCI driver. The problem is that after a reboot a DHCP address is not assigned to sk0. Here is ifconfig -a after a reboot. p4# ifconfig -a sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::20c:6eff:fe91:dea6%sk0 prefixlen 64 scopeid 0x1 ether 00:0c:6e:91:de:a6 media: Ethernet autoselect (100baseTX full-duplex,flag0,flag1) status: active plip0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 Here is the output of resolv.conf and rc.conf p4# cat /etc/resolv.conf search hawaii.rr.com nameserver 24.25.227.66 nameserver 24.25.227.33 nameserver 24.25.227.64 p4# cat /etc/rc.conf # -- sysinstall generated deltas -- # Thu May 20 10:05:35 2004 # Created: Thu May 20 10:05:35 2004 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. hostname=p4.hawaii.rr.com ifconfig_sk0=DHCP linux_enable=YES nfs_client_enable=YES sshd_enable=YES usbd_enable=YES # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. # Enable network daemons for user convenience. # Created: Thu May 20 20:27:06 2004 # -- sysinstall generated deltas -- # Thu May 20 20:27:06 2004 ifconfig_sk0=DHCP hostname=p4.hawaii.rr.com # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. # Enable network daemons for user convenience. Notice that there is a second entry in rc.conf relating to sk0. If I enter /stand/sysinstall and choose configure then networking and then interfaces and then chooses DHCP, the fields are all populated with the correct information. I can then exit back to the # and when I then look at ifconfig -a I get some good stuff! p4# ifconfig -a sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe80::20c:6eff:fe91:dea6%sk0 prefixlen 64 scopeid 0x1 inet 192.168.1.103 netmask 0xff00 broadcast 192.168.1.255 ether 00:0c:6e:91:de:a6 media: Ethernet autoselect (100baseTX full-duplex,flag0,flag1) status: active plip0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 Notice I now have an inet line populated with an IP address. If I now look at rc.conf I get this p4# cat /etc/rc.conf # -- sysinstall generated deltas -- # Thu May 20 10:05:35 2004 # Created: Thu May 20 10:05:35 2004 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. hostname=p4.hawaii.rr.com ifconfig_sk0=DHCP linux_enable=YES nfs_client_enable=YES sshd_enable=YES usbd_enable=YES # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. # Enable network daemons for user convenience. # Created: Thu May 20 20:27:06 2004 # -- sysinstall generated deltas -- # Thu May 20 20:27:06 2004 ifconfig_sk0=DHCP hostname=p4.hawaii.rr.com # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. # Enable network daemons for user convenience. # Created: Tue May 25 16:17:31 2004 # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. # Enable network daemons for user convenience. # Created: Tue May 25 17:28:40 2004 # This file now contains just the overrides from /etc/defaults/rc.conf. # Please make all changes to this file, not to /etc/defaults/rc.conf. # Enable network daemons for user convenience. # Created: Tue May 25 17:31:13 2004 # -- sysinstall generated deltas -- # Tue May 25 17:31:13 2004 ifconfig_sk0=DHCP hostname=p4.hawaii.rr.com Still another
