Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A Linux Evening

fabiensanglard.net

Post reply on HN
Print view View original

51–60 of 330 posts

Re: A Linux Evening

#51

Post by nneonneo »

robin_reala wrote: post #34
vladvasiliu wrote: post #28

Earlier quoted context omitted.

> 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.

There’re also real dual-SIM iPhones, but they’re market restricted (typically to China). Docs for SIM + eSIM: https://support.apple.com/en-gb/guide/iphone/iph9c5776d3c/io... Docs for dual physical SIM: https://support.apple.com/en-us/HT209086

I used to have a dual physical SIM iPhone X from China! However, when I sent it in to get (warranty) a local Apple repair shop screwed up and replaced it with a North American model. After much gnashing of teeth with Apple Support, I wound up with a new iPhone 12…but no dual physical SIM.

Now my phone is still confused after restoring from backup and cannot see the eSIM. I’ve been filing feedbacks and radars to no avail. If I was on Android I’d have just rooted it and deleted the offending (mis)configuration file already!

Re: A Linux Evening

#53

Post by quijoteuniv »

mentos wrote: post #45
_justinfunk wrote: post #44

I used to hear "Linux is only free if you don't value your time." - this article seems to validate that this is still the case. Am I getting the wrong impression?

“You get what you pay for.” has always been my reaction to Linux issues.

1 - I wonder what OS do you use.

2 - Have you actually tried Linux?

Re: A Linux Evening

#54

Post by nneonneo »

l1k wrote: post #15

Thunderbolt devices appear in the OS as a PCIe switch, so you need two additional bus numbers (one for the Switch Upstream Port and one for the Switch Downstream Port). If the device is hotplugged to a port which has run out of bus numbers, you'll get this error message. Mika Westerberg is constantly fine-tuning the allocation of PCI resources in the Linux kernel to avoid such scenarios. Some recent patches: https://…

It sounds like the pause/unpause might be the way to fix this properly, since trying to be heuristically smarter sounds like a recipe for never-ending corner case bugs like the OP’s issue.

The patch for pausing and unpausing seems quite reasonable, except that it does require driver support (unsurprising - you’re literally reallocating the resources used by the driver!). I suppose if you had at least a few movable devices then you should be ok in the event of a hotplug event, so you’d have to hope that enough drivers bother to support the feature.

I wonder what is necessary to get people to care about the patch enough to fix it up and mainline it? I suppose the problem it fixes is still niche enough that not so many people are clamoring for the fix.

Re: A Linux Evening

#55

Post by goosedragons »

I had a similar problem on Windows where it suddenly refused to work with any of my USB C ports. Linux could still detect them however. I did manage to get it working by doing a BIOs update on my motherboard since I noticed that the BIOs update notes mentioned "Improved USB compatibility". The weird thing is it worked in the past but I guess some Windows update changed something somewhere.

I think all OSs can experience these kinds of weird problems from time to time.

Re: A Linux Evening

#56

Post by revolvingocelot »

nicoco wrote: post #33

> 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 from the problem for a while, as one does, while I mused about the way troubleshooting works, and how my early life with Windows and now modern containerization has predisposed me to certain types of solu-- wait, I've got it! rmmod the bluetooth modules, modprobe 'em back in. Everything worked flawlessly. I'm not sure what I learned.

*sigh*

Re: A Linux Evening

#57

Post by eythian »

postit wrote: post #32

That’s where Linux burned all the bridges on being my main machine. Nowadays, I cannot afford to take a day off to fix obscure incompatibilities like this. The last straw to me was when I stored my closed lid xps in a bag and 3 hours later everything was smelling like burning plastic because the computer suspend suddenly stoped working. To get things worst, it happened during a long haul flight.

I seem to recall Dell saying that you should never store a suspended laptop in a laptop bag, because there are situations where it might wake up and overheat.

Re: A Linux Evening

#58

Post by Ygg2 »

kibwen wrote: post #40

> dkozel and your kind, whoever you are, wherever you are, and whatever you are doing right now, you are legend. Perhaps dkozel is reading this right now. :P https://news.ycombinator.com/threads?id=dkozel https://lobste.rs/threads/dkozel

Last comment was in 2020.

Re: A Linux Evening

#59

Post by rvdca »

sph wrote: post #11
quijoteuniv wrote: post #9

Yes, sometimes you land in these situations in Linux, but many times are self inflicted by unnecesary tinkering. I cannot see why dealing with all the … unwanted things from windows can ever be better. With mac if it is too new it will not be supported and after a few years you need to upgrade your hardware or are left to die. Apart from being an exclusive system for the rich.

This is why I run Fedora Silverblue. My Linux is now an appliance that upgrades atomically. If something breaks, I rollback. Once in a while, I pin a version that is known to work so it never gets garbage collected. The other day I changed /etc/ld.so.conf and the system would not boot—my fault. I choose the previous deployment in GRUB and I had a working system back.

NixOS feels the same but somehow... I still end up in those Linux evenings but for different reasons...

Re: A Linux Evening

#60

Post by sampa »

it is strange not to know to run dmesg first-thing when you have a HW problem for a guy who rants about "I spent several hours fixing a problem and I learned next to nothing in the process"

if you wanna learn, you should've known at least about dmesg

Post reply on HN