Ask Your Question
2

Fedora 28: Screen resolution not working

asked 2018-07-24 06:04:33 -0600

starchyme gravatar image

updated 2018-07-26 03:05:55 -0600

hhlp gravatar image

Did a new install of Fedora 28, and my monitor no longer can be selected to change from 1024x768 to 1366x768. On Fedora 27 this worked correctly.

I have tried many suggestions from changing "nomodeset", "UEFI"-stuff to "xandr" and monitor detection routes with no success.

My monitor is an Acer v93HQL and is 1366x768 capable. Regression back to F27 will be painful. Are there perhaps a stepped approach to resolving the screen resolution issue?

Using AMD/Radeon 8570HD graphics card. (Worked on F27, so expecting F28 to retain support for card/screen at least)

Outputs:
cat proc/cmdline: 
BOOT_IMAGE=/vmlinuz-4.17.7-200.fc28.x86_64 root=/dev/mapper/fedora_localhost--live-root ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet LANG=en_ZA.UTF-8 nomodeset

xrandr:
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
default connected primary 1024x768+0+0 0mm x 0mm
   1024x768      76.00*

inxi -SGxxxz:
System:
  Host: localhost.localdomain Kernel: 4.17.7-200.fc28.x86_64 x86_64 
  bits: 64 compiler: gcc v: 8.1.1 Console: tty 1 wm: KWin dm: gdm,sddm 
  Distro: Fedora release 28 (Twenty Eight) 
Graphics:
  Card-1: AMD Richland [Radeon HD 8570D] driver: N/A bus ID: 00:01.0 
  chip ID: 1002:990e 
  Display: server: Fedora Project X.org 1.19.6 
  driver: ati,fbdev,modesetting,radeon unloaded: vesa 
  compositor: gnome-shell resolution: 1024x768~76Hz 
  OpenGL: renderer: llvmpipe (LLVM 6.0 128 bits) v: 3.3 Mesa 18.0.5 
  compat-v: 3.0 direct render: Yes
edit retag flag offensive close merge delete

Comments

If after system update (e.g. using sudo dnf update --refresh) and reboot problem still persists, edit you question and add output of:

  • cat /proc/cmdline
  • xrandr
  • inxi -SGxxxz
ozeszty gravatar imageozeszty ( 2018-07-24 07:12:31 -0600 )edit

It was nto an upgrade. Clean install. performed functio in any case with no difference. The question has been edited with the required outputs.

starchyme gravatar imagestarchyme ( 2018-07-24 10:05:54 -0600 )edit

remove nomodeset, once you are certain that the correct video driver is installed, by running lsmod to see which vga driver is being used. What i understand is that open source for AMD cards is better than the AMD provided drivers.

SteveEbey73701 gravatar imageSteveEbey73701 ( 2018-07-24 10:46:00 -0600 )edit

When "nomodeset" is removed, then Fedora crashes immediately at startup and reboots. this then carries on in a continious loop untill nomodeset is placed back in.

starchyme gravatar imagestarchyme ( 2018-07-24 11:55:25 -0600 )edit

Have this started immediately after installation or after an update to latest F28 packages? Is this also happening on a live system booted from USB stick?

ozeszty gravatar imageozeszty ( 2018-07-24 15:51:18 -0600 )edit

Yes. this was the case right after fresh installation. the screen resolution was the first thing I wanted to change.

To test the question on the LIVE system I attempted to start the PC with the LIVE disk, but came up with SELinux permission denied on /run/rootfsbase and then then rebooted... but differently because it then started with the normal Fedora image loadup screen and not the three dots. however, my mouse and keyboard was not working after. So rebooted and the normal startup ocurred with everything functional but screen resolution.

Unable to boot my system up with LIVE now also.

starchyme gravatar imagestarchyme ( 2018-07-25 00:17:31 -0600 )edit

Here are updated Fedora images, use them for testing of live system: https://dl.fedoraproject.org/pub/alt/...

To rule out hardware issue you could Live-boot Fedora 27 and if it'll work fine, then you'll know it's a regression in F28. In that case for bugzilla you'll need some logs from boot without nomodeset kernel parameter, look in journalctl for errors with drm, radeon, x.Org.

Make sure that signal cable is properly plugged-in to the PC and monitor.

ozeszty gravatar imageozeszty ( 2018-07-25 04:13:15 -0600 )edit

As a quick test I used my Fedora 23 Live boot USB (because I used upgrade and did not use a disk from F23 - F27) F23 booted up one shot and started the display in 1366x786 resolution. Cables and connections fine. In fact I am considering regressing to F23. The performance is awesome. works better in LIVE than full setup. So this then means it is not a cable issue. This is a regression and serious issue I am experiencing in the F28 video rendering modules somewhere for AMD/64bit. I took a camera pic, but cannot insert it here it seems. any other ideas? cannot boot without nomodeset.

starchyme gravatar imagestarchyme ( 2018-07-25 05:58:55 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted
1

answered 2018-07-26 01:32:02 -0600

starchyme gravatar image

running "modprobe radeon modeset=1" resolved the problem.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2018-07-24 06:04:33 -0600

Seen: 1,134 times

Last updated: Jul 26 '18