[CentOS] [FIPS] FIPS_selftest failing in Centos 7

2020-03-06 Thread Akshar Kanak 
Dear team
The API FIPS_selftest() is failing .
The content of the file /proc/sys/crypto/fips_enabled is 1
I have executed the below mentioned code

The code is
#include "stdio.h"
int main()
{
int ret=0;
ret=FIPS_mode();
printf("\nFIPS_mode = %u  \n",ret);
ret=FIPS_selftest();
printf("\nFIPS_selftest=%u  \n",ret);
ERR_print_errors_fp(stderr);
}


 Output  is
"
FIPS_mode = 1

FIPS_selftest=0
140091346814640:error:0607B0A3:lib(6):func(123):reason(163):evp_enc.c:313:
140091346814640:error:2D06F065:lib(45):func(111):reason(101):fips_des_selftest.c:134:
"

 Looks like flag EVP_CIPH_FLAG_FIPS is not set for the cipher returned
by EVP_des_ede_ecb() .

 I am using openssl-1.0.2k-19.el7.x86_64 on "CentOS Linux release
7.6.1810 (Core)"

Please let me know you thoughts on this

Thanks and Regards
Akshar
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Support for Intel Graphics 605 UHD

2020-03-06 Thread Jerry Geis 
This is my /proc/cmdline


BOOT_IMAGE=(hd0,gpt2)/boot/vmlinuz-4.18.0-147.5.1.el8_1.x86_64
root=UUID=c1bef884-0180-4955-a669-c99a8c64f75a ro crashkernel=auto
resume=UUID=0fe1a972-9912-4803-b5ec-265a13a888c1 biosdevname=0
net.ifnames=0 rhgb quiet rd.driver.
blacklist=nouveau nomodeset nouveau.modeset=0 acpi_backlight=vendor
"acpi_osi=!Windows 2013" "acpi_osi=!Windows 2012"

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

Re: [CentOS] Support for Intel Graphics 605 UHD

2020-03-06 Thread Leon Fauster via CentOS 

Am 06.03.20 um 15:23 schrieb Jerry Geis:

This is my /proc/cmdline


BOOT_IMAGE=(hd0,gpt2)/boot/vmlinuz-4.18.0-147.5.1.el8_1.x86_64
root=UUID=c1bef884-0180-4955-a669-c99a8c64f75a ro crashkernel=auto
resume=UUID=0fe1a972-9912-4803-b5ec-265a13a888c1 biosdevname=0
net.ifnames=0 rhgb quiet rd.driver.
blacklist=nouveau nomodeset nouveau.modeset=0 acpi_backlight=vendor
"acpi_osi=!Windows 2013" "acpi_osi=!Windows 2012"


Mmmh, are you using a dual graphics platform?

Just a wild guess; substitute your grub config part

blacklist=nouveau nomodeset nouveau.modeset=0

with

module_blacklist=nouveau,amdgpu,radeon i915.alpha_support=1

Install the new grub config and rebuild your
init ramdisk, just for consistency ...

--
Leon


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

Re: [CentOS] Support for Intel Graphics 605 UHD

2020-03-06 Thread Jerry Geis 
> module_blacklist=nouveau,amdgpu,radeon i915.alpha_support=1

ok I did that - regen that file and verified with cat /proc/cmdline
This is not a dual monitor situation. I also removed all that other
"legacy" stuff I had in there.

no difference.

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

Re: [CentOS] Support for Intel Graphics 605 UHD

2020-03-06 Thread Jonathan Billings 
On Fri, Mar 06, 2020 at 01:20:23PM -0500, Jerry Geis wrote:
>
> > module_blacklist=nouveau,amdgpu,radeon i915.alpha_support=1
> 
> ok I did that - regen that file and verified with cat /proc/cmdline
> This is not a dual monitor situation. I also removed all that other
> "legacy" stuff I had in there.

Those settings aren't typically for a dual-monitor setup specifically,
but for enabling the 3rd-party NVidia or AMD drivers, instead of the
open source, in-kernel drivers.

If you are only using an intel GPU, you don't need them.

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

[CentOS] Convert CentOS-8 UEFI img to hyper-V

2020-03-06 Thread Jerry Geis 
Hi All,

Anyone tried to convert QEMU to hyper v?
I tried this:
   qemu-img convert -f raw “kvm-virtal-machine.img” -O vhdx -o
subformat=dynamic “hyperv-virtual-machine.vhdx”

Then defined new HyperV stuff - and booted it did not boot got a dracut
error.

Anyone done that ? If so how ?

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

Re: [CentOS] Support for Intel Graphics 605 UHD

2020-03-06 Thread Jerry Geis 
Ok so I re-installed CentOS 8 from scratch. and compared the two. C7 and C8
X log files.
As 7 loaded Intel drivers and 8 does not.

grep LoadModule Xorg.0.log on CentOS 7
[22.856] (II) LoadModule: "glx"
[22.863] (II) LoadModule: "intel"
[22.878] (II) LoadModule: "dri3"
[22.878] (II) LoadModule: "dri2"
[22.878] (II) LoadModule: "present"
[23.054] (II) LoadModule: "evdev"
Clearly loading the intel driver... Good.

grep LoadModule Xorg.0.log on CentOS 8
[12.792] (II) LoadModule: "glx"
[12.804] (II) LoadModule: "modesetting"
[12.812] (II) LoadModule: "fbdev"
[12.813] (II) LoadModule: "vesa"
[12.835] (II) LoadModule: "fbdevhw"
[12.839] (II) LoadModule: "glamoregl"
[13.120] (II) LoadModule: "fb"
[13.726] (II) LoadModule: "libinput"
Not loading the intel driver - bad

What should I look at to find out why ?

My Kernel 4.18.0-147.5.1.el8_1.x86_64

rpm -qa | grep -i intel
xorg-x11-drv-intel-2.99.917-38.20180618.el8.x86_64


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