| 1 |
On 30 Sep 2009, at 11:58, Cinder wrote: |
| 2 |
|
| 3 |
>> What is the NIC in the box where eth0 isn't showing up? |
| 4 |
> Intel Corporation 82547EI Gigabit Ethernet Controller |
| 5 |
>> Is the driver in your kernel? |
| 6 |
> No. It's a module (e1000) and I watched it compile. I tried a static |
| 7 |
> driver as well. |
| 8 |
> |
| 9 |
> lspci say's http://pastebin.com/md3578a6 |
| 10 |
> |
| 11 |
> I deleted etc/udev/rules.d/70-persistent-net.rules and rebooted. Now |
| 12 |
> there's a message that loading module e1000 failed, and still device |
| 13 |
> eth0 does not exist as well as device eth1 does not exits, but there |
| 14 |
> are symlinks in /etc/init.d for both. |
| 15 |
|
| 16 |
Just seen this, following my other reply. |
| 17 |
|
| 18 |
`tail -f /var/log/messages` in one window whilst running the `modprobe |
| 19 |
-v e1000` in another. |
| 20 |
|
| 21 |
`dmesg` should show the same stuff as /var/log/messages (in this |
| 22 |
instance, at least), but using `tail -f /var/log/messages` it's easy |
| 23 |
to hit enter a few times (to clear some space on the screen) and then |
| 24 |
see what's happening in real-time. Although there's probably a very |
| 25 |
good reason for it, it's sometimes frustrating that `dmesg` isn't time |
| 26 |
stamped. |
| 27 |
|
| 28 |
Stroller. |
Archives