Wifi adapter


98 posts   Page 2 of 4   1, 2, 3, 4
by Lorian » Sat Jun 02, 2012 2:23 pm
No, I literally installed pisces and then ran the script for wifi to work.
I just ran apt-get update and apt-get dist-upgrade and wifi still works.

I plan to make a backup image and then I'll get back at nosing at the new kernel/wifi incompatibility issue
<edited>
Posts: 112
Joined: Sun Mar 11, 2012 10:09 am
by Lorian » Sat Jun 02, 2012 8:43 pm
If I run export SKIP_KERNEL=1;rpi-update Then wifi still works, so it's not a firmware issue, its a kernel/module issue. Could of guessed that I suppose.
Posts: 112
Joined: Sun Mar 11, 2012 10:09 am
by MarrsAttax » Mon Jun 04, 2012 7:44 am
I too am trying to get a wireless adapter working. I'm trying to install the drivers for a Realtek rtl8192su but I get errors when I do a make.

Code: Select all
make: *** /lib/modules/3.1.9+/build: No such file or directory.  Stop.
make: *** [all] Error 2


It seems to be complaining it can't find the kernel source.

Here is the Makefile

Code: Select all
LINUX_KSRC_MODULE = /lib/modules/$(shell uname -r)/kernel/drivers/net/wireless/
RTL819x_DIR = $(shell pwd)
KVER  = $(shell uname -r)
KSRC = /lib/modules/$(KVER)/build
RTL819x_FIRM_DIR = $(RTL819x_DIR)/firmware
HAL_SUB_DIR = rtl8192u
MODULE_FILE = $(RTL819x_DIR)/ieee80211/Module.symvers

export LINUX_KSRC_MODULE_DIR RTL819x_FIRM_DIR

all:
ifeq ($(shell uname -r|cut -d. -f1,2), 2.4)
#       @make -C $(RTL819x_DIR)/ieee80211
        @make -C $(RTL819x_DIR)/HAL/$(HAL_SUB_DIR)
else
#       @make -C $(KSRC) SUBDIRS=$(RTL819x_DIR)/ieee80211 modules
        @test -f $(MODULE_FILE) && cp $(MODULE_FILE) $(RTL819x_DIR)/HAL/$(HAL_SUB_DIR) || echo > /dev/null
        @make -C $(KSRC) SUBDIRS=$(RTL819x_DIR)/HAL/$(HAL_SUB_DIR) modules
endif
install:
        @cp $(RTL819x_DIR)/RadioPower.sh /etc/acpi/events/
        @cp $(RTL819x_DIR)/wireless-rtl-ac-dc-power.sh /etc/acpi/
#       @make -C ieee80211/ install
        @make -C HAL/$(HAL_SUB_DIR)/ install
uninstall:
#       @make -C ieee80211/ uninstall
        @make -C HAL/$(HAL_SUB_DIR)/ uninstall
clean:
        @make -C HAL/$(HAL_SUB_DIR)/ clean
        @make -C ieee80211/ clean
        @rm -fr Modules.symvers
        @rm -fr Module.symvers
        @rm -fr Module.markers
        @rm -fr modules.order


The directory /lib/modules/3.1.9+ is empty on my system but there is a directory /lib/modules.bak/3.1.9+ which appears to have files in it but no build directory

here are the contents of the modules.bak directory

Code: Select all
drwxr-xr-x 8 root root   4096 May  1 22:15 kernel
-rw------- 1 root root 198701 May 13 13:34 modules.alias
-rw------- 1 root root 200894 May 13 13:34 modules.alias.bin
-rw-r--r-- 1 root root   2690 May 13 13:34 modules.builtin
-rw------- 1 root root   3387 May 13 13:34 modules.builtin.bin
-rw-r--r-- 1 root root     69 May 13 13:34 modules.ccwmap
-rw------- 1 root root  25835 May 13 13:34 modules.dep
-rw------- 1 root root  41787 May 13 13:34 modules.dep.bin
-rw------- 1 root root    214 May 13 13:34 modules.devname
-rw-r--r-- 1 root root     73 May 13 13:33 modules.ieee1394map
-rw-r--r-- 1 root root    218 May 13 13:34 modules.inputmap
-rw-r--r-- 1 root root     81 May 13 13:33 modules.isapnpmap
-rw-r--r-- 1 root root     74 May 13 13:34 modules.ofmap
-rw-r--r-- 1 root root  13709 May 13 13:33 modules.order
-rw-r--r-- 1 root root     99 May 13 13:33 modules.pcimap
-rw-r--r-- 1 root root    127 May 13 13:33 modules.seriomap
-rw------- 1 root root    131 May 13 13:34 modules.softdep
-rw------- 1 root root  52682 May 13 13:34 modules.symbols
-rw------- 1 root root  64047 May 13 13:34 modules.symbols.bin
-rw-r--r-- 1 root root 640929 May 13 13:33 modules.usbmap


