Elitebook with mint wont connect again,peviously I was reduced to new
ssd and reinstall.
Cant keep this up
It boots and connects with modem but does not connect with net, tried
reboot of modem no joy had brainwave and made phone wi fi hub the laptop
connects with phone but does not talk to net
another laptop (dell)has no problem.
so is it hp,mint or browser related.or other
is it cache related

On Fri, 22 Apr 2022 20:50:45 +1000, F Murtz wrote:
> Elitebook with mint wont connect again,peviously I was reduced to new
> ssd and reinstall.
> Cant keep this up
> It boots and connects with modem but does not connect with net, tried
> reboot of modem no joy had brainwave and made phone wi fi hub the laptop
> connects with phone but does not talk to net
> another laptop (dell)has no problem.
> so is it hp,mint or browser related.or other
> is it cache related

To check cache with free. If swap is being used then that might be a problem.
$ free -h
total used free shared buff/cache available
Mem: 7.8Gi 641Mi 272Mi 17Mi 6.9Gi 6.8Gi
Swap: 8.0Gi 120Mi 7.9Gi

Shows I have 272Mi free ram and plenty of buffer/cache available and barely used swap.

You will have to check the system log for errors.

Problems I have seen in the past was addresses handed out to devices on lan.
Solution was to power down devices then power each one up and check connectivity.

I found it was easier to assign fixed ip addresses to each device which makes it easier
to troubleshoot network problems. You and run
arp --numeric | sort --version-sort --key=1
to get list of devices mac HWaddress to use in router dhcp table to assign
mac a fixed ip addressses. After that configure each device as static ip
and set value in /etc/hosts which is copied to each system, Example:
arp --numeric | sort --version-sort --key=1
192.168.50.1 ether a4:2b:8c:09:90:f9 CM enp3s0
192.168.50.3 ether c0:74:ad:34:6f:97 C enp3s0
192.168.50.100 ether d8:eb:97:6f:35:b4 CM enp3s0
192.168.50.140 ether d8:eb:97:6f:9c:05 CM enp3s0
192.168.50.196 ether cc:79:cf:03:c8:43 CM enp3s0
192.168.50.197 ether 78:a5:dd:11:93:a2 CM enp3s0
192.168.50.198 ether 78:a5:dd:11:93:bd CM enp3s0
192.168.50.200 ether 08:60:6e:44:25:56 CM enp3s0
Address HWtype HWaddress Flags Mask Iface

$ grep .50. /etc/hosts
192.168.50.1 myrtr.home.test home-router-lan
192.168.50.100 tb.home.test tb
192.168.50.132 wb.home.test wb
192.168.50.140 wb4.home.test wb4
192.168.50.190 ptr.home.test ptr
192.168.50.190 scr.home.test scanner
192.168.50.195 webcam4.wcams.test webcam4
192.168.50.196 webcam3.wcams.test webcam3
192.168.50.197 webcam2.wcams.test webcam2
192.168.50.198 webcam.wcams.test webcam
192.168.50.200 mtv.home.test mtv

F Murtz wrote:
> Elitebook with mint wont connect again,

> so is it hp,mint or browser related.or other

My 'theory' on my ether network problems which I have to solve by
booting a Win and using its network troubleshooter is that it might be
related to the linux 'binary blob' for the network chipset getting out
of whack.

Since I don't know how to delve into tweaking what the OS does to solve
firmware problems, I have to resort to a strategy which works for me and
doesn't take any time.

The machine on which the ethernet problem has arisen the most is one
which I use to boot multiple linux live .iso/s on a Ventoy multiboot and
that machine has Win7 on its hdd; so I just boot the Win7 and let the
Win network troubleshooter solve the problem and then I go back to my
Ventoy USB for the linuxes. It might be months before the problem
arises again.

--
Mike Easter

On Fri, 22 Apr 2022 08:46:38 -0700, Mike Easter wrote:

>
> The machine on which the ethernet problem has arisen the most is one
> which I use to boot multiple linux live .iso/s on a Ventoy multiboot and
> that machine has Win7 on its hdd; so I just boot the Win7 and let the
> Win network troubleshooter solve the problem and then I go back to my
> Ventoy USB for the linuxes. It might be months before the problem
> arises again.

Back when I did have a win7 installed I noticed the nic card would not
come up under linux after a soft win7 boot. I had to poweroff before
booting Linux for the nic card to work.

Bit Twister wrote:
> Back when I did have a win7 installed I noticed the nic card would not
> come up under linux after a soft win7 boot. I had to poweroff before
> booting Linux for the nic card to work.

Hmm. I'll keep the poweroff strategy in mind as an alternative (to
booting the Win). I would say when wrestling w/ the problem, I
typically just rebooted.

--
Mike Easter

