search for: pro100s

Hello everybody, for just one week I try to install three servers on an OpenSuSE 10.3 dom0 equipped with 4 NICs. One server is an OX using the onboard NIC via xenbr0. This server runs!! For my IPCop server I intended to use the three remaining NICs (Intel Pro100/S, 3Com 3C590, Realtek RTL-8139). These three NICs should be used natively by my IPCop. So I tried to use the pciback driver. I wrote a

Folks, I'm trying to add a network interface card to my SUSE 9.3 box, and I'm not having much luck with a US Robotics version. What manufacturer do any of you use in your machines--either 10/100MB or GigE NIC? Thanks Eric Hines There is no nonsense so errant that it cannot be made the creed of the vast majority by adequate governmental action. --Bertrand Russell

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

...to the configuration files. Cheers, MaZe. PS. alternatively you can open the case and switch the two network cards, they'll be detected in reverse order and the previous renaming problem should vanish. On Mon, 9 May 2005, Michael Rock wrote: > btw - the two NIC cards are identical Intel Pro100S > and I also tried latest drivers. > > --- Michael Rock <mikerocks65 at yahoo.com> wrote: >> Hi, I have a problem when adding a second NIC card. >> It will not configure to eth1 and keeps changing its >> device name on reboot to dev and a number, like >> dev8...

Hi, I have a problem when adding a second NIC card. It will not configure to eth1 and keeps changing its device name on reboot to dev and a number, like dev8761. I tried changing BIOS setting, plug/play on/off and forcing IRQ for PCI slots. But no difference. centos-3-4.2 Any ideas? thx __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best

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

On 7/11/2017 3:58 PM, Fred Smith wrote: > I faced the same issue some years ago, and found a low-priced mono > laser that lated me quite a few years. no color, but few thing I > wanted to print actually demanded color. my last two laser printers have been Brother black&white all-in-ones ("MFC"). *VERY* cheap per page printing costs, even if you use Brother brand toner

First, THANKS! The SYSLINUX/PXELINUX s/w and docs are great. I have been able to set up a working server for PXE boot in very little time, using our existing Win2k DHCP server and a Red Hat 7.2 Linux server for tftp, etc... It took very little time (compared to an earlier effort 4 months ago.....) and the pxelinux/menu/memdisk environment is great for us. The environment seems to support PXE

I have a hp photosmart C3180 all-in-one and am well and truly sick of it. It seems like every time I go on another printing binge, I need yet another print cartridge. hp-clean doesn't help. IIRC this use it or lose it "feature" is common to inkjets. What should I replace it with? If I want a non-cloggging printer, is laser jet the way I need to go? I'd like to do color

Hi all, I''ve got a lot of video files on a zfs/cifs fileserver running SXCE. A little while ago the dual onboard NICs died and I had to replace them with a PCI 10/100 NIC. The system was fine for a couple of weeks but now the performance when viewing a video file from the cifs share is appauling. Videos stop and jerk with audio distortion. I have tried this from several client machines

copy d:\bugs.ps \\ouessant\lexmark after having deleted all the samba log files and restarted the SMBd daemon from the SWAT Web interface. This leads to the INTERNAL ERROR, see samba.oulx Now, to locate the problem, I tried the same kind of command on the same file, bugs.ps, but using the SMBCLIENT application from the Linux server itself, without changing anything, nor restarting the SMBd