Re: 2.6.19-rc3-mm1 -- missing network adaptors

[Greg KH <gregkh@suse.de>]

On Tue, Oct 31, 2006 at 06:11:13PM -0800, Martin Bligh wrote:
> Greg KH wrote:
> >On Tue, Oct 31, 2006 at 05:39:10PM -0800, Martin Bligh wrote:
> >
> >>Cornelia Huck wrote:
> >>
> >>>On Tue, 31 Oct 2006 09:09:16 -0800,
> >>>"Martin J. Bligh" <mbligh@google.com> wrote:
> >>>
> >>>
> >>>
> >>>>Cornelia Huck wrote:
> >>>>
> >>>>
> >>>>>That's because /sys/class/net/<interface> is now a symlink instead of a
> >>>>>directory (and that hasn't anything to do with acpi, but rather with
> >>>>>the conversions in the driver tree). Seems the directory -> symlink
> >>>>>change shouldn't be done since it's impacting user space...
> >>>>
> >>>>You know which individual patch in -mm broke that? Can't see it easily.
> >>>>Then we can just test across all the machines with just that one backed
> >>>>out.
> >>>
> >>>
> >>>I'd try reverting gregkh-driver-network-device.patch for the network
> >>>device stuff.
> >>
> >>Reverting that patch does indeed appear to fix it.
> >
> >
> >Even with CONFIG_SYSFS_DEPRECATED enabled?  For some reason I'm guessing
> >that you missed that suggestion a while back...
> 
> Yes - Enabling CONFIG_SYSFS_DEPRECATED didn't help.

Ok, you are correct, for a stupid reason, this option didn't correctly
work for a range of device types (I can get into the gory details if
anyone really cares...)

I've now fixed this up, and a few other bugs that I kept tripping on
(which others also hit), and have refreshed my tree so that the next -mm
will be much better in this area.

If the problem persists (and I've built a zillion different kernels in
different configurations today testing to make sure it doesn't), please
let me know.

I can post updated patches here if people want them.

thanks for everyone's patience, I appreciated it.

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