jdfthetech

This article appears to explain how to flash this chip for a 2 channel relay of similar build:

https://www.hagensieker.com/wordpress/2019/02/21/hacking-unknown-2-channel-relay-with-tasmota/

In this article, he discusses the 4 channel version and how it relates to the 2 channel.
 

Would it be good to have a sticky with most commonly answered questions?
What things would you recommend we include?
 
some ideas I had:
 
How to burn an ISO to a disk in different operating systems How to add a user How to modify a group How to change permissions How to do a symlink (and what they are for) How to change file permissions What is a distro / package manager and how do they work together? What is efi and how does it work? How do I set nomodeset (seems to pop up quite a bit) Common keyboard commands (looking at you CTRL+SHIFT+C / Vand ALT+F2 / ALT+F7) difference between yum, deb and pacman

Right now, I'm just looking for a list of common problems, and then thinking we could as a group write up different answers and perhaps this will help folks faster than them having to ask the same questions and waiting hours / days to get an answer to a simple question.  
One concern I can see off the bat is this could get monolithic, but I think if we could organize it properly we could perhaps keep it tidy and easily searchable.
Maybe put certain items above the fold?
 
Thoughts, concerns?

Yes. It could also explain why it couldn't mount the live filesystem on the other distros. It would of become corrupt during decompression for mount.
 
As far as security, I generally don't worry to much. I don't keep anything sensitive on my system, it would need root to damage anything and I can verify and repair my arch install fairly quick if it did. Nearly all my online accounts require 2 factor auth. Heck you can wipe all installed packages minus base and reinstall without ever leaving the desktop in arch.

General Protection Fault. Something went wrong when it was accessing the systems memory. You could potentially have a bad ram stick.
I would start with running a memtest on the system. If it passes we can look into other possibilities.
 
 

The first error only says you drive doesn't have a write cache. It can be ignored.
If you remove quite splash from Grub it will help show where it actually hangs.
You can reference this Fedora guide more info on how to do that. -> https://docs.fedoraproject.org/en-US/Fedora/22/html/Multiboot_Guide/GRUB-runtime.html
 
 
mount: /run/miso/sfs/livefs ...  /dev/loop0 indicates it can't mount the live file-system.
This is usually the result of a bad ISO image or a bad Install Media.
I would start with re-creating your Installation Media with etcher or Rufus in DD Mode for GPT.
etcher -> https://www.balena.io/etcher/
or from your other Manjaro Install -> yay -Sy chaotic-aur/balena-etcher

just use vscode, it's becoming a standard since it works on OSX, Linux, Windows and is now being incorporated into github.  Don't niche yourself, learn the standards

there really isn't too much to it, to be honest.  Not sure if there is a book on the topic because the history is pretty simple.

I get what you are saying. Maybe this will help: the problem is the technical aspects are not lost, they are just from an old email list from the mid 90s.  Before there was a versioning system, Linus was just using an email list and compiling all the submissions manually.  This means your best bet is to read through a lot of those technical docs as those compiled all that information.  It's literally a window into the conversations the devs make every day.

Hopefully this will help.

Now, you can find the public information on kernel dev conversations here:
 
https://lkml.org/
 
There is another archive here (which can be rather fun to read):

https://lore.kernel.org/lkml/
 
There is also the main page:

https://www.kernel.org/
 
 

That is awesome! that is the type of stuff i was looking for, A good look into the actual development process and how linux as we know it came to be. thank you.

I think I understand what you are trying to do, so let me first phrase what it is I think you are trying to do and you can correct me there:
 
You wrote a custom library of functions you want to import into your own main .py file.
This would be similar to how someone would module.exports in node with the addition of a require on the main file.

If this indeed what you are trying to do, I have good news for you.
This is incredibly simple in python.
 
