AB9 Pro - Wake on LAN (WOL) enable


Recommended Posts

Has anyone using Abit AB9 Pro motherboard been successful at enabling the WOL feature? If so, can you please share your solution. I am running unRaid 4.3.3.

 

I have tried everything I can imagine. tried: ethtool -s eth0 wol g

 

I get something similar to (copied from another thread):

root@Tower:/boot# ethtool eth0

Settings for eth0:

        Supported ports: [ TP ]

        Supported link modes:  10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supports auto-negotiation: Yes

        Advertised link modes:  10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Advertised auto-negotiation: Yes

        Speed: 1000Mb/s

        Duplex: Full

        Port: Twisted Pair

        PHYAD: 1

        Transceiver: internal

        Auto-negotiation: on

        Supports Wake-on: umbg

        Wake-on: g

        Current message level: 0x00000007 (7)

        Link detected: yes

 

WOL in BIOS is enabled. I have setup other PCs using XP and Vista with no problem, but this system keeps puzzling me. Any help is appreciated!

 

 

Link to comment
  • 9 months later...

OK. Read lot's about different baords and ended up buying one of these, Great, Lot's of options, and it was already @ Bios 22 (The latest from Abit)

So what's stopping me at the moment.. Wakr On Lan (wol).

It will work from S3 if the p option is set but nothing else i.e. not the default umbg, or any of them on their own.

 

So

ethtool -s eth0 wol p

but

ethtool -s eth0 wol umbg

does not

 

I'm using

echo 3 > /proc/acpi/sleep

in telnet to force a sleep and then perform all sorts of magic packet sending etc from windows (XP SP3 -> Win 7) to attempt to wake it  up.. nothing

 

My go script looks like this :

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &


# For an often large improvement in read performance
sleep 30; blockdev --setra 2048 /dev/md*

# Inform the Linux kernel that you want it to put the highest priority on keeping directory entries in the cache, and avoid flushing them out
/boot/scripts/cache_dirs  -d  5  -m  3  -M  5  -w


# start the UnMENU server
/boot/unmenu/uu


# Force via cron monthly_parity_check
fromdos < /boot/scripts/monthly_parity_check.sh | sh 


# p-    Wake on phy activity 
# u-    Wake on unicast messages 
# m-    Wake on multicast messages 
# b-    Wake on broadcast messages 
# a-    Wake on ARP 
# g-    Wake on MagicPacket(tm) 
# disable all wakeup
ethtool -s eth0 wol d
sleep 2;
#enable wakeup
ethtool -s eth0 wol umbg
# ethtool -s eth0 wol g

# Move to the host and intialise PowerDown to the ctrl+Alt+Del
fromdos < /boot/scripts/S30-inittab-powerdown | sh 


# Have it go to sleep if it has not been used for a while
cd /boot/scripts
fromdos < /boot/scripts/goto_sleep.sh | at now + 1 minute


# Startup FEMUR Listener
nohup awk -W re-interval -f /boot/femur/listen.awk >/dev/nul 2>&1 &

 

 

Link to comment

I've done little more playing around "in the bios" fro this M/B and found the following things:

 

Lan 2 in the BIOS is actually identified as etho in telnet unraid;

 

Diabling all of the Wkae events but the USB and not have anything but the USB unraid stick in restarts the m/b as soon as it goes into S3;

 

PCI Express, or PCI VGA cards make no difference.

 

Still got lots of other options try, But now I have disable Lan 1 in the Bios as UnRaid will never identify it as useable anyway.

 

Link to comment

The Story Continues, (Just in case anyone is wondering what steps are being taken...)

Installed XP last night. Woo hoo..

Set all the setting for magic packet waje etc. in the drivers (Via Device Manager) to allow device to bring out of sleep.

Instigated a Sleep state (Press power button and it went into standby)

Went to another XP box and sent the same magic packet I was sending for the UnRaid OS, and hey presto it woke up..

 

Now to test trying to find the setting(s) in XP to wake up for any directed packet (Like just browsing to known share or even sending a ping) and then it'll be back here to report progress..

 

