Announcement

**GreyGeek** · Jun 20, 2012, 09:09 PM

Trying to rebuild the kernel is probably the wrong approach.

http://code.google.com/p/msi-wind-linux/wiki/installer

**1richard** · Jun 21, 2012, 05:58 AM

I was not trying to rebuild the kernel, I was merely trying to compile a driver for my usb dongle and following directions that was in the file

**GreyGeek** · Jun 21, 2012, 10:34 AM

When you get a compile error that looks like a source error and you have kernel-devel and kernel-headers installed - then the problem is that the driver is not compatible with the 3.2.0 kernel. Did you install kernel-devel? And, while you are at it, what about fakeroot, build-essential and build-dep

?

Have you tried the other, similar, rtl drivers?
r8187se.ko
r8192e_pci.ko
r8192u_usb.ko
r8712u.ko

:~$ modinfo r8192u_usb
filename: /lib/modules/3.2.0-23-generic/kernel/drivers/staging/rtl8192u/r8192u_usb.ko
description: Linux driver for Realtek RTL8192 USB WiFi cards
version: V 1.1
license: GPL
firmware: RTL8192U/data.img
firmware: RTL8192U/main.img
firmware: RTL8192U/boot.img
license: GPL
description: HostAP crypto
author: Jouni Malinen
license: GPL
description: Host AP crypt: TKIP
author: Jouni Malinen
license: GPL
description: Host AP crypt: CCMP
author: Jouni Malinen
license: GPL
description: Host AP crypt: WEP
author: Jouni Malinen
license: GPL
author: Copyright (C) 2004 Intel Corporation <jketreno@linux.intel.com>
description: 802.11 data/management/control stack
srcversion: CBD0699D19E4573A143D13E
alias: usb:v043Ep7A01d*dc*dsc*dp*ic*isc*ip*
alias: usb:v5A57p0290d*dc*dsc*dp*ic*isc*ip*
alias: usb:v2001p3301d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1740p9201d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0DF6p0031d*dc*dsc*dp*ic*isc*ip*
alias: usb:v050Dp805Ed*dc*dsc*dp*ic*isc*ip*
alias: usb:v07AAp0043d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0BDAp8709d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0BDAp8192d*dc*dsc*dp*ic*isc*ip*
depends:
staging: Y
intree: Y
vermagic: 3.2.0-23-generic SMP mod_unload modversions
parm: debug:debug output mask (int)
parm: ifname: Net interface name, wlan%d=default (charp)
parm: hwwep: Try to use hardware security support. (int)
parm: channels: Channel bitmask for specific locales. NYI (int)

You can do
lsusb
and see if your device alias matches any shown in read above.

Even if they don't there is no harm in trying
sudo modprobe r8192u_usb
and seeing if you get a device created. If you see wlan0 or something similar you can use
sudo ifconfig wlan0 up
iwlist wlan0 scanning
iwconfig wlan0

to see what's happening. If you don't see a wireless connection then
sudo rmmod r8192u_usb
and you are back to where you were.

Lacking any other information I have no other help to offer.

**1richard** · Jun 21, 2012, 01:55 PM

Greygeek, thanks again here is what I got

richard@richard:~$ sudo modprobe r8192u_usb
[sudo] password for richard:
richard@richard:~$ sudo ifconfig wlan1
wlan1 Link encap:Ethernet HWaddr f8:d1:11:0c:74:42
UP BROADCAST 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)

richard@richard:~$ sudo ifconfig wlan1 up
richard@richard:~$ iwlist wlan1 scanning
wlan1 Scan completed :
Cell 01 - Address: 00:60:B3:20:5A:6E
ESSID:"digitron-r1"
Protocol:IEEE 802.11b
Mode:Master
Frequency:2.422 GHz (Channel 3)
Encryption key

ff
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Signal level=44/100
Cell 02 - Address: 00:0F:66:AD:5B:AE
ESSID:"linksys"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.437 GHz (Channel 6)
Encryption key

ff
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Signal level=96/100

richard@richard:~$ iwconfig wlan1
wlan1 unassociated Nickname:"rtl_wifi"
Mode:Managed Access Point: Not-Associated Sensitivity:0/0
Retry

