airo_cs in Fedora Core 3 test

airo_cs in Fedora Core 3 test

[Doran Barton]

Hey people,

I'm running the 2.4.9-643 kernel for FC3t3 on a HP Pavilion zv5000z laptop
(AMD Athlon 64 3000). With the 2.4.8 kernel on FC2, I had no problem using
my Aironet 350 PCMCIA wireless network adapter, but there was no udev in
FC2.

So, when I insert the card now, I get this in my messages file:

  Nov  5 14:49:29 moo kernel: eth1: index 0x05: Vcc 5.0, Vpp 5.0, irq 11, io
  0x4100-0x413f
  Nov  5 14:49:34 moo wait_for_sysfs[5906]: either wait_for_sysfs (udev 039)
  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,
  please report to <linux-hotplug-devel@lists.sourceforge.net>
  Nov  5 14:49:34 moo wait_for_sysfs[5908]: either wait_for_sysfs (udev 039)
  needs an update to handle the device '/class/net/wifi0' 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>
  
Could someone tell me if this a udev issue or a kernel issue?

THanks!

-- 
fozz@iodynamics.com is Doran L. Barton, president, Iodynamics LLC
Iodynamics: Linux solutions - Web development - Business connectivity
 "New study of obesity looks for larger test group"
    -- Headline seen in newspaper


-------------------------------------------------------
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

Re: airo_cs in Fedora Core 3 test

[Kay Sievers]

On Fri, Nov 05, 2004 at 04:12:06PM -0700, Doran Barton wrote:
> Hey people,
> 
> I'm running the 2.4.9-643 kernel for FC3t3 on a HP Pavilion zv5000z laptop
> (AMD Athlon 64 3000). With the 2.4.8 kernel on FC2, I had no problem using
> my Aironet 350 PCMCIA wireless network adapter, but there was no udev in
> FC2.
> 
> So, when I insert the card now, I get this in my messages file:
> 
>   Nov  5 14:49:29 moo kernel: eth1: index 0x05: Vcc 5.0, Vpp 5.0, irq 11, io
>   0x4100-0x413f
>   Nov  5 14:49:34 moo wait_for_sysfs[5906]: either wait_for_sysfs (udev 039)
>   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,
>   please report to <linux-hotplug-devel@lists.sourceforge.net>
>   Nov  5 14:49:34 moo wait_for_sysfs[5908]: either wait_for_sysfs (udev 039)
>   needs an update to handle the device '/class/net/wifi0' 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>
>   
> 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.

1.
PCMCIA-sysfs is not supported now, but already in the -mm kernel, so this
should be fixed sooner than later.

2.
The latest wait_for_sysfs in the udev package will not print any error for
net devices.

3.
Kernel 2.6.10* and later will add what we can expect in sysfs to the hotplug
event, so we can handle that right, without useless waiting for the symlink
and printing errors.

o.k.? :)

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

Re: airo_cs in Fedora Core 3 test

[Kay Sievers]

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_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

Re: airo_cs in Fedora Core 3 test

[Doran Barton]

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? If so, what do I need to know?

-=Fozz

-- 
fozz@iodynamics.com is Doran L. Barton, president, Iodynamics LLC
Iodynamics: Linux solutions - Web development - Business connectivity
 "Hospitals are sued by 7 foot doctors"
    -- Headline seen in newspaper


-------------------------------------------------------
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