[SOLVED] Slackware64 -current video problem with ATI HD5570

lpallard · 11-20-2010, 10:34 PM

Hey guys! I just built a machine for a friend and he has a HIS Radeon HD5570. I successfully installed slack64 current (as of today nov. 20) and upon first attempt to enter the desktop, I experienced a problem. Basically, I log in, type startx to start the X server and then I see the KDE loading bar, and boom! black screen, the monitor goes to sleep. It happens with all monitors so far... Should I suspect a hardware problem? Please note I did not install any drivers so far.. Only Slackware...

How can I fix this? What do you need in order to help me?

If useful, I pasted my Xorg.0.log at pastbin

http://pastebin.com/XYfFnx39

Thanks as always!

acummings · 11-21-2010, 01:13 AM

Quote:

[ 33.210] (--) RADEON(0): Chipset: "ATI Radeon HD 5570" (ChipID = 0x68d

#
Fatal server error:
#
[ 36.548] Caught signal 11 (Segmentation fault). Server aborting

Oop, seg. fault, X-server aborted.

Poor thing. Looks like it tried really hard ie loaded then unloaded copius amounts of drivers including vesa BTW I don't think vesa and radeon can coexist.

You need to enable kms. you also need the next file.

Code:

/etc/modprobe.d/radeon.conf

I ran xorgsetup (I think) which gave me an xorg.conf file.

I'm now running 2.6.35.8 and my HD 5450 radeon kms video is even better now than it was with 2.6.35.7

http://www.linuxquestions.org/questi...ml#post4117004

http://www.linuxquestions.org/questi...ml#post4130065

http://www.linuxquestions.org/questi...ml#post4117015

http://www.linuxquestions.org/questi...5/#post4133185

--
Alan.

acummings · 11-21-2010, 01:28 AM

http://www.linuxquestions.org/questi...ml#post4117100

Quote:

BTW I been dink with this off and on now for more than a week and a half. I Nearly sledge hammered my hd 5450 and I *very* nearly queried slack forum here for a (like, let's get *real* <grin>) a "Linux friendly pci-E video adapter"

<grin><grin><grin><grin><grin>

Are we having fun yet?

*Yes*!!! Silly late hardware anyways. Go Slackware!!!!

Slackware rocks.

It's Slackware *equals* "Do what you want"

I do what I want ie virtual machines all over the place.

Serving desktop across lan and across internet be next on my agenda in my Slackware travels.

--
Alan.

JackHair · 11-21-2010, 02:30 AM

I had the same problem with my HD5850. It has to do with the new mesa pkg.

Code:

  If X crashes at start, try disabling compositing.  Create a file named
  /etc/X11/xorg.conf.d/disable-composite.conf with this in it:
    Section "Extensions"
      Option "Composite" "Disable"
    EndSection

After doing this I got to the desktop. But obviously composite doesn't work. I just removed the disable-composite.conf again and installed fglrx. Now it's working fine.

Chuck56 · 11-21-2010, 08:50 AM

I just went through a similar experience with an HD4200:

http://www.linuxquestions.org/questi...ml#post4166070

Follow the link to Eric's post and see if the mesa-7.9 to mesa-7.8.2 change helps.

lpallard · 11-21-2010, 09:30 AM

I am sooooooooooooooo confused! reminds me of the days I was trying to install my FireGL card on mandrake.... hahaha the good ol' days!

now with this issue, I started off by trying what JackHair suggested. i.e. adding

Code:

Section "Extensions"
   Option "Composite" "Disable"
EndSection

to /etc/X11/xorg.conf.d/disable-composite.conf

And I could boot to the desktop. Then I continued with Jack's suggestion (removing the disabled-composite.conf file) and install the fglrx driver. To do so, I followed the instructions on the ATI's wiki for slackware64... That means I downloaded the installer.run , converted into 2 tgz packages and installed both of them using installpkg.

I ran aticonfig --initial and so far so good. I verified the content of xorg.conf as suggested on ATI's wiki but noticed a few problems such as the section module should be populated but it is not (empty).

I ran fglrxinfo but got a segmentation fault.

I think this is going to be complicated. Would reverting to the latest stable release of slack64 help? If not, I will need some major step by step assistance because I never really played with drivers and Xorg before....

thanks to all!

adamk75 · 11-21-2010, 11:09 AM

OK, let's try and focus on getting fglrx working, rather than using the mesa drivers.

Can you show us the /var/log/Xorg.0.log file you have while using fglrx?

Adam

lpallard · 11-21-2010, 11:57 AM

thanks adam75k for replying!

just before I got your reply, I took the initiative to uninstall current and install the last stable release of slack64. I noticed that I could log in the desktop withourt problems but I experienced the "monitor going to sleep" upon clicking logout in KDE...

I then installed the fglrx driver following the same procedure as above and now xorg.conf contains:

Code:

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

Section "Module"
EndSection

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

Section "Device"
        Identifier  "aticonfig-Device[0]-0"
        Driver      "fglrx"
        BusID       "PCI:1:0:0"
EndSection

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

section module is still empty but fglrxinfo now gives :

Code:

display: :0.0  screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon HD 5500 Series
OpenGL version string: 4.0.10317 Compatibility Profile Context

instead of a segmentation fault...

now to the Xorg.0.log as you requested, please look at http://pastebin.com/pfM30R8u

The log contains tons of fglrx lines so I think its good sign?!

adamk75 · 11-21-2010, 12:03 PM

Yes, according to everything you just posted, your drivers are working fine now.

Adam

lpallard · 11-21-2010, 12:22 PM

Adam, if you dont mind I would have one more question... I tried to hook up the computer to the LCD tv via HDMI and noticed something funny. The resolution reported by the catalyst driver is 1920x1080 and that correspond to the native resolution of the tv we try to work with. So normally, the bottom of the desktop (the taskbar) and all other edges should be right on the edges of the tv display.... Right now, the image is somehow scaled up (like if the resolution was set higher than the TV can handle, and all 4 edges of the desktop are hidding.

DO you know how to fix this? I tried to play around with the catalist driver but no success.

UPDATE: I just tried to change the settings in the Tv and set the picture to scale to fit instead of 16:9.. Is that normal?

adamk75 · 11-21-2010, 12:39 PM

To me it sounds like the driver is overscanning or underscanning your display. Most new HDMI displays have an option to underscan or overscan. If yours does not, catalyst might, but I've never had to deal with it before so I wouldn't even know where to look.

Adam

lpallard · 11-21-2010, 05:05 PM

Just as good as your guess was, I the overscanning was responsible for the problem... In the catalyst driver applet, I found the option to adjust the overscan and I lowered the slide bar to roughly 90% of what It was and now I have a perect match with the hdtv. We're happy with that!

Now I need to find out why I have no sound. Only KDE sounds (login, logout, and all sound events) work but playing flash videos from the web or even local media wont work. However MP3's work like a charm!

That mean that the sound is carried through HDMI but not for videos...

T3slider · 11-22-2010, 01:27 AM

Quote:

Originally Posted by lpallard

That mean that the sound is carried through HDMI but not for videos...

If you have another sound card it is very likely that those applications are trying to use it instead of the HDMI output. For video applications you should be able to specify the device (or set them to use KDE4's sound server instead of ALSA directly), but I really am not sure how to get Flash to behave other than setting your HDMI output as the default sound device (either through ~/.asoundrc or by setting it as card 0 in /etc/modprobe.d/sound.conf).

adamk75 · 11-22-2010, 04:30 AM

Quote:

Originally Posted by lpallard

Just as good as your guess was, I the overscanning was responsible for the problem... In the catalyst driver applet, I found the option to adjust the overscan and I lowered the slide bar to roughly 90% of what It was and now I have a perect match with the hdtv. We're happy with that!

Now I need to find out why I have no sound. Only KDE sounds (login, logout, and all sound events) work but playing flash videos from the web or even local media wont work. However MP3's work like a charm!

That mean that the sound is carried through HDMI but not for videos...

Run firefox from a terminal and start up a flash video. See what errors firefox displays.

Adam

andrewthomas · 11-22-2010, 11:07 AM

Try this out, it should work good

http://www.shcherbyna.com/?p=866