* Re: wait_for_sysfs update for orinoco (eth)
2004-11-03 9:58 wait_for_sysfs update for orinoco (eth) Max Kutny
@ 2004-11-03 11:11 ` Kay Sievers
2004-11-03 12:58 ` Max Kutny
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: Kay Sievers @ 2004-11-03 11:11 UTC (permalink / raw)
To: linux-hotplug
On Wed, Nov 03, 2004 at 11:58:08AM +0200, Max Kutny wrote:
> I've got the following in the syslog:
>
> either wait_for_sysfs (udev 042) needs an update to handle the device
> '/class/net/eth1' properly (no device symlink) or the sysfs-support of
> your device's driver needs to be fixed.
>
> As I see, /sys/class/net/eth1 directory exists, so it's not the driver
> problem.
>
> Just in case, here are the correspondent eth1 module lines from syslog:
>
> Nov 3 11:11:22 localhost cardmgr[6566]: executing: 'modprobe orinoco_cs'
> Nov 3 11:11:22 localhost kernel: orinoco 0.13e (David Gibson <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
> Nov 3 11:11:22 localhost kernel: orinoco_cs 0.13e (David Gibson <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
> Nov 3 11:11:23 localhost kernel: eth1: Station identity 001f:0001:0008:000a
> Nov 3 11:11:23 localhost kernel: eth1: Looks like a Lucent/Agere firmware version 8.10
> Nov 3 11:11:23 localhost kernel: eth1: Ad-hoc demo mode supported
> Nov 3 11:11:23 localhost kernel: eth1: IEEE standard IBSS ad-hoc mode supported
> Nov 3 11:11:23 localhost kernel: eth1: WEP supported, 104-bit key
> Nov 3 11:11:23 localhost kernel: eth1: MAC address 00:02:2D:69:CB:C1
> Nov 3 11:11:23 localhost kernel: eth1: Station name "HERMES I"
> Nov 3 11:11:23 localhost kernel: eth1: ready
> Nov 3 11:11:23 localhost kernel: eth1: index 0x01: Vcc 3.3, irq 10, io 0x0100-0x013f
Thanks, but the message will stay until the pcmcia sysfs support reaches
the mainline kernel and the pcmcia drivers can be changed to create
the "device" symlink to the physical device. The pcmcia sysfs support is
already in the -mm tree.
Thanks,
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_id\x12065&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
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: wait_for_sysfs update for orinoco (eth)
2004-11-03 9:58 wait_for_sysfs update for orinoco (eth) Max Kutny
2004-11-03 11:11 ` Kay Sievers
@ 2004-11-03 12:58 ` Max Kutny
2004-11-03 13:56 ` Kay Sievers
2004-11-03 14:20 ` Max Kutny
3 siblings, 0 replies; 5+ messages in thread
From: Max Kutny @ 2004-11-03 12:58 UTC (permalink / raw)
To: linux-hotplug
On Wed, Nov 03, 2004 at 12:11:28PM +0100, Kay Sievers wrote:
> On Wed, Nov 03, 2004 at 11:58:08AM +0200, Max Kutny wrote:
> >
> > either wait_for_sysfs (udev 042) needs an update to handle the device
> > '/class/net/eth1' properly (no device symlink) or the sysfs-support of
> > your device's driver needs to be fixed.
> >
> > As I see, /sys/class/net/eth1 directory exists, so it's not the driver
> > problem.
>
> Thanks, but the message will stay until the pcmcia sysfs support reaches
> the mainline kernel and the pcmcia drivers can be changed to create
> the "device" symlink to the physical device.
Oh, I see now. Misunderstanding rised because syslog entry appeared to
be a bit ambiguous. Since I'm not deep in udev I didn't realized from
that message that there should be '/sys/class/net/eth1/device' symlink
pointing to the physical device. Might it be worth to rewrite udev
message?
And one more unclarity: why udev writes that it needs an update in
case it's a driver problem?
-- Max
-------------------------------------------------------
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_id\x12065&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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: wait_for_sysfs update for orinoco (eth)
2004-11-03 9:58 wait_for_sysfs update for orinoco (eth) Max Kutny
2004-11-03 11:11 ` Kay Sievers
2004-11-03 12:58 ` Max Kutny
@ 2004-11-03 13:56 ` Kay Sievers
2004-11-03 14:20 ` Max Kutny
3 siblings, 0 replies; 5+ messages in thread
From: Kay Sievers @ 2004-11-03 13:56 UTC (permalink / raw)
To: linux-hotplug
On Wed, 2004-11-03 at 14:58 +0200, Max Kutny wrote:
> On Wed, Nov 03, 2004 at 12:11:28PM +0100, Kay Sievers wrote:
> > On Wed, Nov 03, 2004 at 11:58:08AM +0200, Max Kutny wrote:
> > >
> > > either wait_for_sysfs (udev 042) needs an update to handle the device
> > > '/class/net/eth1' properly (no device symlink) or the sysfs-support of
> > > your device's driver needs to be fixed.
> > >
> > > As I see, /sys/class/net/eth1 directory exists, so it's not the driver
> > > problem.
> >
> > Thanks, but the message will stay until the pcmcia sysfs support reaches
> > the mainline kernel and the pcmcia drivers can be changed to create
> > the "device" symlink to the physical device.
>
> Oh, I see now. Misunderstanding rised because syslog entry appeared to
> be a bit ambiguous. Since I'm not deep in udev I didn't realized from
> that message that there should be '/sys/class/net/eth1/device' symlink
> pointing to the physical device. Might it be worth to rewrite udev
> message?
>
> And one more unclarity: why udev writes that it needs an update in
> case it's a driver problem?
Some devices are virtual only and don't have this symlink for good
reason. So wait_for_sysfs may need a new entry to handle it or the
driver needs to create the link - wait_for_sysfs can't be sure
what's wrong here.
But it's a good question. We may print a more specific message in the
class/net/eth* case. I will look into that.
Thanks,
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_id\x12065&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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: wait_for_sysfs update for orinoco (eth)
2004-11-03 9:58 wait_for_sysfs update for orinoco (eth) Max Kutny
` (2 preceding siblings ...)
2004-11-03 13:56 ` Kay Sievers
@ 2004-11-03 14:20 ` Max Kutny
3 siblings, 0 replies; 5+ messages in thread
From: Max Kutny @ 2004-11-03 14:20 UTC (permalink / raw)
To: linux-hotplug
On Wed, Nov 03, 2004 at 02:56:16PM +0100, Kay Sievers wrote:
> On Wed, 2004-11-03 at 14:58 +0200, Max Kutny wrote:
> > On Wed, Nov 03, 2004 at 12:11:28PM +0100, Kay Sievers wrote:
> > > On Wed, Nov 03, 2004 at 11:58:08AM +0200, Max Kutny wrote:
> > > >
> > > > either wait_for_sysfs (udev 042) needs an update to handle the device
> > > > '/class/net/eth1' properly (no device symlink) or the sysfs-support of
> > > > your device's driver needs to be fixed.
> > > >
> > > > As I see, /sys/class/net/eth1 directory exists, so it's not the driver
> > > > problem.
> > >
> > > Thanks, but the message will stay until the pcmcia sysfs support reaches
> > > the mainline kernel and the pcmcia drivers can be changed to create
> > > the "device" symlink to the physical device.
> >
> > Oh, I see now. Misunderstanding rised because syslog entry appeared to
> > be a bit ambiguous. Since I'm not deep in udev I didn't realized from
> > that message that there should be '/sys/class/net/eth1/device' symlink
> > pointing to the physical device. Might it be worth to rewrite udev
> > message?
> >
> > And one more unclarity: why udev writes that it needs an update in
> > case it's a driver problem?
>
> Some devices are virtual only and don't have this symlink for good
> reason. So wait_for_sysfs may need a new entry to handle it or the
> driver needs to create the link - wait_for_sysfs can't be sure
> what's wrong here.
That's clear now.
> But it's a good question. We may print a more specific message in the
> class/net/eth* case. I will look into that.
I'd suggest to put the message in the following way to make it more
clear:
"udev-042: there is no symlink '/sys/class/net/eth1/device' pointing to
the physical 'eth1' device. Either it's a virtual device in which case
udev should be updated in order to handle it properly or proper sysfs
support is missing in the device driver. In both cases please report
to linux-hotplug-devel@lists.sourceforge.net".
Thanks.
-- Max
-------------------------------------------------------
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_id\x12065&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
^ permalink raw reply [flat|nested] 5+ messages in thread