But whenever I wanted to try out something new or install anything, some random stuff would go wrong and would need hours of searching and fixing. Happens much less often with MacOs.
A Linux Evening
71–80 of 330 posts
Re: A Linux Evening
#72Kernel parameters are usually documented in the kernel-parameters.txt file in the source. See https://github.com/torvalds/linux/blob/master/Documentation/... : hpbussize=nn The minimum amount of additional bus numbers reserved for buses below a hotplug bridge. Default is 1. The way to get from the error "No bus number available for hot-added bridge" at https://github.com/torvalds/linux/blob/master/drivers/pci/pr... t…
What's the approach used by OSes that "just work" for things like this? Is this due to the more monolithic kernel of Linux making more things required to be known up front than e.g. in Windows?
Re: A Linux Evening
#73OK.
Re: A Linux Evening
#74> I spent several hours fixing a problem and I learned next to nothing in the process. This is probably true for this specific case here, but my experience with fixing stuff in Linux is actually the opposite. I learnt a lot doing so, and learnt stuff that turned out to be later useful in very unexpected spots. Back when I was a teen and using Windows, I've spent countless hours fiddling in stuff in regedit and other…
I think unless one uses Linux on daily basis it's really difficult to sink in the knowledge. I decided to install an Archlinux VM and see what happens. I'm kinda disappointed to myself as I found out I didn't like too much trouble so I'll probably never be a good/great programmer.
Re: A Linux Evening
#75Re: A Linux Evening
#76Couldn't agree more with the takeaways. Especially #3 - and it is exacerbated if you are a finicky person who wants everything exactly the way you want it + loves to customize and tinker. Linux basically keeps me hooked by virtue of catering to those needs even though I have to deal with these Linux evenings (which are thankfully getting rarer over time). In time too because my tolerance is depleting as I age and hav…
I use iPhone + Mac, but I don’t remember any hiccups when it was android + Mac. Most of my interaction between the devices is pretty indirect anyway (photos are shared through google cloud, etc).
Re: A Linux Evening
#77Couldn't agree more with the takeaways. Especially #3 - and it is exacerbated if you are a finicky person who wants everything exactly the way you want it + loves to customize and tinker. Linux basically keeps me hooked by virtue of catering to those needs even though I have to deal with these Linux evenings (which are thankfully getting rarer over time). In time too because my tolerance is depleting as I age and hav…
> and there aren't any dual sim models of iPhone. Aren't phones with an eSIM + regular SIM effectively dual-SIM? I'm pretty sure iphones have those.
Also, I like the flexibility of using the physical SIM because I can easily use them with both smart and feature phones without issues.
Re: A Linux Evening
#78This is prototypical of the standard Linux experience, but I'd like to remark on just how much less common this sort of thing is. Modern Linux and modern Linux distributions have a much larger "just work" factor and it's getting better every year in my experience. Slowly and asymptotically, but it is improvement. This was driven home recently by my experience switching to NixOS. NixOS is brilliant in many ways, but b…
As a Mac-user would do?
I guess a Windows-User would just rate [1/5] stars and don't even research.
We should keep in mind:
Linux users care a lot and do research. Most other will just say "nope" and leave it a issue for the manufacturer or keep turning it off and on again. What I don't know is if the initial situation is to blame upon Linux, Intel (Thunderbolt), device manufacturer or all of them. We have valuable post a the top explaining PCIe-Pause on MacOS and that Linux tries to apply a similar mitigation?
Apple:
Because Thunderbolt allows the addition and removal of arbitrary numbers of peripherals connected in arbitrary topologies, the task of dividing up the PCI tree’s address space can be challenging. Sometimes, particularly when large numbers of devices are attached, it is possible to exhaust portions of that address space. When this happens, a new device cannot be enabled without moving existing devices.
To solve this problem, OS X v10.9 supports PCIe Pause—a special power management state in which all driver and device operations are temporarily suspended. Whenever address space exhaustion occurs, OS X may ask drivers to pause operations. After the drivers are paused, OS X changes the address space layout of the paused devices to make room for new devices, and then tells the drivers to resume normal operation
Oh. If your driver does not explicitly declare support for pausing, your driver will never receive pause requests. As a result, devices may fail to appear when the user plugs in additional devices, particularly on hardware with multiple Thunderbolt ports. For this reason, you are strongly encouraged to support this functionality as soon as possible.
Ouch. On Linux this shouldn't be an big issue because the kernel provides them.From the mentioned Linux patches:
Currently PCI hotplug works on top of resources which are usually reserved:
by BIOS, bootloader, firmware, or by the kernel (pci=hpmemsize=XM). These resources are gaps in the address space where BARs of new devices may fit, and extra bus number per port, so bridges can be hot-added. This series aim the BARs problem: it shows the kernel how to redistribute them on the run, so the hotplug becomes predictable and cross-platform.
Fits into what Apple describes. The patch for Linux would be helpful. And I've the feeling that the approach Intel has chosen to add TB upon PCIE isn't bulletproof?Re: A Linux Evening
#79I've been trying for a week now to get Windows to properly suspend and stay suspended on a Thinkpad X1. Even after changing the BIOS to "Linux" mode (S3 Sleep), fiddling with drivers and the registry, and issuing powercfg commands it's still flaky. The function keys to change audio settings also work poorly sometimes. These are the kinds of issues we used to have when trying to bring up Linux on a laptop. But now it'…
Re: A Linux Evening
#80> I spent several hours fixing a problem and I learned next to nothing in the process. This is probably true for this specific case here, but my experience with fixing stuff in Linux is actually the opposite. I learnt a lot doing so, and learnt stuff that turned out to be later useful in very unexpected spots. Back when I was a teen and using Windows, I've spent countless hours fiddling in stuff in regedit and other…
Usually my go-to for "Linux problems" is "tear down the VM and start a new one", but a few days ago my Manjaro rig at home lost power, and bluetooth wouldn't work upon restart. I wracked my brain, pored through forum threads, man pages, and LFS, but nothing really helped. It looked like several different problems at once, but none of the individual fixes worked, or only worked for minutes at a time. I stepped away fr…
"Have you tried turning it off and on again?"