I'm sure I'm just a few easy steps from getting this working but would appreciate someone taking me by the hand and helping me to the finish line :)
Posts: 24
Joined: Fri Jun 01, 2012 2:39 pm
by TenderLoins » Mon Jun 04, 2012 12:38 pm
Try this:

sudo apt-get install git
git clone –depth 1 https://github.com/raspberrypi/linux.git
sudo mv linux /lib/modules/3.1.9+/build
cd /lib/modules/3.1.9+/build
make mrproper
gzip -dc /proc/config.gz > .config
make modules_prepare
Posts: 12
Joined: Tue May 29, 2012 11:48 am
by MrEngman » Mon Jun 04, 2012 1:06 pm
MarrsAttax wrote:I too am trying to get a wireless adapter working. I'm trying to install the drivers for a Realtek rtl8192su but I get errors when I do a make.

Code: Select all
make: *** /lib/modules/3.1.9+/build: No such file or directory.  Stop.
make: *** [all] Error 2


It seems to be complaining it can't find the kernel source.

The directory /lib/modules/3.1.9+ is empty on my system but there is a directory /lib/modules.bak/3.1.9+ which appears to have files in it but no build directory


I'm sure I'm just a few easy steps from getting this working but would appreciate someone taking me by the hand and helping me to the finish line :)


The kernel source needs loading for a start and there may be some other items needed but I'm not sure. I'm hoping to get some tips from here

This pointer may help in organising the kernel source code and setting up links to the source code needed to compile the driver. I've been able to compile the kernel and make an image that is running on my Pi now using mpmc's guide. Just need to compile my wifi driver, like you, so I can get that back running as well.

One question - where do I need to put the driver source to compile it. Do I just generate a directory and install it there and then cd into that directory to do the compile? Guess you should know the answer to that as you're compiling your driver even though it's not quite working yet ;)

MrEngman
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra
Posts: 1843
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK
by MarrsAttax » Tue Jun 05, 2012 11:30 am
Thanks for the tips - I'll read through and report what success I had.

I think you can compile from wherever you want. I copied the source tar.gz file into my home directory and unpacked it there. Then just navigated into the directory it created and ran make. Hope that helps.
Posts: 24
Joined: Fri Jun 01, 2012 2:39 pm
by MarrsAttax » Tue Jun 05, 2012 12:12 pm
I tried TenderLoins script and it's moved me on a bit. I now get the following error when I do a make

Code: Select all
make[1]: Entering directory `/lib/modules/3.1.9+/build'

  WARNING: Symbol version dump /lib/modules/3.1.9+/build/Module.symvers
           is missing; modules will have no dependencies and modversions.

  CC [M]  /home/marrs/rtl8192su_linux_2.6.0002.0708.2009/HAL/rtl8192u/r8180_93cx6.o
gcc: error: -msoft-float and -mhard_float may not be used together
make[2]: *** [/home/marrs/rtl8192su_linux_2.6.0002.0708.2009/HAL/rtl8192u/r8180_93cx6.o] Error 1
make[1]: *** [_module_/home/marrs/rtl8192su_linux_2.6.0002.0708.2009/HAL/rtl8192u] Error 2
make[1]: Leaving directory `/l


Does this mean this particular driver isn't compatible with Raspbian?
Posts: 24
Joined: Fri Jun 01, 2012 2:39 pm
by MrEngman » Tue Jun 05, 2012 12:12 pm
MarrsAttax wrote:Thanks for the tips - I'll read through and report what success I had.

