la, 2008-03-15 kello 12:02 +1000, Brian Chadwick kirjoitti: > Peter J. Stieber wrote: > > PS = Peter Stieber > > PS>> I'm running the x86_64 version of F8 on a dual > > PS>> AMD Opteron box. I regularly run yum update to > > PS>> keep everything up to date. On March 9 I ran > > PS>> the update to get the most recent kernel > > PS>> (kernel-2.6.24.3-12.fc8.x86_64), but I didn't > > PS>> reboot to actually start using the latest kernel. > > PS>> > > PS>> I ran yum update again on March 13. After this > > PS>> update, I rebooted and tried to use the new > > PS>> kernel. I lost my network connections. > > > > Robert P. J. Day wrote: > > RD> join the club. just back off to the earlier > > RD> kernel and stay there until things sort > > RD> themselves out. > > > > I am running the prior kernel, but one of the adapters is still not > > working when I booted the prior kernel. I was asking for help with > > that problem. Sorry if I wasn't clear enough. > > > > Pete > > > rename ifcfg-ethx.bak to ifcfg.ethx, then "service network restart" > The GUI approach is to go to System->Administration->Network and edit the nicknames of NICs. In my case I changed "eth0.bak" to "lan" and "eth1.bak" to "wan" because my eth0 card is connected to local network and eth1 card to the Internet. It looks like kernel 2.6.24.3-12.fc8 either named ifcfg-ethx in /etc/sysconfig/network-scripts to ifcfg-ethx.bak - and refused to activate anything ".bak" at boot - or just erroneously tries to use nicknames of NICs instead of the usual ifcfg-ethx files. In any case, my both network cards now get activated at boot which was not the case after updating to 2.6.24.3-12.fc8 -kernel. Now, if only the GUI would show the proper card in "Physical device" tab instead of showing them interchanged - but that's another story. BR, Antti