So in short XP does allow more control over nics than the driver in slackware under UnRaid..

Link to comment

XP Story:

Downloaded the latest Realtek 8168/8111 driver and set the appropriate settings for allow Wake-On-Lan

 

1) Sent it to sleep.

2) Browsed via explorer to the share

3) Bingo.. Machine woke up.  ::)

 

Did a bit more reading and it turns out that XP might reset the WOL settings if a full shutdown is done

http://ubuntuforums.org/showthread.php?t=538448

 

So Back into XP and instigate a sleep, pull H/D and plugin in UnRaid USB

That wakes up the M/B As it sees a USB event and then it start to load UnRaid..

 

Allow Unraid to finish and then call the echo 3 > etc

Goto Client XP box and attempt to browse to the flash share..

Nothing  :-\

 

So Back to square one..

So More reading, And it turns out that early kernels of ubuntu had problems with these relatek chips, So could it be that the slackware also has these problems ? Anyone ?

 

So back to ubuntu..

Found this which suggests powerdown, and then removing the cable

http://ubuntuforums.org/showthread.php?t=538448

Nope still no dice

 

So found this http://ubuntuforums.org/showthread.php?t=1032411

and ran

dmesg | grep eth
Driver 'sd' needs updating - please use bus_type methods
eth0: RTL8168b/8111b at 0xf823c000, 00:50:8d:98:0b:b6, XID 38000000 IRQ 29
r8169: eth0: link up
r8169: eth0: link up
r8169: eth0: link up

Me thinks a clue has been revealed, But what do I do with it ?

 

Link to comment

Seems like RealTek have updated their Unix drivers

http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=5&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false#RTL8111B/RTL8168B/RTL8111/RTL8168%3Cbr%3ERTL8111C/RTL8111CP/RTL8111D%28L%29%3Cbr%3ERTL8168C/RTL8111DP.

Latest is :

 LINUX driver for kernel 2.6.x and 2.4.x (Support x86 and x64)
8.014.00	2009/8/31	40k	GO	GO	GO	

Anyone now have the know how to compile these and then to insert them into unRaid latest beta so that I can test? 8)

 

 

Link to comment

If you look inside the file you directed us to, there is a README file that provides directions on doing so.

 


<Linux device driver for Realtek Ethernet controllers>

 

This is the Linux device driver released for RealTek RTL8168B/8111B, RTL8168C/8111C, RTL8168CP/8111CP, RTL8168D/8111D Gigabit Ethernet controllers with PCI-Express interface.

 

<Requirements>

 

- Kernel source tree (supported Linux kernel 2.6.x and 2.4.x)

- For linux kernel 2.4.x, this driver supports 2.4.20 and latter.

- Compiler/binutils for kernel compilation

 

<Quick install with proper kernel settings>

Check whether the built-in driver, r8169.ko (or r8169.o for kernel 2.4.x), is installed.

# lsmod | grep r8169

 

If it is installed, please remove it.

# rmmod r8169

note: If the built-in driver cannot removed by rmmod, please edit /etc/modprobe.conf and comment 'alias eth0 r8169'. Then, remmove it again or reboot your computer.

 

Unpack the tarball :

# tar vjxf r8168-8.aaa.bb.tar.bz2

 

Change to the directory:

# cd r8168-8.aaa.bb

 

If you are running the target kernel, then you should be able to do :

 

# make clean modules (as root or with sudo)

# make install

# depmod -a

# modprobe r8168

 

You can check whether the driver is loaded by using following commands.

 

# lsmod | grep r8168

# ifconfig -a

 

If there is a device name, ethX, shown on the monitor, the linux

driver is loaded. Then, you can use the following command to activate

the ethX.

 

# ifconfig ethX up

 

,where X=0,1,2,...

 

<Set the network related information>

1. Set manually

a. Set the IP address of your machine.

 

# ifconfig ethX "the IP address of your machine"

 

b. Set the IP address of DNS.

 

  Insert the following configuration in /etc/resolv.conf.

 

