similar to: New RTL8111B Wiki Page

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

I'd like to add a page for the Realtek RTL8111b NIC. I'm not sure how you'd like to organize it since the page really could be relevant to both CentOS 4 and CentOS 5. I think a single page like: http://wiki.centos.org/HardwareList/RealTekRTL8111b Would work with links to both CentOS 4 *and* CentOS 5? However, if the wiki admins want two pages, that'll be fine too. Can you also

Hi, I have a new mainboard with a Realtek RTL8111B / RTL8168B NIC. In 5.1 are no driver integrated for this nic, but there is driver disk: http://wiki.centos.org/HardwareList/RealTekRTL8111b and http://wiki.centos.org/HardwareList/RealTekRTL8111b?action=AttachFile&do=get&target=r8168-2.6.18-53.el5-i686-x86_64.img.zip Can I integrate this driver do the CentOS 5.1 ISO or can i use this

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

I'd like to add a page for the Realtek r1000 NIC driver for the RTL8110SC (and others) chipset. This driver is not included in the kernel. I've previously posted to the general mail list: http://lists.centos.org/pipermail/centos/2007-February/075383.html I'm guessing this would go in the HardwareList section. Otherwise a page titled 'Realtek r1000 Driver' would work. my

Could I get write access to http://wiki.centos.org/HardwareList/CentOS5/RealTek/r1000? There's a couple of things I'd like to copy over from my CentOS4 R1000 page. Wiki Name: kirkbocek Thanks, Kirk Bocek

On May 24, 2015 4:46:18 PM PDT, Jonathan Billings <billings at negate.org> wrote: >> On May 24, 2015, at 18:24, Kirk Bocek <t004 at kbocek.com> wrote: >> >> So: >> >> $rpm -e --nodeps chrony > >No. Bad. > Okay, okay! I'll go on the paper. I'll reinstall chrony. But there *are* places I've needed to use nodeps. Mostly to manage

On 5/25/2015 4:40 AM, Jonathan Billings wrote: >> On May 25, 2015, at 01:10, Kirk Bocek <t004 at kbocek.com> wrote: >> >> I'll reinstall chrony. But there *are* places I've needed to use nodeps. Mostly to manage inter-repo package incompatibilities. > You should look into the yum priorities option to ensure packages from different repos don't step on each

Dear All, I have an onboard Realtek RTL8111/8168B NIC. from lspci -vv : 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) It is detected, but why the speed is always 100Mbps, already change cable but still no luck. I use ethtool and from the output it seems that system know that this NIC support gigabit speed : ???????

------------ Original Message ------------ > Date: Friday, May 22, 2015 11:52:43 AM -0700 > From: Kirk Bocek <t004 at kbocek.com> > > On May 22, 2015 11:46:23 AM PDT, Bowie Bailey > <Bowie_Bailey at BUC.com> wrote: >> I have a CentOS 7 server that I want to use as an audio source >> for our hold music. It does not have a GUI installed, so I am >>

On 5/24/2015 12:22 PM, Gordon Messmer wrote: > On 05/24/2015 11:41 AM, Kirk Bocek wrote: >> to activate your selected daemon. I just used the new systemd commands, >> thinking that would be enough. So I tried that and rebooted. Nope, same >> problem: > > chronyd and ntpd both use UDP port 123, so each will terminate the > other when it starts. If both are enabled,

Hello, I am bussy building a xen cluster. When selecting mainboards for this cluster i came only up with core 2 duo mainboards with onboard gigabit ethernet cards with the realtek RTL8111B chipset. I have tested a mainboard and could not find a way to compile the driver sourcecode from the realtek site because of a missing /lib/modules/2.6.16-xen/Build directory. Can anyone help me out? I am

Can anyone help getting a Tripplite SU2200XL to work with nut 2.0.3 using the supplied serial cable? Starting the ups service yields: Starting tripplitesu: Network UPS Tools - Tripp Lite SmartOnline driver 0.02 (2.0.3) Unable to detect Tripp Lite SmartOnline UPS on port /dev/ttyS0 I also have Tripplite's PowerAlert 12 software installed and when run it finds the UPS without a problem. So

I'm unable to install x86_64 on a host. The installer gets through the first part, asking for install type and it begins loading the images from whatever media was selected. Then anaconda spills a series of cryptic messages ending in 'file not found' and the console on F2 is locked up. I've tried this with physical DVD media, PXE-HTTP and media-boot HTTP install. It happens

Hello I've just been hit by one of the chipsets described at http://wiki.centos.org/HardwareList/RealTekRTL8111b. Because a) it does not work with the stock driver included in Centos 5.1 and b) I am very lazy and I do not like manually compiling modules each time a new kernel is installed (not to mention that I never forget anything, except for the important things which always go

Bryan J. Smith wrote: > Kirk Bocek <t004 at kbocek.com> wrote: > >>- I was originally planning on using KnoppMyth. >>But their CD appears to be only for i386. >>Without realizing it, the P4 CPU I picked is one of >>the newer ones with the x86_64 extensions. >>It won't boot i386. > > > ??? It should run i386 code all-the-same. That what I

Can you send me the serial number (at least 1st 12 characters, see: https://www.tripplite.com/support/identify-products) and lsusb -v output for the UPS? Thank you, David Zomaya Tripp Lite From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at alioth-lists.debian.net> on behalf of Kirk Bocek <t004 at kbocek.com> Sent: Tuesday, September 22, 2020 11:55 AM To:

Thanks! I think we ran into something similar in the past with the 2012 protocol a while back. Let me look into it and follow up. Feel free to nudge me if I don't respond in a day or two. (There are others on the list who may know a fix quicker than I, feel free to chime in!) From: Kirk Bocek <t004 at kbocek.com> Sent: Tuesday, September 22, 2020 1:38 PM To: David Zomaya; nut-upsuser

Not a whole lot to do in the field for a legitimate USB not responding issue other than verify cabling and give a power cycle and/or discharge reset a try (which, given the nature of a UPS isn't always something you can easily do of course). If it looks like a problem with USB being completely dead, as opposed to just the "drops" issue we started with, I definitely recommend

On 5/22/2015 3:01 PM, Richard wrote: > > ------------ Original Message ------------ >> Date: Friday, May 22, 2015 11:52:43 AM -0700 >> From: Kirk Bocek <t004 at kbocek.com> >> >> On May 22, 2015 11:46:23 AM PDT, Bowie Bailey >> <Bowie_Bailey at BUC.com> wrote: >>> I have a CentOS 7 server that I want to use as an audio source >>>