[Prism54-users] eth1 won't com up during boot

[Elimar Riesebieter]

--Kj7319i9nmIyA2yE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi list,

1st I want to tell that a SMC2835W is running on my ppc-albook with
kernel 2.6.1-rc1-ben1 ;-)

2nd is, that the bounded eth1 doesn't com up during boot. I have to
start the interface by hand.

Debian unstable
hotplug-version: 0.0.20031013
/usr/lib/hotplug/firmware/isl3890 exists
/sys is mounted via fstab: none /sys sysfs defaults 0 0
The card is configured via wireless-tools.
I am not running pcmcia-cs.
yenta_socket is loaded at boottime (via /etc/modules)
alias eth1 prism54 is set in /lib/modules/modprobe.conf.
patchversion: /usr/src/patch-2.6.0-prism54-cvs20031230.bz2

syslog tells while running /etc/init.d/networking:

I:0001:02:00.0 Resource 0 [00000000-00001fff] is unassigned
bus pci: add device 0001:02:00.0
Loaded prism54 driver, version 1.0.2.2
bus pci: add driver prism54
PCI: Enabling device 0001:02:00.0 (0000 -> 0002)
bound device '0001:02:00.0' to driver 'prism54'
eth1: prism54_mib_init()
eth1: islpci_open()
eth1: resetting device...
eth1: uploading firmware...
prism54: request_firmware() failed for 'isl3890'

I suppose eth1 doesn:t come up at that time, because it is not
present?

Thanks for any hint.

Elimar

--=20
  Excellent day for drinking heavily.=20
  Spike the office water cooler;-)

--Kj7319i9nmIyA2yE
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQE/9rgD3Ig8bsVPf7ARAh5AAJ47rIw4ial7GNGSDbNk6FSmMW02fgCgtolj
pG7kfarfPWiIEjrvtRImink=
=RRro
-----END PGP SIGNATURE-----

--Kj7319i9nmIyA2yE--