On 07/26/16 22:22, Johnny Hughes wrote:
<<>>
hello Johnny,
glad you caught my post.
> If you can not get that NIC working with the default kernel, you could
> try the experimental kernel per the bottom of:
>
> https://wiki.centos.org/SpecialInterestGroup/AltArch/i386
>
--->
thank you. just
On 07/26/2016 02:58 PM, geo wrote:
>
> hello Ned.
>
> On 07/26/2016 02:04 PM, Ned Slider wrote:
>> On 26/07/16 19:04, geo.inbox.ignored wrote:
> <<>>
>
>>> ]$ lspci|grep Realtek
>>> 0e:00.0 Network controller: Realtek Semiconductor Co., Ltd. \
>>> RTL8187SE Wireless LAN Controller (rev
CentOS Errata and Security Advisory 2016:1486 Moderate
Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1486.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
On 7/26/2016 2:56 PM, m.r...@5-cent.us wrote:
Yeah, well, the thing is, for years I've just been shoving ordinary SATA
drives into the same server, to use to copy from other machines via rsync,
getting a drive ready to replace in another server. I've never had trouble
with SATA. This is the
John R Pierce wrote:
> On 7/26/2016 2:38 PM, Peter wrote:
>> On 27/07/16 09:11,m.r...@5-cent.us wrote:
>>> >This is... odd. Got a 6.8 box, a Dell R320 lspci tells me
>>> >01:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS
>>> 2008 [Falcon] (rev 03)
>>> >so it*should* accept an
CentOS Errata and Security Advisory 2016:1487 Moderate
Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1487.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
CentOS Errata and Security Advisory 2016:1486 Moderate
Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1486.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
Source:
On 7/26/2016 2:38 PM, Peter wrote:
On 27/07/16 09:11,m.r...@5-cent.us wrote:
>This is... odd. Got a 6.8 box, a Dell R320 lspci tells me
>01:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 2008
>[Falcon] (rev 03)
>so it*should* accept an SAS drive. I've got a Cheetah that's a
On 27/07/16 09:11, m.r...@5-cent.us wrote:
> This is... odd. Got a 6.8 box, a Dell R320 lspci tells me
> 01:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 2008
> [Falcon] (rev 03)
> so it *should* accept an SAS drive. I've got a Cheetah that's a few years
> old, and having pulled
Denniston, Todd A CIV NAVSURFWARCENDIV Crane wrote:
>> From: m.r...@5-cent.us [mailto:m.r...@5-cent.us]
>> Sent: Friday, July 22, 2016 4:15 PM
>> m.r...@5-cent.us wrote:
>> >
>> >I am perplexed. I updated my workstation at work Wed before I left,
>> > from 6.7 to 6.8. Then, yesterday, I went
This is... odd. Got a 6.8 box, a Dell R320 lspci tells me
01:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 2008
[Falcon] (rev 03)
so it *should* accept an SAS drive. I've got a Cheetah that's a few years
old, and having pulled it out of another server (in the datecenter), I put
> -Original Message-
> From: m.r...@5-cent.us [mailto:m.r...@5-cent.us]
> Sent: Friday, July 22, 2016 4:15 PM
> To: CentOS mailing list
> Subject: Re: [CentOS] CentOS 6.7->6.8, ssh-add issue, followup, more info
>
> m.r...@5-cent.us wrote:
> > Folks,
> >
> >I am perplexed. I updated
On 07/26/2016 11:21 AM, Jim Perrin wrote:
A number of older storage and network drivers were purged from the
kernel with the release of el7. If this hardware is old enough, it's
entirely possible that it's no longer supported out of the box.
This is particularly likely if this same hardware
hello Ned.
On 07/26/2016 02:04 PM, Ned Slider wrote:
> On 26/07/16 19:04, geo.inbox.ignored wrote:
<<>>
>> ]$ lspci|grep Realtek
>> 0e:00.0 Network controller: Realtek Semiconductor Co., Ltd. \
>> RTL8187SE Wireless LAN Controller (rev 22)
>> 14:00.0 Ethernet controller: Realtek
On 26/07/16 19:04, geo.inbox.ignored wrote:
greetings one and all.
installing centos 7 32 bit i386 to laptop;
specs:
toshiba satellite l455d-s5976
amd sempron si-42
2 GB ddr2
250 GB hdd
]$ lspci|grep Realtek
0e:00.0 Network controller: Realtek Semiconductor Co., Ltd. \
RTL8187SE
John R Pierce wrote:
> On 7/26/2016 10:20 AM, Fawzy Ibrhim wrote:
>> I want to install Centos 7 latest build on NEC Server 5800/120b-2.
>>
>> The installation wizard fails to detect the storage connected to LSI
>> SATA MegaRaid PCI.
>
> which megaraid card? they've made quite a lot. lspci will
On 07/26/2016 12:20 PM, Fawzy Ibrhim wrote:
> Dear All;
>
> I want to install Centos 7 latest build on NEC Server 5800/120b-2.
>
> The installation wizard fails to detect the storage connected to LSI SATA
> MegaRaid PCI.
>
> Centos 5/6 were working fine with this H/W configuration but not
On 7/26/2016 10:20 AM, Fawzy Ibrhim wrote:
I want to install Centos 7 latest build on NEC Server 5800/120b-2.
The installation wizard fails to detect the storage connected to LSI SATA
MegaRaid PCI.
which megaraid card? they've made quite a lot. lspci will list the
card type...
linux
greetings one and all.
installing centos 7 32 bit i386 to laptop;
specs:
toshiba satellite l455d-s5976
amd sempron si-42
2 GB ddr2
250 GB hdd
]$ lspci|grep Realtek
0e:00.0 Network controller: Realtek Semiconductor Co., Ltd. \
RTL8187SE Wireless LAN Controller (rev 22)
14:00.0 Ethernet
Dear All;
I want to install Centos 7 latest build on NEC Server 5800/120b-2.
The installation wizard fails to detect the storage connected to LSI SATA
MegaRaid PCI.
Centos 5/6 were working fine with this H/W configuration but not the case with
Centos 7.
Please; advise.
Fawzy Ibrahim
On Tue, 26 Jul 2016 16:21:00 +0100 (BST)
John Hodrien wrote:
> On Tue, 26 Jul 2016, Gabriele Pohl wrote:
>
> > on all of my CentOS7 VMs on different hypervisors
> > the config file e2fsck.conf contains the line
> >
> > broken_system_clock = 1
> >
> > Do you see similiar
On Tue, 26 Jul 2016, Gabriele Pohl wrote:
Hi,
on all of my CentOS7 VMs on different hypervisors
the config file e2fsck.conf contains the line
broken_system_clock = 1
I found this because on all of them, the
root partition was not checked triggered
by interval setting with tune2fs.
Do you
On Tue, 26 Jul 2016 17:03:52 +0200
Gabriele Pohl wrote:
> on all of my CentOS7 VMs on different hypervisors
> the config file e2fsck.conf contains the line
>
> broken_system_clock = 1
>
> I found this because on all of them, the
> root partition was not checked triggered
> by
Hi,
on all of my CentOS7 VMs on different hypervisors
the config file e2fsck.conf contains the line
broken_system_clock = 1
I found this because on all of them, the
root partition was not checked triggered
by interval setting with tune2fs.
Do you see similiar /default/ settings on
your
Due to the nature of XSA-182, we built binaries privately and pushed
the signed binaries out as soon as the embargo lifted.
Everyone is urged to update as soon as possible.
-George
___
CentOS-virt mailing list
CentOS-virt@centos.org
25 matches
Mail list logo