From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Wed, 20 Oct 2004 13:17:17 +0000 Subject: Re: [Report about error: unknown bus] Message-Id: <20041020131717.GB13394@vrfy.org> List-Id: References: <1098244606.7230.7.camel@blaze.homeip.net> In-Reply-To: <1098244606.7230.7.camel@blaze.homeip.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Wed, Oct 20, 2004 at 01:33:45AM -0400, Paul Blazejowski wrote: > On Wed, 2004-10-20 at 06:27 +0200, Kay Sievers wrote: > > > A lot of these errors are already fixed. If possible, please update to a > > newer version of udev. If you still get errors, please report it again. > > We've added some more detailed information to the log, to see what exactly > > failed. > > > > Thanks, > > Kay > > > > Kay, thanks for suggestion. > > I did upgrade to 040 and it still spits some errors such as: > > unknown bus, please > report to 'ieee1394' Fine, I will go fix that tonight. > '/devices/pci0000:00/0000:00:0d.0/fw-host0' properly (unknown bus) Greg, any idea how to handle that properly? Should we exclude "fw-host*"? Or is it expected to have a "bus" and the firewire driver should be fixed instead? > '/class/net/eth1' properly (no device symlink) What driver creates the eth1 device? It needs to crete the "device" symlink and the maintainer should know. Thanks, Kay ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ 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