[-] vortexal@lemmy.ml 3 points 1 day ago* (last edited 1 day ago)

Yes but the problem for me was more complicated. Mesa is installed by default in Linux Mint and Vulkan should have worked out of the box but for some reason it defaulted to the wrong Kernel driver for the GPU. I didn't know this before posting and, as I stated in other replies, every search result on every search engine told me the wrong information.

[-] vortexal@lemmy.ml 1 points 2 days ago

I don't know if I need to do that because Vulkan seems to be working now but is that correct? My sources.list file is empty and it states the wrong version of Linux mint. Should I actually edit "/etc/apt/sources.list.d/official-package-repositories.list", seeing that that has the actual list of repositories?

[-] vortexal@lemmy.ml 3 points 2 days ago

Yeah it seems like it's working now.

[-] vortexal@lemmy.ml 2 points 2 days ago

Ok, it seems to have worked as the game I was using for testing seems to be working fine.

Although, I keep getting the error message (WARNING: radv is not a conformant Vulkan implementation, testing use only.), is that to be expected?

[-] vortexal@lemmy.ml 1 points 2 days ago

Ok, do I need to restart my computer now?

[-] vortexal@lemmy.ml 1 points 2 days ago

For some reason, I can't get Lemmy's "code" fuction to work properly in this reply but both commands give the same information:

`j@j-HP-Notebook:~$ vulkaninfo --summary WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Failed to CreateInstance in ICD 2. Skipping ICD. ERROR: [../src/amd/vulkan/radv_physical_device.c:1877] Code 0 : Device '/dev/dri/renderD128' is not using the AMDGPU kernel driver: Invalid argument (VK_ERROR_INCOMPATIBLE_DRIVER)

VULKANINFO

Vulkan Instance Version: 1.3.204

Instance Extensions: count = 20

VK_EXT_acquire_drm_display : extension revision 1 VK_EXT_acquire_xlib_display : extension revision 1 VK_EXT_debug_report : extension revision 10 VK_EXT_debug_utils : extension revision 2 VK_EXT_direct_mode_display : extension revision 1 VK_EXT_display_surface_counter : extension revision 1 VK_EXT_swapchain_colorspace : extension revision 4 VK_KHR_device_group_creation : extension revision 1 VK_KHR_display : extension revision 23 VK_KHR_external_fence_capabilities : extension revision 1 VK_KHR_external_memory_capabilities : extension revision 1 VK_KHR_external_semaphore_capabilities : extension revision 1 VK_KHR_get_display_properties2 : extension revision 1 VK_KHR_get_physical_device_properties2 : extension revision 2 VK_KHR_get_surface_capabilities2 : extension revision 1 VK_KHR_surface : extension revision 25 VK_KHR_surface_protected_capabilities : extension revision 1 VK_KHR_wayland_surface : extension revision 6 VK_KHR_xcb_surface : extension revision 6 VK_KHR_xlib_surface : extension revision 6

Instance Layers: count = 7

VK_LAYER_INTEL_nullhw INTEL NULL HW 1.1.73 version 1 VK_LAYER_MESA_device_select Linux device selection layer 1.3.211 version 1 VK_LAYER_MESA_overlay Mesa Overlay layer 1.3.211 version 1 VK_LAYER_VALVE_steam_fossilize_32 Steam Pipeline Caching Layer 1.3.207 version 1 VK_LAYER_VALVE_steam_fossilize_64 Steam Pipeline Caching Layer 1.3.207 version 1 VK_LAYER_VALVE_steam_overlay_32 Steam Overlay Layer 1.3.207 version 1 VK_LAYER_VALVE_steam_overlay_64 Steam Overlay Layer 1.3.207 version 1

Devices:

GPU0: apiVersion = 4206847 (1.3.255) driverVersion = 1 (0x0001) vendorID = 0x10005 deviceID = 0x0000 deviceType = PHYSICAL_DEVICE_TYPE_CPU deviceName = llvmpipe (LLVM 15.0.7, 256 bits) driverID = DRIVER_ID_MESA_LLVMPIPE driverName = llvmpipe driverInfo = Mesa 23.2.1-1ubuntu3.1~22.04.2 (LLVM 15.0.7) conformanceVersion = 1.3.1.1 deviceUUID = 6d657361-3233-2e32-2e31-2d3175627500 driverUUID = 6c6c766d-7069-7065-5555-494400000000 `

[-] vortexal@lemmy.ml 1 points 2 days ago

Did I do it correctly? GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.cik_support=0 amdgpu.cik_support=1" After saving, is there anything else I have to do it get it to work?

[-] vortexal@lemmy.ml 1 points 2 days ago

