Asus NX1001 card

[Oskarm]

I have two network cards on my computer:
ASUS NX1001 and Realtek RTL 8111/8168B

For some reason I cannot get any one of them to work! I tried to install Realtek driver from the web and nothing happened! Asus has a CD with drivers for kernels 2.4 and 2.6, but none of the commands in README file work!

I am a beginner in this and I have searched around for AGES trying to get an answer for either two and I still can't find anything that would help me.

EDIT: I found the README file for Asus network card. None of this actually want to work.

                ASUS NX1001 Network Adapter  
                       Linux Driver  
 
Contents: 
----------- 
1. File Description 
2. Driver Installation for Linux 
3. Driver Parameter 
 
1. File Description 
------------------- 
 
Filename                Description 
====================    ======================================================= 
NX1001_main.c           ASUS NX1001 Network Adapter Driver Source Code. 
                        This file is the main part of ASUS NX1001 Network Adapter. 
 
compat.h                Network interface message level settings. 
 
crc32.h                 Crc function for early Linux 2.4.19pre kernel inclusion 
 
ethtool.h:              Defines for Linux ethtool. 
 
mii.h                   definitions for MII-compatible transceivers. 
 
mii.c                   MII interface library. 
 
makefile                Make File For ASUS NX1001 Network Adapter. 
                        Using "make all" for your kernel. 
 
readme.txt              A summary of the contents for Linux Driver. 
                        This file, which you are reading me now. 
 
 
 
2. Driver Installation for Linux 
----------------------------------------- 
a. for kernel 2.4.x 
   a1. Redhat 7.3 (linux kernel 2.4.18) 
   a2. Mandrake 8.1 (kernel 2.4.8) 
b. for kernel 2.6.x 
c. automatically load and configure at next boot time 
 
   a.for kernel 2.4.x 
   ------------------- 
     a1. Redhat 7.3 (linux kernel 2.4.18) 
     a1.1. install way 1: 
         #make all =>generate NX1001.o 
         #cp NX1001.o /lib/modules/2.4.18-3/kernel/drivers/net/ 
         #insmod ./NX1001.o 
         #ifconfig eth0 xxx.xxx.xxx.xxx netmask yyy.yyy.yyy.yyy 
            eth0 is your network adapter,use "dmesg" to check it, ex: eth0, eth1... 
            xxx  is your ip address, ex: 192.168.102.211 
            yyy  is your netmask address, ex:255.255.255.0 
 
     a1.2.  install way 2: 
        #make all =>generate NX1001.o 
        #cp NX1001.o /lib/modules/2.4.18-3/kernel/drivers/net/ 
        #insmod./NX1001.o 
        #setup 
        [network configuration] =>to setup your ip address 
        #ifup eth0 
           eth0 is your network adapter, ex: eth0, eth1...     
 
 
     a2. Mandrake 8.1 (kernel 2.4.8) 
       #make all  => generate Nx1001.o 
       #cp NX1001.o /lib/modules/2.4.8-26mdk/kernel/drivers/net 
       #insmod ./NX1001.o 
       #ifconfig eth0 xxx.xxx.xxx.xxx netmask yyy.yyy.yyy.yyy 
           eth0 is your network adapter,use "dmesg" to check it, ex: eth0, eth1... 
           xxx  is your ip address, ex: 192.168.102.211 
           yyy  is your netmask address, ex:255.255.255.0 
 
 
   b. for kernel 2.6.x 
   ------------------- 
      #make all  => generate NX1001.ko 
      #insmod ./NX1001.ko (or NX1001.o) 
      #ifconfig eth0 xxx.xxx.xxx.xxx netmask yyy.yyy.yyy.yyy 
            eth0 is your network adapter,use "dmesg" to check it, ex: eth0, eth1... 
            xxx  is your ip address, ex: 192.168.102.211 
            yyy  is your netmask address, ex:255.255.255.0       
    
   c. automatically load and configure at next boot time 
   ----------------------------------------------------- 
     c1. cp NX1001.o /lib/modules/`uname -r`/kernel/drivers/net 
     *note: The `uname -r` is a command. Don't replace `uname -r` with 
            2.4.18, 2.4.20smp, or some others. Must type `uname -r` directly. 
 
     c2. Add the following lines at /etc/modules.conf: 
                
          alias eth0 NX1001 
          options NX1001 <optional parameters> 
                               
     c3. Run "netconfig" or "netconf" to create configuration script  
 
              ifcfg-eth0 located at /etc/sysconfig/network-scripts or  
              create it manually. 
              [see - Configuration Script Sample] 
 
     c4. Driver will automatically load and configure at  
              next boot time. 
               
     c5. Configuration Script Sample 
     =========================== 
         Here is a sample of a simple configuration script: 
 
         DEVICE=eth0 
         USERCTL=no 
         ONBOOT=yes 
         POOTPROTO=none 
         BROADCAST=207.200.5.255 
         NETWORK=207.200.5.0 
         NETMASK=255.255.255.0 
         IPADDR=207.200.5.2 
               
 
