On Thu, 2007-01-04 at 15:57 -0800, Greg KH wrote: > On Thu, Jan 04, 2007 at 11:50:02PM +0000, Hugh Dickins wrote: > > On Thu, 4 Jan 2007, Greg KH wrote: > > > On Sat, Dec 30, 2006 at 02:47:20AM -0800, Miles Lane wrote: > > > > Sorry Andrew, I am not sure which maintainer to contact about this. I > > > > CCed gregkh for sysfs and Yi for ipw2200. Hopefully this is helpful. > > > > BTW, I also found that none of my network drivers were recognized by > > > > hal (lshal did not show their "net" entries) unless I set > > > > CONFIG_SYSFS_DEPRECATED=y. I am running Ubuntu development (Feisty > > > > Fawn), so it seems like I ought to be running pretty current hal > > > > utilities: hal-device-manager 0.5.8.1-4ubuntu1. After > > > > reenabling CONFIG_SYSFS_DEPRECATED, I am able to use my IPW2200 > > > > driver, in spite of this recursive locking message, so this INFO > > > > message may not indicate a problem. > > > > > > Does this show up on the 2.6.20-rc3 kernel too? > > > > Yes. Well, I can't speak for Miles on Ubuntu, but I have ipw2200 > > on openSUSE 10.2 (using ifplugd if that matters), and have to build > > my 2.6.20-rc3 with CONFIG_SYSFS_DEPRECATED=y in order to get an IP > > address (no idea whether it's a hald issue in my case). Likewise > > needed CONFIG_SYSFS_DEPRECATED=y with 2.6.19-rc-mm on SuSE 10.1. > > I was referring to the locking traceback :) > > But anyway, Kay, I thought that 10.2 would work with > CONFIG_SYSFS_DEPRECATED=y?
Yes, HAL, udev, NetworkManager, ... from 10.2 works fine here, without that option set. Kay - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
