[Prism54-users] do I need to download a driver for 2.6.11 ?

[Maximilian Engelhardt]

On Mon, 2005-05-23 at 22:40 +0200, Ulrich Lauther wrote:
> -- Start of PGP signed section.
> > On Mon, 2005-05-23 at 17:28 +0200, Ulrich Lauther wrote:
> > > 
> > > when I insert the card, I get:
> > > 
> > > May 23 17:02:08 tahiti kernel: Loaded prism54 driver, version 1.2
> > > May 23 17:02:08 tahiti kernel: ACPI: PCI interrupt 0000:03:00.0[A] -> GSI
> > > 11 (level, low) -> IRQ 11
> > > May 23 17:02:08 tahiti net.agent[3722]: how do I bring interfaces up on
> > > this distro?
> > > May 23 17:02:08 tahiti net.agent[3722]: add event not handled
> > > 
> > > lspci -n gives:
> > > 07:00.0 Class 0280: 1260:3890 (rev 01
> > > 
> > > I guess, above messages are no indication of success?
> > > 
> > Looks good so far, the driver loads and a network interface is created.
> > The only small problem is that your net.agent doesn't know how to bring
> > the interface up.
> > 
> > Try the following:
> > 
> > iwconfig
> >   The interface should be shown as "NOT READY!".
> > 
> yes, but I also get a warning, that I don't know whether I may ignore it or
> not:
> 	Warning : Device eth2 has been compiled with version 17
> 	of Wireless Extension, while we are using version 12.
> 	Some things may be broken...
> 
> 	eth2      NOT READY!  ESSID:off/any  
> 
Look like something (kernel or wireless tools, I don't know ATM) uses an
old version of the Wireless Extension. You can run "iwconfig -v" to find
out more.
> 
> "ifconfig eth2 up" gives me:
> 
> 	SIOCSIFFLAGS: No such file or directory
> 
> in /usr/adm/debug I find:
> 
> May 23 22:15:50 tahiti kernel: eth2: resetting device...
> May 23 22:15:50 tahiti kernel: eth2: uploading firmware...
> 
> (nothing in /usr/adm/messages)
> 
> However, iwconfig still gives "NOT READY!"
> 
> PS: dmesg gives:
> 
> eth2: resetting device...
> eth2: uploading firmware...
> prism54: request_firmware() failed for 'isl3890'
> eth2: could not upload firmware ('isl3890')
> eth2: islpci_reset: failure
> 
> However, I do have isl3890.arm (copied from 1.0.4.3.arm) both in
> /etc/hotplug and in /usr/lib/hotplug/firmware/ (where SHOULD it go?).
> 
The other error messages are all related to the firmware loading
failure. 
Run "grep FIRMWARE_DIR= /etc/hotplug/firmware.agent" to find out where
the firmware to put, but it's usually one of the locations you already
put it in.

You must name the file "isl3890" not "isl3890.arm" so remove the ".arm"
and try again.

If it still doesn't work check you have firmware loading enabled in the
kernel and that sysfs is mounted (in case you are running a 2.6 kernel).

Maxi

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://prism54.org/pipermail/prism54-users/attachments/20050523/ce008d3e/attachment.pgp