vortexal

joined 4 years ago
[–] vortexal@lemmy.ml 4 points 1 week ago* (last edited 1 week ago) (1 children)

I looked through my bash history and it looks like I needed it to build an Xbox eeprom editor for Xemu. Xemu doesn't (or at least didn't, I haven't used newer versions yet) have a built in eeprom editor and editing the Xbox eeprom is required for enabling both wide screen and higher resolutions for the games that support them natively.

I just looked at Xemu's documentation, and it looks like they've added a link to an online eeprom editor, so the editor I used (which they do still link to) is no longer required.

[–] vortexal@lemmy.ml 4 points 1 week ago (4 children)

I've only used aliases twice so far. The first was to replace yt-dlp with a newer version because the version that comes pre-installed in Linux Mint is too outdated to download videos from YouTube. The second was because I needed something called "Nuget". I don't remember exactly what Nuget is but I think it was a dependency for some application I tried several months ago.

alias yt-dlp='/home/j/yt-dlp/yt-dlp'
alias nuget="mono /usr/local/bin/nuget.exe"
[–] vortexal@lemmy.ml 10 points 1 month ago

This is the reason box86/64 exists.

[–] vortexal@lemmy.ml 9 points 2 months ago (1 children)

Back in the days of MS-DOS, there was something called "PC-Booters". They were created because of the fact that there was a lot of different operating systems that were actively used. So their solution was to just create a basic OS that contained the bare minimum required to run the game.

[–] vortexal@lemmy.ml 1 points 2 months ago

I am, wireplumber is part of pipewire.

[–] vortexal@lemmy.ml 2 points 2 months ago

While I have already found a working solution, I think the issue wasn't that it was selecting the wrong device. it was almost as if my normal audio devices didn't exist for some reason because nothing could see them, even my input devices were missing.

[–] vortexal@lemmy.ml 2 points 2 months ago (1 children)

Ok, even though I said I'd wait until tomorrow, I decided to try it again. It seemed to boot more or less normally but I did try someone else's suggestion and it got audio working again. I did undo the edit I made to the modprobe blacklist and I did keep fluidsynth and pulseaudio uninstalled but I tried using the wireplumber ppa, like someone else suggested and my audio is working again. Granded, I have no idea what actually fixed the issue, so I don't know who to fully credit but thanks for helping.

[–] vortexal@lemmy.ml 1 points 2 months ago (3 children)

Ok, so a lot of them are old messages, none of the messages from this session are labeled as busy. I did just try logging out and back in and that was pretty much instantaneous, so whatever it was that caused my computer to boot slowly just effect the boot itself. But yeah, I tried restarting pipewire and everything related to it and it's still just showing the dummy output device and audio isn't working. Thanks for trying though.

[–] vortexal@lemmy.ml 3 points 2 months ago

Ok well, pipewire is what's pre-installed and as of now neither pipewire nor pulseaudio are working. I have already uninstalled pulseaudio, as I would like to just use what's preinstalled if I can get it working again.

[–] vortexal@lemmy.ml 1 points 2 months ago

Ok and that command doesn't list anything.

[–] vortexal@lemmy.ml 1 points 2 months ago (5 children)

For some reason the the "stop" command didn't work as it thought pulseaudio wasn't running but I was able terminate it through htop. Also, that didn't work, it did restart pipewire but my normal audio devices are still missing and I still don't have working audio. I did, just in case, also check the journalctl and fuser commands you gave me previously, and fuser still just lists pipewire and journalctl stil gives the same error messages as before.

[–] vortexal@lemmy.ml 1 points 2 months ago (7 children)

I just saw you edit and I did just remove pulseaudio.

 

Final update (hopefully): It seems that I have been able to fix the issue. I'm not sure what exactly caused the problem but either removing fluidsynth or installing the wireplumber ppa fixed the issue and I have working audio again. I've also removed pulseaudio and undid my edit to the modprobe blacklist, as they were only done as a temporary solution and they are no longer necessary.

For the past three days, I've been having this issue where my computer starts with no audio and the only sound device listed is a "dummy output" device. I've tried looking online for solution but the only solution I found has to be redone manually every time I start/restart my computer. It also seems like this issue is common with and possibly specific to the sound card my computer has, which is an "Intel Sunrise Point-LP HD Audio".

The solution that worked for me was to add blacklist snd_soc_avs to the modprobe blacklist and then run the two commands sudo alsa force-reload and pulseaudio. Adding snd_soc_avs to the blacklist permanently brought back my actually audio devices but it didn't fix the audio nor did it remove the dummy output device. The two commands I listed do restore the audio and remove the dummy output device but they only work for the current session and I have to run them again after starting/restarting my computer.

I have no problem doing this if there isn't a permanent solution but I would like a permanent solution, if possible.

 

I'm using the Cinnamon edition of Linux Mint 22 (Wilma) and I've installed all of the dependencies listed on the build documention but when I try running meson setup builddir in the android_translation_layer folder, it gives me this error:

ERROR: C shared or static library 'art' not found

Assuming that the "art" that it needs is "art_standalone", I've already installed that and it seemed to install just fine but for some reason meson still can't find it. Assuming that it can work in Linux Mint, what should I try next?

 

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.

 

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:

 

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.

 

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?

 

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.

 

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.

 

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?

view more: next ›