[Prism54-users] eth1 won't com up during boot
Elimar Riesebieter
riesebie@lxtec.de
Sun, 4 Jan 2004 22:50:06 +0100
--7AUc2qLy4jB3hD7Z
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sat, 03 Jan 2004 the mental interface of=20
Elimar Riesebieter told:
> Hi list,
>=20
> 1st I want to tell that a SMC2835W is running on my ppc-albook with
> kernel 2.6.1-rc1-ben1 ;-)
>=20
> 2nd is, that the bounded eth1 doesn't com up during boot. I have to
> start the interface by hand.
I do not know wether this is the right place for posting as follows:
I installed the kernelpatch from 04.01.2004 because I sugested the
changelog:
=2E.. This fixes startup with SMC2835W ....
While bootup the following oops appears:
Yenta: CardBus bridge found at 0001:01:13.0 [0000:0000]
Yenta: ISA IRQ mask 0x0000, PCI irq 53
Socket status: 30000868
bound device '0001:01:13.0' to driver 'yenta_cardbus'
input: USB HID v1.11 Keyboard [05ac:1000] on usb-0001:01:1a.0-1
bound device '2-1:1.0' to driver 'hid'
bus usb: add device 2-1:1.1
drivers/usb/input/hid-core.c: ctrl urb status -32 received
input: USB HID v1.11 Mouse [05ac:1000] on usb-0001:01:1a.0-1
bound device '2-1:1.1' to driver 'hid'
PCI: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'
eth1: could not upload firmware ('isl3890')
eth1: islpci_open()
eth1: resetting device...
eth1: uploading firmware...
request_module: failed /sbin/modprobe -- char-major-10-135. error =3D 256
prism54: request_firmware() failed for 'isl3890'
eth1: could not upload firmware ('isl3890')
Oops: kernel access of bad area, sig: 11 [#1]
NIP: C00530E8 LR: C0053250 SP: EE23BEF0 REGS: ee23be40 TRAP: 0301 Not ta=
inted
MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 00000084, DSISR: 40000000
TASK =3D ee14aa80[686] 'cp' Last syscall: 4=20
GPR00: C0087C7C EE23BEF0 EE14AA80 FFFFFFF7 00000000 00001000 EE11ED00 0FF25=
8A8=20
GPR08: 0000D032 C026511C EE11ECE0 00000002 00000000=20
Call trace:
[c0053250] sys_write+0x40/0x74
[c0007c0c] ret_from_syscall+0x0/0x4c
Oops: kernel access of bad area, sig: 11 [#2]
NIP: C006EC9C LR: C00527E4 SP: EE23BCB0 REGS: ee23bc00 TRAP: 0301 Not ta=
inted
MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 00000020, DSISR: 40000000
TASK =3D ee14aa80[686] 'cp' Last syscall: 4=20
GPR00: C00527E4 EE23BCB0 EE14AA80 00000000 EE6A6920 00000064 00000000 EEB8D=
26C=20
GPR08: 0000004C EE1DB080 EFFFBA10 EE11ECE0 8210C082=20
Call trace:
[c00527e4] filp_close+0x64/0xbc
[c001d398] put_files_struct+0xac/0x110
[c001e168] do_exit+0x1e4/0x450
[c00085a4] _exception+0x0/0x74
[c0012d8c] bad_page_fault+0x5c/0x60
[c0012b68] do_page_fault+0x1e0/0x3a8
[c0008218] ret_from_except+0x0/0x1c
[c00530e8] vfs_write+0x74/0x128
[c0053250] sys_write+0x40/0x74
[c0007c0c] ret_from_syscall+0x0/0x4c
######################################
eth1 was not up, so I did ifconfig up. Afterwards iwconfig eth1
shows correct key but no essid from my wireless-tools. I did a
iwconfig eth1 essid BLAFASEL and iwconfig shows:
eth1 (WE) : Buffer for request 8B1B too small (33<256)
eth1 SMC2835W Mode:Managed Channel:8
=2E.........
=2E.........
Do I have to report a bug? If someone needs more infos, please
contact me!
Ciao
Elimar
--=20
>what IMHO then?
IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
--posting from alex in debian-user--
--7AUc2qLy4jB3hD7Z
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQE/+IqO3Ig8bsVPf7ARAnDpAJ93EJMP4D3Da2Ry8AjRiRaQBjoD8ACgunti
4q6mZoIapr22kmIE4Ep47pk=
=qT+M
-----END PGP SIGNATURE-----
--7AUc2qLy4jB3hD7Z--