Re: [opensuse] Wireless Woes
try manual
load module:
modprobe you_module
check if is ok
dmesg
and check interface
iwconfig
Dnia 4 października 2007 14:56 Jeremy Figgins
I've tried that, but it doesn't seem to work (in either 10.1 or 10.2). After I enter the module name and the configuration, iwconfig doesn't show the interface and trying the ifup on the interface name that SuSE assigns the card gives:
Interface wlan0 is not available wlan0: unknown interface: No such device
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I checked /var/log/messages with the prism2 card and all of it seemed normal until: ifup: wlan0 ifup-dhcp: Starting DHCP Client Daemon on wlan0... ifup-dhcp: . kernel: NET: Registered protocol family 17 dhcpcd[3854]: dhcpStart: ioctl SIOCSIFFLAGS: No such device ifup-dhcp: . ifup-dhcp: . syslog-ng[2184]: last message repeated 2 times ifup-dhcp: no IP address yet... backgrounding. ifup: Cannot enable interface wlan0. ifup-route: interface wlan0 is not up -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
The version of the linux-wlan-ng drivers that are included with SuSE are 0.2.7. I just tried the newest (0.2.8) and it didn't help. The problem seems to be related to SIOCSIFFLAGS message, which I read somewhere else is related to the interrupts. I did a cat /proc/interrupts, but my wireless card was not listed there (and I don't even know if it should be). What might I try next? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jeremy Figgins wrote:
The version of the linux-wlan-ng drivers that are included with SuSE are 0.2.7. I just tried the newest (0.2.8) and it didn't help. The problem seems to be related to SIOCSIFFLAGS message, which I read somewhere else is related to the interrupts. I did a cat /proc/interrupts, but my wireless card was not listed there (and I don't even know if it should be).
What might I try next?
Try adding the boot parameter 'noapic' and/or 'nolapic'. This will eliminate the irq sharing/balancing that can cause problems. I have seen systems where apic works just fine. I have see others (2 in my home right now) where apic renders certain cards inoperable and causes hard lockups on occasion. Certainly would be my next try. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
David C. Rankin
-
fazer
-
Jeremy Figgins