From: pablarribas@vodafone.es
To: linux-hotplug@vger.kernel.org
Subject: (no subject)
Date: Sat, 04 Dec 2004 11:58:52 +0000 [thread overview]
Message-ID: <i875a4$4061962996909466341@vodafone.es> (raw)
In-Reply-To: <marc-linux-hotplug-105363331927786@msgid-missing>
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>
Dec 3 13:29:46 localhost kernel: ip_tables: (C) 2000-2002 Netfilter core team
Dec 3 13:29:46 localhost dhclient: sit0: unknown hardware address type 776
Dec 3 13:29:46 localhost kernel: -> vnet_open(atml0)
Dec 3 13:29:46 localhost kernel: Sending Authentication Request with Transaction Sequence Number:1...
Dec 3 13:29:47 localhost kernel: Sending Authentication Request with Transaction Sequence Number:1...
Dec 3 13:29:47 localhost dhclient: sit0: unknown hardware address type 776
Dec 3 13:29:47 localhost kernel: Sending Authentication Request with Transaction Sequence Number:1...
Dec 3 13:29:48 localhost kernel: Sending Authentication Request with Transaction Sequence Number:1...
Dec 3 13:29:49 localhost dhclient: DHCPDISCOVER on atml0 to 255.255.255.255 port 67 interval 4
Dec 3 13:29:49 localhost kernel: Sending Authentication Request with Transaction Sequence Number:1...
Dec 3 13:29:52 localhost last message repeated 4 times
Dec 3 13:29:53 localhost dhclient: DHCPDISCOVER on atml0 to 255.255.255.255 port 67 interval 8
Dec 3 13:29:53 localhost kernel: Sending Authentication Request with Transaction Sequence Number:1...
Dec 3 13:30:00 localhost last message repeated 9 times
Dec 3 13:30:01 localhost dhclient: DHCPDISCOVER on atml0 to 255.255.255.255 port 67 interval 9
Dec 3 13:30:01 localhost kernel: Sending Authentication Request with Transaction Sequence Number:1...
Dec 3 13:30:09 localhost last message repeated 10 times
Dec 3 13:30:10 localhost dhclient: DHCPDISCOVER on atml0 to 255.255.255.255 port 67 interval 18
Dec 3 13:30:10 localhost kernel: Sending Authentication Request with Transaction Sequence Number:1...
Dec 3 13:30:27 localhost last message repeated 20 times
Dec 3 13:30:28 localhost dhclient: DHCPDISCOVER on atml0 to 255.255.255.255 port 67 interval 11
Dec 3 13:30:28 localhost kernel: Sending Authentication Request with Transaction Sequence Number:1...
Dec 3 13:30:38 localhost last message repeated 13 times
Dec 3 13:30:39 localhost dhclient: DHCPDISCOVER on atml0 to 255.255.255.255 port 67 interval 11
Dec 3 13:30:39 localhost kernel: Sending Authentication Request with Transaction Sequence Number:1...
Dec 3 13:30:49 localhost last message repeated 12 times
Dec 3 13:30:50 localhost dhclient: No DHCPOFFERS received.
Dec 3 13:30:50 localhost kernel: Sending Authentication Request with Transaction Sequence Number:1...
Dec 3 13:31:21 localhost last message repeated 39 times
Dec 3 13:32:22 localhost last message repeated 75 times
Dec 3 13:33:23 localhost last message repeated 76 times
Dec 3 13:34:24 localhost last message repeated 76 times
What can I do to make it work? (If there is something...)
Thanks
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-12-04 11: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 [this message]
2004-12-05 2:58 ` Kay Sievers
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='i875a4$4061962996909466341@vodafone.es' \
--to=pablarribas@vodafone.es \
--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).