Simply create the file in the same directory, (not 100% necessary but saying to do so for simplicity sake), name it a NONRESERVED name (ie. don't name it os, import, pandas etc) I'll use chicken.py as an example.

After this, simply use the same statement you would use for any other wheel (or python module depending on nomenclature):
 
import chicken

There are some caveats to this, and some dos and donts so you'll want to read up on the process more, but hopefully that gets you started.
If I was incorrect in my base assumption, feel free to correct me and I'll try and help further.

try ntfs-3g

 
sudo apt-get install ntfs-3g https://wiki.archlinux.org/index.php/NTFS-3G

to be clear:  the reason many people recommend against dual booting has to do with Windows 10 overwriting the boot parameters and leaving your Linux system inoperable after Win 10 does updates.  This has happened fairly often since Win 10 was introduced.  It is not related to any sort of thinking on the part of more experienced users thinking it will confuse new users.  It's relatively straightforward to rebuild this but it's a PIA for new users who may not want the hassle.

It was good info you laid out, just wanted to make this clear for anyone who was curious.

I was working on a huge data restore which left me with 500 GB of data in around 5000 directories.  I wrote this little python script to rip all the files into a single directory so I could export to a drive and find files more easily.
Not 100% sure on the win version, so YMMV.
 
anyways, here it is:
 
https://github.com/jdfthetech/recursiveCopy/
 
 
(yes I posted this over on L1 forums too in case anyone cares)

there are so many things that could have gone wrong here it's hard to give any advice.  Plug it into your pc, check the bios, see if it shows up.  Check the cables, etc.

You need to troubleshoot why the device is not showing up as it's obvious the drive is not physically broken.

It appears this is an issue with Tomb Raider ignoring the default sound output.
 
This bug is something I encountered a long time ago when playing it.  It would default to a weird sound output and I had to change it in the volume config tool in kde. 

As you have seen, if you change it to the correct output it begins to work.
Pretty sure this is because of pulseaudio constantly changing the defaults.

Base on the color theme, it look like Manjaro KDE. 

https://wiki.gentoo.org/wiki/GRUB2
https://wiki.archlinux.org/index.php/GRUB

If you want really good info on VFIO passthrough, the Level 1 techs forums has a ton of info.
 
It's probably one of the better resources out there.

https://forum.level1techs.com/c/software/vfio

Wendell did a great write up on how to get it working with Pop using one vid card in this thread:

https://forum.level1techs.com/t/vfio-in-2019-pop-os-how-to-general-guide-though-draft/142287

You can use QEMU KVM to achieve this, you can use libvirt along with virt-manager to set it up.
However depending on what your doing with it, you still have to allocate resources away from linux to the Virtual instance.
So if you need say 4cores 8 threads for Linux and Windows, you need a 8core 16thread. Same with Memory. If you want full GPU acceleration, you need a second GPU.
The overhead on the cpu side is very low and the GPU side is almost non-existant, but your still splitting up system resources to achieve it.
 

Folks, some people will like Linux and will enjoy being able to tinker with it and learn.
Others will not.

If someone posts a rant about how bad Linux is, it's probably best to not argue.
Just let them state publicly their failure in comprehension and ignore it.

Arguing about this does nothing for the community and simply manages to push more relevant threads to the bottom.
 

As a person who uses Linux on all but one of my machines, I would say I don't really care.

All I care about is that the hardware is compatible.
That's it.

I don't care if a reviewer figures that out, and don't feel it's really fair to suggest this is something reviewers should do as it's only a 2% user base.

Now, if the reviewer dedicates a channel to it like some folks, they might just get my patreon cash.
I vote with my wallet.

That's my only statement on the subject.

As a person who uses Linux on all but one of my machines, I would say I don't really care.

All I care about is that the hardware is compatible.
That's it.

I don't care if a reviewer figures that out, and don't feel it's really fair to suggest this is something reviewers should do as it's only a 2% user base.

Now, if the reviewer dedicates a channel to it like some folks, they might just get my patreon cash.
I vote with my wallet.

That's my only statement on the subject.

As a person who uses Linux on all but one of my machines, I would say I don't really care.

All I care about is that the hardware is compatible.
That's it.

I don't care if a reviewer figures that out, and don't feel it's really fair to suggest this is something reviewers should do as it's only a 2% user base.

Now, if the reviewer dedicates a channel to it like some folks, they might just get my patreon cash.
I vote with my wallet.

That's my only statement on the subject.

Yeah, it's time for a hardware refresh to a newer rig (i5 or i7, newer ASUS board like a Z390 and DDR4 memory, but things are a wee bit tight at the moment. Trying to milk a few more months out of this rig.

thank you for the recommendation! i'll look into it.