Is it safe to upgrade to Kernel 3.0.4-2.1??? (fglrx/ATI related!!)

So, I have a ATI M. Radeon HD 3650 Graphic Card and the official fglrx driver installed.
The installation said: “Postprocessing Kernel Module…”, I don’t know what this mean :\

My question now is: Should I update from Kernel Version 2.6.37.6-0.7-desktop x86_64 to 3.0.4-2.1-desktop x86_64 :
I’m not sure if aticonfig --initial will work or something other horrible will be happen…
I won’t broke my System!

What should I do? pls help me

2D Driver Version (fglrx): 8.86.5
3D Driver Version (ATI/OpenGL): 3.3.10831

EDIT: I think I should add this information

the fglrx driver NEVER worked with kernel version 2.6.37.6-0.5 but with 2.6.37.6-0.7
strange or not?


cannot edit my post, the limit of 10 minutes is over :open_mouth:

It did for sure work with both kernels. I have absolutely no doubt about that. You simply didn’t have the kernel sources installed for kernel 2.6.37.6-0.5 and so boot.fglrxrebuild could not compile the module. That would explain why it didn’t work.
I don’t know what you mean by “official fglrx driver” though. The one installed with atiupgrade is always the latest released by ATI. As I’m not using kernel 3.0.x, I can not tell for sure if it’s going to work. I assume it could. atiupgrade would install the kernel sources and compiler for you if they are missing an run aticonfig --initial for you if it is needed. This command simply adds a Driver entry in the Device section of xorg.conf, really not a big deal. You don’t have to be afraid of it.

so upgrading is safe,
but how to re-compile the fglrx kernel module after a kernel upgrade
the ati installer from the amd website is a gui, so it needs X to be running

i have also a xorg.conf with the open source radion driver
would x start with the radeon driver, so that i can re-install (re-compile) the fglrx kernel module from gui
or is there a terminal way too? will aticonfig --initial re-compile something or not?

btw, i’m plan to install this kernel Index of /repositories/Kernel:/stable
so no problems, because they are from the opensuse website :slight_smile: right?

I cannot tell you anything about the ati GUI installer (and about GUI installers in general). Just install and run atiupgrade following the method in the link I provided. This is all you need. Notice that I don’t know if fglrx works with kernel 3.x. You’ll find out.

Fine! atiupgrade will see that and run aticonfig --initial for you.

If you don’t have fglrx already loaded, you can do everything in one step and in X. The command you need to type (as root) is

atiupgrade

If you had another (older) version of fglrx installed and loaded, the method is the same, except that you’ll have to run atiupgrade twice, the second time after exiting X or rebooting in runlevel 3.

It is explained in details in the howto. Whether in X in a terminal or in console, you never have anything else to type but atiupgrade. It could be hardly simpler than that.

aticonfig doesn’t compile anything. It justs create/replace the driver in the xorg.conf Device section.
**After a kernel update, the service /etc/init.d/boot.fglrxrebuild will recompile the module. This service is started before entering X runlevel. You don’t need to do anything. **

I can not answer this question, since I don’t know this kernel. atiupgrade needs to install the kernel sources. It will if they are available in a repo which is installed, enabled and up to date. Once you have a kernel + kernel sources installed, the kernel sources should get updated together with the kernel, and so /etc/init.d/boot.fglrxrebuild will be able to rebuild the module at the next boot after each kernel update.

Again, this is all generaly speaking. I don’t know if there are particular issues with this kernel. But I don’t see why it would be a problem. If for some reason, fglrx doesn’t work for you, simply switch back to the radeon driver. Installing Catalyst with atiupgrade (or with another method) is not dangerous. Better use atiupgrade, because it will create an install a rpm package that you could uninstall like any other package if ever you need to.

a last question: where to get atiupgrade?

linux-5ahv:~ # atiupgrade
If 'atiupgrade' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    cnf atiupgrade
linux-5ahv:~ # cnf atiupgrade
atiupgrade: command not found                           
linux-5ahv:~ # zypper install atiupgrade
Loading repository data...
Reading installed packages...
'atiupgrade' not found in package names. Trying capabilities.
No provider of 'atiupgrade' found.
Resolving package dependencies...

Nothing to do.
linux-5ahv:~ # 

