Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

You can observe a lot just by watching. -- Yogi Berra


computers / alt.os.linux.mint / Re: Mint 21.1 Cinnamon locking up

SubjectAuthor
* Mint 21.1 Cinnamon locking upRob H
+* Re: Mint 21.1 Cinnamon locking upYrrah
|`* Re: Mint 21.1 Cinnamon locking upRob H
| `* Re: Mint 21.1 Cinnamon locking uppinnerite
|  `- Re: Mint 21.1 Cinnamon locking upPaul
+* Re: Mint 21.1 Cinnamon locking upBig Al
|+- Re: Mint 21.1 Cinnamon locking upYrrah
|+* Re: Mint 21.1 Cinnamon locking upMike Easter
||`* Re: Mint 21.1 Cinnamon locking upBig Al
|| `- Re: Mint 21.1 Cinnamon locking upMike Easter
|+- Re: Mint 21.1 Cinnamon locking upRob H
|`- Re: Mint 21.1 Cinnamon locking upRonB
+* Re: Mint 21.1 Cinnamon locking upPaul
|`- Re: Mint 21.1 Cinnamon locking upRob H
`* Re: Mint 21.1 Cinnamon locking upNic
 `* Re: Mint 21.1 Cinnamon locking upRob H
  `* Re: Mint 21.1 Cinnamon locking upNic
   `* Re: Mint 21.1 Cinnamon locking upRob H
    `* Re: Mint 21.1 Cinnamon locking upNic
     `* Re: Mint 21.1 Cinnamon locking upRob H
      `* Re: Mint 21.1 Cinnamon locking upRob H
       `* Re: Mint 21.1 Cinnamon locking upBig Al
        `* Re: Mint 21.1 Cinnamon locking upRob H
         `* Re: Mint 21.1 Cinnamon locking upPaul
          `* Re: Mint 21.1 Cinnamon locking upRob H
           `* Re: Mint 21.1 Cinnamon locking upPaul
            `* Re: Mint 21.1 Cinnamon locking upRob H
             +* Re: Mint 21.1 Cinnamon locking upPaul
             |`* Re: Mint 21.1 Cinnamon locking upPaul
             | `* Re: Mint 21.1 Cinnamon locking upRob H
             |  `* Re: Mint 21.1 Cinnamon locking uppinnerite
             |   `* Re: Mint 21.1 Cinnamon locking upRob H
             |    `* Re: Mint 21.1 Cinnamon locking uppinnerite
             |     `* Re: Mint 21.1 Cinnamon locking upRob H
             |      `* Re: Mint 21.1 Cinnamon locking upPaul
             |       `* Re: Mint 21.1 Cinnamon locking upRob H
             |        `* Re: Mint 21.1 Cinnamon locking upNic
             |         `* Re: Mint 21.1 Cinnamon locking upRob H
             |          +- Re: Mint 21.1 Cinnamon locking upPaul
             |          `* Re: Mint 21.1 Cinnamon locking upNic
             |           `* Re: Mint 21.1 Cinnamon locking upRob H
             |            `* Re: Mint 21.1 Cinnamon locking upNic
             |             +- Re: Mint 21.1 Cinnamon locking upRob H
             |             `* Re: Mint 21.1 Cinnamon locking upRob H
             |              +* Re: Mint 21.1 Cinnamon locking upPaul
             |              |`- Re: Mint 21.1 Cinnamon locking upRob H
             |              `* Re: Mint 21.1 Cinnamon locking upNic
             |               `* Re: Mint 21.1 Cinnamon locking upRob H
             |                `* Re: Mint 21.1 Cinnamon locking upNic
             |                 `* Re: Mint 21.1 Cinnamon locking upRob H
             |                  `* Re: Mint 21.1 Cinnamon locking upNic
             |                   `* Re: Mint 21.1 Cinnamon locking upRob H
             |                    `* Re: Mint 21.1 Cinnamon locking upNic
             |                     `* Re: Mint 21.1 Cinnamon locking upRob H
             |                      `* Re: Mint 21.1 Cinnamon locking upNic
             |                       `* Re: Mint 21.1 Cinnamon locking upRob H
             |                        `* Re: Mint 21.1 Cinnamon locking upNic
             |                         `* Re: Mint 21.1 Cinnamon locking upRob H
             |                          `* Re: Mint 21.1 Cinnamon locking upNic
             |                           `- Re: Mint 21.1 Cinnamon locking upRob H
             `* Re: Mint 21.1 Cinnamon locking upRob H
              `* Re: Mint 21.1 Cinnamon locking upRob H
               `* Re: Mint 21.1 Cinnamon locking upNic
                `* Re: Mint 21.1 Cinnamon locking upRob H
                 `* Re: Mint 21.1 Cinnamon locking upRob H
                  `* Re: Mint 21.1 Cinnamon locking upPaul
                   `* Re: Mint 21.1 Cinnamon locking upRob H
                    `- Re: Mint 21.1 Cinnamon locking upJack

Pages:123
Re: Mint 21.1 Cinnamon locking up

<u966tf$1luj3$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6462&group=alt.os.linux.mint#6462

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nos...@needed.invalid (Paul)
Newsgroups: alt.os.linux.mint
Subject: Re: Mint 21.1 Cinnamon locking up
Date: Tue, 18 Jul 2023 10:17:19 -0400
Organization: A noiseless patient Spider
Lines: 102
Message-ID: <u966tf$1luj3$1@dont-email.me>
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 18 Jul 2023 14:17:19 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="7c4bdd048ba6bf2c6a98ac83097c7098";
logging-data="1768035"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18BYfzaXA+6u9QJk4gNjg7mITOf2f8Owfw="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
Cancel-Lock: sha1:9LwMGiFeP4eWTsOLuhOSKp32pm4=
Content-Language: en-US
In-Reply-To: <u95uo1$1kmq0$1@dont-email.me>
 by: Paul - Tue, 18 Jul 2023 14:17 UTC

On 7/18/2023 7:57 AM, Rob H wrote:
> On 18/07/2023 10:09, Paul wrote:
>> On 7/18/2023 3:07 AM, Rob H wrote:
>>> On 18/07/2023 03:48, Paul wrote:
>>>> On 7/17/2023 5:26 PM, Rob H wrote:
>>>>> On 17/07/2023 22:17, Big Al wrote:
>>>>>> On 7/17/23 14:02, this is what Rob H wrote:
>>>>>>> On 16/07/2023 23:07, Rob H wrote:
>>>>>>>> On 16/07/2023 21:04, Nic wrote:
>>>>>>>>> On 7/16/23 3:51 PM, Rob H wrote:
>>>>>>>>>> On 16/07/2023 20:48, Nic wrote:
>>>>>>>>>>> On 7/16/23 3:41 PM, Rob H wrote:
>>>>>>>>>>>> On 16/07/2023 20:26, Nic wrote:
>>>>>>>>>>>>> On 7/16/23 7:24 AM, Rob H wrote:
>>>>>>>>>>>>>> These last few weeks I have found that every now and again, becoming more frequent now, my Mint system seems to freeze, or at least my wired mouse does.
>>>>>>>>>>>>>> Sometimes if I leave it for a an hour or so,the mouse becomes usable again, but this is not always convenient, and I have to hard reboot the system.
>>>>>>>>>>>>>> If it helps , the mouse is a Kensigton wired mouse. I have tried unplugging and plugging back in, and also using a different usb port, but neither made any difference.
>>>>>>>>>>>>>> I've had this same mouse for a long time now, maybe 7/8 years, and would it be time to get a new one, if it would make any difference.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> thanks
>>>>>>>>>>>>> Is there some system log file that might say what is occurring? Do a search for the the most recent .log file after the hard reboot.
>>>>>>>>>>>>
>>>>>>>>>>>> This is all I could find in the hardware section of logs:
>>>>>>>>>>>>
>>>>>>>>>>>> time: 12:05:17
>>>>>>>>>>>> Message: hid-generic 0003:1BCF:08A0.0001: input,hiddev0,hidraw0: USB HID    v1.10 Mouse [HID 1bcf:08a0] on usb-0000:00:14.0-5/input0
>>>>>>>>>>>>
>>>>>>>>>>>> Kernel Device: +hid:0003:1BCF:08A0.0001
>>>>>>>>>>>>
>>>>>>>>>>>> Priority: 6
>>>>>>>>>>> It looks like it is going to sleep. I thought you said you were using a wired mouse, this message has to do with a usb device.
>>>>>>>>>>
>>>>>>>>>> I am using a wired mouse which is plugged into a USB port on the motherboard of my desktop machine
>>>>>>>>> So the message suggests to me the mouse is hibernating.
>>>>>>>>
>>>>>>>> Well that is weird as I've never known that before, but why would it.
>>>>>>>> Also, as I don't know how long I'd have to wait before it does respond to movement, it becomes a bit inconvenient.
>>>>>>>
>>>>>>> Well the replacement mouse has also locked up, and the keyboard didn't work either, o it must be something else which i causing it to happen.
>>>>>>>
>>>>>>> Time:    18:56:37
>>>>>>> Message:hid-generic 0003:04F2:0939.0003: input,hidraw0: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-0000:00:14.0-6/input0
>>>>>>> kernel Device : +hid:0003:04F2:0939.0003
>>>>>>> Priority 6
>>>>>>>
>>>>>> Looks like the 's' key is intermittently not working too.
>>>>>
>>>>> Hardware etc information:
>>>>> rob@rob-Z97:~$ inxi -Fxxxrz
>>>>> System:
>>>>>     Kernel: 5.15.0-76-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
>>>>>       Desktop: Cinnamon 5.6.8 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0
>>>>>       Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
>>>>
>>>> If you have the boot menu set up, and you haven't been purging all
>>>> the old kernels, you can temporarily revert back to a previous
>>>> kernel and test your USB ports again.
>>>>
>>>>      [Picture]
>>>>
>>>>       https://i.postimg.cc/Tw3nfFsh/select-an-old-kernel-and-retest.gif
>>>>
>>>>     Paul
>>>
>>> Thanks Paul.
>>> I can't help thinking that the problem is being caused by a latest? update , ie a later version kernel.
>>> I have installed installed kernel version 5.19.0-41 from Update Manager/Linux Kernels.
>>>
>>> I don't know, so I will ask, does that mean that the system will always boot or use the said kernel version, or do I have to do something else as well.
>>
>> When no menu is present during the boot sequence, it
>> should follow the default (single OS offering) line, and
>> not the Advanced Option items.
>>
>> If you set up the Menu, then if you respond in time, you can
>> take control. If you instead, relax and just let it boot,
>> it chooses the Default line.
>>
>> Setting up the Menu, is part of preparing for broken-ness.
>> And this is especially the case, if you are accelerating the
>> kernel choices and choosing whizzy ones.
>>
>> This is why I'm recommending this step, as you can "join us
>> poor folk" with our old-kernels and see if your USB device
>> works better. I've partaken of whizzy kernels before, without
>> too much impact except for DKMS stuff no longer working.
>> (When stuff is added via DKMS, there is a kernel range
>> set of numbers and if your new kernel is outside the
>> DKMS item defined range, then the DKMS item cannot be applied.
>> Maybe this would include an NVidia driver, VirtualBox Additions,
>> and so on.)
>>
>>     Paul
>
> Thanks, but how do I setup the menu as I've never used one before.

There is a depiction of what to do, in the picture I posted.

https://i.postimg.cc/Tw3nfFsh/select-an-old-kernel-and-retest.gif

Paul

Re: Mint 21.1 Cinnamon locking up

<u9672t$1lvng$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6463&group=alt.os.linux.mint#6463

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: rob...@despammer.com (Rob H)
Newsgroups: alt.os.linux.mint
Subject: Re: Mint 21.1 Cinnamon locking up
Date: Tue, 18 Jul 2023 15:20:13 +0100
Organization: A noiseless patient Spider
Lines: 127
Message-ID: <u9672t$1lvng$1@dont-email.me>
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 18 Jul 2023 14:20:14 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="5e222208ef964d50bd5fe7adeb7fc943";
logging-data="1769200"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19ajpu6QgplxCI8nNbHnbnc"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.13.0
Cancel-Lock: sha1:eMlKVGULefOE1+O86AVEMo5QguM=
In-Reply-To: <u95uo1$1kmq0$1@dont-email.me>
Content-Language: en-US
 by: Rob H - Tue, 18 Jul 2023 14:20 UTC

On 18/07/2023 12:57, Rob H wrote:
> On 18/07/2023 10:09, Paul wrote:
>> On 7/18/2023 3:07 AM, Rob H wrote:
>>> On 18/07/2023 03:48, Paul wrote:
>>>> On 7/17/2023 5:26 PM, Rob H wrote:
>>>>> On 17/07/2023 22:17, Big Al wrote:
>>>>>> On 7/17/23 14:02, this is what Rob H wrote:
>>>>>>> On 16/07/2023 23:07, Rob H wrote:
>>>>>>>> On 16/07/2023 21:04, Nic wrote:
>>>>>>>>> On 7/16/23 3:51 PM, Rob H wrote:
>>>>>>>>>> On 16/07/2023 20:48, Nic wrote:
>>>>>>>>>>> On 7/16/23 3:41 PM, Rob H wrote:
>>>>>>>>>>>> On 16/07/2023 20:26, Nic wrote:
>>>>>>>>>>>>> On 7/16/23 7:24 AM, Rob H wrote:
>>>>>>>>>>>>>> These last few weeks I have found that every now and
>>>>>>>>>>>>>> again, becoming more frequent now, my Mint system seems to
>>>>>>>>>>>>>> freeze, or at least my wired mouse does.
>>>>>>>>>>>>>> Sometimes if I leave it for a an hour or so,the mouse
>>>>>>>>>>>>>> becomes usable again, but this is not always convenient,
>>>>>>>>>>>>>> and I have to hard reboot the system.
>>>>>>>>>>>>>> If it helps , the mouse is a Kensigton wired mouse. I have
>>>>>>>>>>>>>> tried unplugging and plugging back in, and also using a
>>>>>>>>>>>>>> different usb port, but neither made any difference.
>>>>>>>>>>>>>> I've had this same mouse for a long time now, maybe 7/8
>>>>>>>>>>>>>> years, and would it be time to get a new one, if it would
>>>>>>>>>>>>>> make any difference.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> thanks
>>>>>>>>>>>>> Is there some system log file that might say what is
>>>>>>>>>>>>> occurring? Do a search for the the most recent .log file
>>>>>>>>>>>>> after the hard reboot.
>>>>>>>>>>>>
>>>>>>>>>>>> This is all I could find in the hardware section of logs:
>>>>>>>>>>>>
>>>>>>>>>>>> time: 12:05:17
>>>>>>>>>>>> Message: hid-generic 0003:1BCF:08A0.0001:
>>>>>>>>>>>> input,hiddev0,hidraw0: USB HID    v1.10 Mouse [HID
>>>>>>>>>>>> 1bcf:08a0] on usb-0000:00:14.0-5/input0
>>>>>>>>>>>>
>>>>>>>>>>>> Kernel Device: +hid:0003:1BCF:08A0.0001
>>>>>>>>>>>>
>>>>>>>>>>>> Priority: 6
>>>>>>>>>>> It looks like it is going to sleep. I thought you said you
>>>>>>>>>>> were using a wired mouse, this message has to do with a usb
>>>>>>>>>>> device.
>>>>>>>>>>
>>>>>>>>>> I am using a wired mouse which is plugged into a USB port on
>>>>>>>>>> the motherboard of my desktop machine
>>>>>>>>> So the message suggests to me the mouse is hibernating.
>>>>>>>>
>>>>>>>> Well that is weird as I've never known that before, but why
>>>>>>>> would it.
>>>>>>>> Also, as I don't know how long I'd have to wait before it does
>>>>>>>> respond to movement, it becomes a bit inconvenient.
>>>>>>>
>>>>>>> Well the replacement mouse has also locked up, and the keyboard
>>>>>>> didn't work either, o it must be something else which i causing
>>>>>>> it to happen.
>>>>>>>
>>>>>>> Time:    18:56:37
>>>>>>> Message:hid-generic 0003:04F2:0939.0003: input,hidraw0: USB HID
>>>>>>> v1.11 Mouse [PixArt USB Optical Mouse] on usb-0000:00:14.0-6/input0
>>>>>>> kernel Device : +hid:0003:04F2:0939.0003
>>>>>>> Priority 6
>>>>>>>
>>>>>> Looks like the 's' key is intermittently not working too.
>>>>>
>>>>> Hardware etc information:
>>>>> rob@rob-Z97:~$ inxi -Fxxxrz
>>>>> System:
>>>>>     Kernel: 5.15.0-76-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
>>>>>       Desktop: Cinnamon 5.6.8 tk: GTK 3.24.33 wm: muffin vt: 7 dm:
>>>>> LightDM 1.30.0
>>>>>       Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
>>>>
>>>> If you have the boot menu set up, and you haven't been purging all
>>>> the old kernels, you can temporarily revert back to a previous
>>>> kernel and test your USB ports again.
>>>>
>>>>      [Picture]
>>>>
>>>>       https://i.postimg.cc/Tw3nfFsh/select-an-old-kernel-and-retest.gif
>>>>
>>>>     Paul
>>>
>>> Thanks Paul.
>>> I can't help thinking that the problem is being caused by a latest?
>>> update , ie a later version kernel.
>>> I have installed installed kernel version 5.19.0-41 from Update
>>> Manager/Linux Kernels.
>>>
>>> I don't know, so I will ask, does that mean that the system will
>>> always boot or use the said kernel version, or do I have to do
>>> something else as well.
>>
>> When no menu is present during the boot sequence, it
>> should follow the default (single OS offering) line, and
>> not the Advanced Option items.
>>
>> If you set up the Menu, then if you respond in time, you can
>> take control. If you instead, relax and just let it boot,
>> it chooses the Default line.
>>
>> Setting up the Menu, is part of preparing for broken-ness.
>> And this is especially the case, if you are accelerating the
>> kernel choices and choosing whizzy ones.
>>
>> This is why I'm recommending this step, as you can "join us
>> poor folk" with our old-kernels and see if your USB device
>> works better. I've partaken of whizzy kernels before, without
>> too much impact except for DKMS stuff no longer working.
>> (When stuff is added via DKMS, there is a kernel range
>> set of numbers and if your new kernel is outside the
>> DKMS item defined range, then the DKMS item cannot be applied.
>> Maybe this would include an NVidia driver, VirtualBox Additions,
>> and so on.)
>>
>>     Paul
>
> Thanks, but how do I setup the menu as I've never used one before.

I googled how to do and found I had to edit grub.cfg timout from 0 to 5
Then the boot menu appeared and in Advanced options the kernel version
which I installed earlier was at the top of the list and booted from or
to it.
If the system still locks up, then I will have to install an earlier
version kernel, but we'll see how it goes

Re: Mint 21.1 Cinnamon locking up

<u9675h$1m111$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6464&group=alt.os.linux.mint#6464

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nos...@needed.invalid (Paul)
Newsgroups: alt.os.linux.mint
Subject: Re: Mint 21.1 Cinnamon locking up
Date: Tue, 18 Jul 2023 10:21:37 -0400
Organization: A noiseless patient Spider
Lines: 110
Message-ID: <u9675h$1m111$1@dont-email.me>
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
<u966tf$1luj3$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 18 Jul 2023 14:21:37 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="7c4bdd048ba6bf2c6a98ac83097c7098";
logging-data="1770529"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX182BomU/QC2jHLHd2YaYMNBkKMlS0Ehfxs="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
Cancel-Lock: sha1:J7RRGbLj4GqaVDPnaig0reBMGGM=
In-Reply-To: <u966tf$1luj3$1@dont-email.me>
Content-Language: en-US
 by: Paul - Tue, 18 Jul 2023 14:21 UTC

On 7/18/2023 10:17 AM, Paul wrote:
> On 7/18/2023 7:57 AM, Rob H wrote:
>> On 18/07/2023 10:09, Paul wrote:
>>> On 7/18/2023 3:07 AM, Rob H wrote:
>>>> On 18/07/2023 03:48, Paul wrote:
>>>>> On 7/17/2023 5:26 PM, Rob H wrote:
>>>>>> On 17/07/2023 22:17, Big Al wrote:
>>>>>>> On 7/17/23 14:02, this is what Rob H wrote:
>>>>>>>> On 16/07/2023 23:07, Rob H wrote:
>>>>>>>>> On 16/07/2023 21:04, Nic wrote:
>>>>>>>>>> On 7/16/23 3:51 PM, Rob H wrote:
>>>>>>>>>>> On 16/07/2023 20:48, Nic wrote:
>>>>>>>>>>>> On 7/16/23 3:41 PM, Rob H wrote:
>>>>>>>>>>>>> On 16/07/2023 20:26, Nic wrote:
>>>>>>>>>>>>>> On 7/16/23 7:24 AM, Rob H wrote:
>>>>>>>>>>>>>>> These last few weeks I have found that every now and again, becoming more frequent now, my Mint system seems to freeze, or at least my wired mouse does.
>>>>>>>>>>>>>>> Sometimes if I leave it for a an hour or so,the mouse becomes usable again, but this is not always convenient, and I have to hard reboot the system.
>>>>>>>>>>>>>>> If it helps , the mouse is a Kensigton wired mouse. I have tried unplugging and plugging back in, and also using a different usb port, but neither made any difference.
>>>>>>>>>>>>>>> I've had this same mouse for a long time now, maybe 7/8 years, and would it be time to get a new one, if it would make any difference.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> thanks
>>>>>>>>>>>>>> Is there some system log file that might say what is occurring? Do a search for the the most recent .log file after the hard reboot.
>>>>>>>>>>>>>
>>>>>>>>>>>>> This is all I could find in the hardware section of logs:
>>>>>>>>>>>>>
>>>>>>>>>>>>> time: 12:05:17
>>>>>>>>>>>>> Message: hid-generic 0003:1BCF:08A0.0001: input,hiddev0,hidraw0: USB HID    v1.10 Mouse [HID 1bcf:08a0] on usb-0000:00:14.0-5/input0
>>>>>>>>>>>>>
>>>>>>>>>>>>> Kernel Device: +hid:0003:1BCF:08A0.0001
>>>>>>>>>>>>>
>>>>>>>>>>>>> Priority: 6
>>>>>>>>>>>> It looks like it is going to sleep. I thought you said you were using a wired mouse, this message has to do with a usb device.
>>>>>>>>>>>
>>>>>>>>>>> I am using a wired mouse which is plugged into a USB port on the motherboard of my desktop machine
>>>>>>>>>> So the message suggests to me the mouse is hibernating.
>>>>>>>>>
>>>>>>>>> Well that is weird as I've never known that before, but why would it.
>>>>>>>>> Also, as I don't know how long I'd have to wait before it does respond to movement, it becomes a bit inconvenient.
>>>>>>>>
>>>>>>>> Well the replacement mouse has also locked up, and the keyboard didn't work either, o it must be something else which i causing it to happen.
>>>>>>>>
>>>>>>>> Time:    18:56:37
>>>>>>>> Message:hid-generic 0003:04F2:0939.0003: input,hidraw0: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-0000:00:14.0-6/input0
>>>>>>>> kernel Device : +hid:0003:04F2:0939.0003
>>>>>>>> Priority 6
>>>>>>>>
>>>>>>> Looks like the 's' key is intermittently not working too.
>>>>>>
>>>>>> Hardware etc information:
>>>>>> rob@rob-Z97:~$ inxi -Fxxxrz
>>>>>> System:
>>>>>>     Kernel: 5.15.0-76-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
>>>>>>       Desktop: Cinnamon 5.6.8 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0
>>>>>>       Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
>>>>>
>>>>> If you have the boot menu set up, and you haven't been purging all
>>>>> the old kernels, you can temporarily revert back to a previous
>>>>> kernel and test your USB ports again.
>>>>>
>>>>>      [Picture]
>>>>>
>>>>>       https://i.postimg.cc/Tw3nfFsh/select-an-old-kernel-and-retest.gif
>>>>>
>>>>>     Paul
>>>>
>>>> Thanks Paul.
>>>> I can't help thinking that the problem is being caused by a latest? update , ie a later version kernel.
>>>> I have installed installed kernel version 5.19.0-41 from Update Manager/Linux Kernels.
>>>>
>>>> I don't know, so I will ask, does that mean that the system will always boot or use the said kernel version, or do I have to do something else as well.
>>>
>>> When no menu is present during the boot sequence, it
>>> should follow the default (single OS offering) line, and
>>> not the Advanced Option items.
>>>
>>> If you set up the Menu, then if you respond in time, you can
>>> take control. If you instead, relax and just let it boot,
>>> it chooses the Default line.
>>>
>>> Setting up the Menu, is part of preparing for broken-ness.
>>> And this is especially the case, if you are accelerating the
>>> kernel choices and choosing whizzy ones.
>>>
>>> This is why I'm recommending this step, as you can "join us
>>> poor folk" with our old-kernels and see if your USB device
>>> works better. I've partaken of whizzy kernels before, without
>>> too much impact except for DKMS stuff no longer working.
>>> (When stuff is added via DKMS, there is a kernel range
>>> set of numbers and if your new kernel is outside the
>>> DKMS item defined range, then the DKMS item cannot be applied.
>>> Maybe this would include an NVidia driver, VirtualBox Additions,
>>> and so on.)
>>>
>>>     Paul
>>
>> Thanks, but how do I setup the menu as I've never used one before.
>
> There is a depiction of what to do, in the picture I posted.
>
> https://i.postimg.cc/Tw3nfFsh/select-an-old-kernel-and-retest.gif
>
> Paul
>

You edit the grub file, then do an "update-grub" to rebuild the menu.

sudo xed /etc/default/grub
sudo update-grub

Paul

Re: Mint 21.1 Cinnamon locking up

<u968mi$1m82i$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6466&group=alt.os.linux.mint#6466

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: rob...@despammer.com (Rob H)
Newsgroups: alt.os.linux.mint
Subject: Re: Mint 21.1 Cinnamon locking up
Date: Tue, 18 Jul 2023 15:47:46 +0100
Organization: A noiseless patient Spider
Lines: 4
Message-ID: <u968mi$1m82i$1@dont-email.me>
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
<u966tf$1luj3$1@dont-email.me> <u9675h$1m111$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 18 Jul 2023 14:47:46 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="5e222208ef964d50bd5fe7adeb7fc943";
logging-data="1777746"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1988AQ5BCtk6VlhV5KRudc9"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.13.0
Cancel-Lock: sha1:6zMYZPFcccgS1i3NLqHeGC43OPk=
Content-Language: en-US
In-Reply-To: <u9675h$1m111$1@dont-email.me>
 by: Rob H - Tue, 18 Jul 2023 14:47 UTC

On 18/07/2023 15:21, Paul wrote:
> sudo update-grub

Thanks, yes I did that before I rebooted.

Re: Mint 21.1 Cinnamon locking up

<u98mbi$258vu$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6482&group=alt.os.linux.mint#6482

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: rob...@despammer.com (Rob H)
Newsgroups: alt.os.linux.mint
Subject: Re: Mint 21.1 Cinnamon locking up
Date: Wed, 19 Jul 2023 13:53:06 +0100
Organization: A noiseless patient Spider
Lines: 136
Message-ID: <u98mbi$258vu$1@dont-email.me>
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
<u9672t$1lvng$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 19 Jul 2023 12:53:06 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="af8879955588181a5bd64fd2c7a14d31";
logging-data="2270206"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/nrQPDuYf1eGoXhsNjFy/1"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.13.0
Cancel-Lock: sha1:WioRa5JJEFuzi/Cb0U7HdeDXr9U=
In-Reply-To: <u9672t$1lvng$1@dont-email.me>
Content-Language: en-US
 by: Rob H - Wed, 19 Jul 2023 12:53 UTC

On 18/07/2023 15:20, Rob H wrote:
> On 18/07/2023 12:57, Rob H wrote:
>> On 18/07/2023 10:09, Paul wrote:
>>> On 7/18/2023 3:07 AM, Rob H wrote:
>>>> On 18/07/2023 03:48, Paul wrote:
>>>>> On 7/17/2023 5:26 PM, Rob H wrote:
>>>>>> On 17/07/2023 22:17, Big Al wrote:
>>>>>>> On 7/17/23 14:02, this is what Rob H wrote:
>>>>>>>> On 16/07/2023 23:07, Rob H wrote:
>>>>>>>>> On 16/07/2023 21:04, Nic wrote:
>>>>>>>>>> On 7/16/23 3:51 PM, Rob H wrote:
>>>>>>>>>>> On 16/07/2023 20:48, Nic wrote:
>>>>>>>>>>>> On 7/16/23 3:41 PM, Rob H wrote:
>>>>>>>>>>>>> On 16/07/2023 20:26, Nic wrote:
>>>>>>>>>>>>>> On 7/16/23 7:24 AM, Rob H wrote:
>>>>>>>>>>>>>>> These last few weeks I have found that every now and
>>>>>>>>>>>>>>> again, becoming more frequent now, my Mint system seems
>>>>>>>>>>>>>>> to freeze, or at least my wired mouse does.
>>>>>>>>>>>>>>> Sometimes if I leave it for a an hour or so,the mouse
>>>>>>>>>>>>>>> becomes usable again, but this is not always convenient,
>>>>>>>>>>>>>>> and I have to hard reboot the system.
>>>>>>>>>>>>>>> If it helps , the mouse is a Kensigton wired mouse. I
>>>>>>>>>>>>>>> have tried unplugging and plugging back in, and also
>>>>>>>>>>>>>>> using a different usb port, but neither made any difference.
>>>>>>>>>>>>>>> I've had this same mouse for a long time now, maybe 7/8
>>>>>>>>>>>>>>> years, and would it be time to get a new one, if it would
>>>>>>>>>>>>>>> make any difference.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> thanks
>>>>>>>>>>>>>> Is there some system log file that might say what is
>>>>>>>>>>>>>> occurring? Do a search for the the most recent .log file
>>>>>>>>>>>>>> after the hard reboot.
>>>>>>>>>>>>>
>>>>>>>>>>>>> This is all I could find in the hardware section of logs:
>>>>>>>>>>>>>
>>>>>>>>>>>>> time: 12:05:17
>>>>>>>>>>>>> Message: hid-generic 0003:1BCF:08A0.0001:
>>>>>>>>>>>>> input,hiddev0,hidraw0: USB HID    v1.10 Mouse [HID
>>>>>>>>>>>>> 1bcf:08a0] on usb-0000:00:14.0-5/input0
>>>>>>>>>>>>>
>>>>>>>>>>>>> Kernel Device: +hid:0003:1BCF:08A0.0001
>>>>>>>>>>>>>
>>>>>>>>>>>>> Priority: 6
>>>>>>>>>>>> It looks like it is going to sleep. I thought you said you
>>>>>>>>>>>> were using a wired mouse, this message has to do with a usb
>>>>>>>>>>>> device.
>>>>>>>>>>>
>>>>>>>>>>> I am using a wired mouse which is plugged into a USB port on
>>>>>>>>>>> the motherboard of my desktop machine
>>>>>>>>>> So the message suggests to me the mouse is hibernating.
>>>>>>>>>
>>>>>>>>> Well that is weird as I've never known that before, but why
>>>>>>>>> would it.
>>>>>>>>> Also, as I don't know how long I'd have to wait before it does
>>>>>>>>> respond to movement, it becomes a bit inconvenient.
>>>>>>>>
>>>>>>>> Well the replacement mouse has also locked up, and the keyboard
>>>>>>>> didn't work either, o it must be something else which i causing
>>>>>>>> it to happen.
>>>>>>>>
>>>>>>>> Time:    18:56:37
>>>>>>>> Message:hid-generic 0003:04F2:0939.0003: input,hidraw0: USB HID
>>>>>>>> v1.11 Mouse [PixArt USB Optical Mouse] on usb-0000:00:14.0-6/input0
>>>>>>>> kernel Device : +hid:0003:04F2:0939.0003
>>>>>>>> Priority 6
>>>>>>>>
>>>>>>> Looks like the 's' key is intermittently not working too.
>>>>>>
>>>>>> Hardware etc information:
>>>>>> rob@rob-Z97:~$ inxi -Fxxxrz
>>>>>> System:
>>>>>>     Kernel: 5.15.0-76-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
>>>>>>       Desktop: Cinnamon 5.6.8 tk: GTK 3.24.33 wm: muffin vt: 7 dm:
>>>>>> LightDM 1.30.0
>>>>>>       Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
>>>>>
>>>>> If you have the boot menu set up, and you haven't been purging all
>>>>> the old kernels, you can temporarily revert back to a previous
>>>>> kernel and test your USB ports again.
>>>>>
>>>>>      [Picture]
>>>>>
>>>>>
>>>>> https://i.postimg.cc/Tw3nfFsh/select-an-old-kernel-and-retest.gif
>>>>>
>>>>>     Paul
>>>>
>>>> Thanks Paul.
>>>> I can't help thinking that the problem is being caused by a latest?
>>>> update , ie a later version kernel.
>>>> I have installed installed kernel version 5.19.0-41 from Update
>>>> Manager/Linux Kernels.
>>>>
>>>> I don't know, so I will ask, does that mean that the system will
>>>> always boot or use the said kernel version, or do I have to do
>>>> something else as well.
>>>
>>> When no menu is present during the boot sequence, it
>>> should follow the default (single OS offering) line, and
>>> not the Advanced Option items.
>>>
>>> If you set up the Menu, then if you respond in time, you can
>>> take control. If you instead, relax and just let it boot,
>>> it chooses the Default line.
>>>
>>> Setting up the Menu, is part of preparing for broken-ness.
>>> And this is especially the case, if you are accelerating the
>>> kernel choices and choosing whizzy ones.
>>>
>>> This is why I'm recommending this step, as you can "join us
>>> poor folk" with our old-kernels and see if your USB device
>>> works better. I've partaken of whizzy kernels before, without
>>> too much impact except for DKMS stuff no longer working.
>>> (When stuff is added via DKMS, there is a kernel range
>>> set of numbers and if your new kernel is outside the
>>> DKMS item defined range, then the DKMS item cannot be applied.
>>> Maybe this would include an NVidia driver, VirtualBox Additions,
>>> and so on.)
>>>
>>>     Paul
>>
>> Thanks, but how do I setup the menu as I've never used one before.
>
> I googled how to do and found I had to edit grub.cfg timout from 0 to 5
> Then the boot menu appeared and in Advanced options the kernel version
> which I installed earlier was at the top of the list and booted from or
> to it.
> If the system still locks up, then I will have to install an earlier
> version kernel, but we'll see how it goes

Well that didn't last very long before it locked up again.
After my system was not used for 3 hours or so, I went to check emails
and then it locked up again after less than 5 minutes.
This resulted in yet another hard restart.

I don't know what else to do now.

Re: Mint 21.1 Cinnamon locking up

<DbRtM.26628$AsA.4162@fx18.iad>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6483&group=alt.os.linux.mint#6483

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx18.iad.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.13.0
Reply-To: Nic@none.net
Subject: Re: Mint 21.1 Cinnamon locking up
Content-Language: en-US
Newsgroups: alt.os.linux.mint
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
<u9672t$1lvng$1@dont-email.me> <u98mbi$258vu$1@dont-email.me>
From: Nic...@none.net (Nic)
Organization: Arm Chair Observer
In-Reply-To: <u98mbi$258vu$1@dont-email.me>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Lines: 145
Message-ID: <DbRtM.26628$AsA.4162@fx18.iad>
X-Complaints-To: abuse(at)newshosting.com
NNTP-Posting-Date: Wed, 19 Jul 2023 13:04:35 UTC
Date: Wed, 19 Jul 2023 09:04:34 -0400
X-Received-Bytes: 7940
 by: Nic - Wed, 19 Jul 2023 13:04 UTC

On 7/19/23 8:53 AM, Rob H wrote:
> On 18/07/2023 15:20, Rob H wrote:
>> On 18/07/2023 12:57, Rob H wrote:
>>> On 18/07/2023 10:09, Paul wrote:
>>>> On 7/18/2023 3:07 AM, Rob H wrote:
>>>>> On 18/07/2023 03:48, Paul wrote:
>>>>>> On 7/17/2023 5:26 PM, Rob H wrote:
>>>>>>> On 17/07/2023 22:17, Big Al wrote:
>>>>>>>> On 7/17/23 14:02, this is what Rob H wrote:
>>>>>>>>> On 16/07/2023 23:07, Rob H wrote:
>>>>>>>>>> On 16/07/2023 21:04, Nic wrote:
>>>>>>>>>>> On 7/16/23 3:51 PM, Rob H wrote:
>>>>>>>>>>>> On 16/07/2023 20:48, Nic wrote:
>>>>>>>>>>>>> On 7/16/23 3:41 PM, Rob H wrote:
>>>>>>>>>>>>>> On 16/07/2023 20:26, Nic wrote:
>>>>>>>>>>>>>>> On 7/16/23 7:24 AM, Rob H wrote:
>>>>>>>>>>>>>>>> These last few weeks I have found that every now and
>>>>>>>>>>>>>>>> again, becoming more frequent now, my Mint system seems
>>>>>>>>>>>>>>>> to freeze, or at least my wired mouse does.
>>>>>>>>>>>>>>>> Sometimes if I leave it for a an hour or so,the mouse
>>>>>>>>>>>>>>>> becomes usable again, but this is not always
>>>>>>>>>>>>>>>> convenient, and I have to hard reboot the system.
>>>>>>>>>>>>>>>> If it helps , the mouse is a Kensigton wired mouse. I
>>>>>>>>>>>>>>>> have tried unplugging and plugging back in, and also
>>>>>>>>>>>>>>>> using a different usb port, but neither made any
>>>>>>>>>>>>>>>> difference.
>>>>>>>>>>>>>>>> I've had this same mouse for a long time now, maybe 7/8
>>>>>>>>>>>>>>>> years, and would it be time to get a new one, if it
>>>>>>>>>>>>>>>> would make any difference.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> thanks
>>>>>>>>>>>>>>> Is there some system log file that might say what is
>>>>>>>>>>>>>>> occurring? Do a search for the the most recent .log file
>>>>>>>>>>>>>>> after the hard reboot.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> This is all I could find in the hardware section of logs:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> time: 12:05:17
>>>>>>>>>>>>>> Message: hid-generic 0003:1BCF:08A0.0001:
>>>>>>>>>>>>>> input,hiddev0,hidraw0: USB HID    v1.10 Mouse [HID
>>>>>>>>>>>>>> 1bcf:08a0] on usb-0000:00:14.0-5/input0
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Kernel Device: +hid:0003:1BCF:08A0.0001
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Priority: 6
>>>>>>>>>>>>> It looks like it is going to sleep. I thought you said you
>>>>>>>>>>>>> were using a wired mouse, this message has to do with a
>>>>>>>>>>>>> usb device.
>>>>>>>>>>>>
>>>>>>>>>>>> I am using a wired mouse which is plugged into a USB port
>>>>>>>>>>>> on the motherboard of my desktop machine
>>>>>>>>>>> So the message suggests to me the mouse is hibernating.
>>>>>>>>>>
>>>>>>>>>> Well that is weird as I've never known that before, but why
>>>>>>>>>> would it.
>>>>>>>>>> Also, as I don't know how long I'd have to wait before it
>>>>>>>>>> does respond to movement, it becomes a bit inconvenient.
>>>>>>>>>
>>>>>>>>> Well the replacement mouse has also locked up, and the
>>>>>>>>> keyboard didn't work either, o it must be something else which
>>>>>>>>> i causing it to happen.
>>>>>>>>>
>>>>>>>>> Time:    18:56:37
>>>>>>>>> Message:hid-generic 0003:04F2:0939.0003: input,hidraw0: USB
>>>>>>>>> HID v1.11 Mouse [PixArt USB Optical Mouse] on
>>>>>>>>> usb-0000:00:14.0-6/input0
>>>>>>>>> kernel Device : +hid:0003:04F2:0939.0003
>>>>>>>>> Priority 6
>>>>>>>>>
>>>>>>>> Looks like the 's' key is intermittently not working too.
>>>>>>>
>>>>>>> Hardware etc information:
>>>>>>> rob@rob-Z97:~$ inxi -Fxxxrz
>>>>>>> System:
>>>>>>>     Kernel: 5.15.0-76-generic x86_64 bits: 64 compiler: gcc v:
>>>>>>> 11.3.0
>>>>>>>       Desktop: Cinnamon 5.6.8 tk: GTK 3.24.33 wm: muffin vt: 7
>>>>>>> dm: LightDM 1.30.0
>>>>>>>       Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
>>>>>>
>>>>>> If you have the boot menu set up, and you haven't been purging all
>>>>>> the old kernels, you can temporarily revert back to a previous
>>>>>> kernel and test your USB ports again.
>>>>>>
>>>>>>      [Picture]
>>>>>>
>>>>>> https://i.postimg.cc/Tw3nfFsh/select-an-old-kernel-and-retest.gif
>>>>>>
>>>>>>     Paul
>>>>>
>>>>> Thanks Paul.
>>>>> I can't help thinking that the problem is being caused by a
>>>>> latest? update , ie a later version kernel.
>>>>> I have installed installed kernel version 5.19.0-41 from Update
>>>>> Manager/Linux Kernels.
>>>>>
>>>>> I don't know, so I will ask, does that mean that the system will
>>>>> always boot or use the said kernel version, or do I have to do
>>>>> something else as well.
>>>>
>>>> When no menu is present during the boot sequence, it
>>>> should follow the default (single OS offering) line, and
>>>> not the Advanced Option items.
>>>>
>>>> If you set up the Menu, then if you respond in time, you can
>>>> take control. If you instead, relax and just let it boot,
>>>> it chooses the Default line.
>>>>
>>>> Setting up the Menu, is part of preparing for broken-ness.
>>>> And this is especially the case, if you are accelerating the
>>>> kernel choices and choosing whizzy ones.
>>>>
>>>> This is why I'm recommending this step, as you can "join us
>>>> poor folk" with our old-kernels and see if your USB device
>>>> works better. I've partaken of whizzy kernels before, without
>>>> too much impact except for DKMS stuff no longer working.
>>>> (When stuff is added via DKMS, there is a kernel range
>>>> set of numbers and if your new kernel is outside the
>>>> DKMS item defined range, then the DKMS item cannot be applied.
>>>> Maybe this would include an NVidia driver, VirtualBox Additions,
>>>> and so on.)
>>>>
>>>>     Paul
>>>
>>> Thanks, but how do I setup the menu as I've never used one before.
>>
>> I googled how to do and found I had to edit grub.cfg timout from 0 to 5
>> Then the boot menu appeared and in Advanced options the kernel
>> version which I installed earlier was at the top of the list and
>> booted from or to it.
>> If the system still locks up, then I will have to install an earlier
>> version kernel, but we'll see how it goes
>
> Well that didn't last very long before it locked up again.
> After my system was not used for 3 hours or so, I went to check emails
> and then it locked up again after less than 5 minutes.
> This resulted in yet another hard restart.
>
> I don't know what else to do now.
A point of curiosity for me, when the lock up happens, and your mouse /
keyboard are not available, can you tell if there are any running
process, such as a video that was playing? If the video is playing and
the audio is playing, this would force me to look at the hardware end
for the problem. Is it safe to assume that your keyboard is also plugged
into a usb port?


Click here to read the complete article
Re: Mint 21.1 Cinnamon locking up

<u98va6$26v5b$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6485&group=alt.os.linux.mint#6485

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!usenet.goja.nl.eu.org!weretis.net!feeder8.news.weretis.net!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: rob...@despammer.com (Rob H)
Newsgroups: alt.os.linux.mint
Subject: Re: Mint 21.1 Cinnamon locking up
Date: Wed, 19 Jul 2023 16:25:58 +0100
Organization: A noiseless patient Spider
Lines: 154
Message-ID: <u98va6$26v5b$1@dont-email.me>
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
<u9672t$1lvng$1@dont-email.me> <u98mbi$258vu$1@dont-email.me>
<DbRtM.26628$AsA.4162@fx18.iad>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 19 Jul 2023 15:25:58 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="af8879955588181a5bd64fd2c7a14d31";
logging-data="2325675"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18NmJTiC+DT5Cy6PUZjP3M5"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.13.0
Cancel-Lock: sha1:OhFGI2NG0m6apnuCsrs0hmVu+l4=
In-Reply-To: <DbRtM.26628$AsA.4162@fx18.iad>
Content-Language: en-US
 by: Rob H - Wed, 19 Jul 2023 15:25 UTC

On 19/07/2023 14:04, Nic wrote:
> On 7/19/23 8:53 AM, Rob H wrote:
>> On 18/07/2023 15:20, Rob H wrote:
>>> On 18/07/2023 12:57, Rob H wrote:
>>>> On 18/07/2023 10:09, Paul wrote:
>>>>> On 7/18/2023 3:07 AM, Rob H wrote:
>>>>>> On 18/07/2023 03:48, Paul wrote:
>>>>>>> On 7/17/2023 5:26 PM, Rob H wrote:
>>>>>>>> On 17/07/2023 22:17, Big Al wrote:
>>>>>>>>> On 7/17/23 14:02, this is what Rob H wrote:
>>>>>>>>>> On 16/07/2023 23:07, Rob H wrote:
>>>>>>>>>>> On 16/07/2023 21:04, Nic wrote:
>>>>>>>>>>>> On 7/16/23 3:51 PM, Rob H wrote:
>>>>>>>>>>>>> On 16/07/2023 20:48, Nic wrote:
>>>>>>>>>>>>>> On 7/16/23 3:41 PM, Rob H wrote:
>>>>>>>>>>>>>>> On 16/07/2023 20:26, Nic wrote:
>>>>>>>>>>>>>>>> On 7/16/23 7:24 AM, Rob H wrote:
>>>>>>>>>>>>>>>>> These last few weeks I have found that every now and
>>>>>>>>>>>>>>>>> again, becoming more frequent now, my Mint system seems
>>>>>>>>>>>>>>>>> to freeze, or at least my wired mouse does.
>>>>>>>>>>>>>>>>> Sometimes if I leave it for a an hour or so,the mouse
>>>>>>>>>>>>>>>>> becomes usable again, but this is not always
>>>>>>>>>>>>>>>>> convenient, and I have to hard reboot the system.
>>>>>>>>>>>>>>>>> If it helps , the mouse is a Kensigton wired mouse. I
>>>>>>>>>>>>>>>>> have tried unplugging and plugging back in, and also
>>>>>>>>>>>>>>>>> using a different usb port, but neither made any
>>>>>>>>>>>>>>>>> difference.
>>>>>>>>>>>>>>>>> I've had this same mouse for a long time now, maybe 7/8
>>>>>>>>>>>>>>>>> years, and would it be time to get a new one, if it
>>>>>>>>>>>>>>>>> would make any difference.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> thanks
>>>>>>>>>>>>>>>> Is there some system log file that might say what is
>>>>>>>>>>>>>>>> occurring? Do a search for the the most recent .log file
>>>>>>>>>>>>>>>> after the hard reboot.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> This is all I could find in the hardware section of logs:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> time: 12:05:17
>>>>>>>>>>>>>>> Message: hid-generic 0003:1BCF:08A0.0001:
>>>>>>>>>>>>>>> input,hiddev0,hidraw0: USB HID    v1.10 Mouse [HID
>>>>>>>>>>>>>>> 1bcf:08a0] on usb-0000:00:14.0-5/input0
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Kernel Device: +hid:0003:1BCF:08A0.0001
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Priority: 6
>>>>>>>>>>>>>> It looks like it is going to sleep. I thought you said you
>>>>>>>>>>>>>> were using a wired mouse, this message has to do with a
>>>>>>>>>>>>>> usb device.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I am using a wired mouse which is plugged into a USB port
>>>>>>>>>>>>> on the motherboard of my desktop machine
>>>>>>>>>>>> So the message suggests to me the mouse is hibernating.
>>>>>>>>>>>
>>>>>>>>>>> Well that is weird as I've never known that before, but why
>>>>>>>>>>> would it.
>>>>>>>>>>> Also, as I don't know how long I'd have to wait before it
>>>>>>>>>>> does respond to movement, it becomes a bit inconvenient.
>>>>>>>>>>
>>>>>>>>>> Well the replacement mouse has also locked up, and the
>>>>>>>>>> keyboard didn't work either, o it must be something else which
>>>>>>>>>> i causing it to happen.
>>>>>>>>>>
>>>>>>>>>> Time:    18:56:37
>>>>>>>>>> Message:hid-generic 0003:04F2:0939.0003: input,hidraw0: USB
>>>>>>>>>> HID v1.11 Mouse [PixArt USB Optical Mouse] on
>>>>>>>>>> usb-0000:00:14.0-6/input0
>>>>>>>>>> kernel Device : +hid:0003:04F2:0939.0003
>>>>>>>>>> Priority 6
>>>>>>>>>>
>>>>>>>>> Looks like the 's' key is intermittently not working too.
>>>>>>>>
>>>>>>>> Hardware etc information:
>>>>>>>> rob@rob-Z97:~$ inxi -Fxxxrz
>>>>>>>> System:
>>>>>>>>     Kernel: 5.15.0-76-generic x86_64 bits: 64 compiler: gcc v:
>>>>>>>> 11.3.0
>>>>>>>>       Desktop: Cinnamon 5.6.8 tk: GTK 3.24.33 wm: muffin vt: 7
>>>>>>>> dm: LightDM 1.30.0
>>>>>>>>       Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
>>>>>>>
>>>>>>> If you have the boot menu set up, and you haven't been purging all
>>>>>>> the old kernels, you can temporarily revert back to a previous
>>>>>>> kernel and test your USB ports again.
>>>>>>>
>>>>>>>      [Picture]
>>>>>>>
>>>>>>> https://i.postimg.cc/Tw3nfFsh/select-an-old-kernel-and-retest.gif
>>>>>>>
>>>>>>>     Paul
>>>>>>
>>>>>> Thanks Paul.
>>>>>> I can't help thinking that the problem is being caused by a
>>>>>> latest? update , ie a later version kernel.
>>>>>> I have installed installed kernel version 5.19.0-41 from Update
>>>>>> Manager/Linux Kernels.
>>>>>>
>>>>>> I don't know, so I will ask, does that mean that the system will
>>>>>> always boot or use the said kernel version, or do I have to do
>>>>>> something else as well.
>>>>>
>>>>> When no menu is present during the boot sequence, it
>>>>> should follow the default (single OS offering) line, and
>>>>> not the Advanced Option items.
>>>>>
>>>>> If you set up the Menu, then if you respond in time, you can
>>>>> take control. If you instead, relax and just let it boot,
>>>>> it chooses the Default line.
>>>>>
>>>>> Setting up the Menu, is part of preparing for broken-ness.
>>>>> And this is especially the case, if you are accelerating the
>>>>> kernel choices and choosing whizzy ones.
>>>>>
>>>>> This is why I'm recommending this step, as you can "join us
>>>>> poor folk" with our old-kernels and see if your USB device
>>>>> works better. I've partaken of whizzy kernels before, without
>>>>> too much impact except for DKMS stuff no longer working.
>>>>> (When stuff is added via DKMS, there is a kernel range
>>>>> set of numbers and if your new kernel is outside the
>>>>> DKMS item defined range, then the DKMS item cannot be applied.
>>>>> Maybe this would include an NVidia driver, VirtualBox Additions,
>>>>> and so on.)
>>>>>
>>>>>     Paul
>>>>
>>>> Thanks, but how do I setup the menu as I've never used one before.
>>>
>>> I googled how to do and found I had to edit grub.cfg timout from 0 to 5
>>> Then the boot menu appeared and in Advanced options the kernel
>>> version which I installed earlier was at the top of the list and
>>> booted from or to it.
>>> If the system still locks up, then I will have to install an earlier
>>> version kernel, but we'll see how it goes
>>
>> Well that didn't last very long before it locked up again.
>> After my system was not used for 3 hours or so, I went to check emails
>> and then it locked up again after less than 5 minutes.
>> This resulted in yet another hard restart.
>>
>> I don't know what else to do now.
> A point of curiosity for me, when the lock up happens, and your mouse /
> keyboard are not available, can you tell if there are any running
> process, such as a video that was playing? If the video is playing and
> the audio is playing, this would force me to look at the hardware end
> for the problem. Is it safe to assume that your keyboard is also plugged
> into a usb port?


Click here to read the complete article
Re: Mint 21.1 Cinnamon locking up

<u99e4k$29lq6$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6489&group=alt.os.linux.mint#6489

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: rob...@despammer.com (Rob H)
Newsgroups: alt.os.linux.mint
Subject: Re: Mint 21.1 Cinnamon locking up
Date: Wed, 19 Jul 2023 20:39:00 +0100
Organization: A noiseless patient Spider
Lines: 120
Message-ID: <u99e4k$29lq6$1@dont-email.me>
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
<u9672t$1lvng$1@dont-email.me> <u98mbi$258vu$1@dont-email.me>
<DbRtM.26628$AsA.4162@fx18.iad> <u98va6$26v5b$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Wed, 19 Jul 2023 19:39:00 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="af8879955588181a5bd64fd2c7a14d31";
logging-data="2414406"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+zwi3Kj4Zz/Mh9dRgHQZfP"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.13.0
Cancel-Lock: sha1:WuMY+5M2k/mQOKF6ytIIQL4a8tI=
In-Reply-To: <u98va6$26v5b$1@dont-email.me>
Content-Language: en-US
 by: Rob H - Wed, 19 Jul 2023 19:39 UTC

On 19/07/2023 16:25, Rob H wrote:

> My system has ran fine for years without any hard restarts nor lockups
> until these last few weeks.

System information if this helps

System:
Kernel: 5.15.0-75-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
Desktop: Cinnamon 5.6.8
tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.1 Vera
base: Ubuntu 22.04 jammy
Machine:
Type: Desktop Mobo: Gigabyte model: Z97-HD3 v: x.x serial: <superuser
required>
BIOS: American Megatrends v: F5 date: 06/03/2014
CPU:
Info: quad core model: Intel Core i5-4690 bits: 64 type: MCP arch:
Haswell rev: 3 cache:
L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 3789 high: 3833 min/max: 800/3900 cores: 1: 3833 2:
3810 3: 3735 4: 3780
bogomips: 28000
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated
Graphics vendor: Gigabyte
driver: i915 v: kernel ports: active: none empty:
HDMI-A-1,HDMI-A-2,VGA-1 bus-ID: 00:02.0
chip-ID: 8086:0412
Device-2: AMD Oland PRO [Radeon R7 240/340 / Radeon 520] vendor:
ASUSTeK driver: radeon
v: kernel pcie: speed: 8 GT/s lanes: 8 ports: active: DVI-D-1,VGA-2
empty: HDMI-A-3
bus-ID: 01:00.0 chip-ID: 1002:6613
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded:
ati,modesetting,radeon
unloaded: fbdev,vesa gpu: radeon display-ID: :0 screens: 1
Screen-1: 0 s-res: 3200x1080 s-dpi: 96
Monitor-1: DVI-0 mapped: DVI-D-1 pos: primary,top-right model:
Samsung SyncMaster
res: 1920x1080 dpi: 96 diag: 585mm (23")
Monitor-2: VGA-1 mapped: VGA-2 pos: bottom-l model: Dell E1715S res:
1280x1024 dpi: 96
diag: 433mm (17")
OpenGL: renderer: OLAND ( LLVM 15.0.7 DRM 2.50 5.15.0-75-generic)
v: 4.5 Mesa 22.2.5-0ubuntu0.1~22.04.3 direct render: Yes
Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
driver: snd_hda_intel v: kernel
bus-ID: 00:03.0 chip-ID: 8086:0c0c
Device-2: Intel 9 Series Family HD Audio vendor: Gigabyte driver:
snd_hda_intel v: kernel
bus-ID: 00:1b.0 chip-ID: 8086:8ca0
Device-3: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD
7000 Series]
vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s
lanes: 8 bus-ID: 01:00.1
chip-ID: 1002:aab0
Sound Server-1: ALSA v: k5.15.0-75-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Gigabyte driver: r8169
v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 03:00.0
chip-ID: 10ec:8168
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: docker0 state: down mac: <filter>
Drives:
Local Storage: total: 1.36 TiB used: 97.51 GiB (7.0%)
ID-1: /dev/sda vendor: Samsung model: SSD 870 EVO 250GB size: 232.89
GiB speed: 6.0 Gb/s
serial: <filter>
ID-2: /dev/sdb vendor: Western Digital model: WD10EZEX-07WN4A0 size:
931.51 GiB
speed: 6.0 Gb/s serial: <filter>
ID-3: /dev/sdc vendor: Samsung model: SSD 860 EVO 250GB size: 232.89
GiB speed: 6.0 Gb/s
serial: <filter>
Partition:
ID-1: / size: 227.68 GiB used: 56.52 GiB (24.8%) fs: ext4 dev: /dev/sdc5
ID-2: /boot/efi size: 511 MiB used: 4 KiB (0.0%) fs: vfat dev: /dev/sdc1
ID-3: /home size: 228.17 GiB used: 40.99 GiB (18.0%) fs: ext4 dev:
/dev/sda1
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 768 KiB (0.0%) priority: -2
file: /swapfile
USB:
Hub-1: 1-0:1 info: Full speed or root hub ports: 2 rev: 2.0 speed:
480 Mb/s chip-ID: 1d6b:0002
Hub-2: 1-1:2 info: Intel ports: 6 rev: 2.0 speed: 480 Mb/s chip-ID:
8087:8009
Hub-3: 2-0:1 info: Full speed or root hub ports: 2 rev: 2.0 speed:
480 Mb/s chip-ID: 1d6b:0002
Hub-4: 2-1:2 info: Intel Integrated Hub ports: 8 rev: 2.0 speed: 480
Mb/s chip-ID: 8087:8001
Hub-5: 3-0:1 info: Full speed or root hub ports: 5 rev: 2.0 speed:
480 Mb/s chip-ID: 1d6b:0002
Hub-6: 4-0:1 info: Full speed or root hub ports: 3 rev: 1.1 speed: 12
Mb/s chip-ID: 1d6b:0001
Hub-7: 5-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12
Mb/s chip-ID: 1d6b:0001
Hub-8: 6-0:1 info: Hi-speed hub with single TT ports: 14 rev: 2.0
speed: 480 Mb/s
chip-ID: 1d6b:0002
Device-1: 6-5:2 info: Cherry GmbH Keyboard type: Keyboard,HID driver:
cherry,usbhid rev: 2.0
speed: 1.5 Mb/s chip-ID: 046a:0023
Device-2: 6-6:3 info: Sunplus Innovation Gaming mouse [Philips
SPK9304] type: Mouse
driver: hid-generic,usbhid rev: 2.0 speed: 1.5 Mb/s chip-ID: 1bcf:08a0
Hub-9: 6-9:4 info: VIA Labs VL812 Hub ports: 4 rev: 2.1 speed: 480
Mb/s chip-ID: 2109:2812
Hub-10: 7-0:1 info: Super-speed hub ports: 6 rev: 3.0 speed: 5 Gb/s
chip-ID: 1d6b:0003
Hub-11: 7-5:2 info: VIA Labs VL812 Hub ports: 4 rev: 3.0 speed: 5
Gb/s chip-ID: 2109:0812
Sensors:
System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: radeon temp: 47.0 C

Re: Mint 21.1 Cinnamon locking up

<u9a0at$2cm8u$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6492&group=alt.os.linux.mint#6492

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nos...@needed.invalid (Paul)
Newsgroups: alt.os.linux.mint
Subject: Re: Mint 21.1 Cinnamon locking up
Date: Wed, 19 Jul 2023 20:49:32 -0400
Organization: A noiseless patient Spider
Lines: 113
Message-ID: <u9a0at$2cm8u$1@dont-email.me>
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
<u9672t$1lvng$1@dont-email.me> <u98mbi$258vu$1@dont-email.me>
<DbRtM.26628$AsA.4162@fx18.iad> <u98va6$26v5b$1@dont-email.me>
<u99e4k$29lq6$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 20 Jul 2023 00:49:33 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="0a2f17ee0e6343456c04c1f865dc3c3f";
logging-data="2513182"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19iZoGL+Hhd4rkOFy7d5q2+6gbvkGhIzl0="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
Cancel-Lock: sha1:K++7nqtyDDq39YX581LEWxkwV/8=
Content-Language: en-US
In-Reply-To: <u99e4k$29lq6$1@dont-email.me>
 by: Paul - Thu, 20 Jul 2023 00:49 UTC

On 7/19/2023 3:39 PM, Rob H wrote:
> On 19/07/2023 16:25, Rob H wrote:
>
>> My system has ran fine for years without any hard restarts nor lockups until these last few weeks.
>
> System information if this helps
>
> System:
>   Kernel: 5.15.0-75-generic x86_64 bits: 64 compiler: gcc v: 11.3.0 Desktop: Cinnamon 5.6.8
>     tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
> Machine:
>   Type: Desktop Mobo: Gigabyte model: Z97-HD3 v: x.x serial: <superuser required>
>     BIOS: American Megatrends v: F5 date: 06/03/2014
> CPU:
>   Info: quad core model: Intel Core i5-4690 bits: 64 type: MCP arch: Haswell rev: 3 cache:
>     L1: 256 KiB L2: 1024 KiB L3: 6 MiB
>   Speed (MHz): avg: 3789 high: 3833 min/max: 800/3900 cores: 1: 3833 2: 3810 3: 3735 4: 3780
>     bogomips: 28000
>   Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
> Graphics:
>   Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics vendor: Gigabyte
>     driver: i915 v: kernel ports: active: none empty: HDMI-A-1,HDMI-A-2,VGA-1 bus-ID: 00:02.0
>     chip-ID: 8086:0412
>   Device-2: AMD Oland PRO [Radeon R7 240/340 / Radeon 520] vendor: ASUSTeK driver: radeon
>     v: kernel pcie: speed: 8 GT/s lanes: 8 ports: active: DVI-D-1,VGA-2 empty: HDMI-A-3
>     bus-ID: 01:00.0 chip-ID: 1002:6613
>   Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: ati,modesetting,radeon
>     unloaded: fbdev,vesa gpu: radeon display-ID: :0 screens: 1
>   Screen-1: 0 s-res: 3200x1080 s-dpi: 96
>   Monitor-1: DVI-0 mapped: DVI-D-1 pos: primary,top-right model: Samsung SyncMaster
>     res: 1920x1080 dpi: 96 diag: 585mm (23")
>   Monitor-2: VGA-1 mapped: VGA-2 pos: bottom-l model: Dell E1715S res: 1280x1024 dpi: 96
>     diag: 433mm (17")
>   OpenGL: renderer: OLAND ( LLVM 15.0.7 DRM 2.50 5.15.0-75-generic)
>     v: 4.5 Mesa 22.2.5-0ubuntu0.1~22.04.3 direct render: Yes
> Audio:
>   Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel v: kernel
>     bus-ID: 00:03.0 chip-ID: 8086:0c0c
>   Device-2: Intel 9 Series Family HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
>     bus-ID: 00:1b.0 chip-ID: 8086:8ca0
>   Device-3: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series]
>     vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 8 bus-ID: 01:00.1
>     chip-ID: 1002:aab0
>   Sound Server-1: ALSA v: k5.15.0-75-generic running: yes
>   Sound Server-2: PulseAudio v: 15.99.1 running: yes
>   Sound Server-3: PipeWire v: 0.3.48 running: yes
> Network:
>   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169
>     v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168
>   IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
>   IF-ID-1: docker0 state: down mac: <filter>
> Drives:
>   Local Storage: total: 1.36 TiB used: 97.51 GiB (7.0%)
>   ID-1: /dev/sda vendor: Samsung model: SSD 870 EVO 250GB size: 232.89 GiB speed: 6.0 Gb/s
>     serial: <filter>
>   ID-2: /dev/sdb vendor: Western Digital model: WD10EZEX-07WN4A0 size: 931.51 GiB
>     speed: 6.0 Gb/s serial: <filter>
>   ID-3: /dev/sdc vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB speed: 6.0 Gb/s
>     serial: <filter>
> Partition:
>   ID-1: / size: 227.68 GiB used: 56.52 GiB (24.8%) fs: ext4 dev: /dev/sdc5
>   ID-2: /boot/efi size: 511 MiB used: 4 KiB (0.0%) fs: vfat dev: /dev/sdc1
>   ID-3: /home size: 228.17 GiB used: 40.99 GiB (18.0%) fs: ext4 dev: /dev/sda1
> Swap:
>   ID-1: swap-1 type: file size: 2 GiB used: 768 KiB (0.0%) priority: -2 file: /swapfile
> USB:
>   Hub-1: 1-0:1 info: Full speed or root hub ports: 2 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
>   Hub-2: 1-1:2 info: Intel ports: 6 rev: 2.0 speed: 480 Mb/s chip-ID: 8087:8009
>   Hub-3: 2-0:1 info: Full speed or root hub ports: 2 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
>   Hub-4: 2-1:2 info: Intel Integrated Hub ports: 8 rev: 2.0 speed: 480 Mb/s chip-ID: 8087:8001
>   Hub-5: 3-0:1 info: Full speed or root hub ports: 5 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
>   Hub-6: 4-0:1 info: Full speed or root hub ports: 3 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
>   Hub-7: 5-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
>   Hub-8: 6-0:1 info: Hi-speed hub with single TT ports: 14 rev: 2.0 speed: 480 Mb/s
>     chip-ID: 1d6b:0002
>   Device-1: 6-5:2 info: Cherry GmbH Keyboard type: Keyboard,HID driver: cherry,usbhid rev: 2.0
>     speed: 1.5 Mb/s chip-ID: 046a:0023
>   Device-2: 6-6:3 info: Sunplus Innovation Gaming mouse [Philips SPK9304] type: Mouse
>     driver: hid-generic,usbhid rev: 2.0 speed: 1.5 Mb/s chip-ID: 1bcf:08a0
>   Hub-9: 6-9:4 info: VIA Labs VL812 Hub ports: 4 rev: 2.1 speed: 480 Mb/s chip-ID: 2109:2812
>   Hub-10: 7-0:1 info: Super-speed hub ports: 6 rev: 3.0 speed: 5 Gb/s chip-ID: 1d6b:0003
>   Hub-11: 7-5:2 info: VIA Labs VL812 Hub ports: 4 rev: 3.0 speed: 5 Gb/s chip-ID: 2109:0812
> Sensors:
>   System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: radeon temp: 47.0 C

The only technique I know of at this point is:

1) Ping the machine from another machine, assuming address is known.
This is to see if the graphics and UI are dead and everything else is still running.
I've had a few failures like that over the years.

2) Set up an RS232 connection from the Linux machine to another machine.
I connect a Linux machine to a Windows machine (fitted with Putty for
the terminal session) over RS232. The RS232 cable rolls TX and RX when you
need to connect two computers together like that. There is a "blob" in my
chain of RS232 blobs, to do the Null Modem function of swapping TX and RX.

To the end of the kernel boot line, where it would say "quiet splash", I would place

console=ttyS0,57600n8

This assumes the motherboard has a serial port on the SuperIO. Both of my current
machines here today, have that. But making a serial port adapter, that goes from a
2x5 serial port header, to a DB9, that took soldering :-) The modern machines never
come with the slot adapter for the function, neither will they place a DB9 on the
I/O plate for this.

Why do we want to set up an RS232 port ? Because the target machine has to be
really really dead, to ignore input on it, that's why. You can run "dmesg" and
look for issues near the end of the information.

Paul

Re: Mint 21.1 Cinnamon locking up

<u9b0ge$2lefh$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6495&group=alt.os.linux.mint#6495

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: rob...@despammer.com (Rob H)
Newsgroups: alt.os.linux.mint
Subject: Re: Mint 21.1 Cinnamon locking up
Date: Thu, 20 Jul 2023 10:58:38 +0100
Organization: A noiseless patient Spider
Lines: 120
Message-ID: <u9b0ge$2lefh$1@dont-email.me>
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
<u9672t$1lvng$1@dont-email.me> <u98mbi$258vu$1@dont-email.me>
<DbRtM.26628$AsA.4162@fx18.iad> <u98va6$26v5b$1@dont-email.me>
<u99e4k$29lq6$1@dont-email.me> <u9a0at$2cm8u$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 20 Jul 2023 09:58:38 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="d9b9258c5fe9ae4b53e9dbfecd4a254f";
logging-data="2800113"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18nzZEkZBtPChk1Xf9QkGvb"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.13.0
Cancel-Lock: sha1:NG+fzF/A4ZiL4F1mSOU6U3S5i7I=
Content-Language: en-US
In-Reply-To: <u9a0at$2cm8u$1@dont-email.me>
 by: Rob H - Thu, 20 Jul 2023 09:58 UTC

On 20/07/2023 01:49, Paul wrote:
> On 7/19/2023 3:39 PM, Rob H wrote:
>> On 19/07/2023 16:25, Rob H wrote:
>>
>>> My system has ran fine for years without any hard restarts nor lockups until these last few weeks.
>>
>> System information if this helps
>>
>> System:
>>   Kernel: 5.15.0-75-generic x86_64 bits: 64 compiler: gcc v: 11.3.0 Desktop: Cinnamon 5.6.8
>>     tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
>> Machine:
>>   Type: Desktop Mobo: Gigabyte model: Z97-HD3 v: x.x serial: <superuser required>
>>     BIOS: American Megatrends v: F5 date: 06/03/2014
>> CPU:
>>   Info: quad core model: Intel Core i5-4690 bits: 64 type: MCP arch: Haswell rev: 3 cache:
>>     L1: 256 KiB L2: 1024 KiB L3: 6 MiB
>>   Speed (MHz): avg: 3789 high: 3833 min/max: 800/3900 cores: 1: 3833 2: 3810 3: 3735 4: 3780
>>     bogomips: 28000
>>   Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
>> Graphics:
>>   Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics vendor: Gigabyte
>>     driver: i915 v: kernel ports: active: none empty: HDMI-A-1,HDMI-A-2,VGA-1 bus-ID: 00:02.0
>>     chip-ID: 8086:0412
>>   Device-2: AMD Oland PRO [Radeon R7 240/340 / Radeon 520] vendor: ASUSTeK driver: radeon
>>     v: kernel pcie: speed: 8 GT/s lanes: 8 ports: active: DVI-D-1,VGA-2 empty: HDMI-A-3
>>     bus-ID: 01:00.0 chip-ID: 1002:6613
>>   Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: ati,modesetting,radeon
>>     unloaded: fbdev,vesa gpu: radeon display-ID: :0 screens: 1
>>   Screen-1: 0 s-res: 3200x1080 s-dpi: 96
>>   Monitor-1: DVI-0 mapped: DVI-D-1 pos: primary,top-right model: Samsung SyncMaster
>>     res: 1920x1080 dpi: 96 diag: 585mm (23")
>>   Monitor-2: VGA-1 mapped: VGA-2 pos: bottom-l model: Dell E1715S res: 1280x1024 dpi: 96
>>     diag: 433mm (17")
>>   OpenGL: renderer: OLAND ( LLVM 15.0.7 DRM 2.50 5.15.0-75-generic)
>>     v: 4.5 Mesa 22.2.5-0ubuntu0.1~22.04.3 direct render: Yes
>> Audio:
>>   Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel v: kernel
>>     bus-ID: 00:03.0 chip-ID: 8086:0c0c
>>   Device-2: Intel 9 Series Family HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
>>     bus-ID: 00:1b.0 chip-ID: 8086:8ca0
>>   Device-3: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series]
>>     vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 8 bus-ID: 01:00.1
>>     chip-ID: 1002:aab0
>>   Sound Server-1: ALSA v: k5.15.0-75-generic running: yes
>>   Sound Server-2: PulseAudio v: 15.99.1 running: yes
>>   Sound Server-3: PipeWire v: 0.3.48 running: yes
>> Network:
>>   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169
>>     v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168
>>   IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
>>   IF-ID-1: docker0 state: down mac: <filter>
>> Drives:
>>   Local Storage: total: 1.36 TiB used: 97.51 GiB (7.0%)
>>   ID-1: /dev/sda vendor: Samsung model: SSD 870 EVO 250GB size: 232.89 GiB speed: 6.0 Gb/s
>>     serial: <filter>
>>   ID-2: /dev/sdb vendor: Western Digital model: WD10EZEX-07WN4A0 size: 931.51 GiB
>>     speed: 6.0 Gb/s serial: <filter>
>>   ID-3: /dev/sdc vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB speed: 6.0 Gb/s
>>     serial: <filter>
>> Partition:
>>   ID-1: / size: 227.68 GiB used: 56.52 GiB (24.8%) fs: ext4 dev: /dev/sdc5
>>   ID-2: /boot/efi size: 511 MiB used: 4 KiB (0.0%) fs: vfat dev: /dev/sdc1
>>   ID-3: /home size: 228.17 GiB used: 40.99 GiB (18.0%) fs: ext4 dev: /dev/sda1
>> Swap:
>>   ID-1: swap-1 type: file size: 2 GiB used: 768 KiB (0.0%) priority: -2 file: /swapfile
>> USB:
>>   Hub-1: 1-0:1 info: Full speed or root hub ports: 2 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
>>   Hub-2: 1-1:2 info: Intel ports: 6 rev: 2.0 speed: 480 Mb/s chip-ID: 8087:8009
>>   Hub-3: 2-0:1 info: Full speed or root hub ports: 2 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
>>   Hub-4: 2-1:2 info: Intel Integrated Hub ports: 8 rev: 2.0 speed: 480 Mb/s chip-ID: 8087:8001
>>   Hub-5: 3-0:1 info: Full speed or root hub ports: 5 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
>>   Hub-6: 4-0:1 info: Full speed or root hub ports: 3 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
>>   Hub-7: 5-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
>>   Hub-8: 6-0:1 info: Hi-speed hub with single TT ports: 14 rev: 2.0 speed: 480 Mb/s
>>     chip-ID: 1d6b:0002
>>   Device-1: 6-5:2 info: Cherry GmbH Keyboard type: Keyboard,HID driver: cherry,usbhid rev: 2.0
>>     speed: 1.5 Mb/s chip-ID: 046a:0023
>>   Device-2: 6-6:3 info: Sunplus Innovation Gaming mouse [Philips SPK9304] type: Mouse
>>     driver: hid-generic,usbhid rev: 2.0 speed: 1.5 Mb/s chip-ID: 1bcf:08a0
>>   Hub-9: 6-9:4 info: VIA Labs VL812 Hub ports: 4 rev: 2.1 speed: 480 Mb/s chip-ID: 2109:2812
>>   Hub-10: 7-0:1 info: Super-speed hub ports: 6 rev: 3.0 speed: 5 Gb/s chip-ID: 1d6b:0003
>>   Hub-11: 7-5:2 info: VIA Labs VL812 Hub ports: 4 rev: 3.0 speed: 5 Gb/s chip-ID: 2109:0812
>> Sensors:
>>   System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: radeon temp: 47.0 C
>
> The only technique I know of at this point is:
>
> 1) Ping the machine from another machine, assuming address is known.
> This is to see if the graphics and UI are dead and everything else is still running.
> I've had a few failures like that over the years.
>
> 2) Set up an RS232 connection from the Linux machine to another machine.
> I connect a Linux machine to a Windows machine (fitted with Putty for
> the terminal session) over RS232. The RS232 cable rolls TX and RX when you
> need to connect two computers together like that. There is a "blob" in my
> chain of RS232 blobs, to do the Null Modem function of swapping TX and RX.
>
> To the end of the kernel boot line, where it would say "quiet splash", I would place
>
> console=ttyS0,57600n8
>
> This assumes the motherboard has a serial port on the SuperIO. Both of my current
> machines here today, have that. But making a serial port adapter, that goes from a
> 2x5 serial port header, to a DB9, that took soldering :-) The modern machines never
> come with the slot adapter for the function, neither will they place a DB9 on the
> I/O plate for this.
>
> Why do we want to set up an RS232 port ? Because the target machine has to be
> really really dead, to ignore input on it, that's why. You can run "dmesg" and
> look for issues near the end of the information.
>
> Paul
>

thanks Paul, I'll try that later.
I have just finished running Memtest86+ for about 2.5 hours, and there
are no memory errors at all. The cpu is running at around 50C give or take
Thanks

Re: Mint 21.1 Cinnamon locking up

<u9bs6b$3dffi$1@paganini.bofh.team>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6497&group=alt.os.linux.mint#6497

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!paganini.bofh.team!not-for-mail
From: inva...@invalid.net (Jack)
Newsgroups: alt.os.linux.mint
Subject: Re: Mint 21.1 Cinnamon locking up
Date: Thu, 20 Jul 2023 19:00:00 +0100
Organization: To protect and to server
Message-ID: <u9bs6b$3dffi$1@paganini.bofh.team>
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
<u9672t$1lvng$1@dont-email.me> <u98mbi$258vu$1@dont-email.me>
<DbRtM.26628$AsA.4162@fx18.iad> <u98va6$26v5b$1@dont-email.me>
<u99e4k$29lq6$1@dont-email.me> <u9a0at$2cm8u$1@dont-email.me>
<u9b0ge$2lefh$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain;
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 20 Jul 2023 17:51:07 -0000 (UTC)
Injection-Info: paganini.bofh.team; logging-data="3587570"; posting-host="lvwnlrZOTyXOUFTBTyWy3g.user.paganini.bofh.team"; mail-complaints-to="usenet@bofh.team"; posting-account="9dIQLXBM7WM9KzA+yjdR4A";
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha256:rob2AgZXIPZP2vlRyf41ha5bOlkPFqDILQczaeQUxSs=
Content-Language: en-CA
X-Notice: Filtered by postfilter v. 0.9.3
 by: Jack - Thu, 20 Jul 2023 18:00 UTC

On 20/07/2023 10:58, Rob H wrote:
>
>
>
> I have just finished running Memtest86+ for about 2.5 hours, and there
> are no memory errors at all. The cpu is running� at around 50C give or
> take
>
>

Have you tried ubuntu cinnamon? It's worth a try:
<https://ubuntucinnamon.org/>

It combines Linux Mint�s flagship Cinnamon Desktop with Ubuntu.

Re: Mint 21.1 Cinnamon locking up

<20230721104041.48fe31449055955e67c4911f@gmail.com>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6500&group=alt.os.linux.mint#6500

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: pinner...@gmail.com (pinnerite)
Newsgroups: alt.os.linux.mint
Subject: Re: Mint 21.1 Cinnamon locking up
Date: Fri, 21 Jul 2023 10:40:41 +0100
Organization: A noiseless patient Spider
Lines: 20
Message-ID: <20230721104041.48fe31449055955e67c4911f@gmail.com>
References: <u90k23$oje8$1@dont-email.me>
<CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me>
<mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me>
<u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me>
<u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me>
<u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me>
<u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me>
<u95uo1$1kmq0$1@dont-email.me>
<u966tf$1luj3$1@dont-email.me>
<u9675h$1m111$1@dont-email.me>
<u968mi$1m82i$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Info: dont-email.me; posting-host="32b78ac1b744be6fca946a4076170c6b";
logging-data="3360197"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19hwqfhN5Wclev2XfX/VYe4DJ5O6Q2TlTE="
Cancel-Lock: sha1:CzpX7c2yX8uDXoDzTwGIPUplmdQ=
X-Newsreader: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu)
 by: pinnerite - Fri, 21 Jul 2023 09:40 UTC

On Tue, 18 Jul 2023 15:47:46 +0100
Rob H <rob@despammer.com> wrote:

> On 18/07/2023 15:21, Paul wrote:
> > sudo update-grub
>
> Thanks, yes I did that before I rebooted.

I saw that you had tested your dram.
Just to be sure, I would test the disk drive.
I usually run:

# fsck -y -C -V /dev/sd(x)

before getting elaborate.

One other thing. I highly recommend the Logitech wireless mouse.
It is very light on batteries and has not let me down since purchase about five or six years ago.

Best of luck

Re: Mint 21.1 Cinnamon locking up

<u9eidh$3cdpm$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6509&group=alt.os.linux.mint#6509

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: rob...@despammer.com (Rob H)
Newsgroups: alt.os.linux.mint
Subject: Re: Mint 21.1 Cinnamon locking up
Date: Fri, 21 Jul 2023 19:22:41 +0100
Organization: A noiseless patient Spider
Lines: 23
Message-ID: <u9eidh$3cdpm$1@dont-email.me>
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
<u966tf$1luj3$1@dont-email.me> <u9675h$1m111$1@dont-email.me>
<u968mi$1m82i$1@dont-email.me>
<20230721104041.48fe31449055955e67c4911f@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Fri, 21 Jul 2023 18:22:41 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="43294a9e4e46aa6a75eed0b478a278a7";
logging-data="3553078"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/Kl9b+RTHZb1LTKfZ+kYhM"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.13.0
Cancel-Lock: sha1:gqBHhI11QpKJmMw42Ku9dVH2j+g=
In-Reply-To: <20230721104041.48fe31449055955e67c4911f@gmail.com>
Content-Language: en-US
 by: Rob H - Fri, 21 Jul 2023 18:22 UTC

On 21/07/2023 10:40, pinnerite wrote:
> On Tue, 18 Jul 2023 15:47:46 +0100
> Rob H <rob@despammer.com> wrote:
>
>> On 18/07/2023 15:21, Paul wrote:
>>> sudo update-grub
>>
>> Thanks, yes I did that before I rebooted.
>
> I saw that you had tested your dram.
> Just to be sure, I would test the disk drive.
> I usually run:
>
> # fsck -y -C -V /dev/sd(x)
>
> before getting elaborate.
>
> One other thing. I highly recommend the Logitech wireless mouse.
> It is very light on batteries and has not let me down since purchase about five or six years ago.
>
> Best of luck

Thanks but silly question, how do I test the disc when it is in use

Re: Mint 21.1 Cinnamon locking up

<20230721232131.47855419fb72a7136ca202bb@gmail.com>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6514&group=alt.os.linux.mint#6514

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: pinner...@gmail.com (pinnerite)
Newsgroups: alt.os.linux.mint
Subject: Re: Mint 21.1 Cinnamon locking up
Date: Fri, 21 Jul 2023 23:21:31 +0100
Organization: A noiseless patient Spider
Lines: 33
Message-ID: <20230721232131.47855419fb72a7136ca202bb@gmail.com>
References: <u90k23$oje8$1@dont-email.me>
<CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me>
<mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me>
<u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me>
<u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me>
<u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me>
<u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me>
<u95uo1$1kmq0$1@dont-email.me>
<u966tf$1luj3$1@dont-email.me>
<u9675h$1m111$1@dont-email.me>
<u968mi$1m82i$1@dont-email.me>
<20230721104041.48fe31449055955e67c4911f@gmail.com>
<u9eidh$3cdpm$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Info: dont-email.me; posting-host="3dfb94bc0df0c8bdc53286bc8d1cc0b9";
logging-data="3646391"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/2Jprmp1bDfQm0Ekvl/G9VggFmbDK04zM="
Cancel-Lock: sha1:4Nu0q9fK1mGtBjNsDTpNQUJ4o4E=
X-Newsreader: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu)
 by: pinnerite - Fri, 21 Jul 2023 22:21 UTC

On Fri, 21 Jul 2023 19:22:41 +0100
Rob H <rob@despammer.com> wrote:

> On 21/07/2023 10:40, pinnerite wrote:
> > On Tue, 18 Jul 2023 15:47:46 +0100
> > Rob H <rob@despammer.com> wrote:
> >
> >> On 18/07/2023 15:21, Paul wrote:
> >>> sudo update-grub
> >>
> >> Thanks, yes I did that before I rebooted.
> >
> > I saw that you had tested your dram.
> > Just to be sure, I would test the disk drive.
> > I usually run:
> >
> > # fsck -y -C -V /dev/sd(x)
> >
> > before getting elaborate.
> >
> > One other thing. I highly recommend the Logitech wireless mouse.
> > It is very light on batteries and has not let me down since purchase about five or six years ago.
> >
> > Best of luck
>
> Thanks but silly question, how do I test the disc when it is in use

Boot up on a live CD/DVD or flash drive.
My favourite's are Knoppix and Parted Magic.

Re: Mint 21.1 Cinnamon locking up

<u9jp4n$adud$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6531&group=alt.os.linux.mint#6531

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: rob...@despammer.com (Rob H)
Newsgroups: alt.os.linux.mint
Subject: Re: Mint 21.1 Cinnamon locking up
Date: Sun, 23 Jul 2023 18:48:07 +0100
Organization: A noiseless patient Spider
Lines: 54
Message-ID: <u9jp4n$adud$1@dont-email.me>
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
<u966tf$1luj3$1@dont-email.me> <u9675h$1m111$1@dont-email.me>
<u968mi$1m82i$1@dont-email.me>
<20230721104041.48fe31449055955e67c4911f@gmail.com>
<u9eidh$3cdpm$1@dont-email.me>
<20230721232131.47855419fb72a7136ca202bb@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 23 Jul 2023 17:48:07 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="086365c5784b92c27dd7e1ec2dddc159";
logging-data="341965"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19cuX0ammca4NKZKJz0Qdle"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.13.0
Cancel-Lock: sha1:MrA95qHspJgYQkE6L8WnIvyd6B4=
Content-Language: en-US
In-Reply-To: <20230721232131.47855419fb72a7136ca202bb@gmail.com>
 by: Rob H - Sun, 23 Jul 2023 17:48 UTC

On 21/07/2023 23:21, pinnerite wrote:
> On Fri, 21 Jul 2023 19:22:41 +0100
> Rob H <rob@despammer.com> wrote:
>
>> On 21/07/2023 10:40, pinnerite wrote:
>>> On Tue, 18 Jul 2023 15:47:46 +0100
>>> Rob H <rob@despammer.com> wrote:
>>>
>>>> On 18/07/2023 15:21, Paul wrote:
>>>>> sudo update-grub
>>>>
>>>> Thanks, yes I did that before I rebooted.
>>>
>>> I saw that you had tested your dram.
>>> Just to be sure, I would test the disk drive.
>>> I usually run:
>>>
>>> # fsck -y -C -V /dev/sd(x)
>>>
>>> before getting elaborate.
>>>
>>> One other thing. I highly recommend the Logitech wireless mouse.
>>> It is very light on batteries and has not let me down since purchase about five or six years ago.
>>>
>>> Best of luck
>>
>> Thanks but silly question, how do I test the disc when it is in use
>
> Boot up on a live CD/DVD or flash drive.
> My favourite's are Knoppix and Parted Magic.
>
>
>
>

I have just booted up a live knoppix usb and ran
fsck -y -C -V /dev/sda

but got this:
Found a dos partition table in /dev/sdc
e2fsck_open2: Bad magic number in super block
fsck.ext2 Superblock invalid
fsck.ext2 Bad magic number in super-block while trying to open /dev/sda

The superblock could not be read or does not describe a valid
ext2/ext3/ext4 fileystem If the device is valid and it realy contains
and ext2/et3/ext4 filesystem (and not aq swap or ufs or something else),
then the superblock is corrupt , and you might try running e2fsck with
an alternative superblock.

Does it mean my filesystem is corrupt or?

Thanks

Re: Mint 21.1 Cinnamon locking up

<u9ju0q$aul5$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6532&group=alt.os.linux.mint#6532

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nos...@needed.invalid (Paul)
Newsgroups: alt.os.linux.mint
Subject: Re: Mint 21.1 Cinnamon locking up
Date: Sun, 23 Jul 2023 15:11:20 -0400
Organization: A noiseless patient Spider
Lines: 98
Message-ID: <u9ju0q$aul5$1@dont-email.me>
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
<u966tf$1luj3$1@dont-email.me> <u9675h$1m111$1@dont-email.me>
<u968mi$1m82i$1@dont-email.me>
<20230721104041.48fe31449055955e67c4911f@gmail.com>
<u9eidh$3cdpm$1@dont-email.me>
<20230721232131.47855419fb72a7136ca202bb@gmail.com>
<u9jp4n$adud$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 23 Jul 2023 19:11:22 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="07dd410f532f4f123552e1f9c8c1bd08";
logging-data="359077"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+aG6tNJpBOAUlR7Fze3GQLYR0RJYQw8NA="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
Cancel-Lock: sha1:W0MGtCfEu9rF/4wMlVn95RXLgyY=
In-Reply-To: <u9jp4n$adud$1@dont-email.me>
Content-Language: en-US
 by: Paul - Sun, 23 Jul 2023 19:11 UTC

On 7/23/2023 1:48 PM, Rob H wrote:
> On 21/07/2023 23:21, pinnerite wrote:
>> On Fri, 21 Jul 2023 19:22:41 +0100
>> Rob H <rob@despammer.com> wrote:
>>
>>> On 21/07/2023 10:40, pinnerite wrote:
>>>> On Tue, 18 Jul 2023 15:47:46 +0100
>>>> Rob H <rob@despammer.com> wrote:
>>>>
>>>>> On 18/07/2023 15:21, Paul wrote:
>>>>>> sudo update-grub
>>>>>
>>>>> Thanks, yes I did that before I rebooted.
>>>>
>>>> I saw that you had tested your dram.
>>>> Just to be sure, I would test the disk drive.
>>>> I usually run:
>>>>
>>>> # fsck -y -C -V /dev/sd(x)
>>>>
>>>> before getting elaborate.
>>>>
>>>> One other thing. I highly recommend the Logitech wireless mouse.
>>>> It is very light on batteries and has not let me down since purchase about five or six years ago.
>>>>
>>>> Best of luck
>>>
>>> Thanks but silly question, how do I test the disc when it is in use
>>
>> Boot up on a live CD/DVD or flash drive.
>> My favourite's are Knoppix and Parted Magic.
>>
>>
>>
>>
>
> I have just booted up a live knoppix usb and ran
> fsck -y -C -V /dev/sda
>
> but got this:
> Found a dos partition table in /dev/sdc
> e2fsck_open2: Bad magic number in super block
> fsck.ext2 Superblock invalid
> fsck.ext2 Bad magic number in super-block while trying to open /dev/sda
>
> The superblock could not be read or does not describe a valid ext2/ext3/ext4 fileystem If the device is valid and it realy contains and ext2/et3/ext4 filesystem (and not aq swap or ufs or something else), then the superblock is corrupt , and you might try running e2fsck with an alternative superblock.
>
> Does it mean my filesystem is corrupt or?
>
> Thanks
>

The identifier "/dev/sda" is the entire disk, starting at the MBR (sector 0).

Partition identifiers are "/dev/sda1" or "/dev/sda2". In one of those,
you are more likely to find a file system and all the trimmings.

fsck -y -C -V /dev/sda1
fsck -y -C -V /dev/sda2

If you use gparted

sudo gparted /dev/sda

then graphically you can select some of these functions.
The benefit of doing it graphically, is there will be
little "hints" in the GUI, that the thing you are pointed
at, is an EXT2 or a FAT32 or an NTFS. And you have a better
idea what partition you are checking.

[Picture]

https://i.postimg.cc/tJ29Pz4D/gparted-graphical-info.gif

You can also do

sudo disktype /dev/sda

and it will print out what it finds.

Or for that matter, with a booted system, try

gnome-disks

and select the drive from the menu.

1) Create a partition (nominal partition type like 0x83)
2) Format it so the superblock will be there.
3) Don't mount it, if you're going to check it.
If it is mounted, then unmount it first, then check it.

Mounting a partition, does a certain amount of checking anyway.
The assumption is, there is a partition not currently mounted,
and it does not seem interested in accepting a mount command.

Paul

Re: Mint 21.1 Cinnamon locking up

<u9jvio$b2p0$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6533&group=alt.os.linux.mint#6533

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: rob...@despammer.com (Rob H)
Newsgroups: alt.os.linux.mint
Subject: Re: Mint 21.1 Cinnamon locking up
Date: Sun, 23 Jul 2023 20:38:00 +0100
Organization: A noiseless patient Spider
Lines: 110
Message-ID: <u9jvio$b2p0$1@dont-email.me>
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
<u966tf$1luj3$1@dont-email.me> <u9675h$1m111$1@dont-email.me>
<u968mi$1m82i$1@dont-email.me>
<20230721104041.48fe31449055955e67c4911f@gmail.com>
<u9eidh$3cdpm$1@dont-email.me>
<20230721232131.47855419fb72a7136ca202bb@gmail.com>
<u9jp4n$adud$1@dont-email.me> <u9ju0q$aul5$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 23 Jul 2023 19:38:00 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="086365c5784b92c27dd7e1ec2dddc159";
logging-data="363296"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/ZbCmB3B53kds933sAnLqU"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.13.0
Cancel-Lock: sha1:2feLLo7Esw42ZjD09gj66Q6LLdQ=
Content-Language: en-US
In-Reply-To: <u9ju0q$aul5$1@dont-email.me>
 by: Rob H - Sun, 23 Jul 2023 19:38 UTC

On 23/07/2023 20:11, Paul wrote:
> On 7/23/2023 1:48 PM, Rob H wrote:
>> On 21/07/2023 23:21, pinnerite wrote:
>>> On Fri, 21 Jul 2023 19:22:41 +0100
>>> Rob H <rob@despammer.com> wrote:
>>>
>>>> On 21/07/2023 10:40, pinnerite wrote:
>>>>> On Tue, 18 Jul 2023 15:47:46 +0100
>>>>> Rob H <rob@despammer.com> wrote:
>>>>>
>>>>>> On 18/07/2023 15:21, Paul wrote:
>>>>>>> sudo update-grub
>>>>>>
>>>>>> Thanks, yes I did that before I rebooted.
>>>>>
>>>>> I saw that you had tested your dram.
>>>>> Just to be sure, I would test the disk drive.
>>>>> I usually run:
>>>>>
>>>>> # fsck -y -C -V /dev/sd(x)
>>>>>
>>>>> before getting elaborate.
>>>>>
>>>>> One other thing. I highly recommend the Logitech wireless mouse.
>>>>> It is very light on batteries and has not let me down since purchase about five or six years ago.
>>>>>
>>>>> Best of luck
>>>>
>>>> Thanks but silly question, how do I test the disc when it is in use
>>>
>>> Boot up on a live CD/DVD or flash drive.
>>> My favourite's are Knoppix and Parted Magic.
>>>
>>>
>>>
>>>
>>
>> I have just booted up a live knoppix usb and ran
>> fsck -y -C -V /dev/sda
>>
>> but got this:
>> Found a dos partition table in /dev/sdc
>> e2fsck_open2: Bad magic number in super block
>> fsck.ext2 Superblock invalid
>> fsck.ext2 Bad magic number in super-block while trying to open /dev/sda
>>
>> The superblock could not be read or does not describe a valid ext2/ext3/ext4 fileystem If the device is valid and it realy contains and ext2/et3/ext4 filesystem (and not aq swap or ufs or something else), then the superblock is corrupt , and you might try running e2fsck with an alternative superblock.
>>
>> Does it mean my filesystem is corrupt or?
>>
>> Thanks
>>
>
> The identifier "/dev/sda" is the entire disk, starting at the MBR (sector 0).
>
> Partition identifiers are "/dev/sda1" or "/dev/sda2". In one of those,
> you are more likely to find a file system and all the trimmings.
>
> fsck -y -C -V /dev/sda1
> fsck -y -C -V /dev/sda2
>
> If you use gparted
>
> sudo gparted /dev/sda
>
> then graphically you can select some of these functions.
> The benefit of doing it graphically, is there will be
> little "hints" in the GUI, that the thing you are pointed
> at, is an EXT2 or a FAT32 or an NTFS. And you have a better
> idea what partition you are checking.
>
> [Picture]
>
> https://i.postimg.cc/tJ29Pz4D/gparted-graphical-info.gif
>
> You can also do
>
> sudo disktype /dev/sda
>
> and it will print out what it finds.
>
> Or for that matter, with a booted system, try
>
> gnome-disks
>
> and select the drive from the menu.
>
> 1) Create a partition (nominal partition type like 0x83)
> 2) Format it so the superblock will be there.
> 3) Don't mount it, if you're going to check it.
> If it is mounted, then unmount it first, then check it.
>
> Mounting a partition, does a certain amount of checking anyway.
> The assumption is, there is a partition not currently mounted,
> and it does not seem interested in accepting a mount command.
>
> Paul
>
>
Thanks Paul, and both sda1 and sdc5 are clean with no errors, after. I
ran the said cmd

So my ssd drive is ok as is the filesystem as well as no errors with my
ram sticks.
I would deduce then that it something to do with linux mint itself??
On the LM forum , where I posted my problem, and I am not the only one
it seems, I was told to remove any powered usb adaptors, which I did 2
days ago. All was well until earlier today when it locked up again.

I have yet to try your earlier suggestion with a RS232 cable.

Re: Mint 21.1 Cinnamon locking up

<gmgvM.18926$JG_b.13352@fx39.iad>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6534&group=alt.os.linux.mint#6534

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx39.iad.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.13.0
Reply-To: Nic@none.net
Subject: Re: Mint 21.1 Cinnamon locking up
Content-Language: en-US
Newsgroups: alt.os.linux.mint
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
<u966tf$1luj3$1@dont-email.me> <u9675h$1m111$1@dont-email.me>
<u968mi$1m82i$1@dont-email.me>
<20230721104041.48fe31449055955e67c4911f@gmail.com>
<u9eidh$3cdpm$1@dont-email.me>
<20230721232131.47855419fb72a7136ca202bb@gmail.com>
<u9jp4n$adud$1@dont-email.me> <u9ju0q$aul5$1@dont-email.me>
<u9jvio$b2p0$1@dont-email.me>
From: Nic...@none.net (Nic)
Organization: Arm Chair Observer
In-Reply-To: <u9jvio$b2p0$1@dont-email.me>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Lines: 119
Message-ID: <gmgvM.18926$JG_b.13352@fx39.iad>
X-Complaints-To: abuse(at)newshosting.com
NNTP-Posting-Date: Sun, 23 Jul 2023 20:48:12 UTC
Date: Sun, 23 Jul 2023 16:48:12 -0400
X-Received-Bytes: 5482
 by: Nic - Sun, 23 Jul 2023 20:48 UTC

On 7/23/23 3:38 PM, Rob H wrote:
> On 23/07/2023 20:11, Paul wrote:
>> On 7/23/2023 1:48 PM, Rob H wrote:
>>> On 21/07/2023 23:21, pinnerite wrote:
>>>> On Fri, 21 Jul 2023 19:22:41 +0100
>>>> Rob H <rob@despammer.com> wrote:
>>>>
>>>>> On 21/07/2023 10:40, pinnerite wrote:
>>>>>> On Tue, 18 Jul 2023 15:47:46 +0100
>>>>>> Rob H <rob@despammer.com> wrote:
>>>>>>
>>>>>>> On 18/07/2023 15:21, Paul wrote:
>>>>>>>> sudo update-grub
>>>>>>>
>>>>>>> Thanks, yes I did that before I rebooted.
>>>>>>
>>>>>> I saw that you had tested your dram.
>>>>>> Just to be sure, I would test the disk drive.
>>>>>> I usually run:
>>>>>>
>>>>>> # fsck -y -C -V /dev/sd(x)
>>>>>>
>>>>>> before getting elaborate.
>>>>>>
>>>>>> One other thing. I highly recommend the Logitech wireless mouse.
>>>>>> It is very light on batteries and has not let me down since
>>>>>> purchase about five or six years ago.
>>>>>>
>>>>>> Best of luck
>>>>>
>>>>> Thanks but silly question, how do I test the disc when it is in use
>>>>
>>>> Boot up on a live CD/DVD or flash drive.
>>>> My favourite's are Knoppix and Parted Magic.
>>>>
>>>>
>>>>
>>>>
>>>
>>> I have just booted up a live knoppix usb and ran
>>> fsck -y -C -V /dev/sda
>>>
>>> but got this:
>>> Found a dos partition table in /dev/sdc
>>> e2fsck_open2: Bad magic number in super block
>>> fsck.ext2 Superblock invalid
>>> fsck.ext2 Bad magic number in super-block while trying to open /dev/sda
>>>
>>> The superblock could not be read or does not describe a valid
>>> ext2/ext3/ext4 fileystem If the device is valid and it realy
>>> contains and ext2/et3/ext4 filesystem (and not aq swap or ufs or
>>> something else), then the superblock is corrupt , and you might try
>>> running e2fsck with an alternative superblock.
>>>
>>> Does it mean my filesystem is corrupt or?
>>>
>>> Thanks
>>>
>>
>> The identifier "/dev/sda" is the entire disk, starting at the MBR
>> (sector 0).
>>
>> Partition identifiers are "/dev/sda1" or "/dev/sda2". In one of those,
>> you are more likely to find a file system and all the trimmings.
>>
>>     fsck -y -C -V /dev/sda1
>>     fsck -y -C -V /dev/sda2
>>
>> If you use gparted
>>
>>     sudo gparted /dev/sda
>>
>> then graphically you can select some of these functions.
>> The benefit of doing it graphically, is there will be
>> little "hints" in the GUI, that the thing you are pointed
>> at, is an EXT2 or a FAT32 or an NTFS. And you have a better
>> idea what partition you are checking.
>>
>>     [Picture]
>>
>>      https://i.postimg.cc/tJ29Pz4D/gparted-graphical-info.gif
>>
>> You can also do
>>
>>     sudo disktype /dev/sda
>>
>> and it will print out what it finds.
>>
>> Or for that matter, with a booted system, try
>>
>>     gnome-disks
>>
>> and select the drive from the menu.
>>
>> 1) Create a partition (nominal partition type like 0x83)
>> 2) Format it so the superblock will be there.
>> 3) Don't mount it, if you're going to check it.
>>     If it is mounted, then unmount it first, then check it.
>>
>> Mounting a partition, does a certain amount of checking anyway.
>> The assumption is, there is a partition not currently mounted,
>> and it does not seem interested in accepting a mount command.
>>
>>     Paul
>>
>>
> Thanks Paul, and both sda1 and sdc5 are clean with no errors, after. I
> ran the said cmd
>
> So my ssd drive is ok as is the filesystem as well as no errors with
> my ram sticks.
> I would deduce then that it something to do with linux mint itself??
> On the LM forum , where I posted my problem, and I am not the only one
> it seems, I was told to remove any powered usb adaptors, which I did 2
> days ago. All was well until earlier today when it locked up again.
>
> I have yet to try your earlier suggestion with a RS232 cable.
Is  a windows product also installed on this machine? I thought that a
DOS partition might indicate such.

Re: Mint 21.1 Cinnamon locking up

<u9l6sk$ip3g$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6536&group=alt.os.linux.mint#6536

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: rob...@despammer.com (Rob H)
Newsgroups: alt.os.linux.mint
Subject: Re: Mint 21.1 Cinnamon locking up
Date: Mon, 24 Jul 2023 07:48:52 +0100
Organization: A noiseless patient Spider
Lines: 127
Message-ID: <u9l6sk$ip3g$1@dont-email.me>
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
<u966tf$1luj3$1@dont-email.me> <u9675h$1m111$1@dont-email.me>
<u968mi$1m82i$1@dont-email.me>
<20230721104041.48fe31449055955e67c4911f@gmail.com>
<u9eidh$3cdpm$1@dont-email.me>
<20230721232131.47855419fb72a7136ca202bb@gmail.com>
<u9jp4n$adud$1@dont-email.me> <u9ju0q$aul5$1@dont-email.me>
<u9jvio$b2p0$1@dont-email.me> <gmgvM.18926$JG_b.13352@fx39.iad>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 24 Jul 2023 06:48:52 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="872a5e5c4136f266ad462ffbf8f20340";
logging-data="615536"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+jkODCtoK89yBT19MY6Trs"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.13.0
Cancel-Lock: sha1:pNTbotSaCrYkD0Ql6XyghhcY+pc=
In-Reply-To: <gmgvM.18926$JG_b.13352@fx39.iad>
Content-Language: en-US
 by: Rob H - Mon, 24 Jul 2023 06:48 UTC

On 23/07/2023 21:48, Nic wrote:
> On 7/23/23 3:38 PM, Rob H wrote:
>> On 23/07/2023 20:11, Paul wrote:
>>> On 7/23/2023 1:48 PM, Rob H wrote:
>>>> On 21/07/2023 23:21, pinnerite wrote:
>>>>> On Fri, 21 Jul 2023 19:22:41 +0100
>>>>> Rob H <rob@despammer.com> wrote:
>>>>>
>>>>>> On 21/07/2023 10:40, pinnerite wrote:
>>>>>>> On Tue, 18 Jul 2023 15:47:46 +0100
>>>>>>> Rob H <rob@despammer.com> wrote:
>>>>>>>
>>>>>>>> On 18/07/2023 15:21, Paul wrote:
>>>>>>>>> sudo update-grub
>>>>>>>>
>>>>>>>> Thanks, yes I did that before I rebooted.
>>>>>>>
>>>>>>> I saw that you had tested your dram.
>>>>>>> Just to be sure, I would test the disk drive.
>>>>>>> I usually run:
>>>>>>>
>>>>>>> # fsck -y -C -V /dev/sd(x)
>>>>>>>
>>>>>>> before getting elaborate.
>>>>>>>
>>>>>>> One other thing. I highly recommend the Logitech wireless mouse.
>>>>>>> It is very light on batteries and has not let me down since
>>>>>>> purchase about five or six years ago.
>>>>>>>
>>>>>>> Best of luck
>>>>>>
>>>>>> Thanks but silly question, how do I test the disc when it is in use
>>>>>
>>>>> Boot up on a live CD/DVD or flash drive.
>>>>> My favourite's are Knoppix and Parted Magic.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> I have just booted up a live knoppix usb and ran
>>>> fsck -y -C -V /dev/sda
>>>>
>>>> but got this:
>>>> Found a dos partition table in /dev/sdc
>>>> e2fsck_open2: Bad magic number in super block
>>>> fsck.ext2 Superblock invalid
>>>> fsck.ext2 Bad magic number in super-block while trying to open /dev/sda
>>>>
>>>> The superblock could not be read or does not describe a valid
>>>> ext2/ext3/ext4 fileystem If the device is valid and it realy
>>>> contains and ext2/et3/ext4 filesystem (and not aq swap or ufs or
>>>> something else), then the superblock is corrupt , and you might try
>>>> running e2fsck with an alternative superblock.
>>>>
>>>> Does it mean my filesystem is corrupt or?
>>>>
>>>> Thanks
>>>>
>>>
>>> The identifier "/dev/sda" is the entire disk, starting at the MBR
>>> (sector 0).
>>>
>>> Partition identifiers are "/dev/sda1" or "/dev/sda2". In one of those,
>>> you are more likely to find a file system and all the trimmings.
>>>
>>>     fsck -y -C -V /dev/sda1
>>>     fsck -y -C -V /dev/sda2
>>>
>>> If you use gparted
>>>
>>>     sudo gparted /dev/sda
>>>
>>> then graphically you can select some of these functions.
>>> The benefit of doing it graphically, is there will be
>>> little "hints" in the GUI, that the thing you are pointed
>>> at, is an EXT2 or a FAT32 or an NTFS. And you have a better
>>> idea what partition you are checking.
>>>
>>>     [Picture]
>>>
>>>      https://i.postimg.cc/tJ29Pz4D/gparted-graphical-info.gif
>>>
>>> You can also do
>>>
>>>     sudo disktype /dev/sda
>>>
>>> and it will print out what it finds.
>>>
>>> Or for that matter, with a booted system, try
>>>
>>>     gnome-disks
>>>
>>> and select the drive from the menu.
>>>
>>> 1) Create a partition (nominal partition type like 0x83)
>>> 2) Format it so the superblock will be there.
>>> 3) Don't mount it, if you're going to check it.
>>>     If it is mounted, then unmount it first, then check it.
>>>
>>> Mounting a partition, does a certain amount of checking anyway.
>>> The assumption is, there is a partition not currently mounted,
>>> and it does not seem interested in accepting a mount command.
>>>
>>>     Paul
>>>
>>>
>> Thanks Paul, and both sda1 and sdc5 are clean with no errors, after. I
>> ran the said cmd
>>
>> So my ssd drive is ok as is the filesystem as well as no errors with
>> my ram sticks.
>> I would deduce then that it something to do with linux mint itself??
>> On the LM forum , where I posted my problem, and I am not the only one
>> it seems, I was told to remove any powered usb adaptors, which I did 2
>> days ago. All was well until earlier today when it locked up again.
>>
>> I have yet to try your earlier suggestion with a RS232 cable.
> Is  a windows product also installed on this machine? I thought that a
> DOS partition might indicate such.

No I don't have windows on this machine, but have a disk with win10 for
my aged laptop.

I am not aware there is a DOS partition, but the boot partition is fat
32. I'm not sure how that happened as I just let the install do it's
thing at the time.

Re: Mint 21.1 Cinnamon locking up

<u9ld8n$jj54$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6537&group=alt.os.linux.mint#6537

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nos...@needed.invalid (Paul)
Newsgroups: alt.os.linux.mint
Subject: Re: Mint 21.1 Cinnamon locking up
Date: Mon, 24 Jul 2023 04:37:41 -0400
Organization: A noiseless patient Spider
Lines: 173
Message-ID: <u9ld8n$jj54$1@dont-email.me>
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
<u966tf$1luj3$1@dont-email.me> <u9675h$1m111$1@dont-email.me>
<u968mi$1m82i$1@dont-email.me>
<20230721104041.48fe31449055955e67c4911f@gmail.com>
<u9eidh$3cdpm$1@dont-email.me>
<20230721232131.47855419fb72a7136ca202bb@gmail.com>
<u9jp4n$adud$1@dont-email.me> <u9ju0q$aul5$1@dont-email.me>
<u9jvio$b2p0$1@dont-email.me> <gmgvM.18926$JG_b.13352@fx39.iad>
<u9l6sk$ip3g$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 24 Jul 2023 08:37:43 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="faee819d58fc3547ed77e5f7b64eefb5";
logging-data="642212"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/KJzPWSX7j7QkdwTElXvJhKvRTlwiBXwA="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
Cancel-Lock: sha1:24G3yCAm+tNya79bHZsCg0keA1Q=
In-Reply-To: <u9l6sk$ip3g$1@dont-email.me>
Content-Language: en-US
 by: Paul - Mon, 24 Jul 2023 08:37 UTC

On 7/24/2023 2:48 AM, Rob H wrote:
> On 23/07/2023 21:48, Nic wrote:
>> On 7/23/23 3:38 PM, Rob H wrote:
>>> On 23/07/2023 20:11, Paul wrote:
>>>> On 7/23/2023 1:48 PM, Rob H wrote:
>>>>> On 21/07/2023 23:21, pinnerite wrote:
>>>>>> On Fri, 21 Jul 2023 19:22:41 +0100
>>>>>> Rob H <rob@despammer.com> wrote:
>>>>>>
>>>>>>> On 21/07/2023 10:40, pinnerite wrote:
>>>>>>>> On Tue, 18 Jul 2023 15:47:46 +0100
>>>>>>>> Rob H <rob@despammer.com> wrote:
>>>>>>>>
>>>>>>>>> On 18/07/2023 15:21, Paul wrote:
>>>>>>>>>> sudo update-grub
>>>>>>>>>
>>>>>>>>> Thanks, yes I did that before I rebooted.
>>>>>>>>
>>>>>>>> I saw that you had tested your dram.
>>>>>>>> Just to be sure, I would test the disk drive.
>>>>>>>> I usually run:
>>>>>>>>
>>>>>>>> # fsck -y -C -V /dev/sd(x)
>>>>>>>>
>>>>>>>> before getting elaborate.
>>>>>>>>
>>>>>>>> One other thing. I highly recommend the Logitech wireless mouse.
>>>>>>>> It is very light on batteries and has not let me down since purchase about five or six years ago.
>>>>>>>>
>>>>>>>> Best of luck
>>>>>>>
>>>>>>> Thanks but silly question, how do I test the disc when it is in use
>>>>>>
>>>>>> Boot up on a live CD/DVD or flash drive.
>>>>>> My favourite's are Knoppix and Parted Magic.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> I have just booted up a live knoppix usb and ran
>>>>> fsck -y -C -V /dev/sda
>>>>>
>>>>> but got this:
>>>>> Found a dos partition table in /dev/sdc
>>>>> e2fsck_open2: Bad magic number in super block
>>>>> fsck.ext2 Superblock invalid
>>>>> fsck.ext2 Bad magic number in super-block while trying to open /dev/sda
>>>>>
>>>>> The superblock could not be read or does not describe a valid ext2/ext3/ext4 fileystem If the device is valid and it realy contains and ext2/et3/ext4 filesystem (and not aq swap or ufs or something else), then the superblock is corrupt , and you might try running e2fsck with an alternative superblock.
>>>>>
>>>>> Does it mean my filesystem is corrupt or?
>>>>>
>>>>> Thanks
>>>>>
>>>>
>>>> The identifier "/dev/sda" is the entire disk, starting at the MBR (sector 0).
>>>>
>>>> Partition identifiers are "/dev/sda1" or "/dev/sda2". In one of those,
>>>> you are more likely to find a file system and all the trimmings.
>>>>
>>>>     fsck -y -C -V /dev/sda1
>>>>     fsck -y -C -V /dev/sda2
>>>>
>>>> If you use gparted
>>>>
>>>>     sudo gparted /dev/sda
>>>>
>>>> then graphically you can select some of these functions.
>>>> The benefit of doing it graphically, is there will be
>>>> little "hints" in the GUI, that the thing you are pointed
>>>> at, is an EXT2 or a FAT32 or an NTFS. And you have a better
>>>> idea what partition you are checking.
>>>>
>>>>     [Picture]
>>>>
>>>>      https://i.postimg.cc/tJ29Pz4D/gparted-graphical-info.gif
>>>>
>>>> You can also do
>>>>
>>>>     sudo disktype /dev/sda
>>>>
>>>> and it will print out what it finds.
>>>>
>>>> Or for that matter, with a booted system, try
>>>>
>>>>     gnome-disks
>>>>
>>>> and select the drive from the menu.
>>>>
>>>> 1) Create a partition (nominal partition type like 0x83)
>>>> 2) Format it so the superblock will be there.
>>>> 3) Don't mount it, if you're going to check it.
>>>>     If it is mounted, then unmount it first, then check it.
>>>>
>>>> Mounting a partition, does a certain amount of checking anyway.
>>>> The assumption is, there is a partition not currently mounted,
>>>> and it does not seem interested in accepting a mount command.
>>>>
>>>>     Paul
>>>>
>>>>
>>> Thanks Paul, and both sda1 and sdc5 are clean with no errors, after. I ran the said cmd
>>>
>>> So my ssd drive is ok as is the filesystem as well as no errors with my ram sticks.
>>> I would deduce then that it something to do with linux mint itself??
>>> On the LM forum , where I posted my problem, and I am not the only one it seems, I was told to remove any powered usb adaptors, which I did 2 days ago. All was well until earlier today when it locked up again.
>>>
>>> I have yet to try your earlier suggestion with a RS232 cable.
>> Is  a windows product also installed on this machine? I thought that a DOS partition might indicate such.
>
> No I don't have windows on this machine, but have a disk with win10 for my aged laptop.
>
> I am not aware there is a DOS partition, but the boot partition is fat 32.
> I'm not sure how that happened as I just let the install do it's thing at the time.

UEFI uses an ESP (EFI System Partition) which is FAT32, on a GPT disk.

Presumably such a daft choice, is "free to BIOS developers", and
the parsing of FAT32, there are already simplified modules for
parsing FAT32. The choice then, was not to impress OS people, it
was to make a lighter-weight license requirement.

The FAT32 in there is not "ordinary" either. I don't understand
what part of is bodged or broken, but some of the things
listed in that partition, aren't really there. Some parts of the
FAT32 may not be entirely consistent. FAT32 has no security to
speak of, so it's not a security feature. But it can be confusing
to humans, when looking in there. Red colored items might not exist.

A sample dump, from my Windows disk.

sudo disktype /dev/sda

--- /dev/sda
Block device, size 3.639 TiB (4000787030016 bytes)
DOS/MBR partition map \
Partition 1: 2.000 TiB (2199023255040 bytes, 4294967295 sectors from 1) \___ This prevents older OSes from
Type 0xEE (EFI GPT protective) / creating partitions which conflict
with the GPT partitions...
GPT partition map, 128 entries <===\\
Disk size 3.639 TiB (4000787030016 bytes, 7814037168 sectors) \\--- GPT table is tiny, one at each
Disk GUID CD4D6752-BAC8-B446-90A7-662721F0DD2D end of disk. Failure to copy the duplicate,
leads to poorly worded diagnostic messages.
Partition 1: 100 MiB (104857600 bytes, 204800 sectors from 2048) \
Type EFI System (FAT) (GUID 28732AC1-1FF8-D211-BA4B-00A0C93EC93B) \
Partition Name "EFI system partition" \___ ESP, Windows makes 100MB, Linux likes 300+
Partition GUID BE145A8D-FC87-9B45-AFB1-8959CB4D727A / Folder for Windows, Folder for Ubuntu,
FAT32 file system (hints score 4 of 5) / Linux Mint may be sharing the Ubuntu one.
Volume size 96 MiB (100663296 bytes, 98304 clusters of 1 KiB) /

Partition 2: 16 MiB (16777216 bytes, 32768 sectors from 206848) \
Type MS Reserved (GUID 16E3C9E3-5C0B-B84D-817D-F92DF00215AE) \___ gparted can't move this (no file system),
Partition Name "Microsoft reserved partition" / but Macrium treats all "foreign" items with
Partition GUID B000A1BB-661C-7541-AF97-88BB60627F66 / dd transfers, as its solution to moving.

Partition 3: 118.7 GiB (127481675776 bytes, 248987648 sectors from 239616) \
Type Basic Data (GUID A2A0D0EB-E5B9-3344-87C0-68B6B72699C7) \
Partition Name "Basic data partition" \___ Windows NTFS
Partition GUID 6A16D60B-3608-4140-891C-792DF2C72ABD /
NTFS file system /
Volume size 118.7 GiB (127481675264 bytes, 248987647 sectors)


Click here to read the complete article
Re: Mint 21.1 Cinnamon locking up

<6tsvM.154025$TPw2.151097@fx17.iad>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6538&group=alt.os.linux.mint#6538

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx17.iad.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.13.0
Reply-To: Nic@none.net
Subject: Re: Mint 21.1 Cinnamon locking up
Newsgroups: alt.os.linux.mint
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
<u966tf$1luj3$1@dont-email.me> <u9675h$1m111$1@dont-email.me>
<u968mi$1m82i$1@dont-email.me>
<20230721104041.48fe31449055955e67c4911f@gmail.com>
<u9eidh$3cdpm$1@dont-email.me>
<20230721232131.47855419fb72a7136ca202bb@gmail.com>
<u9jp4n$adud$1@dont-email.me> <u9ju0q$aul5$1@dont-email.me>
<u9jvio$b2p0$1@dont-email.me> <gmgvM.18926$JG_b.13352@fx39.iad>
<u9l6sk$ip3g$1@dont-email.me>
Content-Language: en-US
From: Nic...@none.net (Nic)
Organization: Arm Chair Observer
In-Reply-To: <u9l6sk$ip3g$1@dont-email.me>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Lines: 137
Message-ID: <6tsvM.154025$TPw2.151097@fx17.iad>
X-Complaints-To: abuse(at)newshosting.com
NNTP-Posting-Date: Mon, 24 Jul 2023 10:34:42 UTC
Date: Mon, 24 Jul 2023 06:34:42 -0400
X-Received-Bytes: 6428
 by: Nic - Mon, 24 Jul 2023 10:34 UTC

On 7/24/23 2:48 AM, Rob H wrote:
> On 23/07/2023 21:48, Nic wrote:
>> On 7/23/23 3:38 PM, Rob H wrote:
>>> On 23/07/2023 20:11, Paul wrote:
>>>> On 7/23/2023 1:48 PM, Rob H wrote:
>>>>> On 21/07/2023 23:21, pinnerite wrote:
>>>>>> On Fri, 21 Jul 2023 19:22:41 +0100
>>>>>> Rob H <rob@despammer.com> wrote:
>>>>>>
>>>>>>> On 21/07/2023 10:40, pinnerite wrote:
>>>>>>>> On Tue, 18 Jul 2023 15:47:46 +0100
>>>>>>>> Rob H <rob@despammer.com> wrote:
>>>>>>>>
>>>>>>>>> On 18/07/2023 15:21, Paul wrote:
>>>>>>>>>> sudo update-grub
>>>>>>>>>
>>>>>>>>> Thanks, yes I did that before I rebooted.
>>>>>>>>
>>>>>>>> I saw that you had tested your dram.
>>>>>>>> Just to be sure, I would test the disk drive.
>>>>>>>> I usually run:
>>>>>>>>
>>>>>>>> # fsck -y -C -V /dev/sd(x)
>>>>>>>>
>>>>>>>> before getting elaborate.
>>>>>>>>
>>>>>>>> One other thing. I highly recommend the Logitech wireless mouse.
>>>>>>>> It is very light on batteries and has not let me down since
>>>>>>>> purchase about five or six years ago.
>>>>>>>>
>>>>>>>> Best of luck
>>>>>>>
>>>>>>> Thanks but silly question, how do I test the disc when it is in use
>>>>>>
>>>>>> Boot up on a live CD/DVD or flash drive.
>>>>>> My favourite's are Knoppix and Parted Magic.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> I have just booted up a live knoppix usb and ran
>>>>> fsck -y -C -V /dev/sda
>>>>>
>>>>> but got this:
>>>>> Found a dos partition table in /dev/sdc
>>>>> e2fsck_open2: Bad magic number in super block
>>>>> fsck.ext2 Superblock invalid
>>>>> fsck.ext2 Bad magic number in super-block while trying to open
>>>>> /dev/sda
>>>>>
>>>>> The superblock could not be read or does not describe a valid
>>>>> ext2/ext3/ext4 fileystem If the device is valid and it realy
>>>>> contains and ext2/et3/ext4 filesystem (and not aq swap or ufs or
>>>>> something else), then the superblock is corrupt , and you might
>>>>> try running e2fsck with an alternative superblock.
>>>>>
>>>>> Does it mean my filesystem is corrupt or?
>>>>>
>>>>> Thanks
>>>>>
>>>>
>>>> The identifier "/dev/sda" is the entire disk, starting at the MBR
>>>> (sector 0).
>>>>
>>>> Partition identifiers are "/dev/sda1" or "/dev/sda2". In one of those,
>>>> you are more likely to find a file system and all the trimmings.
>>>>
>>>>     fsck -y -C -V /dev/sda1
>>>>     fsck -y -C -V /dev/sda2
>>>>
>>>> If you use gparted
>>>>
>>>>     sudo gparted /dev/sda
>>>>
>>>> then graphically you can select some of these functions.
>>>> The benefit of doing it graphically, is there will be
>>>> little "hints" in the GUI, that the thing you are pointed
>>>> at, is an EXT2 or a FAT32 or an NTFS. And you have a better
>>>> idea what partition you are checking.
>>>>
>>>>     [Picture]
>>>>
>>>> https://i.postimg.cc/tJ29Pz4D/gparted-graphical-info.gif
>>>>
>>>> You can also do
>>>>
>>>>     sudo disktype /dev/sda
>>>>
>>>> and it will print out what it finds.
>>>>
>>>> Or for that matter, with a booted system, try
>>>>
>>>>     gnome-disks
>>>>
>>>> and select the drive from the menu.
>>>>
>>>> 1) Create a partition (nominal partition type like 0x83)
>>>> 2) Format it so the superblock will be there.
>>>> 3) Don't mount it, if you're going to check it.
>>>>     If it is mounted, then unmount it first, then check it.
>>>>
>>>> Mounting a partition, does a certain amount of checking anyway.
>>>> The assumption is, there is a partition not currently mounted,
>>>> and it does not seem interested in accepting a mount command.
>>>>
>>>>     Paul
>>>>
>>>>
>>> Thanks Paul, and both sda1 and sdc5 are clean with no errors, after.
>>> I ran the said cmd
>>>
>>> So my ssd drive is ok as is the filesystem as well as no errors with
>>> my ram sticks.
>>> I would deduce then that it something to do with linux mint itself??
>>> On the LM forum , where I posted my problem, and I am not the only
>>> one it seems, I was told to remove any powered usb adaptors, which I
>>> did 2 days ago. All was well until earlier today when it locked up
>>> again.
>>>
>>> I have yet to try your earlier suggestion with a RS232 cable.
>> Is  a windows product also installed on this machine? I thought that
>> a DOS partition might indicate such.
>
> No I don't have windows on this machine, but have a disk with win10
> for my aged laptop.
>
> I am not aware there is a DOS partition, but the boot partition is fat
> 32. I'm not sure how that happened as I just let the install do it's
> thing at the time.
From your post "I have just booted up a live knoppix usb and ran
fsck -y -C -V /dev/sda

but got this:
Found a dos partition table in /dev/sdc"     How do you interpret this
message? What is the purpose of the dos partition table? Question: How
many drives are in this machine?

Re: Mint 21.1 Cinnamon locking up

<u9m6rn$nebe$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6539&group=alt.os.linux.mint#6539

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: rob...@despammer.com (Rob H)
Newsgroups: alt.os.linux.mint
Subject: Re: Mint 21.1 Cinnamon locking up
Date: Mon, 24 Jul 2023 16:54:31 +0100
Organization: A noiseless patient Spider
Lines: 150
Message-ID: <u9m6rn$nebe$1@dont-email.me>
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
<u966tf$1luj3$1@dont-email.me> <u9675h$1m111$1@dont-email.me>
<u968mi$1m82i$1@dont-email.me>
<20230721104041.48fe31449055955e67c4911f@gmail.com>
<u9eidh$3cdpm$1@dont-email.me>
<20230721232131.47855419fb72a7136ca202bb@gmail.com>
<u9jp4n$adud$1@dont-email.me> <u9ju0q$aul5$1@dont-email.me>
<u9jvio$b2p0$1@dont-email.me> <gmgvM.18926$JG_b.13352@fx39.iad>
<u9l6sk$ip3g$1@dont-email.me> <6tsvM.154025$TPw2.151097@fx17.iad>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 24 Jul 2023 15:54:31 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="872a5e5c4136f266ad462ffbf8f20340";
logging-data="768366"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX187g6I8RqlfiokhmGM7cEYc"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.13.0
Cancel-Lock: sha1:/jN2SanMdqDkn8Q04myLfR6Ya/E=
In-Reply-To: <6tsvM.154025$TPw2.151097@fx17.iad>
Content-Language: en-US
 by: Rob H - Mon, 24 Jul 2023 15:54 UTC

On 24/07/2023 11:34, Nic wrote:
> On 7/24/23 2:48 AM, Rob H wrote:
>> On 23/07/2023 21:48, Nic wrote:
>>> On 7/23/23 3:38 PM, Rob H wrote:
>>>> On 23/07/2023 20:11, Paul wrote:
>>>>> On 7/23/2023 1:48 PM, Rob H wrote:
>>>>>> On 21/07/2023 23:21, pinnerite wrote:
>>>>>>> On Fri, 21 Jul 2023 19:22:41 +0100
>>>>>>> Rob H <rob@despammer.com> wrote:
>>>>>>>
>>>>>>>> On 21/07/2023 10:40, pinnerite wrote:
>>>>>>>>> On Tue, 18 Jul 2023 15:47:46 +0100
>>>>>>>>> Rob H <rob@despammer.com> wrote:
>>>>>>>>>
>>>>>>>>>> On 18/07/2023 15:21, Paul wrote:
>>>>>>>>>>> sudo update-grub
>>>>>>>>>>
>>>>>>>>>> Thanks, yes I did that before I rebooted.
>>>>>>>>>
>>>>>>>>> I saw that you had tested your dram.
>>>>>>>>> Just to be sure, I would test the disk drive.
>>>>>>>>> I usually run:
>>>>>>>>>
>>>>>>>>> # fsck -y -C -V /dev/sd(x)
>>>>>>>>>
>>>>>>>>> before getting elaborate.
>>>>>>>>>
>>>>>>>>> One other thing. I highly recommend the Logitech wireless mouse.
>>>>>>>>> It is very light on batteries and has not let me down since
>>>>>>>>> purchase about five or six years ago.
>>>>>>>>>
>>>>>>>>> Best of luck
>>>>>>>>
>>>>>>>> Thanks but silly question, how do I test the disc when it is in use
>>>>>>>
>>>>>>> Boot up on a live CD/DVD or flash drive.
>>>>>>> My favourite's are Knoppix and Parted Magic.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> I have just booted up a live knoppix usb and ran
>>>>>> fsck -y -C -V /dev/sda
>>>>>>
>>>>>> but got this:
>>>>>> Found a dos partition table in /dev/sdc
>>>>>> e2fsck_open2: Bad magic number in super block
>>>>>> fsck.ext2 Superblock invalid
>>>>>> fsck.ext2 Bad magic number in super-block while trying to open
>>>>>> /dev/sda
>>>>>>
>>>>>> The superblock could not be read or does not describe a valid
>>>>>> ext2/ext3/ext4 fileystem If the device is valid and it realy
>>>>>> contains and ext2/et3/ext4 filesystem (and not aq swap or ufs or
>>>>>> something else), then the superblock is corrupt , and you might
>>>>>> try running e2fsck with an alternative superblock.
>>>>>>
>>>>>> Does it mean my filesystem is corrupt or?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>
>>>>> The identifier "/dev/sda" is the entire disk, starting at the MBR
>>>>> (sector 0).
>>>>>
>>>>> Partition identifiers are "/dev/sda1" or "/dev/sda2". In one of those,
>>>>> you are more likely to find a file system and all the trimmings.
>>>>>
>>>>>     fsck -y -C -V /dev/sda1
>>>>>     fsck -y -C -V /dev/sda2
>>>>>
>>>>> If you use gparted
>>>>>
>>>>>     sudo gparted /dev/sda
>>>>>
>>>>> then graphically you can select some of these functions.
>>>>> The benefit of doing it graphically, is there will be
>>>>> little "hints" in the GUI, that the thing you are pointed
>>>>> at, is an EXT2 or a FAT32 or an NTFS. And you have a better
>>>>> idea what partition you are checking.
>>>>>
>>>>>     [Picture]
>>>>>
>>>>> https://i.postimg.cc/tJ29Pz4D/gparted-graphical-info.gif
>>>>>
>>>>> You can also do
>>>>>
>>>>>     sudo disktype /dev/sda
>>>>>
>>>>> and it will print out what it finds.
>>>>>
>>>>> Or for that matter, with a booted system, try
>>>>>
>>>>>     gnome-disks
>>>>>
>>>>> and select the drive from the menu.
>>>>>
>>>>> 1) Create a partition (nominal partition type like 0x83)
>>>>> 2) Format it so the superblock will be there.
>>>>> 3) Don't mount it, if you're going to check it.
>>>>>     If it is mounted, then unmount it first, then check it.
>>>>>
>>>>> Mounting a partition, does a certain amount of checking anyway.
>>>>> The assumption is, there is a partition not currently mounted,
>>>>> and it does not seem interested in accepting a mount command.
>>>>>
>>>>>     Paul
>>>>>
>>>>>
>>>> Thanks Paul, and both sda1 and sdc5 are clean with no errors, after.
>>>> I ran the said cmd
>>>>
>>>> So my ssd drive is ok as is the filesystem as well as no errors with
>>>> my ram sticks.
>>>> I would deduce then that it something to do with linux mint itself??
>>>> On the LM forum , where I posted my problem, and I am not the only
>>>> one it seems, I was told to remove any powered usb adaptors, which I
>>>> did 2 days ago. All was well until earlier today when it locked up
>>>> again.
>>>>
>>>> I have yet to try your earlier suggestion with a RS232 cable.
>>> Is  a windows product also installed on this machine? I thought that
>>> a DOS partition might indicate such.
>>
>> No I don't have windows on this machine, but have a disk with win10
>> for my aged laptop.
>>
>> I am not aware there is a DOS partition, but the boot partition is fat
>> 32. I'm not sure how that happened as I just let the install do it's
>> thing at the time.
> From your post "I have just booted up a live knoppix usb and ran
> fsck -y -C -V /dev/sda
>
> but got this:
> Found a dos partition table in /dev/sdc"     How do you interpret this
> message? What is the purpose of the dos partition table? Question: How
> many drives are in this machine?

There are x2 250Gb ssd drives, 1 for the boot partition and the other
for my /home partition.
There is also a 3rd spinning disc drive which I use for some backups.

just for information, my machine locked at about 10.30am this morning,
and I have been out since then to about 4.45pm , and the machine was
still locked up.

I am now thinking about doing a new reinstall of LM, but I'm not sure if
that would cure the problem.

Re: Mint 21.1 Cinnamon locking up

<DAxvM.43052$uEkc.38019@fx35.iad>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6540&group=alt.os.linux.mint#6540

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx35.iad.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.13.0
Reply-To: Nic@none.net
Subject: Re: Mint 21.1 Cinnamon locking up
Newsgroups: alt.os.linux.mint
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
<u966tf$1luj3$1@dont-email.me> <u9675h$1m111$1@dont-email.me>
<u968mi$1m82i$1@dont-email.me>
<20230721104041.48fe31449055955e67c4911f@gmail.com>
<u9eidh$3cdpm$1@dont-email.me>
<20230721232131.47855419fb72a7136ca202bb@gmail.com>
<u9jp4n$adud$1@dont-email.me> <u9ju0q$aul5$1@dont-email.me>
<u9jvio$b2p0$1@dont-email.me> <gmgvM.18926$JG_b.13352@fx39.iad>
<u9l6sk$ip3g$1@dont-email.me> <6tsvM.154025$TPw2.151097@fx17.iad>
<u9m6rn$nebe$1@dont-email.me>
Content-Language: en-US
From: Nic...@none.net (Nic)
Organization: Arm Chair Observer
In-Reply-To: <u9m6rn$nebe$1@dont-email.me>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Lines: 154
Message-ID: <DAxvM.43052$uEkc.38019@fx35.iad>
X-Complaints-To: abuse(at)newshosting.com
NNTP-Posting-Date: Mon, 24 Jul 2023 16:24:03 UTC
Date: Mon, 24 Jul 2023 12:24:03 -0400
X-Received-Bytes: 7379
 by: Nic - Mon, 24 Jul 2023 16:24 UTC

On 7/24/23 11:54 AM, Rob H wrote:
> On 24/07/2023 11:34, Nic wrote:
>> On 7/24/23 2:48 AM, Rob H wrote:
>>> On 23/07/2023 21:48, Nic wrote:
>>>> On 7/23/23 3:38 PM, Rob H wrote:
>>>>> On 23/07/2023 20:11, Paul wrote:
>>>>>> On 7/23/2023 1:48 PM, Rob H wrote:
>>>>>>> On 21/07/2023 23:21, pinnerite wrote:
>>>>>>>> On Fri, 21 Jul 2023 19:22:41 +0100
>>>>>>>> Rob H <rob@despammer.com> wrote:
>>>>>>>>
>>>>>>>>> On 21/07/2023 10:40, pinnerite wrote:
>>>>>>>>>> On Tue, 18 Jul 2023 15:47:46 +0100
>>>>>>>>>> Rob H <rob@despammer.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> On 18/07/2023 15:21, Paul wrote:
>>>>>>>>>>>> sudo update-grub
>>>>>>>>>>>
>>>>>>>>>>> Thanks, yes I did that before I rebooted.
>>>>>>>>>>
>>>>>>>>>> I saw that you had tested your dram.
>>>>>>>>>> Just to be sure, I would test the disk drive.
>>>>>>>>>> I usually run:
>>>>>>>>>>
>>>>>>>>>> # fsck -y -C -V /dev/sd(x)
>>>>>>>>>>
>>>>>>>>>> before getting elaborate.
>>>>>>>>>>
>>>>>>>>>> One other thing. I highly recommend the Logitech wireless mouse.
>>>>>>>>>> It is very light on batteries and has not let me down since
>>>>>>>>>> purchase about five or six years ago.
>>>>>>>>>>
>>>>>>>>>> Best of luck
>>>>>>>>>
>>>>>>>>> Thanks but silly question, how do I test the disc when it is
>>>>>>>>> in use
>>>>>>>>
>>>>>>>> Boot up on a live CD/DVD or flash drive.
>>>>>>>> My favourite's are Knoppix and Parted Magic.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> I have just booted up a live knoppix usb and ran
>>>>>>> fsck -y -C -V /dev/sda
>>>>>>>
>>>>>>> but got this:
>>>>>>> Found a dos partition table in /dev/sdc
>>>>>>> e2fsck_open2: Bad magic number in super block
>>>>>>> fsck.ext2 Superblock invalid
>>>>>>> fsck.ext2 Bad magic number in super-block while trying to open
>>>>>>> /dev/sda
>>>>>>>
>>>>>>> The superblock could not be read or does not describe a valid
>>>>>>> ext2/ext3/ext4 fileystem If the device is valid and it realy
>>>>>>> contains and ext2/et3/ext4 filesystem (and not aq swap or ufs or
>>>>>>> something else), then the superblock is corrupt , and you might
>>>>>>> try running e2fsck with an alternative superblock.
>>>>>>>
>>>>>>> Does it mean my filesystem is corrupt or?
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>
>>>>>> The identifier "/dev/sda" is the entire disk, starting at the MBR
>>>>>> (sector 0).
>>>>>>
>>>>>> Partition identifiers are "/dev/sda1" or "/dev/sda2". In one of
>>>>>> those,
>>>>>> you are more likely to find a file system and all the trimmings.
>>>>>>
>>>>>>     fsck -y -C -V /dev/sda1
>>>>>>     fsck -y -C -V /dev/sda2
>>>>>>
>>>>>> If you use gparted
>>>>>>
>>>>>>     sudo gparted /dev/sda
>>>>>>
>>>>>> then graphically you can select some of these functions.
>>>>>> The benefit of doing it graphically, is there will be
>>>>>> little "hints" in the GUI, that the thing you are pointed
>>>>>> at, is an EXT2 or a FAT32 or an NTFS. And you have a better
>>>>>> idea what partition you are checking.
>>>>>>
>>>>>>     [Picture]
>>>>>>
>>>>>> https://i.postimg.cc/tJ29Pz4D/gparted-graphical-info.gif
>>>>>>
>>>>>> You can also do
>>>>>>
>>>>>>     sudo disktype /dev/sda
>>>>>>
>>>>>> and it will print out what it finds.
>>>>>>
>>>>>> Or for that matter, with a booted system, try
>>>>>>
>>>>>>     gnome-disks
>>>>>>
>>>>>> and select the drive from the menu.
>>>>>>
>>>>>> 1) Create a partition (nominal partition type like 0x83)
>>>>>> 2) Format it so the superblock will be there.
>>>>>> 3) Don't mount it, if you're going to check it.
>>>>>>     If it is mounted, then unmount it first, then check it.
>>>>>>
>>>>>> Mounting a partition, does a certain amount of checking anyway.
>>>>>> The assumption is, there is a partition not currently mounted,
>>>>>> and it does not seem interested in accepting a mount command.
>>>>>>
>>>>>>     Paul
>>>>>>
>>>>>>
>>>>> Thanks Paul, and both sda1 and sdc5 are clean with no errors,
>>>>> after. I ran the said cmd
>>>>>
>>>>> So my ssd drive is ok as is the filesystem as well as no errors
>>>>> with my ram sticks.
>>>>> I would deduce then that it something to do with linux mint itself??
>>>>> On the LM forum , where I posted my problem, and I am not the only
>>>>> one it seems, I was told to remove any powered usb adaptors, which
>>>>> I did 2 days ago. All was well until earlier today when it locked
>>>>> up again.
>>>>>
>>>>> I have yet to try your earlier suggestion with a RS232 cable.
>>>> Is  a windows product also installed on this machine? I thought
>>>> that a DOS partition might indicate such.
>>>
>>> No I don't have windows on this machine, but have a disk with win10
>>> for my aged laptop.
>>>
>>> I am not aware there is a DOS partition, but the boot partition is
>>> fat 32. I'm not sure how that happened as I just let the install do
>>> it's thing at the time.
>>  From your post "I have just booted up a live knoppix usb and ran
>> fsck -y -C -V /dev/sda
>>
>> but got this:
>> Found a dos partition table in /dev/sdc"     How do you interpret
>> this message? What is the purpose of the dos partition table?
>> Question: How many drives are in this machine?
>
> There are x2 250Gb ssd drives, 1 for the boot partition and the other
> for my /home partition.
> There is also a 3rd spinning disc drive which I use for some backups.
>
> just for information, my machine locked at about 10.30am this morning,
> and I have been out since then to about 4.45pm , and the machine was
> still locked up.
>
> I am now thinking about doing a new reinstall of LM, but I'm not sure
> if that would cure the problem.
>
Take a look at the syslog in the Home directory

Re: Mint 21.1 Cinnamon locking up

<u9m9pv$ns47$1@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6541&group=alt.os.linux.mint#6541

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: rob...@despammer.com (Rob H)
Newsgroups: alt.os.linux.mint
Subject: Re: Mint 21.1 Cinnamon locking up
Date: Mon, 24 Jul 2023 17:44:47 +0100
Organization: A noiseless patient Spider
Lines: 158
Message-ID: <u9m9pv$ns47$1@dont-email.me>
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
<u966tf$1luj3$1@dont-email.me> <u9675h$1m111$1@dont-email.me>
<u968mi$1m82i$1@dont-email.me>
<20230721104041.48fe31449055955e67c4911f@gmail.com>
<u9eidh$3cdpm$1@dont-email.me>
<20230721232131.47855419fb72a7136ca202bb@gmail.com>
<u9jp4n$adud$1@dont-email.me> <u9ju0q$aul5$1@dont-email.me>
<u9jvio$b2p0$1@dont-email.me> <gmgvM.18926$JG_b.13352@fx39.iad>
<u9l6sk$ip3g$1@dont-email.me> <6tsvM.154025$TPw2.151097@fx17.iad>
<u9m6rn$nebe$1@dont-email.me> <DAxvM.43052$uEkc.38019@fx35.iad>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 24 Jul 2023 16:44:47 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="872a5e5c4136f266ad462ffbf8f20340";
logging-data="782471"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18mv5wlD1Je+TM4wub7ly7Z"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.13.0
Cancel-Lock: sha1:yWBnTaVYxx5+aNWsYl0UfP/YXRw=
Content-Language: en-US
In-Reply-To: <DAxvM.43052$uEkc.38019@fx35.iad>
 by: Rob H - Mon, 24 Jul 2023 16:44 UTC

On 24/07/2023 17:24, Nic wrote:
> On 7/24/23 11:54 AM, Rob H wrote:
>> On 24/07/2023 11:34, Nic wrote:
>>> On 7/24/23 2:48 AM, Rob H wrote:
>>>> On 23/07/2023 21:48, Nic wrote:
>>>>> On 7/23/23 3:38 PM, Rob H wrote:
>>>>>> On 23/07/2023 20:11, Paul wrote:
>>>>>>> On 7/23/2023 1:48 PM, Rob H wrote:
>>>>>>>> On 21/07/2023 23:21, pinnerite wrote:
>>>>>>>>> On Fri, 21 Jul 2023 19:22:41 +0100
>>>>>>>>> Rob H <rob@despammer.com> wrote:
>>>>>>>>>
>>>>>>>>>> On 21/07/2023 10:40, pinnerite wrote:
>>>>>>>>>>> On Tue, 18 Jul 2023 15:47:46 +0100
>>>>>>>>>>> Rob H <rob@despammer.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> On 18/07/2023 15:21, Paul wrote:
>>>>>>>>>>>>> sudo update-grub
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks, yes I did that before I rebooted.
>>>>>>>>>>>
>>>>>>>>>>> I saw that you had tested your dram.
>>>>>>>>>>> Just to be sure, I would test the disk drive.
>>>>>>>>>>> I usually run:
>>>>>>>>>>>
>>>>>>>>>>> # fsck -y -C -V /dev/sd(x)
>>>>>>>>>>>
>>>>>>>>>>> before getting elaborate.
>>>>>>>>>>>
>>>>>>>>>>> One other thing. I highly recommend the Logitech wireless mouse.
>>>>>>>>>>> It is very light on batteries and has not let me down since
>>>>>>>>>>> purchase about five or six years ago.
>>>>>>>>>>>
>>>>>>>>>>> Best of luck
>>>>>>>>>>
>>>>>>>>>> Thanks but silly question, how do I test the disc when it is
>>>>>>>>>> in use
>>>>>>>>>
>>>>>>>>> Boot up on a live CD/DVD or flash drive.
>>>>>>>>> My favourite's are Knoppix and Parted Magic.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> I have just booted up a live knoppix usb and ran
>>>>>>>> fsck -y -C -V /dev/sda
>>>>>>>>
>>>>>>>> but got this:
>>>>>>>> Found a dos partition table in /dev/sdc
>>>>>>>> e2fsck_open2: Bad magic number in super block
>>>>>>>> fsck.ext2 Superblock invalid
>>>>>>>> fsck.ext2 Bad magic number in super-block while trying to open
>>>>>>>> /dev/sda
>>>>>>>>
>>>>>>>> The superblock could not be read or does not describe a valid
>>>>>>>> ext2/ext3/ext4 fileystem If the device is valid and it realy
>>>>>>>> contains and ext2/et3/ext4 filesystem (and not aq swap or ufs or
>>>>>>>> something else), then the superblock is corrupt , and you might
>>>>>>>> try running e2fsck with an alternative superblock.
>>>>>>>>
>>>>>>>> Does it mean my filesystem is corrupt or?
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>
>>>>>>> The identifier "/dev/sda" is the entire disk, starting at the MBR
>>>>>>> (sector 0).
>>>>>>>
>>>>>>> Partition identifiers are "/dev/sda1" or "/dev/sda2". In one of
>>>>>>> those,
>>>>>>> you are more likely to find a file system and all the trimmings.
>>>>>>>
>>>>>>>     fsck -y -C -V /dev/sda1
>>>>>>>     fsck -y -C -V /dev/sda2
>>>>>>>
>>>>>>> If you use gparted
>>>>>>>
>>>>>>>     sudo gparted /dev/sda
>>>>>>>
>>>>>>> then graphically you can select some of these functions.
>>>>>>> The benefit of doing it graphically, is there will be
>>>>>>> little "hints" in the GUI, that the thing you are pointed
>>>>>>> at, is an EXT2 or a FAT32 or an NTFS. And you have a better
>>>>>>> idea what partition you are checking.
>>>>>>>
>>>>>>>     [Picture]
>>>>>>>
>>>>>>> https://i.postimg.cc/tJ29Pz4D/gparted-graphical-info.gif
>>>>>>>
>>>>>>> You can also do
>>>>>>>
>>>>>>>     sudo disktype /dev/sda
>>>>>>>
>>>>>>> and it will print out what it finds.
>>>>>>>
>>>>>>> Or for that matter, with a booted system, try
>>>>>>>
>>>>>>>     gnome-disks
>>>>>>>
>>>>>>> and select the drive from the menu.
>>>>>>>
>>>>>>> 1) Create a partition (nominal partition type like 0x83)
>>>>>>> 2) Format it so the superblock will be there.
>>>>>>> 3) Don't mount it, if you're going to check it.
>>>>>>>     If it is mounted, then unmount it first, then check it.
>>>>>>>
>>>>>>> Mounting a partition, does a certain amount of checking anyway.
>>>>>>> The assumption is, there is a partition not currently mounted,
>>>>>>> and it does not seem interested in accepting a mount command.
>>>>>>>
>>>>>>>     Paul
>>>>>>>
>>>>>>>
>>>>>> Thanks Paul, and both sda1 and sdc5 are clean with no errors,
>>>>>> after. I ran the said cmd
>>>>>>
>>>>>> So my ssd drive is ok as is the filesystem as well as no errors
>>>>>> with my ram sticks.
>>>>>> I would deduce then that it something to do with linux mint itself??
>>>>>> On the LM forum , where I posted my problem, and I am not the only
>>>>>> one it seems, I was told to remove any powered usb adaptors, which
>>>>>> I did 2 days ago. All was well until earlier today when it locked
>>>>>> up again.
>>>>>>
>>>>>> I have yet to try your earlier suggestion with a RS232 cable.
>>>>> Is  a windows product also installed on this machine? I thought
>>>>> that a DOS partition might indicate such.
>>>>
>>>> No I don't have windows on this machine, but have a disk with win10
>>>> for my aged laptop.
>>>>
>>>> I am not aware there is a DOS partition, but the boot partition is
>>>> fat 32. I'm not sure how that happened as I just let the install do
>>>> it's thing at the time.
>>>  From your post "I have just booted up a live knoppix usb and ran
>>> fsck -y -C -V /dev/sda
>>>
>>> but got this:
>>> Found a dos partition table in /dev/sdc"     How do you interpret
>>> this message? What is the purpose of the dos partition table?
>>> Question: How many drives are in this machine?
>>
>> There are x2 250Gb ssd drives, 1 for the boot partition and the other
>> for my /home partition.
>> There is also a 3rd spinning disc drive which I use for some backups.
>>
>> just for information, my machine locked at about 10.30am this morning,
>> and I have been out since then to about 4.45pm , and the machine was
>> still locked up.
>>
>> I am now thinking about doing a new reinstall of LM, but I'm not sure
>> if that would cure the problem.
>>
> Take a look at the syslog in the Home directory

syslog not found even after showing hidden files in the home directory

Re: Mint 21.1 Cinnamon locking up

<u9ma7o$ns47$2@dont-email.me>

 copy mid

https://www.novabbs.com/computers/article-flat.php?id=6542&group=alt.os.linux.mint#6542

 copy link   Newsgroups: alt.os.linux.mint
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: rob...@despammer.com (Rob H)
Newsgroups: alt.os.linux.mint
Subject: Re: Mint 21.1 Cinnamon locking up
Date: Mon, 24 Jul 2023 17:52:08 +0100
Organization: A noiseless patient Spider
Lines: 168
Message-ID: <u9ma7o$ns47$2@dont-email.me>
References: <u90k23$oje8$1@dont-email.me> <CvXsM.338180$edN3.303956@fx14.iad>
<u91h4o$rh8r$1@dont-email.me> <mQXsM.126126$OwWc.21600@fx45.iad>
<u91ho2$rjgn$1@dont-email.me> <u3YsM.58883$_2s1.44233@fx44.iad>
<u91pmf$seiv$1@dont-email.me> <u93vnh$1af0g$1@dont-email.me>
<u94b56$1bnbl$1@dont-email.me> <u94bl8$1bop5$1@dont-email.me>
<u94uig$1hdqu$1@dont-email.me> <u95dng$1ikgf$1@dont-email.me>
<u95kri$1jca9$1@dont-email.me> <u95uo1$1kmq0$1@dont-email.me>
<u966tf$1luj3$1@dont-email.me> <u9675h$1m111$1@dont-email.me>
<u968mi$1m82i$1@dont-email.me>
<20230721104041.48fe31449055955e67c4911f@gmail.com>
<u9eidh$3cdpm$1@dont-email.me>
<20230721232131.47855419fb72a7136ca202bb@gmail.com>
<u9jp4n$adud$1@dont-email.me> <u9ju0q$aul5$1@dont-email.me>
<u9jvio$b2p0$1@dont-email.me> <gmgvM.18926$JG_b.13352@fx39.iad>
<u9l6sk$ip3g$1@dont-email.me> <6tsvM.154025$TPw2.151097@fx17.iad>
<u9m6rn$nebe$1@dont-email.me> <DAxvM.43052$uEkc.38019@fx35.iad>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 24 Jul 2023 16:52:08 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="872a5e5c4136f266ad462ffbf8f20340";
logging-data="782471"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/24AVyTC2b2jbD6Sk618zF"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.13.0
Cancel-Lock: sha1:Xy84Cfs1G9bkTUp6iMIZrROkfYY=
In-Reply-To: <DAxvM.43052$uEkc.38019@fx35.iad>
Content-Language: en-US
 by: Rob H - Mon, 24 Jul 2023 16:52 UTC

On 24/07/2023 17:24, Nic wrote:
> On 7/24/23 11:54 AM, Rob H wrote:
>> On 24/07/2023 11:34, Nic wrote:
>>> On 7/24/23 2:48 AM, Rob H wrote:
>>>> On 23/07/2023 21:48, Nic wrote:
>>>>> On 7/23/23 3:38 PM, Rob H wrote:
>>>>>> On 23/07/2023 20:11, Paul wrote:
>>>>>>> On 7/23/2023 1:48 PM, Rob H wrote:
>>>>>>>> On 21/07/2023 23:21, pinnerite wrote:
>>>>>>>>> On Fri, 21 Jul 2023 19:22:41 +0100
>>>>>>>>> Rob H <rob@despammer.com> wrote:
>>>>>>>>>
>>>>>>>>>> On 21/07/2023 10:40, pinnerite wrote:
>>>>>>>>>>> On Tue, 18 Jul 2023 15:47:46 +0100
>>>>>>>>>>> Rob H <rob@despammer.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> On 18/07/2023 15:21, Paul wrote:
>>>>>>>>>>>>> sudo update-grub
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks, yes I did that before I rebooted.
>>>>>>>>>>>
>>>>>>>>>>> I saw that you had tested your dram.
>>>>>>>>>>> Just to be sure, I would test the disk drive.
>>>>>>>>>>> I usually run:
>>>>>>>>>>>
>>>>>>>>>>> # fsck -y -C -V /dev/sd(x)
>>>>>>>>>>>
>>>>>>>>>>> before getting elaborate.
>>>>>>>>>>>
>>>>>>>>>>> One other thing. I highly recommend the Logitech wireless mouse.
>>>>>>>>>>> It is very light on batteries and has not let me down since
>>>>>>>>>>> purchase about five or six years ago.
>>>>>>>>>>>
>>>>>>>>>>> Best of luck
>>>>>>>>>>
>>>>>>>>>> Thanks but silly question, how do I test the disc when it is
>>>>>>>>>> in use
>>>>>>>>>
>>>>>>>>> Boot up on a live CD/DVD or flash drive.
>>>>>>>>> My favourite's are Knoppix and Parted Magic.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> I have just booted up a live knoppix usb and ran
>>>>>>>> fsck -y -C -V /dev/sda
>>>>>>>>
>>>>>>>> but got this:
>>>>>>>> Found a dos partition table in /dev/sdc
>>>>>>>> e2fsck_open2: Bad magic number in super block
>>>>>>>> fsck.ext2 Superblock invalid
>>>>>>>> fsck.ext2 Bad magic number in super-block while trying to open
>>>>>>>> /dev/sda
>>>>>>>>
>>>>>>>> The superblock could not be read or does not describe a valid
>>>>>>>> ext2/ext3/ext4 fileystem If the device is valid and it realy
>>>>>>>> contains and ext2/et3/ext4 filesystem (and not aq swap or ufs or
>>>>>>>> something else), then the superblock is corrupt , and you might
>>>>>>>> try running e2fsck with an alternative superblock.
>>>>>>>>
>>>>>>>> Does it mean my filesystem is corrupt or?
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>
>>>>>>> The identifier "/dev/sda" is the entire disk, starting at the MBR
>>>>>>> (sector 0).
>>>>>>>
>>>>>>> Partition identifiers are "/dev/sda1" or "/dev/sda2". In one of
>>>>>>> those,
>>>>>>> you are more likely to find a file system and all the trimmings.
>>>>>>>
>>>>>>>     fsck -y -C -V /dev/sda1
>>>>>>>     fsck -y -C -V /dev/sda2
>>>>>>>
>>>>>>> If you use gparted
>>>>>>>
>>>>>>>     sudo gparted /dev/sda
>>>>>>>
>>>>>>> then graphically you can select some of these functions.
>>>>>>> The benefit of doing it graphically, is there will be
>>>>>>> little "hints" in the GUI, that the thing you are pointed
>>>>>>> at, is an EXT2 or a FAT32 or an NTFS. And you have a better
>>>>>>> idea what partition you are checking.
>>>>>>>
>>>>>>>     [Picture]
>>>>>>>
>>>>>>> https://i.postimg.cc/tJ29Pz4D/gparted-graphical-info.gif
>>>>>>>
>>>>>>> You can also do
>>>>>>>
>>>>>>>     sudo disktype /dev/sda
>>>>>>>
>>>>>>> and it will print out what it finds.
>>>>>>>
>>>>>>> Or for that matter, with a booted system, try
>>>>>>>
>>>>>>>     gnome-disks
>>>>>>>
>>>>>>> and select the drive from the menu.
>>>>>>>
>>>>>>> 1) Create a partition (nominal partition type like 0x83)
>>>>>>> 2) Format it so the superblock will be there.
>>>>>>> 3) Don't mount it, if you're going to check it.
>>>>>>>     If it is mounted, then unmount it first, then check it.
>>>>>>>
>>>>>>> Mounting a partition, does a certain amount of checking anyway.
>>>>>>> The assumption is, there is a partition not currently mounted,
>>>>>>> and it does not seem interested in accepting a mount command.
>>>>>>>
>>>>>>>     Paul
>>>>>>>
>>>>>>>
>>>>>> Thanks Paul, and both sda1 and sdc5 are clean with no errors,
>>>>>> after. I ran the said cmd
>>>>>>
>>>>>> So my ssd drive is ok as is the filesystem as well as no errors
>>>>>> with my ram sticks.
>>>>>> I would deduce then that it something to do with linux mint itself??
>>>>>> On the LM forum , where I posted my problem, and I am not the only
>>>>>> one it seems, I was told to remove any powered usb adaptors, which
>>>>>> I did 2 days ago. All was well until earlier today when it locked
>>>>>> up again.
>>>>>>
>>>>>> I have yet to try your earlier suggestion with a RS232 cable.
>>>>> Is  a windows product also installed on this machine? I thought
>>>>> that a DOS partition might indicate such.
>>>>
>>>> No I don't have windows on this machine, but have a disk with win10
>>>> for my aged laptop.
>>>>
>>>> I am not aware there is a DOS partition, but the boot partition is
>>>> fat 32. I'm not sure how that happened as I just let the install do
>>>> it's thing at the time.
>>>  From your post "I have just booted up a live knoppix usb and ran
>>> fsck -y -C -V /dev/sda
>>>
>>> but got this:
>>> Found a dos partition table in /dev/sdc"     How do you interpret
>>> this message? What is the purpose of the dos partition table?
>>> Question: How many drives are in this machine?
>>
>> There are x2 250Gb ssd drives, 1 for the boot partition and the other
>> for my /home partition.
>> There is also a 3rd spinning disc drive which I use for some backups.
>>
>> just for information, my machine locked at about 10.30am this morning,
>> and I have been out since then to about 4.45pm , and the machine was
>> still locked up.
>>
>> I am now thinking about doing a new reinstall of LM, but I'm not sure
>> if that would cure the problem.
>>
> Take a look at the syslog in the Home directory

Found it in /var/logs and found these 2 entries for this morning:

Jul 24 10:30:45 rob-Z97 touchegg[644]: libinput error: client bug: timer
event5 debounce: scheduled expiry is in the past (-603ms), your system
is too slow
Jul 24 11:05:57 rob-Z97 touchegg[644]: libinput error: client bug: timer
event5 debounce short: scheduled expiry is in the past (-4702ms), your
system is too slow


Click here to read the complete article
Pages:123
server_pubkey.txt

rocksolid light 0.9.7
clearnet tor