https://bugzilla.novell.com/show_bug.cgi?id=408205 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=408205#c1 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #1 from Stefan Dirsch 2008-07-15 04:47:02 MDT --- 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408205 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=408205#c3 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@novell.com --- Comment #3 from Stefan Dirsch 2008-07-15 18:34:17 MDT --- (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? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408205 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=408205#c5 --- Comment #5 from Stefan Dirsch 2008-07-16 01:06:19 MDT --- 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 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=408205 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=408205#c7 --- Comment #7 from Stefan Dirsch 2008-07-18 01:30:45 MDT --- 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.