Apparently, _Adam Aube_, on 20/12/04 19:32,typed:
H. S. wrote:
Yesterday, due to some weird reason, my network went down yesterday.
When I rebooted into Fedora to see if it worked, it did. Then I rebooted
into 2.4.26 kernel in Debian. That worked too. Then I tried again in
2.6.9 and 2.6.7 kernels
Yesterday, due to some weird reason, my network went down yesterday.
When I rebooted into Fedora to see if it worked, it did. Then I rebooted
into 2.4.26 kernel in Debian. That worked too. Then I tried again in
2.6.9 and 2.6.7 kernels in Debian and networking failed again.
This morning I ran
On Mon, Dec 20, 2004 at 03:59:15PM -0500, H. S. wrote:
I then realized that I had updated discover just recently. Maybe that
detected the NICs in a different way and made eth0 as eth1 and vice versa.
That sounds like what happened. When you move between kernel versions
(atleast a 2.4 to a
H. S. wrote:
Yesterday, due to some weird reason, my network went down yesterday.
When I rebooted into Fedora to see if it worked, it did. Then I rebooted
into 2.4.26 kernel in Debian. That worked too. Then I tried again in
2.6.9 and 2.6.7 kernels in Debian and networking failed again.
The
On Monday 20 December 2004 05:39 pm, Jeremy Turner wrote:
(atleast a 2.4 to a 2.6) the order in which modules load might change.
If you use a kernel with modules for your NICs, I would suggest using
aliases to explicitly name your ethernet cards. Something like:
# echo alias eth0 3c59x
Apparently, _Jeremy Turner_, on 20/12/04 17:39,typed:
On Mon, Dec 20, 2004 at 03:59:15PM -0500, H. S. wrote:
I then realized that I had updated discover just recently. Maybe that
detected the NICs in a different way and made eth0 as eth1 and vice versa.
That sounds like what happened. When you
6 matches
Mail list logo