This is what I get when I try to run that set of commands: `j@j-HP-Notebook:~$ sudo apt install mesa-vulkan-drivers mesa-vulkan-drivers:i386 libvulkan1 libvulkan1:i386 vulkan-tools vkd3d-demos mesa-opencl-icd clinfo libxrandr2 libxrandr2:i386 libvulkan-dev libvulkan-dev:i386 libgl1-mesa-dri libgl1-mesa-dri:i386 vkmark glmark2-x11 firmware-amd-graphics radeontop xserver-xorg-video-amdgpu [sudo] password for j:
Reading package lists... Done Building dependency tree... Done Reading state information... Done Package firmware-amd-graphics is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source

E: Unable to locate package vkmark E: Unable to locate package glmark2-x11 E: Package 'firmware-amd-graphics' has no installation candidate `

[-] vortexal@lemmy.ml 2 points 2 days ago

My computer has an AMD Radeon R2 Graphics. It seems like both the radeon and the amdgpu modules are installed but the kernel driver in use is radeon. I'd show the output of "vulkaninfo" but it doesn't seem to show the full thing, is there a way I can get it to show the full output?

[-] vortexal@lemmy.ml 1 points 2 days ago

The GPU is an AMD Radeon R2 Graphics. It was a bit hard for me to find and I have no idea if it's accurate but it should support at least Vulkan 1.2.170.

[-] vortexal@lemmy.ml 1 points 2 days ago

Ok, what is my solution then? Right now, the only thing I know is that when ever I try to run anything in Linux that requires Vulkan, it defaults to Lavapipe instead of using my GPU and if I try to disable Lavapipe, it acts like Vulkan isn't installed.

[-] vortexal@lemmy.ml 1 points 2 days ago

I would but I'm actually using Linux Mint because the Xfce edition has low ram usage. My computer's ram is very slow and it's only 4GB.

27
submitted 2 days ago* (last edited 2 days ago) by vortexal@lemmy.ml to c/linux@lemmy.ml

Edit: I think I've figured it out, it seems like Linux Mint defaulted to the wrong Kernel driver and I was able to switch it to the correct one.

I've already tried searching for this online but there is a reason I'm posting about it here. The last time I tried to install Vulkan drivers in Linux Mint, there was an update to the oibaf PPA that completely broke my Linux Mint installation and I had to manually reinstall it. I've read that, at least in the past, the oibaf PPA causes problems in Ubuntu but I can't find another solution to installing Vulkan drivers in Linux Mint. Is that the only way to install the Vulkan Drivers in Linux Mint, or is there another way?

Also, yes, Vulkan works in Windows and it did work in my previous installation of Linux.

48
submitted 2 months ago* (last edited 2 months ago) by vortexal@lemmy.ml to c/linux@lemmy.ml

Edit: Last night, I used the "Fix MergeList problems" option in the maintenance tab of software sources and at least for now, it seems to be working. So I probably wont need help with this anymore, hopefully.

Every hour or two, the Update Manager keeps giving me an error message saying that my APT configuration is corrupt and that I should switch to another Linux Mint mirror. It usually goes away when I do a manual refresh but it just keeps coming back. I have also tried switching to a different mirror but I get the same error. It also tells me to run apt-get update but even if I add "sudo" it just gives me an error message saying to run apt-get update.

It happened again so I'm adding screenshots in case they help. The first is the initial error, then it's the error I get when I try to change the repository and the third is the error I get when I try running the command it suggested:

48
submitted 3 months ago* (last edited 3 months ago) by vortexal@lemmy.ml to c/linux@lemmy.ml

I recently found out about a Linux Distro named Q4OS and I wanted to test out their claim that it only requires 256 MB of ram when using the trinity desktop environment. However, when I used the live cd in virt-manager with 256 MB or ram, it just kernel panicked at boot. So I then tried it with 512 MB of ram. In addition to some issues that are not present when you are using at least 1 GB of ram, such as "sudo apt update" causing the entire VM to become unresponsive, I noticed that it seemed to actually use anywhere between 290 MB to 370 MB of ram when the only thing running was the process viewer (which is htop).

Obviously, this is still very low for a modern Linux distro but I was wondering how accurate VMs are for testing ram usage.

And, yes I know that it would be pretty much useless on a PC that only had 256 MB of ram even if it did work. I'm actually checking the ram usage because there is a possibility that I may be using a very old computer of mine that only has 1 GB of ram at some point in the future. So I'm just testing it and eventually other distros out to to see which one I'm going to end up using (assuming I do actually end up even using that computer).

Edit: I just tried the 32-bit version in virt-manager and htop stated it was only using 232 MB of ram, which means that their claim was right and that I might have been using the wrong version.

Edit 2: I just tried installing the 64-bit version in virt-manager and htop stated that it was using about 350 MB of ram, so I don't know if installing it actually made a difference.

34
submitted 5 months ago* (last edited 5 months ago) by vortexal@lemmy.ml to c/linux@lemmy.ml

