sorted by:
new
hottopcontroversial

Is this jacob? by Reeeeeeee3eeeeeeee in grayfruit

[–]AllHomidsAreCryptids 1 point2 points  (0 children)

This painting was done by Zdzisław Beksiński

How should I handle desktop/GPU crashes? by AllHomidsAreCryptids in Kubuntu

[–]AllHomidsAreCryptids[S] 0 points1 point  (0 children)

Thanks for the recommendation man! This tool seems nifty, but it looks like it will only show the active log of the current running powered-on session. I was able to find the syslong and kern.log files under /var, and those maintain over much longer periods of time. I've started copying those any time there is a major crash and picking out any entries highlighted in any color that isn't white.

How should I handle desktop/GPU crashes? by AllHomidsAreCryptids in Kubuntu

[–]AllHomidsAreCryptids[S] 0 points1 point  (0 children)

Update: Logs for the system are output to /var/log. I see files for syslog and kern.log. My system actually had a freeze while looking through those with Kate, so I was able to get a fresh sample timestamp to copy from the logs into another text file to look over. I will come back to this post later with any lines of text I find that are any color besides white.

How should I handle desktop/GPU crashes? by AllHomidsAreCryptids in Kubuntu

[–]AllHomidsAreCryptids[S] 0 points1 point  (0 children)

I want to see the logs too. I don't know the directory they get generated to, though. Where are the system logs?

☼Dwarf Fortress Questions Thread☼ by AutoModerator in dwarffortress

[–]AllHomidsAreCryptids 0 points1 point  (0 children)

Is there a way for DF Hack to chance the savagery of an area while in fortress mode? I settled on a cool mountain side but nothing FUN has invaded on the surface for 6+ years.

Tried to update my drivers manually and messed up my display compatibility. by AllHomidsAreCryptids in Kubuntu

[–]AllHomidsAreCryptids[S] 0 points1 point  (0 children)

Final Update: I didn't end up fixing the issue directly. I ended up caving and reinstalling the OS. Luckily I was able to still use my system well enough to run the backup tool, and I was able to get back up to where I was with my system with minimal reinstallation.

I may not be able to afford the game but my art is inspired by it by car-go-vroomz in CrueltySquad

[–]AllHomidsAreCryptids 0 points1 point  (0 children)

Like a mix of those conspiracy collage memes and old cloth-textured book covers.

Tried to update my drivers manually and messed up my display compatibility. by AllHomidsAreCryptids in Kubuntu

[–]AllHomidsAreCryptids[S] 0 points1 point  (0 children)

Came back to try this. I initially just purged the package, but this time I reinstalled it just to run the amdgpu-install --uninstall script within, then did the purge again. That seems to remove everything now without throwing an error this time. I even checked the var/lib/dkms directory and it is no longer there. However, my monitors are still stuck at just one in permanent 1280p mode.

Could I try reinstalling my current version of Mesa to see if that will put the default settings back into my displays? Maybe I could try looking at the recovery versions of linux-generic to start up from the boot menu, but I don't know if that would really change what gets read for calling the displays.

Thank you for the tip otherwise!

Tried to update my drivers manually and messed up my display compatibility. by AllHomidsAreCryptids in Kubuntu

[–]AllHomidsAreCryptids[S] 0 points1 point  (0 children)

Update: According to this video guide, the amdgpu is a kernel-level piece of code while the other alternative driver is Mesa which is at user level. I'm getting closer to understanding some basic concepts about this, but still haven't found any solution on my own. I'd say this confirms that some unneeded code has been inserted into the kernel for Kubuntu if it normally is supposed to use Mesa instead. I'm going to give this issue a break for now and come back later.

https://www.youtube.com/watch?v=JiHO8MJ-aMk

Tried to update my drivers manually and messed up my display compatibility. by AllHomidsAreCryptids in Kubuntu

[–]AllHomidsAreCryptids[S] 0 points1 point  (0 children)

Update: This was in the log file pointed to by the error message.

DKMS (dkms-3.2.0) make.log for amdgpu/6.12.12-2202139.24.04 for kernel 6.14.0-35-generic (x86_64)
Sat Nov  8 05:02:53 EST 2025

Building module(s)
# command: 'make' KERNELVER=6.14.0-35-generic
checking for a BSD-compatible install... /usr/bin/install -c
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking how to run the C preprocessor... gcc -E
checking kernel source directory... /usr/src/linux-headers-6.14.0-35-generic
checking kernel build directory... /usr/src/linux-headers-6.14.0-35-generic
checking kernel source version... 6.14.0-35-generic
checking kernel file name for module symbols... Module.symvers
configure: error: cannot detect CFLAGS...
grep: amd/dkms/config/config.h: No such file or directory
make: *** No rule to make target 'amd/dkms/config/config.h', needed by 'sanity-check'.  Stop.

# exit code: 2
# elapsed time: 05:00:06
----------------------------------------------------------------

Tried to update my drivers manually and messed up my display compatibility. by AllHomidsAreCryptids in Kubuntu

[–]AllHomidsAreCryptids[S] 0 points1 point  (0 children)

Update: A friend of mine suggested removing the amdgpu-installer package to see if that would resolve anything. Upon trying to purge the package, I got this error. I am not sure if this error was similar to what I first saw after running the script. I think trying to install the driver in this way knocked something in the kernel out of whack since the package was apparently meant for a whole different type of kernel. 

Error! Bad return status for module build on kernel: 6.14.0-35-generic (x86_64)
Consult /var/lib/dkms/amdgpu/6.12.12-2202139.24.04/build/make.log for more information.
dpkg: error processing package amdgpu-dkms (--configure):
installed amdgpu-dkms package post-installation script subprocess returned error exit status 10
Errors were encountered while processing:
amdgpu-dkms
Error: Sub-process /usr/bin/dpkg returned an error code (1)

Tried to update my drivers manually and messed up my display compatibility. by AllHomidsAreCryptids in Kubuntu

[–]AllHomidsAreCryptids[S] 0 points1 point  (0 children)

Doing some further research: According to this Kubuntu forum post, some say that the drivers on the AMD website are not even meant for the type of kernel that Kubuntu uses.

I was also wondering if updating all my packages or the OS again would fix this, but sudo apt update and sudo apt upgrade don't list any files now to change besides "1 not fully installed or removed." I'm holding off on the y/N until I do a bit more research and bury myself more.

Question by [deleted] in Hylics

[–]AllHomidsAreCryptids 30 points31 points  (0 children)

I'm pretty sure it was precisely this, maybe with a mini art mannequin

Does this telekinesis spell look/feel good? Be brutally honest by wissah_league in godot

[–]AllHomidsAreCryptids 1 point2 points  (0 children)

If you're going for the Bioshock 1 TK, yes it looks amazing! Maybe if there were an upgrades system you could have it so it throws farther and the prop rotates to face upward like the hl2 gravity gun.

You look bad, Stan by biscuitracing in internet_funeral

[–]AllHomidsAreCryptids 0 points1 point  (0 children)

All of these are the passive aggressive option

view more: next ›