I think you can compile from wherever you want. I copied the source tar.gz file into my home directory and unpacked it there. Then just navigated into the directory it created and ran make. Hope that helps.


Thanks, that's fine. I'll try that and see what happens.
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra
Posts: 1843
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK
by drcosquared » Tue Jun 05, 2012 11:03 pm
Hi All,

I noticed that some of the non-free firmware blobs from Debian were added to the Raspbian archive, so I attempted to install the Realek firmware by following this guide: http://wiki.debian.org/rtl819x. Everything installed fine, however when I plugged the card, it didn't work for iwconfig could not identify any wireless device. I did notice lots of activity in my kernel log however, so hopefully someone finds this useful.
Plugging in the device:
Code: Select all
un  5 18:29:53 rpi kernel: usb 1-1.3: new high speed USB device number 5 using dwc_otg
Jun  5 18:29:53 rpi kernel: usb 1-1.3: New USB device found, idVendor=2001, idProduct=3309
Jun  5 18:29:53 rpi kernel: usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jun  5 18:29:53 rpi kernel: usb 1-1.3: Product: 11n Adapter
Jun  5 18:29:53 rpi kernel: usb 1-1.3: Manufacturer: Realtek
Jun  5 18:29:53 rpi kernel: usb 1-1.3: SerialNumber: 00e04c000001
Jun  5 18:29:53 rpi kernel: cfg80211: Calling CRDA to update world regulatory domain
Jun  5 18:36:16 rpi kernel: DEBUG:handle_hc_chhltd_intr_dma:: XactErr with NYET/NAK/ACK
Jun  5 18:36:16 rpi kernel:
Jun  5 18:36:16 rpi kernel: DEBUG:handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK
Jun  5 18:36:16 rpi kernel:
Jun  5 18:36:16 rpi kernel: DEBUG:handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK
Jun  5 18:36:16 rpi kernel:
Jun  5 18:36:16 rpi kernel: DEBUG:handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK
Jun  5 18:36:16 rpi kernel:
Jun  5 18:36:16 rpi kernel: DEBUG:handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK
Jun  5 18:36:16 rpi kernel:
Jun  5 18:36:16 rpi kernel: DEBUG:handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK
Jun  5 18:36:16 rpi kernel:
Jun  5 18:36:16 rpi kernel: rtlwifi: reg 0x32, usbctrl_vendorreq TimeOut! status:0xffffffb9 value=0x0


After unplugging the device the log gets spamed with this message:
Code: Select all
Jun  5 18:36:16 rpi kernel: usb 1-1.3: USB disconnect, device number 5
Jun  5 18:36:16 rpi kernel: rtlwifi: reg 0x33, usbctrl_vendorreq TimeOut! status:0xffffffed value=0x0
Jun  5 18:36:16 rpi kernel: rtlwifi: reg 0x30, usbctrl_vendorreq TimeOut! status:0xffffffed value=0x0


Hope this is helpful!
Posts: 1
Joined: Tue Jun 05, 2012 10:45 pm
by thom_thumb » Wed Jun 06, 2012 2:51 am
I'm running into similar issues. I'm running Hexxeh's raspbian-r3 image (with or without rpi-update). And I've tried both the original instructions and Hexxeh's driver install script.

The driver install script runs and completes successfully, but the interface never comes up. In fact - /dev/wlan0 never appears, dmesg reports:

Code: Select all
usb 1-1.3: new high speed USB device number 4 using dwc_otg
usb 1-1.3: New USB device found, idVendor=7392, idProduct=7811
usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1.3: Product: 802.11n WLAN Adapter
usb 1-1.3: Manufacturer: Realtek
usb 1-1.3: SerialNumber: 00e04c000001
8192cu: disagrees about version of symbol module_layout


As other folks have mentioned previously. Any thoughts?
Posts: 21
Joined: Tue May 29, 2012 9:21 pm
by Lorian » Wed Jun 06, 2012 6:21 am
MarrsAttax wrote:I tried TenderLoins script and it's moved me on a bit. I now get the following error when I do a make

