[Prism54-users] Help: SMC2802W - firmware loading fails, eth0 does not start

[Milan Zimmermann]

On January 14, 2004 07:44 am, Karl-Heinz Herrmann wrote:
> On Wed, 14 Jan 2004 01:18:43 -0500

<<snip>>

>
> Hmm... what Distribution is that? I had a SuSE 7.2 or 3 and there was a
> hotplug and firmware.agent in place. They have it in /etc/hotplug with
> an unused /etc/hotplug.d/ next to it. My firmware goes to
> /usr/lib/hotplug/firmware/isl3890 (check place and spelling again -- got
> me fooled for some time, number twister in the 38...)

This is SuSE 8.2. It did not have firmware.agent in /etc/hotplug, I copied it 
there and make executable. I just found firmware.agent is never called! I put 
"echo XXX >> /tmp/AA" at the beginning and /tmp/AA is never created ... Would 
you know what is calling firmware.agent and what the reason can be? Thanks!

>
> Then I think the firmware was loading once I try to get eth1 up. But
> this was not working on insertion, only by doing the ifconfig myself.
> I hacked the net.agent to actually get to the place where a network is
> setup and instead of fooling around with more script I just issued the
> iwconfig/ifconfig.

Are you saying I have to run "ifconfig/iwconfig eth0 up" or similar for the 
firmware.agent to be called? I tried "iwconfig eth0" and it said "eth0 does 
not exist ... But in dmesg I see it's attempting to load the firmware, but it 
fails.

Not sure where to take it from here, tomorrow is another day

Thanks Milan
>
> The script sources another source where msg() and debug_msg() are
> defined. They in term use "logger" and this should therfore go to sylogd
> and be logged somewhere in the syslog. For temporary debugging until I
> found the if [] which was preventing to even reach the place I was
> looking at I put direct "logger" debug messages like "entering script
> xy...", "valid net device, interface is ...", "trying the ifconfig",
> etc.
>
> Mind that this can look quite different on another distri but the
> general holds true.
>
>  Hope this helps,
>
>
> K.-H.
> _______________________________________________
> Prism54-users mailing list
> Prism54-users@prism54.org
> http://prism54.org/mailman/listinfo/prism54-users
>
> Milan Zimmermann <milan.zimmermann@sympatico.ca> wrote:
> > Jens,
> >
> > Thanks for your reply - I am getting back to this a week later, was
> > gone last week.
> >
> > I do have firmware.agent in /etc/hotplug, it is executable, still the
> > same problem. I am completely confused as to what to try next, I
> > double checked everything I read in the docs...
> >
> > 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?