ff RTS thr

ff Fragment thr

ff
Power Management

ff
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

**vinnywright** · Jun 21, 2012, 03:25 PM

looks like it's up (working) which of the 2 access points that it see's is yours ESSID:"digitron-r1" or ESSID:"linksys" ?

click the network manager icon in the system tray (lower right) and then click your connection if you see it listed .............what happens?

VINNY

PS both of those are open (unprotected) which means that any one close enough can use them ....if one is you you should probably fix that ASAP

**1richard** · Jun 21, 2012, 04:16 PM

it cannot get p address, waited 5 minutes and nothing, something is missing I think

**GreyGeek** · Jun 21, 2012, 05:04 PM

Originally posted by 1richard View Post

it cannot get p address, waited 5 minutes and nothing, something is missing I think

You are not clear on what you did.

Assuming you are running some version of Kubuntu, is the network manager showing in the system tray? If it is then left click on it and choose "Network Management Settings". When the dialog appears click on the "Wireless" tab. Click the "Add" button and select "Wireless". On the next dialog select "Scan" and on that graphic click on your ESSID and click "OK". That will take you back to the "Network Management" dialog containing the "Scan" button, but with the ESSID you selected showing in the SSID text box.

Now, using the dialog below as a guide, make up a network name for your wireless connection and put it in the text box labled "Connection Name:" and check the box below that which automatically connects that access point. Also check the "System Connection" check box.

Since you have not set up any security on your wireless router all you have to do is select the new access point you just added and then click the "OK" button.

Attached Files

**GreyGeek** · Jun 21, 2012, 05:14 PM

I forgot to add that you SHOULD protect your wireless access point by setting up WPA2 protection, if your wireless router allows it. Even WEP is better than no protection.

To do that, open your browser to 192.168.1.1 (which is the usually IP address of the wireless router). It may ask for a name and password. If your documentation gives that info to you (or gives a different IP, like 192.168.10.1 for example) then use them. Otherwise, try something like "admin" for the name and a blank password, or perhaps "password" for the password.

IF you get confused or mixed up you can take a straightened paper clip and use it to hit the reset button, which restores factory defaults. That reset button is behind a pin hole in the rear of the case, or sometimes on the bottom.

**1richard** · Jun 21, 2012, 05:34 PM

It still will not get an ip address WICD just keeps trying, I live in the canyon and there is no one near me, so that is why i did not use a password as I use it on 3 different computers here. I am using Kubuntu 12.04. Will keep trying as my other computers are only wireless

**GreyGeek** · Jun 21, 2012, 07:13 PM

Ah, you are using WICD!

It will exhibit that problem IF you have not removed ALL of the NetworkManager files. There is another thread about this topic on the forum which explains what to remove and what to add. You may need to use a cable attached to your AP (as eth0) so that you can make these changes.

But, with Precise installed I would re-install network-manager, network-manager-kde and their required files from the repository (or install the "Network Management" widget into the system tray), and remove all WICD packages, then reboot (or use

sudo service networking start)

.

NetworkManagement is really very good now. But, if you want to stay with it then go on the hunt for stray network-manager packages:
network-manager
network-manager-kde
network-manager-gnome
network-manager-openvpn
network-manager-pptp
network-manager-vpnc
etc...
and remove them and then restart the network. Since you aren't using security it should almost snap in.

BTW, my previous recommendations about removing knm-runtime, network-manager, etc..., did not survive the move to the new forum database and vBulletin.

, but those instructions are no longer practical with Precise because of file name changes.

**Snowhog** · Jun 21, 2012, 07:18 PM

Originally posted by GreyGeek View Post

BTW, my previous recommendations about removing knm-runtime, network-manager, etc..., did not survive the move to the new forum database and vBulletin.

, but those instructions are no longer practical with Precise because of file name changes.

Are you sure? This may not have been the 'original' post on the subject, but it does contain the steps:

http://www.kubuntuforums.net/showthr...etwork-manager

**GreyGeek** · Jun 21, 2012, 11:00 PM

Great! You found it. I looked for it but my vaunted search powers failed me.

Announcement

RTL8188SU will not make

RTL8188SU will not make

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment