Re: SL 4.x problems with ATI fglrx after kernel-update
Hi all we currently have no real RedHat or CentOS systems running at Aachen. So, we cannot check if the problem with the drivers is ScientificLinux-made or a general problem of this kernel version. This seems to be generic problem with the -78.0.22.EL kernel (-89.EL too BTW): we see it as well here at CERN Unfortunately we are not able to find any fix/workaround: so far we tested the catalyst 9.5/9.4/9.3/9.2/9.1/8.8/8.7/ 8.28.8 fglrx driver and none works on SL(C)4 anymore. (Also none of fglrx driver versions we've tested - 9.5/9.4/9.2/8.7 - works on SL(C)5 with kernel -128.1.10.el5) So if anybody on this list got a version of fglrx that works: please let others know... As for unresolved symbols in driver: this is due to picking up wrong fglrx X11 driver version from ATI/AMD package: ie not the one for X11 release that 4 uses: x710 Cheers Jarek PS: We've asked RedHat about and they also do not know which version(s) of fglrx could work on 4/5 ... __ --- _ Jaroslaw_Polok ___ CERN - IT/FIO/LA _ _ http://home.cern.ch/~jpolok ___ tel_+41_22_767_1834 _ _ +41_78_792_0795 _
Re: SL 4.x problems with ATI fglrx after kernel-update
Hi, we currently have no real RedHat or CentOS systems running at Aachen. So, we cannot check if the problem with the drivers is ScientificLinux-made or a general problem of this kernel version. Michael. Troy Dawson schrieb: Hi All, Is this happening with CentOS and real RedHat systems as well? Has anyone tried using one of their kernels? I just want to make sure that it isn't something we did. Troy Matthias Schroeder wrote: Hi, I have no answer to your questions, but we have problems with the .22 kernel and ati-gflrx drivers. For some machines the screen simply stays black, and X is completely stuck. Apparently while initialising the hardware acceleration. Disabling that gives you a working X, but slow is not the right description... One workaround is to use the vesa driver, but I already had complaints about the limited resolution :( In our case the unresolved 'floor' also gets mentioned when we boot with the old kernel (and get a working X). Matthias Michael Bontenackels wrote: Hello, we encountered a problem with the newest kernel for SL 4.x on our institute cluster: after installing the new kernel-smp-2.6.9-78.0.22.EL.i686 on our machines the ATI Catalyst 9.3/9.4 drivers crash when X is started. All kernel modules have been rebuilt suiting to the new kernel. The Xorg.0.log shows following error messages: . (WW) fglrx(0): Only one display is connnected,so single mode is enabled Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbPictureInit from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. Fatal server error: Caught signal 11. Server aborting . Switching back to kernel 2.6.9-78.0.17.EL or even much older versions and rebuilding the fglrx kernel modules works fine. Does anyone know what has happend to the new kernel? Why can the symbols (I guess they have something to do with framebuffer access) not be resolved with the newest kernel update? Actualy I would expect bug-fixes to be included in the new kernels but no changes of interfaces etc. Any ideas (or new kernel version) are welcome. Cheers, Michael. -- --- Dipl.-Phys. Michael Bontenackels III. Physikalisches Institut A Phone +49 241 80 27285 Office 28A221 Fax +49 241 80 22189 III. Physikalisches Institut B Phone +49 241 80 27281 Office 28A206 Fax +49 241 80 22244 RWTH Aachen Physikzentrum Otto-Blumenthal-Straße 52074 Aachen Germanybontenack...@physik.rwth-aachen.de -- private Michael Bontenackels Phone +49 241 4459858 Haßlerstraße 7-9 Mobile +49 178 1488219 52066 Aachen Fax+49 1212 515369028 Germany michael.bontenack...@gmx.de ---
SL 4.x problems with ATI fglrx after kernel-update
Hello, we encountered a problem with the newest kernel for SL 4.x on our institute cluster: after installing the new kernel-smp-2.6.9-78.0.22.EL.i686 on our machines the ATI Catalyst 9.3/9.4 drivers crash when X is started. All kernel modules have been rebuilt suiting to the new kernel. The Xorg.0.log shows following error messages: . (WW) fglrx(0): Only one display is connnected,so single mode is enabled Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbPictureInit from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. Fatal server error: Caught signal 11. Server aborting . Switching back to kernel 2.6.9-78.0.17.EL or even much older versions and rebuilding the fglrx kernel modules works fine. Does anyone know what has happend to the new kernel? Why can the symbols (I guess they have something to do with framebuffer access) not be resolved with the newest kernel update? Actualy I would expect bug-fixes to be included in the new kernels but no changes of interfaces etc. Any ideas (or new kernel version) are welcome. Cheers, Michael. -- --- Dipl.-Phys. Michael Bontenackels III. Physikalisches Institut A Phone +49 241 80 27285 Office 28A221 Fax +49 241 80 22189 III. Physikalisches Institut B Phone +49 241 80 27281 Office 28A206 Fax +49 241 80 22244 RWTH Aachen Physikzentrum Otto-Blumenthal-Straße 52074 Aachen Germanybontenack...@physik.rwth-aachen.de -- private Michael Bontenackels Phone +49 241 4459858 Haßlerstraße 7-9 Mobile +49 178 1488219 52066 Aachen Fax+49 1212 515369028 Germany michael.bontenack...@gmx.de ---
Re: SL 4.x problems with ATI fglrx after kernel-update
Hi, I have no answer to your questions, but we have problems with the .22 kernel and ati-gflrx drivers. For some machines the screen simply stays black, and X is completely stuck. Apparently while initialising the hardware acceleration. Disabling that gives you a working X, but slow is not the right description... One workaround is to use the vesa driver, but I already had complaints about the limited resolution :( In our case the unresolved 'floor' also gets mentioned when we boot with the old kernel (and get a working X). Matthias Michael Bontenackels wrote: Hello, we encountered a problem with the newest kernel for SL 4.x on our institute cluster: after installing the new kernel-smp-2.6.9-78.0.22.EL.i686 on our machines the ATI Catalyst 9.3/9.4 drivers crash when X is started. All kernel modules have been rebuilt suiting to the new kernel. The Xorg.0.log shows following error messages: . (WW) fglrx(0): Only one display is connnected,so single mode is enabled Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbPictureInit from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. Fatal server error: Caught signal 11. Server aborting . Switching back to kernel 2.6.9-78.0.17.EL or even much older versions and rebuilding the fglrx kernel modules works fine. Does anyone know what has happend to the new kernel? Why can the symbols (I guess they have something to do with framebuffer access) not be resolved with the newest kernel update? Actualy I would expect bug-fixes to be included in the new kernels but no changes of interfaces etc. Any ideas (or new kernel version) are welcome. Cheers, Michael.
Re: SL 4.x problems with ATI fglrx after kernel-update
Hi All, Is this happening with CentOS and real RedHat systems as well? Has anyone tried using one of their kernels? I just want to make sure that it isn't something we did. Troy Matthias Schroeder wrote: Hi, I have no answer to your questions, but we have problems with the .22 kernel and ati-gflrx drivers. For some machines the screen simply stays black, and X is completely stuck. Apparently while initialising the hardware acceleration. Disabling that gives you a working X, but slow is not the right description... One workaround is to use the vesa driver, but I already had complaints about the limited resolution :( In our case the unresolved 'floor' also gets mentioned when we boot with the old kernel (and get a working X). Matthias Michael Bontenackels wrote: Hello, we encountered a problem with the newest kernel for SL 4.x on our institute cluster: after installing the new kernel-smp-2.6.9-78.0.22.EL.i686 on our machines the ATI Catalyst 9.3/9.4 drivers crash when X is started. All kernel modules have been rebuilt suiting to the new kernel. The Xorg.0.log shows following error messages: . (WW) fglrx(0): Only one display is connnected,so single mode is enabled Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbGetWinPrivateIndex from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! Symbol fbPictureInit from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved! *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. Fatal server error: Caught signal 11. Server aborting . Switching back to kernel 2.6.9-78.0.17.EL or even much older versions and rebuilding the fglrx kernel modules works fine. Does anyone know what has happend to the new kernel? Why can the symbols (I guess they have something to do with framebuffer access) not be resolved with the newest kernel update? Actualy I would expect bug-fixes to be included in the new kernels but no changes of interfaces etc. Any ideas (or new kernel version) are welcome. Cheers, Michael. -- __ Troy Dawson daw...@fnal.gov (630)840-6468 Fermilab ComputingDivision/LCSI/CSI LMSS Group __
