On 7/14/07, Frans Pop <[EMAIL PROTECTED]> wrote:On Thursday 12 July 2007 20:59, Matheus Morais wrote:
The most likely cause is that you have multiple NICs in your system and the order in which they are recognized is different after reboot then it was during installation.
The problem also happen with only one ethernet adapter. On 7/14/07, Otavio Salvador <[EMAIL PROTECTED]> wrote:
The problem of using auto is that the booting gets stuck until dhclient3 timeouts, if you lack network support while booting the system. If you use allow-hotplug it doesn't happen. Maybe, Matheus NIC lacks MII extensions. Matheus, can you provide the output of the command: #: mii-tool -v
alferes:~# mii-tool -v eth0: negotiated 100baseTx-FD flow-control, link ok product info: vendor 00:40:63, model 50 rev 10 basic mode: autonegotiation enabled basic status: autonegotiation complete, link ok capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control I don't believe that is a problem with my network adapter specifically, because this also happen with other machines around here with different NIC models.
