Just installed rc8a.  The server booted fine and I have access to the console, but I can not get to the web interface.  ifconfig shows that I only have the lo device... no eth1 device.  I'm not sure right now how to determine my network card model (it is on-board), but it does appear that rc8a doesn't support my network card.  I was running rc4, I'll go back to that.

On the console of RC4 try "lsmod", propably there is a line starting with r8168.

If so, welcome to the club

 

 

http://lime-technology.com/forum/index.php?topic=22605.0

Check you have RC8a and not the original RC8

 

There was a R8168 issue with the original package.  The a version resolved it for myself and a few others.

The file I downloaded was "unRAID Server 5.0-rc8a AiO.zip".  Pretty sure I've got rc8a. 

 

I tried lsmod, but no such line indicating r8186.  I can keep rc8a running a few days longer if there are any other tests that someone can suggest.  Maybe I can provide helpful information that might result in improvements that help others.  Let me know.

I'd re-download and copy it to your thumbdrive just to be safe.  Everyone that had the error is now reporting it's fixed.

 

If that doesn't fix it then I have no idea.

I rolled back to 5.0-rc4 and I now have network again.  Looking at my syslog I see the following:

 

Sep 19 13:55:25 UNRAID kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
Sep 19 13:55:25 UNRAID kernel: r8169 0000:02:07.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
Sep 19 13:55:25 UNRAID kernel: r8169 0000:02:07.0: (unregistered net_device): no PCI Express capability
Sep 19 13:55:25 UNRAID kernel: r8169 0000:02:07.0: eth0: RTL8110s at 0xf8466000, 00:14:c1:4c:38:6f, XID 04000000 IRQ 23

 

The release notes say that the r8169 driver was removed and replaced with r8168 driver.  Should I expect the r8168 driver to work with my r8169 card?  Or, has my NIC been depreciated from unRaid?

 

I saved the syslog from my attempt to boot into rc8a.  In that log I see no attempt to load a network driver at all.  (see attached).

20120919_syslog.txt

This is also a concern I have. I have one nic that requires r8169 and would like to know how to add that driver to the rc8a build.

You guys are not doing anything wrong rc8a does not seem to be working with R8169 nics. This has be a long battle for unRAID with realtek nics. He has not official stated about not supporting either and has made changes many times. So unfortunately you have to wait for the next RC or possible a RC8b...

 

Try my build

https://dl.dropbox.com/u/49442039/unraid-rc8a-media-tree-2.zip

 

im add 8169 driver

Let me know if work - thanks

Try my build

https://dl.dropbox.com/u/49442039/unraid-rc8a-media-tree-2.zip

 

im add 8169 driver

Let me know if work - thanks

hey,

your build works great! i managed to get my 8169 up and running and i'm on 5rc8a for the first time

good to hear that everything works, im in kernel Enable realtek 8169 module

agreed, both nics working well.

good to hear that everything works, im in kernel Enable realtek 8169 module

 

Works great, thanks!

For the record, I also installed this to support a Netis AD-1102 (PCI Gigabyte Ethernet Card, roughly $12) which uses the Realtek RTL8169SC controller.

Worked for me,

 

thanks a bundle

Also had issues with nic drivers in all builds after rc4, but piotrasd version worked for me.

I have downloaded and re-downloaded 5rc8a AIO and cannot get it to show the driver in lsmod, I have used the modify version supplied by piotrasd that version is working for me. Thanks for sharing!

Just to add my name to the list...  I'm another one hit by this NIC incompatibility. 

 

Thanks for the modded version piotrasd.  I will be happier when we can get the NIC supported by an official build though.

 

[EDIT] I can confirm piotrasd's build does work for me too

 

A little late here as well, but the modded kernel is working perfectly for me.  Thanks piotrasd!

I have just experienced a problem related to this version.  I have a KVM switch, and on switching to my unraid box, the mouse and keyboard are re-detected.  When that occurred, it seems that there is an irq problem:

 

Jan 13 16:42:57 Tower kernel: usb 1-1.3: USB disconnect, device number 4
Jan 13 16:42:58 Tower kernel: usb 1-1.4: USB disconnect, device number 5
Jan 13 16:42:59 Tower kernel: irq 16: nobody cared (try booting with the "irqpoll" option)
Jan 13 16:42:59 Tower kernel: Pid: 0, comm: swapper/1 Not tainted 3.4.11-unRAID#1
Jan 13 16:42:59 Tower kernel: Call Trace:
Jan 13 16:42:59 Tower kernel:  [<c1052256>] __report_bad_irq+0x1f/0x95
Jan 13 16:42:59 Tower kernel:  [<c105240e>] note_interrupt+0x142/0x190
Jan 13 16:42:59 Tower kernel:  [<c1050b9a>] handle_irq_event_percpu+0xef/0x102
Jan 13 16:42:59 Tower kernel:  [<c1050bd2>] handle_irq_event+0x25/0x3c
Jan 13 16:42:59 Tower kernel:  [<c10529c3>] ? handle_simple_irq+0x4f/0x4f
Jan 13 16:42:59 Tower kernel:  [<c1052a20>] handle_fasteoi_irq+0x5d/0x8c
Jan 13 16:42:59 Tower kernel:  <IRQ>  [<c10034b1>] ? do_IRQ+0x36/0x91
Jan 13 16:42:59 Tower kernel:  [<c1324169>] ? common_interrupt+0x29/0x30
Jan 13 16:42:59 Tower kernel:  [<c104007b>] ? load_balance+0x181/0xf31
Jan 13 16:42:59 Tower kernel:  [<c11ecece>] ? acpi_idle_enter_bm+0x23e/0x276
Jan 13 16:42:59 Tower kernel:  [<c1285e37>] ? cpuidle_enter+0xe/0x12
Jan 13 16:42:59 Tower kernel:  [<c1286329>] ? cpuidle_idle_call+0x56/0xa6
Jan 13 16:42:59 Tower kernel:  [<c1008586>] ? cpu_idle+0x41/0x65
Jan 13 16:42:59 Tower kernel:  [<c131e893>] ? start_secondary+0x192/0x197
Jan 13 16:42:59 Tower kernel: handlers:
Jan 13 16:42:59 Tower kernel: [<c1254c5b>] usb_hcd_irq
Jan 13 16:42:59 Tower kernel: [<f8507b70>] rtl8169_interrupt
Jan 13 16:42:59 Tower kernel: Disabling IRQ #16

 

After this error, my network speeds become horrible.  ping times are huge, and the box is unusable for moving any amount of data to/from it.

 

Has anyone else seen this, or have an idea how to fix it?  I found this thread on another board:  http://forums.opensuse.org/english/get-technical-help-here/hardware/473848-disabling-irq-16-a.html

 

Try rc10.