I've a Toshiba Satellite Pro C850-147 with O.S. Ubuntu 14.04.4 LTS. Its graphic card is an AMD Radeon HD 6610M/7610M. With all kernel version from 3.x to 4.5.x the screen resolution worked well with the 1366x768 setting. After the upgrade to kernel version 4.7.0-rc3-generic the screen resolution is now 1024x768. The 1366x768 value doesn't appears anymore in the resolutions list box of my monitor settings panel. Best Regards Luca Ercoli
I've the same problem with kernel version 4.6.2.
Created attachment 225641 [details] error log for graphics problem Radeon HD7670M kernel 4.6.4
I have got the same problem with a Toshiba Satellite L850-1CC with an AMD Radeon HD 7670M. The maximum screen resolution is also 1024x768 instead of 1366x768. Additionally the screen flickers when i open the application menu in KDE. Currently I am working on Fedora 24 and the problem occured with the installation of the 4.6.3 Fedora kernel and is also existing with 4.6.4 Fedora Kernel, 4.7rc7 vanilla Kernel on Fedora, 4.6.4 on openSUSE tumbleweed an an 4.6 on archlinux. If i boot an the kernel 4.5 or older everything is normal. The error I get is in the attachement "error log for graphics problem Radeon HD7670M kernel 4.6.4" Best Regards Lukas Pichler
Hello, This bug #120321 has a duplicate as bug #141741, which itself has a duplicate as bug #175391. Troubleshooting was the most advanced in bug #175391 thread, eventually leading to a fix. I invite you to then carefully read the full threads of *both* bugs #141741 (as an intro) *and* #175391 (troubleshooting and fix per se). In hope this helps. Sincerely, Valentin
Could you test this with v4.9? It includes a change that is related: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=16d917b130d7 ("PCI: Don't attempt to claim shadow copies of ROM"). If the problem still occurs on v4.9, please attach the complete dmesg log.
I've kernel version 4.10-rc1. Should I test on this kernel version ?
Sure, testing v4.10-rc1 would be fine. v4.10-rc1 contains the bugfix I mentioned, as well as a lot of new material. The new material probably includes some new unrelated bugs as well, so it's possible you'll trip over one of them. But hopefully, *this* bug is fixed in v4.10-rc1.
On kernel v4.10-rc1 it works.
Great, thank you for testing it! I'll close this bug report.