similar to: conflict between Realtek 8139 (client) and 3c2000T (server) NIC's with Samba?

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

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 such high CPU useage when transferring large documents (Quark

Hi, When trying to copy 5000+ files from a client PC to a Samba server I have the following problem. Halfway during the operation it hangs on always the same file. Windows XP (SP1) gives: Unable to copy file [filename]. Specified network name is no longer available. (I had to translate this from Dutch, so it is not the exact message). When checking with smbstatus I get this:

Hi, After trying too long I fixed the problem below by reverting to the old 3c905 NIC. Problem solved but not understood. I had a similar 3c2000 NIC in another Samba server and it also failed to copy a large amount (5000+) of files. So that's two completely servers (hardware and Samba / Slackware version) having the same problem with any number of different clients. I couldn't imagine

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

I was trying to do some performance testing between using iSCSI on the host as a diskfile to a guest vs the VM guest using the iSCSI device directly. However, in the process of trying to establish a baseline performance figure, I started increasing the MTU settings on the PCI-express NICs with RTL8168B chips. First bottleneck was discovering the max MTU allowed on these is 7K instead of 9K but

Dear group, Here is my df : df <- structure(list(DESCRIPTION = c("PRM HGH GD ALUMINIUM USD 09/07/10 ", "PRM HGH GD ALUMINIUM USD 09/07/10 ", "PRIMARY NICKEL USD 04/06/10 " ), CREATED.DATE = structure(c(18361, 18361, 18325), class = "Date"), QUANITY = c(-1L, 1L, 1L), CLOSING.PRICE = c("2,415.90", "2,415.90",

Greetings, I am tearing my hair at getting this to work under centos 5.5/Ubuntu 10.04. Any suggesstions (Repos, RPMs etc)? My MB Intel embedded NIC blow up after a lightning (Mumbai get _real_ heavy mansoon rains inter alia). I want this to make work under Centos 5.x (and 6.x subsequently who DVD I have been downloading with a pithy 128kbps connection). -- Regards, Rajagopal

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 (Realtek PXE bug) r ^([[:graph:]]*)(.+)$ \1

Dear group, Here is my data.frame : df <- structure(list(DESCRIPTION = c("PRM HGH GD ALU", "PRM HGH GD ALU", "PRIMARY NICKEL", "PRIMARY NICKEL", "PRIMARY NICKEL", "PRIMARY NICKEL", "STANDARD LEAD ", "STANDARD LEAD ", "STANDARD LEAD ", "STANDARD LEAD ", "STANDARD LEAD ",

Hi all, I swapped a Realtek 8139 100M Net Card for a Realtek 8169 Gig Net card in a Centos 5.6 system. After reconfiguring the network settings I find that on boot up the 8169 interface does not start. The startup script says something like "The 8169 is not available..." ifconfig -a shows a device with the right mac address called __tmpsomethingorother I can get it going if I

Howdy, It appears that CentOS 5.2's support for the RTL8111B/C chip is incomplete. The wiki has some blanket statements regarding this support: http://wiki.centos.org/AdditionalResources/HardwareList/CentOS5/RealTek/r1000 http://wiki.centos.org/AdditionalResources/HardwareList/RealTekRTL8111b I could dive in an make the changes *I* think need to happen but I'd like to talk to people

Jerry Geis <geisj at pagestation.com <http://lists.centos.org/mailman/listinfo/centos>> wrote: >/ Hi, />/ I have a compaq V2000 laptop. Specs for network say its a />/ realtek 8139/8139C+ NIC. / Is it really a RTL8139? Or it is possible that it's a RTL8100? The reason I ask is because while the RTL8100 is supposed to be MAC compatible with the RTL8139, I'm finding

I''m trying to build out a test cloud using XCP 1.0.0 beta with 3 machines of 18 cores total (Phenom II 1090s). I''ve built three machines, installed XCP 1.0.0 beta on them and they all three have the same problem - the Realtek network cards don''t work. The following is the output from lspci 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI

Found this solution. It is maybe not the most elegant way, but it does the job. > a=as.data.frame(substr(lme$DESCRIPTION,1,14)) > colnames(a)=c("DESCRIPTION") > lme=as.data.frame(c(a,lme[,2:3])) > lme DESCRIPTION CLOSING.PRICE POSITION 1 PRIMARY NICKEL 25,755.7100 0 2 PRIMARY NICKEL 25,760.8600 0 3 PRM HGH GD ALU 2,415.9000 0

Dear group, I know this issue has been already covered, and before you reply I must say I have read the R-FAQ and search the mailing list archive. I still can't manage to change my factor to numeric as I couldn't find any clear answer. Here is my df : Pose1 <- structure(list(DESCRIPTION = structure(c(1L, 2L, 3L, 4L, 5L, 8L), .Label = c(" SUGAR NO.11 May/10 ", "COTTON

Hi all, Our intranet's WAN interface just stopped working yesterday, and I can't figure it out. The machine has a Gigabyte motherboard, with on-board RTL-8110SC/8169SC Gigabit Ethernet and D-Link PCI NIC for the LAN side. I can get into the LAN side without an issue, but can't see the WAN side at all. [root at intranet ~]# ifconfig eth0 up eth0: unknown interface: No such device

Bill, your CentOS 5 RTL8110 page should probably be updated. I've confirmed that there's a newer r8169 driver in the kernel that works with the RTL8110. RealTek's web site now carries the new r8169 instead of the r1000. The newer driver fixed a problem I was having on one host so we should probably recommend it over the older r1000. I've updated my CentOS 4 page. Kirk Bocek

If one of you wanted to try to create a patch to support ALTREP generic vectors here are some notes: The main challenge I am aware of (there might be others): Allowing DATAPTR to return a writable pointer would be too dangerous because the GC write barrier needs to see all mutations. So it would be best if Dataptr and Dataptr_or_null methods were not allowed to be defined. The default methods in

I can work on this. Thanks Luke. ~G On Wed, Jul 24, 2019 at 8:25 AM Tierney, Luke <luke-tierney at uiowa.edu> wrote: > If one of you wanted to try to create a patch to support ALTREP > generic vectors here are some notes: > > The main challenge I am aware of (there might be others): Allowing > DATAPTR to return a writable pointer would be too dangerous because > the GC