Code: Select all
make[1]: Entering directory `/lib/modules/3.1.9+/build'

  WARNING: Symbol version dump /lib/modules/3.1.9+/build/Module.symvers
           is missing; modules will have no dependencies and modversions.

  CC [M]  /home/marrs/rtl8192su_linux_2.6.0002.0708.2009/HAL/rtl8192u/r8180_93cx6.o
gcc: error: -msoft-float and -mhard_float may not be used together
make[2]: *** [/home/marrs/rtl8192su_linux_2.6.0002.0708.2009/HAL/rtl8192u/r8180_93cx6.o] Error 1
make[1]: *** [_module_/home/marrs/rtl8192su_linux_2.6.0002.0708.2009/HAL/rtl8192u] Error 2
make[1]: Leaving directory `/l


Does this mean this particular driver isn't compatible with Raspbian?

Looks like you are getting close you need to get rid of the soft float switch from the compile
Posts: 112
Joined: Sun Mar 11, 2012 10:09 am
by thom_thumb » Wed Jun 06, 2012 6:55 pm
So after giving a couple more tries, I see the drivers being loaded and it looks like it's properly talking to the hardware but eventually a lot of these errors show up:

Code: Select all
 ===> FirmwareDownload91C() fw:Rtl819XFwImageArray_TSMC
fw_ver=v75, fw_subver=0, sig=0x88c0
rtl8192c_FirmwareSelfReset =====> 8051 reset success (100) .
reg 0x80, usb read  fail ,status:-110 value=0x0
fw download ok!
Set RF Chip ID to RF_6052 and RF type to 1T1R.
GPIO_IN=0c
eRfPowerStateToSet=0
pdmpriv->TxPowerTrackControl = 1
MAC Address from REG_MACID = 80:1f:02:5c:46:51
MAC Address = 80:1f:02:5c:46:51
-871x_drv - drv_open, bup=1
[rtw_wx_set_pmkid] IW_PMKSA_FLUSH!
set_mode = IW_MODE_INFRA
=>rtw_wx_set_essid
ssid=g\xffffffc6isQ\xffffffffJ\xffffffec)\xffffffcd\xffffffba\xffffffba\xffffffab\xfffffff2\xfffffffb\
*xffffffe3F|\xffffffc2T\xfffffff8\x1b\xffffffe8\xffffffe7\xffffff8dvZ.                               
*c3\xffffff9f\xffffffc9\xffffff9a\xffffff9a, len=32
[rtw_wx_set_pmkid] IW_PMKSA_FLUSH!
###=> usb_read_port_complete => urb status(-71)
continual_urb_error > 4
DEBUG:handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK


and eventually it re-enumerates and starts over. Complete dmesg output can be found here: https://gist.github.com/2883890
Posts: 21
Joined: Tue May 29, 2012 9:21 pm
by Jimmer » Wed Jun 06, 2012 11:50 pm
Just thought I'd put up my notes (in a more organised form) about how exactly I built the 8192cu.ko module after running rpi-update. Figured someone might find it useful.

