Matt Posted April 12, 2008 Report Share Posted April 12, 2008 I am trying to get my fresh debian install to work with my wireless connection. Here's my info:debian:/home/matt# lspci00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O Controller (rev 03)00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP Controller (rev 03)00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81)00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 01)00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 01)00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01)01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 [Mobility FireGL 9000] (rev 01)02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5702X Gigabit Ethernet (rev 02)02:01.0 CardBus bridge: O2 Micro, Inc. OZ711EC1 SmartCardBus Controller (rev 20)02:01.1 CardBus bridge: O2 Micro, Inc. OZ711EC1 SmartCardBus Controller (rev 20)02:03.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)debian:/home/matt# lspci | grep Ethernet02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5702X Gigabit Ethernet (rev 02)debian:/home/matt# cat /etc/issueDebian GNU/Linux 4.0 \n \lI'm not sure how ti get and install the correct drivers. Quote Link to post Share on other sites
Matt Posted April 13, 2008 Author Report Share Posted April 13, 2008 I've attempted to follow this as a guide:http://www.debian-administration.org/articles/401But have had no luck. Maybe I installed the wrong driver? (Dell Wireless 1450)Edit:Ok, I think I had the wrong driver. Here's what I've got now:debian:/home/matt# ndiswrapper -linstalled drivers:w70n501 driver installed, hardware (8086:1043) present (alternate driver: ipw2100)ndiswrapper's site says:f you get “alternate driver†information, such as, bcmwl5 : driver installed device (14E4:4320) present (alternate driver: bcm43xx)then the kernel may load bcm43xx instead of ndiswrapper to initialize the device. If you want to use ndiswrapper, you must unload the alternate driver Quote Link to post Share on other sites
Matt Posted April 13, 2008 Author Report Share Posted April 13, 2008 Ok, one more piece that might help anyone:debian:/proc# ndiswrapperinstall/manage Windows drivers for ndiswrapperusage: ndiswrapper OPTION-i inffile install driver described by 'inffile'-a devid driver use installed 'driver' for 'devid'-r driver remove 'driver'-l list installed drivers-m write configuration for modprobe-ma write module alias configuration for all devices-mi write module install configuration for all devices-v report version informationwhere 'devid' is either PCIID or USBID of the form XXXX:XXXX,as reported by 'lspci -n' or 'lsusb' for the carddebian:/proc# ndiswrapper -a 8086:1043 w70n501couldn't create symlink for "8086:1043:2522:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:2523:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:2527:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:2528:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:2529:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:252B:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:252C:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:252D:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:2551:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:2553:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:2554:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:2555:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:2561:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:2565:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:2566:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:2567:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:2570:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:2581:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:2585:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:2586:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:2587:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:2591:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:2593:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:2596:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:2598:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043:25A0:8086.5.conf" -installation may be incompletecouldn't create symlink for "8086:1043.5.conf" -installation may be incompletedriver 'w70n501' is not installed (properly)! Quote Link to post Share on other sites
naraku9333 Posted April 13, 2008 Report Share Posted April 13, 2008 (edited) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5702X Gigabit Ethernet (rev 02)You have an intel card, try the ipw2100 package.instructions Edited April 13, 2008 by naraku9333 Quote Link to post Share on other sites
shanenin Posted April 13, 2008 Report Share Posted April 13, 2008 good catch, I did not even notice that was referring to the wired ethernet chipsethere is your wireless chipset20)02:03.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04) Quote Link to post Share on other sites
Matt Posted April 14, 2008 Author Report Share Posted April 14, 2008 Awesome naraku! I've now got the wireless options in the upper right corner. It can see my home network. Now, I'm having issues logging in. I've got WEP set up, and I enter the key (I've verified the key many times) yet it can't connect. Do I need to do anything else to enable WEP connectivity? Quote Link to post Share on other sites
Sir_Siddy Posted April 14, 2008 Report Share Posted April 14, 2008 Make sure you arnt typing in the wep passphrase and have selected the wep hex key. It took me a while when I first installed it to realize that. Quote Link to post Share on other sites
Matt Posted April 14, 2008 Author Report Share Posted April 14, 2008 Make sure you arnt typing in the wep passphrase and have selected the wep hex key. It took me a while when I first installed it to realize that.Lol, yes I'm doing that correctly.I have also confirmed that this is a WEP issue, as I can connect to open networks. When I send the WEP key, it attempts to join, staying at "waiting for key" and it fails, then asks for the key again. Quote Link to post Share on other sites
Matt Posted April 14, 2008 Author Report Share Posted April 14, 2008 FIXED!! Here's what I did:iwconfig eth1 mode managediwconfig eth1 essid onDetected the network immediately. Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.