linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: (no subject)
Date: Sun, 05 Dec 2004 02:58:30 +0000	[thread overview]
Message-ID: <1102215510.5596.19.camel@localhost.localdomain> (raw)
In-Reply-To: <marc-linux-hotplug-105363331927786@msgid-missing>

On Sat, 2004-12-04 at 12:58 +0100, pablarribas@vodafone.es wrote:
>  Another wait_for_sysfs error. I came across this one trying to make the atmelwlan sourceforge driver:
> Dec  3 13:29:40 localhost kernel: usb 1-1: new full speed USB device using address 4
> Dec  3 13:29:40 localhost kernel: usb vendor/product\x1371/13
> Dec  3 13:29:40 localhost kernel: usbvnet5_2958: driver version 2.0.1.0, compiled Dec  3 2004 11:46:34 (dbg_mask x0)
> Dec  3 13:29:40 localhost kernel: MAC addr 00:08:A1:6B:8B:B6 firmware 1.103.0.175
> Dec  3 13:29:41 localhost kernel: Sending Authentication Request with Transaction Sequence Number:1...
> Dec  3 13:29:45 localhost last message repeated 6 times
> Dec  3 13:29:46 localhost wait_for_sysfs[3626]: either wait_for_sysfs (udev 039) needs an update to handle the device '/class/net/atml0' properly (no device symlink) or the sysfs-support of your device's driver needs to be fixed, please report to <linux-hotplug-devel@lists.sourceforge.net>

>  What can I do to make it work? (If there is something...)

The message is unrelated to your nonworking device.
A later versions of udev will not print it.

Thanks and good luck,
Kay



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
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

  parent reply	other threads:[~2004-12-05  2:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22 19:49 (no subject) Curtis Lehman
2003-05-22 21:10 ` Greg KH
2003-05-22 22:41 ` Curtis Lehman
2003-05-23  1:03 ` Johannes Erdfelt
2003-05-23 22:19 ` Greg KH
2004-02-16 15:15 ` christophe.varoqui
2004-10-09 13:36 ` Emilia Greenberg
2004-12-04 11:58 ` pablarribas
2004-12-05  2:58 ` Kay Sievers [this message]
2005-04-05 18:58 ` craig
2005-04-05 20:23 ` Patrick Mansfield
2005-05-04 17:30 ` Layne Garrett Pedersen
2005-05-04 17:40 ` Kay Sievers
2005-05-06 13:27 ` Victor Riquelme Durán
2005-05-16 22:50 ` Kay Sievers
2005-06-02 11:52 ` Rajat Jain
2005-06-05  7:21 ` shubhrangam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1102215510.5596.19.camel@localhost.localdomain \
    --to=kay.sievers@vrfy.org \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).