On Mon, May 25, 2009 at 9:34 PM, Barkle <barkle@xxxxxxx> wrote: > Have a look in the appended file "dmesg_2009-05-25.txt" and it's not wlan0, > it's phy0. > I hope, I haven't cut off too much . You have removed almost everything that might be useful... e.g. it is not possible to tell even if you have a 32-bit CPU or a 64-bit CPU for sure (although it *looks* like a 64-bit system), dual core/SMP or single CPU, and what else is on your PCI bus. Is that really necessary??? Very few people are telepathic, you know... at least I don't know of any. > There is no more reaktion, no change by pressing num-lock, caps-lock or > scroll-lock. No answer on a ping. What I didn't tested is the "magic SysRq". And any last minute syslog, etc in your log files after you power-cycle? > wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf -W > -dd If you are not using any encryption (WEP/WPA, etc), there is no need to run wpa_supplicant. Also, what's in /var/log/wpa_supplicant.log ? In fact you should shutdown network manager and wpa_suplicant and probably dbus as well. > No entry in the syslog Again you have edited away your CPU type, and, since you are trying to see what's wrong with your wireless device, you really should disable dhcp against your wired networking interface. > OK, no I didn't tried the compat-wireless so far.. > It will take a while, when I got an result of the change. Please gIve compat-wireless a go. You have edited away any useful info in your dmesg and syslog, so there is nothing to tell. Why did you do that? -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
