Re: [SLE] new at wireless configuration
But that is exactly what you need to do, install the "windows" driver using ndiswrapper for the linksys card to work. There are no native drivers in 10.1 (nor 10.0).
As root:
ndiswrapper -i <driver>.inf (found on the CD) ndiswrapper -m modprobe ndiswrapper ndiswrapper -l (should show the installed driver)
I would also add ndiswrapper to the MODULES_LOADED_ON_BOOT="" line in /etc/sysconfig/kernel to have the driver loaded during boot.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
It worked! Thanks. As stated in a previous message, the complete -i line is ndiswrapper -i LSTINDS.INF.Once I've added ndiswrapper to MODULES_LOAD_ON_BOOT, the power led greened at boot time. Now, the iwconfig output looks like this: -- citlali:~ # iwconfig lo no wireless extensions. eth0 no wireless extensions. wlan0 IEEE 802.11g ESSID:off/any Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Bit Rate:54 Mb/s Tx-Power:10 dBm Sensitivity=0/3 RTS thr:4096 B Fragment thr:4096 B Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 sit0 no wireless extensions. citlali:~ # -- Thus I have added the network card by using YaST>Network Devices>Network Cards>Traditional Method with ifup>Add and choosing new Wireless PCMCIA card. After restarting the computer, power led is green at startup, but it seems that no wireless link is established. After adding the PCMCIA wireless card, the iwconfig output is not exactly the same: no access point is associated with wlan0, but a nichname appears -- citlali:~ # iwconfig lo no wireless extensions. eth0 no wireless extensions. wlan0 IEEE 802.11g ESSID:off/any Nickname:"citlali" Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Bit Rate=54 Mb/s Tx-Power:10 dBm Sensitivity=0/3 RTS thr=4096 B Fragment thr=4096 B Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 sit0 no wireless extensions. citlali:~ # -- Please, how could I debug/solve this issue? Once again, thanks for your help, Ricardo -- Ricardo Rodríguez XEN, Resources Management
At 01:37 AM 6/1/2006 +0200, Ricardo Rodríguez - XEN wrote:
But that is exactly what you need to do, install the "windows" driver using ndiswrapper for the linksys card to work. There are no native drivers in 10.1 (nor 10.0).
As root:
ndiswrapper -i <driver>.inf (found on the CD) ndiswrapper -m modprobe ndiswrapper ndiswrapper -l (should show the installed driver)
I would also add ndiswrapper to the MODULES_LOADED_ON_BOOT="" line in /etc/sysconfig/kernel to have the driver loaded during boot.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
It worked! Thanks. As stated in a previous message, the complete -i line
is ndiswrapper -i LSTINDS.INF.Once I've added ndiswrapper to MODULES_LOAD_ON_BOOT, the power led greened at boot time.
Now, the iwconfig output looks like this:
-- citlali:~ # iwconfig lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:off/any Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Bit Rate:54 Mb/s Tx-Power:10 dBm Sensitivity=0/3 RTS thr:4096 B Fragment thr:4096 B Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
sit0 no wireless extensions.
citlali:~ # --
Thus I have added the network card by using YaST>Network Devices>Network
Cards>Traditional Method with ifup>Add and choosing new Wireless PCMCIA card. After restarting the computer, power led is green at startup, but it seems that no wireless link is established.
After adding the PCMCIA wireless card, the iwconfig output is not exactly
the same: no access point is associated with wlan0, but a nichname appears
-- citlali:~ # iwconfig lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:off/any Nickname:"citlali" Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Bit Rate=54 Mb/s Tx-Power:10 dBm Sensitivity=0/3 RTS thr=4096 B Fragment thr=4096 B Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
sit0 no wireless extensions.
citlali:~ # --
Please, how could I debug/solve this issue?
Once again, thanks for your help,
Ricardo
-- Ricardo Rodríguez XEN, Resources Management
You say "it worked", but then you say it doesn't work. I have broadcom ethernet on the mobo, and email doesn't work from Linux 10.0, but I went to the ndiswrapper site from Google, and I don't understand a damn thing there, so you probably have the same problem. You have to recompile the kernel--a real show-stopper there, I think--and find a windows driver (good luck) and all kinds of other esoteric things. I'm not an IT person, I'm a retired RF engineer, and I can't deal with this stuff, and now I see that Novel is taking even the existing drivers out of Linux, so you'll have nothing. I'm totally disgusted! --dm -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.1.394 / Virus Database: 268.8.0/353 - Release Date: 5/31/2006 -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Wed, 2006-05-31 at 20:04 -0400, Doug McGarrett wrote:
You say "it worked", but then you say it doesn't work. I have broadcom ethernet on the mobo, and email doesn't work from Linux 10.0, but I went to the ndiswrapper site from Google, and I don't understand a damn thing there, so you probably have the same problem. You have to recompile the kernel--a real show-stopper there, I think--and find a windows driver (good luck) and all kinds of other esoteric things. I'm not an IT person, I'm a retired RF engineer, and I can't deal with this stuff, and now I see that Novel is taking even the existing drivers out of Linux, so you'll have nothing. I'm totally disgusted!
Why did you feel compelled to go to the ndiswrapper site for info? There is an info file at /usr/share/doc/packages/ndiswrapper that has all the info needed to use ndiswrapper. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
** Reply to message from Ricardo Rodríguez - XEN <rrodriguez@xen.net> on Thu, 01 Jun 2006 01:37:23 +0200
Please, how could I debug/solve this issue?
Once again, thanks for your help,
Ricardo
This is from an earlier post about ndiswrapper: It worked. Man ifup-dhcp does nothing. I have no idea what it is, but all I know is that when I did a ifup-dhcp wlan0 -o debug,auto, dhcp assigned an address to wlan0 . Go figure, thanks everyone Jim. I have also had success using ifup-dhcp wlan0, only. I did not have to add the -o debug,auto to get my to get an address.If wlan0 should happen to be unavailable, try ifup-dhcp wlan1. One of them should be there. By the way, in YaST did you configure your card with module "ndiswrapper"? ndiswrapper -m sets up the modprobe.conf file, and this entry for the card module in YaST should load it at startup. Ed Harrison, Linux User # 199533 SuSE10.0, Kernel 2.6.15 PolarBar Mailer 1.26 -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (4)
-
Doug McGarrett -
Ed Harrison -
Ken Schneider -
Ricardo Rodríguez - XEN