2009/1/20 Micha Feigin <mi...@post.tau.ac.il> > On Tue, 20 Jan 2009 09:11:56 +0800 > "Umarzuki Mochlis" <umarz...@gmail.com> wrote: > > > 2009/1/20 Micha Feigin <mi...@post.tau.ac.il> > > > > > On Mon, 19 Jan 2009 22:15:55 +0800 > > > "Umarzuki Mochlis" <umarz...@gmail.com> wrote: > > > > > > [...] > > > > > > > > Looks like it's pointing in the right direction. Does it see you > > > wireless > > > > > when > > > > > you open the window (under available wireless connections) > > > > > > > > > > If so, you need to choose your ap click that little triangle by the > > > name, > > > > > check > > > > > automatically connect to this network if you wish and click > advanced > > > > > settings > > > > > to setup things like wep password and such. > > > > > > > > > > > > > Unfortunately nothing appears when I did that which leads me to make > this > > > > post in the first place. > > > > > > > > > > what does iwlist eth1 scan show? (that is what wicd is supposed to use > > > behind > > > the scenes) > > > > > > > eden:~# iwlist eth1 scan > > eth1 Failed to read scan data : Invalid argument > > > > That is why wicd doesn't find any wireless networks, if iwlist doesn't work > manually it won't work for wicd, so your problem (apart for what's > mentioned > bellow) is enabling scanning on the wireless interface. > > Looks from this thread > http://ubuntuforums.org/showthread.php?t=790778 > that the driver may be problematic, he recommends using ndiswrapper. see if > that makes iwlist work for you >
when i got to the last step to load the .inf file, it says i didn't install the module. > > > > > > > > > did you check that /etc/network/interfaces doesn't mention the wireless > > > interface? > > > > > > > When using wicd and network manager your /etc/network/interfaces should > contain > only the loopback device > > > # The loopback network interface > > auto lo > > iface lo inet loopback > > > > You should comment out everything below this for wicd and network manager > ... > > > #iface eth0 inet dhcp > > > > allow-hotplug eth1 > > iface eth1 inet dhcp > > wireless-essid my-office > > > > > > > > iface eth0 inet dhcp > > > > > > > > > > > > > > > > > > > Some public access points also have a transparent proxy that > requires > > > you > > > > > to > > > > > authenticate when you start browsing (my uni is that way, you need > to > > > enter > > > > > a > > > > > wpa key and then enter your username/password in the browser before > you > > > can > > > > > access outside connections). > > > > > > > > > > > > > Same situation in my office but the network cannot be detected which > > > leads > > > > me to think there must but something amiss. > > > > > > > [... snip ...] > > > > > > > > > -- > > > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > > > with a subject of "unsubscribe". Trouble? Contact > > > listmas...@lists.debian.org > > > > > > > > > > > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > > -- Regards, Umarzuki Mochlis http://gameornot.net
