Live data from Hacker News

A Linux Evening

fabiensanglard.net

21–30 of 330 posts

Re: A Linux Evening

#21
About take away #2:

> I spent several hours fixing a problem and I learned next to nothing in the process. This trick is unlikely to be useful again. By the time I encounter something similar, it is likely I will have forgotten about the solution.

This is why it is important to keep a personal knowledge base/documentation. Mine is full of things I'll probably never encounter again, but I know it may be useful one day or another.

Re: A Linux Evening

#22
Someone should tell the author about the great lshw, it lists full details of the system board (and everything else) without having to go to a GUI display.

  azalp
    description: Desktop Computer
    product: B660M AORUS PRO AX DDR4 (Default string)
    vendor: Gigabyte Technology Co., Ltd.
    version: -CF
    serial: Default string
    width: 64 bits
    capabilities: smbios-3.4.0 dmi-3.4.0 smp vsyscall32
    configuration: boot=normal chassis=desktop family=B660 MB sku=Default string uuid=dotdotdot

People posting those CPU and SSD screens shots rather than, say, some linked data that contributes to make a graph to forums has such a deleterious effect on people's ability to reason. I suppose eventually we'll end up screen scraping the screen shots.

Re: A Linux Evening

#23

Side note: I've been working on creating a new blog now that I've completed my name change (and whatever other aspects of my transition affect my public persona). This blog's minimalism is still distinctively styled and I'd like to do something visually similar. The choice to make it black-on-light-gray is somewhat pleasing. Has a consensus been reached on dark styling affecting readability?

[deleted]

Re: A Linux Evening

#24

I hate linux for this. How the hell a modern OS can be frozen completely shut by some runaway python script running in a VS code debugger, to a point that you have to kill your PC with a button. And then non-obvious issues that just "appear" out of nowhere and steal your perfectly fine evening where you have planned to work on your favorite side project.

Linux will free memory that's backed by files, and load it again when it's needed. Under heavy memory pressure this has the same effect as swap thrashing, even if you have swap disabled. The kernel's out-of-memory killer does not help, because it's designed to work only as a last resort, and the system is still technically making progress despite being unusable in practice. AFAIK no other mainstream OS has this problem.

The solution is running a userspace out-of-memory killer, e.g. earlyoom.

Re: A Linux Evening

#25
post #7
post #5

Earlier quoted context omitted.

How is your comment related to the article? The only connection I can see is bad quality of some hardware and drivers.

It’s a reappearing issue with Linux that you run into problems other operating systems don’t have to this degree. Which is sad, because seeing the direction Windows 11 is heading towards, I’d like for Linux to achieve widespread adoption.

This is false.

My story, I bought a new widget, a gaming wheel a few years back, and it did not work on my Windows machine, I even reinstalled Windows, installed the drivers from disk it did not work. I send the thing back and report it broken and the guys call me to report that works perfectly. In the end I bought a different model that worked both on Windows and Linux.

So a gadget with official Windows support did not work on my machine, even after I wasted my time reinstalling Windows just in case but worked fine for some support people.

I had a diffrent experience with a USB WifFi antenna , it come with a mini CD with drivers but my PC had no CD Drive, there was no online source for that no name brnd.

I plugged it on a Linux machine and it worked, then I done a lsusb and found the real chip powering the device, then Googled for that I found a compatible Windows driver on a drivers website and I fixed it for Windows machine.

Linux has problems, but install a LTS distro on compatible hardware and you should not have issues for a few years.

To balance things, my latest bad experience in KDE was when Kwin crashed and refused to enable compositing again printing a vague reason in the logs, I found using Google that KWin put an isOPenGLSafe=false in soem log file and refused to start compositing but for some reason (maybe is a valid one) was incapable to print also that "I refuse to start compositing because of this setting - lesson for us devs, when we put stuff in log messages, put as much info as possible

Re: A Linux Evening

#26

I had a similar experience recently. Updated my Manjaro setup, rebooted, and was greeted with text mode. X just didn't load. 1 hour of reading logfiles and pondering about why the kernel module wouldn't load, it turns out I needed to add an obscure boot parameter (I think it was something like "ibp=off") to my kernel command line to make the nvidia module load again. Easy solution if you know how to solve it, 1 hour…

Anymore these days if it only takes me an hour to wade through all the reinstall/switch distro garbage to fix some obscure nonsense problem I count it as a win.

Re: A Linux Evening

#27

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.

A lot of my problems are from tinkering as well but that's why I am using linux, to control it better and tinker with it. Why won't I just use macos if I wanted something I can't tinker with? I think people lose sight if why Linux even exists to begin with, it is all about user control and ability to tinker/hack it.

I think better UX and more configurability would solve this stuff (from a friendly interface). The reason desktop/distro people won't do that is because it is considered bad UX practice to have too many decisions for the user. But imo, a Linux user would be an exception. In an ideal world, whoever decided to disable the boot flag in this case should have provided an easy to access distro/de setting to flip it back on.

Re: A Linux Evening

#28

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

Re: A Linux Evening

#29
The thing is.... You found a solution and if you wanted to understand you can always look at the kernel doc. When a similar thing happens in Windows, you are just done... Not only you have a very slim chance of not having to reinstall everything but even less understanding what is happening (ie. Probably an intern that committed something in some close source driver than will be silently fixed some day).

Re: A Linux Evening

#30
This occcurs every time I decided to dab into Linux. Usually I got the answer from a random search on stackoverflow and never managed to understand what happened.

But I think it's OK. I have always had an interest in system programming and that's why I wanted to dab into Linux. But system programming is not a shiny, whole smooth thing one may imagine, but is quite messy all the time. I simply got what I wanted.

Post reply on HN