Hello Ben >I don't understand why you say that eth0 was broken, if it wasn't >configured before. Are you saying that the upgrade *removed* an entry >from /etc/network/interfaces? Are you using a network interface control >program other than ifupdown, e.g. Network Manager or wicd?
I didn't realize eth0 was not configured at the time I reported the problem, that is, when I was part way through the squeeze upgrade. In retrospect, I realize that I had the capability of diagnosing and fixing the problem myself, without help, but I didn't realize that at the time. I am not using wicd. (At least I don't think I am. I don't know what it is.) Is Network Manager the tool that starts when you choose "Network" in KDE? If so, I have used it previously, but not for a long time, and not during or after the squeeze upgrade. About a year ago I was using a network card in addition to the onboard ethernet adaptor, but I removed it. /etc/network/interfaces may have still contained its entry. I don't know what the first squeeze upgrade attempt did to /etc/network/interfaces, as I did not look at it following the kernel, udev, and firmware-realtek upgrade/installation. But I know at that point I got "network unreachable" messages in response to ping 10.0.0.138. Since syslog contained "unable to patch firmware" message, and a search in bugs.debian.org turned up 611954, I assumed that was the problem and didn't look further. After the second (successful) squeeze upgrade attempt, which was conducted via the eth1 adaptor, /etc/network/interfaces contained no entry for eth0. There had to have been an entry prior to the upgrade, as the onboard adaptor was the only one in the machine. The second squeeze upgrade started from a "green fields" state, as I restored pre-upgrade dd partition images then ran the upgrade from the beginning. Regards Gerry. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
