Re: [CentOS] where did SCL go?

2016-02-20 Thread Lamar Owen 

On 02/19/2016 08:55 PM, jason welsh wrote:

No package centos-release-SCL available.
Error: Nothing to do
monsterjam.org:/etc/letsencrypt/archive/monsterjam # cat
/etc/centos-release
CentOS release 6.7 (Final)
monsterjam:/etc/letsencrypt/archive/monsterjam #

any ideas?


Try centos-release-scl instead.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] where did SCL go?

2016-02-20 Thread Jason Welsh 
I believe it's because I'm using the 32 bit flavor of centos. Of course I
found a doc stating that right after I sent the email.

Thanks,
Jason
On Feb 20, 2016 2:18 PM, "Lamar Owen"  wrote:

> On 02/19/2016 08:55 PM, jason welsh wrote:
>
>> No package centos-release-SCL available.
>> Error: Nothing to do
>> monsterjam.org:/etc/letsencrypt/archive/monsterjam # cat
>> /etc/centos-release
>> CentOS release 6.7 (Final)
>> monsterjam:/etc/letsencrypt/archive/monsterjam #
>>
>> any ideas?
>>
>> Try centos-release-scl instead.
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Kernel panic and crash, was Re: [CentOS-announce] CEBA-2016:0150 CentOS 6 kernel BugFix Update

2016-02-20 Thread Max Pyziur 

Greetings,


I just tried upgrading one of my CentOS boxes to this kernel.

It crashes; the screen looks like this:
http://www.brama.com/~deckard/P1010308.JPG

So, I'm continuing to run on
kernel-2.6.32-504.23.4.el6.x86_64

I had previously reported this, and I was told that the reported bug was 
here:

https://bugs.centos.org/view.php?id=9374

Looking at it now, I see that it is closed.

It's odd that CentOS is releasing a production kernel that fails.

fyi,

Max Pyziur
p...@brama.com


On Wed, 10 Feb 2016, Johnny Hughes wrote:



CentOS Errata and Bugfix Advisory 2016:0150

Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-0150.html

The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )

i386:
b5f33a81b28d0a89af970bc08c4a07856c13f9789fe520e90d237dc7a2e5df65  
kernel-2.6.32-573.18.1.el6.i686.rpm
8b375b6d363800343bc325966b4db96347e2508db458547b0df5dc63581e2793  
kernel-abi-whitelists-2.6.32-573.18.1.el6.noarch.rpm
cba169e9faf5ebc0ba25011f3b920de1a3a2943b7e46be6292193b31df7b8a5a  
kernel-debug-2.6.32-573.18.1.el6.i686.rpm
a4bf157c52dc0d736ef7a65a073e543b3f2cf0070aa938da41eeecaca11e783d  
kernel-debug-devel-2.6.32-573.18.1.el6.i686.rpm
5151ae3d0f6dde51c1ec991e14b88f0308ef7d46975ee7e9ed036f1381153901  
kernel-devel-2.6.32-573.18.1.el6.i686.rpm
74ff6b30bd2603f2e859e899a653aaac2daa0ee534abd5ab3e32a8ffc2cdb2fb  
kernel-doc-2.6.32-573.18.1.el6.noarch.rpm
38a27fbf4e7fa229fe8ab6b8cf25ec08031c376cf51ec38400197bc478d0255a  
kernel-firmware-2.6.32-573.18.1.el6.noarch.rpm
f318d66d12c72c060e8f644aa90d0c10099f1ab8ba5e24875f2a1ace22e35a57  
kernel-headers-2.6.32-573.18.1.el6.i686.rpm
81ef77b0d7841946bf8825e599c1f6a6015082013b5ea02a836db34e19ca7fbc  
perf-2.6.32-573.18.1.el6.i686.rpm
a8fa3ef717f09235052dd6bd4285be52ff494ea8c242788df16eda5b9aed7fb6  
python-perf-2.6.32-573.18.1.el6.i686.rpm

x86_64:
1cb5031871e077e7d70fec7801901a948438d10f226ffb4311540c28f9253a55  
kernel-2.6.32-573.18.1.el6.x86_64.rpm
8b375b6d363800343bc325966b4db96347e2508db458547b0df5dc63581e2793  
kernel-abi-whitelists-2.6.32-573.18.1.el6.noarch.rpm
9f31b8f7f4db48d8ba30c16564cb6ad614d04b7d63811c274134654607cbce08  
kernel-debug-2.6.32-573.18.1.el6.x86_64.rpm
a4bf157c52dc0d736ef7a65a073e543b3f2cf0070aa938da41eeecaca11e783d  
kernel-debug-devel-2.6.32-573.18.1.el6.i686.rpm
16cb431b4a01c6b3b915e646c971fa0c79e62f4feeffd57939f39df687ebc6a3  
kernel-debug-devel-2.6.32-573.18.1.el6.x86_64.rpm
b81c297339078d80dda73d86a1aec61c50d7fb05728585c1ebbe81bb088851bf  
kernel-devel-2.6.32-573.18.1.el6.x86_64.rpm
74ff6b30bd2603f2e859e899a653aaac2daa0ee534abd5ab3e32a8ffc2cdb2fb  
kernel-doc-2.6.32-573.18.1.el6.noarch.rpm
38a27fbf4e7fa229fe8ab6b8cf25ec08031c376cf51ec38400197bc478d0255a  
kernel-firmware-2.6.32-573.18.1.el6.noarch.rpm
9dd3a3533ebb6646bafafef2229b6142fa0277f34a534e7c74f3c8cacafd7296  
kernel-headers-2.6.32-573.18.1.el6.x86_64.rpm
5ff27ecbdca7013f093d697f4ba3bcaa9b14be03ef79cafb4a3ed3d0aef1bf69  
perf-2.6.32-573.18.1.el6.x86_64.rpm
c5fee073bee1f19dc848a8302e07e4241e49cbff55f35a3db5ae903352f11dc4  
python-perf-2.6.32-573.18.1.el6.x86_64.rpm

Source:
ef3c944af9b7e94448e3c343da7d6f582b267aa9a5653586b8b9332351b01afc  
kernel-2.6.32-573.18.1.el6.src.rpm





___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Kernel panic and crash, was Re: [CentOS-announce] CEBA-2016:0150 CentOS 6 kernel BugFix Update

2016-02-20 Thread Always Learning 

Greetings Max,

> I had previously reported this, and I was told that the reported bug was 
> here:
> https://bugs.centos.org/view.php?id=9374
> 
> Looking at it now, I see that it is closed.

Wrong. That reports refers to an earlier bug, which appears to be
identical:-

https://bugs.centos.org/view.php?id=9209

Looking at the end of the web page, you will see a splendid Centos hero
has found a solution you may wish to try.


" toracat (developer) 
2016-02-21 04:23
 
The latest centosplus kernel (kernel-2.6.32-573.18.1.el6.centos.plus)
now has CONFIG_DRM_I915_UMS disabled. "


Good Luck.


-- 
Regards,

Paul.
England, EU.  England's place is in the European Union.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos