I am running SuSE 10.1/KDE 3.5.4 on my laptop with a new wireless router for my LAN. Unfortunately, the KWiFiManager tells me that the wireless card is disabled. Scanning for networks results in the message that 'The scan is complete but no networks were found., Hardware information, via yast2, tells me that ACX 111 54Mbps Wireless Interface is present. ifconfig gives me: eth0 Link encap:Ethernet HWaddr 00:10:A4:92:F4:EA inet addr:192.168.2.14 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::210:a4ff:fe92:f4ea/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:53191 errors:0 dropped:0 overruns:0 frame:0 TX packets:29721 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:69005296 (65.8 Mb) TX bytes:2651892 (2.5 Mb) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:2452 errors:0 dropped:0 overruns:0 frame:0 TX packets:2452 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:632052 (617.2 Kb) TX bytes:632052 (617.2 Kb) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) So, it would seem obvious, at least to my limited knowledge that OS isn't finding the wireless card. What do I need to do? I'm sending this from my laptop, but over my wired LAN Thanks in advance.
On Sunday 20 August 2006 12:36, Stephen P. Molnar wrote:
I am running SuSE 10.1/KDE 3.5.4 on my laptop with a new wireless router for my LAN.
Unfortunately, the KWiFiManager tells me that the wireless card is disabled. Scanning for networks results in the message that 'The scan is complete but no networks were found.,
Hardware information, via yast2, tells me that ACX 111 54Mbps Wireless Interface is present.
ifconfig gives me:
eth0 Link encap:Ethernet HWaddr 00:10:A4:92:F4:EA inet addr:192.168.2.14 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::210:a4ff:fe92:f4ea/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:53191 errors:0 dropped:0 overruns:0 frame:0 TX packets:29721 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:69005296 (65.8 Mb) TX bytes:2651892 (2.5 Mb)
Its not clear to me that this is your wireless interface. Looks like a Xircom nic of some sort. I think you want to investigate Ndiswrapper package because your card seems to have a Texas Instruments chipset which may require it. -- _____________________________________ John Andersen
try iwconfig and see what it says Stephen P. Molnar wrote:
I am running SuSE 10.1/KDE 3.5.4 on my laptop with a new wireless router for my LAN.
Unfortunately, the KWiFiManager tells me that the wireless card is disabled. Scanning for networks results in the message that 'The scan is complete but no networks were found.,
Hardware information, via yast2, tells me that ACX 111 54Mbps Wireless Interface is present.
ifconfig gives me:
eth0 Link encap:Ethernet HWaddr 00:10:A4:92:F4:EA inet addr:192.168.2.14 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::210:a4ff:fe92:f4ea/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:53191 errors:0 dropped:0 overruns:0 frame:0 TX packets:29721 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:69005296 (65.8 Mb) TX bytes:2651892 (2.5 Mb)
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:2452 errors:0 dropped:0 overruns:0 frame:0 TX packets:2452 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:632052 (617.2 Kb) TX bytes:632052 (617.2 Kb)
sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
So, it would seem obvious, at least to my limited knowledge that OS isn't finding the wireless card.
What do I need to do?
I'm sending this from my laptop, but over my wired LAN
Thanks in advance.
-- One day at a time, one second if that's what it takes
Thanks for the reply. inga:/home/computation # iwconfig lo no wireless extensions. eth0 no wireless extensions. sit0 no wireless extensions. inga:/home/computation # On Sunday 20 August 2006 16:49, Bruce Ferrell wrote:
try iwconfig and see what it says
Stephen P. Molnar wrote:
I am running SuSE 10.1/KDE 3.5.4 on my laptop with a new wireless router for my LAN.
Unfortunately, the KWiFiManager tells me that the wireless card is disabled. Scanning for networks results in the message that 'The scan is complete but no networks were found.,
Hardware information, via yast2, tells me that ACX 111 54Mbps Wireless Interface is present.
ifconfig gives me:
eth0 Link encap:Ethernet HWaddr 00:10:A4:92:F4:EA inet addr:192.168.2.14 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::210:a4ff:fe92:f4ea/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:53191 errors:0 dropped:0 overruns:0 frame:0 TX packets:29721 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:69005296 (65.8 Mb) TX bytes:2651892 (2.5 Mb)
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:2452 errors:0 dropped:0 overruns:0 frame:0 TX packets:2452 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:632052 (617.2 Kb) TX bytes:632052 (617.2 Kb)
sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
So, it would seem obvious, at least to my limited knowledge that OS isn't finding the wireless card.
What do I need to do?
I'm sending this from my laptop, but over my wired LAN
Thanks in advance.
-- One day at a time, one second if that's what it takes
Stephen P. Molnar wrote:
Thanks for the reply.
inga:/home/computation # iwconfig lo no wireless extensions.
eth0 no wireless extensions.
sit0 no wireless extensions.
inga:/home/computation #
On Sunday 20 August 2006 16:49, Bruce Ferrell wrote:
try iwconfig and see what it says
I also have the same problem, but iwconfig shows lo no wireless extensions. wlan0 IEEE 802.11-b ESSID:"HOME_WLAN" Nickname:"HOME_WLAN" Mode:Managed Frequency:2.412 GHz Access Point: 00:04:E2:8C:D6:A2 Bit Rate:11 Mb/s Tx-Power:2346 dBm Retry min limit:8 RTS thr:off Fragment thr:off Encryption key:18B3-60A5-2C72-A18F-C597-FB4B-46 Security mode:restricted Link Quality=10/92 Signal level=-77 dBm Noise level=-87 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 eth0 no wireless extensions. sit0 no wireless extensions.
James Knott wrote:
Stephen P. Molnar wrote:
Thanks for the reply.
inga:/home/computation # iwconfig lo no wireless extensions.
eth0 no wireless extensions.
sit0 no wireless extensions.
inga:/home/computation #
On Sunday 20 August 2006 16:49, Bruce Ferrell wrote:
try iwconfig and see what it says
I also have the same problem, but iwconfig shows
I just discovered you have to start Kwifimanager as root, for that to work.
On Sun, 2006-08-20 at 16:36 -0400, Stephen P. Molnar wrote:
Hardware information, via yast2, tells me that ACX 111 54Mbps Wireless Interface is present.
It is present but is the driver loaded?
So, it would seem obvious, at least to my limited knowledge that OS isn't finding the wireless card.
It could possibly be that the driver is loaded, but you don't have the firmware for the card. I am not familiar with the acx.... cards, but at least for the prism54 cards, you need the firmware in /usr/lib/firmware or some such place. First find out what driver the card use. rmmod it. Tail -f your /var/log/messages, modprobe the driver, and try to bring the interface up (ifconfig eth1 up) (could be wlan0 or something else too). That should give you an indication of what is wrong/missing. If the native drivers fail, you could always try ndiswrapper - it's well documented on this list. Hans
On Sun, 2006-08-20 at 22:50 +0200, Hans du Plooy wrote:
On Sun, 2006-08-20 at 16:36 -0400, Stephen P. Molnar wrote:
Hardware information, via yast2, tells me that ACX 111 54Mbps Wireless Interface is present.
It is present but is the driver loaded?
So, it would seem obvious, at least to my limited knowledge that OS isn't finding the wireless card.
It could possibly be that the driver is loaded, but you don't have the firmware for the card. I am not familiar with the acx.... cards, but at least for the prism54 cards, you need the firmware in /usr/lib/firmware or some such place.
First find out what driver the card use. rmmod it. Tail -f your /var/log/messages, modprobe the driver, and try to bring the interface up (ifconfig eth1 up) (could be wlan0 or something else too).
That should give you an indication of what is wrong/missing.
If the native drivers fail, you could always try ndiswrapper - it's well documented on this list.
I think acx cards are broken in 10.1. I had no trouble with 10.0, but the kernel driver present in 10.0 seems to have been removed in 10.1. Odd in that it worked fine for me. I then tried ndiswrapper, as suggested on this list. With firmware (both that which came with the card and other versions suggested on the ndiswrapper site). But the card refuses to connect. It is found. The driver and firmware is loaded. But after that all fails. So, I am running 10.0 on the machine in question. If anyone has solved this, I would be happy. The SUSE hardware info implies this chipset works. I bet it is old info from 10.0 -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23
On Sunday 20 August 2006 23:06, Roger Oberholtzer wrote:
But the card refuses to connect. It is found. The driver and firmware is loaded. But after that all fails. So, I am running 10.0 on the machine in question. If anyone has solved this, I would be happy. The SUSE hardware info implies this chipset works. I bet it is old info from 10.0
10.0 and 10.1 are not THAT much different, you could probably move the modules (or the RPMs they came in) from 10 to 10.1 If the firmware loads and the card is found, what other tests were done? I can imagine switching back and forth from 10 to 10.1 does not make testing very easy. -- _____________________________________ John Andersen
On Sun, 2006-08-20 at 23:13 -0800, John Andersen wrote:
On Sunday 20 August 2006 23:06, Roger Oberholtzer wrote:
But the card refuses to connect. It is found. The driver and firmware is loaded. But after that all fails. So, I am running 10.0 on the machine in question. If anyone has solved this, I would be happy. The SUSE hardware info implies this chipset works. I bet it is old info from 10.0
10.0 and 10.1 are not THAT much different, you could probably move the modules (or the RPMs they came in) from 10 to 10.1
It is a kernel module. IIRC, it was called acx_pci. It no longer exists. Or is doing a good job of hiding, I think I read that a new driver is in the works, but not ready. So, of course the working (for me) driver was removed before the replacement is ready. I think the wireless driver layout is significantly different so that I would need to do more than compile the old acx_pci driver. I admit I did not try. Instead I thought I would try ndiswrapper, as others suggested.
If the firmware loads and the card is found, what other tests were done? I can imagine switching back and forth from 10 to 10.1 does not make testing very easy.
After the firmware is loaded, the card tries to contact an access point. I could see that it found one, but nothing happened after that. I control the access point and know that it allows this hardware to access it. I turned off all encryption to eliminate that. Just a 'simple' connection, as done on 10.0. What would a good test be to see what the problem is? /var/log/messages did not say anything. The ndiswrapper driver just went quiet. -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23
On Sunday 20 August 2006 23:53, Roger Oberholtzer wrote:
What would a good test be to see what the problem is? /var/log/messages did not say anything. The ndiswrapper driver just went quiet.
I don't know, as I have only had to use ndiswrapper one time. Does iwconfig still work in conjunction with ndiswrapper? -- _____________________________________ John Andersen
On Mon, 2006-08-21 at 00:01 -0800, John Andersen wrote:
On Sunday 20 August 2006 23:53, Roger Oberholtzer wrote:
What would a good test be to see what the problem is? /var/log/messages did not say anything. The ndiswrapper driver just went quiet.
I don't know, as I have only had to use ndiswrapper one time. Does iwconfig still work in conjunction with ndiswrapper?
I have now sorted the problem. ndiswrapper does not work with knetworkmanager. When configuring the card in yast, choose the traditional ifup method. Then it works. I see that knetworkmanager gets 28% of the way done. It has found the access point (I see this in iwconfig), and then stops. The down side here is that users cannot sort out wireless access points easily. Oh well... -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23
On Mon, 2006-08-21 at 09:53 +0200, Roger Oberholtzer wrote:
It is a kernel module. IIRC, it was called acx_pci. It no longer exists. Or is doing a good job of hiding, I think I read that a new driver is in the works, but not ready. So, of course the working (for me) driver was removed before the replacement is ready. I think the wireless driver layout is significantly different so that I would need to do more than compile the old acx_pci driver. I admit I did not try. Instead I thought I would try ndiswrapper, as others suggested.
Correction: Although the acx_pci driver is indeed gone, it was the driver for the LinkSys WUSB54G that was expecting a replacement driver some time in the future. Until that time this device will not work with SUSE Linux, and presumably others as well. -- Roger Oberholtzer OPQ Systems AB Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23
participants (6)
-
Bruce Ferrell -
Hans du Plooy -
James Knott -
John Andersen -
Roger Oberholtzer -
Stephen P. Molnar