[Prism54-users] weird process
Hugo Koren
hugo@deltaman.nl
Wed, 5 Nov 2003 23:56:38 +0100
This is a multi-part message in MIME format.
------=_NextPart_000_003C_01C3A3F8.7386B210
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi,
I have a weird process:
http://deltaman.nl/prism54/weird_process.jpg
Talking about the process with the big number.
I don't see this with a standard kernel from redhat.
Is it bad?
Running kernel is 2.4.23-pre9.
I also don't have the SMC2802W card running with this new kernel.
When I try to load the module I am getting this error:
/lib/modules/2.4.23-pre9/kernel/drivers/net/wireless/prism54/prism54.o
/lib/modules/2.4.23-pre9/kernel/drivers/net/wireless/prism54/prism54.o: =
unresolved symbol request_firmware_Rsmp_38ce5074
/lib/modules/2.4.23-pre9/kernel/drivers/net/wireless/prism54/prism54.o: =
unresolved symbol release_firmware_Rsmp_33934162
Now I noticed that after the reboot only 1 network card worked, out of =
3.
eth0 =3D 3com [worked after reboot]
eth1 =3D prism54 [insmod error] (SMC2802W PCI)
eth2 =3D realtek8139 [did not worked after the reboot]
I have tried something that Luis R. Rodriguez told me to check =
yesterday:
>> 12: 84 106 IO-APIC-level eth0, PS/2 Mouse
>Try rmmoding the module for your other eth's, and leave just prism54.
>Repeat for each module, see if they are fighting for the IRQ.
What I did:
modprobe -r <3com module>
modprobe prism54
Still getting the same insmod error's
Grtz,
Hugo
------=_NextPart_000_003C_01C3A3F8.7386B210
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1264" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I have a weird process:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><A=20
href=3D"http://deltaman.nl/prism54/weird_process.jpg">http://deltaman.nl/=
prism54/weird_process.jpg</A></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Talking about the process with the big=20
number.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I don't see this with a standard kernel =
from=20
redhat.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Is it bad?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Running kernel is =
2.4.23-pre9.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I also don't have the SMC2802W =
card running=20
with this new kernel.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>When I try to load the module I am =
getting this=20
error:</FONT></DIV>
<DIV>/lib/modules/2.4.23-pre9/kernel/drivers/net/wireless/prism54/prism54=
.o<BR>/lib/modules/2.4.23-pre9/kernel/drivers/net/wireless/prism54/prism5=
4.o:=20
unresolved symbol=20
request_firmware_Rsmp_38ce5074<BR>/lib/modules/2.4.23-pre9/kernel/drivers=
/net/wireless/prism54/prism54.o:=20
unresolved symbol release_firmware_Rsmp_33934162</DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV>
<DIV><FONT face=3DArial size=3D2>Now I noticed that after the =
reboot only 1=20
network card worked, out of 3.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>eth0 =3D=20
3com =
[worked after=20
reboot]</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>eth1 =3D=20
prism54 [insmod error] =
(SMC2802W=20
PCI)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>eth2 =3D =
realtek8139 [did not worked=20
after the reboot]</FONT></DIV></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I have tried something that Luis R. =
Rodriguez told=20
me to check yesterday:</FONT></DIV>
<DIV>>> 12: =20
84 106 =
IO-APIC-level =20
eth0, PS/2 Mouse<BR>>Try rmmoding the module for your other eth's, =
and leave=20
just prism54.<BR>>Repeat for each module, see if they are fighting =
for the=20
IRQ.<BR></DIV>
<DIV><FONT face=3DArial size=3D2>What I did:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>modprobe -r <3com =
module></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>modprobe prism54</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Still getting the same insmod =
error's</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Grtz,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Hugo</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV></BODY></HTML>
------=_NextPart_000_003C_01C3A3F8.7386B210--