Custom Query (41 matches)

On my Lenovo ThinkPad? T510, using e1000e-0.2.2.zip, Virtual PC 5.1, running WinXP and using Virtual Switch, cannot get a DHCP address. Then, trying to close VPC causes a system hang. This works better (I get an address, and I can access the internet, and my home LAN) using e1000e-0.1.8.zip, but it still hangs when I close WinXP.

NAT works, but sees a duplicate name on the network, for some reason. I can access the internet, and I can shut down WinXP.

Using the contents of r8169-0.0.4.zip on my Asus M3A78-EM motherboard (the onboard NIC died, so I have a plug in 8169 in it), with quad core Phenom processor, I have major problems with Virtual Switch. Running WinXP under VPC 5.1, I see windows start to run, then it is hung for about a minute while it attempts to get a DHCP address. That seems to have been successful, but no further network activity is possible, and trying to close WinXP hangs the system.

Using r8169-0.0.3.zip I see the same problem. VPC works fine when I use the GENMAC driver, but performance is not as good otherwise.

I am running eCS 2.0 on Intel H55 chipset i3 CPU system with 4GB RAM. The NIC is:

Bus 1 (PCI Express), Device Number 0, Device Function 0

Vendor 10ECh Realtek Semiconductor Co., Ltd. Device 8168h RTL8111/8168B PCI Express Gigabit Ethernet controller Command 0007h (I/O Access, Memory Access, BusMaster?) Status 0010h (Has Capabilities List, Fast Timing) Revision 03h, Header Type 00h, Bus Latency Timer 00h Self test 00h (Self test not supported) Cache line size 32 Bytes (8 DWords) PCI Class Network, type Ethernet Subsystem ID 76361462h Onboard RTL8111b on MSI P965 Platinum Mainboard (Guess Only!) Subsystem Vendor 1462h Micro-Star International Co., Ltd. Address 0 is an I/O Port : D800h Address 1 is not present or not configured! Address 2 is a Memory Address (64-bit, Prefetchable) : FAFFF000h Address 4 is a Memory Address (64-bit, Prefetchable) : FAFF8000h System IRQ 11, INT# A Expansion ROM of 128 KiB decoded by this card, currently disabled New Capabilities List Present:

Power Management Capability, Version 1.2

Supports low power State D1 Supports low power State D2 Supports PME# signalling from mode(s) D0, D1, D2, D3hot, D3cold PME# signalling is currently disabled 3.3v AUX Current required : 375 mA Current Power State : D0 (Device operational, no power saving)

Message Signalled Interrupt Capability

MSI is disabled MSI function can generate 64-bit addresses

PCI Express Capability, Version 2

Device/Port? Type :

PCI Express Endpoint Device

Device Capabilities :

Unsupported Request Severity is Fatal

Device Status :

Correctable Error Detected Unsupported Request Detected AUX Power Detected

Link Capabilities :

Maximum Link speed : 2.5Gb/s Maximum Link Width : x1 Link Port Number : 0

Link Control :

Asynchronous Clocking in Use

Link Status :

Current Link speed : 2.5Gb/s Current Link Width : x1

MSI-X Capability Vital Product Data Capability

VPD Data not present

With the latest beta (0.1.3) I cannot connect to the network. LANTRAN.LOG says:

IBM OS/2 NETBIOS 4.0 Adapter 0 has 123 NCBs, 96 sessions, and 6 names available to NETBIOS applications. NETBIOS 4.0 is loaded and operational. IBM LANVDD is loaded and operational. IBM OS/2 LAN Netbind PRO0021: A general failure occurred when the program tried to bind TCPIP_NIF to R8110_NIF. TCPBEUI: Logical adapter 0 is trying to bind to TCP/IP interface lan0. LT00141: Errors occurred while attempting to initialize TCPBEUI.

I am able to connect using the beta dated 2-14-2011 if I set the NETADDRESS manually (I am typing this using that). I tried using the NIF from that beta with the new OS2 file, but it does not work either.