LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Slackware 13 Ati Driver 9.8 - System freeze (http://www.linuxquestions.org/questions/slackware-14/slackware-13-ati-driver-9-8-system-freeze-751452/)

vbisis 08-31-2009 05:53 AM

Slackware 13 Ati Driver 9.8 - System freeze
 
Hi everybody,

I just installed Slackware 13 ( tried both 32 bit ( kernel recompiled for pae support - I own 8 GB of ram ) and 64 bit ).

Evertime I install ATI-Driver my system freezes on "startx", with a white non-blinking cursos in the left upper corner.
I tried driver version 9.7 with patch and 9.8.
Both install without any problem and module is loaded without any complains.
I don't see anything related to the crash in either X.org0.log or messages, but the only thing to get my System back to life is to press the reboot-button.
Ctrl-ALt-delete doesn't work and I can't switch to another console.
Keyboard doesn't react to pressing "num-lock" or anything else, but the keyboard-leds aren't blinking either ....

Anyone an idea? At least to see some error or something which might help fix the problem?

Best regards,

isis

Bller 08-31-2009 06:39 AM

Thats why i`m so scared of installing any ATI drivers on my PC :)) as long as i have openGL i think i can live with 1024x768 although i really dislike it, `cose i`m used to 1280x1024.

forum1793 08-31-2009 07:37 AM

What motherboard do you have?

What graphics card do you have?

Did you compile your own kernel and enable the msi stuff?

I don't remember what pae is. The last kernel I compiled, I tried enabling PAT (in the mtrr area) and the ati drivers would not work. If you did that, turn PAT back off and recompile.

kernel-P4N1C 08-31-2009 08:28 AM

It happened to me several times too on 32 bit with pae and 64 bit current (before 13 was release)

try running as root aticonfig --initial or something (when you installed the driver it said exactly what to do; or checking the aticonfig help may tell you)

hint: copy the xorg.conf-vesa file to xorg.conf cause the script need that file to exist.

vbisis 08-31-2009 08:43 AM

Hi,

I have a sapphire 4870 HD 512 MB GDDR5 and an asrock Board ALiveXFire-eSATA2 R3.0 with AMD 480X CrossFire Chipset.
I did aticonfig --initial and it gave me no complains as well.

I compile my own 32bit Kernel ( only option changed to hugesmp.s was to enable 64 GB mem support, and on generic-smp-kernel I added support for ext3 and jfs filesystem and 64 GB memory support )

For 64bit slackware I used huge kernel as it is shipped, because my 8 GB of RAM are recognized there.

On Slackware 12.2 the last working driver was 8.7 on a kernel 2.6.27 if that helps.
Didn't update but reinstall my system because I thought, I somehow managed to break something again.
So my problem occurs on a quite a stock Slackware 13, both 64 and 32 bit.

Best regards,

Isis

forum1793 08-31-2009 09:26 PM

Your hardware is relatively new. Catalyst 8.7 is first time I see hd4000 series showing up.

If you had this hardware working in slackware 12.2 it should definitely work in 13.0.

Because I'm trying out the open source drivers and because only with the last catalyst could you install it with >2.6.28 kernel, I have and am still using a 2.6.27.xx kernel. As you had that working before you should use it again. Download latest 2.6.27.xx kernel (31 I think) and make custom kernel. For graphics area, turn everything off but maybe agpgart as module if that is an option. Then rerun the catalyst installer. Check out log messages in /usr/share/ati. You will likely need an xorg.conf to load the fglrx driver but at slack13 you should not need mouse or keyboard options in the xorg.conf. You shouldn't need any modelines either as edid should take care of that. Maybe just set the 24 bit. Something like:

Code:

Section "ServerLayout"
        Identifier    "Simple Layout"
        Screen      0  "aticonfig-Screen[0]" 0 0
EndSection

Section "Monitor"
        Identifier  "aticonfig-Monitor[0]"
        Option            "VendorName" "ATI Proprietary Driver"
        Option            "ModelName" "Generic Autodetecting Monitor"
        Option            "DPMS" "true"
EndSection

Section "Device"
        Identifier  "aticonfig-Device[0]"
        Driver      "fglrx"
        Option "VideoOverlay" "off"
        Option "OpenGLOverlay" "off"
        Option "TexturedVideo" "on"

        Option            "XAANoOffscreenPixmaps" "on"
EndSection

Section "DRI"
  mode 0666
EndSection

Section "Screen"
        Identifier "aticonfig-Screen[0]"
        Device    "aticonfig-Device[0]"
        Monitor    "aticonfig-Monitor[0]"
        DefaultDepth    24
        SubSection "Display"
                Viewport  0 0
                Depth    24
        EndSubSection
EndSection

Note I used those options quite a while ago. Not sure they're needed anymore.

amiga32 08-31-2009 09:49 PM

Quote:

Originally Posted by forum1793 (Post 3664764)
Your hardware is relatively new. Catalyst 8.7 is first time I see hd4000 series showing up.

If you had this hardware working in slackware 12.2 it should definitely work in 13.0.

Just for the record, all ATi videocards (RV600+ i.e. HD2400 and up) are supposed to be supported on both 2.6.29.x and 2.6.30.x kernels as of the latest 9.8 catalysts.

Just in case anyone comes across this and is wondering if their videocard is still officially supported by ATi.

jazzor 08-31-2009 11:10 PM

Does anyone happen to use ati 9.8 drivers using --buildpkg Slackware/All?

Do you get the "modules" directory ending up in /usr/lib/modules
rather than /usr/lib/xorg/modules? Maybe it is not even seeing the ati drivers at all (?)

Well, at least thats what happens when I install it, I have to manually move the modules directory to the right spot.

On the other hand, I still cannot get 3d to work, it states that it cannot dlopen ati_fglrx.so or something...

vbisis 09-01-2009 01:31 AM

I did a try some time ago with Slackware -current.

There I used my old xorg.coinf wihich worked great in Slackware 12.2. Well I decided to try now just aticonfig --initial and legt the XServer find out the rest, since it should be supposed to detect the correct settings itself.

Yesterday I installed kernel 2.6.30.5 from testing - same result with Ati-Driver 9.8, startx causes my system to freeze, so I finally uninstalled fglrx-driver.

@jazzor: I don't think it ends up in the wrong folder, because with no fglrx-driver installed XServer starts up just fine.

At slackforum.de we discuss the same issue and it is possible DRM_RADEON is the cause of the trouble. Can someone confirm this? Didn't try so far, I didn't have the time, but I will today, hopefully.

cg132 09-01-2009 02:48 AM

Quote:

Originally Posted by jazzor (Post 3664831)
Does anyone happen to use ati 9.8 drivers using --buildpkg Slackware/All?

when i do that on 9.3 drivers i end up with

Code:

ATI Technologies Linux Driver Installer/Packager
==================================================
Generating package: Slackware/All

ATI SlackBuild Version 1.3.9
--------------------------------------------
by: Emanuele Tomasi <tomasiATcli.di.unipi.it>
    Ezio Ghibaudo <ekxiusATgmail.com>
    Federico Rota <federico.rota01ATgmail.com>

ERROR: install command makepkg
ERROR: install command modinfo
AMD kernel module generator version 2.1
doing Makefile based build for kernel 2.6.x and higher
rm -rf *.c *.h *.o *.ko *.GCC* .??* *.symvers
make -C /lib/modules/2.6.29.6-smp/build SUBDIRS=/temp/ati/fglrx-install.pqQHn3/c
ommon/lib/modules/fglrx/build_mod/2.6.x modules
make[1]: Entering directory `/usr/src/linux-2.6.29.6'
  CC [M]  /temp/ati/fglrx-install.pqQHn3/common/lib/modules/fglrx/build_mod/2.6.
x/firegl_public.o
In file included from /temp/ati/fglrx-install.pqQHn3/common/lib/modules/fglrx/bu
ild_mod/2.6.x/firegl_public.c:169:
/temp/ati/fglrx-install.pqQHn3/common/lib/modules/fglrx/build_mod/2.6.x/firegl_p
ublic.h:164:1: warning: "PM_EVENT_SUSPEND" redefined
In file included from /usr/src/linux-2.6.29.6/arch/x86/include/asm/apic.h:4,
                from /usr/src/linux-2.6.29.6/arch/x86/include/asm/smp.h:13,
                from include/linux/smp.h:36,
                from include/linux/topology.h:33,
                from include/linux/mmzone.h:767,
                from include/linux/gfp.h:4,
                from include/linux/kmod.h:22,
                from include/linux/module.h:13,
                from /temp/ati/fglrx-install.pqQHn3/common/lib/modules/fglrx/bu
ild_mod/2.6.x/firegl_public.c:91:
include/linux/pm.h:241:1: warning: this is the location of the previous definiti
on
/temp/ati/fglrx-install.pqQHn3/common/lib/modules/fglrx/build_mod/2.6.x/firegl_p
ublic.c: In function 'KCL_GetEffectiveUid':
/temp/ati/fglrx-install.pqQHn3/common/lib/modules/fglrx/build_mod/2.6.x/firegl_p
ublic.c:1405: error: 'struct task_struct' has no member named 'euid'
/temp/ati/fglrx-install.pqQHn3/common/lib/modules/fglrx/build_mod/2.6.x/firegl_p
ublic.c: In function 'KCL_PosixSecurityCapSetIPCLock':
/temp/ati/fglrx-install.pqQHn3/common/lib/modules/fglrx/build_mod/2.6.x/firegl_p
ublic.c:1779: error: 'struct task_struct' has no member named 'cap_effective'
/temp/ati/fglrx-install.pqQHn3/common/lib/modules/fglrx/build_mod/2.6.x/firegl_p
ublic.c:1783: error: 'struct task_struct' has no member named 'cap_effective'
/temp/ati/fglrx-install.pqQHn3/common/lib/modules/fglrx/build_mod/2.6.x/firegl_p
ublic.c: In function 'KCL_MEM_VM_GetRegionPhysAddrStr':
/temp/ati/fglrx-install.pqQHn3/common/lib/modules/fglrx/build_mod/2.6.x/firegl_p
ublic.c:3223: warning: return makes pointer from integer without a cast
/temp/ati/fglrx-install.pqQHn3/common/lib/modules/fglrx/build_mod/2.6.x/firegl_p
ublic.c:3224: warning: return makes pointer from integer without a cast
/temp/ati/fglrx-install.pqQHn3/common/lib/modules/fglrx/build_mod/2.6.x/firegl_p
ublic.c:3225: warning: return makes pointer from integer without a cast
/temp/ati/fglrx-install.pqQHn3/common/lib/modules/fglrx/build_mod/2.6.x/firegl_p
ublic.c:3227: warning: return makes pointer from integer without a cast
make[2]: *** [/temp/ati/fglrx-install.pqQHn3/common/lib/modules/fglrx/build_mod/
2.6.x/firegl_public.o] Error 1
make[1]: *** [_module_/temp/ati/fglrx-install.pqQHn3/common/lib/modules/fglrx/bu
ild_mod/2.6.x] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.29.6'

I have an old x1300 agp radeon running in vesa. If anyone finds another driver that works on slack13 let me know, I'm having lots of problems as well.

cheires 09-01-2009 06:35 AM

I'v had the same problem.
But in my case the error was at inserting FGLRX module.
I remove the modules Radeon and Drm, them the driver installed OK. bum the problem still was there (black screen with a non blinking cursor in the upper left corner).
Instead of using startx, i'd use KDM under root, and that produces an error log.
I'm still not using the FGLRX module, because i don't know what is the problem.
To fix this, i'v unninstalled de fglrx in /usr/share/ati/ using fglrx_uninstall.sh, a then runned the xorgconfig.
The X system works but no 3d acceleration.
My graphics board is an HD3650

gusluke 09-01-2009 08:32 PM

Ati Driver 9.8 + Slackware64 13 Working!!
 
Hello people! iīm new here, today finally finished installed Slackare64 13 after a couple of iso downloads corrupted :S and get installd fine!

The first problem was ATI driver... but now itīs working! (with glx)

My steps was:

1) sh ati-driver-installer-9-8-x86.x86_64.run --buildpkg Slackware/All
2) installpkg fglrx-module-8.64-x86_64-1_kernel_2.6.29.6.tgz fglrx-x740_64a-8.64-x86_64-1.tgz
3) aticonfig --initial
4) aticonfig --overlay-type=Xv
5) cp /etc/ati/amdpcsdb.default /etc/ati/amdpcsdb
6) rmmod radeon
7) rmmod drm
8) (donīt know if itīs ok, but i do it) gunzip /lib/modules/2.6.29.6/external/fglrx.ko.z (maybe zipped work too, donīt know)
9) depmod -a
10) modprobe fglrx

