Tommy, if you did not install fglrx under 3.13.0-43, could you perhaps
try to boot using the new kernel with "radeon.runpm=0" appended to the
GRUB command line? According to this [1] bug report this might work. I
can't really do that because uninstalling fglrx is too unreliable.
[1]https://bugzill
True, especially because installing fglrx is sometimes quite a pain and
not really an option for many out there, as you pointed out.
I just checked in the kernel.org bugtracker and it appears that this is
actually a known bug
(https://bugzilla.kernel.org/show_bug.cgi?id=88481). This bug was,
howev
This also affects me on Xubuntu 14.04.1 and Elementary OS 0.3 Beta 1.
I'll attach my lshw output and will try to generate a proper set of logs
tomorrow.
** Attachment added: "lshw.html"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1402386/+attachment/4281153/+files/lshw.html
--
You r
Interestingly, I was able to resolve this issue on 3.13.0-43-generic
(eOS Freya) by installing the current AMD proprietary driver, version
14.12 in tty1 which I was - curiously - able to access when basically
hammering the keyboard as soon as the OS logo showed up. This started
for me by issuing an
4 matches
Mail list logo