Hello all.
I just installed test 3 from DVD, and after rebooting eth0 will no longer work. I can't ping local or internet addresses by name or by IP. Currently, it's set to static IP, but DHCP doesn't work either. It worked fine during the installation and on the first boot, but quit after that.
Any ideas? Should this be filed as a bug report, or is this a known issue? I tried googling for it, but turned up no solutions.
Thanks.
--Dane
Dane Mutters wrote: ...
I just installed test 3 from DVD, and after rebooting eth0 will no longer work. I can't ping local or internet addresses by name or by IP. Currently, it's set to static IP, but DHCP doesn't work either. It worked fine during the installation and on the first boot, but quit after that.
Can you give the result of ifconfig ? Also, what is in /etc/hosts and /etc/resolv.conf Can you ping localhost ? Can you ping the eth0 address (potentially retrieved from ifconfig) ?
In anaconda, did you set the address to static or dhcp ? Did you provide a hostname ? When you said currently: what method have you been using to try different ethernet settings ? What is the ethernet adapter ? Is this a wireless adapter ? What is the result of lspci ? How about lsmod ?
Any ideas? Should this be filed as a bug report, or is this a known issue?
I don't know, perhaps there is an error being logged in /var/log/messages ? grep eth0 /var/log/messages that can shed more light on the problem. In any case to make a bugzilla report you would need to provide info like the above; might as well provide it here first, so that there is enough info for others to help/refer you to bugzilla etc. Also, perhaps provide the age and manufacturer/model of the machine (or component parts if hand assembled).
I tried googling for it, but turned up no solutions.
Possibly to new for google; and there is some finesse required in massaging bugzilla to not give "zero bugs found".
DaveT.
Thanks for the suggestions, Dave. Here's some info:
Can you give the result of ifconfig ?
eth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet addr:192.168.1.112 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:11677 errors:0 dropped:0 overruns:0 frame:0 TX packets:255 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:869560 (849.1 KiB) TX bytes:12811 (12.5 KiB)
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:2945 errors:0 dropped:0 overruns:0 frame:0 TX packets:2945 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3294145 (3.1 MiB) TX bytes:3294145 (3.1 MiB)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:12227 errors:0 dropped:736 overruns:0 frame:0 TX packets:610 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:914379 (892.9 KiB) TX bytes:44795 (43.7 KiB) Interrupt:11 Base address:0x2c00
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:255 errors:0 dropped:0 overruns:0 frame:0 TX packets:11682 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:12811 (12.5 KiB) TX bytes:869926 (849.5 KiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:12157 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:725575 (708.5 KiB) TX bytes:468 (468.0 b)
Also, what is in /etc/hosts
# Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 Spot.The.Band Spot localhost.localdomain localhost
and /etc/resolv.conf
search The.Band nameserver 192.168.1.1 nameserver 65.164.104.5 nameserver 65.164.104.4
Can you ping localhost ?
yes.
Can you ping the eth0 address (potentially retrieved from ifconfig) ?
yes.
In anaconda, did you set the address to static or dhcp ?
Static
Did you provide a hostname ?
Yes (Spot)
When you said currently: what method have you been using to try different ethernet settings ?
I have tried using static and DHCP. Currently I'm using static.
What is the ethernet adapter ?
Linksys NC100 Network Everywhere Fast Ethernet 10/100 (rev. 11)
Is this a wireless adapter ?
No
What is the result of lspci ?
00:00.0 Host bridge: Intel Corporation 82815 815 Chipset Host Bridge and Memory Controller Hub (rev 02) 00:01.0 PCI bridge: Intel Corporation 82815 815 Chipset AGP Bridge (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 02) 00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 02) 00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 (rev 02) 00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB (Hub #1) (rev 02) 00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus (rev 02) 00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB (Hub #2) (rev 02) 01:09.0 Ethernet controller: Linksys NC100 Network Everywhere Fast Ethernet 10/100 (rev 11) 01:0a.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07) 01:0a.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 07) 01:0d.0 Communication controller: Conexant HCF 56k Data/Fax/Voice/Spkp Modem (rev 08) 02:00.0 VGA compatible controller: nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro] (rev 15)
How about lsmod ?
Module Size Used by vfat 16449 1 fat 52701 1 vfat sg 36573 0 sd_mod 20673 2 usb_storage 67105 1 scsi_mod 130665 3 sg,sd_mod,usb_storage bridge 51669 0 ppdev 12741 0 autofs4 23237 1 rfcomm 42965 0 l2cap 31809 5 rfcomm bluetooth 53285 2 rfcomm,l2cap sunrpc 142717 1 ip_conntrack_netbios_ns 6977 0 ipt_REJECT 9537 1 xt_state 6209 6 ip_conntrack 54681 2 ip_conntrack_netbios_ns,xt_state nfnetlink 10585 1 ip_conntrack xt_tcpudp 7233 8 iptable_filter 7105 1 ip_tables 16517 1 iptable_filter x_tables 16965 4 ipt_REJECT,xt_state,xt_tcpudp,ip_tables video 19269 0 button 10705 0 battery 13381 0 ac 8901 0 ipv6 249249 14 lp 16393 0 parport_pc 29541 1 parport 38153 3 ppdev,lp,parport_pc nvram 12745 0 uhci_hcd 33489 0 snd_emu10k1_synth 10945 0 snd_emux_synth 36161 1 snd_emu10k1_synth snd_seq_virmidi 11201 1 snd_emux_synth snd_seq_midi_emul 10049 1 snd_emux_synth snd_emu10k1 108741 2 snd_emu10k1_synth snd_rawmidi 28225 2 snd_seq_virmidi,snd_emu10k1 snd_ac97_codec 87905 1 snd_emu10k1 snd_ac97_bus 6465 1 snd_ac97_codec snd_seq_dummy 7749 0 snd_seq_oss 33985 0 snd_seq_midi_event 11329 2 snd_seq_virmidi,snd_seq_oss snd_seq 53297 8 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_dummy,snd_seq_oss,snd_seq_midi_event emu10k1_gp 7873 0 gameport 19785 2 emu10k1_gp snd_pcm_oss 49489 0 snd_mixer_oss 20545 2 snd_pcm_oss snd_pcm 81989 3 snd_emu10k1,snd_ac97_codec,snd_pcm_oss tulip 52449 0 snd_seq_device 12877 7 snd_emu10k1_synth,snd_emux_synth,snd_emu10k1,snd_rawmidi,snd_seq_dummy,snd_seq_oss,snd_seq snd_timer 26949 3 snd_emu10k1,snd_seq,snd_pcm snd_page_alloc 14537 2 snd_emu10k1,snd_pcm snd_util_mem 9153 2 snd_emux_synth,snd_emu10k1 snd_hwdep 13637 2 snd_emux_synth,snd_emu10k1 snd 54085 13 snd_emux_synth,snd_seq_virmidi,snd_emu10k1,snd_rawmidi,snd_ac97_codec,snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_device,snd_timer,snd_hwdep soundcore 13473 2 snd i2c_i801 12365 0 i2c_core 24897 1 i2c_i801 dm_snapshot 20333 0 dm_zero 6337 0 dm_mirror 24209 0 dm_mod 55257 6 dm_snapshot,dm_zero,dm_mirror ext3 123849 2 jbd 57813 1 ext3
I don't know, perhaps there is an error being logged in /var/log/messages ? grep eth0 /var/log/messages that can shed more light on the problem.
Feb 24 10:30:41 Spot kernel: eth0: ADMtek Comet rev 17 at cf076c00, 00:04:5A:55:96:57, IRQ 11. Feb 24 10:30:45 Spot kernel: eth0: Setting full-duplex based on MII#1 link partner capability of 45e1. Feb 24 02:31:06 Spot ntpd[2267]: Listening on interface eth0, 192.168.1.112#123 Feb 24 02:32:09 Spot avahi-daemon[2290]: New relevant interface eth0.IPv4 for mDNS. Feb 24 02:32:09 Spot avahi-daemon[2290]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 24 02:32:09 Spot avahi-daemon[2290]: Registering new address record for 192.168.1.112 on eth0. Feb 24 02:32:17 Spot avahi-daemon[2290]: Withdrawing address record for 192.168.1.112 on eth0. Feb 24 02:32:17 Spot avahi-daemon[2290]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 24 02:32:17 Spot avahi-daemon[2290]: Interface eth0.IPv4 no longer relevant for mDNS. Feb 24 02:32:18 Spot kernel: peth0: Promiscuous mode enabled. Feb 24 02:32:18 Spot kernel: device peth0 entered promiscuous mode Feb 24 02:32:18 Spot kernel: xenbr0: port 2(peth0) entering learning state Feb 24 02:32:18 Spot kernel: xenbr0: port 2(peth0) entering forwarding state Feb 24 02:32:18 Spot avahi-daemon[2290]: New relevant interface eth0.IPv4 for mDNS. Feb 24 02:32:18 Spot avahi-daemon[2290]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 24 02:32:18 Spot avahi-daemon[2290]: Registering new address record for 192.168.1.112 on eth0. Feb 24 02:32:21 Spot kernel: peth0: Setting full-duplex based on MII#1 link partner capability of 45e1. Feb 24 03:06:35 Spot system-config-network[4482]: ln //etc/sysconfig/network-scripts//ifcfg-eth0 //etc/sysconfig/networking/devices//ifcfg-eth0 Feb 24 03:06:35 Spot system-config-network[4482]: Linking eth0 to devices and putting it in profile default. Feb 24 03:06:35 Spot system-config-network[4482]: ln //etc/sysconfig/networking/devices//ifcfg-eth0 //etc/sysconfig/networking/profiles//default/ifcfg-eth0 Feb 24 03:32:30 Spot avahi-daemon[2290]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 24 10:59:59 Spot kernel: eth0: ADMtek Comet rev 17 at cf034c00, FE:FF:FF:FF:FF:FF, IRQ 11. Feb 24 11:00:00 Spot kernel: eth0: Setting full-duplex based on MII#1 link partner capability of 45e1. Feb 24 11:00:22 Spot ntpd[1946]: Listening on interface eth0, 192.168.1.112#123 Feb 24 11:00:26 Spot avahi-daemon[2085]: New relevant interface eth0.IPv4 for mDNS. Feb 24 11:00:26 Spot avahi-daemon[2085]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 24 11:00:26 Spot avahi-daemon[2085]: Registering new address record for 192.168.1.112 on eth0. Feb 24 11:00:37 Spot avahi-daemon[2085]: Interface eth0.IPv4 no longer relevant for mDNS. Feb 24 11:00:37 Spot avahi-daemon[2085]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 24 11:00:37 Spot avahi-daemon[2085]: Withdrawing address record for 192.168.1.112 on eth0. Feb 24 11:00:37 Spot kernel: peth0: Promiscuous mode enabled. Feb 24 11:00:37 Spot kernel: device peth0 entered promiscuous mode Feb 24 11:00:37 Spot kernel: xenbr0: port 2(peth0) entering learning state Feb 24 11:00:37 Spot kernel: xenbr0: port 2(peth0) entering forwarding state Feb 24 11:00:38 Spot avahi-daemon[2085]: New relevant interface eth0.IPv4 for mDNS. Feb 24 11:00:38 Spot avahi-daemon[2085]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 24 11:00:38 Spot avahi-daemon[2085]: Registering new address record for 192.168.1.112 on eth0. Feb 24 11:00:40 Spot kernel: peth0: Setting full-duplex based on MII#1 link partner capability of 45e1. Feb 24 11:06:37 Spot system-config-network[2764]: -+ //etc/modprobe.conf eth0 alias tulip Feb 24 11:06:37 Spot system-config-network[2764]: chmod 0644 //etc/sysconfig/networking/devices/ifcfg-eth0 Feb 24 11:10:35 Spot system-config-network[3115]: -+ //etc/modprobe.conf eth0 alias tulip Feb 24 11:10:35 Spot system-config-network[3115]: chmod 0644 //etc/sysconfig/networking/devices/ifcfg-eth0 Feb 24 11:14:57 Spot avahi-daemon[2085]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 24 11:16:36 Spot kernel: eth0: ADMtek Comet rev 17 at cf076c00, FE:FF:FF:FF:FF:FF, IRQ 11. Feb 24 11:16:37 Spot kernel: eth0: Setting full-duplex based on MII#1 link partner capability of 45e1. Feb 24 11:16:56 Spot ntpd[1933]: Listening on interface eth0, 192.168.1.112#123 Feb 24 11:17:00 Spot avahi-daemon[2073]: New relevant interface eth0.IPv4 for mDNS. Feb 24 11:17:00 Spot avahi-daemon[2073]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 24 11:17:00 Spot avahi-daemon[2073]: Registering new address record for 192.168.1.112 on eth0. Feb 24 11:17:11 Spot avahi-daemon[2073]: Interface eth0.IPv4 no longer relevant for mDNS. Feb 24 11:17:11 Spot avahi-daemon[2073]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 24 11:17:11 Spot avahi-daemon[2073]: Withdrawing address record for 192.168.1.112 on eth0. Feb 24 11:17:12 Spot kernel: peth0: Promiscuous mode enabled. Feb 24 11:17:12 Spot kernel: device peth0 entered promiscuous mode Feb 24 11:17:12 Spot kernel: xenbr0: port 2(peth0) entering learning state Feb 24 11:17:12 Spot kernel: xenbr0: port 2(peth0) entering forwarding state Feb 24 11:17:12 Spot avahi-daemon[2073]: New relevant interface eth0.IPv4 for mDNS. Feb 24 11:17:12 Spot avahi-daemon[2073]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 24 11:17:12 Spot avahi-daemon[2073]: Registering new address record for 192.168.1.112 on eth0. Feb 24 11:17:15 Spot kernel: peth0: Setting full-duplex based on MII#1 link partner capability of 45e1. Feb 24 11:24:23 Spot system-config-network[2742]: -+ //etc/modprobe.conf eth0 alias tulip Feb 24 11:24:23 Spot system-config-network[2742]: chmod 0644 //etc/sysconfig/networking/devices/ifcfg-eth0 Feb 24 11:24:29 Spot avahi-daemon[2073]: Withdrawing address record for 192.168.1.112 on eth0. Feb 24 11:24:29 Spot avahi-daemon[2073]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 24 11:24:29 Spot avahi-daemon[2073]: Interface eth0.IPv4 no longer relevant for mDNS. Feb 24 11:24:29 Spot dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 Feb 24 11:24:36 Spot dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 Feb 24 11:24:51 Spot dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17 Feb 24 11:25:06 Spot system-config-network[2742]: -+ //etc/modprobe.conf eth0 alias tulip Feb 24 11:25:06 Spot system-config-network[2742]: chmod 0644 //etc/sysconfig/networking/devices/ifcfg-eth0 Feb 24 11:25:08 Spot dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14 Feb 24 11:25:10 Spot avahi-daemon[2073]: New relevant interface eth0.IPv4 for mDNS. Feb 24 11:25:10 Spot avahi-daemon[2073]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 24 11:25:10 Spot avahi-daemon[2073]: Registering new address record for 192.168.1.112 on eth0. Feb 24 11:25:22 Spot dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 Feb 24 11:28:01 Spot avahi-daemon[2073]: Withdrawing address record for 192.168.1.112 on eth0. Feb 24 11:28:01 Spot avahi-daemon[2073]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 24 11:28:01 Spot avahi-daemon[2073]: Interface eth0.IPv4 no longer relevant for mDNS. Feb 24 11:28:07 Spot avahi-daemon[2073]: New relevant interface eth0.IPv4 for mDNS. Feb 24 11:28:07 Spot avahi-daemon[2073]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 24 11:28:07 Spot avahi-daemon[2073]: Registering new address record for 192.168.1.112 on eth0. Feb 24 11:28:54 Spot system-config-network[3051]: -+ //etc/modprobe.conf eth0 alias tulip Feb 24 11:28:54 Spot system-config-network[3051]: chmod 0644 //etc/sysconfig/networking/devices/ifcfg-eth0 Feb 24 11:28:56 Spot avahi-daemon[2073]: Withdrawing address record for 192.168.1.112 on eth0. Feb 24 11:28:56 Spot avahi-daemon[2073]: Interface eth0.IPv4 no longer relevant for mDNS. Feb 24 11:29:02 Spot avahi-daemon[2073]: New relevant interface eth0.IPv4 for mDNS. Feb 24 11:29:02 Spot avahi-daemon[2073]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 24 11:29:02 Spot avahi-daemon[2073]: Registering new address record for 192.168.1.112 on eth0. Feb 25 09:33:43 Spot kernel: eth0: ADMtek Comet rev 17 at cf034c00, FE:FF:FF:FF:FF:FF, IRQ 11. Feb 25 09:33:44 Spot kernel: eth0: Setting full-duplex based on MII#1 link partner capability of 45e1. Feb 25 09:34:05 Spot ntpd[1934]: Listening on interface eth0, 192.168.1.112#123 Feb 25 09:34:09 Spot avahi-daemon[2073]: New relevant interface eth0.IPv4 for mDNS. Feb 25 09:34:09 Spot avahi-daemon[2073]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 09:34:09 Spot avahi-daemon[2073]: Registering new address record for 192.168.1.112 on eth0. Feb 25 09:34:20 Spot avahi-daemon[2073]: Withdrawing address record for 192.168.1.112 on eth0. Feb 25 09:34:20 Spot avahi-daemon[2073]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 09:34:20 Spot avahi-daemon[2073]: Interface eth0.IPv4 no longer relevant for mDNS. Feb 25 09:34:20 Spot kernel: peth0: Promiscuous mode enabled. Feb 25 09:34:20 Spot kernel: device peth0 entered promiscuous mode Feb 25 09:34:20 Spot kernel: xenbr0: port 2(peth0) entering learning state Feb 25 09:34:20 Spot kernel: xenbr0: port 2(peth0) entering forwarding state Feb 25 09:34:21 Spot avahi-daemon[2073]: New relevant interface eth0.IPv4 for mDNS. Feb 25 09:34:21 Spot avahi-daemon[2073]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 09:34:21 Spot avahi-daemon[2073]: Registering new address record for 192.168.1.112 on eth0. Feb 25 09:34:23 Spot kernel: peth0: Setting full-duplex based on MII#1 link partner capability of 45e1. Feb 25 09:51:44 Spot kernel: xenbr0: port 2(peth0) entering disabled state Feb 25 09:51:44 Spot kernel: device peth0 left promiscuous mode Feb 25 09:51:44 Spot kernel: xenbr0: port 2(peth0) entering disabled state Feb 25 09:51:52 Spot avahi-daemon[2073]: Withdrawing address record for 192.168.1.112 on eth0. Feb 25 09:51:52 Spot avahi-daemon[2073]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 09:51:52 Spot avahi-daemon[2073]: Interface eth0.IPv4 no longer relevant for mDNS. Feb 25 09:52:03 Spot avahi-daemon[2073]: New relevant interface eth0.IPv4 for mDNS. Feb 25 09:52:03 Spot avahi-daemon[2073]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 09:52:03 Spot avahi-daemon[2073]: Registering new address record for 192.168.1.112 on eth0. Feb 25 09:52:18 Spot avahi-daemon[2073]: Withdrawing address record for 192.168.1.112 on eth0. Feb 25 09:52:18 Spot avahi-daemon[2073]: Interface eth0.IPv4 no longer relevant for mDNS. Feb 25 09:52:58 Spot avahi-daemon[2073]: New relevant interface eth0.IPv4 for mDNS. Feb 25 09:52:58 Spot avahi-daemon[2073]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 09:52:58 Spot avahi-daemon[2073]: Registering new address record for 192.168.1.112 on eth0. Feb 25 10:02:07 Spot avahi-daemon[2073]: Withdrawing address record for 192.168.1.112 on eth0. Feb 25 10:02:07 Spot avahi-daemon[2073]: Interface eth0.IPv4 no longer relevant for mDNS. Feb 25 10:02:17 Spot avahi-daemon[2073]: New relevant interface eth0.IPv4 for mDNS. Feb 25 10:02:17 Spot avahi-daemon[2073]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 10:02:17 Spot avahi-daemon[2073]: Registering new address record for 192.168.1.112 on eth0. Feb 25 10:09:28 Spot avahi-daemon[2073]: Withdrawing address record for 192.168.1.112 on eth0. Feb 25 10:09:28 Spot avahi-daemon[2073]: Interface eth0.IPv4 no longer relevant for mDNS. Feb 25 10:09:35 Spot avahi-daemon[2073]: New relevant interface eth0.IPv4 for mDNS. Feb 25 10:09:35 Spot avahi-daemon[2073]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 10:09:35 Spot avahi-daemon[2073]: Registering new address record for 192.168.1.112 on eth0. Feb 25 10:10:55 Spot avahi-daemon[2073]: Withdrawing address record for 192.168.1.112 on eth0. Feb 25 10:10:55 Spot avahi-daemon[2073]: Interface eth0.IPv4 no longer relevant for mDNS. Feb 25 10:11:01 Spot avahi-daemon[2073]: New relevant interface eth0.IPv4 for mDNS. Feb 25 10:11:01 Spot avahi-daemon[2073]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 10:11:01 Spot avahi-daemon[2073]: Registering new address record for 192.168.1.112 on eth0. Feb 25 10:12:57 Spot avahi-daemon[2073]: Withdrawing address record for 192.168.1.112 on eth0. Feb 25 10:12:57 Spot avahi-daemon[2073]: Interface eth0.IPv4 no longer relevant for mDNS. Feb 25 10:13:04 Spot avahi-daemon[2073]: New relevant interface eth0.IPv4 for mDNS. Feb 25 10:13:04 Spot avahi-daemon[2073]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 10:13:04 Spot avahi-daemon[2073]: Registering new address record for 192.168.1.112 on eth0. Feb 25 11:45:32 Spot kernel: eth0: ADMtek Comet rev 17 at cf076c00, FE:FF:FF:FF:FF:FF, IRQ 11. Feb 25 11:45:33 Spot kernel: eth0: Setting full-duplex based on MII#1 link partner capability of 45e1. Feb 25 11:45:54 Spot ntpd[1948]: Listening on interface eth0, 192.168.1.112#123 Feb 25 11:45:58 Spot avahi-daemon[2087]: New relevant interface eth0.IPv4 for mDNS. Feb 25 11:45:58 Spot avahi-daemon[2087]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 11:45:58 Spot avahi-daemon[2087]: Registering new address record for 192.168.1.112 on eth0. Feb 25 11:46:09 Spot avahi-daemon[2087]: Interface eth0.IPv4 no longer relevant for mDNS. Feb 25 11:46:09 Spot avahi-daemon[2087]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 11:46:09 Spot avahi-daemon[2087]: Withdrawing address record for 192.168.1.112 on eth0. Feb 25 11:46:09 Spot kernel: peth0: Promiscuous mode enabled. Feb 25 11:46:09 Spot kernel: device peth0 entered promiscuous mode Feb 25 11:46:09 Spot kernel: xenbr0: port 2(peth0) entering learning state Feb 25 11:46:09 Spot kernel: xenbr0: port 2(peth0) entering forwarding state Feb 25 11:46:10 Spot avahi-daemon[2087]: New relevant interface eth0.IPv4 for mDNS. Feb 25 11:46:10 Spot avahi-daemon[2087]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 11:46:10 Spot avahi-daemon[2087]: Registering new address record for 192.168.1.112 on eth0. Feb 25 11:46:12 Spot kernel: peth0: Setting full-duplex based on MII#1 link partner capability of 45e1. Feb 25 11:50:36 Spot avahi-daemon[2087]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 11:52:54 Spot kernel: eth0: ADMtek Comet rev 17 at cf0c6c00, FE:FF:FF:FF:FF:FF, IRQ 11. Feb 25 11:52:55 Spot kernel: eth0: Setting full-duplex based on MII#1 link partner capability of 45e1. Feb 25 11:53:17 Spot ntpd[1944]: Listening on interface eth0, 192.168.1.112#123 Feb 25 11:53:21 Spot avahi-daemon[2094]: New relevant interface eth0.IPv4 for mDNS. Feb 25 11:53:21 Spot avahi-daemon[2094]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 11:53:21 Spot avahi-daemon[2094]: Registering new address record for 192.168.1.112 on eth0. Feb 25 11:53:32 Spot avahi-daemon[2094]: Interface eth0.IPv4 no longer relevant for mDNS. Feb 25 11:53:32 Spot avahi-daemon[2094]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 11:53:32 Spot avahi-daemon[2094]: Withdrawing address record for 192.168.1.112 on eth0. Feb 25 11:53:32 Spot kernel: peth0: Promiscuous mode enabled. Feb 25 11:53:32 Spot kernel: device peth0 entered promiscuous mode Feb 25 11:53:33 Spot kernel: xenbr0: port 2(peth0) entering learning state Feb 25 11:53:33 Spot kernel: xenbr0: port 2(peth0) entering forwarding state Feb 25 11:53:33 Spot avahi-daemon[2094]: New relevant interface eth0.IPv4 for mDNS. Feb 25 11:53:33 Spot avahi-daemon[2094]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 11:53:33 Spot avahi-daemon[2094]: Registering new address record for 192.168.1.112 on eth0. Feb 25 11:53:33 Spot kernel: eth0: duplicate address detected! Feb 25 11:53:35 Spot kernel: peth0: Setting full-duplex based on MII#1 link partner capability of 45e1. Feb 25 12:02:02 Spot avahi-daemon[2094]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 12:03:40 Spot kernel: eth0: ADMtek Comet rev 17 at cf076c00, FE:FF:FF:FF:FF:FF, IRQ 11. Feb 25 12:03:41 Spot kernel: eth0: Setting full-duplex based on MII#1 link partner capability of 45e1. Feb 25 12:04:04 Spot ntpd[1942]: Listening on interface eth0, 192.168.1.112#123 Feb 25 12:04:07 Spot avahi-daemon[2080]: New relevant interface eth0.IPv4 for mDNS. Feb 25 12:04:07 Spot avahi-daemon[2080]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 12:04:07 Spot avahi-daemon[2080]: Registering new address record for 192.168.1.112 on eth0. Feb 25 12:04:18 Spot avahi-daemon[2080]: Interface eth0.IPv4 no longer relevant for mDNS. Feb 25 12:04:18 Spot avahi-daemon[2080]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 12:04:18 Spot avahi-daemon[2080]: Withdrawing address record for 192.168.1.112 on eth0. Feb 25 12:04:19 Spot kernel: peth0: Promiscuous mode enabled. Feb 25 12:04:19 Spot kernel: device peth0 entered promiscuous mode Feb 25 12:04:19 Spot kernel: xenbr0: port 2(peth0) entering learning state Feb 25 12:04:19 Spot kernel: xenbr0: port 2(peth0) entering forwarding state Feb 25 12:04:19 Spot avahi-daemon[2080]: New relevant interface eth0.IPv4 for mDNS. Feb 25 12:04:19 Spot avahi-daemon[2080]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 12:04:19 Spot avahi-daemon[2080]: Registering new address record for 192.168.1.112 on eth0. Feb 25 12:04:19 Spot kernel: eth0: duplicate address detected! Feb 25 12:04:22 Spot kernel: peth0: Setting full-duplex based on MII#1 link partner capability of 45e1. Feb 25 12:11:33 Spot avahi-daemon[2080]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 12:13:32 Spot kernel: eth0: ADMtek Comet rev 17 at cf042c00, FE:FF:FF:FF:FF:FF, IRQ 11. Feb 25 12:13:32 Spot kernel: eth0: Setting full-duplex based on MII#1 link partner capability of 45e1. Feb 25 12:13:55 Spot ntpd[1905]: Listening on interface eth0, 192.168.1.112#123 Feb 25 12:13:59 Spot avahi-daemon[2056]: New relevant interface eth0.IPv4 for mDNS. Feb 25 12:13:59 Spot avahi-daemon[2056]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 12:13:59 Spot avahi-daemon[2056]: Registering new address record for 192.168.1.112 on eth0. Feb 25 12:14:10 Spot avahi-daemon[2056]: Interface eth0.IPv4 no longer relevant for mDNS. Feb 25 12:14:10 Spot avahi-daemon[2056]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 12:14:10 Spot avahi-daemon[2056]: Withdrawing address record for 192.168.1.112 on eth0. Feb 25 12:14:11 Spot kernel: peth0: Promiscuous mode enabled. Feb 25 12:14:11 Spot kernel: device peth0 entered promiscuous mode Feb 25 12:14:11 Spot kernel: xenbr0: port 2(peth0) entering learning state Feb 25 12:14:11 Spot kernel: xenbr0: port 2(peth0) entering forwarding state Feb 25 12:14:11 Spot avahi-daemon[2056]: New relevant interface eth0.IPv4 for mDNS. Feb 25 12:14:11 Spot avahi-daemon[2056]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.112. Feb 25 12:14:11 Spot avahi-daemon[2056]: Registering new address record for 192.168.1.112 on eth0. Feb 25 12:14:13 Spot kernel: peth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
In any case to make a bugzilla report you would need to provide info like the above; might as well provide it here first, so that there is enough info for others to help/refer you to bugzilla etc. Also, perhaps provide the age and manufacturer/model of the machine (or component parts if hand assembled).
It's a 6-year-old Gateway with a Pentium 3 800MHz processor.
Also, I seem to have forgotten an important detail. I get this error message when disabling the device (eth0) in the network configuration tool in Gnome:
Device eth0 has MAC address FE:FF:FF:FF:FF:FF, instead of configured address 00:04:5A:55:96:57. Ignoring.
Here's what dmesg | grep eth0 shows:
eth0: ADMtek Comet rev 17 at cf042c00, FE:FF:FF:FF:FF:FF, IRQ 11. eth0: Setting full-duplex based on MII#1 link partner capability of 45e1. eth0: no IPv6 routers present peth0: Promiscuous mode enabled. device peth0 entered promiscuous mode xenbr0: port 2(peth0) entering learning state xenbr0: port 2(peth0) entering forwarding state peth0: Setting full-duplex based on MII#1 link partner capability of 45e1. peth0: no IPv6 routers present eth0: no IPv6 routers present
Hope that helps!
--Dane
Dane Mutters wrote:
Thanks for the suggestions, Dave. Here's some info:
Can you give the result of ifconfig ?
eth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet addr:192.168.1.112 Bcast:192.168.1.255 Mask:255.255.255.0
I don't think I have seen any machine not show the MAC address properly; this one (HWaddr) does not seem legit, but I have no idea why. ...
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:12227 errors:0 dropped:736 overruns:0 frame:0 TX packets:610 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:914379 (892.9 KiB) TX bytes:44795 (43.7 KiB) Interrupt:11 Base address:0x2c00
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:255 errors:0 dropped:0 overruns:0 frame:0 TX packets:11682 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:12811 (12.5 KiB) TX bytes:869926 (849.5 KiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:12157 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:725575 (708.5 KiB) TX bytes:468 (468.0 b)
... So you are doing the xen thing, or did you not mean to install xen ? Maybe try uninstalling the xen parts: again, I have no experience with this.
When you said currently: what method have you been using to try different ethernet settings ?
I have tried using static and DHCP. Currently I'm using static.
What I meant was are you hand editing config files or are you using system-config-network (System|Admin|Network) ?
# rpm -q system-config-network
What does system-config-network|eth0|edit|hardware device|Mac address show ? Is the bind to MAC address ticked ? Does clicking probe update / put in a real address ?
What is the ethernet adapter ?
Linksys NC100 Network Everywhere Fast Ethernet 10/100 (rev. 11)
Under what OS was the card last working ? If you dual boot, does the card work OK in the other OS ? Is this an upgrade install ? ...
What is the result of lspci ?
...
01:09.0 Ethernet controller: Linksys NC100 Network Everywhere Fast Ethernet
...
How about lsmod ?
Module Size Used by
...
tulip 52449 0
... I can only guess that tulip is the correct driver for your card If another linux used previously was it previously using the tulip module ? Can you find out which eth chip your linksys card actually uses ?
I don't know, perhaps there is an error being logged in /var/log/messages ? grep eth0 /var/log/messages that can shed more light on the problem.
Feb 24 10:30:41 Spot kernel: eth0: ADMtek Comet rev 17 at cf076c00, 00:04:5A:55:96:57, IRQ 11. Feb 24 10:30:45 Spot kernel: eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
It seems to be detecting the link carrier, and going in full duplex OK. Is the netcard and switch / hub showing link activity ?
Feb 24 02:32:18 Spot kernel: peth0: Promiscuous mode enabled. Feb 24 02:32:18 Spot kernel: device peth0 entered promiscuous mode
Someone else know if this is normal for xen installs ? (this is normal when doing packet captures, but why here ?)
...
In any case to make a bugzilla report you would need to provide info like the above; might as well provide it here first, so that there is enough info for others to help/refer you to bugzilla etc. Also, perhaps provide the age and manufacturer/model of the machine (or component parts if hand assembled).
It's a 6-year-old Gateway with a Pentium 3 800MHz processor.
Also, I seem to have forgotten an important detail. I get this error message when disabling the device (eth0) in the network configuration tool in Gnome:
Device eth0 has MAC address FE:FF:FF:FF:FF:FF, instead of configured address 00:04:5A:55:96:57. Ignoring.
Do you know/can you find out the correct address and enter it in sys-con-network, in the area mentioned above ?
My guess is: for some reason the tools aren't able to retrieve the correct MAC address. Your machine will happily send out data with a return MAC address that is incorrect, which the eth driver ignores (since not destined to itself), leaving you in network isolation.
Hope that helps!
As you can see it's not a one step troubleshooting process ;-)
DaveT.
On Saturday 25 February 2006 07:22 pm, David Timms wrote:
I don't think I have seen any machine not show the MAC address properly; this one (HWaddr) does not seem legit, but I have no idea why.
Seems very odd to me as well.
So you are doing the xen thing, or did you not mean to install xen ? Maybe try uninstalling the xen parts: again, I have no experience with this.
I installed Xen so that I could experiment with it. I haven't yet done anything with it, although I would like to leave it on in case I decide to (this being a testing machine).
What I meant was are you hand editing config files or are you using system-config-network (System|Admin|Network) ?
I have been using the GUI tool in gnome (System|Admin|Network). I occasionally do an ifconfig or ifup/down to test things and get info.
# rpm -q system-config-network
system-config-network-1.3.30-2.1
What does system-config-network|eth0|edit|hardware device|Mac address show ? Is the bind to MAC address ticked ? Does clicking probe update / put in a real address ?
The box is ticked, but probing it changes it from what I think is the right one, to fe:ff:ff:ff:ff:ff.
Under what OS was the card last working ? If you dual boot, does the card work OK in the other OS ? Is this an upgrade install ?
Fedora 5 Test 3. I installed fresh from the DVD (NOT an upgrade), rebooted and it worked. Then I rebooted again and it didn't work. Before the install I had Ubuntu (Breezy) installed, and it worked perfectly.
I can only guess that tulip is the correct driver for your card If another linux used previously was it previously using the tulip module ? Can you find out which eth chip your linksys card actually uses ?
So far I don't know what chipset it uses, but several web sites say it uses the Tulip driver. Knoppix agrees that it uses the tulip driver.
It seems to be detecting the link carrier, and going in full duplex OK. Is the netcard and switch / hub showing link activity ?
It shows a minimal amount of activity.
Feb 24 02:32:18 Spot kernel: peth0: Promiscuous mode enabled. Feb 24 02:32:18 Spot kernel: device peth0 entered promiscuous mode
Someone else know if this is normal for xen installs ? (this is normal when doing packet captures, but why here ?)
hmmm...dunno...
In any case to make a bugzilla report you would need to provide info like the above; might as well provide it here first, so that there is enough info for others to help/refer you to bugzilla etc. Also, perhaps provide the age and manufacturer/model of the machine (or component parts if hand assembled).
It's a 6-year-old Gateway with a Pentium 3 800MHz processor.
Also, I seem to have forgotten an important detail. I get this error message when disabling the device (eth0) in the network configuration tool in Gnome:
Device eth0 has MAC address FE:FF:FF:FF:FF:FF, instead of configured address 00:04:5A:55:96:57. Ignoring.
Do you know/can you find out the correct address and enter it in sys-con-network, in the area mentioned above ?
Fedora originally reported the MAC as being: 00:04:5A:55:96:57, but now Fedora and Knoppix are both reporting it as: FE:FF:FF:FF:FF:FF. Very strange...
My guess is: for some reason the tools aren't able to retrieve the correct MAC address. Your machine will happily send out data with a return MAC address that is incorrect, which the eth driver ignores (since not destined to itself), leaving you in network isolation.
Hope that helps!
As you can see it's not a one step troubleshooting process ;-)
DaveT.
So it would seem! :-)
--Dane
Dane Mutters wrote:
On Saturday 25 February 2006 07:22 pm, David Timms wrote:
...
I installed Xen so that I could experiment with it. I haven't yet done anything with it, although I would like to leave it on in case I decide to (this being a testing machine).
http://www.google.com.au/search?q=linux+eth0+mac+address+wrong+FE:FF:FF:FF:F... http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=471 - it's a bit different - the xen part is getting the weird mac, but eth0 is OK. Looks like some serious config is required for xen, I think fedoranews or one of those sites has an intro page.
I'd be interested to see if removing (temporarily) the xen stuff solves the problem. This would definitely narrow down the possibilities ;) and point to which component is applicable.
DaveT.
On Saturday 25 February 2006 11:51 pm, David Timms wrote:
Dane Mutters wrote:
On Saturday 25 February 2006 07:22 pm, David Timms wrote:
...
I installed Xen so that I could experiment with it. I haven't yet done anything with it, although I would like to leave it on in case I decide to (this being a testing machine).
http://www.google.com.au/search?q=linux+eth0+mac+address+wrong+FE:FF:FF:FF: FF:FF&hl=en&lr=&start=20&sa=N http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=471
- it's a bit different - the xen part is getting the weird mac, but eth0
is OK. Looks like some serious config is required for xen, I think fedoranews or one of those sites has an intro page.
I'd be interested to see if removing (temporarily) the xen stuff solves the problem. This would definitely narrow down the possibilities ;) and point to which component is applicable.
DaveT.
I've uninstalled Xen and the Hypervisor kernel, and installed the more standard Fedora kerner, and now it seems to work properly despite having the wrong MAC address. Also, Kudzu no longer segfaults. (I still wonder if the two are related...)
Cheers!
--Dane
HI
I've uninstalled Xen and the Hypervisor kernel, and installed the more standard Fedora kerner, and now it seems to work properly despite having the wrong MAC address. Also, Kudzu no longer segfaults. (I still wonder if the two are related...)
Yes. It is related. A bug report has already been filed on this. Check the archives.
On Sat, Feb 25, 2006 at 09:38:21PM -0800, Dane Mutters wrote:
Fedora originally reported the MAC as being: 00:04:5A:55:96:57, but now Fedora and Knoppix are both reporting it as: FE:FF:FF:FF:FF:FF. Very strange...
I've seen more than one Ethernet card dying this way, so it might very well be a real hardware failure.
What you can try: power off the system completely, remove power cable, wait 10 sec or so, plug in the cable and power on again and see if something has changed. At least with one piece of (bad) HW this helped in the past (but it can go wrong again at every boot).
On Sunday 26 February 2006 01:34 am, Jos Vos wrote:
On Sat, Feb 25, 2006 at 09:38:21PM -0800, Dane Mutters wrote:
Fedora originally reported the MAC as being: 00:04:5A:55:96:57, but now Fedora and Knoppix are both reporting it as: FE:FF:FF:FF:FF:FF. Very strange...
I've seen more than one Ethernet card dying this way, so it might very well be a real hardware failure.
What you can try: power off the system completely, remove power cable, wait 10 sec or so, plug in the cable and power on again and see if something has changed. At least with one piece of (bad) HW this helped in the past (but it can go wrong again at every boot).
-- -- Jos Vos jos@xos.nl -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204
That fixed it! It now reports the MAC address of "00:04:5A:55:96:57". It does look like it's at least somewhat hardware-related. The one question I have, though, is why does this this card work with the wrong MAC address in Knoppix, but not in Fedora? Could it have to do with Kudzu segfaulting?
Thanks for your help, everybody.
--Dane
On Sun, Feb 26, 2006 at 12:19:08PM -0800, Dane Mutters wrote:
That fixed it! It now reports the MAC address of "00:04:5A:55:96:57". It does look like it's at least somewhat hardware-related. The one question I have, though, is why does this this card work with the wrong MAC address in Knoppix, but not in Fedora? Could it have to do with Kudzu segfaulting?
It's just flakyness, you probably see randomly the good or bad MAC address appearing after a reboot. After some day the card will only show the wrong MAC address (in our case at least two of these cards died definitively after an external power failure, I don't know why).
On Mon, Feb 27, 2006 at 11:16:37AM +0100, Jos Vos wrote:
show the wrong MAC address (in our case at least two of these cards died definitively after an external power failure, I don't know why).
Usually eeprom corruption. In some cases you'll the find the vendor disks or for 3com the Becker tool can recover them by writing new eeprom data
I installed the FC5 test 3 CD's. Using kernel version kernel-smp-2.6.15-1.1955_FC5, in run level 5 after the user logs on the system locks up hard. No keyboard input, no changes on the screen, no network functions. Using kernel kernel-2.6.15-1.1955_FC5
To make sure I have the latest and greatest of everything I ran "yum -y update" at 17:47 Februrary 27 (Eastern time) except for kernel and kernel-smp and got the same results.
The reason why id did not upgrade the kernel is because I get the following error message from yum for kernel-smp-2.6.15-1.1977_FC5 and kernel-2.6.15-1.1977_FC5
Downloading Packages: (1/1): kernel-2.6.15-1.19 100% |=========================| 13 MB 01:35 Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing: kernel ######################### [1/1] error resolving symbolic link ./../../devices/pci0000:00/0000:00:02.0/0000:01:00.0/0000:02:0e.0/host0/target0:2:0/0:2:0:0\u047fD\u047f \u047f,\u047f\uffff: No such file or directory
After I did the upgrade and booted to run level 5 with the SMP kernel, XOrg was using 99% of the processors (per top) and never prompted for a user to log in. I could connect via ssh, but the system was running very slow.
Starting the sytem with SMP in run level 3 is fine until you do "startx" or init 5 - then the processor utilization goes off the chart. Nothing every appears on the monitor. ssh will function.
The system has (2) 2.8G processors and
As I am not an expert in X, could somebody suggest something stupid I might be doing, is there more information I should provide, or should I file a bug report?
Thanks! Charlie
On Mon, Feb 27, 2006 at 05:49:44PM -0500, Charles Deling wrote:
./../../devices/pci0000:00/0000:00:02.0/0000:01:00.0/0000:02:0e.0/host0/target0:2:0/0:2:0:0\u047fD\u047f \u047f,\u047f\uffff: No such file or directory
nash problem, should be fixed in mkinitrd in tomorrows rawhide.
Dave
I have upgraded to kernel version 2.6.15-1.991 and have the same results. Run the SMP kernel and go to run level 5 and the processor utilization goes through the roof.
Any suggestions?
TIA Charlie
Charles Deling wrote:
I installed the FC5 test 3 CD's. Using kernel version kernel-smp-2.6.15-1.1955_FC5, in run level 5 after the user logs on the system locks up hard. No keyboard input, no changes on the screen, no network functions. Using kernel kernel-2.6.15-1.1955_FC5
To make sure I have the latest and greatest of everything I ran "yum -y update" at 17:47 Februrary 27 (Eastern time) except for kernel and kernel-smp and got the same results.
The reason why id did not upgrade the kernel is because I get the following error message from yum for kernel-smp-2.6.15-1.1977_FC5 and kernel-2.6.15-1.1977_FC5
Downloading Packages: (1/1): kernel-2.6.15-1.19 100% |=========================| 13 MB 01:35 Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing: kernel ######################### [1/1] error resolving symbolic link ./../../devices/pci0000:00/0000:00:02.0/0000:01:00.0/0000:02:0e.0/host0/target0:2:0/0:2:0:0\u047fD\u047f \u047f,\u047f\uffff: No such file or directory
After I did the upgrade and booted to run level 5 with the SMP kernel, XOrg was using 99% of the processors (per top) and never prompted for a user to log in. I could connect via ssh, but the system was running very slow.
Starting the sytem with SMP in run level 3 is fine until you do "startx" or init 5 - then the processor utilization goes off the chart. Nothing every appears on the monitor. ssh will function.
The system has (2) 2.8G processors and is a Dell Power Edge 2850
As I am not an expert in X, could somebody suggest something stupid I might be doing, is there more information I should provide, or should I file a bug report?
Thanks! Charlie
-
Alan Cox -
Charles Deling -
Dane Mutters -
Dave Jones -
David Timms -
Jos Vos -
Rahul Sundaram