I've installed Natty on my Samsung N130. It has the Realtek card. It's pretty good, except the wireless does not always work. It seems like it's 5 minutes on, 5 minutes off. I have already tried most of the solutions offered for previous versions of Ubuntu. The one thing I haven't tried is using ndiswrapper to install the Windows drivers because I can't find the drivers anywhere.

I had this working perfectly in Maverick using this (http://www.greenhughes.com/content/installing-ubuntu-1010-samsung-nb30-touchscreen-netbook) solution. There is no samsung-wireless for Natty (yet), so I tried using the package for Maverick to no avail. If it makes a difference, the wireless was working perfectly during the installation.

Any help is appreciated. Thank you.

jcr1

April 30th, 2011, 08:34 PM

Sorry no solution here, but I am going to be keeping an eye on this one as I have the same netbook and the same problem. Just upgraded to Natty and no wireless.

Hippytaff

April 30th, 2011, 08:35 PM

if you post the results.txt generated by the wireless script (link below) people will be able to assist :-)

Shake 'n' Bake

April 30th, 2011, 09:57 PM

I'll run that script in an hour or two. I've got to go take care of a fallen tree right now. Thanks for that.

************************************************** ************************
Modules file
************************************************** ************************
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

lp
r8192_pci

************************************************** ***********************
Blacklist file
************************************************** ***********************
# This file lists those modules which we don't want to be loaded by
# alias expansion, usually so some other driver will be loaded for the
# device instead.

# evbug is a debug tool that should be loaded explicitly
blacklist evbug

# these drivers are very simple, the HID drivers are usually preferred
blacklist usbmouse
blacklist usbkbd

# replaced by e100
blacklist eepro100

# replaced by tulip
blacklist de4x5

# causes no end of confusion by creating unexpected network interfaces
blacklist eth1394

# snd_intel8x0m can interfere with snd_intel8x0, doesn't seem to support much
# hardware on its own (Ubuntu bug #2011, #6810)
blacklist snd_intel8x0m

# ugly and loud noise, getting on everyone's nerves; this should be done by a
# nice pulseaudio bing (Ubuntu: #77010)
blacklist pcspkr

# EDAC driver for amd76x clashes with the agp driver preventing the aperture
# from being initialised (Ubuntu: #297750). Blacklist so that the driver
# continues to build and is installable for the few cases where its
# really needed.
blacklist amd76x_eda
blacklist r8192se_pci
blacklist r8192e_pci

Anybody got anything? The only thing I can think of is the wrong drivers are being loaded.

Shake 'n' Bake

May 3rd, 2011, 01:39 AM

I just tried installing the Windows drivers with ndiswrapper after finding them on the Samsung site. That didn't work. So I tried that in addition to all the other things I have done and that didn't work. If this problem can't get solved by next Sunday, I'm probably going back to 10.10, just because it works.

************************************************** ************************
Modules file
************************************************** ************************
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

lp
r8192_pci

************************************************** ***********************
Blacklist file
************************************************** ***********************
# This file lists those modules which we don't want to be loaded by
# alias expansion, usually so some other driver will be loaded for the
# device instead.

That's my old "friend"- a Realtek 8192E! The good news- you do have wireless connectivity and that wireless is a LOT easier under 32-bit.

It looks to me like we need to get rid of that conflicting "r8169" Realtek module that I highlighted in red. Try the following terminal commad:

sudo rmmod r8169Then disconnect your ethernet cable and see if your wireless connection behaves better. If so, we will need to blacklist "r8169" in your /etc/modprobe.d/blacklist.conf file. Sometimes it takes a few minutes for the wireless changes to take effect.

I've got a copy of a relative's "blacklist.conf" file with the changes that I needed to make to get the Realtek 8192E working under 64-bit Ubuntu, but I'll need to locate a couple of USB thumb drives first.

NOTE: One thing you will want to watch- the Realtek 8192E is quite different from the Realtek 8192SE (as well as the USB Reatlek 8192SU). This affects the driver modules, and your blacklisting, etc.

Thank you so much! I did both "sudo rmmod r8169" and the blacklist changes and the wireless is working perfectly, so far. I'll mark it solved if it's still working ten minutes or so from now.

Shake 'n' Bake

May 3rd, 2011, 10:19 PM

It appears I've spoken too soon. After about half an hour of working, it just stopped. So I did a fresh install and I'm trying everything over again. None of it has worked, unfortunately.

I did notice that when I blacklist r8169 with the two others (and I'm testing on its own now), my wireless card is not even recognized.

EDIT: When I blacklist just "r8169", the wireless appears, but does not connect. When I blacklist just "r8169_pci", the wireless simply does not appear.

northd_tech

May 4th, 2011, 05:35 AM

How did you make your blacklist changes exactly? The sudo/su thing might have prevented the changes from being saved (most editors like gedit and Kate will open the "system" files as read only if you don't "promote" the file permissions).

It might be good to post the results of this command (and review the changes in your system fairly often to see if/which modules disappear and/or reappear while your wireless is/isn't working):

lsmod | grep 81Have you tried building the module(s) directly from the Realtek sourcecode that was in the #comments of my recent blacklist post? That's the ONLY way that I was able to get that Realtek 8192E working (but that was under both Ubuntu 9.xx and 10.xx).

Once again, that sourcecode was at post #34 by "eldergs":
http://ubuntuforums.org/showpost.php?p=10487458&postcount=34

I summarized my blacklisting stuff at post #44 on that same thread:
http://ubuntuforums.org/showpost.php?p=10760256&postcount=44

northd_tech

May 4th, 2011, 06:42 AM

If this problem can't get solved by next Sunday, I'm probably going back to 10.10, just because it works.

If you eventually plan to reinstall anyway, I'd consider 10.04 LTS (with LTS meaning Long Term Support, read by me as "much less futzing with your kernel modules, drivers, etc." ;) ).

https://wiki.ubuntu.com/LTS

Just my $0.02 U.S....

Shake 'n' Bake

May 4th, 2011, 08:01 PM

Here are the results of "lsmod | grep 81":

r8192e_pci 251260 0
r8169 42534 0
I'm going to try building the modules right now. Thanks again for your help.

EDIT: Building the module from scratch seems like it has worked perfectly (for now). I'm going to install some software and if it keeps working I'd say its fixed. Thanks.