Re: Possible NetworkManager problem with 2.6.35-rc3

[Dan Williams]

On Tue, 2010-06-15 at 04:50 -0400, Kyle McMartin wrote:
> On Mon, Jun 14, 2010 at 02:26:55PM -0700, Alan wrote:
> > In order to get my sata controller to work I built a current kernel using
> > the config file from my Fedora 13 system.
> > 
> > Everything works except for networking.
> > 
> > It uses the forcedeth driver, but network manager does not want to see the
> > card whatsoever.
> > 
> <snip>
> > Jun 14 13:43:43 zowie NetworkManager[894]: <warn> /sys/class/net/eth0:
> > couldn't determine device driver; ignoring...
> > Jun 14 13:43:43 zowie NetworkManager[894]: <warn> /sys/class/net/eth1:
> > couldn't determine device driver; ignoring...
> 
> Even if there is a sysfs bug in 2.6.35-rc3, it looks pretty braindead
> that network-manager falls over for this.
> 
> Dan, any ideas?

Yes, we require a correctly set up sysfs.  It's not strictly necessary,
but the checks for driver are there to validate the driver that the
hardware uses.  If the driver isn't setting up sysfs correctly, it's a
sure bet something else is wrong or that the driver is a pile of
steaming junk.

cd -P /sys/class/net/eth0/device
ls -al
cd -P driver
pwd

and lets see what we get.  If the "cd -P driver" doesn't dump you into
the directory for that driver (ie 'forcedeth' or 'e1000e' etc) then the
driver needs to get fixed.

Dan

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/