Blacklist displays only one thing.
Code:oscar@ubuntu:~$ cat /etc/modprobe.d/blacklist.confg
blacklist r8168
Printable View
Blacklist displays only one thing.
Code:oscar@ubuntu:~$ cat /etc/modprobe.d/blacklist.confg
blacklist r8168
Please do:Reboot and let us see:Code:sudo su
echo "blacklist r8168" >> /etc/modprbe.d/blacklist.conf
rm /etc/modprobe.d/blacklist.confg <--proofread carefully before you press Enter!
exit
Hopefully, it's blank.Code:dmesg | grep r816
I hope there is some change here:Code:nm-tool
Quote:
Type: Wired
Driver: sundance
State: unavailable
Default: no
HW Address: 00:26:18:EB:8F:9E
I typed in everything word for word (except the first line, where it said no such file or directory - modprbe.d/blacklist.conf
I did modprobe.d/blacklist.conf
Then the rest I did the same as you instructed and yet:
Too bad it didn't go as planned. I also went to /etc/modprobe.d/blacklist.conf and found this at the end of the file:Code:oscar@ubuntu:~$ dmesg | grep r816
[ 1.388084] r8168 Gigabit Ethernet driver 8.034.00-NAPI loaded
[ 1.388114] r8168 0000:04:00.0: enabling device (0000 -> 0003)
[ 1.388125] r8168 0000:04:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 1.388139] r8168 0000:04:00.0: PowerManagement capability not found.
[ 1.388155] r8168 0000:04:00.0: setting latency timer to 64
[ 1.388227] Modules linked in: r8168(O+) floppy pata_jmicron
[ 1.388332] [<ffffffffa002cdf2>] rtl8168_init_one+0x673/0x2c6ff [r8168]
[ 1.388416] [<ffffffffa005f01e>] rtl8168_init_module+0x1e/0x1000 [r8168]
oscar@ubuntu:~$ nm-tool
NetworkManager Tool
State: disconnected
- Device: eth1 -----------------------------------------------------------------
Type: Wired
Driver: sundance
State: unavailable
Default: no
HW Address: 00:26:18:EB:8F:9E
Capabilities:
Wired Properties
Carrier: off
Code:# 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_edac
blacklist r8168
blacklist r8168
The module r8168 is somehow still loading! There must be some other file that invokes it. Let's see:Quote:
[ 1.388084] r8168 Gigabit Ethernet driver 8.034.00-NAPI loaded
[ 1.388114] r8168 0000:04:00.0: enabling device (0000 -> 0003)
[ 1.388125] r8168 0000:04:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 1.388139] r8168 0000:04:00.0: PowerManagement capability not found.
[ 1.388155] r8168 0000:04:00.0: setting latency timer to 64
[ 1.388227] Modules linked in: r8168(O+) floppy pata_jmicron
[ 1.388332] [<ffffffffa002cdf2>] rtl8168_init_one+0x673/0x2c6ff [r8168]
[ 1.388416] [<ffffffffa005f01e>] rtl8168_init_module+0x1e/0x1000 [r8168]
Code:cat /etc/modules
ls /etc/modprobe.d
Good catch; sorry about that.Quote:
(except the first line, where it said no such file or directory - modprbe.d/blacklist.conf
I did modprobe.d/blacklist.conf
*Chili cleans his glasses and monitor*
Sorry for the long delay in reply.. had a busy day. heh
Here's the stuff that were asked.
Code:oscar@ubuntu:~$ cat /etc/modules
# /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
rtc
alias eth0 NX1001
options NX1001
sundance
oscar@ubuntu:~$ ls /etc/modprobe.d
alsa-base.conf blacklist-framebuffer.conf blacklist-watchdog.conf
blacklist-ath_pci.conf blacklist-modem.conf vmwgfx-fbdev.conf
blacklist.conf blacklist-oss.conf
blacklist-firewire.conf blacklist-rare-network.conf
The parts I've highlighted are meaningless; they may be confusing to the system, I don't know. In either case, let's remove them:Quote:
# /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
rtc
alias eth0 NX1001
options NX1001
sundance
Remove the highlighted lines so that it reads:Code:gksudo gedit /etc/modules
Proofread, save and close gedit.Code:# /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
rtc
sundance
Is r8168 still loading as if by magic?I am still trying to work out how; back in a few minutes.Code:lsmod | grep r816
EDIT: I still see no reason it's loading. Does it appear still in dmesg and lsmod?
Erased the part and saved.
Yes, r8168 still shows up in lsmod and dmesg.
Frankly, I think our chances of getting the Realtek going are a lot better than the NX1001. If you are still convinced the NX1001 is a better choice, let's rename the r8168 driver so it won't load:Those backticks are on the left side of my US keyboard on the same key with ~.Code:sudo mv /lib/modules/`uname -r`/kernel/drivers/net/ethernet/realtek/r8168.ko /lib/modules/`uname -r`/kernel/drivers/net/ethernet/realtek/r8168.bak
By renaming the r8168 driver, we can prevent it from loading and yet restore it again in the future if needed.
Reboot and confirm it's no longer in lsmod and demsg. Then let us see:Code:sudo cat /var/log/syslog | grep -e sundance -e etwork | tail -n20
This is ridiculous. I have renamed the file as said, I checked if its there, rebooted and r8168 still shows up in lsmod and dmesg.
It seems you are more than right - Asus just doesn't seem to be a good choice in this situation. I mean it works just fine on Windows, whilst Realtek doesn't work at all in there.
On Ubuntu, however, Realtek is the stubborn one...
I did the syslog and here's what showed up:
I know it seems silly at this point, where we tried to get rid of Realtek by any means, but if it is really easier to get it working than Asus then I think we'd go with it.Code:oscar@ubuntu:~$ sudo cat /var/log/syslog | grep -e sundance -e etwork | tail -n20
Nov 16 14:10:06 ubuntu NetworkManager[744]: <info> modem-manager is now available
Nov 16 14:10:06 ubuntu NetworkManager[744]: <info> monitoring kernel firmware directory '/lib/firmware'.
Nov 16 14:10:06 ubuntu NetworkManager[744]: <info> WiFi enabled by radio killswitch; enabled by state file
Nov 16 14:10:06 ubuntu NetworkManager[744]: <info> WWAN enabled by radio killswitch; enabled by state file
Nov 16 14:10:06 ubuntu NetworkManager[744]: <info> WiMAX enabled by radio killswitch; enabled by state file
Nov 16 14:10:06 ubuntu NetworkManager[744]: <info> Networking is enabled by state file
Nov 16 14:10:06 ubuntu NetworkManager[744]: <warn> failed to allocate link cache: (-10) Operation not supported
Nov 16 14:10:06 ubuntu NetworkManager[744]: <info> (eth1): driver 'sundance' does not support carrier detection.
Nov 16 14:10:06 ubuntu NetworkManager[744]: <error> [1353075006.175899] [nm-device-ethernet.c:456] real_update_permanent_hw_address(): (eth1): unable to read permanent MAC address (error 22)
Nov 16 14:10:06 ubuntu NetworkManager[744]: <info> (eth1): new Ethernet device (driver: 'sundance' ifindex: 2)
Nov 16 14:10:06 ubuntu NetworkManager[744]: <info> (eth1): exported as /org/freedesktop/NetworkManager/Devices/0
Nov 16 14:10:06 ubuntu NetworkManager[744]: <info> (eth1): now managed
Nov 16 14:10:06 ubuntu NetworkManager[744]: <info> (eth1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov 16 14:10:06 ubuntu NetworkManager[744]: <info> (eth1): bringing up device.
Nov 16 14:10:06 ubuntu NetworkManager[744]: nm_netlink_monitor_get_flags_sync: assertion `self != NULL' failed
Nov 16 14:10:06 ubuntu NetworkManager[744]: <warn> (eth1): couldn't get carrier state: (-1) unknown
Nov 16 14:10:06 ubuntu NetworkManager[744]: <info> (eth1): carrier now OFF (device state 20, deferring action for 4 seconds)
Nov 16 14:10:06 ubuntu NetworkManager[744]: <info> (eth1): preparing device.
Nov 16 14:10:06 ubuntu NetworkManager[744]: <info> (eth1): deactivating device (reason 'managed') [2]
Nov 16 14:10:06 ubuntu kernel: [ 10.445144] type=1400 audit(1353075006.201:8): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=781 comm="apparmor_parser"
I suspect it is. I suggest you physically remove the NX1001. Restore the r8168 driver:Quote:
if it is really easier to get it working than Asus then I think we'd go with it.
Remove the blacklists:Code:sudo mv /lib/modules/`uname -r`/kernel/drivers/net/ethernet/realtek/r8168.bak /lib/modules/`uname -r`/kernel/drivers/net/ethernet/realtek/r8168.ko
Attach the ethernet cable to the Realtek and reboot. Then let us see:Code:gksudo gedit /etc/modprobe.d/blacklist.conf
Code:nm-tool
sudo cat /var/log/syslog | grep -e r816 -e etwork | tail -n20
This is probably most of the problem. I have no idea what to do to try to fix it.Quote:
(eth1): unable to read permanent MAC address (error 22)