total used free shared buff/cache available

Mem: 3354 350 3032 1 171 3004

Swap: 8191 0 8191 on another reboot the memory dropped back down?

Thank you so much it just worked now!!

I added the use flags,

compiled wpa_supplicant again with --newuse,

restarted NM and wpa,

and still the same issue :(

did a killall wpa_supplicant and now my ssid shows up and i can connect to it :)

its the 3rd day for me, so as I said i don’t want to recompile anything right now

I have 2 cores with 2 threads, compiling anything again is not an option for me, atleast right now: My router only has system logs unfortunately it doesnt show any logging for connection attempts

it works fine with literally, anyother wifi accesspoint, do you have any tips on waht I should do for the relevant logs to show up? I dont have journalctl but would dmesg work fine?

1. DWA-131: RTL8192EU
2. it also works on my pop-os system
3. no it was using WPA/WPA2, I changed it to use WPA2 only

sunk cost fallacy is a thing and i am falling for it

before I gave up and installed NM i tried it the manual way, (including trouble shooting steps), then i spent some time compiling wireless-tools package and tried with them, same issue, then spent hours compiling NM for some hope(I disabled the relevant background services before trying NM) only for the ssid to not even show up

I am willing to begin from scratch, any proper resources you can point me to? l

that looks like something opposite to what i want Vulkan -> OpenGl, instead of something like OpenGl -> Vulkan

there are gnome extensions but they were installed over a year ago and have been disabled for more than 6 months

grep: /var/log/syslog*: No such file or directory

I am getting this error but yes there were some JS errors that I attribute to extensions like

JS ERROR: TypeError: this.actor is null
                                          _syncEnabled@resource:///org/gnome/shell/ui/windowManager.js:144:25
                                          onStopped@resource:///org/gnome/shell/ui/windowManager.js:161:35
                                          _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:65:22
                                          _easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:247:60
                                          _destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1611:21
                                          onStopped@resource:///org/gnome/shell/ui/windowManager.js:1579:39
                                          _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:65:22
                                          _easeActor/<@resource:///org/gnome/shell/ui/environment.js:160:64
                                          @resource:///org/gnome/shell/ui/init.js:21:20

What about dmesg? if it’s a hardware problem (and it looks like, but I may wrong) dmesg will print some usefull data

I tried sysrq then, now i know why it didn’t work sysrq: This sysrq operation is disabled.

nothing useful in dmesg, at least to me

No i dont have another system that I can ssh with right now, There are some OOM messages before the timestamps in my first paste, I have edited the post to include more journalctl entries, yes I have a swapfile.

The code did have a fi at the end, i am using fedora.

Thank you, removing the module and adding it again fixed the issue, for future reference is there an easier more seamless way to go about it?

Is edid/sony.bin your new EDID?

Yes

your new EDID? Does it revert back if you remove drm.edid_firmware all together?

how do i do that?

Here is the EDID file I decoded using edid-deode

No before i passed the custom EDID it showed up as “Unknown display” and letter-boxed the entire display, limiting my resolution to 640x480 and 1366x768

Are they worth it(Last long)?

Is the command key useful on Linux DE?