Ndiswrapper error: No rule to make target `WLAN/ndiswrapper
I am trying currently to get Ndiswrapper working in order to use my wireless internet usb key. Unfortunately, I have encountered some technical difficulties when I compile it. (Also, I am new to linux)
After following the INSTALL instructions for the ndiswrapper-1.53 software, I obtain the following error:
[root@localhost ndiswrapper-1.53]# make
make -C driver
make: Entering directory `/dl/Linux WLAN/ndiswrapper-1.53/ndiswrapper-1.53/driver'
*** WARNING: This kernel uses 4K stack size option
(CONFIG_4KSTACKS); many Windows drivers will not work
with this option enabled. Disable CONFIG_4KSTACKS
in kernel's .config file, recompile and install kernel
make -C /usr/src/kernels/2.6.18-53.el5-i686 M=/dl/Linux WLAN/ndiswrapper-1.53/ndiswrapper-1.53/driver
make: Entering directory `/usr/src/kernels/2.6.18-53.el5-i686'
make: *** No rule to make target `WLAN/ndiswrapper-1.53/ndiswrapper-1.53/driver'. Stop.
make: Leaving directory `/usr/src/kernels/2.6.18-53.el5-i686'
make: *** [modules] Error 2
make: Leaving directory `/dl/Linux WLAN/ndiswrapper-1.53/ndiswrapper-1.53/driver'
make: *** [all] Error 2
I have googled this error and although I found some mention of it, I have yet to find a solution that I can apply.
Linux distro: RHEL 5.1
Wireless USB key: Dlink DWL-G122 rev A2
Any help will be appreciated
ndiswrapper error fixed. However I have now more choices than I expected
Good eye. Yes, in fact the mistake was that a folder (Linux WLAN) had a space in it causing a command to break in 2. I feel like an idiot.
I don't know if that is a command that you entered, or if it was automatically entered. A space can sometimes be entered with a backslash, to get it to work.
Edit: It looks to me that Linux WLAN is a folder in your directory. Just change the name to eliminate the space.
After the space was removed, ndiswrapper compiled like a charm.
However, once ndiswrapper installed I did not proceed with the driver installation as I first wanted to list the device ID info:
P.S I have my motorola cell phone connected to my computer (via usb) for charging purposes, that is why it is listed in the "lsusb" output.
[root@localhost ~]# lsusb
Bus 001 Device 001: ID 0000:0000
Bus 001 Device 002: ID 22b8:4810 Motorola PCS Triplet GSM Phone (storage)
Bus 002 Device 001: ID 0000:0000
Bus 002 Device 002: ID 2001:3704 D-Link Corp. [hex] DWL-G122 802.11g rev. A2
[root@localhost ~]# lsmod
Module Size Used by
radeon 103777 2
drm 65493 3 radeon
autofs4 24389 2
hidp 23105 2
rfcomm 42457 0
l2cap 29633 10 hidp,rfcomm
bluetooth 53925 5 hidp,rfcomm,l2cap
sunrpc 144253 1
ip_conntrack_netbios_ns 6977 0
ipt_REJECT 9537 1
xt_state 6209 2
ip_conntrack 53025 2 ip_conntrack_netbios_ns,xt_state
nfnetlink 10713 1 ip_conntrack
iptable_filter 7105 1
ip_tables 17028 1 iptable_filter
ip6t_REJECT 9409 1
xt_tcpudp 7105 10
ip6table_filter 6849 1
ip6_tables 18181 1 ip6table_filter
x_tables 17349 6 ipt_REJECT,xt_state,ip_tables,ip6t_REJECT,xt_tcpudp,ip6_tables
ipv6 251393 15 ip6t_REJECT
dm_multipath 21577 0
video 19269 0
sbs 18533 0
backlight 10049 0
i2c_ec 9025 1 sbs
button 10705 0
battery 13637 0
asus_acpi 19289 0
ac 9157 0
lp 15849 0
sd_mod 25025 0
sg 36061 0
floppy 57125 0
8139too 28865 0
pcspkr 7105 0
snd_cmipci 36449 0
snd_opl3_lib 14017 1 snd_cmipci
snd_mpu401_uart 12097 1 snd_cmipci
mii 9409 1 8139too
snd_emu10k1_synth 10945 0
snd_emux_synth 34625 1 snd_emu10k1_synth
snd_seq_virmidi 11073 1 snd_emux_synth
snd_seq_midi_emul 9921 1 snd_emux_synth
snd_emu10k1 121953 2 snd_emu10k1_synth
snd_rawmidi 26561 3 snd_mpu401_uart,snd_seq_virmidi,snd_emu10k1
snd_ac97_codec 93025 1 snd_emu10k1
ac97_bus 6337 1 snd_ac97_codec
snd_seq_dummy 7877 0
snd_seq_oss 32577 0
snd_seq_midi_event 11072 2 snd_seq_virmidi,snd_seq_oss
snd_seq 49713 8 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_pcm_oss 42945 0
snd_mixer_oss 19009 1 snd_pcm_oss
snd_pcm 72133 4 snd_cmipci,snd_emu10k1,snd_ac97_codec,snd_pcm_oss
snd_seq_device 11725 8 snd_opl3_lib,snd_emu10k1_synth,snd_emux_synth,snd_emu10k1,snd_rawmidi,snd_seq_dummy,snd_seq_oss,snd_seq
snd_timer 24645 4 snd_opl3_lib,snd_emu10k1,snd_seq,snd_pcm
snd_page_alloc 13641 2 snd_emu10k1,snd_pcm
snd_util_mem 8769 2 snd_emux_synth,snd_emu10k1
snd_hwdep 12869 3 snd_opl3_lib,snd_emux_synth,snd_emu10k1
snd 52421 18 snd_cmipci,snd_opl3_lib,snd_mpu401_uart,snd_emux_synth,snd_seq_virmidi,snd_emu10k1,snd_rawmidi,snd_ac97_codec,snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_device,snd_timer,snd_hwdep
soundcore 11553 1 snd
emu10k1_gp 7873 0
gameport 18633 3 snd_cmipci,emu10k1_gp
via686a 18889 0
hwmon 7365 1 via686a
i2c_isa 9153 1 via686a
i2c_viapro 12117 0
i2c_core 23745 4 i2c_ec,via686a,i2c_isa,i2c_viapro
usb_storage 76577 0
scsi_mod 133069 3 sd_mod,sg,usb_storage
parport_pc 29157 1
parport 37513 2 lp,parport_pc
ide_cd 40033 0
cdrom 36705 1 ide_cd
serio_raw 10693 0
dm_snapshot 20709 0
dm_zero 6209 0
dm_mirror 28741 0
dm_mod 58201 9 dm_multipath,dm_snapshot,dm_zero,dm_mirror
ext3 123337 2
jbd 56553 1 ext3
ehci_hcd 32973 0
ohci_hcd 23261 0
uhci_hcd 25421 0
a list should be available informing if my *.inf/*.sys driver files would function with the ndiswrapper. However the link is broken. Thus I do not know for sure if my windows driver is compatible with ndiswrapper but I am keeping my fingers crossed.
Also, like you mentioned earlier, I did find a linux driver that should work for my DWL-G122 rev A2 wireless usb key. However it is only source code, so I had opted to install ndiswrapper since it sounded easier as there was more internet feedback on this topic.
Downloads - Rt2x00Wiki
(The rt2570 (USB) version)
Also according to an unbuntu forum post, this driver should work for my device:
Prism54 softmac linux driver
And lastly, I looked on my installation cds for the compat-wireless.rpm package. I did not find it. However I did find the following package which seems to have potential:
So now, I have 3 choices:
1) Continue with the ndiswrapper approach
2) Compile the source code for the linux driver I found. (It does not seems as daunting as it originally did after spending an evening installing the missing packages needed to compile ndiswrapper)
3) Install the wireless-tools-28-2.el5.i386.rpm package and see what happens.
Any feedback would be appreciated.
Dlink DWL-G122 rev A2 driver
You are correct. The rt2570 driver should not work.
I Googled the device ID [2001:3704] and got this page.
Linux Kernel Driver Database: CONFIG_P54_USB: Prism54 USB support
So I think that the native driver is the prism one, not the rt2570. If this were a regular Linux distro, the driver p54 driver would automatically load. You would still need to install firmware before it would work. It has full support in Linux, something that using NDISwrapper may not have (and you may not need).
It seems that the Dlink DWL-G122 rev A2 usb key requires a prism driver or ndiswrapper - ralink drivers are not mentioned to function for A2. Rev B1, C1 require a ralink driver. Rev D1 requires a marvel chipset driver or ndiswrapper.
Thanks for all your help. Will probably try ndiswrapper.