Good day all,

I have a HP h8-1520t desktop with a Radeon HD 7570 video card (from what I understand is the same as the HD 6570). The issue is I'm having a problem with a recent upgrade to Fedora 20 (kernel-3.15.5-200.fc20.x86_64). Everything worked well with Fedora 19, but since the upgrade, the display is shifted (or offset) to the right of the screen. But it appears to be random. Sometimes it's shifted to the far right, sometimes it's shifted halfway to the right, and other times it's perfectly normal.

If I use the 3.15.6 kernel, it boots as if I had modeset=0 as a boot option (1024x768 resolution) and the display is centered properly.

I don't see any glaring errors in the log files so I'm not sure what to do about this. Any help would be appreciated.

Also I am aware that Fedora 20 has dropped support for the proprietary AMD Cyatalyst driver, but to be honest, I don't know if that's what I was using before the upgrade.

$>uname -rv
3.15.5-200.fc20.x86_64 #1 SMP Mon Jul 14 15:40:08 UTC 2014

$>sudo lspci -vnn |grep VGA -A 14
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 7570] [1002:675d] (prog-if 00 [VGA controller])
Subsystem: Pegatron Device [1b0a:90bc]
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at e0000000 (64-bit, prefetchable) [size=256M]
Memory at f7e20000 (64-bit, non-prefetchable) [size=128K]
I/O ports at e000 [size=256]
Expansion ROM at f7e00000 [disabled] [size=128K]
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
Capabilities: [150] Advanced Error Reporting
Kernel driver in use: radeon
Kernel modules: radeon

$>monitor-edid
Name: Linux FHD
EDID version: 1.3
EDID extension blocks: 0
Screen size: 50.0 cm x 28.1 cm (22.58 inches, aspect ratio 16/9 = 1.78)
Gamma: 2.2
Analog signal
Max video bandwidth: 150 MHz

HorizSync 66-68
VertRefresh 59-61

# Monitor preferred modeline (60.0 Hz vsync, 67.5 kHz hsync, ratio 16/9, 97 dpi)
ModeLine "1920x1080" 148.5 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync

Xorg.0.log and excerpts from messages are attached.

Attached Files

	Xorg.0.log (52.0 KB, 22 views)
	grep.radeon.messages.log (6.9 KB, 33 views)

3.15 seems to have regressed a bunch of radeon issues. I have a 4670, and have been unable to hibernate since 3.15 hit F20 - was fine on 3.14 kernels. Suspend only works with "radeon.dpm=0" on 3.15 kernel option.
I haven't seen the screen issues you have - even before I added radeon.dpm

Your pc was using the radeon module/driver that was installed by default.
Otherwise you would have had to of downloaded the AMD driver and install it via the terminal.
I have not had success with the AMD/ATI drivers, if anything they are buggy:-

You could (if you want to) roll back to kernel 3.14 for a while at least until Fedora 21 is released.

OK, that's not what I was wanting to hear, thanks all the same though. At least I'm now fairly confident that it's not a bad configuration issue. I guess I'll have to revert to 3.14 until such time.

I didn't mean to be the bearer of bad news. Sorry-

Has rolling back to kernel 3.14 helped?

I downloaded the 3.14.13 kernel, compiled it with a config similar to the 3.15.6 kernel, (particularly ->Device Drivers-> Graphics support), created an initramfs.3.14.3 and booted several times. It has the same problem as 3.15.6, the display is being shifted right as soon as graphics is enabled you can see the boot messages shifted to the right. ( "splash" and "quiet" are removed from grub boot line) In an effort to grasp for straws, I unplugged the PC/monitor overnight, just to see. No change, and Windows boots fine.

It appears to me that it may have something to do with KMS and the radeon driver not initializing the card or some related variable correctly eventhough the card is identified properly. I would file a bug, but I don't know who to file it with, plus I don't know the source of the problem, just the symptoms. I did notice that there are a bunch of fairly significant radeon related patches in the 3.16-rc6 kernel, so it may be already solved.

