Michael Schmitz wrote: >> On an older 2.6.11.9 kernel I can use my eth0 port but on my newer 2.6.17.11 >> kernel I have not been able to use eth0 and get this error. > >> sungem.c:v0.98 8/24/03 David S. Miller ([email protected]) >> PHY ID: 1410cc1, addr: 0 >> eth0: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:0d:93:35:91:44 >> eth0: Found Marvell 88E1101 PHY > [...] >> ieee80211: 802.11 data/management/control stack, git-1.1.7 >> ieee80211: Copyright (C) 2004-2005 Intel Corporation <[EMAIL PROTECTED]> >> ieee80211_crypt: registered algorithm 'NULL' >> ieee80211_crypt: registered algorithm 'WEP' >> ieee80211_crypt: registered algorithm 'CCMP' >> ieee80211_crypt: registered algorithm 'TKIP' > [...] >> orinoco 0.15rc3 (David Gibson <[EMAIL PROTECTED]>, Pavel Roskin <[EMAIL >> PROTECTED]>, et al) >> airport 0.15rc3 (Benjamin Herrenschmidt <[EMAIL PROTECTED]>) > [...] > > Check that your SUNGEM isn't actually eth1 now. > > Michael >
Yes, it had switched. Now the investigation goes to find out why eth0 is now eth1. Apparently, I have installed a package that is conflicting with the order networking devices are scanned. I used the same kernel on a fresh install partition and it works just fine so the only difference between the two are: one a new install and the other was running on my powerbook 15 TI. My /etc/network looks like this: /etc/network # l * -rw-r--r-- 1 root root 724 2006-10-06 14:00 interfaces -rw-r--r-- 1 root root 1.3K 2006-09-02 19:25 interfaces-old -rw-r--r-- 1 root root 2.0K 2005-05-03 02:28 secvpn.conf if-down.d: total 12K -rwxr-xr-x 1 root root 141 2006-04-10 16:02 openvpn* -rwxr-xr-x 1 root root 803 2006-06-08 02:00 postfix* -rwxr-xr-x 1 root root 488 2006-04-11 21:45 resolvconf* lrwxrwxrwx 1 root root 32 2006-10-05 17:57 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh* if-post-down.d: total 8.0K -rwxr-xr-x 1 root root 997 2006-02-09 15:37 wireless-tools* lrwxrwxrwx 1 root root 32 2006-10-05 17:57 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh* if-pre-up.d: total 20K -rwxr-xr-x 1 root root 2.3K 2006-02-09 15:37 wireless-tools* lrwxrwxrwx 1 root root 32 2006-10-05 17:57 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh* if-up.d: total 24K -rwxr-xr-x 1 root root 651 2006-04-11 21:45 000resolvconf* -rwxr-xr-x 1 root root 1.4K 2006-05-23 03:40 mountnfs* -rwxr-xr-x 1 root root 551 2006-05-28 19:49 ntpdate* -rwxr-xr-x 1 root root 142 2006-04-10 16:02 openvpn* -rwxr-xr-x 1 root root 1.1K 2006-06-08 02:00 postfix* Could any of these be conflicting with the network devices on startup? That is a start. I am amiss. I took out a bunch of wireless packages thinking that may have contributed to my issue but it did not. i also took out anything to do with bluetooth thinking when starting up it could be attributing to the missaragement of network devices and still no difference. Now when I dmesg I still see bluetooth but there are not any package related to bluetooth installed. Thanks for the input. -Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
