[elrepo] Latest Fglrx Drivers
dominic at dcrdev.com
dominic at dcrdev.com
Wed Oct 28 08:58:34 EDT 2015
As I mentioned I'd be willing to test as well, if needs be I can give
you remote access to a machine as well.
Probably a naive question but since fglrx 15.9 has RHEL 7.1 support out
of the box, shouldn't it be compatible with systemd? Or is there
something specific that has to happens with the kmod drivers, that
differ from the AMD installer?
On 2015-10-27 16:00, elrepo-request at lists.elrepo.org wrote:
> Send elrepo mailing list submissions to
> elrepo at lists.elrepo.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.elrepo.org/mailman/listinfo/elrepo
> or, via email, send a message with subject or body 'help' to
> elrepo-request at lists.elrepo.org
>
> You can reach the person managing the list at
> elrepo-owner at lists.elrepo.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of elrepo digest..."
>
>
> Today's Topics:
>
> 1. Re: Latest Fglrx Drivers (Manuel Wolfshant)
> 2. Re: after kmod-nvidia el7 update during boot still use the
> old kmod (Phil Perry)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 26 Oct 2015 21:51:39 +0200
> From: Manuel Wolfshant <wolfy at nobugconsulting.ro>
> To: EL Repo General Mailing List <elrepo at lists.elrepo.org>
> Subject: Re: [elrepo] Latest Fglrx Drivers
> Message-ID: <CB1B96BE-4E82-4B88-894F-3EE6823C7D35 at nobugconsulting.ro>
> Content-Type: text/plain; charset=UTF-8
>
> On 26 octombrie 2015 21:19:29 EET, "Williams, Roy" <rwilli95 at uncc.edu>
> wrote:
>> Hello Manuel,
>>
>> Is it a problem you don't have a machine to test against?
> Exactly
>
>
>> I can provide
>> access to a machine to test against remotely, not sure what kind of
>> testing
>> you currently do under EL6.
> Thank you for your ofer. What I need is to [literally] see that
> - the PC boots
> - it enters runlevel 5
> - X stsrts succesfuly
> - the desktop env of choice starts sucessfully
> With the current packages, the last 2 steps do not always happen. I
> have a feeling tgar there is a race between ATI's daemon and
> "something" else (I suspect acpid). Due to this problem the user is
> presented with a black screen, leaving the impression that the system
> is frozen. IIRC from my tests,one can switch to a text console,
> restart ATI's daemon and X continues its normal startup process. But
> this is obviously not the normal&desired approach. While I still had a
> "victim" to test on I tried playing with the service file that I had
> written for the daemon but unfortunately I had to install EL6 on that
> PC and hand it to its user prior to reaching a satisfactory result.
> And I have zero incentive so far to make friends with systemd so I do
> not know how to solve the problem.
>
>
>> We actually have a need for the fglrx
>> driver
>> under EL7 for our environment.
>>
> If you are willing to test, I could provide updated packages for
> testing purposes by the end of this week, but with no guarantees
> regarding the problem that I detailed earlier
>
>> Regards,
>> Roy
>>
>> On Mon, Oct 26, 2015 at 1:06 PM, Manuel Wolfshant
>> <wolfy at nobugconsulting.ro>
>> wrote:
>>
>>> On 26 octombrie 2015 18:14:31 EET, dominic at dcrdev.com wrote:
>>> >I don't suppose there's any chance of an el7 package? I'd be more
>> than
>>> >willing to test it!
>>> >
>>> You can find a test package (newer than what's in elrepo's testing
>> but
>>> older than what ATI currently ships) on my personal website,
>>> wdl.lug.ro/fglrx
>>> I could update to the new ATI release pretty soon but my problem is
>> that I
>>> am afraid that the incompatibility between atidaemon and systemd will
>> still
>>> be there. And I have no system to experiment with, our ecosystem is
>> EL6.
>>>
>>>
>>> >Thanks,
>>> >
>>> >
>>> >On 2015-10-26 16:00, elrepo-request at lists.elrepo.org wrote:
>>> >> Send elrepo mailing list submissions to
>>> >> elrepo at lists.elrepo.org
>>> >>
>>> >> To subscribe or unsubscribe via the World Wide Web, visit
>>> >> http://lists.elrepo.org/mailman/listinfo/elrepo
>>> >> or, via email, send a message with subject or body 'help' to
>>> >> elrepo-request at lists.elrepo.org
>>> >>
>>> >> You can reach the person managing the list at
>>> >> elrepo-owner at lists.elrepo.org
>>> >>
>>> >> When replying, please edit your Subject line so it is more
>> specific
>>> >> than "Re: Contents of elrepo digest..."
>>> >>
>>> >>
>>> >> Today's Topics:
>>> >>
>>> >> 1. Latest Fglrx Drivers (dominic at dcrdev.com)
>>> >> 2. Re: Latest Fglrx Drivers (Manuel Wolfshant)
>>> >>
>>> >>
>>> >>
>>>
>>> ----------------------------------------------------------------------
>>> >>
>>> >> Message: 1
>>> >> Date: Mon, 26 Oct 2015 10:48:44 +0000
>>> >> From: dominic at dcrdev.com
>>> >> To: elrepo at lists.elrepo.org
>>> >> Subject: [elrepo] Latest Fglrx Drivers
>>> >> Message-ID: <b36ee586ea9d247a82ae72345b88ec40 at dcrdev.com>
>>> >> Content-Type: text/plain; charset=US-ASCII; format=flowed
>>> >>
>>> >> Hi,
>>> >>
>>> >> I'm in the process of migrating to CentOS - my system has a recent
>>> >AMD
>>> >> APU and am looking to install the fglrx driver.
>>> >>
>>> >> I noticed that kmod-fglrx is no longer in the main repo, but only
>> in
>>> >> the
>>> >> "testing" repo.
>>> >>
>>> >> Is fglrx still being maintained, if so are there any plans to
>> package
>>> >a
>>> >> more up-to-date version i.e. the 15.x series?
>>> >>
>>> >> Thanks,
>>> >>
>>> >>
>>> >> ------------------------------
>>> >>
>>> >> Message: 2
>>> >> Date: Mon, 26 Oct 2015 12:52:10 +0200
>>> >> From: Manuel Wolfshant <wolfy at nobugconsulting.ro>
>>> >> To: EL Repo General Mailing List <elrepo at lists.elrepo.org>
>>> >> Subject: Re: [elrepo] Latest Fglrx Drivers
>>> >> Message-ID: <562E05DA.10506 at nobugconsulting.ro>
>>> >> Content-Type: text/plain; charset=windows-1252; format=flowed
>>> >>
>>> >> On 10/26/2015 12:48 PM, dominic at dcrdev.com wrote:
>>> >>> Hi,
>>> >>>
>>> >>> I'm in the process of migrating to CentOS - my system has a
>> recent
>>> >AMD
>>> >>> APU and am looking to install the fglrx driver.
>>> >>>
>>> >>> I noticed that kmod-fglrx is no longer in the main repo, but only
>> in
>>> >>> the "testing" repo.
>>> >>>
>>> >>> Is fglrx still being maintained, if so are there any plans to
>>> >package
>>> >>> a more up-to-date version i.e. the 15.x series?
>>> >>
>>> >> I am maintaining it but since I do not have in use any system
>> running
>>> >> EL7, I have pushed updates only for EL6.
>>> >> http://lists.elrepo.org/pipermail/elrepo/2015-July/002677.html --
>> I
>>> >am
>>> >> using these packages on the system I am mailing from in this
>> moment
>>> >>
>>> >>
>>> >>
>>> >> ------------------------------
>>> >>
>>> >> _______________________________________________
>>> >> elrepo mailing list
>>> >> elrepo at lists.elrepo.org
>>> >> http://lists.elrepo.org/mailman/listinfo/elrepo
>>> >>
>>> >>
>>> >> End of elrepo Digest, Vol 76, Issue 17
>>> >> **************************************
>>> >
>>> >_______________________________________________
>>> >elrepo mailing list
>>> >elrepo at lists.elrepo.org
>>> >http://lists.elrepo.org/mailman/listinfo/elrepo
>>>
>>>
>>> _______________________________________________
>>> elrepo mailing list
>>> elrepo at lists.elrepo.org
>>> http://lists.elrepo.org/mailman/listinfo/elrepo
>>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> elrepo mailing list
>> elrepo at lists.elrepo.org
>> http://lists.elrepo.org/mailman/listinfo/elrepo
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 26 Oct 2015 23:00:03 +0000
> From: Phil Perry <phil at elrepo.org>
> To: elrepo at lists.elrepo.org
> Subject: Re: [elrepo] after kmod-nvidia el7 update during boot still
> use the old kmod
> Message-ID: <562EB073.8040604 at elrepo.org>
> Content-Type: text/plain; charset=windows-1252
>
> On 26/10/15 19:20, Farkas Levente wrote:
>> 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?
>>
>
> The nvidia drivers are comprised of a two package set - the kernel
> module provided by kmod-nvidia and the X11 driver package,
> nvidia-x11-drv.
>
> Because we do quite a bit of scripting in %post, we prefer to keep it
> all together in one place so one can clearly see everything that is
> happening - this makes it easier to maintain. It's simply easier to do
> this in the conventional nvidia-x11-drv package rather than the
> kmod-nvidia package, where any scripts would need to go into kmodtool.
> This choice is reinforced by our policy to try to keep our kmodtool as
> close as possible to that shipped by Red Hat. So that's the reasons we
> prefer the scripting to be done in the nvidia-x11-drv package. However,
> we can use kmodtool if necessary, but I would prefer not for the
> reasons
> given above.
>
>> anyway i still don't know why this do not properly set my initramfs
>> during update.
>>
>
> Me neither. We need to figure this out before we can fix it.
>
> Did you try uninstalling, and reinstalling?
>
> The weak-modules script is supposed to compare the list of modules
> before and after by md5 checksum to determine if they have changed and
> thus whether to install a new initramfs. If the old nvidia module is
> still in the initramfs and the initramfs isn't being updated then it
> would appear there is possibly a bug in either weak-modules or dracut.
>
>> but thanks you solve my problem:-)
>>
>
> Well we worked around it. I would prefer to figure out why it happened
> in the first place and if necessary prevent it from happening.
>
>
>
>
> ------------------------------
>
> _______________________________________________
> elrepo mailing list
> elrepo at lists.elrepo.org
> http://lists.elrepo.org/mailman/listinfo/elrepo
>
>
> End of elrepo Digest, Vol 76, Issue 19
> **************************************
More information about the elrepo
mailing list