I would like to see a release (or find a fix) soon as re-installing is not one of my favourite pastimes, especially since I don't have a backup (I know, I live dangerously). But I imagine now is probably not a bad time for one, albeit a wee bit late

I'm not sure if this will help but I looked up KMS on this Arch WiKi-
I know your not running Arch but it might work.

You may want to disable KMS for various reasons, such as getting a blank screen or a "no signal" error from the display, when using the Catalyst driver, etc. To disable KMS add nomodeset as a kernel parameter. See Kernel parameters for more info.

Along with nomodeset kernel parameter, for Intel graphics card you need to add i915.modeset=0 and for Nvidia graphics card you need to add nouveau.modeset=0.
https://wiki.archlinux.org/index.php...l_mode_setting

As far as a bug report; now that Mr. Matthew Miller is the new Fedora Project Leader I am not sure entirely what has changed and the protocol for filling a bug is now. I think you still need a Bugzilla Account.
http://fedoraproject.org/wiki/How_to_file_a_bug_report

Or it could be like Syg00 mentioned that it's associated with kernel regression.
If indeed it's a kernel bug this is a start:
https://www.kernel.org/pub/linux/doc...ting-bugs.html

Aside from that I wonder if building a driver from src would be the answer?
(just an idea)

If i'm not mistaken it's radeon.modeset=0 for me (radeon card as oppsed to Nvidia) which disables Kernel Mode Settings for radeon cards, which works, but it also means I'm stuck in geriatrics video mode. I'm starting to wonder if this is indeed a kernel bug or something else. It can't be my kernel config, becuase the yum install Fedora 20 kernels exibit the same behaviour. (I'll test that a few more times just to verify)

syg00 may be right, but I'm not convinced that's my problem just yet, especially having tried the 3.14 kernel, I'm leaning towards some Fedora 20 quirk. I'd like to understand what the issue is rather than just re-installing to get rid of it, but GUIs really aren't my thing.

Building it outside of the kernel build? hhmm... That's a thought.

Here's another thought: "The complexity of computational simplicity"
I think I'll use that as my tagline

-:GUI's are not my thing either:-

I had thought that re-compiling the kernel would of helped. If fact it's puzzling why it didn't solve the issue. Evidently the last resort of installing the most cutting edge kernel (3.15.6) if I had to guess isn't going to solve the problem if rolling back to 3.14 wasn't productive to begin with.
I can see where this is tad frustrating for you.
Sorry, I don't know what else to try-

Your new tagline not only makes me smile LOL! It's incredibly genius!

I should note that I upgraded to F20 via the aptly named "fedup" process. So I decided to try a fresh F20 install on an external drive - same machine. The installed kernel 3.11.10-301 works, and a functional radeon driver is in use, I can't speak to any enhanced features.

After a "yum update" the shifted display problem, not too surprisingly occurs again.

The culprit is definately a package from the Fedora 20 upgrade, the problem is isolating which one. As a note, I did try the 3.15.6 kernel, yum upgrade and build from source, same issues.

As I said I had no issues on F20 until the first update that introduced a 3.15 kernel - lots of updates to video in that, some of which have been rectified. Some not.

It could very well be a pkg; or maybe the lack of a module/driver is the issue.
One way (I'm thinking) is to read through the kernel change logs to see what has changed, added, or taken away.

What I am wondering and pondering now is what does kernel 3.15 lack that the kernel that did work for you have?

Isolating which one will most certainly so be the challenge.

Good luck-

Hi!

I have HD 6850 and Kernel 4.4.14.

radeon.dmp=1 and boot black screen halt appeared for me when I changed rootflags.
Solved with rootflags=relatime,lazytime,commit=60 in kernel parameters and in options in fstab.

I believe dpm need some fs information to work well, maybe its causing mess in your system too.

HTH

Best regards
Weber Kai

if you installed fedora 20
-- you have a PROBLEM


this thread is over 2 years old

fedora 20 is unsupported
fedora 21 is unsupported
fedora 22 is unsupported
and
fedora 23 will be unsupported soon