https://youtu.be/pnqH-atn52c

I cant code to save my life but I cobbled together my asus laptop and got the sound working. Due to an extra AMP, I had to patch the SSDT. I found a thread on how to do it on another laptop then found the idenifier for my laptop and patched it in. The laptop had just been released, so I went to the discord and pasted a how to.

The repo owner reached out to me and asked me if I could provide a couple of other identifiers, they were so incredibly friendly! I had never done something like this before and they greatfully created a better patch and submitted it upstream.

It was super awesome to have someone help me and ensure that the work was pushed out so other people could use it. 10/10 would contribute to the Asus on Linux project any day!!

Well if it was for a tech job im sure you could’ve shown off some troubleshooting skills haha

And the ArchWiki link is perfect. Ill read up on that and ensure I’m using it correctly. Thank you very much for the pointer kind stranger! :)

I’ll ask! How do you know? Lol

All jokes aside, I think this might really help me with a side project I’ve been working on. Ive been trying to get full disk encryption working on a NanoPi R6S running NixOS. The issue that im having is that im not sure exactly what modules I need in the initrd. When I boot, there is no output on the display after systemd-boot shows.

The manufacturer puts out a version of Ubuntu thats works flawlessly so I know its possible. But I’ll pass on the snaps and id rather not use uboot. System is working with edk2 and nixos.

Long story short, will this software allow me to figure out what is running in the manufacturer’s kernel and port it over?

Woah woah… is there someplace in the event logs where this would show? Does this mean that you cannot run a windows computer headless?

Not OP but I use headscale and have it configured using Authentik for SSO. Works flawlessly once its up and running. I also use headplane for the UI. It has SSO integration as well which makes everything a breeze.

Edit: Forgot to mention, all running in docker with traefik as the reverse proxy.

Its not as cut and dry as everyone here is making it out to be. This is an organization of people, rules are bent and broken CONSTANTLY.

Each branch has a form of peer-mentoring. In some form or another you’re graded on your ability to do your job and those grades get looked at for your promotion.

It starts off as a negative counseling. Sometimes written, most times just verbal. These are the “oh man I forgot to do this duty at the end of the day” type offenses. More than likely someone is just gonna tell you to pull you’re head out of your ass and fix it.

Get enough of these and eventually you will get whats called a “non-judical punishment”. These are punishments handed out by commanding officers. See “UCMJ Article 15”. These are offenses under the rest of the UCMJ. Some things like adultery are still chargeable offenses. If they cant find something to charge you with “UCMJ Article 134” is a general offense. Basically “hey we didnt like what you did, its not illegal, but were gonna charge you anyway”

Think of NJPs as a misdemeanor, smaller but still serious infraction. When you leave the military, nobody will know that you got charged with something. But these do come with punishments. You basically get “grounded” cant leave your barracks room / get put on restriction. Also loss of pay.

Decide to commit a serous crime defined in the UCMJ? Well thats what a court-martial is. That is equivalent to a felony and will show up on any criminal background check. These often include jail time and reductions in rank.

Its all incredibly suggestive and depends on all the parties involved.

Holy shit I had no idea about this. Thank you so much!

c/unixsocks

Ah, what you’re looking for is called udev. It supplies the system with device events from the linux kernel.

This gist of it is, to use this command

udevadm monitor --environment --udev

then unplug and plug in your monitor. You should see the events on screen. You then write a rule and place it in /etc/udev/rules.d. To run a script add something like

ACTION=="change", SUBSYSTEM=="drm", KERNEL=="card0-HDMI-A-1", \
  RUN+="/usr/local/monitor-script.sh"

See the man udev page for more info (☞ﾟヮﾟ)☞

Have you tried setting up qemu with virt-manager? Theres a lot of info on how to set it up for most distros and I find the GUI is very straightforward and easy to use.

Made me laugh in the middle of a restaurant, thanks 🤣

Thank you for the laugh (⁀ᗢ⁀)

Yeah you just have to deal with mast bumping, as if thats any less worrying.

You can use Authentik to setup an LDAP outpost then use a jellyfin LDAP plug-in to sync everything up.

https://github.com/jellyfin/jellyfin-plugin-ldapauth?tab=readme-ov-file

Course, feel free to DM if you have questions.

This is a common setup. Have a firewall block all traffic. Use docker to punch a hole through the firewall and expose only 443 to the reverse proxy. Now any container can be routed through the reverse proxy as long as the container is on the same docker network.

If you define no network, the containers are put into a default bridge network, use docker inspect to see the container ips.

Here is an example of how to define a custom docker network called “proxy_net” and statically set each container ip.

networks:
  proxy_net:
    driver: bridge
    ipam:
      config:
        - subnet: 172.28.0.0/16

services:
  app1:
    image: nginx:latest
    container_name: app1
    networks:
      proxy_net:
        ipv4_address: 172.28.0.10
    ports:
      - "8080:80"

  whoami:
    image: containous/whoami:latest
    container_name: whoami
    networks:
      proxy_net:
        ipv4_address: 172.28.0.11

Notice how “who am I” is not exposed at all. The nginx container can now serve the whoami container with the proper config, pointing at 172.28.0.11.

Well if your reverse proxy is also inside of a container, you dont need to expose the port at all. As long as the containers are in the same docker network then they can communicate.

If your reverse proxy is not inside a docker container, then yes this method would work to prevent clients from connecting to a docker container.

Something like this. This is a compose.yml that only allows ips from the local host 8080 to connect to the container port 80.

services:
  webapp:
    image: nginx:latest
    container_name: local_nginx
    ports:
      - "127.0.0.1:8080:80"

Excuse me have you heard about our lord and savior, NixOS?