LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   ati radeon hd6970 catalyst 12.4 blank screen at boot slackware current 3.2.13 kernel (https://www.linuxquestions.org/questions/slackware-14/ati-radeon-hd6970-catalyst-12-4-blank-screen-at-boot-slackware-current-3-2-13-kernel-4175411217/)

matters 06-13-2012 08:20 AM

ati radeon hd6970 catalyst 12.4 blank screen at boot slackware current 3.2.13 kernel
 
Hello, im having an issue. I upgraded current up to date, everything was perfectly fine untill now.

kernel is 3.2.13, catalyst 12.4 proprietary driver.

The problem is i get blank screen during boot, after 30 seconds or so.

if i disable kms then everything is okay. but then if i reinstall propriatery driver i cant get into X. If i uninstall proprietary driver, after reboot, during boot time after a while i get blank screen again.

im wondering what might be the problem?

thanks!

san 06-13-2012 09:08 AM

Quote:

Originally Posted by matters (Post 4702195)
if i disable kms then everything is okay ...

this is the second thread on -current and kms within a week :confused:
Quote:

...but then if i reinstall propriatery driver i cant get into X
which errors does Xorg.0.log show?
have you blacklisted the stock radeon module? it conflicts with fglrx.
did you run aticonfig --initial or did you already have an xorg.conf?

Darth Vader 06-13-2012 10:59 AM

Quote:

Originally Posted by matters (Post 4702195)
Hello, im having an issue. I upgraded current up to date, everything was perfectly fine untill now.

kernel is 3.2.13, catalyst 12.4 proprietary driver.

The problem is i get blank screen during boot, after 30 seconds or so.

if i disable kms then everything is okay. but then if i reinstall propriatery driver i cant get into X. If i uninstall proprietary driver, after reboot, during boot time after a while i get blank screen again.

im wondering what might be the problem?

thanks!

Catalyst do not have support for the xserver 1.12 right now. So, no Catalyst for you while running slackware-current.

Still good news: there will be support for that xserver (1.12) in Catalyst 12.6
Very bad news: The support for HD2000, HD3000 and HD4000 will be dropped, so no support for you if you do not run an HD5000 or higher graphics card.

So, I suggest you right now, to stuck in the open-source ATI stack and enjoy it. :)

matters 06-13-2012 02:02 PM

I have hd6970 and removed catalyst but the problem still remains. During the boot i get blank screen after 30 secs or so. If i disable KMS everything is ok and i get to console login prompt. How can i solve this problem?

If it helps i use dvi-to vga adapter and to clarify kernel is 3.2.13 from the current. thanks!

adamk75 06-13-2012 02:26 PM

Sounds like a missing firmware problem. Can you login remote and grab the output of 'dmesg' ?

Adam

matters 06-13-2012 04:21 PM

@adamk75 hello, heres dmesg

http://sprunge.us/gCLX

thanks alot!

adamk75 06-13-2012 05:07 PM

Hmmm:

Code:

[    8.914045] [drm] Internal thermal controller with fan control
[    8.915636] [drm] radeon: power management initialized
[    8.939632] No connectors reported connected with modes
[    8.939700] [drm] Cannot find any crtc or sizes - going 1024x768
[    8.941398] [drm] fb mappable at 0xE0142000
[    8.941462] [drm] vram apper at 0xE0000000
[    8.941526] [drm] size 3145728
[    8.941589] [drm] fb depth is 24
[    8.941651] [drm]    pitch is 4096

The No connectors reported suggests that the radeon kernel driver can't detect any monitors. Sometimes the video drivers have problems reading monitor EDID information with certain models. You could perhaps try forcing a resolution with video=640x480 passed to the kernel, though I'm doubtful that will work. I would suggest trying a newer kernel and hoping this bug has been worked out.

Adam

ReaperX7 06-13-2012 06:39 PM

By the nature of using -Current being classified as a developer/tester/unstable branch, you should not attempt to use any Proprietary drivers from any manufacturer.

Someone may want to add that to an FAQ somewhere sometime.

The -Current tree(s) are constantly in a state of evolution and because Proprietary drivers from OEMs tend to be centered more towards stable releases of major distributions that have been out for some time, there often will be problems with kernels not being properly supported and other such issues.

All current Radeon devices should be supported through the modern "ati" driver package, Mesa is now compiled to support 3D acceleration using Gallium3D, and -Current should also have the latest firmware for all major Radeon devices in the "/lib/firmware/radeon" directory.

matters 06-14-2012 03:10 AM

@adam by forcing resolution to 640x480 actually did the trick and now everything is working.
If i understand you correctly from logs it tried to read edid under 1024x768 and couldnt, by forcing it it tried to read edid under 640x480 correct?

HD6970 wasnt supported by open source, when i purchased it over a year ago. So i used proprietary driver.

Thanks!


All times are GMT -5. The time now is 08:55 AM.