Jump to content

Archived

This topic is now archived and is closed to further replies.

Aakaado

pas de connection WiFi

Recommended Posts

ben justement, après le modprobe, il ne te dit rien ?

et quelles sont les 10 dernière lignes du dmesg ?

Share this post


Link to post
Share on other sites

[root@localhost ~]# dmesg | tail -n 6

[<c01c69df>] do_ioctl+0x4f/0x80

[<c01c6bf2>] vfs_ioctl+0x62/0x1d0

[<c01c6da1>] sys_ioctl+0x41/0x70

[<c0102e5d>] sysenter_past_esp+0x52/0x75

Code: 35 ea ff ff 8b 45 fc 8b 80 20 22 00 00 80 a0 d3 10 00 00 00 8b 45 fc ff b0 20 22 00 00 e8 0b f9 00 00 33 c0 5f 5b 5e c9 c2 18 00 <55> 8b ec 83 ec 7c 57 6a 00 ff 75 0c ff 75 08 68 ac 6d 58 e1 ff

<3>ndiswrapper (ndiswrapper_load_driver:98): loadndiswrapper failed (11); check system log for messages from 'loadndisdriver'

(pour modprobe c ok il dit rien apres donc sa veut dire que c normal)

Share this post


Link to post
Share on other sites
Un kernel oops? c'est moyen ça...

J'ai pas compris :S

--------------

[root@localhost 80211g]# ndiswrapper -i bcmwl5.inf

Installing bcmwl5

Forcing parameter IBSSGMode|0 to IBSSGMode|2

Forcing parameter IBSSGMode|0 to IBSSGMode|2

[root@localhost 80211g]# ndiswrapper -l

Installed ndis drivers:

bcmwl5 driver present, hardware present

[root@localhost 80211g]# modprobe ndiswrapper

[root@localhost 80211g]# dmesg | tail -n 20

esi: 00000001 edi: d3c5ac38 ebp: d3e7fefc esp: d3e7fed0

ds: 007b es: 007b ss: 0068

Process loadndisdriver (pid: 7683, threadinfo=d3e7e000 task=d3ede060)

Stack: e1482c0a d3c5ac00 d3e7fee8 00000000 000000d0 00000000 00090009 e149374d

d3c5ac00 e14fd000 d3c5afa0 d3e7ff24 e1482dea d3c5ac00 e14fd000 e14fd000

b7e83008 000301a8 00000000 e14fd000 fffffff7 d3e7ff4c e1483498 e14fd000

Call Trace:

[<c0103c4f>] show_stack+0x7f/0xa0

[<c0103de6>] show_registers+0x156/0x1d0

[<c0103fe8>] die+0xc8/0x150

[<c011637a>] do_page_fault+0x47a/0x71a

[<c01038eb>] error_code+0x2b/0x30

[<e1482dea>] load_ndis_driver+0x9a/0x110 [ndiswrapper]

[<e1483498>] wrapper_ioctl+0x78/0xe0 [ndiswrapper]

[<c01c69df>] do_ioctl+0x4f/0x80

[<c01c6bf2>] vfs_ioctl+0x62/0x1d0

[<c01c6da1>] sys_ioctl+0x41/0x70

[<c0102e5d>] sysenter_past_esp+0x52/0x75

Code: 35 ea ff ff 8b 45 fc 8b 80 20 22 00 00 80 a0 d3 10 00 00 00 8b 45 fc ff b0 20 22 00 00 e8 0b f9 00 00 33 c0 5f 5b 5e c9 c2 18 00 <55> 8b ec 83 ec 7c 57 6a 00 ff 75 0c ff 75 08 68 ac 6d 58 e1 ff

<3>ndiswrapper (ndiswrapper_load_driver:98): loadndiswrapper failed (11); check system log for messages from 'loadndisdriver'

Share this post


Link to post
Share on other sites
J'ai pas compris :S

oops

    An oops is generated on some kernel errors. This may be due to kernel bugs or faulty hardware (especially bad RAM). Often the kernel can continue to operate mostly correctly after an oops. More serious or potentially dangerous errors can cause a kernel panic (the O/S freezes). This is sometimes done to protect a filesystem from incurring further harm. An oops report will appear in the kernel logs, but is only useful to developers after decoding it with ksymoops (see Documentation/oops-tracing.txt). Note also that klogd can corrupt oops reports by incorrectly decoding it automatically. It is recommended to pass the -x option to klogd on startup to prevent this from happening. The plural form is oopsen.

http://www.kernelhacking.org/docs/kernelha...O/indexs17.html

Share this post


Link to post
Share on other sites

Tu suggere que j'ai un probleme materiel ? :/

Ta pas de solution plus constructive... ? :S sa c une solution deprimante :S !

Personne peut vraiment rien pour moi ?

Share this post


Link to post
Share on other sites
Tu suggere que j'ai un probleme materiel ? :/

Ta pas de solution plus constructive... ? :S sa c une solution deprimante :S !

Personne peut vraiment rien pour moi ?

non, je dirais "kernel bug"

Share this post


Link to post
Share on other sites

×
×
  • Create New...