You have to have the kernel sources (and they have to match the one that you've just updated to, so you need to pull them freshly after the update. You'll have to follow to the letter (and if anything gives you errors, don't blindly barrel on, 'cause it will end up failing). Please note I did a full kernel build in order to get this working because there are no headers supplied that match the kernel and I know of no other way to stop the sym versions errors when compiling modules without having proper headers. The full kernel build takes AGES and is best left overnight. This may be a massive hassle (and not something you can be bothered to repeat after each update) but it's the way I did it (and my wireless works). Plus the realtek source allows you to select the 8192su chipset as well and build that module (but I haven't test it works since I don't have one)

login as root:

get all necessary tools:
Code: Select all
apt-get install git wget unzip wireless-tools wpasupplicant


update firmware & kernel
Code: Select all
rpi-update
reboot


find and remove all previous instances of 8192cu.ko and then depmod
Code: Select all
find / -type f -name "8192cu.ko" -exec rm -f {} \;
depmod -a


get and prepare kernel source (last step takes a long time - best to leave it going overnight):
Code: Select all
mkdir /root/src
cd /root/src
git clone –depth 1 https://github.com/raspberrypi/linux.git
ln -s linux /lib/modules/3.1.9+/build
cd /lib/modules/3.1.9+/build
ln -s arch/arm arch/armv6l
make mrproper
gzip -dc /proc/config.gz > .config
make prepare
make modules_prepare
make && make modules



get wi-fi driver source from
Code: Select all
http://218.210.127.131/downloads/downloadsView.aspx?Langid=1&PNid=48&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true#2772


/path/to is the place you put the file you downloaded in the last step

Code: Select all
cp /path/to/RTL819xCU_USB_linux_v3.4.2_3727.20120404.zip /root/src/
cd /root/src
unzip RTL819xCU_USB_linux_v3.4.2_3727.20120404.zip
cd RTL8188C_8192C_8192D_USB_linux_v3.4.2_3727.20120404
sh install.sh


get firmware and put it in place:
Code: Select all
wget ftp://ftp.dlink.com/Wireless/dwa130_revC/Drivers/dwa130_revC_drivers_linux_006.zip
unzip dwa130_revC_drivers_linux_006.zip
mkdir -p /usr/local/lib/firmware/RTL8192U
cp rtl8192u_linux_2.6.0006.1031.2008/firmware/RTL8192U/* /usr/local/lib/firmware/RTL8192U/


Create a wpa_supplicant config file
Code: Select all
nano /etc/wpa_supplicant/wpa_supplicant.conf


whack the following in (edit ssid, psk and id_str (network name, password and nickname respectively) for your values, leave the rest as written below (alter proto to WPA if using WPA1, keep as RSN if using WPA2):

Code: Select all
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=2

network={
  ssid="My Network"
  proto=RSN
  key_mgmt=WPA-PSK
  pairwise=CCMP TKIP
  group=CCMP TKIP
  psk="My Password"
  id_str="Nickname"
}


If you have more than one network (I've been taking my pi to work and using my SGS2 as a portable hotspot) then add another network={ } stanza changing the ssid, proto, psk and id_str values for this second (or third, or forth) network.

Create a network config file:
Code: Select all
nano /etc/network/interfaces


put the following in it:
Code: Select all
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

allow-hotplug wlan0
  iface wlan0 inet dhcp
  wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf


blacklist original non-working kernel module:
Code: Select all
echo "blacklist rtl8192cu" >> /etc/modprobe.d/blacklist.conf


make sure our module is loaded at boot:
Code: Select all
echo "8192cu" >> /etc/modules


reboot:

Code: Select all
reboot


Enjoy wireless!
Posts: 20
Joined: Tue Jan 10, 2012 5:34 pm
by MrEngman » Thu Jun 07, 2012 1:38 am
Hi Jimmer,

I like it! I've been able to compile the new wifi driver but I've only been able to get it to run on one of my SD cards and even then only after I'd rebooted after installing it. Some initialisation appeared to happen while booting up and the wifi came alive and its been OK since. But I cannot get it running after installing it on several other SD cards and trying them.

I tried recompiling today and something went wierdly wrong. The driver module that I compiled yesterday was 619747 bytes. But when I recompiled today the size was an unbelievable 8041828 bytes!!! Almost 13 times bigger. :o

God knows what happened. Recompiling again gave the same result. What has happened I have no idea.

I'm now going to try your method so I'm off to reload the linux source and start that compiling and it should be done in the morning. Then to try recompiling the driver.

Just one thing. The firmware for the wifi from the file dwa130.... now appears redundant and not used. Put it this way, on the SD card that my wifi is working on with the newly compiled driver I have deleted that firmware. And if you look in the driver source there is a large include file - farray.h - which contains a load of hex data - the included firmware. So no more trouble with loading seperately licenced firmware.

I also saw somewhere on the Debian web site that the driver is being included in the latest versions of source code so hopefully soon we will not need to worry about recompile the driver seperately.

Anyway thanks for posting all that info. It's really helpful and I'll let you know how I get on.
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra
Posts: 1843
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK
by Lorian » Thu Jun 07, 2012 8:52 am
I've built version 3.4.2 of the 8192cu driver under raspbian and for me this now appears to work OK after running rpi-update, with limited testing.

If anyone else wants to try it you can grab it, before doing an rpi-update.

Code: Select all
cd /lib/modules/3.1.9+/kernel/drivers/net/wireless
mv 8192cu.ko 8192cu.ko.old
wget http://www.bug-byte.co.uk/pi/8192cu.ko

I would suggest taking an image of your card first in case you need to roll-back.

Obviously you have had to do the setup mentioned previously in the thread first, blacklisting the rtl8192 driver etc.
Posts: 112
Joined: Sun Mar 11, 2012 10:09 am
by Jimmer » Thu Jun 07, 2012 9:58 am
Ah Mr Engman, thanks for the fw tip! I hope that by posting the details of how I built the module, people can have a go for themselves. After all, it's meant to be that kind of platform! Anyway, I had some issues with the 3.4.x driver after I tried this again after another kernel update: everything compiles fine and the module loads without issue, but no wlan0 interface is created. Typically dmesg shows no info!

Anyway, long story short, I tried to compile the earlier 3.0.2 driver source instead. This worked first time! I wonder if it's this fw issue you mention. the 3.0.x series driver expects a fw file, looks for it, finds it where it likes and loads it fine. The 3.4.x series has a bundled fw but the stick itself fails to load it.....

I will dig further!
Posts: 20
Joined: Tue Jan 10, 2012 5:34 pm
by Jimmer » Thu Jun 07, 2012 10:28 am
Just for a test, I downloaded the 8192cu.ko that Lorian so kindly provided. Again, the module loads on my kernel, but it will not bring up a wlan0 interface. I can still get a working interface by insmod-ding my 3.0.x driver.

I wonder what is different for me that for Lorian. I will provide a few details: I'm running Raspbian from a usb stick (possible issue there with the usb?), I am overclocking and overvolting the Pi (1000 Mhz, Overvolt 6). Before the last kernel update I had the 3.4.x drivers working fine with this set-up though.....
Posts: 20
Joined: Tue Jan 10, 2012 5:34 pm
by MarrsAttax » Thu Jun 07, 2012 10:29 am
Thanks for this Jimmer, I'll give it a go. Is there a special tool I need to backup the image on my SD card?
Posts: 24
Joined: Fri Jun 01, 2012 2:39 pm
by Jimmer » Thu Jun 07, 2012 11:40 am
Marrs, you can use the reverse process of how you imaged the card in the first place. On a linux machine find the /dev/ node that corresponds to your sdcard ie /dev/sdX (where X is the letter a,b,c, etc depending on your machine configuration - see my note on the mount command below) and then:

dd bs=1M if=/dev/sdX of=~/MyRpiBackup.img

make sure you don't use the partition numbers (ie sdX1), but the root device sdX to create an image of the whole sdcard. Also make sure none of the partitions are mounted on your linux machine (issuing mount from the commandline will show you a list of all currently mounted disks, after you 1st plug in the sdcard, it'll probably automount on most modern distros and you can use this to find the /dev/sdX info for the dd command).

if you want to do this on a mac, then you need to find the diskX number (highlight the sdcard in diskutility, press cmd+i and in the info window it will say something like diskXs1 in the device identifier field (where X will be a number). You then use the following (after unmounting):

dd bs=1M if=/dev/rdiskX of=~/MyRpiBackup.img

obviously subbing in the number you found out for X

I'm not sure how to do it on windows, but someone here will probably know.....
Posts: 20
Joined: Tue Jan 10, 2012 5:34 pm
by MarrsAttax » Thu Jun 07, 2012 12:29 pm
Thanks Jimmer. I am using Windows and have just worked out how to do it.

I used Win32 Disk Imager to write my original image to the SD. Backing up is as easy as entering a new file name e.g backup.img and then clicking the 'Read' button' rather than the 'Write' button :lol:
Posts: 24
Joined: Fri Jun 01, 2012 2:39 pm
by Jimmer » Thu Jun 07, 2012 12:52 pm
Lol!
Posts: 20
Joined: Tue Jan 10, 2012 5:34 pm
by thom_thumb » Thu Jun 07, 2012 2:25 pm
Just a heads-up: as of this morning I'm having trouble just doing a `rpi-update` - I got this in dmesg before the update finished:

Code: Select all
mmc0: Controller never released inhibit bit(s).
mmc0: Controller never released inhibit bit(s).
mmc0: Controller never released inhibit bit(s).
mmc0: Controller never released inhibit bit(s).
mmc0: Controller never released inhibit bit(s).
mmc0: Controller never released inhibit bit(s).
mmc0: Controller never released inhibit bit(s).
ipv6: disagrees about version of symbol module_layout


Then after one reboot, the rpi boot a second time.
Posts: 21
Joined: Tue May 29, 2012 9:21 pm
by thom_thumb » Thu Jun 07, 2012 3:16 pm
So I learned a couple things.... After trying to get an Apple USB keyboard to working and seeing this same error:

Code: Select all
DEBUG:handle_hc_chhltd_intr_dma:: XactErr without NYET/NAK/ACK


turns out that is a symptom of needing a powered USB hub!

So I went back to hexxeh's stock raspbian-r3 image and ran raspbian-hexxeh-install-rtl8188cus.sh. Now it works! So my (initial) problem seems to be the power draw on the wifi dongle is too great to plug directly into the rpi!

Now it still seems like there are other issues with newer kernel versions, simply running rpi-update this morning was causing problems for me with other drivers (ipv6) unrelated to the 8192cu driver. Hopefully this explains why it's working for some people and not others!
Posts: 21
Joined: Tue May 29, 2012 9:21 pm
by Lorian » Thu Jun 07, 2012 5:16 pm
Jimmer wrote:Just for a test, I downloaded the 8192cu.ko that Lorian so kindly provided. Again, the module loads on my kernel, but it will not bring up a wlan0 interface. I can still get a working interface by insmod-ding my 3.0.x driver.

I wonder what is different for me that for Lorian. I will provide a few details: I'm running Raspbian from a usb stick (possible issue there with the usb?), I am overclocking and overvolting the Pi (1000 Mhz, Overvolt 6). Before the last kernel update I had the 3.4.x drivers working fine with this set-up though.....


Weird. I've copied the 3.4.2 driver over to another card which I haven't used for a few days and then rpi-updated and it works OK on that one too. As far as I am aware there is nothing else special about my installs.

Do you get anything interesting in dmesg?

To add to the comparison of environment, I'm running on a Pi with two installs, SD cards (8GB class 4 and 16Gb class 10) overclocked at 850/500 with no over-volt. One has the full kernel dev environment, one does not.

I have the Edimax Micro USB version of the device, acroding to the specs it is an 8192cu not a variation, although the drivers seem to be the same for a number of the realtek devices.

I'm not using wpa-supplicant. I recall there might be a new version but I haven't compiled it.
Last edited by Lorian on Thu Jun 07, 2012 5:35 pm, edited 2 times in total.
Posts: 112
Joined: Sun Mar 11, 2012 10:09 am
by Lorian » Thu Jun 07, 2012 5:20 pm
thom_thumb wrote:Just a heads-up: as of this morning I'm having trouble just doing a `rpi-update` - I got this in dmesg before the update finished:

Code: Select all
mmc0: Controller never released inhibit bit(s).
mmc0: Controller never released inhibit bit(s).
mmc0: Controller never released inhibit bit(s).
mmc0: Controller never released inhibit bit(s).
mmc0: Controller never released inhibit bit(s).
mmc0: Controller never released inhibit bit(s).
mmc0: Controller never released inhibit bit(s).
ipv6: disagrees about version of symbol module_layout


Then after one reboot, the rpi boot a second time.

The last error message is the one we have been trying to re-compile the drivers to fix. You could try a 3.4.2 version and see if it works for you:

cd /lib/modules/3.1.9+/kernel/drivers/net/wireless
mv 8192cu.ko 8192cu.ko.old
wget http://www.bug-byte.co.uk/pi/8192cu.ko

obviously you need to be on a wired connection to do this after doing a rpi-update

Will be interesting to see if this works. If it doesn't you might need Jimmer's 3.0.x version
Posts: 112
Joined: Sun Mar 11, 2012 10:09 am