Sunday, March 1, 2026

GA-970A-DS3P FX wake on lan not working on Lubuntu

Looks like WOL is Enabled by default, if Erp Disabled, and MB is made solely for Windows, where WOL is enabled in driver. Enabled Power On By Mouse, Power On By Keyboard just in case... No lights on LAN port but 2.5W power draw... If CPU Turbo mode is enabled, 3.5W power draw...

https://www.gigabyte.com/Motherboard/GA-970A-DS3P-FX-rev-21

Windows 8 Features > Other OS

CSM Support > Never

Boot Mode Selection > UEFI and Legacy

LAN PXE Boot Option ROM > Disabled

Storage Boot Option Control > Disabled

Network stack > Disabled

IOMMU Controller > Enabled


ON REMOTE/TARGER/HOST/SERVER PC:

sudo nano /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

GRUB_CMDLINE_LINUX_DEFAULT=""

sudo update-grub


sudo apt install openssh-server -y

sudo systemctl enable --now ssh


ip link

sudo ethtool enp3s0 | grep Wake

        Supports Wake-on: pumbg

        Wake-on: d

sudo ethtool -s enp3s0 wol g

sudo ethtool enp3s0 | grep Wake

        Supports Wake-on: pumbg

        Wake-on: g

sudo poweroff

BUT IF REBOOT > Wake-on: d > sudo poweroff > Wake-on: d


nmcli connection show

sudo nmcli connection modify "Wired connection 1" 802-3-ethernet.wake-on-lan magic

sudo nmcli connection down "Wired connection 1" && sudo nmcli connection up "Wired connection 1"


Alternatives:

Option A — NetworkManager

Create a dispatcher script:

sudo nano /etc/NetworkManager/dispatcher.d/99-wol

Put:

#!/bin/sh

ethtool -s eth0 wol g

Make executable:

sudo chmod +x /etc/NetworkManager/dispatcher.d/99-wol

Reboot and check:

ethtool eth0 | grep Wake


Option B — systemd service

sudo nano /etc/systemd/system/wol.service

[Unit]

Description=Enable Wake-on-LAN

[Service]

Type=oneshot

ExecStart=/usr/sbin/ethtool -s eth0 wol g

[Install]

WantedBy=multi-user.target

sudo systemctl enable wol.service


ON CLIENT PC:

sudo apt install wakeonlan

wakeonlan [MAC_ADDRESS]

Sunday, February 22, 2026

KVM install and configuration on Kubuntu

sudo apt install qemu-kvm libvirt-daemon-system libvirt-clients bridge-utils virt-manager


groups                    List groups for the current user.

groups <username>   List groups for a specific user.

id <username>    Display UID, GID, and all group memberships.

cat /etc/group            Show all local groups and their members by reading a file.

getent group            List all groups from all configured databases.


sudo adduser $USER libvirt


Virtual Machine Manager > File > New Virtual Machine > Local Install Media (ISO image or CD-ROM)


If failed to create image, create image.qcow2 in storage location and then choose it for OS install.


sudo nano /etc/libvirt/qemu.conf

# Some examples of valid values are:

#

#       user = "qemu"   # A user named "qemu"

#       user = "+0"     # Super user (uid=0)

#       user = "100"    # A user named "100" or a user with uid=100

#

#user = "libvirt-qemu"


# The group for QEMU processes run by the system instance. It can be

# specified in a similar way to user.

#group = "kvm"


user = "your_username"

group = "your_username"


user = "your_username"

group = "libvirt"


sudo systemctl restart libvirtd


Network selection > Bridge device... > virbr0


ifconfig


On KDE couldn't turn off full screen with shortcuts... but right mouse button > tick full screen > untick full screen... Changing window size and position with shortcuts started working.


dpkg-query -W -f='${Installed-Size} \t ${Package}\n' virtualbox*

qemu-img convert -f vdi -O qcow2 /path/to/your/vm.vdi /path/to/new/vm.qcow2

sudo apt purge "virtualbox*"

sudo apt autoremove


Rescue mode without graphics:

sudo grub-install /dev/vda

sudo update-grub

Thursday, February 19, 2026

No truth - just approximation

