On Sat, 2005-08-13 at 16:18 +0200, Johan Lozano wrote: > On Wed, 2005-08-10 at 17:26 +0800, Edward Dekkers wrote: > > Johan Lozano wrote: > > > On Mon, 2005-08-08 at 16:42 -0400, Reuben D. Budiardja wrote: > > > > > >>On Sunday 07 August 2005 04:00, Johan Lozano wrote: > > >> > > >>>hi list, > > >>> > > >>>i am trying to install a wireless network on a acer aspire 5020 with a > > >>>broadcom 4318 nic without any success. > > >>> > > >>>ndiswrapper is installed > > >>>ndiswrapper -l reports: > > >>>installed ndis drivers: > > >>>bcmwl5 driver present, hardware present > > >>> > > >>>but in the network configuration keep having this message on activating > > >>>wlan0: > > >>>ndiswrapper device wlan0 does not seem to be present, delaying > > >>>initialisation. > > >> > > >>Did you follow the instruction here: > > >>http://ndiswrapper.sourceforge.net/mediawiki/index.php/Installation > > >>? > > >> > > >>What's the output of 'iwconfig' ? > > >> > > >>RDB > > >> > > >> > > > > > > with the driver in time of posting this, the output of iwconfig was: > > > > > > [root@mbarwen ~]$ iwconfig > > > > > > lo no wireless extensions. > > > > > > eth0 no wireless extensions. > > > > > > sit0 no wireless extensions. > > > > > > i suppose it was because the driver is a win32 driver. > > > in the meantime i found an other driver, one for the x86_64 > > > architecture. wlan0 is now detected but now he complains about the fact > > > it is compiled for revision 17 and the card is one of revision 18 and > > > that some options will not work properly. > > > and really, it does not work at all. > > > > > > so i sent a mail to acer for help, got a ticket number but still no > > > answer. > > > > > > thanks anyway > > > > > > > > > Johan Lozano > > > MicroBit, Duffel > > > E-mail : johan.lozano@xxxxxxxxxx > > > > > > GPG key : 9A9FBFE1 > > > > > > > > > > > > > Stupid question, but is the driver even loading? > > > > insmod ndiswrapper > > lsmod | grep ndiswrapper > > > > [root@mbarwen ~]# insmod ndiswrapper > insmod: can't read 'ndiswrapper': No such file or directory > > [root@mbarwen ~]# lsmod | grep ndiswrapper > ndiswrapper 216464 0 > > > Check logs if not and see why not. > > > [root@mbarwen ~]# dmesg | grep ndis > ndiswrapper: Unknown parameter `' > ndiswrapper version 1.2 loaded (preempt=no,smp=no) > ndiswrapper: driver bcmwl5 (Broadcom,02/11/2005, 3.100.64.0) loaded > ndiswrapper: using irq 169 > wlan0: ndiswrapper ethernet device 00:0e:9b:c4:a1:16 using driver > bcmwl5, configuration file 14E4:4318.5.conf > > > Regards, > > Ed. > > > > P.S. the revision 17/18 thing I get as well but it still works just fine. > > > > > > > root@mbarwen ~]# iwconfig > lo no wireless extensions. > > eth0 no wireless extensions. > > Warning: Driver for device wlan0 recommend version 18 of Wireless > Extension, > but has been compiled with version 17, therefore some driver features > may not be available... > > wlan0 IEEE 802.11g ESSID:off/any Nickname:"mbarwen.mbd.com" > Mode:Auto Frequency:2.437 GHz Access Point: > 00:00:00:00:00:00 > Bit Rate=54 Mb/s Tx-Power:25 dBm > RTS thr:off Fragment thr:off > Encryption key:off > Power Management:off > Link Quality:100/100 Signal level:-10 dBm Noise level:-256 > dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > you should assign this interface an essid to match the AP. If the AP requires a key you will also need to assign the key for wlan0. > sit0 no wireless extensions. > > [root@mbarwen ~]# ifconfig -a > eth0 Link encap:Ethernet HWaddr 00:0A:E4:E1:36:D7 > inet addr:192.168.1.33 Bcast:192.168.1.255 > Mask:255.255.255.0 > inet6 addr: fe80::20a:e4ff:fee1:36d7/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1634 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1800 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:542940 (530.2 KiB) TX bytes:299621 (292.5 KiB) > > > Interrupt:225 Base address:0xc400 > > 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:2547 errors:0 dropped:0 overruns:0 frame:0 > TX packets:2547 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:2971196 (2.8 MiB) TX bytes:2971196 (2.8 MiB) > > 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) > > wlan0 Link encap:Ethernet HWaddr 00:0E:9B:C4:A1:16 > inet addr:192.168.1.33 Bcast:192.168.1.255 ^^^^^^^^^^^^^^^^^^^^^^^^ This is the exact same inet addr as eth0 above. You *must* use different addresses, and they should also be on different subnets. You do not say whether these addresses are assigned by dhcp or static, but regardless of how they are assigned they must not be the same. > Mask:255.255.255.0 > inet6 addr: fe80::20e:9bff:fec4:a116/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 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:1000 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > Memory:c0204000-c0205fff > > can you figure out what is wrong with this? > thanks > > > Johan Lozano > MicroBit, Duffel > E-mail : johan.lozano@xxxxxxxxxx > > GPG key : 9A9FBFE1 > > >
