forty
Bonjour je possede un carte wifi Linsys WMP54G dont le chipset est RT2561/RT61. J'ai compilé et installé le driver RT61 de Rt2x00. Tous ce passe bien jusqu'à ce que j'active le resaux (avec 'service NetworkManager start' par exemple). Voici ce qui s'afiche sur la console:
Message from syslogd@localhost at Sat Feb 17 19:11:29 2007 ...
localhost kernel: ------------[ cut here ]------------
Message from syslogd@localhost at Sat Feb 17 19:11:29 2007 ...
localhost kernel: kernel BUG at mm/slab.c:594!
Message from syslogd@localhost at Sat Feb 17 19:11:29 2007 ...
localhost kernel: invalid opcode: 0000 [#1]
Message from syslogd@localhost at Sat Feb 17 19:11:29 2007 ...
localhost kernel: SMP
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: CPU: 0
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: EIP is at kfree+0x2e/0x65
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: eax: c0000020 ebx: 00001c90 ecx: f8d20000 edx: c171fb60
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: esi: 00200282 edi: f8fdb040 ebp: e63c0000 esp: e0b16e74
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: ds: 007b es: 007b ss: 0068
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: Process ip (pid: 20919, ti=e0b16000 task=f474f9b0 task.ti=e0b16000)
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: Stack: 00001c90 f8fdb040 00001c90 f8fbc562 00200246 00000000 00000000 00000000
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: fffffffe f8fdb040 c0000000 e63c0000 dffd4800 00000000 00000000 f8fa79f6
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: dffd4800 dffd4800 dffd4800 00001003 00001002 c05b9c13 dffd4800 c05b8637
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: Call Trace:
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: [<f8fbc562>] NICLoadFirmware+0x311/0x38c [rt61]
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: [<f8fa79f6>] RT61_open+0xe2/0x2e5 [rt61]
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: [<c05b9c13>] dev_open+0x2b/0x62
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: [<c05b8637>] dev_change_flags+0x47/0xe4
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: [<c05f453c>] devinet_ioctl+0x250/0x551
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: [<c05af529>] sock_ioctl+0x19b/0x1bf
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: [<c047ef37>] do_ioctl+0x1f/0x62
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: [<c047f1c4>] vfs_ioctl+0x24a/0x25c
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: [<c047f222>] sys_ioctl+0x4c/0x66
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: [<c0404013>] syscall_call+0x7/0xb
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: DWARF2 unwinder stuck at syscall_call+0x7/0xb
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: Leftover inexact backtrace:
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: =======================
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: Code: 56 89 c7 53 74 58 9c 5e fa 8d 90 00 00 00 40 c1 ea 0c c1 e2 05 03 15 90 c6 80 c0 8b 02 f6 c4 40 74 03 8b 52 0c 8b 02 84 c0 78 08 <0f> 0b 52 02 fb 90 63 c0 89 e0 8b 4a 18 25 00 f0 ff ff 8b 40 10
Message from syslogd@localhost at Sat Feb 17 19:11:30 2007 ...
localhost kernel: EIP: [<c046b149>] kfree+0x2e/0x65 SS:ESP 0068:e0b16e74
Puis plus rien ne marche et je suis obligé d'etteindre "à la bourrin".
Quelqu'un aurait il une explication ?
kwizart
Au mieux tu n'a pas installé le firmware au pire tu as un kernel i586 (et tu devras recommencer la compilation!)
Dans tout les cas, rien ne te dispense de lire la doc ni de reprendre la configuration depuis le début...
le rt2x00 n'est pas compatible avec NetworkManager ( utilisation a proscrire!)
forty
Comment faire pour savoir si j'ai un kernel i586 ?
merci de ta reponse.
liho