What we’ve been circling around is **not new at all**. Different pieces of this worldview appeared **independently** across cultures, usually when thinkers hit the same wall you’re hitting now: “certainty collapses, dogma looks violent, truth looks provisional.”

Here’s a rough historical map of *when humans first articulated these ideas*.

Wednesday, February 18, 2026

Worst Human Dogmas

### 1. **“My group is chosen / superior / righteous”**

The nuclear reactor of evil.

* Justifies genocide, slavery, crusades, purges, and ethnic cleansing.

* Turns neighbors into “less than human.”

* Works with religion, race, nation, class, or ideology.

  **Body count: maximal.**

Tuesday, February 17, 2026

Android Studio sound problems on Kubuntu

Mucis palyers glitch when Android Studio emulator is running.

pw-top

pactl list short clients

cd ~/.android/avd

nano Medium_Phone_API_30.ini


avd.ini.encoding=UTF-8

path=/home/user/.android/avd/Medium_Phone_API_30.avd

path.rel=avd/Medium_Phone_API_30.avd

target=android-30

hw.audioInput = no

hw.audioOutput = no

audio.backend=none

Turning audio off NOT WORKING!!!


Before starting Android Studio:

export QEMU_AUDIO_DRV=none

Turning audio off NOT WORKING!!!


~/.android/avd$ emulator -avd Medium_Phone_API_30 -no-audio

Command 'emulator' not found, but can be installed with:

sudo apt install google-android-emulator-installer


emulator -avd Medium_Phone_API_30 -no-audio

PANIC: Cannot find AVD system path. Please define ANDROID_SDK_ROOT


Add to ~/.bashrc:

export ANDROID_HOME=$HOME/Android/Sdk

export ANDROID_SDK_ROOT=$ANDROID_HOME


Reload: source ~/.bashrc


emulator -avd Medium_Phone_API_30 -no-audio -verbose

Turning audio off WORKS!!!

pw-top

Monday, February 16, 2026

MobSF VM cannot be used for Dynamic Analysis

[INFO] 05/Feb/2026 09:25:06 - Performing System check

[INFO] 05/Feb/2026 09:25:06 - Android API Level identified as 30

[ERROR] 05/Feb/2026 09:25:06 - VM's /system is not writable. This VM cannot be used for Dynamic Analysis.

[ERROR] 05/Feb/2026 09:25:06 - Please start the AVD as per MobSF documentation!

[ERROR] 05/Feb/2026 09:25:06 - Cannot Connect to emulator-5554

[ERROR] 05/Feb/2026 09:25:06 - Internal Server Error: /android_dynamic/a312049526219c769f2fe0d599fc4bc8

[ERROR] 05/Feb/2026 09:25:06 - Internal Server Error: /android_dynamic/a312049526219c769f2fe0d599fc4bc8

adb root

adbd cannot run as root in production builds

Android Studio > Tools > Device Manager > Create Virtual Device > Medium Phone > API 29 > Services > Android Open Source


[INFO] 05/Feb/2026 10:56:33 - Testing Environment is Ready!

adb shell

su


https://stackoverflow.com/questions/43923996/adb-root-is-not-working-on-emulator-cannot-run-as-root-in-production-builds/45668555#45668555

https://xdaforums.com/t/question-how-to-get-writable-system-on-emulator-with-google-apps-android-13-arm-image.4567963/

You should use the open source version of Partition and run AVD with the following code:

emulator -avd <NameAVD> -writable-system

sudo apt install google-android-emulator-installer

Add to ~/.bashrc:

export ANDROID_HOME=$HOME/Android/Sdk

export ANDROID_SDK_ROOT=$ANDROID_HOME

Reload:

source ~/.bashrc

emulator -avd Medium_Phone_API_29 -writable-system -verbose

emulator -avd Medium_Phone_API_29 -writable-system -no-audio -verbose

Sunday, February 15, 2026

git patch automatic code replacement in repository

git show commitID -- folder/ >> 001commitID.patch

cd to fresh git repo without changes and

git apply 001commitID.patch

git format-patch -10 --author="YOURNAME" // look 10 commits and creat separate patch files

git apply ../0001-your.patch

git log -p // full commit history with code changes (the patch/diff output) for each commit