building r8168-ck for linux-ck => 3.3

mynis01 · 2012-04-07 19:49:13

I tried editing the pkgbuild and install files to use the proper directories and get rid of the linux-ck <= 3.3 dependency and it seemed like all was going well until I got some ambiguous errors:

make -C src/ clean
make[1]: Entering directory `/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src'
make -C /lib/modules/3.3.1-2-ck/build SUBDIRS=/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src clean
make[2]: Entering directory `/usr/src/linux-3.3.1-2-ck'
  CLEAN   /tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/.tmp_versions
make[2]: Leaving directory `/usr/src/linux-3.3.1-2-ck'
make[1]: Leaving directory `/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src'
make -C src/ modules
make[1]: Entering directory `/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src'
make -C /lib/modules/3.3.1-2-ck/build SUBDIRS=/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src modules
make[2]: Entering directory `/usr/src/linux-3.3.1-2-ck'
  CC [M]  /tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.o
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2235:2: error: unknown field ‘get_rx_csum’ specified in initializer
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2235:2: warning: initialization from incompatible pointer type [enabled by default]
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2235:2: warning: (near initialization for ‘rtl8168_ethtool_ops.nway_reset’) [enabled by default]
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2236:2: error: unknown field ‘set_rx_csum’ specified in initializer
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2236:2: warning: initialization from incompatible pointer type [enabled by default]
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2236:2: warning: (near initialization for ‘rtl8168_ethtool_ops.get_link’) [enabled by default]
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2237:2: error: unknown field ‘get_tx_csum’ specified in initializer
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2237:2: warning: initialization from incompatible pointer type [enabled by default]
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2237:2: warning: (near initialization for ‘rtl8168_ethtool_ops.get_eeprom_len’) [enabled by default]
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2238:2: error: unknown field ‘set_tx_csum’ specified in initializer
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2238:2: warning: initialization from incompatible pointer type [enabled by default]
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2238:2: warning: (near initialization for ‘rtl8168_ethtool_ops.get_eeprom’) [enabled by default]
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2239:2: error: unknown field ‘get_sg’ specified in initializer
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2239:2: warning: initialization from incompatible pointer type [enabled by default]
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2239:2: warning: (near initialization for ‘rtl8168_ethtool_ops.set_eeprom’) [enabled by default]
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2240:2: error: unknown field ‘set_sg’ specified in initializer
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2240:2: warning: initialization from incompatible pointer type [enabled by default]
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2240:2: warning: (near initialization for ‘rtl8168_ethtool_ops.get_coalesce’) [enabled by default]
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2242:2: error: unknown field ‘get_tso’ specified in initializer
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2242:14: error: ‘ethtool_op_get_tso’ undeclared here (not in a function)
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2243:2: error: unknown field ‘set_tso’ specified in initializer
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:2243:14: error: ‘ethtool_op_set_tso’ undeclared here (not in a function)
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:12811:2: warning: initialization from incompatible pointer type [enabled by default]
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:12811:2: warning: (near initialization for ‘rtl8168_netdev_ops.ndo_fix_features’) [enabled by default]
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:12812:2: warning: initialization from incompatible pointer type [enabled by default]
/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.c:12812:2: warning: (near initialization for ‘rtl8168_netdev_ops.ndo_set_features’) [enabled by default]
make[3]: *** [/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src/r8168_n.o] Error 1
make[2]: *** [_module_/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src] Error 2
make[2]: Leaving directory `/usr/src/linux-3.3.1-2-ck'
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/tmp/packerbuild-0/r8168-ck/r8168-ck/src/r8168-8.028.00/src'
make: *** [modules] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
The build failed.

Is there a way to fix this? Or does the current r8168 driver just not support linux 3.3 yet?

graysky · 2012-04-07 19:54:21

Doesn't appear that the maintainer has updated it for 3.3 yet. Could be that upstream is to blame.

Last edited by graysky (2012-04-07 19:55:55)

mynis01 · 2012-04-07 20:04:25

The driver on the reakltek page hasn't been updated since January, I was hoping there was a way to coax it into building. I was reading through the "make" man pages and other various documentation earlier to no avail to see what things like this mean:

make[1]: *** [modules] Error 2

graysky · 2012-04-07 20:05:01

http://www.archlinux.org/packages/?sort … =&limit=50

The official Arch packages are not updated yet which leads me to think that upstream is to blame.

graysky · 2012-04-08 10:48:09

Temp fix: https://bbs.archlinux.org/viewtopic.php?id=139219

mynis01 · 2012-04-08 17:35:26

Thanks for the suggestion but I'd rather just deal with using r8169 or the stock arch kernel for the time being rather than switch to ndiswrapper. Or are you suggesting similar patching techniques could work for r8168? Either way, I haven't had any packets drop or anything yet using r8169 instead of the proper r8168 driver, so it's really not that important I guess.

Last edited by mynis01 (2012-04-08 17:41:07)

xzy3186 · 2012-04-09 02:28:35

mynis01 wrote:

Thanks for the suggestion but I'd rather just deal with using r8169 or the stock arch kernel for the time being rather than switch to ndiswrapper. Or are you suggesting similar patching techniques could work for r8168? Either way, I haven't had any packets drop or anything yet using r8169 instead of the proper r8168 driver, so it's really not that important I guess.

Today the r8168 package in official repository has been updated for linux-3.3. However, I have some problems to run with the patch. Indeed I can makepkg with the linux-3.3 patch without error under linux-ck-3.3 but I can not connect to Ethernet after installing the driver (continuously getting ip address but no result). Please wait for a while until I find a solution

mynis01 · 2012-04-09 19:58:15

I noticed that there is a newer driver version listed on the Realtek downloads page than there is in the official repos, version 8.029.00. It says it went up 03/29/2012 but I could have sworn it wasn't up there a couple days ago.

Edit: Got the file and tried building it, still got the same errors.

Last edited by mynis01 (2012-04-09 20:07:40)

mynis01 · 2012-04-14 11:46:18

I got r8168-8.029.00 working with 3.3.2-1-ck. The trick is to comment out lines 2232-2240 in the file src/r8168_n.c. Not sure if this affects performance but it's running well for me so far.

graysky · 2012-04-14 11:52:29

You should alert the package maintainer so others can use the driver (if you haven't already).

mynis01 · 2012-04-15 05:08:19

I alerted the package maintainer and he's apparently not achieving the same results as I am, so I'm going to post some information for anyone interested in building this for themselves.

People report a wide range of problems when using this fix in conjunction with gnome network manager, including high CPU usage and not being able to get an address from a DHCP server. I'm using wicd-curses, and I have a static IP assigned, no problems here.

I have ipv6 disabled. I did this by adding ipv6.disable=1 to the append line in syslinux.cfg

I didn't bother making a pkgbuild. I just downloaded the driver from the Realtek downloads page and ran their autorun.sh

The modified file I created can be viewed here.

The end result, is an i5 desktop system that not only has fully functional networking, but is faster than any machine I've ever used before in my life! linux-3.3-ck on a SSD is crazy fast!

Last edited by mynis01 (2012-04-15 05:13:43)

pivonroll · 2012-04-22 09:34:02

Hi all, I have downloaded latest stable .iso installation of Arch and I tried to build the driver for Realtek 8168, but when I start ./autorun.sh I get an error: no make rule for clean in /lib/modules/3.0-ARCH/build. After that I tried copying src from the Realtek driver to /lib/modules/3.0-ARCH/build but after that system just hangs after a couple of minutes.
After that I tried to run: make clean modules, but the only message I see is:
make -C /lib/modules/3.0-ARCH/build /root/realtek clean

and this message is repeated on and on and on and on and on, until system runs out of memory and freezes.

Can anyone help me please. Arch is i686.

This post is sent from Windows 7

Last edited by pivonroll (2012-04-22 09:35:45)

Arch Linux

#1 2012-04-07 19:49:13

building r8168-ck for linux-ck => 3.3

#2 2012-04-07 19:54:21

Re: building r8168-ck for linux-ck => 3.3

#3 2012-04-07 20:04:25

Re: building r8168-ck for linux-ck => 3.3

#4 2012-04-07 20:05:01

Re: building r8168-ck for linux-ck => 3.3

#5 2012-04-08 10:48:09

Re: building r8168-ck for linux-ck => 3.3

#6 2012-04-08 17:35:26

Re: building r8168-ck for linux-ck => 3.3

#7 2012-04-09 02:28:35

Re: building r8168-ck for linux-ck => 3.3

#8 2012-04-09 19:58:15

Re: building r8168-ck for linux-ck => 3.3

#9 2012-04-14 11:46:18

Re: building r8168-ck for linux-ck => 3.3

#10 2012-04-14 11:52:29

Re: building r8168-ck for linux-ck => 3.3

#11 2012-04-15 05:08:19

Re: building r8168-ck for linux-ck => 3.3

#12 2012-04-22 09:34:02

Re: building r8168-ck for linux-ck => 3.3

Board footer