Hi,
I have the sources from
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(L)%3Cbr%3ERTL8168C/RTL8111DP
They compile without any change. Unfortunately, I have no idea how to integrate
them into
the linux tree. Because of the discussion to move to another kernel tree, I
also see no use
in taking any effort into this integration, as an out-of-kernel compile works
pretty well.
Note: I use V8.011.00.
BR,
Carsten.
----- Originalnachricht -----
Von: Maik Brauer <mailinglist@xxxxxxxxxxxxxxx>
Gesendet: Mit, 10.6.2009 13:45
An: Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>
Cc: Carsten Schiers <carsten@xxxxxxxxxx>
Betreff: Re: AW: [Xen-users] XEN 3.4 - Problems with eth0 (link down)
Hi,
I think the card which I've build in, is not well implemented in the
patched r8169.c module.
So the new revisions of this card needs to be updated in this
particular file.
Has sombody expirience with that?
Cheers,
Maik
On Jun 10, 2009, at 12:23 PM, Carsten Schiers wrote:
> Hi,
>
> not 100% sure, but isn't the 8111b the transceiver of an 8168B, for
> which you have to compile your own driver r8168.ko from source
> supplied
> at Realtek? At least I had to do so. r8169.ko which is supplied will
> not
> work.
>
> BR,
> Carsten.
>
> ----- Originalnachricht -----
> Von: Maik Brauer <mailinglist@xxxxxxxxxxxxxxx>
> Gesendet: Mit, 10.6.2009 10:26
> An: Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>
> Betreff: [Xen-users] XEN 3.4 - Problems with eth0 (link down)
>
> Hi,
>
> I've inside my new server a Realtek 8111b and with XEN it displays in
> the Console: "ADDRCONF(NETDEV_UP) eth0: Link down".
> If I boot it via the normal Debian Kernel via Aptitude the Interface
> comes up and a network connection is working.
> Over XEN the Interface is still dead and not responding. The only
> thing is that I can see "ADDRCONF(NETDEV_UP) eth0: link down".
>
> I've made the "make world", "make install", "depmod 2.6.18-8-xen".
> So I did the usual stuff, which I've done for the other 3.2.x
> installations as well, but without any success.
>
> What could might be the reason for this.
> Thanks.
>
> Cheers,
> Maik
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home