On Thu, 2008-04-03 at 08:35 -0800, Jeff Spaleta wrote: > On Thu, Apr 3, 2008 at 6:10 AM, Adam Jackson <ajackson@xxxxxxxxxx> wrote: > > Dan Williams actually tracked this down a while ago. Thank you for > > reminding me, I'll push out an update for this. > > The only reason i ran into it was because NM stopped seeing my wired > network hardware. > So i flipped over to the legacy network script and was greeted with > this far more fascinating perversion of application hang ups when the > network segment changes. > > Once this gets fixed, I'll get back to trying to figure out why NM > doesn't see that eth0 exists. If you check your ifcfg files, do they have NM_CONTROLLED=false in them? Or is the device itself not seen by NM at all any more? If the later (and nm-tool doesn't show it) the output of 'lshal' would be quite useful. Dan -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