3. Driver Parameter 
------------------- 
  If you want to change the link speed, you could use parameter after  
  insmod command. 
   
  insmod NX1001.o <optional parameter>    ; add parameter 
 
  ======================================================================== 
   example: insmod NX1001.o media=100mbps_hd 
   or        insmod NX1001.o media=3 
   or        insmod NX1001.o media=1,2,3,4    ; for 4 cards or NX1001 
  ========================================================================               
   
  Parameter Description 
  ===================== 
  You can install this driver without any addtional parameter. However, if  
  you are going to have extensive functions then it is necessary to set  
  extra parameter. Below is a list of the command line parameters supported  
  by the Linux device driver. 
 
media=xxxxxxxxx            - Specifies the media type the NIC operates at. 
                  autosense    Autosensing active media. 
                  10mbps_hd    10Mbps half duplex. 
                  10mbps_fd    10Mbps full duplex. 
                  100mbps_hd    100Mbps half duplex. 
                  100mbps_fd    100Mbps full duplex. 
                  0        Autosensing active media. 
                  1        10Mbps half duplex. 
                  2        10Mbps full duplex. 
                  3        100Mbps half duplex. 
                  4        100Mbps full duplex. 
                  By default, the copper devices operate at  
                  autosense, the fiber devices operate at 
                  100Mbps full duplex. 
                  Note that, the fiber adapter only support  
                  100Mbps half/full duplex types.     
 
  If wanting to change speed, this driver needed to be unloaded and reloaded with  
  new media parameter. 
 
flowctrl=[0|1]            - Specifies the flow control function. 
                  0    Disable flow control.     
                  1    Enable flow control.

[chili555]

Driver-dawg is here and we'll solve the mystery. First of all, this antique is mostly useless:

ASUS NX1001 Network Adapter
Linux Driver

Contents:
-----------
1. File Description
2. Driver Installation for Linux
3. Driver Parameter
<snip>

It was written in 2005 (!!) which is 1492 in Linux years. It does, however, offer some clues. Here is a quote from the nx1001_main.c file:

// 04/13/2004 {"Sundance Technology Alta"},
{"ASUS NX1001 Network Adapter"},
{"ASUS NX1001 Network Adapter" },
{0,}, /* 0 terminated list. */

'Sundance' you say?? We have a module named sundance in Ubuntu. Here is its modinfo:

$ modinfo sundance
filename: /lib/modules/3.5.0-18-generic/kernel/drivers/net/ethernet/dlink/sundance.ko
license: GPL
description: Sundance Alta Ethernet driver
author: Donald Becker <becker@scyld.com>
srcversion: EFE11127C4FE4C585542FB2
alias: pci:v000013F0d00000200sv*sd*bc*sc*i*
alias: pci:v000013F0d00000201sv*sd*bc*sc*i*
alias: pci:v00001186d00001002sv*sd*bc*sc*i*
alias: pci:v00001186d00001002sv00001186sd00001040bc*sc*i*
alias: pci:v00001186d00001002sv00001186sd00001012bc*sc*i*
alias: pci:v00001186d00001002sv00001186sd00001003bc*sc*i*
alias: pci:v00001186d00001002sv00001186sd00001002bc*sc*i*
depends:
intree: Y
vermagic: 3.5.0-18-generic SMP mod_unload modversions
parm: media:array of charp
parm: debug:Sundance Alta debug level (0-5) (int)
parm: rx_copybreak:Sundance Alta copy breakpoint for copy-only-tiny-frames (int)
parm: flowctrl:Sundance Alta flow control [0|1] (int)