nameserver "the IP address of DNS"

 

c. Set the IP address of gateway.

 

# route add default gw "the IP address of gateway"

 

2. Set by doing configurations in /etc/sysconfig/network-scripts

  /ifcfg-ethX for Redhat and Fedora, or /etc/sysconfig/network

  /ifcfg-ethX for SuSE. There are two examples to set network

  configurations.

 

a. Fix IP address:

DEVICE=eth0

BOOTPROTO=static

ONBOOT=yes

TYPE=ethernet

NETMASK=255.255.255.0

IPADDR=192.168.1.1

GATEWAY=192.168.1.254

BROADCAST=192.168.1.255

 

b. DHCP:

DEVICE=eth0

BOOTPROTO=dhcp

ONBOOT=yes

 

<Modify the MAC address>

There are two ways to modify the MAC address of the NIC.

1. Use ifconfig:

 

# ifconfig ethX hw ether YY:YY:YY:YY:YY:YY

 

  ,where X is the device number assigned by Linux kernel, and

  YY:YY:YY:YY:YY:YY is the MAC address assigned by the user.

 

2. Use ip:

 

# ip link set ethX address YY:YY:YY:YY:YY:YY

 

  ,where X is the device number assigned by Linux kernel, and

  YY:YY:YY:YY:YY:YY is the MAC address assigned by the user.

 

<Force Link Status>

 

1. Force the link status when insert the driver.

 

  If the user is in the path ~/r8168, the link status can be forced

  to one of the 5 modes as following command.

 

# insmod ./src/r8168.ko speed=SPEED_MODE duplex=DUPLEX_MODE autoneg=NWAY_OPTION

 

,where

SPEED_MODE = 1000 for 1000Mbps

= 100 for 100Mbps

= 10 for 10Mbps

DUPLEX_MODE = 0 for half-duplex

= 1 for full-duplex

NWAY_OPTION = 0 for auto-negotiation off (true force)

= 1 for auto-negotiation on (nway force)

For example:

 

# insmod ./src/r8168.ko speed=100 duplex=0 autoneg=1

 

will force PHY to operate in 100Mpbs Half-duplex(nway force).

 

2. Force the link status by using ethtool.

a. Insert the driver first.

b. Make sure that ethtool exists in /sbin.

c. Force the link status as the following command.

 

# ethtool -s ethX speed SPEED_MODE duplex DUPLEX_MODE autoneg NWAY_OPTION

 

,where

SPEED_MODE = 1000 for 1000Mbps

= 100 for 100Mbps

= 10 for 10Mbps

DUPLEX_MODE = half for half-duplex

= full for full-duplex

NWAY_OPTION = off for auto-negotiation off (true force)

= on for auto-negotiation on (nway force)

 

For example:

 

# ethtool -s eth0 speed 100 duplex full autoneg on

 

will force PHY to operate in 100Mpbs Full-duplex(nway force).

 

<Jumbo Frame>

Transmitting Jumbo Frames, whose packet size is bigger than 1500 bytes, please change mtu by the following command.

 

# ifconfig ethX mtu MTU

 

, where X=0,1,2,..., and MTU is configured by user.

 

RTL8168B/8111B supports Jumbo Frame size up to 4 kBytes.

RTL8168C/8111C and RTL8168CP/8111CP support Jumbo Frame size up to 6 kBytes.

RTL8168D/8111D supports Jumbo Frame size up to 9 kBytes.

 

Link to comment

Thanks for the readme dump (It was late but suspected it's contents), But that's my point, I do not have the capability to call make, and the other things.

They are not in the UnRaid distro.

 

So if someone has set up the necessary bit's to perform a make then please do, and return the driver so that I call the install parts and tests.

 

I'm sure there are lot's of RealTek 81## chipset based cards out there (They do have quite a lot of the market for PCI cards as well, as they are also [at least] behind belkin and compaq PCI cards).

 

So Again, If someone has the UnRaid with make capabilites then please perform the steps and I'll Give them a test..

 

Cheers

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.