I’m relatively new to openSUSE (3-4 months), though I’ve been playing around with other distros for a year. Last night, after noticing I have problems with hibernting my laptop running openSUSE 12.3 (with KDE 4.10), I thought the problem may have been raised from display driver (as used to be the case with Windows). So, I tried what AlianDuc had said in this topic:
Installing fglrx64_xpic_SUSE121-9.012-1.x86_64.rpm did the trick. I hope it will help others facing the same issue
I installed the mentioned driver from this (http://geeko.ioda.net/mirror/amd-fglrx/openSUSE_12.1/x86_64/). But after a reboot, noticed that it had messed up everything, including Xorg. Doing a lot of searches through the web and being awake all the night, by following instructions here (among others), I managed to fix it up partially, i.e. the open source “radeon” driver is now installed again, and the resolution is correct. I also added the following line (for 3D support) to the file “20-radeon.conf”:
As mentioned in the thread’s title, all videos are played back with a 90 degrees of rotation to the right. I have couple of other distros installed besides openSUSE, the video files themselves are intact and correct because they get played back correctly in other distros, but the playback in openSUSE has got corrupt. I use VLC.
The splash screen is now gone, and instead a green progress bar shows up. Can I restore openSUSE’s default splash screen or any other splash screen?
As mentioned in the thread’s title, all videos are played back with a 90 degrees of rotation to the right
.That’s an interesting one.
The splash screen is now gone, and instead a green progress bar shows up. Can I restore openSUSE’s default splash screen or any other splash screen?
Do you mean for Plymouth or KDE splash ? (both are capable of displaying a progress bar. Plymouth occurs right after the bootloader (grub) and before the Display Manager login screen (if you are using one). KDE splash starts after login from DM.
@Caf4926
Yes, you’re right. I just noticed! I’ve suffered a lot from being careless, ans still I don’t pay attention to details. This kind of mistake is also the source of most of my coding mistakes.
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RV620 [Mobility Radeon HD 3400 Series] [1002:95c4]
Subsystem: Dell Device [1028:0254]
Kernel driver in use: radeon
I meant Plymouth splash screen. By the way, before I enabled glamor, I used to see the login screen, though a messy huge one with low (maybe 8-bit) color depth (I’m not sure if the distro itself includes a Display Manager, I didn’t install any DM). I’m using MDM on Linux Mint, but I guess I’m not using any DM on openSUSE.
By the way, I’m using the 64bit version of the distro (and kernel?).
By the way, here are correct ATI’s proprietary drivers (for 12.3 amd64), but like a sticky thread on the forums had already stated, it doesn’t support older cards including 3400 series. so, I think I have to stick to either radeonhd or radeon. But can somebody help and demonstrate in details how can I fix it up?
you seem confused about glamor, as you wrote earlier that it was for 3D accel. Its not. It provides a 2D accel via openGL (i.e. using shaders in the 3D engine). For certain modern hardware, glamor is
required for 2D acceleration and also required in order for to get 3D, but neither of those apply in your case – you don’t need glamor for your adapter. 1. you can use it, if you want, for 2D accel (it has nothing to do with getting 3D accel for your case) but
glamor is still plenty buggy.
I’d bet that many of the people who think they’re using glamor actually aren’t (it isn’t enabled … when its enabled, there are some very explicit messages in the xorg log) and are using the older, default, EXA instead
the version of glamor available in openSUSE currently does not feature something that is desirable: Xv support … that should be available in a couple of days, as it was just enabled by default in builds
I meant Plymouth splash screen.
okay
By the way, before I enabled glamor, I used to see the login screen, though a messy huge one with low (maybe 8-bit) color depth (I’m not sure if the distro itself includes a Display Manager, I didn’t install any DM). I’m using MDM on Linux Mint, but I guess I’m not using any DM on openSUSE.
The distro will indeed install a DM by default (KDM for KDE, GDM in the case of GNOME), and you will still be using one even if you’re using auto login (I was not clear about that earlier, my mistake). If you’re using auto login, you simply won’t see the greeter for the DM, but the DM will still work in the background to authenticate your session. you can change this in yast > security & users > users and group mgmt > user tab > select user > hit expert options > login settings > auto login … phewwww:P … or, as root, you can just change the same thing yourself in /etc/sysconfig/displaymanager … if you’re using KDE, in configure desktop > login screen > convenience tab > should be able to set auto logins too (I’m not using KDM right now, so can’t test it off hand, but I’d assume it works (i.e. writes to the /etc/sysconfig/displaymanger))
glamor could impact the DM’s greeter login screen (the X server is running), but it would in no way impact plymouth (X is not running).
what output do you have for:
grep radeon /etc/modprobe.d/*
and just as a check:
cat /proc/cmdline
My feeling right now is that something like this is happening: you have the radeon kernel driver blacklisted (a holdout from your fglrx experiment * ), hence it doesn’t load on boot, and plymouth uses the vesafb during the boot to display the progress bar, and when X starts, your xorg.conf.d is actually working and the radeon X driver loads (which then evokes the radeon kernel driver loading), and glamor accel is actually enabled and working for you. As glamor would be lacking Xv support, that might be messing vlc up, and the video gets twisted
btw, you can’t use the prop. drivers, as there isn’t support for your hardware, though that doesn’t matter anymore as the OSS is just fine for it now … also, as was mentioned, you were attempting to use a driver from 12.1 … wouldn’t have worked given the server and kernel requirements can not be met
I commented out the blacklist line related to radeonfb in 50-blacklist.conf, and then rebooted the system, but nothing changed.
By the way, though I’m not sure if this is of help or not, but: although VLC manages to play back videos (though tilted), Kaffeine doesn’t play them back at all.
okay, its fine (I didn’t expect anything to be wrong with it, going from what you’d described, but just wanted to check)
Yes, you were right, the radeon kernel driver was blacklisted. … I commented out the blacklist line related to radeonfb in 50-blacklist.conf, and then rebooted the system, but nothing changed.
okay, plymouth is still working in text mode … which shouldn’t happen if the radeon DRM/KMS driver is gettng loaded at boot (dmesg would indicate if it is) … try rebuilding the initrd (“sudo mkinitrd”). Also get rid of your xorg configs, specifically that file containing the glamor accel option! Just let X autoconfig itself.
By the way, though I’m not sure if this is of help or not, but: although VLC manages to play back videos (though tilted), Kaffeine doesn’t play them back at all.
I have no idea atm … one step at a time.
its unfortunate that kaffeine’s development has fallen to the wayside. however, I still use it regularly for dvb, as its still one of the best standalone apps for that. I also use it for DVDs, simply as its the default player OOTB. I have no problem with it in that regard. Otherwise, all else, its smplayer for me.
Thank you Tyler_K and sorry for the late reply again, I was quite busy past few days. I deleted all config files in /etc/X11/xorg.conf.d and also rebuilt initrd (using “mkinitrd” command/program (/sbin/mkinitrd)). But it didn’t make any difference, I still see the green progress bar instead of Plymouth splash. Do I need to delete also /etc/X11/xorng.conifg & /etc/X11/xorng.config.install? Right now, after 2 reboots, X has created only one config file named “90-keytable.conf” in /etc/X11/xorg.conf.d. I don’t know if it’s part of openSUSE normal boot process or not, but I see “doing fast boot” (or something like that) before the progress bar shows up. Here is the content of /etc/modprobe.d/50-blacklist.conf (I also have a “blacklist.conf” in /etc/modprobe.d/, but it’s empty (maybe I’ve created it by mistake)).
> cat 50-blacklist.conf
#
# $Id$
#
# Listing a module here prevents modprobe from loading it via modalias (only
# aliases from /lib/modules/*/modules.alias). You may still load it explicitely.
# We blacklist some modules becaus they may harm on certain devices or they
# prevent other modules from grabbing the device.
#
# Syntax: blacklist <driver name>
# See 'man modprobe'.
#
# uhci ... usb-uhci handles the same pci class
blacklist uhci
# usbcore ... module is loaded implicitly, ignore it otherwise
blacklist usbcore
# tulip ... de4x5, xircom_tulip_cb, dmfe (...) handle same devices
blacklist de4x5
# At least 2.4.3 and later xircom_tulip doesn't have that conflict
# xircom_tulip_cb
blacklist dmfe
# list all framebuffer drivers, some of them tend to crash during boot
# they are either compiled into the kernel, or vesafb is active
# X works fine without them, rcfbset can load them if really required
# sed -e '/\/drivers\/video\/.*\.\(o\|ko\)$/{s@^.*/@@;s@\..*$@@;p};d'
blacklist aty128fb
blacklist atyfb
blacklist clgenfb
blacklist cyber2000fb
# cyblafb, bug 466280
blacklist cyblafb
blacklist encode-big5
blacklist encode-gb
blacklist encode-gbk
blacklist encode-jis
blacklist encode-kscm
blacklist fbcon-afb
blacklist fbcon-cfb2
blacklist fbcon-cfb4
blacklist fbcon-hga
blacklist fbcon-ilbm
blacklist fbcon-iplan2p2
blacklist fbcon-iplan2p4
blacklist fbcon-iplan2p8
blacklist fbcon-mac
blacklist fbcon-mfb
blacklist fbcon-vga
blacklist fbcon-vga-planes
blacklist fbgen
blacklist g450_pll
blacklist hgafb
blacklist i2c-matroxfb
blacklist i810fb
blacklist intelfbdrv
blacklist intelfbhw
blacklist matroxfb_accel
blacklist matroxfb_base
blacklist matroxfb_crtc2
blacklist matroxfb_DAC1064
blacklist matroxfb_g450
blacklist matroxfb_maven
blacklist matroxfb_misc
blacklist matroxfb_proc
blacklist matroxfb_Ti3026
blacklist mdacon
blacklist neofb
blacklist pm2fb
blacklist pm3fb
blacklist rivafb
blacklist sisfb
blacklist sstfb
blacklist tdfxfb
blacklist tridentfb
blacklist unikey
blacklist vga16fb
blacklist vgastate
blacklist vmware
# for kyrofb see Bug 35810
blacklist kyrofb
# list was not complete (bug 106715)
blacklist arcfb
blacklist backlight
blacklist lcd
blacklist cirrusfb
blacklist gx1fb
blacklist intelfb
blacklist macmodes
blacklist nvidiafb
blacklist s1d13xxxfb
blacklist savagefb
# additional modules since SLE11, bug 468964
blacklist arkfb
blacklist carminefb
blacklist gxfb
blacklist hecubafb
blacklist lxfb
blacklist s3fb
blacklist sm501fb
blacklist viafb
blacklist vmlfb
blacklist vt8623fb
# ISDN modules are load from /lib/udev/isdn.sh
blacklist fcusb
blacklist fcusb2
blacklist fxusb
blacklist fxusb_CZ
blacklist fcdslusb
blacklist fcdslusb2
blacklist fcdslusba
blacklist fcdslslusb
blacklist fcdslslusb2
blacklist e2220pc
blacklist e5520pc
blacklist bfusb
blacklist b1isa
blacklist b1pci
blacklist b1pcmcia
blacklist c4
blacklist t1isa
blacklist t1pci
blacklist divas
blacklist act2000
blacklist hfc_usb
blacklist hisax
blacklist hisax_fcpcipnp
blacklist hisax_st5481
blacklist hysdn
blacklist icn
blacklist pcbit
blacklist sc
blacklist tpam
blacklist fcpci
blacklist fcclassic
blacklist fcdsl
blacklist fcdsl2
# mISDN modules
blacklist hfcsusb
blacklist hfcpci
blacklist hfcmulti
blacklist l1oip
blacklist mISDN_dsp
blacklist mISDN_core
# OSS PCI sound modules
blacklist ad1889
blacklist ali5455
blacklist btaudio
blacklist cmpci
blacklist cs4281
blacklist emu10k1
blacklist es1370
blacklist es1371
blacklist esssolo1
blacklist forte
blacklist i810_audio
blacklist maestro
blacklist maestro3
blacklist nm256_audio
blacklist opl3sa2 # Bug 219758
blacklist rme96xx
blacklist sonicvibes
blacklist trident
blacklist via82cxxx_audio
blacklist ymfpci
# If you really need firewire direct networking, then remove this entry
blacklist eth1394
# this is a debugging module which should only be loaded manually
blacklist evbug
# These mtd drivers should be loaded manually.
blacklist scb2_flash
blacklist ich2rom
blacklist pci
blacklist l440gx
blacklist amd76xrom
# job of rcdvb
blacklist snd_bt87x
blacklist snd-bt87x
# HP Touch Screen usb input driver. breaks all other mouse input devices
blacklist tsdev
# https://bugzilla.novell.com/show_bug.cgi?id=115132
blacklist slamr
blacklist slusb
# This module seems to be good for nothing. See bug 129301.
blacklist dpt_i2o
# This driver is obsolete and should never be loaded as default.
# See https://bugzilla.novell.com/show_bug.cgi?id=146728
blacklist eepro100
# This driver is obsolete and should never be loaded as default.
# See https://bugzilla.novell.com/show_bug.cgi?id=146930
blacklist sk98lin
# This driver is rarely needed and causes trouble when scanning devices.
# See: https://bugzilla.novell.com/show_bug.cgi?id=144623
blacklist stradis
# These devices have bt878 chip without PCI Subsystem ID. Without that info bttv
# does not know how to treat them properly. Therefore we disable autoloading of
# modules for these devices.
# See https://bugzilla.novell.com/show_bug.cgi?id=149588
# To enable your device create a hardware configuration file for your device.
# See man hwup for details.
# You will probably have to specify an option to identify your card. Have a
# look in /usr/src/linux/Documentation/video4linux/CARDLIST.bttv.
alias pci:v0000109Ed0000036Esv00000000sd00000000bc04sc00i00 bttv_skip_it
alias pci:v0000109Ed00000878sv00000000sd00000000bc04sc80i00 bttv_skip_it
install bttv_skip_it /bin/echo "module alias skipped (bt878 chip without PCI Subsystem ID)"
# For some bridges both intel-agp and i82875p_edac are loaded. If i82875p_edac
# is loaded first it will grab the device. Then intel-agp doesn't work.
# Therefore we disable automatic loading of 82875p_edac. (Bug 213840)
blacklist i82875p_edac
#
# Blacklist the IBM s390 module for I/O dynamic configuration support
# Bug bnc#478601
blacklist chsc_sch
# uas has been confirmed to be hopelessly broken
# Bug bnc#770301
blacklist uas
sorry, my fault, as tha’ts not what I meant … what I had intended was for you to get rid of any personalised changes to the xorg config files you’ve made (or the aborted catalystt/fglrx install may have) … but not to worry, as deleting all the default xorg.conf.d files is not going to be disastrous by any stretch of the imagination for you.
and also rebuilt initrd (using “mkinitrd” command/program (/sbin/mkinitrd)). But it didn’t make any difference, I still see the green progress bar instead of Plymouth splash.
okay … I have another thing in mind but could you first boot into runlevel 3 (if ur unaware, you can do that in by hitting “e” in grub and then appending an “3” at the end of the linux boot line and then f10 to boot the temp config) … then at the console prompt, login and then provide the output of “/sbin/lspci -nnk | grep VGA -A2” … specifically, what driver does it say is in use?
Do I need to delete also /etc/X11/xorng.conifg
yes, if you have a xorg.conf file, delete it or rename it xorg.conf.old or whatever.
& /etc/X11/xorng.config.install?
no, leave that – its used by the recovery mode boot
Right now, after 2 reboots, X has created only one config file named “90-keytable.conf” in /etc/X11/xorg.conf.d.
that’s fine … don’t worry about anything in there – all I’d wanted to clean out was any changes from the defaults.
I don’t know if it’s part of openSUSE normal boot process or not, but I see “doing fast boot” (or something like that) before the progress bar shows up.
yes, that’s normal
Here is the content of /etc/modprobe.d/50-blacklist.conf (I also have a “blacklist.conf” in /etc/modprobe.d/, but it’s empty (maybe I’ve created it by mistake)).
all we want is to make sure the radeon kernel driver isn’t being blacklisted at boot.
Hey,
First I’m sorry for the late reply again. Second, it’s very weird: I posted a reply yesterday, but when I came back (copule of minutes ago) to check for an answer, I noticed that my post has been disappeared. There was’t anything wrong with that, so I don’t think that moderators have removed that. What happended to my detailed post?!
OK., so I have to write that again. I deleted the config files, and rebuit initrd (using “mkinitrd” program(compiler?)). But nothing changed!
My guess is that the radeon DRM kernel driver is loading late … so plymouth’s drm render (which requires the DRM/KMS driver) fails and so it falls back to text mode. Here are some things to try:
check in /etc/sysconfig/kernel to see whether you have the “no_KMS_IN_INITRD” value set “No” … if its set to “yes”, change it to “no” and then rebuild the initrd
use the kernel boot parm "plymouth.debug=stream:/dev/kmsg" ... (you do that similar to how you booted into rl3 by appending it to the linux line in grub) ... it will then place plymouth debug log messages into "dmesg" output ... copy your dmesg to [susepaste](http://paste.opensuse.org/) and provide us a link
plymouth itself also has a command to rebuild the initrd, but I don’t know offhand if it does anything differently then a regular build
NO_KMS_IN_INITRD was set to “yes” (why?), so I changed it to “no”, and rebuilt the initrd. The plymouth’ splash now loads! Thank you so much.
And here’s dmesg’s output.
By the way, the rotated play back problem still exists in VLC, though yesterday I installed smplayer, and it didn’t have any problem with videos (probably initrd is only for boot time (?), but even before changing NO_KMS_IN_INITRD’s value, smplayer used to play videos correctly (and still plays correctly)). Isn’t it wierd? only smplayer manages to play the videos correctly, even mplayer itself doesn’t show the videos at all and only I I hear the sound of the video that’s being played. VLC playes them back with 90 degrees of rotation and Kaffeine doesn’t play any video at all!
PS:
I decided to give smplayer a shot after you guys said you use it and it’s better. It’s so fast, and amazing! Thanks for the suggestion. Its youtube player is much better than Youtube’s own web interface.
I use gist for sharing code and text, but this opensuse paste also seems promising.
](https://forums.opensuse.org/members/caf4926.html)@caf4926
I didn’t undestand what you said? Am I using the grub for the same what? what “install” do you mean? do you mean do I use the same grub file to “boot” to other distros? If so, yes, I’ve written grub2 to MBR (and also have it on all my partitions), so after each rebuild of initrd, it overwirtes the new grub2, and deletes my windows chainloader, so I boot to my Linux Mint and run Grub Customizer to resotre my previous (backed-up) grub2 and overwrite it to MBR.
