[Prism54-users] Help: SMC2802W - SUCCESS on SuSE 8.2 (with newer hotplug), Thanks

[Milan Zimmermann]

Jens, Sepp,

Thanks both of you for your suggestions.

The core of my problem was, as you both of you suggested, the '/sbin/hotplug'. 

SuSE 8.2 seems to have a very old version (2001) and once I put some echo 
statements there, they showed it never makes it behind first line, it 
expected file "/var/lock/subsys/hotplug' file to exist and it was not there.

Once I changed that, things started working but I upgraded to latest hotplug 
from SourceForge anyway.

Everything works nicely, and seems quite fast.

For all who have SuSE 8.2 - it seems that updating hotplug is a wise thing to 
do before installing wireless.

Thanks again to all who helped, Milan

On January 17, 2004 05:02 am, Sepp Heid wrote:
> Hi,
>
> I running SuSe 9.0 with a Netgear WG511: hotplugging is working ok. What
> I had to do is
> to add a 'firmware.agent' to the standard distribution and to enable PCI
> in '/etc/syconfig/hotplug'
> which for unknown reason was disabled. Perhaps you check the settings in
> '/etc/syconfig/hotplug'!
>
> I ran the Netgear WG511also under SuSE 8.2 but probably without
> 'firmware.agent'. Perhaps
> the SuSe 8.2 '/sbin/hotplug' is too old for 'firmware.agent' and an
> update will do!
>
> h
>
> Milan Zimmermann wrote:
> >Jens,
> >
> >Thanks for your help again. By putting some echos into firmware.agent (it
> > is executable) I found it is never called ...  would you know who should
> > be calling it and what can be the reason it is not hapennig?
> >
> >Milan
> >
> >On January 15, 2004 02:17 pm, Jens Maurer wrote:
> >>Milan Zimmermann wrote:
> >>>I'd like to get some suggestion on how to debug this problem, for
> >>>example, can I put some echos inside the firmware.agent and see what the
> >>>$DEVPATH and $FIRMWARE are set to?  Where do they come from when
> >>>firmware.agent is executed? If I set the DEBUG=yes, where is the output
> >>>going to be?
> >>
> >>All the hotplug stuff are simple shell scripts, so you can put in
> >>"echo" statements as much as you please.  To circumvent any potential
> >>issues with syslog etc., I'd recommend doing it so
> >>   echo "hello I'm here" >> /tmp/mylog
> >>
> >>This will put the stuff in /tmp/mylog, which is the most direct
> >>way you'll get debugging info out of the script.
> >>
> >>Make a backup copy before changing any script, and then hack
> >>away until you find out the control flow in your specific
> >>case.  And where it fails the firmware loading.
> >>
> >>Jens Maurer
> >
> >_______________________________________________
> >Prism54-users mailing list
> >Prism54-users@prism54.org
> >http://prism54.org/mailman/listinfo/prism54-users
>
> _______________________________________________
> Prism54-users mailing list
> Prism54-users@prism54.org
> http://prism54.org/mailman/listinfo/prism54-users