On 22/4/22 22:31, Bit Twister wrote:
> On Fri, 22 Apr 2022 20:50:45 +1000, F Murtz wrote:
>> Elitebook with mint wont connect again,peviously I was reduced to new
>> ssd and reinstall.
>> Cant keep this up
>> It boots and connects with modem but does not connect with net, tried
>> reboot of modem no joy had brainwave and made phone wi fi hub the laptop
>> connects with phone but does not talk to net
>> another laptop (dell)has no problem.
>> so is it hp,mint or browser related.or other
>> is it cache related
>
> To check cache with free. If swap is being used then that might be a problem.
> $ free -h
> total used free shared buff/cache available
> Mem: 7.8Gi 641Mi 272Mi 17Mi 6.9Gi 6.8Gi
> Swap: 8.0Gi 120Mi 7.9Gi
>
> Shows I have 272Mi free ram and plenty of buffer/cache available and barely used swap.
>
> You will have to check the system log for errors.
>
> Problems I have seen in the past was addresses handed out to devices on lan.
> Solution was to power down devices then power each one up and check connectivity.
>
> I found it was easier to assign fixed ip addresses to each device which makes it easier
> to troubleshoot network problems. You and run
> arp --numeric | sort --version-sort --key=1
> to get list of devices mac HWaddress to use in router dhcp table to assign
> mac a fixed ip addressses. After that configure each device as static ip
> and set value in /etc/hosts which is copied to each system, Example:
> arp --numeric | sort --version-sort --key=1
> 192.168.50.1 ether a4:2b:8c:09:90:f9 CM enp3s0
> 192.168.50.3 ether c0:74:ad:34:6f:97 C enp3s0
> 192.168.50.100 ether d8:eb:97:6f:35:b4 CM enp3s0
> 192.168.50.140 ether d8:eb:97:6f:9c:05 CM enp3s0
> 192.168.50.196 ether cc:79:cf:03:c8:43 CM enp3s0
> 192.168.50.197 ether 78:a5:dd:11:93:a2 CM enp3s0
> 192.168.50.198 ether 78:a5:dd:11:93:bd CM enp3s0
> 192.168.50.200 ether 08:60:6e:44:25:56 CM enp3s0
> Address HWtype HWaddress Flags Mask Iface
>
> $ grep .50. /etc/hosts
> 192.168.50.1 myrtr.home.test home-router-lan
> 192.168.50.100 tb.home.test tb
> 192.168.50.132 wb.home.test wb
> 192.168.50.140 wb4.home.test wb4
> 192.168.50.190 ptr.home.test ptr
> 192.168.50.190 scr.home.test scannerand do not understand
> 192.168.50.195 webcam4.wcams.test webcam4
> 192.168.50.196 webcam3.wcams.test webcam3
> 192.168.50.197 webcam2.wcams.test webcam2
> 192.168.50.198 webcam.wcams.test webcam
> 192.168.50.200 mtv.home.test mtv
>
>
>
>
My problem is trying to use linux without being a boffin and do not
understand most of that gobbledygook

On Sat, 23 Apr 2022 02:39:23 +1000, F Murtz wrote:
> On 22/4/22 22:31, Bit Twister wrote:
>> On Fri, 22 Apr 2022 20:50:45 +1000, F Murtz wrote:
>>> Elitebook with mint wont connect again,peviously I was reduced to new
>>> ssd and reinstall.
>>> Cant keep this up
>>> It boots and connects with modem but does not connect with net, tried
>>> reboot of modem no joy had brainwave and made phone wi fi hub the laptop
>>> connects with phone but does not talk to net
>>> another laptop (dell)has no problem.
>>> so is it hp,mint or browser related.or other
>>> is it cache related
>>
>> To check cache with free. If swap is being used then that might be a problem.
>> $ free -h
>> total used free shared buff/cache available
>> Mem: 7.8Gi 641Mi 272Mi 17Mi 6.9Gi 6.8Gi
>> Swap: 8.0Gi 120Mi 7.9Gi
>>
>> Shows I have 272Mi free ram and plenty of buffer/cache available and barely used swap.
>>
>> You will have to check the system log for errors.
>>
>> Problems I have seen in the past was addresses handed out to devices on lan.
>> Solution was to power down devices then power each one up and check connectivity.
>>
>> I found it was easier to assign fixed ip addresses to each device which makes it easier
>> to troubleshoot network problems. You and run
>> arp --numeric | sort --version-sort --key=1
>> to get list of devices mac HWaddress to use in router dhcp table to assign
>> mac a fixed ip addressses. After that configure each device as static ip
>> and set value in /etc/hosts which is copied to each system, Example:
>> arp --numeric | sort --version-sort --key=1
>> 192.168.50.1 ether a4:2b:8c:09:90:f9 CM enp3s0
>> 192.168.50.3 ether c0:74:ad:34:6f:97 C enp3s0
>> 192.168.50.100 ether d8:eb:97:6f:35:b4 CM enp3s0
>> 192.168.50.140 ether d8:eb:97:6f:9c:05 CM enp3s0
>> 192.168.50.196 ether cc:79:cf:03:c8:43 CM enp3s0
>> 192.168.50.197 ether 78:a5:dd:11:93:a2 CM enp3s0
>> 192.168.50.198 ether 78:a5:dd:11:93:bd CM enp3s0
>> 192.168.50.200 ether 08:60:6e:44:25:56 CM enp3s0
>> Address HWtype HWaddress Flags Mask Iface
>>
>> $ grep .50. /etc/hosts
>> 192.168.50.1 myrtr.home.test home-router-lan
>> 192.168.50.100 tb.home.test tb
>> 192.168.50.132 wb.home.test wb
>> 192.168.50.140 wb4.home.test wb4
>> 192.168.50.190 ptr.home.test ptr
>> 192.168.50.190 scr.home.test scannerand do not understand
>> 192.168.50.195 webcam4.wcams.test webcam4
>> 192.168.50.196 webcam3.wcams.test webcam3
>> 192.168.50.197 webcam2.wcams.test webcam2
>> 192.168.50.198 webcam.wcams.test webcam
>> 192.168.50.200 mtv.home.test mtv
>>
>>
>>
>>
> My problem is trying to use linux without being a boffin and do not
> understand most of that gobbledygook

well, that is your choice. You either make the computer work for you
or you let the computer work you.

The above is pretty straight forward. You can direct the dhcp server
to hand out a fixed ip address to a specific hardware/mac addresses.

You put the ip address in /etc/hosts and the computer then knows
the ip address of a node. For example I can test if the network printer
is alive using "ping ptr" or "ping ptr.home.test"

A Linux/doze out of the box setup is usually the device ip address is
set as dynamic and assigned the next available ip address.

So, turning off/on a device may cause the device to get a new ip address
assigned by the router.