then... starx... and everything is working :D glxgears run OK !

hope that helps!

(sorry for my english)

Gusluke!

cg132 09-01-2009 09:08 PM

Quote:

Originally Posted by amiga32 (Post 3664790)
Just for the record, all ATi videocards (RV600+ i.e. HD2400 and up) are supposed to be supported on both 2.6.29.x and 2.6.30.x kernels as of the latest 9.8 catalysts.

Just in case anyone comes across this and is wondering if their videocard is still officially supported by ATi.

Yea the xorg ati/radeon drivers work...if you dont want TV out. Or at least for me, when I have the tv on during boot time I see the console but when I startx the TV goes nuts with black and white lines or boxes everywhere and the monitor give me out of range error. The modelines I've tried have no effect on the TV. Not sure what to do. Guess the TV needs to be declared in xorg.conf somewhere. I was happy with the drivers from amd previously...the xorg drivers are really touchy. Oh yea, if the TV is off at boot time i can startx using xorg ati drivers no problem. The amd drivers were a bit more looser friendly, i guess, since i'm not leet enough to get the xorg drivers working properly

CrowTRobot 09-01-2009 10:34 PM

I'm also having problems with ATI's proprietary drivers on Slackware 13. My card is a Radeon X1200 (R690).

The 9.8 version actually installs, but when I try to run aticonfig it claims my card isn't supported. Apparently they dropped my card beginning with 9.3. Any driver older than 9.8 can't recognize my Xorg version and kernel version. It looks like this is the end of the line for me using ATI proprietary drivers...