Let's see if your device is claimed by sundance. Please open a terminal and run and post:

lspci -nn | grep 0200
uname -rp

The pipe symbol | is on the right side of my US keyboard on the same key with \.

Are you planning somehow to run both cards at the same time? Is the Realtek not working as expected?

[Oskarm]

Okay I did some tap tapping into terminal and here are the results.

lspci -nn | grep 0200
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 01)
05.00.0 Ethernet controller [0200]: Sundance Technology Inc / IC Plus Corp IC Plus IP100A Integrated 10/100 Ethernet MAC + PHY [13f0:0200] (rev 31)

uname -rp
3.2.0-29-generic x86_64

I am still using Ubuntu 12.04 on the PC mainly because it stays idle due to no internet connection.
The realtek card didn't even want to work under Windows. For some reason whenever I tried to install the driver for it, it changed its own name and declined that the driver was correct. Anyhow, that's the reason I got the Asus card and it works fine under Windows (because it has an auto-installer), but can't get it to work here just yet.

I don't plan to run both of them together, just one so I can start using ubuntu with internet. Right now I'm typing with laptop on my lap.

[chili555]

Sundance Technology Inc / IC Plus Corp IC Plus IP100A Integrated 10/100 Ethernet MAC + PHY [13f0:0200]

Here is a snip from the modinfo I posted above:

$ modinfo sundance | grep 13F0
alias: pci:v000013F0d00000200sv*sd*bc*sc*i*
alias: pci:v000013F0d00000201sv*sd*bc*sc*i*

Let's save ourselves some anguish. In case the driver for the Realtek is trying to load and interfer, let's blacklist it:

sudo su
echo 'blacklist r8169' >> /etc/modprobe.d/blacklist.conf

Now, let's get sundance to load automagically:

echo sundance >> /etc/modules
exit

Now hook up the ethernet cable and reboot. Now run and post:

ifconfig
dmesg | grep -e sundance -e eth

Thanks.

[Oskarm]

Okay I did the blacklist thing then this:

oscar@ubuntu:~$ ifconfig
eth1      Link encap:Ethernet  HWaddr 00:26:18:eb:8f:9e  
          inet6 addr: fe80::226:18ff:feeb:8f9e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:247 errors:0 dropped:0 overruns:0 frame:0
          TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:35804 (35.8 KB)  TX bytes:6346 (6.3 KB)
          Interrupt:16 Base address:0xec00 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  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:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

oscar@ubuntu:~$ dmesg | grep -e sundance -e eth
[    0.252496] i2c-core: driver [aat2870] using legacy suspend method
[    0.252498] i2c-core: driver [aat2870] using legacy resume method
[    1.365623] sundance.c:v1.2 11-Sep-2006 Written by Donald Becker
[    1.365669] sundance 0000:05:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    1.366903] eth0: IC Plus Corporation IP100A FAST Ethernet Adapter at 000000000001ec00, 00:26:18:eb:8f:9e, IRQ 16.
[    1.367470] eth0: MII PHY found at address 0, status 0x7849 advertising 01e1.
[    9.023588] ADDRCONF(NETDEV_UP): eth0: link is not ready
[    9.596669] udevd[386]: renamed network interface eth0 to eth1
[   10.701340] eth1: Link up
[   10.701646] eth1: Link changed: 100Mbps, full duplex

[chili555]

Looking good so far! Are you using Network Manager? Is there any recognition of your Wired Network? Let's see what NM is doing behind the scenes:

sudo cat /var/log/syslog | grep etwork | tail -n15

[Oskarm]

I'm not sure, if I have a Network Manager. I mean when I got to connections at the top of the screen it says Wired Network device not ready.

Anyway, more terminal results:

oscar@ubuntu:~$ sudo cat /var/log/syslog | grep etwork | tail -n15
[sudo] password for oscar: 
Nov 13 18:23:40 ubuntu NetworkManager[730]: <info> Networking is enabled by state file
Nov 13 18:23:40 ubuntu NetworkManager[730]: <warn> failed to allocate link cache: (-10) Operation not supported
Nov 13 18:23:40 ubuntu NetworkManager[730]: <info> (eth1): driver 'sundance' does not support carrier detection.
Nov 13 18:23:40 ubuntu NetworkManager[730]: <error> [1352831020.641210] [nm-device-ethernet.c:456] real_update_permanent_hw_address(): (eth1): unable to read permanent MAC address (error 22)
Nov 13 18:23:40 ubuntu NetworkManager[730]: <info> (eth1): new Ethernet device (driver: 'sundance' ifindex: 2)
Nov 13 18:23:40 ubuntu NetworkManager[730]: <info> (eth1): exported as /org/freedesktop/NetworkManager/Devices/0
Nov 13 18:23:40 ubuntu NetworkManager[730]: <info> (eth1): now managed
Nov 13 18:23:40 ubuntu NetworkManager[730]: <info> (eth1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov 13 18:23:40 ubuntu NetworkManager[730]: <info> (eth1): bringing up device.
Nov 13 18:23:40 ubuntu NetworkManager[730]: nm_netlink_monitor_get_flags_sync: assertion `self != NULL' failed
Nov 13 18:23:40 ubuntu NetworkManager[730]: <warn> (eth1): couldn't get carrier state: (-1) unknown
Nov 13 18:23:40 ubuntu NetworkManager[730]: <info> (eth1): carrier now OFF (device state 20, deferring action for 4 seconds)
Nov 13 18:23:40 ubuntu NetworkManager[730]: <info> (eth1): preparing device.
Nov 13 18:23:40 ubuntu NetworkManager[730]: <info> (eth1): deactivating device (reason 'managed') [2]
Nov 13 18:23:40 ubuntu kernel: [   10.909915] type=1400 audit(1352831020.662:8): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=783 comm="apparmor_parser"
oscar@ubuntu:~$

[chili555]

Let's see:

cat /etc/network/interfaces
nm-tool

And just for the amusement of an old student of networking:

sudo modprobe -rf sundance
sudo modprobe  r8169
dmesg | grep r8169

I ask for the latter so we can see if the Realtek can work.

[Oskarm]

EDIT: Please note, that I have to disconnect the ethernet cable from PC and put it in laptop, so I can actually post this.

I didn't know if r8169 was a typo or not so I did 8168 and 8169.

oscar@ubuntu:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

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

oscar@ubuntu:~$ sudo modprobe -rf sundance
[sudo] password for oscar: 
WARNING: All config files need .conf: /etc/modprobe.d/blacklist.confg, it will be ignored in a future release.
oscar@ubuntu:~$ sudo modprobe r8169
WARNING: All config files need .conf: /etc/modprobe.d/blacklist.confg, it will be ignored in a future release.
FATAL: Module r8169 not found.
oscar@ubuntu:~$ sudo modprobe r8168
WARNING: All config files need .conf: /etc/modprobe.d/blacklist.confg, it will be ignored in a future release.
oscar@ubuntu:~$ dmesg | grep r8169
oscar@ubuntu:~$ 
oscar@ubuntu:~$ dmesg | grep r8168
[    1.359474] r8168 Gigabit Ethernet driver 8.034.00-NAPI loaded
[    1.359506] r8168 0000:04:00.0: enabling device (0000 -> 0003)
[    1.359517] r8168 0000:04:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    1.359530] r8168 0000:04:00.0: PowerManagement capability not found.
[    1.359547] r8168 0000:04:00.0: setting latency timer to 64
[    1.359624] Modules linked in: r8168(O+) pata_jmicron(+) floppy(+)
[    1.359732]  [<ffffffffa002cdf2>] rtl8168_init_one+0x673/0x2c6ff [r8168]
[    1.359814]  [<ffffffffa005f01e>] rtl8168_init_module+0x1e/0x1000 [r8168]
oscar@ubuntu:~$

[chili555]

WARNING: All config files need .conf: /etc/modprobe.d/blacklist.confg, it will be ignored in a future release.

Quite a little problem we have here. Let's unravel this first:

cat /etc/modprobe.d/blacklist.confg

We'll put the contents in the correct place.

It appears you built the newer r8168 module to replace the sometimes stubborn r8169.

[ 1.359474] r8168 Gigabit Ethernet driver 8.034.00-NAPI loaded

The timestamp indicates the r8168 module is being loaded as the computer is booting and therefor isn't effectively blacklisted.