This guides your through installing AMD ATI proprietary driver (fglrx) in Kali Linux 1.0.6 running Kernel version 3.12.6 and get amdcccle work. Catalyst Control. Install AMD drivers on Kali 2.0 [duplicate]. To install AMD Catalyst on my Kali 2.0. To install without the tools. Forcing install will disable AMD hardware.
This video teaches you how to install the latest AMD Catalyst Drivers. This should work with all Linux OS's and all of the video cards. I'm happy to help if you need, just leave a comment in the comment section. (ctrl + alt + t) Terminal: sudo apt-get install dkms fakeroot lib32gcc1 libc6-i386 libfakeroot libqtcore4 sudo apt-get update Create Folder in home directory and rename it: AMD link: Download according to your OS. Place downloaded drivers (packages) inside “AMD” (ctrl + alt + t) Terminal: cd /home/yourusername/AMD sudo dpkg -i.deb sudo amdconfig -initial RESTART: Log in and check “About this computer”, if graphics says: AMD Radeon (TM) R9 390 Series Then you have correctly installed the AMD Catalyst drivers for your R9 390, Enjoy.
Song: Ivan B - Happy Feels Software: Kazam, Audacity, Blender, Kdenlive.
Step by step guide to install proprietary fglrx driver in Kali Linux Following instructions were tested on 64-bit Kali Linux 1.0.6 running Kernel version 3.12.6: lsbrelease -a Output: No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux Kali Linux 1.0.6 Release: Kali Linux 1.0.6 Codename: n/a Step 1 ( Check your /etc/apt/sources.list. If it’s anything different to the following, you need to fix it. You can follow this guide to if you’re not too sure on how to do it. For the sake of clarity I will keep things simple here. Leafpad /etc/apt/sources.list Remove or comment out existing lines and add the following: ## Kali Regular repositories deb kali main non-free contrib deb kali/updates main contrib non-free ## Kali Source repositories deb-src kali main non-free contrib deb-src kali/updates main contrib non-free Step 2 (update with apt-get) Now we need to update and make sure we get the latest list from Kali Linux official repositories. So perform an apt-get update.
Apt-get update STOP: NVIDIA users after driver installation and cuda/pyrit related issues go here: Also those who would like to use Graphics card processing power to crunch data (such as cracking wii password faster) see the following posts:. I have amd radeon 7310 installed on my laptop, i follow your intruction to install driver but when i finish this intruction i type 'fglrxinfo' to test my vga, but this is the result, fglrxinfo display::0.0 screen: 0 OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 0x209) OpenGL version string: 1.4 (2.1 Mesa 8.0.5) i think there is something wrong, please reply ASAP thanks sorry for my bad english:) note: i don't see bunch of popups like you said in step 4. Same issue here, but I have installed Kali (fresh new install, new formatted partition) with kernel 3.7 I proceed to apt update, upgrade and dist-upgrade.
Then kernel is 3.12, lsbrelease replies as expected (1.0.6). At this point nothing but the default drivers are installed. Then I follow the instructions from this howto and I also get Gallium 0.4 and mesa when querying fglrxinfo. Which packages should I have removed or installed previously? I use a AMD Radeon 7600M (same as you, I guess).
Thanks for the guide and your efforts. Hi, thanks for your awesome HOWTOs but I am confused a little bit: I followed your guide with a fresh installed Kali 1.0.6 started with this guide here. Card: PowerColor R9 290X PCS+ root@ozo:# fglrxinfo display::0.0 screen: 0 OpenGL vendor string: Advanced Micro Devices, Inc. OpenGL renderer string: AMD Radeon R9 290 Series OpenGL version string: 4.3.12618 Compatibility Profile Context 13.251 but when I am checking via System Settings – Details I see Graphics: VESA: HAWAII root@ozo:# grep -i vesa /var/log/Xorg.0.log 3.167 (II) fglrx(0): VESA BIOS detected 3.167 (II) fglrx(0): VESA VBE Version 3.0 3.167 (II) fglrx(0): VESA VBE Total Mem: 16384 kB 3.167 (II) fglrx(0): VESA VBE OEM: AMD ATOMBIOS 3.167 (II) fglrx(0): VESA VBE OEM Software Rev: 15.42 3.167 (II) fglrx(0): VESA VBE OEM Vendor: (C) 1988-2010, Advanced Micro Devices, Inc. 3.167 (II) fglrx(0): VESA VBE OEM Product: HAWAII 3.167 (II) fglrx(0): VESA VBE OEM Product Rev: 01.00 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. AMD/ATI Hawaii XT Radeon R9 290X (prog-if 00 VGA controller) Kernel driver in use: fglrxpci So which driver I am using?
Thanks for your help and reply! I get the same thing and mine works fine: $ grep -i vesa /var/log/Xorg.0.log 68.051 (II) fglrx(0): VESA BIOS detected 68.051 (II) fglrx(0): VESA VBE Version 3.0 68.051 (II) fglrx(0): VESA VBE Total Mem: 16384 kB 68.051 (II) fglrx(0): VESA VBE OEM: AMD ATOMBIOS 68.051 (II) fglrx(0): VESA VBE OEM Software Rev: 13.10 68.051 (II) fglrx(0): VESA VBE OEM Vendor: (C) 1988-2010, AMD Technologies Inc. 68.051 (II) fglrx(0): VESA VBE OEM Product: CAYMAN 68.051 (II) fglrx(0): VESA VBE OEM Product Rev: 01.00. This was so helpful I did have hashcat working but kept crashing followed your step by step guide worked great the only bit that didnt work for me was the fglrxinfo this didnt show like yours so i ignored did the rest of the steps after reboot did fglrxinfo again this time i did get the output that you had so knew all was good. So you are aware the below azan is what i saw before my reboot OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 0×209) this is a hard machine not a virtual machine. It did all work for me many thanks I did see the posts in the kali forums too thanks again Dave.
Nice guide, with nice errors.! Explain why “radeon.modeset=0” should be added to the boot.cfg? I did follow this guides and had lot of errors and damaged the grub. What u talking about, Grub 1 or Grub2? How ever, on my Grub 1 (20GB partition) I DON’T added the moddeset and all works fine!
On Grub 2 I FIXED my grub.cfg REMOVING the radeon.modeset=0 from the grub.cfg! So just do the whole procedure without touching your grub if you got problems after this install – make aticonfig and that’s all for the AMD Catalyst Install. I should probably give you my lspci, would be helpful. Hi Daniel, Your card is exactly same as mine (on my Laptop – Radeon 7500M/7600M Series). Unless your Kali Linux installation is heavily modified (i.e. You tried linking lib and GL.so like some of the forums/blogs claims to fix their issue, and got PPA or unofficial repositories added), I see no reason why this solution wouldn’t work.
Also note that I use Kali v1.0.6 64-bit and I can’t confirm if this solution would work for 32-bit. (though package names are same but as AMD provides the driver, it is upto them to provide a standard solution for both 32 and 64 bit). Perhaps you could try a fresh install, update, upgrade and then try this guide. Alternatively, Kali forums and their IRC channel is always a good place to seek help.
Userbase in the forum is much larger and interactive. Cheers, -BMO. I’ve fixed the little code issue on Step 6. Sharp eyes indeed. Hello, I’ve been following your guide, but when entering apt-get install amd-opencl-icd, it tells me it can’t find the files: Reading package lists Done Building dependency tree Reading state information Done The following NEW packages will be installed: amd-opencl-icd 0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded. Need to get 14.1 MB of archives. After this operation, 39.5 MB of additional disk space will be used.
Err kali/non-free amd-opencl-icd amd64 1:14.4.2-1kali1 404 Not Found Failed to fetch 404 Not Found E: Unable to fetch some archives, maybe run apt-get update or try with –fix-missing? Even with –fix-missing uname Linux BLACKJACK 3.14-kali1-amd64 #1 SMP Debian 3.14.4-1kali1 (2014-05-14) x8664 GNU/Linux lsbrelease: No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux Kali Linux 1.0.7 Release: Kali Linux 1.0.7 Codename: n/a Thanks in advance. Doesn’t look like it – Thought I’d give it a go last night the gears app worked (dead slow 299 frames p/5s) until I rebooted then got errors when I tried to run the gears app Some posts saying that their beta driver goes up to 3.1.3 but nothing on 3.1.4. Aticonfig –list-adapters lists the adapter with no issue AMD Radeon HD7500M/7600M Series AMD officially doesn’t list Debian / Kali as a supported OS You’ll be able to find this sort of info quicker than I would anyway so I shall leave you to it:) Cheers, Ray. Hey doctorpopkorn maybe this will help Are you sure of the model number because this is what I found at HP 7 matches found. Please select one below HP G61-600 Notebook PC series HP G61-631NR Notebook PC HP G61-632NR Notebook PC HP G61-300 Notebook PC series HP G61-304NR Notebook PC HP G61-306NR Notebook PC HP G61-321NR Notebook PC HP G61-322NR Notebook PC HP G61-336NR Notebook PC I’m wondering if it is one of these.
This is where I would start then maybe on to the ATI site to verify if they have a driver / catalsyt for your model. Also if I am to read this correctly you tried on vmware? There is no solution as of yet that provides for proprietary drivers using vbox or vmware unless I am mistaken.
If you answer the first two questions ie which model and what does ATI say then I’m sure the rest will work out:). Sir I applaud your great work and commend you on your efforts. Myself if not for the Obsessive compulsive disorder would have been bald or dead by now. I have tried to follow every step and kept coming up empty, thank God for the OCD. I pushed through and can say I am now proficient at installing Kali as this is probably my 49 th time.
I have no idea why I can’t get the svn to work with pyrit and it wasn’t until yesterday that I realized calpp90 is different than the cpyritcalpp. Having downloaded the cpyritcalpp from sourceforge I am able to see the explanation of the line titled Edit setup.py file and modify/replace the followings: find VERSION = ‘0.4.0-dev’ and replace with VERSION = ‘0.4.1-dev’ find CALPPINCDIRS.append(os.path.join(CALPPINCDIR, ‘include’)) and replace with CALPPINCDIRS.append(os.path.join(CALPPINCDIR, ‘include/CAL’)). Maybe its just me or perhaps the svn of pyrit contains the cpyritcalpp, but a little light shedding on the subject may help some other learning impaired individual like me in the future.
I would however ask one question of you since you have vast knowledge, is there a way to bridge or install Nvidia and ATI side by side? Example on board ATI radeon and secondary Nvidia PCIe? If so could you please post a how to? One more small question if I may impose, why does the oclhashcat not provide a response using these steps?
Thanks again and good day to you HERO:) FYI system stats Asus F1A75-V Pro A8 quad core radeon 6550HD 16Gb ram 19455.0 PMKs/s PS the 1radtech is because I am a radiology tech Lol. Thanks for the nice snippet Having downloaded the cpyritcalpp from sourceforge I am able to see the explanation of the line titled Edit setup.py file and modify/replace the followings: find VERSION = ’0.4.0-dev’ and replace with VERSION = ’0.4.1-dev’ find CALPPINCDIRS.append(os.path.join(CALPPINCDIR, ‘include’)) and replace with CALPPINCDIRS.append(os.path.join(CALPPINCDIR, ‘include/CAL’)).
ATI/NVIDIA on same Computer? On-Board card will be disabled when you’re using PCIe card. (just like Intel/ATI or Intel/NVIDIA combination). Even if you manage to install both drivers (NVIDIA CUDA and ATI FGLRX/SDK), you can only use 1 card at anytime. If I remember correctly, it’s a Motherboard settings that controls how they behave. Thx for your guides. Got Nvidia Cuda working.
Now fighting with ATI. Could you advise on the ATI legacy drivers install?
Have 2x 4890s that I’d like to get working. I was able to install ATI legacy drivers with functional fglrxinfo + fglglxgears following this other guide. However Radeon listed as module and not fglrx. Nano /etc/apt/sources.list # Backported packages for Debian 7 “Wheezy” deb wheezy-backports main contrib non-free aptitude update aptitude install linux-headers-$(uname -r sed ‘s,^-.-^-.-,’) aptitude -r -t wheezy-backports install fglrx-legacy-driver Then following remaining part of this guide for AMD SDK/ CAL resulted in Pyrit still not find GPUs. First, thank you blackMORE Ops for those tricks and tips:) I have an hybrid graphic card: lspci grep VGA 00:02.0 VGA compatible controller: Intel Corporation Haswell Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: Advanced Micro Devices AMD nee ATI Mars Radeon HD 8790M Using your help, i tried to install fglrx-drivers. After installing everything, fglglxgears box worked well, but i had the VMware bug with Gallium renderer string with fglrxinfo. So i tried to reboot and got a blackscreen, which i removed by renaming the xorg.conf.
And now when i type fglrxinfo: fglrxinfo X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 135 (GLX) Minor opcode of failed request: 19 (XGLXQueryServerString) Serial number of failed request: 12 Current serial number in output stream: 12 Any tips to help me to configure this card, is welcome:) Thanks. Hi Tisa, After installing everything, fglglxgears box worked well, but i had the VMware bug with Gallium renderer string with fglrxinfo.
All the people who had Gallium related issue ended up reinstalling (Fresh Reinstall) and installed AMD Drivers first (including dependencies but excluding update/upgrade/dist-upgrade). I am not sure why this would happen as I got a similar config (Hybrid AMD/Intel) and mine worked no matter what. As for this GLX error, usually it goes away once you’ve reinstalled mesa-utils.
Aptitude reinstall mesa-utils You are on the right track as far I can understand. I’m following the 20 post-install tips, but got snagged on the graphics driver. Hi guardian-venom, This worked on 1.0.6 and will continue to work on any of the newer versions of Kali where you have kernel headers available. I thought it was quite clear from the Kali Forum posts (i.e. Kali dev team removed old kernel headers). The instructions are solid to date and worked every time for the newer versions of Kali.
Also, if you’re using Kali 1.0.7 you won’t be able to upgrade to Kali 1.0.9 cause like I said, Kali dev team removed the packages in-between. I suggest starting with Kali 1.0.9 fresh install. Hope that clears our some confusions.
Cheers, -BMO. Great guide blackMORE. I was hoping you could provide some advice on an issue I am having.
I have the GPU accelerated pyrit functioning on my HDD, however decided to add the LUKS-nuke on a USB 3.0, the installation and the persistence seems to be working fine but am unable to find the grub.cfg file, infact the entire grub folder does not exist. I would imagine this is because the file system differs on a USB from a true installation on a HDD. That being said, is there an analogous file or folder for applying the “radeon.modset=0” change on a USB persistence install. Thanks a million, schmorrison.
(Initially, written on another post, sorry) Hi! Your tuto is very nice and very clear.
I have one little question though: by chance would you know how I can make it work for hybrid graphics (Intel/Ati 6990m)? Seemingly, my ati card is off (DynOff) and I would like to benefit from video acceleration Fglrx installation goes well but when I run fglrxinfo, the results I get are about my integrated card, the Intel one. Moreover, when I want to launch aticonfig –initial -f, I am told that there is no supported adapter. Thank you very much! Been trying this for a little while. Cannot seem to get it to work. Trying to install drivers for hybrid GFX in laptop with a HD6600m Following the tutoral, once i get to the first fglrxinfo I am shown the sandybridge CPU not the AMD gfx If i keep going i eventually get either X Error of failed request: BadRequest (invalid request code or no such operation) or Segment fault.
As responses to fglrxinfo glrxinfo and both gears programs Finally if i ignore that, and do aticonfig -initial then reboot, in 1.0.6 X failed to load with a leaving only simple prompt (not responsive) at which point I revert the xorg.conf, reboot and i get it working again. I also did the same process with similar results on 1.0.9 but X fails just drops me dirrectly to ttyl1 instead of giving the no responsive prompt. I also tried installing the drivers dirrectly from the AMD site.
This resulted in the same thing. Finally i fiddled with blacklists and nothing has worked. I guess i dont have a specific enough question to warrent the post, but if someone sees some glaring issue with what im doing perhaps they could poke me in the correct dirrection, that or maybe others are running into the same issue and need some conformation that the problem is not unique to them. Hello,I have followed your steps and do it exactly.The first time,everything goes well with the installation,but things go weired.The AMD ard give me blurred screen after installation but i do not how to uninstall the driver. There’s few possibilities.
It happens when you’re behind a proxy server that caches or truncates contents. In your case, this is probably not the issue. Your Kali Linux is not fully up to date. Run apt-get update && apt-get upgrade -y && apt-get dist-upgrade -y. Usually this is the most common problem. Also make sure you have the correct official repositories in your sources.list file. Update and upgrade will take time, so be patient.
No, don’t allow anyone to remote into Kali Linux as they will have root access and can destroy your machine. Need some helpso I went through this guide and everything worked. Then about 20mins later or so I went back to check fglrxinfo because it looked different then what you had and was bugging me. This is what came up the second time I checked it: fglrxinfo X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 139 (ATIFGLEXTENSION) Minor opcode of failed request: 66 Serial number of failed request: 13 Current serial number in output stream: 13 This is after I had ran fglglxgears which had worked. Now that gives me the same. Ok, I have been pounding my head against my desk for 2 days now and I am about to give up and reinstall 1.0.9, but I am curious to know what actually went wrong. Yes, this is a harddrive install.
I’m fairly new to Linux, so you might have to be specific. Everything went well and I got the gears running just fine but when I tried to do the aticonfig i got no supported adapters. So i tried a few things and then rebooted to see if that would help. Upon starting up, I got a black screen where no X windows came up. So I’m currently just running in the Ctrl+Alt+F1. I have tried removing/reinstalling Xorg, gdm3, and kdm.
Before rebooting, my system claimed that my graphics was a VESA, I can’t remember the next word but it started with a G and was about 8 letters. I think my issue was in the Xorg.conf but it never was in my X11 directory. I moved a xorg.conf.new from my root directory into the X11 and renamed it xorg.conf.bkp and rebooted but that didn’t work either. Furthermore, now when I run an apt-get update it keeps running through the same amd64 and translation headers every time. Can you please update this guide for Kali Linux 1.0.9 please This guide is not working anymore.
I followed the guide above, the screen goes blank. I hope you are doing very well? I had wanted to know if this will work on an AMD+AMD switchable display VGA’s because I get an error about trying to install incompatilbe driver. And it’s clean dual boot with Windows 8.1 install. Root@Kronfour:# lspci -nn grep VGA 01:05.0 VGA compatible controller 0300: Advanced Micro Devices AMD nee ATI RS880M Mobility Radeon HD 4200 Series 1002:9712 02:00.0 VGA compatible controller 0300: Advanced Micro Devices AMD nee ATI Manhattan Mobility Radeon HD 5400 Series 1002:68e0 root@Kronfour:# lsbrelease -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux Kali Linux 1.0.9 Release: Kali Linux 1.0.9 Codename: n/a Thank you.
Hi blackMORE Ops I got laptop dell inspiron 15 (5537), 8GB RAM, AMD Radeon HD 8670M 2GB DDR3, i7-4500U Processor. I followed step by step on this tutorial (clean system, updated, upgraded, dist-upgraded) alle installed fine, but after that i got OpenGL vendor string: VMware, Inc. Issue (fglrxinfo).
After reboot got error like kernel bug error: kernel BUG at /build/kalibuild-linux3.14.5-1kali2-amd64-igeTGG/linux-3.14.5/drivers/pci/msi.c:939 (its only a small part of that error) and after another reboot – blank screen. After gui back by restore xorg.conf, i tried to reinstall mesa utils (aptitude reinstall mesa-utils) as u suggested below to someone, but nothing changed.And i got different output from fglrxinfo now: fglrxinfo X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 135 (GLX) Minor opcode of failed request: 19 (XGLXQueryServerString) Serial number of failed request: 12 Current serial number in output stream: 12 Can you help me pleasei digged whole internet and i couldnt find solution Thank You. Hello blackMORE Ops, thanks for all your guides, they helped a lot. Unfortunately, after the last upgrade of Kali to 1.1.0 and Kernel 3.18 I had problems with the ATI driver again.
So I tried to remove the driver and reinstall it from the kali repos. They failed at building the DKMS. The same happens if I download and try to install the driver from the AMD web site. It fails with “Error Kernel Module: Failed to build fglrx-14.501.1003 with DKMS”.
Nevertheless it still works if I boot with the 3.14 Kernel. Does anybody has experienced the same problem?
Try this: apt-get update apt-get upgrade apt-get dist-upgrade. Make sure this is done without an error’s ( if any programes like a zaproxy comes with downloading errors. Go to synaptic and delete it. And update and upgrade and dist-upgrade.then: apt-get reinstall firmware-linux-nonfree apt-get install amd-opencl-icd apt-get install linux-headers-$(uname -r). Then: aticonfig –initial -f then STEP 6 then reboot and after reboot you will be able to see changes when you type: fglrxinfo and you are done. This is my way to do it and the most steps i’ve learned from (blackmore) but added some and it worked like a charm.
This is right way to do it on 3.18 root@Secure:# fglrxinfo display::0.0 screen: 0 OpenGL vendor string: Advanced Micro Devices, Inc. OpenGL renderer string: AMD Radeon HD 7500/7600 Series OpenGL version string: 4.4.12874 Compatibility Profile Context.1001 root@Secure:# uname -a Linux Secure 3.18.0-kali3-amd64 #1 SMP Debian 3.18.6-1kali2 (2015-03-02) x8664 GNU/Linux root@Secure:#. Hi blackMORE Ops I got laptop dell inspiron 15 (5537), 8GB RAM, AMD Radeon HD 8670M 2GB DDR3, i7-4500U Processor. I followed step by step on this tutorial (clean system, updated, upgraded, dist-upgraded) alle installed fine, but after that i got OpenGL vendor string: VMware, Inc. Issue (fglrxinfo).
After reboot got error like kernel bug error: kernel BUG at /build/kalibuild-linux3.14.5-1kali2-amd64-igeTGG/linux-3.14.5/drivers/pci/msi.c:939 (its only a small part of that error) and after another reboot – blank screen. After gui back by restore xorg.conf, i tried to reinstall mesa utils (aptitude reinstall mesa-utils) as u suggested below to someone, but nothing changed.And i got different output from fglrxinfo now: fglrxinfo X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 135 (GLX) Minor opcode of failed request: 19 (XGLXQueryServerString) Serial number of failed request: 12 Current serial number in output stream: 12 Can you help me pleasei digged whole internet and i couldnt find solution Thank You Its this same situation on Kali 1.1.0!!!!! I’m wondering if a recent update broke some of the AMD driver functionalities. I previously ran through this entire tutorial with Kali 32-bit v1.0.9 without any issues (Radeon R9 280X) and had great benchmark results. However, yesterday I noticed that Pyrit wouldn’t even work anymore. I decided to re-image my machine with 32-bit v1.1.0a, and now even the AMD ATI drivers seem to be having issues installing.
Here is what I’m getting after reboot and check fglrxinfo: root@kali10:# fglrxinfo X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 139 (ATIFGLEXTENSION) Minor opcode of failed request: 66 Serial number of failed request: 13 Current serial number in output stream: 13 It looks like some other folks are getting some of the same errors, hoping someone smarter than me is able to dig into this and see what’s going on. Nice job bro. The artcle is complete and easy to follow. I am facing three problems right now, 1.
Root@localhost:# apt-get install linux-headers-$(uname -r) Reading package lists Done Building dependency tree Reading state information Done E: Unable to locate package linux-headers-3.14-kali1-amd64 E: Couldn’t find any package by regex ‘linux-headers-3.14-kali1-amd64’ (remaining two were installed flawlessly) 2. Whenever there is this file “xorg.conf” in X11 I cannot start Kali, I have to rename it to “xorg.conf.bkp” 3. ATI catalyst control centre is there in the preferences but when it is opened it shows an error that no drivers are installed Thanks once again. I have a toshiba laptop running kali 1.1.0 as the only OS installed. I have installed FGLRX using ubuntu when ubuntu was installed previously. I know the drivers will work.
For some reason kali thinks my os is a virtual machine. When I run: fglrxinfo I get the following display::0 screen: 0 OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 0x209) OpenGL version string: 1.4 (2.1 Mesa 8.0.5) FGLRX fails to initialize with this error: aticonfig: No supported adapters detected Is their a way to get this working in kali? So far this site is the only one worth anything when trying to get kali to behave rationally.
Any help is appreciated. Could it be a header issue?
The problem is apt-get install fglrx-atieventsd fglrx-driver fglrx-control fglrx-modules-dkms -y Reading package lists Done Building dependency tree Reading state information Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming.