El Viernes, 1 de Diciembre de 2006 20:17, Marcelo Magno T. Sales escribió: > Hi, people > > I have a centrino notebook with intel ipw2200 wireless card. Almost every > time I cold-boot this computer, the card is shown as __tmp1804289383 or > something like that instead of eth1. It is not in an usable state when this > happens. If I just reboot, the card is then correctly shown as eth1 and > works ok. Restarting the network and/or NetworkManager services do not > correct the problem. So, I always have to boot and then reboot to get the > wirless card working. This did not happen in FC5. > > These lines appear in dmesg (I can post the complete file if requested): > > ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.1.2kmprq > ipw2200: Copyright(c) 2003-2006 Intel Corporation > ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection > ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels) > eth1: Identified chip type is 'RTL8169s/8110s'. > eth1: RTL8169 at 0xf8b28c00, 00:03:0d:3a:f0:5b, IRQ 185 > ADDRCONF(NETDEV_UP): __tmp1804289383: link is not ready > r8169: eth0: link down > ADDRCONF(NETDEV_UP): eth0: link is not ready > ADDRCONF(NETDEV_CHANGE): __tmp1804289383: link becomes ready > ieee80211_crypt: registered algorithm 'CCMP' > ieee80211_crypt: registered algorithm 'TKIP' > ADDRCONF(NETDEV_UP): __tmp1804289383: link is not ready > ADDRCONF(NETDEV_CHANGE): __tmp1804289383: link becomes ready > __tmp1804289383: no IPv6 routers present > ADDRCONF(NETDEV_UP): __tmp1804289383: link is not ready > > > Sometimes I also get: > > ADDRCONF(NETDEV_UP): __tmp1804289383: link is not ready > ADDRCONF(NETDEV_CHANGE): __tmp1804289383: link becomes ready > __tmp1804289383: no IPv6 routers present > ipw2200: Failed to send RSN_CAPABILITIES: Command timed out. > ipw2200: Failed to send SSID: Command timed out. > > > When the card is shown as __tmp1804289383 and I command ifup eth1, I get: > ipw2200 device eth1 seems not to be present; delaying initialization > > > Why is this happening? How can I get wireless working after the first boot? > > Thanks, > > Marcelo try to set the HWADDR manually to each interface in your: /etc/sysconfig/network-scripts/ifcfg-eth1 Using the line below: HWADDR=00:0a:e4:c4:02:cd (Change the HWADDR to use yours or whatever) Hope that helps -- Manuel Arostegui Ramirez. Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues. -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list