Ubuntu. I just don’t like how they do things. I cant even maintain a repo for the machines i host without putting aside multiple terabytes of space. So to me they cant even make it reasonably easy for me to help them and be self reliant on their ecosystem.
Like SD cards suddenly being read only, then, as mysteriously as it started, they’re read/write again (sometimes while mid-operation)? Yeah. I have that.
Thanks. That helped a lot. It gave me a good basis for some further googling.
It ended up that the Internal Clock of the hardware interface was deselected in alsamixer. Enabling it fixed the no audio issue.
For the channel remapping I tried a bunch of different config files until finally one actually managed to not be ignored. It’s absurd how many separate configuration files and sound settings menus exist for linux audio and there’s no guarantee the one your editing is even being used. An absolute mess IMO and it’s no wonder people shy away from linux for desktop purposes.
Funny enough, despite getting the channel remapping to work, it’s completely ignored unless you put pulseaudio -k into your user profile. And even now, because the remapped output device doesn’t show up on boot, it has to be manually set to the default output every login.
At least I have the right channels mapped though.
I love linux but god damn is it a hot mess for the simple stuff.
Glad you were able to figure it out. Yeah, there are a lot of settings and different moving parts involved in doing audio. And the config files are all over the place. It can get nasty.
There has to be a way to make your settings and that pipeline the (system) default. Or at least change the profile that gets loaded for your specific soundcard and change and override the channel mapping so it won’t load something else first.
Ubuntu. I initially downloaded it for my sibling’s pc but now that I’ve downloaded and configured all these things on their computer, I don’t want to reinstall a new OS and reconfigure and download everything again.
Keep in mind that asahi cut out X11 support and went straight for wayland. It can support xwayland, just know that some things may or may not play nicely if the software doesn’t support wayland. As Wayland is the future of compositors, most popular Linux software should support it eventually.
Linux on arm is good, however as it is not nearly as popular in the desktop space as x86, common binaries for certain applications may not exist on arm if it closed source. You may or may not need those, you can make that judgement call.
Battery life is better than I expected but still not nearly as good as Macos. At least until they can come up with a proper solution for low power usage. Which currently a logistical problem of making something Linux kernel upstream compatible instead of applying a functional dirty solution now.
Linux on M1 is noticeably snappier than anything else I have ever used. It has a great future ahead of it. If your workloads don’t rely on heavy gpu usage and all your software can be found or compiled there. It is a pleasant experience. If you have any other questions, feel free to ask. I think some of the other users talked about the common things well enough.
Also yes, dual booting is currently the only supported option. They still need macos for firmware upgrades.
fwiw I’ve been on Wayland for a few years now and the amount of times I’ve had to think “oh, I’m on Wayland” are in the single digits. not to pretend it you don’t run into things you have to solve or alternatives you have to find, you definitely do, but I’ve been very happy especially over the last year or so.
I do not use asahi though so I can’t comment on that specifically.
I am new to Wayland, but on asahi it is mandatory. So I am having to get used to it. Which is more noticeable as I had to change from i3 to sway. They are functionally identical but different in how you configure it with the wayland compositor.
yes, I’m using sway as well. i was lucky that my old i3 config mostly worked without modification, although it took a while to find good replacements for many of the little apps I’d come to rely on. I settled on bemenu, waybar, and then a dozen little glue apps like clipboard managers eventually fell into place. the archlinux wiki pages on sway and wayland are a great resource.
I don’t currently use it as a daily driver, but I tried. The basic, core experience is fine. Depending on what you need, it could be great. In the end I went back to using macOS (though I did ask myself what was working so well for me with GNOME that I wanted to try the experiment to begin with, and that has resulted in a leaner, simpler macOS setup).
The stoppers for me were webcam support (it kind of worked, but with bad image quality issues), and a number of Flatpaks quietly failing at launch. Non-stoppers but papercuts included that you can find ARM packages for some things but they’re direct downloads instead of dnf sources you can set up (e.g. 1Password, Sublime Text), and there are a few weird glitches with some fonts that work fine on x86 setups.
It’s trivial to set up dual-boot, and pretty easy to back out if it doesn’t work for you, provided you read a few paragraphs of documentation. I’ve done it twice on two different machines.
Over the years I have tried most mainstream distros. I have never seen a reason to use anything other than Debian. Never had it break due to upgrading, I have never tried Nix, Alpine, Gentoo, or Slackware, not many other others I haven’t tried since I started using Linux in 2000.
its easy for you because you been playing around with Linux, I tried to install SSH on zorin os. But after installing SSH , it needs to be restarted, when tried to do that , it won’t saying the ash server did not start, A simple thing like this is have me stumped in Linux where as in windows it was just installing putty and done.
I mean for most Linux derivatives, getting SSH setup for outgoing connections is usually install the openssh package from your distros repos, though I imagine many preinstall it, no reboot should be necessary, and you just type ssh user@hostname into a terminal to connect to the remote ssh server to access stuff on that computer. There shouldn’t be a need to reboot for installing app that’s not a service.
Wanting to enable ssh access to the computer you are using so a remote client can connect to it? Well the same openssh package should have come with sshd which acts as the server to allow remote ssh client to connect. It’d probably need enabling (so it’s run automatically on boot) and starting (so you don’t have to reboot to have it going), on distributions using systemd that’s usually just systemctl enable sshd.service (which makes sure the sshd daemon will be started on next boot) followed by systemctl start sshd.service to start it immediately so it’s running straight away, (or systemctl enable sshd.service --now to roll both steps into one).
linux
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.