Again I cant access drop box from work, but you could check the instructions for the list of drivers, they may have updated links @MrEngman wrote:
I've just updated the driver to handle the latest rpi-update. Download the new driver using the link on the wiki page in the Micronet SP907NS description.
I've also added a list of driver versions and compatible Linux versions in the instructions. Link also on the wiki page.
Use this one instead. http://dl.dropbox.com/u/80256631/8192cu-20120629.tar.gzDarqueSandu wrote:Thanx for reacting so quickly! I think I already found this link somewhere in this thread, and this is giving me the finger (in the form of a nice 404), so I was hoping somebody had this downloaded file still on disk somewhere, ready to re-share it...!
Code: Select all
eth0 Link encap:Ethernet Hardware Adresse b8:27:eb:... inet Adresse:192.168.1.14 Bcast:192.168.1.255 Maske:255.255.255.0 inet6-Adresse: fe80::ba27:ebff:fe3f:4f83/64 Gültigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1 RX packets:408 errors:0 dropped:1 overruns:0 frame:0 TX packets:344 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:1000 RX bytes:35439 (34.6 KiB) TX bytes:46789 (45.6 KiB) lo Link encap:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine UP LOOPBACK RUNNING MTU:16436 Metrik:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan0 Link encap:Ethernet Hardware Adresse 4c:60:de:5c:... inet Adresse:192.168.1.21 Bcast:192.168.1.255 Maske:255.255.255.0 inet6-Adresse: fe80::4e60:deff:fe5c:31e5/64 Gültigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1 RX packets:39 errors:0 dropped:50 overruns:0 frame:0 TX packets:15 errors:0 dropped:1 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:1000 RX bytes:13634 (13.3 KiB) TX bytes:2007 (1.9 KiB)
Sorry to hear you're having problems. Unfortunately I have no idea why your IP's don't stay the same when being renewed. I think I've seen some posts in the forum where people were having similar issues but cannot remember where. It was quite some time ago.Darkness wrote:I updated my setup with the latest autoconfig script, including the DHCP update (Micronet - RTL8188CUS edimax dongle).
It's all working, however, one very anoying thing is that the DHCP client seems to be a little bit over aggressive on renewing it's IP address (both for wifi and lan). Every so many minutes, the ip addresses are renewed causing me to loose the SSH connection.
Before the update, the interfaces were also using DHCP but were always getting the same IP address.
What is causing this behaviour? Can I revert to the previous scheme where it would always get the same address if available?
Code: Select all
iface eth0 inet static address 192.168.1.201 network 192.168.1.0 netmask 255.255.255.0 gateway 192.168.1.1
How about trying to use wpa_supplicant especially if you're taking it out and about connecting to different systems. It would certainly make that easier as it would avoid having to keep editing /etc/network/interfaces whenever you moved to a different network. Can you use that to set fixed IP's? I'm not sure but it may be something to look at. I've been trying to use it here but for some reason I don't seem to get on with it. But many people seem to find it impossible to live without it.Darkness wrote:Actually, I am using the hostname to connect to it, but putty does not really like it if the IP address changes while connected...
Static IP would indeed solve the problem, but since the boards are so small, you don't want to have to change the IP address everytime you take it somewhere else.
The DHCP server is indeed my router but the one from my ISP and I have very little control over it. My Windows laptop is always getting the same IP as were the raspberry pis before the update, so I guess it must be something with the update or a combination with something I already had installed (like winbind for example)
will experiment some more
yeah, that was also something I was thinking about. Maybe the dhcp client is messing with the mac address as well causing the dhcp server to hand out a different IP every time.Lorian wrote:check the MAC address for the wifi stays he same all the time.
If your MAC address is changing take a look here http://www.raspberrypi.org/phpBB3/viewt ... 975#p90975 for a fixDarkness wrote:yeah, that was also something I was thinking about. Maybe the dhcp client is messing with the mac address as well causing the dhcp server to hand out a different IP every time.Lorian wrote:check the MAC address for the wifi stays he same all the time.
It is not specific to the wifi interface, but both wifi and wired LAN connection.
Up to now, I have not done much in Linux with wifi/wpa_supplicant or other related stuff so I guess I'll have to look into that some more as well.
Using 20120629 is working for me, like you suggested, thanx again!MrEngman wrote:Use this one instead. http://dl.dropbox.com/u/80256631/8192cu-20120629.tar.gzDarqueSandu wrote:Thanx for reacting so quickly! I think I already found this link somewhere in this thread, and this is giving me the finger (in the form of a nice 404), so I was hoping somebody had this downloaded file still on disk somewhere, ready to re-share it...!
With the current script the /etc/network/interface can end up like this if you already have it set up for a wifi adapter before running the script or if you run the script more than once. But as the instructions indicate it is designed to work with a fresh image which doesn't have this issue. I am working on a new script which will avoid this problem and even allow setting up multiple wifi's if required.dmpalmer wrote:Thank you for this script. My pi is now wireless. (EDUP 802.11n from DealExtreme.)
1) The following may be a result of previous thrashing around to install the card before I found your script:
I ended up with multiple definitions of the wlan0 in the /etc/network/interfaces file. This prevented logging in over either wired or wireless until it was straightened out. Also, the file's permissions were world-readable (bad in principle since it exposes the wireless network password). As I say, it is not clear that this was your script's fault or my previous thrashing.
2) Your Y or N questions along the way aren't protected against zero-length (carriage return) replies, when the user just hits the carriage return. (Protect by the "x$RESPONSE" != "xY" trick)
The script will be OK provided the driver version specified is OK. Just to make sure .....Montala wrote:Thanks again to MrEngman for his continuing work on this project, and although I have read the instructions, I would like to clarify one point before I proceed.
I have already updated Debian Wheezy by doing a 'sudo apt-get update && sudo apt-get upgrade' and would now like to 'go wireless' with my Edimax device.
Is it still OK to use the 'wheezy' script (20120619) or is there quicker (or better) way to do it, bearing in mind that I have already updated the OS.
Code: Select all
pi@raspberrypi:~$ uname -v #144 PREEMPT Sun Jul 1 12:37:10 BST 2012 pi@raspberrypi:~$ iwconfig lo no wireless extensions. eth0 no wireless extensions. wlan0 unassociated Nickname:"<WIFI@REALTEK>" Mode:Auto Frequency=2.412 GHz Access Point: Not-Associated Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 pi@raspberrypi:~$ lsusb Bus 001 Device 006: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS] ...
Code: Select all
pi@raspberrypi:~$ iwlist wlan0 scan wlan0 No scan results pi@raspberrypi:~$ sudo iwlist wlan0 scan wlan0 Failed to read scan data : No such device
What happens if you try the commandtehowe wrote:My Edimax EW-7811Un was delivered today, so I took the first opportunity to set up and execute MrEngMan's script on a fresh Debian SD card, however the wlan0 interface remains Unassociated.
Code: Select all
ifup --force wlan0
Look on this wiki page and the links are in the Micronet SP907NS, 11N Wireless LAN USB Adapter section.dcullimore wrote:i have downloaded the 8192cu.ko file.
where can i get the script from as i am new to linux and really dont know anything, so a script would be alot easier.