sic_semper_tyrannis

I'm new to self hosting and just got CasaOS setup following up to part two of Tech DB's guide. The SMB works on my Linux computer, I can create documents, etc. However I'm having trouble accessing it on my Android phone. I'm using Material Files, Search for SMB shares, and find "CASAOS" but it's under a different IP address as the server. Then when I click on it, it prefills some of the lines such as "Hostname: CASAOS" and "Port: 445". I have added my login info as either my CasaOS login and SSH login but both don't work and I've changed the port to 80 as that's CasaOS default but every combination I try fails with "java8... UnknownHostConnection... and more" Any ideas?

I setup a Dell Inspiron 2-in-1 for my Dad with Fedora 40 Kinoite. He wants a basic stylus but I don't know anything about them. All the info I can find on the product page is saying that you can use an "active pen." What am I looking for in a stylus to let me know if it'll work? The Dell and Wacom stylus' say they're for Windows. Do these stylus' need software to work and thus be stuck only working on Windows? Do they actually work on a firmware level? If you know of any that work I'm down for suggestions too.

Hey everyone, I wanted to give my feedback with Linux on a new CoPilot laptop.

I just got a new generation Dell Inspiron 14 2-in-1 Touch laptop (Model: i7445-7326BLU-PUS, SKU: 6576720). It has the new AMD 8840HS and is a new Windows CoPilot branded laptop (with key unfortunately).

I tried booting and logging into Windows once for the heck of it and here's what happened. It wouldn't let me log in without joining an internet network first. So I successfully give it my guest network credentials. It said connected and secured. Then I hit next, next, etc. and it restarts and then would update, still prior to me being able to login. However it restarts and says oops the internet had an issue and please reconnect WiFi. It sends me back to the WiFi credential page to login again but it auto connects as my credentials were correct. So I hit next and it gives me the same problem again.

I then say screw it and proceed to install Linux.

I proceed to install Fedora Kinoite 40 via USB and have absolutely zero issues. It works flawlessly with every feature including the fingerprint scanner and when flipping the laptop keyboard over into tablet mode it even auto disables the keyboard and touchpad but leaves the touchscreen working! The only thing that doesn't seem to work is the CoPilot key. When pressed it doesn't do anything. I tried assigning it as a shortcut key for Konsole where it registers as "Meta" and gets created as "Shift+Meta" but it doesn't actually work still. I didn't change a single thing in BIOS, Secure Boot is still enabled, and I don't see any code displayed during boot or shutdown. Besides the CoPilot key being useless I couldn't be happier with how it all turned out and proved to be better than Windows yet again.

Edit: I played around some more with the CoPilot key. Like I said the shortcuts default to "Shift+Meta" if only pressing the CoPilot (Meta) key. That won't launch anything. However if you add another key into the mix it will work. I created "Shift+K+Meta" to launch Kcalc and it worked, kinda. I may have to either press the combo multiple times or press and hold it for a few milliseconds longer than a normal key press and then it launches the program, but not once, it opens Kcalc multiple times all at once and the amount of times it opens seems random.

Where would I look for a list of what network chips are supported in any given kernel? I'm looking to build my first computer designed from the ground up for Linux and want to be sure that the Ethernet port and WiFi chip will work without needing to do anything special.

I tried using Waydroid on Linux Mint (Edge) only to have it not work and realized that it requires Wayland, and Mint uses X11. So I used VirtualBox to install Fedora 40 Gnome which does use Wayland.

I installed Waydroid as per the instructions and am having seemingly the same issue as on Mint. After downloading "Vanilla" Android and clicking "Done" everything exits out. So I launch the Waydroid application but nothing ever happens.

I then try to manually start Waydroid in terminal but always get "ERROR: WayDroid container service is already running". Then I skip to the second step "waydroid session start" but receive "OSError: container failed to start".

Am I doing something wrong? Is it simply because the VM is causing the issues? Or does WayDroid not work well on Fedora? Thanks