search for: 8139

I have a CentOS 5.8 box that is dropping packets (just from ping). The network is 8139 RTL-8139/8139C/8139C+ Rev 10 Adding the parameters "pci=noacpi acpi=off " has helped but it still happens. Is there something else that helps the network not drop packets? Thanks, jerry

Hallo, rid, Du meintest am 13.06.13: > hi, realtek 8139 \ 8100sc NICs can not be used PXELINUX 5.0 -> > 6.0-pre4 version boot, please verify. tested with 6.0-pre4 and an "etherboot" disk for realtek-8139: no problem. Viele Gruesse! Helmut

Completely agree. I used to have 8139c cards in my home machines, on a switched 100mbit network, including a Dual P3 server that I run 4 x 80G drives with a HPT454 RAID5 array (software I know, but the dual P3 copes admirably), both the server and my main desktop (dual Athlon MP 2600) were getting to the point of being unusable when su...

Hi, Last friday I changed the NIC in two of our Samba servers from a 3com 905b (100mb) to a 3com 2000T (1000mb) to take advantage of our new switch which supports gigabit. One of the workstations (XP SP1, with all subsequent patches and hotfixes and with an onboard Realtek 8139) then started to have problems with the two Samba servers with the new NIC's. It could see the network neighbourhood alright, it could browse but when opening a file a time-out or error occurred. In the logs lines like this: syslog.1:May 15 17:00:56 kylie smbd[27625]: [2004/05/15 17:00:56, 0]...

Hi everyone, Please help, I have built a new server and installed puppet (2.6.17) running on RHEL 6.3. It seems that it is not listening on port 8139. iptables -L: Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination /etc/pup...

hi, realtek 8139 \ 8100sc NICs can not be used PXELINUX 5.0 -> 6.0-pre4 version boot, please verify.

hi, Problem seems to be solved. I could kick myself for not trying the obvious first: updating the drivers for the Realtek card by downloading the latest from their site: http://www.realtek.com.tw/downloads/downloads1-3.aspx?series=16&Software=True The problem seems to be solved. thanks for the fast response. cheers, Bart van Dicjk

...p 00007000 08:06 8317 /lib/x86_64-linux-gnu/libnss_compat-2.13.so 7f3591829000-7f359182a000 rw-p 00008000 08:06 8317 /lib/x86_64-linux-gnu/libnss_compat-2.13.so 7f359182a000-7f3591d21000 r--p 00000000 08:07 590549 /usr/lib/locale/locale-archive 7f3591d21000-7f3591d61000 r-xp 00000000 08:06 8139 /lib/libncurses.so.5.7 7f3591d61000-7f3591f60000 ---p 00040000 08:06 8139 /lib/libncurses.so.5.7 7f3591f60000-7f3591f64000 r--p 0003f000 08:06 8139 /lib/libncurses.so.5.7 7f3591f64000-7f3591f65000 rw-p 00043000 08:06 8139 /lib/libncurses.so.5.7 7f3591f65000-7f3591f6c000 r-xp 00000000 08...

Hi, I am trying to run solaris 10 (9/10) on Xen 3.4 (centos5.5 as dom0) in HVM mode. I can see the realtek 8139 network adapters when I do pciscan but ''ifconfig -a'' just lists loopback device. I can load rtls drivers but still these realtek interfaces are not available. I found a link which does say The rtls driver from Realtek still uses version 0 interfaces that are now unsupported in Sol...

I have finally gotten one version of windows 2003 r2 x64 installed as a guest. The bad news is no network. The network tab says it''s a realtek 8139 when I know it is a intel. I tried downloading the intel drivers and they wont install says it''s the wrong hard ware. Is this common that it uses a 8139 as a generic network card? Also the network card shows The device can not find enough free resources to use. I get that sa...