Edit: I'm no longer looking for help with this. The issue seems to be with the app itself and I have submitted a bug report for the app on github.

Before you tell me I should try another n64 emulator, I have been using other emulators but I have a game that isn't working and I'm trying to run it in other emulators.

Anyways, if I try to run simple64 through the terminal, I get the error message:

Failed to load module "xapp-gtk3-module"

I tried to look into this and it seems that I'm supposed to install "xapp" but I'm getting the error message:

The following packages have unmet dependencies: xapp : Depends: libxapp1 (= 2.2.8-1) but 2.8.2+virginia is to be installed E: Unable to correct problems, you have held broken packages.

I tried to fix it with sudo apt --fix-broken install xapp but it's just giving me the same error message. Is there anything else I can try before I try another emulator?

23
submitted 7 months ago* (last edited 7 months ago) by vortexal@lemmy.ml to c/linux@lemmy.ml

I need to reinstall Linux Mint but MOK Management is preventing me from booting into the live CD. I tried looking for a solution online but (assuming I did everything correctly) I couldn't find anything that actually worked for me. How do I properly disable it?

Also, I forgot to mention that I do have access to Linux Mint, I just have to run it in recovery mode because it wont boot normally.

Update: I was able to bypass MOK using my password, I still wasn't able to disable it but I was at least able to boot into my Live CD for Linux Mint and I'm in the process of reinstalling it. I would prefure if I could just disable MOK but I at least know how to work around it.

Update 2: I have fully reinstalled and updated Linux Mint but for some reason everything looks different despite the fact that I'm using the same settings and software I was before everything broke. But whatever, outside of the fact that I no longer have the dual boot menu and instead I get a string of text saying "booting in insecure mode" for some reason, it seems to be working fine.

51
submitted 7 months ago by vortexal@lemmy.ml to c/linux@lemmy.ml

I got an external hard drive enclosure for the purpose of recovering some of the files from my old laptops hard drive. The hard drive and all of it's partitions show up in both disks and gparted but it wont mount. When I tried to mount it manually, it gave the error message stating that it can't read the superblock. I've never had to deal with this issue before, so the only things I've tried so far were fsck and the data recovery option in GParted, and neither of them helped.

I tried searching about it online but all of the solutions I found online either didn't work or required methods that are currently not possible for me. The hard drive had Ubuntu (22.04 if I remember correctly) installed on it and I just need access to the files in the sdd3 partition, which was formatted in ext4.

30
submitted 9 months ago by vortexal@lemmy.ml to c/asklemmy@lemmy.ml

I started using Spotube a few days ago and it seems interesting but I'm having a specific issue with it. I'm trying to listen to "Darkish" by A-One but despite the fact that there are multiple videos on YouTube, Spotube can't find a source and if I try manually searching for a source, all of the videos, including videos it uses as a source for other songs, are grayed out. There are three versions on Spotify (the original from Vol.7, a release from montage yellow and a remix in the "nonstop" 2012~2013 compilation) and all three of them have the same issue.

I have tried switching the api type from YouTube to Piped but the issue still persists. I mostly use the Linux version but the issue also exists for the android version. Is there anything I should try before contacting the developers?

55
submitted 9 months ago by vortexal@lemmy.ml to c/linux@lemmy.ml

I tried looking into this myself but I couldn't really find much about this error. The only solutions I could find didn't work for me. The first one was to use mokutil but at the point where I was supposed to run sudo mokutil --import MOK.der it gives me the error message "Failed to get file status, MOK.der" even though I did everything it told me to do. The other one was to disable secure boot and then run sudo '/sbin/vboxconfig' but even though it looked like it worked, I'm still getting the error message. I have re-enabled secure boot, so you don't have to worry about that.

Is there something else I can try or does VirtualBox not work in Linux Mint for some reason?

3
submitted 1 year ago by vortexal@lemmy.ml to c/opensource@lemmy.ml

I tried everything from an old tablet running android 4.1.2 to a newer phone running android 10, and it crashes on all of them. The game runs fine on all of them, getting frame rates higher than the display frame rate, but then it just randomly crashes without an error message. So, I was wondering if this was just an issue with the game or if it was somehow an issue with the devices I was using.

I know the game hasn't been updated in a few years and the creator hasn't been active on GitHub in several months, so I know it's not likely that the game will get an update but I still wanted to ask about this issue anyways.

1
submitted 1 year ago by vortexal@lemmy.ml to c/asklemmy@lemmy.ml

There are some games that aren't working on my phone and I wanted to try playing them in Waydroid on my computer running Ubuntu, however, there is a problem. Some of them are games that I've paid for but Google is refusing to allow me access to the Google play store from within Waydroid. So the only way (as far as I can tell) would be to use a third party client, like Aurora Store, to download them but I don't want to risk it if I can get banned.

view more: next ›

vortexal

joined 3 years ago