From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Sat, 06 Nov 2004 02:16:57 +0000 Subject: Re: airo_cs in Fedora Core 3 test Message-Id: <20041106021657.GB24694@vrfy.org> List-Id: References: <20041105231206.GC1480@iodynamics.com> In-Reply-To: <20041105231206.GC1480@iodynamics.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Fri, Nov 05, 2004 at 08:07:54PM -0700, Doran Barton wrote: > Not long ago, Kay Sievers proclaimed... > > > Could someone tell me if this a udev issue or a kernel issue? > > > > It is caused by the fact, that the driver of the card does not create > > the expected "device" symlink in the class device's sysfs representation, > > pointing to the physical device in sysfs. This symlink is necessary for > > e.g. modern hardware integration to match the virtual with the physical > > device. > > Okay- so it sounds like this is a combination of kernel/PCMCIA code and > udev code which should be resolved soon. > > In the meantime, can I manually create the necessary symlink so I can use > the device? No, You can use the device even without the symlink. If this device is not working, it has nothing to do with udev. > If so, what do I need to know? Just ignore it in the meantime, or upgrade to the latest udev to get rid of the message. These messages are logged to help us collecting all the exceptions, we need to know about, not to sit there and wait with udev for anything that will never appear. Kay ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_idU88&alloc_id065&op=click _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel