Re: [elrepo] skylake and nvidia
On 09/20/2016 10:54 PM, Akemi Yagi wrote: > On Tue, Sep 20, 2016 at 9:38 AM, Farkas Levente <lfar...@lfarkas.org> wrote: > >> the other problem that i's still not able to download the source of the >> 7.3 beta. either i try to download the source isos or individual >> package's src.rpm i always got an error from rh. so i can't look into >> the spec file and start to build our own versions. > > Downloading the isos did fail earlier but it seems to be working now. > Try it before it dies again. :) now i've got it!:-) -- Levente "Si vis pacem para bellum!" ___ elrepo mailing list elrepo@lists.elrepo.org http://lists.elrepo.org/mailman/listinfo/elrepo
Re: [elrepo] skylake and nvidia
the question of course what does the "supported" means? for us the supported means that the xvinfo gives us at least 16 port (or more). unfortunately even with the latest7.3 beta it gives only 1. what does it means? it's working! you can start an X or gnome environment etc. but can't really use the integrated graphics which means only a little bit better then vesa mode. unfortunately rh did not even comment my bz:-( https://bugzilla.redhat.com/show_bug.cgi?id=1372383 what i collect so far? fedora 23 and 24 fully support it out of the box. intel linux graphics latest release 2.0.2: https://01.org/linuxgraphics/downloads/intel-graphics-update-tool-linux-os-v2.0.2 packages compared with 7.3 beta packages: * kernel in rhel 7.3 of course only 3.10, but fedora with 4.4 kernel working so probably 4.4 would be enough? but intel page shows 4.6. * mesa 11.2.2 in 7.3 ok. * xf86-video-intel 2.99.917 in 7.3 ok. but the question the build parameters. * libdrm-2.4.68 in 7.3: libdrm-2.4.67, but probably easy to rebuild to the new version. * libva-1.7.1 require new version from based on epel. * vaapi-intel-driver 1.7.1 require new version from based on nux * cairo-1.15.2 ? in 7.3: cairo-1.14.2 we hope it's enough. i do not believe we can replace such a basic library. * Xorg Xserver 1.18.3 now here the funny part:-) in 7.3 it's 1.17.2, but in the changelog of xf86-video-intel there is rebuild just because reenable dri, since 7.3 is based on xorg 1.18!?? so either they plan to rebase to 1.18 or it's an 1.18 looks like an 1.17?! * Intel-gpu-tools - 1.15 ? use inside the xorg driver package the other problem that i's still not able to download the source of the 7.3 beta. either i try to download the source isos or individual package's src.rpm i always got an error from rh. so i can't look into the spec file and start to build our own versions. On 09/20/2016 04:56 PM, Trevor Hemsley wrote: > There was a post made on the forums just recently that said that using > > |i915.preliminary_hw_support=1 > | > on the kernel command lijne makes it work for at least some Skylake > chips with the standard CentOS kernel. > > Skylake support is *meant* to be in 7.2 onwards. > > | > |On 20/09/16 15:46, Nicolas Thierry-Mieg wrote: >> Hi again, >> >> as posted a short while ago, I have a new Acer Aspire E5-575G-55DE >> laptop and am trying to get C7 running on it. >> >> This laptop has an intel i5-6200U with integrated HD Graphics 520. It >> also has an nvidia GeForce GTX 950M. >> Installing kmod-nvidia and bumblebee as explained [1] results in the >> "Oh no! Something has gone wrong" screen. I suspect that's because the >> regular C7 kernel and xorg-x11-drv-intel don't support the intel 520. >> >> Booting into kernel-lt, it seems the intel 520 works...? This is >> surprising because Farkas Levente's recent post to this list suggested >> that a newer xorg-x11-drv-intel should be needed, in addition to the >> newer kernel. But I have a bunch of OK-looking intel messages in >> /var/log/Xorg.0.log , and glxinfo says: >> OpenGL vendor string: Intel Open Source Technology Center >> OpenGL renderer string: Mesa DRI Intel(R) Skylake ULT GT2 >> >> Question 1: does this mean the intel 520 works fully under kernel-lt? >> If not, what should I look at? >> >> >> Assuming the intel GPU works under kernel-lt, I could then hope to get >> nvidia and bumblebee working. I've been using the elrepo nvidia >> drivers for ages, but I could use the nvidia-provided installer and >> hope it doesn't clobber anything (which I doubt...). >> Question 2: any caveats here? >> >> Finally I would need to get bumblebee working, otherwise the nvidia >> stuff is useless. However, bumblebee requires kmod-bbswitch... >> Question 3: I guess I would have to rebuild bbswitch [2] for >> kernel-lt, but could I still use the elrepo-provided bumblebee ? >> >> >> Thanks for any advice anyone can provide. >> Regards, >> Nicolas >> >> >> >> [1] http://elrepo.org/tiki/bumblebee >> [2] https://github.com/Bumblebee-Project/bbswitch >> ___ >> elrepo mailing list >> elrepo@lists.elrepo.org >> http://lists.elrepo.org/mailman/listinfo/elrepo >> >> __ >> This email has been scanned by the Symantec Email Security.cloud service. >> For more information please visit http://www.symanteccloud.com >> __ > > > > > ___ > elrepo mailing list > elrepo@lists.elrepo.org > http://lists.elrepo.org/mailman/listinfo/elrepo > -- Levente "Si vis pacem para bellum!" ___ elrepo mailing list elrepo@lists.elrepo.org http://lists.elrepo.org/mailman/listinfo/elrepo
[elrepo] intel skylake support
Hi, Currently all new intel cpu (ie skylake) has intel hd graphics 515, 520, 530 integrated video card support. It's not supported on centos-6.7. I try to find any kind of solution and read about it. Only linux mint, and latest patched ubuntu support it. The problem is the needed kernel support (at least 4.4) and a patched xorg intel driver. It seems even rhel 7.3 won't support it (at least the beta rhel-7.3 do not support it). Where I mean to support only van use 1 xv port and very basic feature by default. Unfortunately all current motherboard's has a slot which support only skylake or newer intel cpus (not to mention all current and new laptops). Is there any plan to support it in elrepo? IMHO it's on of the biggest lag currently in linux. Regards. -- Levente "Si vis pacem para bellum!" ___ elrepo mailing list elrepo@lists.elrepo.org http://lists.elrepo.org/mailman/listinfo/elrepo
Re: [elrepo] after kmod-nvidia el7 update during boot still use the old kmod
On 10/25/2015 03:27 PM, Phil Perry wrote: > On 25/10/15 10:38, Farkas Levente wrote: >> hi, >> after upgrading to kmod-nvidia-352.55-1.el7.elrepo.x86_64 after boot >> i've only got black screen. and this happended with the previous version >> also. the reason is that during boot the kernel's initramfs still >> contains the old kmod. the relevant part of dmesg: > > But because it's not versioned this won't tell us if the initramfs image > gets updated on updating the driver or not. > > After updating to kmod-nvidia-352.55-1.el7.elrepo we can check if dracut > has been run on the initramfs images: > > So as expected we see dracut has been run twice on all kernels, once > during %post as the new kmod package is installed and once during > %postun as the old kmod is uninstalled. > > Rebooting after the kmod update proceeds as expected. > ... > Check the initramfs as I did above. Then update to > kmod-nvidia-352.55-1.el7.elrepo, watching what dracut does, and see if > you can replicate the issue. > > If we can work out what's happening, and why, then maybe we can come up > with a solution to make the process more robust. > > Note that in the %post script, on first install only, we do: > > /usr/bin/dracut --add-drivers nvidia -f /boot/initramfs-$KERNEL.img $KERNEL so this last line solve my problem. and the reaon is this part only runs once, BUT not in the kmod's post sript but in the nvidia-x11-drv's post script. that's why i can't find it. why? why not the kmod take cares about the kmod update in the initramfs? is there any reason why this part put into the nvidia-x11-drv's post scripts? anyway i still don't know why this do not properly set my initramfs during update. but thanks you solve my problem:-) -- Levente "Si vis pacem para bellum!" ___ elrepo mailing list elrepo@lists.elrepo.org http://lists.elrepo.org/mailman/listinfo/elrepo
[elrepo] after kmod-nvidia el7 update during boot still use the old kmod
hi,
after upgrading to kmod-nvidia-352.55-1.el7.elrepo.x86_64 after boot
i've only got black screen. and this happended with the previous version
also. the reason is that during boot the kernel's initramfs still
contains the old kmod. the relevant part of dmesg:
---
[1.080456] Request for unknown module key 'The ELRepo Project
(http://elrepo.org): ELRepo.org Secure Boot Key:
f365ad3481a7b20e3427b61b2a26635b83fe427b' err -11
[1.080716] nvidia: module license 'NVIDIA' taints kernel.
[1.081210] Disabling lock debugging due to kernel taint
[1.085063] nvidia: module verification failed: signature and/or
required key missing - tainting kernel
[1.088709] vgaarb: device changed decodes:
PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[1.090184] [drm] Initialized nvidia-drm 0.0.0 20150116 for
:01:00.0 on minor 0
[1.090188] libata version 3.00 loaded.
[1.090389] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 352.41
Fri Aug 21 23:09:52 PDT 2015
---
and even if i run manualy kmod's postinstall scripts i i=only got one error:
---
[root@eagle ~]# modules=( $(find
/lib/modules/3.10.0-229.el7.x86_64/extra/nvidia | grep '\.ko$') )
[root@eagle ~]# printf '%s\n' "${modules[@]}" | /sbin/weak-modules
--add-modules
gzip: /boot/initramfs-3.10.0-229.14.1.el7.x86_64.img: not in gzip format
gzip: /boot/initramfs-3.10.0-229.14.1.el7.x86_64.tmp: not in gzip format
---
and probably it's failed to create the new initramfs.
all what can i do is:
rmmod nvidia; modprobe nvidia; systemctl restart graphical.target
and everything works again.
may be it's a bug in rhel/centos-7's kmod or dracut, but it's strange
that no one else has the same problem?
thank you for your help in advance.
regards.
--
Levente "Si vis pacem para bellum!"
___
elrepo mailing list
elrepo@lists.elrepo.org
http://lists.elrepo.org/mailman/listinfo/elrepo
Re: [elrepo] Announcement: EL7 Updated NVIDIA drivers for RHEL 7.1
On 04/02/2015 06:46 PM, Phil Perry wrote: On 02/04/15 16:46, Akemi Yagi wrote: On Thu, Apr 2, 2015 at 8:26 AM, Farkas Levente lfar...@lfarkas.org wrote: Hi, it strange since it's not working for me. ie: installed pacakges: kernel-3.10.0-123.20.1.el7.x86_64 kernel-3.10.0-229.1.2.el7.x86_64 nvidia-x11-drv-32bit-346.47-1.el7.elrepo.x86_64 kmod-nvidia-346.47-1.el7.elrepo.x86_64 nvidia-detect-346.47-1.el7.elrepo.x86_64 nvidia-x11-drv-346.47-1.el7.elrepo.x86_64 if i boot with the old 3.10.0-123.20.1 kernel then everything is working. if i boot with the new latest 7.1 kernel-3.10.0-229.1.2 X don't even start. which is the opposite then what i expect. in xorg's log: [ 196.943] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 196.943] (EE) NVIDIA: system's kernel log for additional error messages and [ 196.943] (EE) NVIDIA: consult the NVIDIA README for details. [ 196.943] (EE) No devices detected. but i can't see anything in the system log. anybody has any tipp? You need kmod-nvidia-346.47-2.el7 for EL 7.1 as stated in the announcement. Akemi Yes, you just need to 'yum update kmod-nvidia' to the latest release. it's tricky since the new kmod package in the directory but not in the repo (ie yum update not working for me although az rpm -Uvh is...) thanks anyway. -- Levente Si vis pacem para bellum! ___ elrepo mailing list elrepo@lists.elrepo.org http://lists.elrepo.org/mailman/listinfo/elrepo
[elrepo] zfs kmod rpms
hi, anybody working on zfs kmod rpms for el6/7 system? there are only dkms rpms on http://zfsonlinux.org/ but as most of our kmods are not dkms i'd like to use kmod rpms. ps. anyway anybody has any experience with zfs on linux in production? thanks in advance. regards. -- Levente Si vis pacem para bellum! ___ elrepo mailing list elrepo@lists.elrepo.org http://lists.elrepo.org/mailman/listinfo/elrepo
