Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content Count

  • Joined

  • Last visited


This user doesn't have any awards

About GCandy77

  • Title

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thx Sauron, il give that link a good read. I honestly didn't know what I was doing regarding the kernel, but lesson learned! The reason I want to run Manjaro & Pop side by side is because im relatively new to the linux world and would like to run a few different distros before I settle down with 1 in the end + its quite a fun learning experience after using MS products for the last 25 years. Nayr438, again thx for your time and suggestions! Im going in ... wish me luck
  2. Started from scratch as you can see above, Ive installed/updated all the usual, mesa + vulkan drivers, updated proton ( just in case ), but have not installed/updated WINE or DXVK/D9VK Im asking now ... what do I need to do?
  3. Hi all and thx for the responses Sauron - 1 - I installed Manjaro, not Arch Linux - Yep, whoops thats embarrassing, I presumed Manjaro ran off the same programs like Pop does with ubuntu n just went for it without checking ? 2 - Thx for the links about the AUR, Kernels and how to configure the Gcard, they will come in useful when I re-install manjaro. 3 - Is it not possible to install 2 different versions of Linux on separate drives and have them use their own kernel? I just assumed you could and all the files would be kept separate as they were on complete separate SSD`s? Sorry about the info dump, but as your probably already aware I have been trying to fix this 1 single issue for approx 4-5 months now. I cant let it go as I keep getting told " Vulkan will run on my card " so I keep trying. Ive started from scratch 10 times now, followed a lot of guides that seem to get me 85% towards my goal, but it always ends up in it bricking the Os or that bl**dy black screen ?. I have however in the last 24hrs figure how to set "nomodeset" in the grub b4 boot ? .. So hopefully i wont need to re-install the Os again. Ive also figured out what "nano" is and how to use it a little too. Since all the mess above Im now planning to have both PopOs & Manjaro on the same SSD. Is this a wise move & can it be done? I followed a guide in preparation that advised to create 2 swap partitions each for its own Os and have basicly spilt the rest of the drive in half, With PopOs currently installed & Manjaro to come in the next few days. Jdfthetech - 1 - Thx for the info about mkinitcpio, interesting but Im still a little confused as mentioned above how the kernels can interact when they are installed to separate drives? I the past I duel booted WinborgXP and Win7 for a while and they both ran as separate Os as I thought they would, I understand Linux is written differently, but there were on completely separate drives? ? Win10 worked fine btw, it was left untouched thank god. 2 - AMDGPU does not work for me ?Im stuck using Radeon, which is great until I use a game that uses Vulkan or DXVK or try to use Lutris. I have tried following so many guides and they get me nowhere. Ive read that my card R9 290 (Sea Islands/Hawaii) and that it falls into the experimental GCN 2.0 ) and that the standard AMDGPU drivers will not work with my card and that I need to use AMDGPU-pro. On the AMD website it advises that It only has drivers for 18.04 and that they will not work with 19.10, hence the reason I tried Manjaro, just to see if a different kernel would all me to use AMDGPU ? .. The journey was interesting at least ? Dont know if ure interested but just in case here are some outputs that other people asked for in other troubleshooting topics - r@pop-os:~$ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.3.0-7629-generic root=UUID=9e0d84f8-270a-4988-b97a-25f024d79e07 ro quiet splash vt.handoff=7 r@pop-os:~$ dpkg -L libgl1-mesa-glx:amd64 dpkg-query: package 'libgl1-mesa-glx' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. r@pop-os:~$ ls -l /usr/lib/x86_64-linux-gnu/libGL.so* lrwxrwxrwx 1 root root 14 Feb 24 09:14 /usr/lib/x86_64-linux-gnu/libGL.so.1 -> libGL.so.1.7.0 -rw-r--r-- 1 root root 547152 Feb 24 09:14 /usr/lib/x86_64-linux-gnu/libGL.so.1.7.0 r@pop-os:~$ dpkg-divert --list | grep -i gl ((( This did nothing ))) r@pop-os:~$ glxinfo | grep OpenGL OpenGL vendor string: X.Org OpenGL renderer string: AMD HAWAII (DRM 2.50.0, 5.3.0-7629-generic, LLVM 9.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.2.8 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.2.8 OpenGL shading language version string: 4.50 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.2.8 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: r@pop-os:~$ vulkaninfo ========== VULKANINFO ========== Vulkan Instance Version: 1.1.114 /build/vulkan-tools-IZAxVX/vulkan-tools- failed with VK_ERROR_INITIALIZATION_FAILED In the past most of the guides I have followed all ask me to edit the grub to this - GRUB_CMDLINE_LINUX_DEFAULT=“quiet splash modprobe.blacklist=radeon si_support=1 radeon.si_support=0 amdgpu.cik_support=1 radeon.cik_support=0” GRUB_CMDLINE_LINUX=“modprobe.blacklist=radeon” or GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1" I then sudo update-grub, re-boot and then slam my face through my table when it black screens ? Which leads me back around to the thinking that the incorrect driver is installed within the Kernel for my particular card, Ive read that people with the 390 also get the same issue+ 70% of those users ive read thru have just given up with no end solution found I have discovered that I can either do this via the "nano" program or by using the " xhost +si:localuser:root; sudo gedit /etc/default/grub " command in terminal. They both seem to do the same thing, what is the difference, Is one better to use than the other? Nayr438 - When I re-install Manjaro, I will certainly give this a go thx for being patient! Also sorry for not doing discord thing but I dont own a mic and type like a old turtle, so itll probably do ure head in I did come across this post that seems to have fixed the issue, but am unsure going ahead with it as it also requires me to edit the " /usr/share/X11/20-amdgpu.conf "file and im not to sure if this is a good move, it is a new one for me to try tho? https://community.khronos.org/t/i-can-not-get-vulkan-to-work-with-mesa-drivers/7393/7 Naturally if anyone else coming across this post wishes to try and help fix one 5 month old problem, let me know what I need to do ?
  4. This topic is kinda related - It was suggested that I could try using Manjaro and decided to give it a go and downloaded the KDE plasma version. I installed it on a totally separate drive to PopOs, next to a WIn10 partition. Once installed, I then followed the instructions on the Arch site to get the AMD drivers installed, update mesa and try to get Vulkan running. I installed all these files from the arch site and then the Linux core via the instructions. When It asked me to "Specify the correct module order" I remembered Nayr438's comments and ran the " sudo nano /etc/modprobe.d/amdgpu.conf " commands and inserted data & saved and then the " sudo nano /etc/mkinitcpio.conf ". In here there were no modules set, so I added amdgpu & Radeon, saved and exited. When I ran " sudo mkinitcpio -p linux54 " The process started but advised there were errors to do with the amdgpu & radeon modules. I guess I did something wrong ? I rebooted and and prayed Vulkan might run, loaded steam and of course it wouldnt So, I headed into the package manager ( think its called that ) and proceeded to install everything that I thought might have something to do with vulkan and amd drivers ... Yes I cried when I saw the amdgpu experimental install ? I thought it would be best just to stick with the normal amd drivers for the mo and installed all of these - I rebooted and it was still the same I looked on some other sites for pointers but just became a bit lost again to be honest and then went into random install anything mad man mode before I really cocked it up ? I did manage to take these SS tho, so hopefully they are helpful - I did however manage to update the manjaro grub so that I had the boot choice option pop up instead of it just loading into Win10 straight away( they share the same drive ), so not a complete waste of time After all that .... I calmed down and rebooted, Vulkan was still the same, but I finally found out how to check what driver was loading and could see that it was the Radeon one So I headed back into the package manager and decided to install the amdgpu-experimental package ... when this ran all these windows came up ( im screenshotting everything by now btw ) and then I got these error messages .. I Kinda determined that this ment it didn't work, but thought I better give it a reboot just in case. Thats when I received that Horrible black screen of nothing when I rebooted back into Manjaro .... It just would not load I still had PopOs & Win10 tho and proceeded to try and boot Pop ... This ended in a grey screen, I wouldn't let me log in or get into the Alt+F2 or F3 thing either. Most My files were on Pop so, I tried to do a refresh install and whereas it brought up the login screen this time, it would not let me log in and ended up in a cycle of accept and reset login screen every time I entered my psw ? I had to do a fresh re-install for the 10th time in the end ? (I got my copy of home directory 1st tho using the live usb - phew) I also did try using the recovery drives for both Os`s, but apart from fixing the Grub and packages, im a bit lost as what to look for when editing the grub ... I see the word splash, but have no idea what to type or remove or even how to save it afterwards still learning. Win10 btw somehow survived all this and still works ... the irony ugh. If you've made it this far well done you must either really like solving issues or fixing Linux. I have a few questions moving forwards .. 1 - How did Installing a graphic driver on one system bork both Os's into not being able to boot? I made sure they both had their own swap partitions and they were on separate drives too? 2 - Two different Os's have both given me the black screen of doom upon boot, PopOs Gnome & Manjaro KDE. Am I doing the correct things to ensure im giving it the best chance to work? As far as im aware the only things I need to update as the mesa drivers and setup dxvk/d9vk, install the amdgpu drivers and set a few grub/kernel commands and it should work. Am I missing anything else I need to install? 3 - Can someone link a video of really basic guide on how to edit the grub thing during boot or via a live usb properly .... I really should be learning how to do this so that I dont have to keep on re-installing my Os, but the guides Ive found tend to over confuse the explanation and I get lost again Thx for reading again if u made it this far & soz for the mass of pictures, im dyslexic and pics inform a lot better imo
  5. Hi mate,, thx for the reply ... I will give that a go ? I'm actually writing this from a fresh install of PopOs atm as I managed to brick my system and had to start all over again ? (see new post) sigh.
  6. Hi Nayr438, sorry but im still having issues. I ran the "sudo nano /etc/initramfs/initramfs.conf" command and it advise that it the directory did not exist when nano popped up, but upon further research I found the directory was slighty different and I ran this command instead "sudo nano /etc/initramfs-tools/initramfs.conf" That did pop up the window that I believe we were looking for, but I cannot find any reference to AMDGPU or Radeon anywhere so the mystery continues ? Here is the full info of what was in that window - GNU nano 4.3 /etc/initramfs-tools/initramfs.conf # # initramfs.conf # Configuration file for mkinitramfs(8). See initramfs.conf(5). # # Note that configuration options from this file can be overridden # by config files in the /etc/initramfs-tools/conf.d directory. # # MODULES: [ most | netboot | dep | list ] # # most - Add most filesystem and all harddrive drivers. # # dep - Try and guess which modules to load. # # netboot - Add the base modules, network modules, but skip block devices. # # list - Only include modules from the 'additional modules' list # MODULES=most # # BUSYBOX: [ y | n | auto ] # # Use busybox shell and utilities. If set to n, klibc utilities will be used. # If set to auto (or unset), busybox will be used if installed and klibc will # be used otherwise. # BUSYBOX=auto # # COMPCACHE_SIZE: [ "x K" | "x M" | "x G" | "x %" ] # # Amount of RAM to use for RAM-based compressed swap space. # # An empty value - compcache isn't used, or added to the initramfs at all. # An integer and K (e.g. 65536 K) - use a number of kilobytes. # An integer and M (e.g. 256 M) - use a number of megabytes. # An integer and G (e.g. 1 G) - use a number of gigabytes. # An integer and % (e.g. 50 %) - use a percentage of the amount of RAM. # # You can optionally install the compcache package to configure this setting # via debconf and have userspace scripts to load and unload compcache. # COMPCACHE_SIZE="" # # COMPRESS: [ gzip | bzip2 | lz4 | lzma | lzop | xz ] # COMPRESS=lz4 # # NFS Section of the config. # # # DEVICE: ... # # Specify a specific network interface, like eth0 # Overridden by optional ip= or BOOTIF= bootarg # DEVICE= # # NFSROOT: [ auto | HOST:MOUNT ] # NFSROOT=auto # # RUNSIZE: ... # # The size of the /run tmpfs mount point, like 256M or 10% # Overridden by optional initramfs.runsize= bootarg # RUNSIZE=10% # # RESUME: [ none | auto | UUID=<uuid> | /dev/<name> ] # RESUME=none ^G Get Help ^O Write Out ^W Where Is ^K Cut Text ^J Justify ^C Cur Pos ^X Exit ^R Read File ^\ Replace ^U Paste Text ^T To Spell ^_ Go To Line ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- I did read in that window the line " Note that configuration options from this file can be overridden by config files in the /etc/initramfs-tools/conf.d directory " So I tried the command " sudo nano /etc/initramfs-tools/conf.d " and that brought up this result .. ( dont know if it helpful tho, but at least im trying ? ) Also thought Id add these just in case it helps Getting there ...... hopefully ?
  7. Hi again, soz hit a issue - I can follow the "sudo nano /etc/modprobe.d/amdgpu.conf" which brings us nano 4.3, I enter the lines, ctrl+x, then Y then Enter When I do the "sudo nano /etc/mkinitcpio.conf" command, nano 4.3 comes back up but is completely blank, If I do the 1st process again, I can see the 2 amdgpu cik & si lines in Nano 4.3 as I entered them in the 1st time. Sorry but im lost again ? I do have screen recorder installed, and can u a vid to u tube if it helps
  8. Hi Nayr438, Thx for laying out for me and explaining the reasons not to go back a kernel. Il give that a go and let u know how it went thx again
  9. I stand corrected, Thx for pointing that out. This topic seems to highlight the exact problems that I am having ( 2nd post onwards ) & as someone pointed out in a post " IHMO in 2019 a card without Vulkan support is almost like a card with no 3d hardware acceleration: pretty useless " https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/open-source-amd-linux/1085095-amdgpu-vs-radeon-kernel-driver-performance-on-linux-5-0-for-amd-gcn-1-0-1-1-gpus The more im reading, the more it suggests that I can run this amdgpu-pro driver with a older kernel. If I installed PopOs version 18.04 ( which I believe is the LTS ver ) would that install an older kernel or is that just a waste of time ? https://web.archive.org/web/20180730184353/https://system76.com/pop So what u think, try and fix this or just give up ?
  10. Sorry for the late reply on this, but I got naffed off with trying to get something to work that works auto on windows & just installed Win10 reluctantly ?. At least I can play some games that I have bought on steam that require a Core 2 Duo and 512mb Gcard. I have a I5 2500 and a 4gb 290 installed ? Electronics Wizardy - Your correct most games do run fine using the radeon driver, however a lot of modern titles require dxvk/d9vk and Vulcan to run, Supraland for example and will not run unless you are using the amdgpu or pro driver. CactusMan - Ive read that its the other way round and that amdgpu are the old drivers and the Radeon are the new drivers ? The amdgpu drivers are important as they still support a version of OpenGl that the Radeon does not ( I think it OpenGl.1.2 - not sure on the rev number tho) Im currently using the AMD® Hawaii Radeon drivers that were auto selected by the kernel, but as said they dont work with dxvk/d9vk or vulcan/proton properly ( for my specific card as its in the GCN2 experimental category ( thx amd really helpful ? )) If I install the catalyst drivers I get a black screen on boot. I am reluctant to try the command you have suggested as I really could do without resetting my OS again due to errors I dont understand, can you explain what the command does and how it may help? Im not unwilling , just reluctant due to fear. Nayr438 - The default mesa stack doesn't allow me to use dxvk/d9vk, vulcan/proton ( I get confused with so many different names all describing scripts (i think) for a GPU driver). I was also trying to get Lutris to work with dxvk/d9vk, but It just wont have it, everytime I selected it & hit save, I would go back into the options n find it switch back too off. Ive followed about 7 guides on how to set this up and the furthest ive got is getting the Uplay installer to load and log me in - trying to play games is a whole other issue. Again, the same with Cactusman .. Im willing to try the things you have suggested but am unwilling atm due to .. A - I dont know how to actually create the file /etc/modprobe.d/amdgpu.conf .... do I literally go into that directory via "files" and create a file called that? or is it a bit more technical? Im still a noob in Linux ? I have done something similar in the past when I was setting up another gpu - https://support.feralinteractive.com/docs/en/warhammer2tw/latest/linux/faqs/#i_amd_200_300_radeon_kernel_blacklist (I did option 5 ) But this does not work with my card even if i set the "amdgpu si_support=1" within it. B - Can you explain what the command " edit /etc/mkinitcpio.conf " does just so I have a clearer underrstanding before I take the plunge. ?Ive read that its something to do with a bash script to do with RAMDISK, but I think a lay-mans explination is needed for that one ? Sir0Tek - Youve hit the nail on the head - I want vulkan support, Ive tried the amdgpu driver and that has always resulted in a black screen upon boot, leading to 5 months of reading only to find out my card isnt supported properly and is experimental, and as the original links suggest, the only driver I can use is the amdgpu pro one that doesnt seem to support the most recent Kernel. What a mess ? Too top the whole weird expeince off ... when I first switched to Linux, I ran a 270x, which I belive used the "Pitcairn" Radeon drivers. I also tried and failed many a time to install the AMDGPU driver and get it to run - it was just black screen city again. Around the same time I bought a R9 280 for my nephew and he needed the AMDGPU driver so that he could run Warhammer game within Linux. I decided to run it in my system so I could learn the setup before I installed into his PC. I found the above warhammer link that explained how to do this and went thru the actions. It all went smoothly and when I rebooted the machine and checked the settings it clearly showed that it was running the AMDGPU driver. Brillaint I thought and proceded to re-install my own 270x. When I restarted, I looked at the settings again, just to make sure everything was good after the swap . To my shock, my 270x that had refused to accept any other driver I had tried to install was now running fine using AMDGPU drier? ? WTF I had a great 2 weeks of gaming ? until my new and current card turned up - the R9 290. When I installed It reverted back to the AMD® Hawaii drivers ? and to put it lightly I felt like sticking my head in front of a train. WTFF!!! ?? Ironically Ive had more luck with just using WINE via steam than vulkan/proton over the mass Os re-setups ive done. Im slowly coming to the realaztion that im just gonna have to bear that 1-2 mins reboot when I wanna game & then again when Ive finished. ? I really like linux over Win10, but probably because its open source I cant expect everything just to work, shame .. but I tried ? P.s sorry for the bad spelling, im dyslexic and either this forum or my browser doesnt have a spell checker installed ( I need the red lines )
  11. TLDR - Using PopOs for approx 5 months & have had to do either a re-install or a re-fresh (when I eventually figured that out) approx 10 times due to trying to use the AMDGPU driver & not the Radeon one - Then getting Blackscreen on boot, Still in the learning phase & havent figured out how to edit the grub thing yet? Anyway .. Ive now found the solution ??? - There are no AMD drivers (R9 290) that work with my card for my current "kernel" version or "OS" version (this is where im getting confused) 5 months it took to figure that out ? This website gives me the "how to" https://www.amd.com/en/support/kb/faq/amdgpu-installation#faq-Prerequisites But the the Package Archive is only for Ubuntu 18.04 https://www.amd.com/en/support/graphics/amd-radeon-r9-series/amd-radeon-r9-200-series/amd-radeon-r9-290 which used the Kernel 4.15 ( as far a I can tell ) Im currently running PopOS 19.10 & as far as I can tell I have the 5.3.0 Kernel running. Do I need to install an older Os, older Kernel or both? Ive read that I can downgrade the Kernel but haven't really found any useful guides on how to do this or if its even possible? + I'd really like to avoid having to install an older Os just to get this driver installed but Is there any harm in it? I dont really know how il be losing out from what 19.10/5.3.0 offers as Im a bit of a noob with that info .. is its security related or just better drivers/features etc? Any suggestions?
  12. I`ll stick my thoughts in as a lifetime user of MS until the end of W7 who just recently jumped & has stayed on PopOS. The advice above imo is ure best best if your not to sure about jumping to Linux or what distro to go for. You can actually run the Os's Live from a thumbdrive & It will give you a very good taste of how the Os runs as long as you dont attempt any hardcore gaming or install large programs (you'll need the whole system working for that). The best analogy imo for Linux is that it runs very much like Android as in you can customize a hell of a lot and not just cosmetically either, because there are so many different types of distros out there for Linux, in some circumstances you can also install programs or apps that are not ment for that OS/environment. Its a very flexible system. Ive only used 3 versions of Linux - Knoppix, Mint & PopOS. Knoppix is like "WTF" for us Linux noobs so I wouldn't recommend going there. I didn't get on well with Mint, not because I had any major problems with it .. I just didn't like the "cinnamon" desktop that it used. It wasn't bad and worked as it should have, but because it looked very similar to the Win7 desktop & I had problems locating programs I wanted to use & I didn't really try to "switch" my brain into learning Linux environment which only hindered me later. Im now on PopOS & am Loving it - granted I dont have everything working how I would like but that seems to be a AMD issue rather than anything Linux, but Im happy with a 98% working system that Imo pis**ss over Win 10 totally & looks down upon the MS users of today. It uses the Gnome desktop environment, which allowed my brain to shift into figuring out a new system & at 1st minor things were a bit of a pain, but there is a great Linux/ubuntu community out there always willing to help :) (they must be nuts to constantly put up with out noob problems). PopOs also installs very easily & has a easy setup that takes approx 10/15 mins - Once ure in the Os, just head over to the Gnome-extentions website and things start to become a little clearer when u start to install apps like dash-to-dock. If youre Gaming on Linux the main things you need to check are - Is your gpu compatible with the Proton/Vulkan Api's as if it is not you will not be able to use DXVK properly Or Lutris & will only be able to run games native via steam or by using a program(I hate to call it that) called WINE. If ure just using the OS for everyday kinda stuff, Linux should be a breeze for you if you install any well supported Distro - If you want to use for gaming I suggest PopOs or Manjaro ( disclaimer - I haven't used Manjaro but my friends advise its all good)
  13. Hi mate thx for the reply but ive got the issue resolved now ( I hope ) Re-installing the wifi drivers left me with the same issue & did not work but this did > sudo apt install --reinstall network-manager Thought I post just in case it helps anyone else