Hi,
I know officially fglrx isn’t working with 13.2, I was wondering however if anybody managed to find some sort of workaround, or got it working. Please let me know your thoughts.
Kind Regards
I don’t think there is a workaround.
The driver doesn’t work with the newer Xorg (the same as the nvidia 304.121 driver apparently).
You cannot patch/fix it either, as it is closed-source.
It might work if you start X with the -ignoreABI option (or set Option “IgnoreABI” “true” in the config’s “ServerFlags” section), but most likely not.
I was wondering the same thing.
Some info can be found here:
https://lizards.opensuse.org/tag/fglrx/
Yeah it sucks, I’m currently running radeon driver and using xrender as compositing type (KDE) otherwise KWin won’t work. No video in kaffeine, only sound. Must set xrender as output driver in smplayer … :disapointed::yawn:
FYI I have to reinstall xorg-x11-server to make direct rendering/opengl working again.
Hello, I just intalled 13.2 and i have a HD7850 since fglrx is not currently working i want to use the radeon drivers, and for what i been reading it’s suppose that opensuse installed this driver one it was installed.
but it seams is not working i have to start always in “recovey mode” to get X. I normal mode i dont get video nor text mode (console, tty).
and in recovery mode when i do a modprobe radeon this is what i get.
linux-larva:/home/larva # modprobe radeon
modprobe: ERROR: could not insert 'radeon': Invalid argument.
but when i do glrxgears i do get the gears.
heres my render info
linux-larva:/home/larva # glxinfo | grep render
direct rendering: Yes
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
GLX_MESA_query_renderer, GLX_OML_swap_method, GLX_SGIS_multisample,
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.5, 256 bits)
GL_ARB_conditional_render_inverted, GL_ARB_conservative_depth,
GL_MESA_ycbcr_texture, GL_NV_blend_square, GL_NV_conditional_render,
and i dont see a xorg.conf in the directory.
linux-larva:/ # cd /etc/X11
linux-larva:/etc/X11 # ls
xdm xim xim.d xinit Xmodmap Xmodmap.remote xorg.conf.d xorg.conf.install Xresources
any help is really helpful thanks.
Yes.
and in recovery mode when i do a modprobe radeon this is what i get.
linux-larva:/home/larva # modprobe radeon modprobe: ERROR: could not insert 'radeon': Invalid argument.
Yes. You cannot load the radeon driver in recovery mode, because KMS is turned off and radeon requires it.
but when i do glrxgears i do get the gears.
heres my render info
linux-larva:/home/larva # glxinfo | grep render direct rendering: Yes GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_query_renderer, GLX_OML_swap_method, GLX_SGIS_multisample, OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.5, 256 bits) GL_ARB_conditional_render_inverted, GL_ARB_conservative_depth, GL_MESA_ycbcr_texture, GL_NV_blend_square, GL_NV_conditional_render,
Yes. You are using Mesa’s software renderer.
Again, normal for recovery mode. A generic graphics driver (fbdev or vesa) is used that obviously doesn’t support most features of your particular graphics card (as t’s “generic”, and intended to work with all cards/chipsets).
So no OpenGL hardware acceleration, but OpenGL still works (albeit much slower of course) as Mesa falls back to its software renderer (swrast).
and i dont see a xorg.conf in the directory.
And you shouldn’t either.
Well, let’s start with the Xorg log.
Please boot normally until it fails, then boot to recovery mode and post the file /var/log/Xorg.0.log.old (upload it to some pasting/sharing site like http://susepaste.org/ and post a link if it is too big).
You could also try to disable plymouth (the boot splash) as a test, this is know to have caused problems in the past.
Press ‘e’ at the boot menu (when the standard entry is selected), search for the line starting with “linux” and append “plymouth.enable=0” at the end. Then press ‘F10’ to boot.
I know that there is a “testing” version of the FGLRX driver that will work (with some caveats). I don’t know how long it’ll take for this testing version to reach beta and I’m not sure how stable it is but the recently released 'buntus (which also ship with xserver 1.16) are using it. Also, Arch users are employing it successfully. However, it apparently doesn’t work with Wine yet.
Well hard to say but the NVIDIA driver problems when 13.1 was released took a couple of weeks if I recall. If you are not into debugging or must have a working system you should always wait a bit before installing a new version. It takes some time for all things to shake down. We who wait solute those intrepid users that ride the cutting edge. >:)
I have read that they’ve employed backports as a workaround. Doesn’t that effectively mean they’re still reliant on Xorg 1.15?
Thanks,
Hrudai.
No doubt that some Arch users have done it that way…but the aforementioned “testing” Catalyst driver IS available to them in the Arch Catalyst testing repo. More info here.
Leisa
before seeing your post i did some test in runlevel 3, (normal mode not recovery).
I did xorg -configure and it created me a new xorg file inside /root
then i tested this with Xorg -/root/filenametouse
but still did not work.
this is the xorg.conf that generate in the /root/
Section “ServerLayout”
Identifier “X.org Configured”
Screen 0 “Screen0” 0 0
InputDevice “Mouse0” “CorePointer”
InputDevice “Keyboard0” “CoreKeyboard”
EndSection
Section “Files”
ModulePath “/usr/lib64/xorg/modules”
FontPath “/usr/share/fonts/misc:unscaled”
FontPath “/usr/share/fonts/Type1/”
FontPath “/usr/share/fonts/100dpi:unscaled”
FontPath “/usr/share/fonts/75dpi:unscaled”
FontPath “/usr/share/fonts/ghostscript/”
FontPath “/usr/share/fonts/cyrillic:unscaled”
FontPath “/usr/share/fonts/misc/sgi:unscaled”
FontPath “/usr/share/fonts/truetype/”
FontPath “built-ins”
EndSection
Section “Module”
Load “vnc”
Load “glx”
EndSection
Section “InputDevice”
Identifier “Keyboard0”
Driver “kbd”
EndSection
Section “InputDevice”
Identifier “Mouse0”
Driver “mouse”
Option “Protocol” “auto”
Option “Device” “/dev/input/mice”
Option “ZAxisMapping” “4 5 6 7”
EndSection
Section “Monitor”
Identifier “Monitor0”
VendorName “Monitor Vendor”
ModelName “Monitor Model”
EndSection
Section “Device”
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: “True”/“False”,
### <string>: “String”, <freq>: “<f> Hz/kHz/MHz”,
### <percent>: “<f>%”
### [arg]: arg optional
#Option “Accel” # <bool>]
#Option “SWcursor” # <bool>]
#Option “EnablePageFlip” # <bool>]
#Option “ColorTiling” # <bool>]
#Option “ColorTiling2D” # <bool>]
#Option “RenderAccel” # <bool>]
#Option “SubPixelOrder” # <str>]
#Option “AccelMethod” # <str>
#Option “EXAVSync” # <bool>]
#Option “EXAPixmaps” # <bool>]
#Option “ZaphodHeads” # <str>
#Option “EnablePageFlip” # <bool>]
#Option “SwapbuffersWait” # <bool>]
Identifier “Card0”
Driver “radeon”
BusID “PCI:1:0:0”
EndSection
Section “Screen”
Identifier “Screen0”
Device “Card0”
Monitor “Monitor0”
SubSection “Display”
Viewport 0 0
Depth 1
EndSubSection
SubSection “Display”
Viewport 0 0
Depth 4
EndSubSection
SubSection “Display”
Viewport 0 0
Depth 8
EndSubSection
SubSection “Display”
Viewport 0 0
Depth 15
EndSubSection
SubSection “Display”
Viewport 0 0
Depth 16
EndSubSection
SubSection “Display”
Viewport 0 0
Depth 24
EndSubSection
EndSection
after that i read your post and tried the plymouth.enable=0 but this also didn’t not work.
and now here’s the log from rescue system /var/log/
anyway here are the log files.
this is for /var/log/Xorg.0.log http://pastebin.com/1rSuTjY8
this is for /var/log/Xorg.0.log.old http://pastebin.com/4ZCH6Q4P
thanks for your time and help.
You can try removing nomodeset in kernel command line or modprobe with modesetting enabled:
modprobe radeon modeset=1
nop did not work.
actually im only able to get X in nomal mode if edit group and set radeon.modeset=0
But that’s the exact opposite!
It turns ON KMS.
As it is on by default anyway (and the radeon driver does not work at all without it) that line is useless!
Yes. That’s actually the same as “nomodeset”, but restricted to the radeon driver only.
In practice it disables the radeon driver and uses fbdev or vesa instead.
The radeonhd driver is dead since years and not available any more. It wouldn’t work anyway in recent distributions.
And radeon is better than radeonhd ever was anyway.
And that particular paragraph tells to add “nomodeset” to the boot options, so how can this be done instead of adding “nomodeset”?
Blacklisting radeon is another way of course, but why would that be better? (if you do not have a hybrid system, that is)
Well, you shouldn’t need an xorg.conf, that’s deprecated.
after that i read your post and tried the plymouth.enable=0 but this also didn’t not work.
and now here’s the log from rescue system /var/log/
anyway here are the log files.
this is for /var/log/Xorg.0.log http://pastebin.com/1rSuTjY8
this is for /var/log/Xorg.0.log.old http://pastebin.com/4ZCH6Q4P
Hm. The radeon driver is loaded and seems to be working fine according to the second log (the first is from recovery mode and irrelevant for this).
I don’t see anything problematic in there regarding the graphics driver.
So, from what I can tell, X started fine.
Can you please clarify what you mean with “I normal mode i dont get video nor text mode (console, tty)”?
What happens exactly? Is the screen just blank?
Can you switch to text mode with Ctrl+Alt+F1?
Maybe it’s a problem with backlight turned off, i.e. brightness set to 0?
I see the splash screen, then after it finish the screen gets ON with backlight (but no mouse cursor or login screen) ( i have autologin OFF) and the system does not respond.
Can you switch to text mode with Ctrl+Alt+F1?
nop, and i thought this was called “tty1” (i just read it somewhere)
Maybe it’s a problem with backlight turned off, i.e. brightness set to 0?
how can i set this change? i dont think is a monitor issue otherwise i guess i could get in to the Ctrl+Alt+F1 no?
normal mode= not recovery mode, just the first option in the grub
PS. if i edit grub to start in init 3 i can use the console.
Just a note:
Sebastian Siebert has released a new version of his makerpm-amd script (called makerpm-amd-14.9-os13.2-refurbished.sh), that takes specific parts from that mentioned inofficial Ubuntu driver and even includes a patch for kernel 3.18 already.
You can get it here:
http://www.sebastian-siebert.de/
As the page is in german, here’s a direct download link:
http://www.sebastian-siebert.de/downloads/makerpm-amd-14.9-os13.2-refurbished.sh
And here are the instructions for how to use it:
http://en.opensuse.org/SDB:AMD_fglrx#Building_the_rpm_yourself
In short, this script downloads the latest version of the fglrx driver, creates RPM packages and installs them. It is also used to create the packages in the repo, so that might be available soon now as well (I don’t know though).
Btw, according to the page, the script should also work on Tumbleweed, so you can install the fglrx driver there via RPMs as well, without even having to care about kernel updates… 
Oops, I completely missed that post.
You might just as well install fglrx now, but anyway…
Ok, so apparently it freezes when X or the login manager tries to start.
nop, and i thought this was called “tty1” (i just read it somewhere)
So, a complete freeze.
And yes, it is indeed called “tty1” (TeleTYpe 1, I think), or “VT1”.
I wrote “text mode”, because that’s what it is.
how can i set this change? i dont think is a monitor issue otherwise i guess i could get in to the Ctrl+Alt+F1 no?
You can set certain things via the kernel command line (“boot options”).
But you’re right, you should be able to switch to another VT in this case.
[QUOTE]normal mode= not recovery mode, just the first option in the grub
Of course, recovery mode will disable the radeon driver.
And it should work.
PS. if i edit grub to start in init 3 i can use the console.
Ok, this confirms another time that it is a graphics driver problem.
But to not waste more time with useless things in trying to get radeon to work, I’d suggest you just install fglrx now…