News for hackers. Stuff that matters.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by bheadmaster on Monday January 15, 2024 @07:09AM (#38999905)
Glad to see that Microsoft is making Windows more and more similar to Linux by every passing day :)
Re:Microsoft suggests command line fiddling to fix faulty Wi... by msla on Monday January 15, 2024 @08:07AM (#39000474)
Yeah, this isn't Linux. Linux is better than this these days.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by bheadmaster on Monday January 15, 2024 @08:22AM (#39000652)
Of course. Things are not perfect, but most of the popular (GNU/)Linux distributions gone a long way from the old days of requiring terminal fixes.

I just meant it as a lighthearted joke.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by carlosjobim on Monday January 15, 2024 @08:38AM (#39000813)
Except for if you want to use dual monitors, etc. etc.

Every time I've tried Linux, I've had to dive into the terminal and paste commands from the internet to get normal things to work.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by trelane on Monday January 15, 2024 @08:50AM (#39000948)
Only two monitors?

I've no problem with more than that. I don't know what hardware you're using, but that's atypical.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by carlosjobim on Monday January 15, 2024 @09:23AM (#39001285)
Two monitors with different DPI. Couldn't get them to work well without running a weird xrandr script on every boot with some "1.9999999999...." setting.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by ParetoOptimal on Monday January 15, 2024 @11:23AM (#39002567)
Without Wayland I'm pretty sure this is still the case.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by trelane on Monday January 15, 2024 @11:56AM (#39002973)
I use Wayland. Perhaps that's your issue?
Re:Microsoft suggests command line fiddling to fix faulty Wi... by ParetoOptimal on Monday January 15, 2024 @04:31PM (#39006363)
I moved to Wayland mostly, but gaming performance is worse. Mostly latency and 1% fps lows.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by justsomehnguy on Monday January 15, 2024 @10:13AM (#39001840)
"Works for me" (r)(tm)
Re:Microsoft suggests command line fiddling to fix faulty Wi... by mr_mitm on Monday January 15, 2024 @08:40AM (#39000832)
Was this in the past decade or before?
Re:Microsoft suggests command line fiddling to fix faulty Wi... by carlosjobim on Monday January 15, 2024 @09:23AM (#39001293)
A couple of years ago.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by Zyst on Monday January 15, 2024 @08:47AM (#39000912)
I use Linux. You absolutely need to drop down to the command line at times. Upgrading my Kennel, or Graphics driver breaks something like 20% of the time for me.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by berkes on Monday January 15, 2024 @08:55AM (#39001007)
Strange.

I've been on Linux some 28 years now, and it used to be like that¹. But today? I haven't had a kernel or graphics driver update failing on me for years. Maybe 10+ years? Granted, my Linux is the most boring, hardly-configged Unbuntu LTS. Boring hardware. Boring drivers. Everything optimized to "Just Work" - My machine pays my bills and if I'm down for a day because I fiddled around with some fancy custom trackpad module, or special Bluetooth whatevers, it's costing me actual money.

I'm certainly in my terminal 80% of the time (developing in nvim etc), so can't say much about how much it is needed by someone who doesn't know or use that terminal.

¹ My personal worst was at a conference doing a presentation for a 200+ audience having to recompile X, while entertaining the audience, because the beamer wasn't found and X crashed on it.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by ParetoOptimal on Monday January 15, 2024 @11:20AM (#39002543)
I bet you use stable graphics drivers on older graphics cards and the person your responding to uses newer graphics cards and quickly updates to the latest drivers.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by berkes on Monday January 15, 2024 @12:48PM (#39003745)
Yes. Hence "boring".
Re:Microsoft suggests command line fiddling to fix faulty Wi... by maleldil on Monday January 15, 2024 @09:23AM (#39001288)
What hardware? Your experience with Linux can be very different depending on that. For example, my laptop's WiFi refuses to work properly on Linux, so I'm forced to use Windows.

Edit: oh, and not to mention graphics (Nvidia), multiple monitors and HiDPI, especially with fractional scaling and different multiples per display. HiDPI on Linux doesn't work nearly as well as Windows and macOS.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by vladvasiliu on Monday January 15, 2024 @10:34AM (#39002069)
It's funny, I can say the exact same thing in reverse. My two latest laptops are boring: integrated graphics, intel wifi, run-of-the-mill hp "enterprise" fare. One running a zen3, the other an 11th gen intel.

On the AMD, I couldn't use the webcam for a good six months under Windows. It wouldn't detect some part of the USB tree.

On the Intel, for a good year, I couldn't get 4k@60Hz over DP via the HP dock. Then at some point, installing Intel drivers fixed the issue, but Windows would insist on "updating" to the older, borken version every so often. Now Windows also has the correct drivers. A different dock still doesn't work. Then there's the fact that the Windows installation (11 22h2) doesn't support the touchpad, nor the wifi card. Bonus points for the default install insisting on connecting to the internet for the online account thing.

Linux had 0 issues on both since the day I got them.

As for HiDPI, yeah, the Linux story, at least with X11, is non-existent if you want multiple HiDPI settings. But Windows is a crap shoot, too. It's easy to get a blurry mess: just connect and disconnect an external screen, and even the freaking windows 11 start menu is borked. It looks fine when you open it, but start typing something and enjoy the blurriness. Apps will be stuck with either enormous or tiny text. The context menus of the systray icons will appear all over the place.

Some apps manage to combine everything: tiny text, yet blurry, and displayed in the middle of the screen. To name and shame: Fortinet VPN client.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by lupusreal on Monday January 15, 2024 @12:09PM (#39003203)
If you know you're going to use Linux before buying a machine, you can generally save yourself all the trouble by simply avoiding broadcom and nvidia. Those two have been the source of the most trouble for years.

Intel for graphics and wifi is generally the safest choice. I pick laptops with those and have great success.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by swells34 on Monday January 15, 2024 @03:41PM (#39005820)
A decade ago I stopped having problems with both BCM and NVidia devices in Linux. Last year I purchased a very recent wifi dongle and had to manually install broadcom drivers, but other than that it's been smooth sailing with no issues.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by berkes on Monday January 15, 2024 @12:51PM (#39003784)
My current machine is a "clevo". Some whitelabel thing that I bought from a company that delivers Laptops with linux preïnstalled. Intel i7, intel iRIS, etc. It all "just works".

I'm not trying to argue that "Linux Just Works" or that "you won't run into hardware issues on Linux". I'm arguing that by choosing "boring" hardware, and "a boring LTS from a large distro" you won't.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by Macha on Monday January 15, 2024 @08:57AM (#39001036)
That's way higher than my experience.

I had a kernel update break a memory management API that JavaScript engines use about a year ago, and then before that my last kernel induced update breakage was in like 2012 with fglrx.

That broken kernel update also would not have made it into more conservative distros, as the change was rolled back 5 days later.

Meanwhile I have previously experienced the windows issue in this topic in like 2019. The windows 7 installer created even smaller reserved partitions than the windows 10 one (100 Vs 500 mb iirc), so users with systems upgraded from 7 to 10 would have seen this sooner.

And for completeness sake I've also experienced OS X fail at updating to High Sierra as that updater didn't like something about the way my employers provisioning software had set up the partition layout some years earlier.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by bheadmaster on Monday January 15, 2024 @09:06AM (#39001131)
nVidia on Linux is particularly nasty in that aspect.

I've administrated a fleet of ~100 Ubuntu devices that used nVidia for some AI stuff - unattended-upgrades disabled and all that - and yet graphics drivers broke in regular intervals, every couple of months. Apparently, nVidia drivers have some system in place that can update drivers on its own. The only solution was to uninstall all nVidia drivers, upgrade all packages, then re-install nVidia drivers.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by wao0uuno on Monday January 15, 2024 @09:01AM (#39001067)
I assume that you’re an Nvidia user. This is most likely the cause of your problem. Linux just works on Intel or AMD.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by bhdlr on Monday January 15, 2024 @09:34AM (#39001393)
I think the point is that the Linux command line is more functional and easier to navigate than the Windows command prompt
Re:Microsoft suggests command line fiddling to fix faulty Wi... by marcosdumay on Monday January 15, 2024 @09:15AM (#39001213)
I don't have anything break on the graphical stack on my computers since 2007.

But somehow Debian keeps uninstalling the display manager. One would think this is the easiest problem in the world to avoid, but they avoid every hard problem, and this one passes by.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by davidgerard on Monday January 15, 2024 @09:49AM (#39001568)
nVidia, I would guess?

I realise it doesn't help now, but in the future you may want to avoid hardware that's specifically hostile to Linux.

there's a reason I chose my latest laptop specifically because it was Ryzen.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by HKH2 on Monday January 15, 2024 @08:58AM (#39001043)
What distro do you use?
Re:Microsoft suggests command line fiddling to fix faulty Wi... by agubelu on Monday January 15, 2024 @09:03AM (#39001093)
On the current LTS version of Ubuntu, I had to drop down to the terminal to adjust the mousewheel's scroll speed.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by ghqst on Monday January 15, 2024 @09:17AM (#39001232)
Having to use such a terrible hack to change scroll speed on GNOME is my least favorite thing about it.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by fsflover on Monday January 15, 2024 @09:20AM (#39001260)
Ubuntu is doing wrong a lot of things, not just this one.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by gchamonlive on Monday January 15, 2024 @08:04AM (#39000426)
You mean 90's Linux?
Re:Microsoft suggests command line fiddling to fix faulty Wi... by OsrsNeedsf2P on Monday January 15, 2024 @08:42AM (#39000855)
Hey! Some of us still use Linux the old "hacker command line" way
Re:Microsoft suggests command line fiddling to fix faulty Wi... by gchamonlive on Monday January 15, 2024 @11:19AM (#39002521)
I use arch btw, and even then with zsh, shell highlighting, annotations, fuzzy finder and vim on steroids, the "hacker way" can be really different from two decades ago.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by fsflover on Monday January 15, 2024 @09:19AM (#39001249)
It doesn't mean that you have to.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by cesarb on Monday January 15, 2024 @09:56AM (#39001647)
It's hard to avoid. I know I can open the GUI file manager to look at a directory, and sometimes I try to force myself to do that, but way too often I quickly open a terminal and type a "ls" command. It's just what I got used to when I first started using computers back in the 1990s, and habits can be hard to break.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by jstummbillig on Monday January 15, 2024 @09:23AM (#39001295)
Are you claiming that using Linux in 2023 will not pretty much require "command line fiddling" to some unavoidable degree (unless you have somebody else do the setup for you and day to day just use what's there)? Because, if so, that would very much not be my experience. Broadly speaking, what advancements am I likely missing out on?
Re:Microsoft suggests command line fiddling to fix faulty Wi... by graemep on Monday January 15, 2024 @09:39AM (#39001461)
Depends on distro and usage, but once installed Linux does not need command line fiddling. There are GUIs for installing and updating the OS and applications and pretty much everything else an average user does.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by jstummbillig on Monday January 15, 2024 @10:19AM (#39001908)
In that case I will have to disagree. I run a stock, up to date Ubuntu. Yes, there is a GUI for a lot of things, but I will most certainly run into something that will require me to drop to the CLI before long – which I am fine with, but I am not going to pretend it won't inevitably happen.

My experience is: On Windows, for most enduser use cases (and this absolutely excludes anything dev related), I would expect the user to get by without touching the CLI. In fact, I would assume that any given application will expose all of its functionality only through a graphical UI. For me, on Linux, the opposite expectation applies.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by swells34 on Monday January 15, 2024 @11:32AM (#39002671)
I disagree. On stock Ubuntu, there is no normal situation you'll run into where you must use a terminal. If you decide to do something that requires a terminal, that's a different story. But basically every normal operation you'd do on windows GUI (and more...), you have a GUI option available on Ubuntu; it is the Windows of the Linux world, and it behaves as such.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by gverrilla on Monday January 15, 2024 @03:27PM (#39005632)
Cmon my ubuntu stock can't even remember my sound input options, which are reset on each reboot. There's no option for that on the GUI. Also upgrading linux can be a big pain for non-experts. I've been using dualboot windows/linux for a long time, and I simply don't upgrade ubuntu: I'll do a fresh install if I want/need the new version.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by rigid on Monday January 15, 2024 @10:38AM (#39002114)
also nothing in linux will ever just give some cryptic hex code error or crash report.

It's either crashdump or nice error message. If not I just increase loglevel to find the actual problem.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by lupusreal on Monday January 15, 2024 @09:39AM (#39001459)
Yeah, in OpenSUSE I'd just rollback a bad update like this. Automatic snapshotting before and after all package manager operations is very nice.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by sixothree on Monday January 15, 2024 @09:28AM (#39001340)
Did a fresh install of windows 11 yesterday and winget doesn’t work. Seriously. I haven’t even installed any software yet.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by kotaKat on Monday January 15, 2024 @09:35AM (#39001395)
You have to wait for all the back-end updates to finish. Install all the Windows Updates, then open Microsoft Store and go to the Library and wait for it to update even more shit, then you finally will have Terminal and WinGet.

Yeah, I found that one out the annoying way too.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by sixothree on Monday January 15, 2024 @01:03PM (#39003956)
Maybe I was experiencing something else on top of that because I was getting exception codes at first. But then once I started getting "source errors" I decided to check the store and such and that's when things started working more normally.

What's surprising though is that it listed the msstore source as operating normally when I did winget source update. Regardless, kind of crappy this doesn't work out of the box and I have wave dead things not mentioned in any instructions to get this dumb thing working.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by kotaKat on Monday January 15, 2024 @01:41PM (#39004393)
My experience (and path that lead to this) was realizing that a fresh install of Windows 11 gave me PowerShell and not Terminal in the Win+X menu.

WinGet would... launch, but provide no output. And of course, it was my first time trying to use WinGet in general...

A few reboots later suddenly Win+X had Terminal and WinGet started working, and on a subsequent reinstall in a VM I spotted that, yeah, apparently all the extra WinGet, Terminal, etc stuff all has to be pushed from the MS Store instead of Windows Update.

Total pain in the ass.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by krger on Monday January 15, 2024 @09:33AM (#39001378)
The output turns blue and nothing happens? Update Terminal and then winget will work.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by sixothree on Monday January 15, 2024 @12:59PM (#39003895)
No I was getting "0x8a15000f : Data required by the source is missing" out of the box. Then after that went away it was another error. It might be related to this not being a "local only" account and not a microsoft account.

Ultimately, thinking winget can be used like apt to get a new system up and running is misguided on my part.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by hooby on Monday January 15, 2024 @09:32AM (#39001369)
I really do not agree with this comparison.

Yes, it is true, that on Linux there are many, many things which are best done through command line fiddling.

But installing a system update, that update borking things, belching up a totally cryptic error message, and then forcing you to clean up the mess through the command line, is nothing something I've experienced on Linux so far. For me, apt updates have always been super reliable - and error messages have mostly been quite specific and easy to google.

So, this specific case seems nothing like Linux to me.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by jstummbillig on Monday January 15, 2024 @09:36AM (#39001411)
> For me, apt updates have always been super reliable - and error messages have mostly been quite specific and easy to google.

The ocean between. While you or me might appreciate a good error message and handy debugging options, the standard windows user experience is optimised to not confront users with errors at all. Either approach comes with its trade offs and is implemented with varying degrees of success.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by swells34 on Monday January 15, 2024 @10:22AM (#39001935)
Ah yes, the classic "if I can't see the bad thing, it doesn't exist" approach to problem solving.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by jstummbillig on Monday January 15, 2024 @10:34AM (#39002072)
Different design goals. While there's tension between Windows/Linux (which, interestingly, has over the years partly been released by each adopting pages of the others' playbook) there are a lot of complex or critical systems in the world, where displaying an error message to the user is clearly not a great design choice.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by swells34 on Monday January 15, 2024 @11:14AM (#39002469)
Yes, and some people just want to take their car to the mechanic, while other people want to fix theirs. It's a classic struggle in any area. The big difference though, is if I use my car in a professional capacity, I want to know how to change my own oil, because I'm not an idiot. I want to be able to fix simple issues, because that's just being professionally responsible.

Windows discourages this kind of professional responsibility, hides everything it can that would give you an inkling of what's going on under the hood. Microsoft wants you to be dependent on them for doing ANYTHING out of the ordinary. And of course, when anything out of the ordinary occurs, there is wailing and gnashing of teeth from millions of windows users, billions of dollars lost by their employers, and all the Linux users just stare in disbelief that y'all don't know how to change your own oil. If you use a computer for work, should probably know how it works. Microsoft has intentionally made it difficult, so... Have you tried Linux, the backbone of modern computing, installed on more devices than Windows by at least a factor of two?

Re:Microsoft suggests command line fiddling to fix faulty Wi... by JoeAltmaier on Monday January 15, 2024 @11:18AM (#39002508)
Might be a bit of hyperbole.

Microsoft had extensive documentation of nearly every API they support, and some they don't. Comprehensive documentation with notes and caveats. Automatically available from their tools.

Compare, for instance, with Apples almost total non-documentation of anything. Mostly just scraped comments with arguments barely described e.g 'a string'. No notes, no architecture, nothing.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by swells34 on Monday January 15, 2024 @03:34PM (#39005733)
Yes, my comment contained more hyperbole than it should have; I was frustrated at the idea of "hiding information about a problem" as a good design goal, and let that frustration influence my writing. Apologies to jstummbillig for that. Thank you for being the voice of reason in the room, Joe.

Interesting, I've never found Microsoft documentation for Windows thorough enough to reason about a problem, especially when compared to Arch or Gentoo's docs. I always feel like I'm reading the abstract of a paper, with no access to the rest of it. Is there some kind of special access or login requirement for deeper documentation, or am I just spoiled by the great Linux docs?

Apple products are the king of the "you don't own your device" mantra. I just refuse to develop anything for them, because the time expense of trying to guess how to get the OS to comply hasn't been worth the reward. That being said, I've found the documentation for Swift to be extremely good, better than most other languages I work with.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by JoeAltmaier on Tuesday January 16, 2024 @08:16AM (#39012920)
Yeah Microsoft is definitely not much better than a walled garden for much of their technology.

I was privileged(?) to have access to source under license for years, contracting with a company that ported Windows to various industrial platforms. So my view is similarly colored.

Linux is definitely the king, no argument there.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by apexalpha on Monday January 15, 2024 @10:04AM (#39001729)
>For me, apt updates have always been super reliable - and error messages have mostly been quite specific and easy to google.

Lmao, come on now.

"Error: unmet dependencies"

Re:Microsoft suggests command line fiddling to fix faulty Wi... by hooby on Monday January 15, 2024 @10:16AM (#39001875)
"Error: unmet dependencies"

I swear, I haven't run into this.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by lnxg33k1 on Monday January 15, 2024 @10:27AM (#39001997)
Ohla' was about to ask where was the lacche' riding on their white horse in order to defend the multinational corporation, welcome to the conversation
Re:Microsoft suggests command line fiddling to fix faulty Wi... by swells34 on Monday January 15, 2024 @10:20AM (#39001926)
I've never had an update issue on a Linux device. I update whenever I like, and have never been forced to. Occasionally some items fail due to dependency issues, the error messages are very descriptive, I handle the dependencies and move on with the update. Failed updates are a uniquely Windows issue in my experience, had something like 10-15 of them in my lifetime.
Re:Microsoft suggests command line fiddling to fix faulty Wi... by masto on Monday January 15, 2024 @10:33AM (#39002057)
Your experience differs from mine. If I only count major incidents, I've had at least two occasions where a Linux operating system update completely hosed my system. One was a Rackspace VPS I never managed to recover, I had to use their management tools to download a binary image of the unbootable disk and fuss around to mount it and get my files off so I could build a new server.

I'm very hesitant to touch Linux updates, but I am occasionally "forced to" when I need to run a new piece of software that ends up being like pulling on a loose string on a sweater.

Re:Microsoft suggests command line fiddling to fix faulty Wi... by swells34 on Monday January 15, 2024 @11:25AM (#39002593)
That's quite strange. What distro? For a while I was managing several hundred Linux devices remotely, so I've done thousands of updates with no issues. Linux has been my daily driver for 15 years, and never had an update issue there (that I didn't create myself). Specifically the thing I've NEVER had an issue with was a standard system update. Apt upgrade, pacman or yay -SYU, things of that nature. Had plenty of problems when trying to do weird shit, but I've also learned how to solve those problems. I've never borked an important system so bad it became unrecoverable. Some distros are prone to update failure because they always give you bleeding edge releases. I'd suggest running Debian, a ridiculously stable "fire and forget" system. Many rolling distros, like Arch, I'd say to update every couple of days to avoid dependency chain problems. But again, none of this is difficult beyond having to read some documentation, and none of this should even be able to cause system loss. Did you do something else weird that you forgot to mention?
Re:Microsoft suggests command line fiddling to fix faulty Wi... by masto on Tuesday January 16, 2024 @07:51AM (#39012732)
In answer to the question, no, I did not forget to mention that I did anything "weird". It was apt-get upgrade.

I'm not going to have an argument about my personal experience. You can find plenty of others in the comments who have had similar problems. I enjoyed the response, as I've been joking for 20+ years that 95% of the time Linux advocates will tell anyone running into issues "you're using the wrong distro".