http://bugzilla.rpmfusion.org/show_bug.cgi?id=171
--- Comment #35 from NicolasChauvet <kwizart(a)gmail.com> 2009-01-26 16:20:03 ---
(In reply to comment #33)
> (In reply to comment #32)
> ...
> > * Every files the tool expect to edit will have to be owned by the package :
> > %ghost %{_sysconfdir}/modprobe.d/%{name}
> > %ghost %{_sysconfdir}/modprobe.d/ld.so.conf.d/%{name}.conf
> > %ghost %{_sysconfdir}/udev/makedev.d/40-%{name} (if needed)
> and
> %ghost %{_sysconfdir}/acpi/actions/ati-powermode.sh (which can cause lot of
> hurt if radeon/nvidia is been used.)
Packaging whole scripts for a driver isn't possible at the moment. Although it
could be, I think this is better off in the xorg-x11-drv-fglrx package anyways.
I
would put a BIG FAT WARNING ON this particular topic.
This isn't needed to remove the hardcoded blacklist-radeon on fglrx install if
we don't remove access to theses scripts. I meant this is a HIGHER LEVEL RISK
to have theses scripts runned while radeon is been used.
Here is what chery picking of problems I've runned into, when I tried to move
from radeon/fglrx.
- vga cannot be used the same as fglrx while using radeon (because of kernel
modesettings ?). If vga mode is specified on grub, we cannot run in radeon
mode. If possible, we need to go to fglrx, or worse, falback to vesa.
- screensaver doesn't quit to segfault, even if the ATI vendor scripts specific
to fglrx are removed.
- While using radeon but radeon isn't present in the initrd kernel image, fglrx
seems to be loaded anyway if not in blacklisted in
blacklist-rpmfusion-config-display (or else). This leads to have Xorg loading
to fail very badly.
--
Configure bugmail:
http://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.