No internet under Ubuntu 22.04 after booting into Windows 10

[Liam Proven]

On Sun, 18 Dec 2022 at 16:10, sciguy <sciguy at vex.net> wrote:
>
> First of all, a big thanks to everyone for responding. I got a lot more
> questions than I expected, and I will do my best to answer them here.

Oh good. :-) Let's hope something proves useful and leads to a fix.

>  I
> feel any talk about a firmware upgrade seems like a red herring,

I think it might not be, and I have 3 reasons for this.

[1] Desktop PC vendors mainly only test against Windows. Running other
OSes thus tends to show up weird firmware bugs. It's an Intel device
so managed by the Intel firmware, which is very complex and involves
Minix 3 in there. Thus, "check for newer firmware" is one of my go-to
bits of advice for weird, hard-to-trace problems.

[2] In my experience working full-time in the Linux world for nearly a
decade now, it's often overlooked. Even inside Linux vendor companies.
It has helped me.

[3] PC lifecycles tend to go like this:

Young hardware, new, shiny, runs Windows and high end demanding apps,
so the firmware shows no problems as it was tested on Windows $CURRENT
and nothing else.

Middle-aged hardware, still usable, getting a bit slow in original
now-dated Windows, let's try Windows $NEW_VERSION which didn't exist
when the hardware was new, or let's try a mainstream high-end Linux
version with tons of proprietary drivers in it.

Elderly hardware, no use at all with Windows or heavyweight Linux now,
so let's try something super-lightweight and obscure.

In the last few years, vendors bundle firmware-updating tools in with
Windows. So it updates itself, or nags you. So firmware issues are
somewhat less problematic. So for young kit, it's less of a problem.

Middle-aged kit: it's harder work but much more worth doing. E.g. one
of my work desktops went from version A01 to version A12 and it took a
good minute or two off the bootup time. That's time saved every single
day.

Elderly kit: check, because there's a good chance it's never been done
and you might be able to leapfrog a dozen versions to something with
all known issues resolved.

> I did go through the trouble
> of checking, and yes, the router firmware is the most current.

OK, that's good.


-- 
Liam Proven ~ Profile: https://about.me/liamproven
Email: lproven at cix.co.uk ~ gMail/gTalk/FB: lproven at gmail.com
Twitter/LinkedIn: lproven ~ Skype: liamproven
UK: (+44) 7939-087884 ~ Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053