I think we do write howtos in the hope not to have to answer the same questions again and again one by one … but it never happens that way.
So what do you read here openSUSE Forums - ATI driver with atiupgrade in the comprehensive guide under Installing atiupgrade?
Use the first method: installing from repo. You’ll get the latest version of the script installed in /usr/bin.

i just found it, before you could replay, sorry
and thanks for you help please_try_again

i will post my results

yeah lol!
the upgrade to version 3.0.4-2.1 was successfully!!!
i had absolutely no problems
and there was also an update of the ati driver from version 11.6 to 11.8

but now the vmware workstation no longer works, but this is another problem

100% SOLVED

also found a vmware patch for kernel 3.0.3 and higher
vmware workstation works again!

Thank you for your feedback. I assumed it would work with this kernel (more precisely I couldn’t think why it would not) but I hadn’t tested it. Now we know it does.

Does this apply aswell if one updates xorg server?

I don’t see why it wouldn’t.

Is this an atiupgrade feature or what?

I seem to recall that when installing the catalysts through the hard way, if one updated kernel or xorg, it would end up with a broken driver.

If you update the kernel, it should not be a problem (anymore), thanks to the script /etc/init.d/boot.fglrxrebuild - which is part of the fglrx package. It will rebuild the module after a kernel update. This is not an atiupgrade feature. It is just included in the package that you can create with atiupgrade (or by running the ati run file “the hard way”).

I you update xorg … well, it depends on the libraries which will get replaced. The ones fglrx needs can be listed with ldd:

# find /usr/X11R6/lib* -type f -name "*fglrx*" -exec ldd "{}" ";"   
        not a dynamic executable
        linux-gate.so.1 =>  (0xffffe000)
        libc.so.6 => /lib/libc.so.6 (0xf7540000)
        /lib/ld-linux.so.2 (0xf76e6000)
        linux-gate.so.1 =>  (0xffffe000)
        libpthread.so.0 => /lib/libpthread.so.0 (0xf75cf000)
        libXext.so.6 => /usr/lib/libXext.so.6 (0xf75bd000)
        libm.so.6 => /lib/libm.so.6 (0xf7593000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xf7575000)
        libc.so.6 => /lib/libc.so.6 (0xf7407000)
        libdl.so.2 => /lib/libdl.so.2 (0xf7402000)
        /lib/ld-linux.so.2 (0xf770b000)
        libX11.so.6 => /usr/lib/libX11.so.6 (0xf72c5000)
        libxcb.so.1 => /usr/lib/libxcb.so.1 (0xf72a5000)
        libXau.so.6 => /usr/lib/libXau.so.6 (0xf72a1000)
        not a dynamic executable
        linux-vdso.so.1 =>  (0x00007fffd549e000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f1112c97000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f111313d000)
        linux-vdso.so.1 =>  (0x00007fffa5f39000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f238a04a000)
        libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007f2389e36000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f2389ac9000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f238a4a5000)
        libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f2389786000)
        libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f2389568000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f2389364000)
        libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f2389160000)

# find /usr/lib*/xorg/modules -type f -name "*fglrx*" -exec ldd "{}" ";"
        linux-vdso.so.1 =>  (0x00007fff815ff000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fa9aabbb000)
        librt.so.1 => /lib64/librt.so.1 (0x00007fa9aa9b1000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007fa9aa7ad000)
        libm.so.6 => /lib64/libm.so.6 (0x00007fa9aa556000)
        libc.so.6 => /lib64/libc.so.6 (0x00007fa9aa1e8000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fa9abd77000)
        linux-vdso.so.1 =>  (0x00007fff7afff000)
        libm.so.6 => /lib64/libm.so.6 (0x00007fd7128aa000)
        libc.so.6 => /lib64/libc.so.6 (0x00007fd71253c000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fd712d30000)
        linux-vdso.so.1 =>  (0x00007fff9b7ff000)
        libatiuki.so.1 => /usr/lib64/libatiuki.so.1 (0x00007fc065410000)
        libc.so.6 => /lib64/libc.so.6 (0x00007fc0650a2000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fc06565d000)

If fglrx doesn’t work anymore, try to rebuild and reinstall the package with atiupgrade (it’s faster than doing it “the hard way” but comes to the same).