...se of some sort, but they'll have none of that...) One workstation in the entire plant is having issues opening it. The file will load, it will change status to [Shared] in the titlebar, then stop. Bad Workstation: Windows 2000 Athlon 1600+ 256MB DDR 333 Soyo Dragon KT333 Ultra Black Realtek 8139 on-board (Also tried PCI 8139) Server: Debian Stable 2x Opteron 240 Broadcom "tg3" 1000Mb NIC Samba 3.0.7-1 as a PDC Network: Phoebe Micro 24+2 10/100/1000 Switches, daisychained via GbE over Gigabit-rated Cat5e. If I copy the file over to the local drive and open it, it works fine. It...

I found (and fixed) a problem with my realtek onboard 8139 controller. dhcpd server sends filename "pxelinux.0" but realtek requests "pxelinux.0\377" (i.e. the octal character 377 is appended), resulting in a file not found during the tftpd phase. I fixed this by adding a mapping to tftpd: # strip ending garbage from filenames (Realte...

I was wondering how to trigger a configration run remotely. Is this possible? Looking through the docs, I see mention that puppet can listen on port 8139, but I don''t see that this is the case on my servers. Can someone please enlighten me as to the proper method of doing this, if it can indeed be done? Thanks!

...rsync *:* LISTEN 9877/rsync I run puppetd which will update my rsyncd.conf file and restart the rsync daemon: -bash-3.00# puppetd --test --serve CCMT-A --server CCMT-A info: Starting handler for Runner info: Starting server for Puppet version 0.22.0 info: Listening on port 8139 notice: Ignoring --listen on onetime run info: Caching configuration at /var/lib/puppet/localconfig.yaml notice: Starting configuration run info: //serv1./systemimager/File[/etc/systemimager/rsyncd.conf]: Filebucketed to backup with sum 720e2bc25914a472146ccc05c1a3ec42 notice: /serv1./systemimager/...

...I failed to make Samba 3.0.0 /3.0.2a working from Windows side on the slightly different Slackware?s. Last try was the ?current? Slackware version(kernel 2.4.25) of some March 20?s with Samba 3.0.2a in it. Server: Asus P4P800-PIV?RAM 1.5(1)Gb- 3Com 3C940 integrated. Client(s): W2k SP3, Realtek 8139 NIC. Installed OK (binaries from a distribution?), user added OK after useradd to Linux. Share path is owned by that user and 'chmod a+rwx'ed. Swat works OK except that it always insists that smbd is not running(?). Smbclient was tried at mget/mput Windows distribution (in thousands of...

...graded 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 card are as follows: lspci:- 00:0e.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) /etc/modprobe.conf:- alias eth0 8139too Any suggestions welcomed.. Thanks Clive

...t bridge: Advanced Micro Devices [AMD] K8 NorthBridge 0000:01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600] 0000:01:00.1 Display controller: ATI Technologies Inc RV350 AP [Radeon 9600] (Secondary) 0000:02:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 0000:02:0b.0 Ethernet controller: Marvell Technology Group Ltd. Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (rev 13) cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 47 model name : AMD Athlon(tm) 64 Proces...

I''ve tried a couple times to PXE boot a domU by passing the "--pxe" option to virt-install but it stalls at: "Searching for server (DHCP)........" I also tried dumping an existing domU to an xml file and editing the boot device to "net", but then I''m unable to import the xml as a new domain. Is PXE possible for an HVM domU on a Solaris dom0? I

...when I attempt to enable jumbo frames, I receive: SIOCSIFMTU: Invalid argument, I receive the same error from ifconfig eth1 mtu 9000 and making the change in the ifcfg-eth1 config file. This is the driver I have running from lspci -vv 00:04.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20) Subsystem: XenSource, Inc. Device 0001 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 64, Cac...

...: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge 00:08.0 Serial controller: Integrated Technology Express, Inc. IT8874F PCI Dual Serial Port Controller (rev 01) 00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 00:0a.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) 00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 00:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 00:0f...