Possible NetworkManager problem with 2.6.35-rc3

Possible NetworkManager problem with 2.6.35-rc3

[Alan]

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.

When I try and start the card through /etc/init.d/network start I get
messages about not being able to start the connection.



Jun 14 13:43:43 zowie NetworkManager[894]:    ifcfg-rh: Acquired D-Bus
service com.redhat.ifcfgrh1
Jun 14 13:43:43 zowie NetworkManager[894]: <info> Loaded plugin ifcfg-rh:
(c) 2007 - 2008 Red Hat, Inc.  To report bugs please use the
NetworkManager mailing list.
Jun 14 13:43:43 zowie NetworkManager[894]:    ifcfg-rh: parsing
/etc/sysconfig/network-scripts/ifcfg-lo ...
Jun 14 13:43:43 zowie NetworkManager[894]:    ifcfg-rh: parsing
/etc/sysconfig/network-scripts/ifcfg-eth0 ...
Jun 14 13:43:43 zowie NetworkManager[894]:    ifcfg-rh:     warning:
NM_CONTROLLED was false but HWADDR was missing; device will be managed
Jun 14 13:43:43 zowie NetworkManager[894]:    ifcfg-rh:     read
connection 'System eth0'
Jun 14 13:43:43 zowie NetworkManager[894]:    ifcfg-rh: parsing
/etc/sysconfig/network-scripts/ifcfg-eth1 ...
Jun 14 13:43:43 zowie NetworkManager[894]:    ifcfg-rh:     read
connection 'System eth1'
Jun 14 13:43:43 zowie NetworkManager[894]: <info> WiFi enabled by radio
killswitch; enabled by state file
Jun 14 13:43:43 zowie NetworkManager[894]: <info> WWAN enabled by radio
killswitch; enabled by state file
Jun 14 13:43:43 zowie NetworkManager[894]: <info> WiMAX enabled by radio
killswitch; enabled by state file
Jun 14 13:43:43 zowie NetworkManager[894]: <info> Networking is enabled by
state file
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...
Jun 14 13:43:43 zowie NetworkManager[894]: <info> modem-manager is now
available
Jun 14 13:43:43 zowie NetworkManager[894]: <warn> bluez error getting
default adapter: The name org.bluez was not provided by any .service files
Jun 14 13:43:43 zowie NetworkManager[894]: <info> Trying to start the
supplicant...

Is there something special I have to set in the kernel config to get this
to work or do I have to get a new version of Network Manager.

It looks like it cannot find all of the driver information.

Any ideas?

Re: Possible NetworkManager problem with 2.6.35-rc3

[Kyle McMartin]

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?

--Kyle

Re: Possible NetworkManager problem with 2.6.35-rc3

[Kyle McMartin]

On Tue, Jun 15, 2010 at 04:50:07AM -0400, Kyle McMartin wrote:
> > In order to get my sata controller to work I built a current kernel using
> > the config file from my Fedora 13 system.
> > 

Also, you should probably attach your dmesg and config file, please.

What did you do? Copy the 2.6.33 config and make oldconfig?

--Kyle

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