search for: rhine

Hi, does anyone have any idea whether VIA VT6102 "Rhine II" and Realtek RTL 8100 Ethernet chips are supported by FreeBSD? The hardware list for supported chips does list 'VT86C100A "Rhine II"' but according to VIA website VT86C100A is actually just "Rhine" and it is obviously not the same chip. (The 'VT3043 "...

It should be noted that a symlink to the built llvm-config will return the paths for the system llvm instead of the built llvm; it's fine on OS X though. Some differences in realpath?

...ments make[2]: *** [bin/forcedeth.o] error 1 make[2]: leaving directory '/working-directory/gpxe/src' make[1]: *** [src/bin/undionly.kpxe] error 2 make[1]: leaving directory '/working-directory/gpxe' make: *** [all] error 2 [...] cc1: warnings being treated as errors drivers/net/via-rhine.c: In function ?rhine_probe1?: drivers/net/via-rhine.c:1011: error: format not a string literal and no format arguments make[2]: *** [bin/via-rhine.o] error 1 make[2]: leaving directory '/working-directory/gpxe/src' make[1]: *** [src/bin/undionly.kpxe] error 2 make[1]: leaving directory ...

Hello list, I've been using PXE Boot for quite some time now and it has been working without any problems. I'm using a Biostar M7VIZ mainboard with a VIA KM400 chipset, and VIA-Rhine VT6102 NIC. Yesterday I upgrade the Kernel on my net-boot machine from 2.4.24 to 2.6.12. When I power on the machine it boots up normally. However, when I reboot the machine, the mainboards PXE-ROM only displays "PXE-M0F: Exiting Intel PXE ROM". It does not even try to retrieve anythin...

So I just finished doing a fresh install of CentOS 6.3. The machine has three ethernet ports in it: one on the motherboard (VIA Rhine), and two add-on cards, an Intel Pro100 and an old SMC1255TX. When CentOS comes up, this is what I see in the dmesg output: # dmesg | grep eth e100 0000:00:08.0: eth0: addr 0xf6043000, irq 16, MAC addr 00:02:b3:be:02:87 eth1: ADMtek Comet rev 17 at MMIO 0xf6040000, 00:4c:69:6e:75:...

Apologies if this is posted on the wrong list, but when I try to get pci passthrough to work on a Wheezy Xen box I get NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out and then not much else works at all. The same hardware works just fine with Xen and Squeeze. It seemed to me that the problem I am seeing is very similar to https://bugzilla.kernel.org/show_bug.cgi?id=15833 but I have had no response to my posting on...

Hello, I have a problem with the latency of the packets passing a Linux router, and I thought perhaps you could put some light on it. It''s quite simple. I have one ADSL connection, and a LAN. The gateway is the Linux machine or a Windows XP machine. When the wXP is routing, for a host inside the LAN, the latency of, for example, the Counter Strike game to a given server is around 20 to 30

Hi. I am use a linux bridge with two via-rhine ethernet cards. I have aprox. the 3% of packet loss in the bridge. This is normal? Is it a possible problem of the via-rhine cards? Is best change the NICs for 3COM? Sincerely Thanks. Daniel.

Hi all, I've recently upgraded a system from CentOS 4.4 to CentOS5, and now when the system boots, the r8169 ethernet card doesn't come up. After the boot sequence, if I type "ifup eth1 | ifup eth1.10 | ifup eth1.203" then the adapter starts up ok. It seems to be something with the boot sequence it loads the ethernet adapters a different way around (ie 4.4 eth0 is now

...IDE" (which disables "hardware" RAID but not the SATA but itself). The install routine for Centos, however, does not seem to recognise that the drives are there (or even that the VIA bridge exists via auto search); if I try to manually select it I'm told it found a VIA VT86c100A Rhine-II PCI (via-rhine). Setting to AHCI does not seem to have an effect. I was hoping to use software RAID, and so didn't want to enable RAID on the motherboard. Does anyone have any suggestions as to how to either nudge the installation, or configure the hardware, to find the SATA drives so I c...

...s-4.3 4.3.0-3+b1 amd64 ii xen-utils-common 4.3.0-3 all ii xenstore-utils 4.3.0-3+b1 amd64 lspci -k . . . 03:00.0 Ethernet controller: VIA Technologies, Inc. \ VT6105/VT6106S [Rhine-III] (rev 86) Subsystem: D-Link System Inc DFE-530TX rev C Kernel driver in use: via-rhine 03:01.0 Ethernet controller: VIA Technologies, Inc. \ VT6105/VT6106S [Rhine-III] (rev 86) Subsystem: D-Link System Inc DFE-530TX rev C Ker...

...#0: Thu Apr 17 03:52:52 CEST 2003 erikrana@<hostname.tld> :/usr/obj/usr/src/sys/fw_48 i386 Anyway in the LINT file there are some text about the vr(4) driver. > # The `vr' device provides support for various fast ethernet adapters > # based on the VIA Technologies VT3043 `Rhine I' and VT86C100A `Rhine II' > # chips, including the D-Link DFE530TX (see 'rl' for DFE530TX+), the > Hawking # Technologies PN102TX, and the AOpen/Acer ALN-320. I think this text should reflect that it also supports the VT86C105/VT86C105M ``Rhine III'' since it doe...

my d-link ethernet pci card not detected in centos 7 even after i have installed kmod forcedth driver.. output of lscpi -nn 01:07.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6105/VT6106S [Rhine-III] [1106:3106] (rev 8b) pl help with regards.. sathish

Currently xcs is run by xend in xen-unstable by simply making it a child process. If you launch xend from an ssh session, the session won''t exit because the xcs still is connected to it''s controlling terminal. xcs should daemonize itself to prevent this from happening. This patch does that along with making the domain id => port mapping dynamically allocated. Regards, --

Hi Yum has just updated 5 of my Linux boxes running CentOS 4.3 to the 2.6.9-42 kernel. All is well on four of the boxes, but on the fifth the network card (eth0) will not work. I've downgraded the kernel to the previous version and the network card works fine again. I've tried removing and re-installing the new kernel, but the network card won't work with it. The details of the

Today I updated several servers running CentOS 4.3, and got the new 2.6.9-42 kernel. One of the machines serves as our firewall. After rebooting I lost all forwarding thru the machine. I reverted back to the 2.6.9-34 kernel and connectivity returned. During the few minutes that the new kernel was running I checked that the routing table looked OK, and with tcpdump I saw that indeed no traffic

I'm getting problems with my bridge (linux 2.6.9, eth0 = via-rhine, eth1 = 8139too). The problem is that eth1 links up and down intermitently (between 1-2 minutes). What can i do? Thanks

...lient udp/2070: Option acknowledgement, tsize=10832 Client udp/2070 to Server udp/32872: Error code, not defined (0), TFTP aborted This is with tftpd-hpa. I've tried with atftpd, and I get much the same conversation -- an error code immediately after an option ack. The hardware is a VIA-Rhine II (VT6102), claiming "Intel UNDI, PXE-2.0 (build 082)" when the PEX boot sequence starts. Is this a duff PXE implementation, or something stupid I've done? Thanks, Hugo. PS. This mailing list seems to have "issues" with PGP/MIME signed emails. Is that the case? --...

Hello everybody! I have some problems with my Astersk. I have an analogical OpenVox card and A Billion ISDN card (with mISDN). I load the modules with modprobe zaptel and modprobe wctdm. When I run ztcfg -vv I have this: Zaptel Configuration ====================== Channel map: Channel 01: FXS Kewlstart (Default) (Slaves: 01) 1 channels configured. ZT_CHANCONFIG failed on channel 1: No

Hi, When I boot my dedicated server from netinstall cd, I see: http://img501.imageshack.us/img501/3828/kernelpaniczm7.jpg System: Intel(R) Celeron(R) CPU 2.60GHz - Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] - Host bridge: VIA Technologies, Inc. P4M266 Host Bridge - IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE - ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge - PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] - USB Controller: VIA T...