I used the latest Kernel and the latest drivers from ATI, and I get this error at step 4:
- trying a sample load of the kernel modules
Then, try reinstalling the driver. As for your VirtualBox issue: even if your kernel panics are no longer a problem, it is my totally unsolicited recommendation that you use KVM over VirtualBox. Does it have something to do with the login prompt?
And +1 for Thoreau reference bitwiseoperator says: December 14, 2014 at 7:16 pm Haha, thanks man. Please sign in help tags people badges ALL UNANSWERED Ask Your Question 0 Radeon HD5470 drivers? I always use the same login, so I've just ignored the issue: I press enter, nothing happens, enter password, and poof! After you upgraded, just change back to the directory where you extracted the driver files and issue the install command with the -force option added. http://forums.fedoraforum.org/showthread.php?t=293090
If I hit "enter", type in password, enter again, I'd get my KDE desktop. Reply bitwiseoperator says: November 23, 2014 at 9:59 am 1) Why are you so behind on your kernel updates!? Reply spookyfox says: April 19, 2016 at 10:20 am I realized that eventually and installed it.
Check if system has the tools required for installation. LucetLux View Public Profile Find all posts by LucetLux #4 5th August 2013, 08:01 PM wintonian Offline Registered User Join Date: Jul 2013 Location: UK Posts: 203 It If the drivers are supposedly designed for the new X server, what the heck version Xorg 7,4 did ATI use? and then gives up altogether:- > (EE) no screens found(EE) This happens irrespective of whether the module parameter radeon.runpm = 0 or not.
If you need 3D Hardware support, don't use Fedora 13. Ati Drivers Are you sure that you used the correct patch ( nenad's fglrx_kernel.4.6.diff.patch ) and that it was correctly applied? what should i do to keep it working after updating the kernel?(should i use Catalyst-hook/Catalyst-generator?)Thanks everyone! https://ask.fedoraproject.org/en/question/6994/radeon-hd5470-drivers/ Without that, Xorg may fail to start properly after uninstalling the driver and rebooting the system.
Uninstalling any previously installed drivers. JoJo says: July 18, 2016 at 3:37 am I have the same issue with Gnome or Gnome Classic, that is a black screen with mouse working. Let me ask this: When Fedora is booting and you have the blue screen with the white area that fills up with the logo… is that X running there or is But the drivers also contain modules for older Xorg servers that do not call UpdateSpriteForScreen.
also, I'm not sure but I think you need to do sudo aticonfig - -initial at the end. This driver is driving me crazy! Error Module Radeon Is In Use Fedora Ensure that you do not select "Generate Distribution Specific Driver Package (Recommended)". This will only work if you use one of the officially supported Linux distributions listed on AMD's site (Fedora Amd cleaning build area… DKMS: build completed.
For instance, applying this blacklist in /etc/modprobe.d/blacklist-fglrx.conf: # Advanced Micro Devices, Inc. # radeon conflicts with AMD Linux Graphics Driver #blacklist radeon blacklist fglrx blacklist amd_iommu_v2 blacklist fglrx_pci and removing xorg.conf Last edited by wintonian; 5th August 2013 at 05:05 PM. Here is dmesg : [ 43.863812] [fglrx] Firegl kernel thread PID: 1217 [ 43.863970] [fglrx] Firegl kernel thread PID: 1218 [ 43.864238] [fglrx] IRQ 31 Enabled [ 43.876306] [fglrx] Reserved FB Like an hour had passed since that crash, and I had already forgotten about it, when completely unlooked for, the x-server crashed and recovered again, I was starting to worry.
I am really, really disappointed with AMD. Tried uninstalling catalyst to re install, gave error, so I forced it and I still get black screen, not sure how to fix this or go back to mesa drivers. It must be coming from somewhere...i regenerated it and restarted system and everything works fine.And there is no nomodeset in the regenerated grub.cfg. The package(s) you need are likely kernel-devel and/or kernel-headers.
on Installing the Proprietary AMD…survient on Installing the Proprietary AMD…nenad on Installing the Proprietary AMD…Jhon on Installing the Proprietary AMD…nenad on Installing the Proprietary AMD… Archives October 2016 September 2016 August nmreis@e6440c-laptop ~]$ DRI_PRIME=1 glmark2 ======================================================= glmark2 2014.03 ======================================================= OpenGL Information GL_VENDOR: X.Org GL_RENDERER: Gallium 0.4 on AMD HAINAN (DRM 2.43.0, LLVM 3.7.0) GL_VERSION: 3.0 Mesa 11.0.0 (git-c4bae57) ======================================================= Comment 4 ja The only way to get my workstation back, was entering in safe mode, uninstall the AMD drivers, reboot.
BTW, thanks for the great page! Now it looks as if I can upgrade with confidence. I think AMD is well aware that people would like them to support GNOME, and they're definitely aware that people actively avoid their products because of poor Linux support, but they I've had gaming systems for the past 17 years, keeping up with the current wave of games and the hardware and software required to play them, and the idea that an
kernel 4.3.5-300.fc23.x86_64 Comment 19 vip.zhijian 2016-03-03 12:28:10 EST I have the same problem on an ASUS F554L using Fedora 23 upgraded from Fedora 22. After I run the install gui in step 8, I got the message: "Your graphics adapter is not supported by this driver. If that still doesn't work, feel free to post terminal output and I'll be glad to help. I moved to Fedora from Ubuntu because of various concerns with that particular distribution, back in Ubuntu I just used the drivers from amd's site and they worked perfectly, I just
Trying to use vga_switcheroo with echo DDIS > /sys/kernel/debug/vgaswitcheroo/switch results in a reversion to the login screen with a message saying that client 0 refused to switch, or in a totally However no info about Linux version. To be fair, Trinidad AMD chipset is not listed on the radeon driver supported list, but they do say the list is not all-inclusive. Given that Xorg downgrades have been necessary up until now, and the version to which one must downgrade is all the way back in the soon-to-be-unsupported Fedora 22, we might be
PS: The NVIDIA machine has been a charm -- it worked with bumblebee right away, and it still works months later, and after many "yum update"s.. Thanks for the input!