|
Bugzilla – Full Text Bug Listing |
| Summary: | Yast2 Online Update Does Not Recognize when newer fglrx driver is installed. | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | David Rankin <drankinatty> |
| Component: | YaST2 | Assignee: | E-mail List <bnc-team-screening> |
| Status: | RESOLVED INVALID | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | meissner, sndirsch |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | openSUSE 11.0 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
Not sure what you expect here. If you've added the ATI repo you should be happy that the RPMs are installed and updated when there is a new driver available through this repo. If you prefer to install the driver manually remove the ATI repo and the RPMs from this repo, which have been installed before. We do not support a mixed scenario as you're trying to use. Well,
I thought you would like to make openSuSE better by making it "aware" of the fglrx driver that for the past year you have encouraged openSuSE users to install until belatedly the build service started catching up on driver versions. Generally the build service is 3 weeks to 2 months behind on the fglrx driver. Present example, 5.01 has been out for quite a while, but the build service is still stuck on 4.9x.
Further, Yast's behavior with regard to the fglrx driver has changed dramatically in the past month. Prior to the last kernel update, Yast would at least accommodate the fglrx driver on kernel updates by not forcing the install of, or downgrade to, whatever fglrx driver happens to be in the build service at the time of a kernel update. In the past the kernel update has simply ignored the driver and installed the new kernel simply resulting in the need for the kernel module being rebuilt.
As I detailed above, now you are forced to take the build service driver as a mandatory dependency without the ability to decline the driver update. That's not the way it should work. That's just a sloppy side effect. If this is the way you want it to work - fine. Being a change that effects ATI driver users, I thought I would bring it to the devs attention so it could be fixed instead of being swept under the rug and something that causes problems later.
(In reply to comment #2 from David Rankin) > I thought you would like to make openSuSE better by making it "aware" of > the fglrx driver that for the past year you have encouraged openSuSE users to > install until belatedly the build service started catching up on driver > versions. Generally the build service is 3 weeks to 2 months behind on the > fglrx driver. Present example, 5.01 has been out for quite a while, but the > build service is still stuck on 4.9x. You're talking about the ATI repo on the ATI server. Please do not mix this up with openSUSE's buildservice. Reason for this delay is that driver updates are synced with SLES10, which gets better testing. And driver updates to the ATI repo can not happen more often than every 6 weeks. :-( > Further, Yast's behavior with regard to the fglrx driver has changed > dramatically in the past month. Prior to the last kernel update, Yast would > at least accommodate the fglrx driver on kernel updates by not forcing the > install of, or downgrade to, whatever fglrx driver happens to be in the build > service at the time of a kernel update. In the past the kernel update has > simply ignored the driver and installed the new kernel simply resulting in > the need for the kernel module being rebuilt. I'm not aware of an kABI incompatible kernel update for openSUSE 11.0. Marcus, did I miss something here? It had this diff, so just additions or unrelated symbols. --- /suse/meissner/projects/kabi/11.0/GA/i386/kernel-pae 2008-06-23 10:43:59.105177000 +0200 +++ 20080713184828/i386/kernel-pae 2008-07-16 08:57:04.119241000 +0200 @@ -47,6 +47,7 @@ kernel(pae:drivers_media_dvb_frontends) = a81d6af8931f10f7 kernel(pae:drivers_media_dvb_ttpci) = b8fe4bb84ce0dd80 kernel(pae:drivers_media_dvb_ttusb_dec) = f2e761e7d7e146cd +kernel(pae:drivers_media_video) = 24289f12c490f684 kernel(pae:drivers_media_video) = 5902a1b7269c64ac kernel(pae:drivers_media_video_bt8xx) = e7a3e8ee97d06835 kernel(pae:drivers_media_video_cx23885) = 9411c85806c5e8e2 @@ -122,7 +123,7 @@ kernel(pae:fs_nfsd) = 92ce6ee3a8b725e5 kernel(pae:fs_ocfs2_cluster) = 838047191455df16 kernel(pae:fs_ocfs2_dlm) = 220e57a5cbb35317 -kernel(pae:fs_xfs) = 00f0f843bf8b1893 +kernel(pae:fs_xfs) = 9624bb6cd2f8e5ee kernel(pae:lib) = 2d6b50809dab072c kernel(pae:lib_lzo) = 95ba81faa389aa2a kernel(pae:lib_reed_solomon) = f1cfc4ea13a81ec6 @@ -180,4 +181,5 @@ kernel(pae:sound_synth) = fd0f5030641c58d3 kernel(pae:sound_synth_emux) = af75bbfeadf91295 kernel(pae:sound_usb) = 6123fbc9bae19be2 +kernel(pae:vmlinux) = 19ac3fde1eb13345 kernel(pae:vmlinux) = 39aba59bbc026c1f Indeed. On 11.0 we're still kABI compatible. # rpm --requires -qp ati-fglrxG01-kmp-pae-8.501_2.6.25.5_1.1-0.1.i586.rpm kernel(pae:vmlinux) = 39aba59bbc026c1f kernel(pae:drivers_char_agp) = 03dd4e9dc2a83744 Guys,
As long as you all understand it, and it's OK, then that's all we can do. I know not what the comments above say, but at least this issue has received good deliberation. The kicker is the mandatory dependency the kernel update imposes on the ATI driver. Seems strange, but if that's the way it has to work, then so it is. It just seems the user should have the right to say, "I'll take the kernel update, but 'no thanks' to the driver." Thanks for looking at the issue.
Well, YaST tries to keep a consistent system, so you still have network/X11 - or whatever external KMPs you're using - after reboot. We just verified that the current ATI KMPs you can download from the ATI repo still match our openSUSE 11.0 kernel (updates) and it does. So you shouldn't run into this issue at all. Hope this helps. |
Devs, (Stefan) Yast online update or zypper up, neither recognize when a newer ati fglrx driver is installed from the ATI package (example: ati-driver-installer-8-6-x86.x86_64.run) and an update using yast or zypper downgrades the fglrx driver. This happens when a new kernel is released, etc. An "update" should not "downgrade" software. In the case of the fglrx driver, yast should check for the existence of the driver installed from the driver-installer package, such as fglrx64_7_1_0_SUSE103-8.501-1.x86_64.rpm and if found, should simply run /usr/bin/fglrx-kernel-build.sh as a post-install script instead of forcing the downgrade. Additionally, when install of the FGLRX driver is triggered as a "dependency" the user should be given the option of saying NO to the auto install of the older driver (or any package for that matter). However, currently, on a kernel update there is no way to say NO to an auto-dependency. Thanks. If you need any additional information, please just ask and I'll be happy to send.