A Linux-Microsoft wireless 'dictionary', please!
Posts: 2
I presently have a successful XP wireless connection from my Laptop HP dv5094EA to a 'central' PC (XP) with a Belkin Wireless G Router.
I have so far failed to make a wireless laptop Internet connection using Simply Mepis 6.0 live DVD (from Linux User & Developer, issue 66), after successful Mepis installation. I have tried several forum suggestions under networking and laptops, without success.
At the Microsoft Windows XP command line, “ipconfig /all” gives:
“Windows IP Configuration
Host Name . . . . . . . . . . . . : maloac
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Belkin
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-0F-B0-C7-26-A2
Ethernet adapter Wireless Network Connection 2:
M1 Connection-specific DNS Suffix . : Belkin
M2 Description . . . . . . . . . . . : Broadcom 802.11b/g WLAN
M3 Physical Address. . . . . . . . . : 00-14-A5-73-53-E6
M4 Dhcp Enabled. . . . . . . . . . . : Yes
M5 Autoconfiguration Enabled . . . . : Yes
M6 IP Address. . . . . . . . . . . . : 192.168.2.3
M7 Subnet Mask . . . . . . . . . . . : 255.255.255.0
M8 Default Gateway . . . . . . . . . : 192.168.2.1
M9 DHCP Server . . . . . . . . . . . : 192.168.2.1
M10 DNS Servers . . . . . . . . . . . : 192.168.2.1
M11 Lease Obtained. . . . . . . . . . : 22 October 2006 11:40:29
M12 Lease Expires . . . . . . . . . . : 19 January 2038 04:14:07 ”
For Linux wireless using ndiswrapper and netcardconfig I am asked for, inter alia:
“L0 DHCP ( .. no)
L1 IP address for eth0
L2 Network mask for eth0
L3 Broadcast address for eth0
L4 Default gateway
L5 Nameserver
L6 Essid for eth0
L7 NWID (cell id), if needed
L8 Mode ( .. managed)
L9 Channel number ( .. 11)
L10 Frequency of eth0
L11 Encryption key (? Wep –sp)
L12 Additional info., sens-80, rts 512,freq 512,rate 5.5M
L13 Additional info., for ‘iwspy eth0’, if needed
L14 Additional info., for ‘iwpriv eth0’, if needed”
The labels M1-12 and L1-14 are mine, and I need to know which (if any) of the Microsoft M1-12 are to be used in the Linux L1-14? , hence a Linux-Microsoft wireless ‘dictionary’.
Finally, in running ndsiwrapper I use file bcmwl5.inf, which exists (search) in XP folders/directories:
C:\swsetup\sp33008a
C:\swsetup\sp31463a
C:\swsetup\wilan
C:\programfiles\broadcom\broadcom 802.11\driver
C:\windows\system32\reinstallbackups\0005\driver files
Which of the five should I use?
Any specific help on the above would be greatly appreciated: I am reasonably PC literate, but my Linux knowledge and skills are very small.
As root, do lspci -v
Posts: 1634
As root, do
lspci -v
Armed with the wireless information that this will yield, visit: http://ndiswrapper.sourceforge.net/mediawiki/index.php/List and correlate the information there, with the lspci info.
Keep in mind that the supplied windoze driver may not work correctly with ndiswrapper. You may have to download a chipset driver from the mfr website, and you may need to blacklist a driver, to keep it from loading automatically.
"You have two labs?"
"Each has its place. At the university, I try to please the Federal Government. Here, I negotiate with God."
first answer was wrong -- sorry
Posts: 1027
first answer was wrong -- sorry
I thought it was your wired network card that was not working.
To get Broadcom working with ndiswrapper, be sure that bcm43xx is blacklisted
(add
blacklist bcm43xx
to /etc/modprobe.d/blacklist as root)
Also, you need both the .inf and .sys files from Windows -- may also need .cat, but I don't think so.
Chances are most of the files are identical -- the only one to watch out for would be 64-bit, and then .sys will probably be called BCMWL564.sys -- that one will be no good for your 32-bit install.
I would first try the files from C:\program_files\broadcom\broadcom 802.11\driver and copy all the files to a directory in linux.
If that auto setup you showed doesn't get it going
type
ndiswrapper - i bcmwl5.inf
as root, in the directory you moved the files to
then
ndiswrapper -l
(good response is driver installed, hardware present)
then
ndiswrapper -m
and reboot
get the connection working with mutilities in Mepis 6, Mepis system center in earlier versions
Set up first without encryption, add encryption later
If it still doesn't work, remove all the drivers with
ndiswrapper -e airplus
ndiswrapper -e bcmwl5
...
and then install the bcmwl5 driver again
Mepis usually comes with a Broadcom driver -- you could check on the blacklist and try to set up that one first, but it may not work -- your Windows drivers are a better chance.
Mike
All I was seeing was the
Posts: 1634
All I was seeing was the RealTek listing, too.
(Time for new glasses)
"You have two labs?"
"Each has its place. At the university, I try to please the Federal Government. Here, I negotiate with God."
not sure
Posts: 1027
not sure of solution, a possibility is that both 8139cp and 8139too kernel modules are loading, they interfere with each other, and you need the 8139too
First try (as root)
rmmod 8139cp
rmmod 8139too
modprobe 8139too
(then set up with mutilities or iwconfig)
if that doesn't work, remove the 8139cp kernel module permanently:
rm /lib/modules/`uname -r`/kernel/drivers/net/8139cp.ko
Mike