I have almost the same mainboard (Asus At3N7A-I) which have same network card. This is what I did to to get it to work: add the following to /etc/driver_aliases: rge "pciex10ec,8168" - then do "touch /reconfigure; init 6"

Thanks a lot, after following you you instructions at least the network interface shows up, and I can access the box via ssh. Currently I'm running some transfer tests (copy some GB over nfs into the box) but unfortunately the rge network interface seems to be unstable. From time to time (some 5 minutes under heavy load) it just stops working, no errors in dmesg. then I have to do

ifconfig rge0 unplumb

ifconfig rge0 plumb

ifconfig rge0 dhcp

and it comes back again.

Hi Christer,

Please let us know if Patrick's suggestion helped.

Hello Anil, Christer gives me the hint and I tried it. I also tried the drivers from -> http://homepage2.nifty.com/mrym3/taiyodo/eng/

• 04/16/2009 gani-2.6.4 and
• rge-6888015-9.tar.gz
• rge.mcast.3.tar.gz

but none of these really fixes the behavior under heavy load. So I decided to wait for a new NCP build.

Is Alpha4 fixes the behavior?

Unfortunately I do not have the hardware availible to verify with NCP3a4. But I'm working on this (to get that M/B back) then I will check back with the newest NCP at that moment. I will report here.

So I tested the ION ATOM330 motherboard with NCP3a4 but unfortunately there is no improvement. NCP installs quite ok (It complains about an unknown PCI ID "pci10de,aa3" It also assign the NIC RTL8111/8168B to the gani driver. But at reboot it does not get the network up and running. the dmesg says:

[ID 217474 kern.info] gani0: ilr 0x0000010a [ID 825931 kern.info] gani0: ddiregsmap_setup failed (ret:-1)

If i could gather any information,and post it here let me know what and how, I would like to act as a debug remote dummy.

Retested with NCP3a5 but still no improvement. the NIC is a PIC-e device, see lspci output...

04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 03)
        Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

Initially this PCI-e ID is assigned to gani2.6.2, but this complains during boottime and does not even attach the NIC

'dmesg | grep gani' says...
Feb 17 04:35:41 nas gani: [ID 217474 kern.info] gani0: ilr 0x0000010a
Feb 17 04:35:41 nas gani: [ID 825931 kern.info] gani0: ddi_regs_map_setup failed (ret:-1)
Feb 17 04:37:09 nas gani: [ID 217474 kern.info] gani0: ilr 0x0000010a
Feb 17 04:37:09 nas gani: [ID 825931 kern.info] gani0: ddi_regs_map_setup failed (ret:-1)


So I tried a bunch of options...


use gani2.6.4 == same result, no NIC attached
use rge-6888015-14 from Murayama-san (http://homepage2.nifty.com/mrym3/taiyodo/rge-6888015-14.tar.gz) == NIC does not attach
use old rge driver rge-6888015-8 this works NIC comes up, but this hangs under heavy network load.


I will keep you informed

hi,

i've the same pb with my msi g31tmp35 with rtl8111D; impossible to get gani0 working.

i wanted to test nexenta to replace opensolaris wich gave me no pb at all with the network (was on ubuntu server before and erased because i try to get a raidz2 / no pb with rtl network).

i hope this bug could be fixed.Let me know if you need any information i could give you...

oups sorry; works fine for me , there was a mistake on network configuration (didn't notice eth stayed at 0:0:0:0:0:0)

Retested under NCP3b1, issue still sustains.

gani driver still not updated?

Hi,

The pci-ids provided by gani are up to date already.(In accordance with the 2.6.4) release from this page.. http://homepage2.nifty.com/mrym3/taiyodo/eng/

There are a few pci-e IDs(pciex10ec,8136) which are currently provided by sunwrge,Hence they are not provided by the third-party driver packages...

But in all the gani driver package is up to date. If your still seeing issues please report back.

Thanks Shampavman.

Hi,

The package has been updated already ,The fix committed. Should be reflected in beta2

Thanks