The reason I wanted them in the first place was the driver it's using (I don't know what it is using, I haven't figured out this new xorg.conf-less system) is acting strange. First I noticed it doesn't have OpenGL support, programs like the BlueMarble widget in KDE4 make this clear. Another problem is that after a while of using KDE4, whenever I open a new window (regardless of the program) my entire screen changes to something like inverted colors but worse picture quality, making it barely usable. However, when I close the new window, everything changes back to normal!

I tried using an xorg.conf with the 'radeon' and 'radeonhd' drivers and the same problems happen with both. I haven't tried using anything but KDE4, I'll see if the same color change thing happens in fluxbox and get back to you.

EDIT:
In fluxbox I got pretty bad cursor corruption when swithing between windows and using the menu. The cursor gets covered by 3 white bars which take a while to disappear. I decided to use xorgsetup to create an xorg.conf, which made all of the same problems, so I changed the driver to 'ati' and now the cursor corruption and screen color distortion in KDE seem to be gone! I still don't have OpenGL support though.

cheires 09-03-2009 12:20 PM

Quote:

Originally Posted by gusluke (Post 3666140)
Hello people! iīm new here, today finally finished installed Slackare64 13 after a couple of iso downloads corrupted :S and get installd fine!

The first problem was ATI driver... but now itīs working! (with glx)

My steps was:

1) sh ati-driver-installer-9-8-x86.x86_64.run --buildpkg Slackware/All
2) installpkg fglrx-module-8.64-x86_64-1_kernel_2.6.29.6.tgz fglrx-x740_64a-8.64-x86_64-1.tgz
3) aticonfig --initial
4) aticonfig --overlay-type=Xv
5) cp /etc/ati/amdpcsdb.default /etc/ati/amdpcsdb
6) rmmod radeon
7) rmmod drm
8) (donīt know if itīs ok, but i do it) gunzip /lib/modules/2.6.29.6/external/fglrx.ko.z (maybe zipped work too, donīt know)
9) depmod -a
10) modprobe fglrx

then... starx... and everything is working :D glxgears run OK !

hope that helps!

(sorry for my english)

Gusluke!


Just to say that did work for me.

Thank you


All times are GMT -5. The time now is 04:03 PM.