X11 error "No screens found" with FGLRX after upgrade to slackware64-current
 

Hi! I have slackware64 13 and my ATI fglrx dont after last update any more...

Seems like xorg 7.5 don't work with fglrx or something else... How to fix it?

Did you also update fglrx?
Check to see if your card is supported by free software drivers.

I am getting a lot of support requests concerning fglrx due to ATI dropping support for a lot of cards. The upside is that these cards are supported in the free software radeon or radeonHD drivers.

my card is hd2600XT... How can I try open source ati drivers? I never did it before...

Seems like xorg 7.5 is currently not supported by fglrx((

Yes, fglrx does not support X server 1.7.* yet. Hopefully in the next month or two.

You can use the open source drivers. They should have worked out-of-the-box on a Slackware64 -current installation, but are probably now broken that you installed fglrx. Remove fglrx, reinstall mesa and the xserver packages, and then switch to the 'radeon' or 'radeonhd' driver in /etc/X11/xorg.conf.

Adam

I removed fglrx and reinstalled all the XORG and MESA packages... and now /etx/X11/xorg.conf is ignored...

xorg.conf is empty (size = 0b), but KDE still runs... still no hardware 3D...

OMG, how can I make open source drivers work

Show us your /var/log/Xorg.0.log file.

Adam

bash-4.1$ tail /var/log/Xorg.0.log

That's clearly not your full log file. :-)

Adam

Oh, I'm sorry) (named xorg.0.log.txt because I can attach txt files only)

This is the problem:

What is the output of 'lsmod | grep drm' and 'dmesg | grep drm'?

both are nothing...

How about the output of 'modprobe radeon' (either as root or with sudo).

>< don't work... How do I fix it? ><

COmmon issue with -current:

http://www.linuxquestions.org/questi...pgrade-792578/

Basically, rebuild the kernel with CONFIG_PREEMPT_NONE=y

omg... that's terrible)

I gonna downgrade back to xprg 7.4... but input devices (mouse and keyboard) don't work at all!

how can I make it work?

---------

The problem was fixed after cup of tea.

I forgot to downgrade xf86-input packages with downgrading xorg back to slackware-13 from current...

Don't panic - that's how it is designed. It is very good except on those few occasions it fails - when it is a pita. In most cases you need only repopulate the xorg.conf as little as you need).How are you getting all these logs?

note: usb kbd+mouse are handled through the usbhid driver. Unless you have a very unusual setup...IIRC: you can also get this error if you have not cleaned up after the fglrx un-install.

Your chipset is RV610/630 (please confirm with lspci | grep ATI).

man radeon(4)
i.e. do not expect 3D accel with the radeon driver.

2600XT is supported by the RadeonHD driver.

It is possible that Adam has ruled these out as possible causes of your problems.

3D acceleration is supported by radeon. The man page is out-of-date. I would not recommend radeonhd as it sees very little development and even user support.

Adam

Yep - it is likely that radeonHD will get merged with radeon - much of why it exists is no longer relevant.

Still - the features page lists 3D element support as "mostly" for R600. Though the DRI wiki just mentions "many shaders missing". RadeonHD features reflect a more Cathedral-style development: stuff is either done or not started.

http://www.x.org/wiki/radeonhd
I dunno - I just have a hard time with the kernel preempting mode affecting the loading of modules in this way... but apparently it does. This prompts me to look in different directions JIC.

I also suspect that recompiling the kernel will be easier than downgrading - and I expect there will be an official kernel update for -current soon.

Normally I don't see trouble with the fglrx packages, just the ati installer and that unusual. But: I have had three of these just this week, all newly unsupported, and for some reason each one has ended up needing large chunks of X removed and installed before the free drivers could work. (None this card, and none slackware.) Where I have been able to preempt the, usually blind, proprietary package install, there has been no problem: it just goes.