Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #222382 > unrolled thread

Suggestion on hardware issue?

Back to article view | Back to linux.debian.user

Contents

  Suggestion on hardware issue? Yvan Masson <yvan@masson-informatique.fr> - 2020-05-11 19:30 +0200
    Re: Suggestion on hardware issue? didier gaumet <didier.gaumet@gmail.com> - 2020-05-11 20:10 +0200
      Re: Suggestion on hardware issue? Yvan Masson <yvan@masson-informatique.fr> - 2020-05-11 21:50 +0200
        Re: Suggestion on hardware issue? didier gaumet <didier.gaumet@gmail.com> - 2020-05-11 22:40 +0200
    Re: Suggestion on hardware issue? David Christensen <dpchrist@holgerdanske.com> - 2020-05-12 03:40 +0200
      Re: Suggestion on hardware issue? Yvan Masson <yvan@masson-informatique.fr> - 2020-05-12 17:10 +0200
        Re: Suggestion on hardware issue? David Christensen <dpchrist@holgerdanske.com> - 2020-05-13 02:40 +0200
          Re: Suggestion on hardware issue? Yvan Masson <yvan@masson-informatique.fr> - 2020-05-14 21:30 +0200
            Re: Suggestion on hardware issue? Yvan Masson <yvan@masson-informatique.fr> - 2020-05-14 22:00 +0200
            Re: Suggestion on hardware issue? David Christensen <dpchrist@holgerdanske.com> - 2020-05-14 22:20 +0200

#222382 — Suggestion on hardware issue?

Hi,

I installed Debian 10 on a Acer AspireOne (32 bits processor, 1GB RAM).
Installation failed two times with corrupted packages, each time on same 
package (tcllib). I finally manage to re-download and install it by hand 
in another TTY so that the installer could finish. However, after the 
reboot, it could not start sddm (segfaults).

I tested RAM by running memtest86+ on this computer (3 passes, 4 hours), 
no issue. I ran debsums to check files integrity, and it returned many 
errors (written here by hand, so there might be typos):

/usr/lib/gcc/i686-linux-gnu/8/cc1
/usr/lib/firefox-esr/libxul.so
/usr/lib/firefox-esr/omni.ja
/usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so
/usr/lib/i386-linux-gnu/dri/nouveau_dri.so
/usr/lib/i386-linux-gnu/dri/r300_dri.so
/usr/lib/i386-linux-gnu/dri/r600_dri.so
/usr/lib/i386-linux-gnu/dri/radeonsi_dri.so
/usr/lib/i386-linux-gnu/dri/swrast_dri.so
/usr/lib/i386-linux-gnu/dri/virtio_gpu_dri.so
/usr/lib/i386-linux-gnu/dri/vmwgfx_dri.so
/usr/share/doc/libgstreamer1.0-0/changelog.gz
/usr/lib/i386-linux-gnu/libgucharmap_2_90.so.7.0.0
/usr/lib/i386-linux-gnu/libicudata.so.63.1
/usr/lib/i386-linux-gnu/libLLVM-7.so.1
/usr/lib/i386-linux-gnu/libQt5WebKit.so.5.212.0
/usr/lib/i386-linux-gnu/libre2.so.5.0.0
/usr/share/libreoffice/share/config/images_helpimg.zip
/usr/lib/libreoffice/program/libmergedlo.so
/usr/lib/libreoffice/program/libpcrlo.so
/usr/lib/jvm/java-11-openjdk-i386/lib/modules
/usr/lib/jvm/java-11-openjdk-i386/lib/server/libjvm.so
/usr/share/thunderbird/omni.ja
[ ] EXT4-fs error (device sda-1): ext4_lookup:1591: inode #1222922: comm 
debsums: iget: checksum invalid
[ ] Aborting journal on device sda1-8.
[ ] EXT4-fs (sda1): Remounting filesystem read-only


I have then thought that it could be the hard drive, so I replaced it 
with a spare one: install failed again, but when configuring a different 
package.

Is the motherboard or processor faulty, or is there any hope for a 
simple solution to save this computer?

Regards,
Yvan

[toc] | [next] | [standalone]

#222384

Hello,

perhaps try to install in text mode and lowmem:
 https://www.debian.org/releases/stable/i386/ch05s03.en.html

perhaps you have a RAM problem in a particular area that is not reported
by the RAM verifying tool you used.
If the installation succeeds, it could mean you have to replace the RAM
bank(s)...

[toc] | [prev] | [next] | [standalone]

#222387

Le 11/05/2020 à 20:03, didier gaumet a écrit :
> 
> Hello,
> 
> perhaps try to install in text mode and lowmem:
>   https://www.debian.org/releases/stable/i386/ch05s03.en.html
> 
> perhaps you have a RAM problem in a particular area that is not reported
> by the RAM verifying tool you used.
> If the installation succeeds, it could mean you have to replace the RAM
> bank(s)...
> 
I used memtest86+: if I understand the answer of this serverfault 
question[1],
it should test all "usable" RAM. I will try a low ram install to be sure.

1. 
https://serverfault.com/questions/750684/does-memtest86-test-memory-which-is-used-to-run-itself

[toc] | [prev] | [next] | [standalone]

#222388

I do not know well the subject but RAM problems can be a nightmare and I
suppose yours could be -for example- caused by a particular area of the
RAM that does not systematically fail under workload (transiant fault)
and thus is not detected
 https://en.wikipedia.org/wiki/Memory_tester

[toc] | [prev] | [next] | [standalone]

#222391

On 2020-05-11 10:28, Yvan Masson wrote:
> Hi,
> 
> I installed Debian 10 on a Acer AspireOne (32 bits processor, 1GB RAM).
> Installation failed two times with corrupted packages, each time on same 
> package (tcllib). I finally manage to re-download and install it by hand 
> in another TTY so that the installer could finish. However, after the 
> reboot, it could not start sddm (segfaults).
> 
> I tested RAM by running memtest86+ on this computer (3 passes, 4 hours), 
> no issue. I ran debsums to check files integrity, and it returned many 
> errors (written here by hand, so there might be typos):
> 
> /usr/lib/gcc/i686-linux-gnu/8/cc1
> /usr/lib/firefox-esr/libxul.so
> /usr/lib/firefox-esr/omni.ja
> /usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so
> /usr/lib/i386-linux-gnu/dri/nouveau_dri.so
> /usr/lib/i386-linux-gnu/dri/r300_dri.so
> /usr/lib/i386-linux-gnu/dri/r600_dri.so
> /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so
> /usr/lib/i386-linux-gnu/dri/swrast_dri.so
> /usr/lib/i386-linux-gnu/dri/virtio_gpu_dri.so
> /usr/lib/i386-linux-gnu/dri/vmwgfx_dri.so
> /usr/share/doc/libgstreamer1.0-0/changelog.gz
> /usr/lib/i386-linux-gnu/libgucharmap_2_90.so.7.0.0
> /usr/lib/i386-linux-gnu/libicudata.so.63.1
> /usr/lib/i386-linux-gnu/libLLVM-7.so.1
> /usr/lib/i386-linux-gnu/libQt5WebKit.so.5.212.0
> /usr/lib/i386-linux-gnu/libre2.so.5.0.0
> /usr/share/libreoffice/share/config/images_helpimg.zip
> /usr/lib/libreoffice/program/libmergedlo.so
> /usr/lib/libreoffice/program/libpcrlo.so
> /usr/lib/jvm/java-11-openjdk-i386/lib/modules
> /usr/lib/jvm/java-11-openjdk-i386/lib/server/libjvm.so
> /usr/share/thunderbird/omni.ja
> [ ] EXT4-fs error (device sda-1): ext4_lookup:1591: inode #1222922: comm 
> debsums: iget: checksum invalid
> [ ] Aborting journal on device sda1-8.
> [ ] EXT4-fs (sda1): Remounting filesystem read-only
> 
> 
> I have then thought that it could be the hard drive, so I replaced it 
> with a spare one: install failed again, but when configuring a different 
> package.
> 
> Is the motherboard or processor faulty, or is there any hope for a 
> simple solution to save this computer?
> 
> Regards,
> Yvan

Was the memory in your computer installed by Acer?


Have you removed or inserted any memory modules?


Do you use static safe tools and work practices?


What is the model/ part number of your computer?


How many memory slots does the computer have?


For each slot, what is the manufacturer name and and model/ part number 
of the installed memory module?


Run Memtest86+ for 24+ hours with the computer in the same location and 
under the same environmental conditions as the failed installations.  I 
have seen  computers pass Memtest86+ for the first 12 hours, then give a 
few failures in the next 12 hours.  Understand that temperature and 
airflow can affect the reliability of electronics.


Try installing from media only; do not use a mirror:

https://cdimage.debian.org/debian-cd/current/i386/iso-cd/debian-10.4.0-i386-xfce-CD-1.iso


Checksum the ISO file after you download it.


Checksum the installation media after you have burned it and before you 
have booted it (installer images on USB flash drives can and do change 
when booted).


Document the choices you make while running the installer.


David

[toc] | [prev] | [next] | [standalone]

#222419

Le 12/05/2020 à 03:37, David Christensen a écrit :
> On 2020-05-11 10:28, Yvan Masson wrote:
>> Hi,
>>
>> I installed Debian 10 on a Acer AspireOne (32 bits processor, 1GB RAM).
>> Installation failed two times with corrupted packages, each time on 
>> same package (tcllib). I finally manage to re-download and install it 
>> by hand in another TTY so that the installer could finish. However, 
>> after the reboot, it could not start sddm (segfaults).
>>
>> I tested RAM by running memtest86+ on this computer (3 passes, 4 
>> hours), no issue. I ran debsums to check files integrity, and it 
>> returned many errors (written here by hand, so there might be typos):
>>
>> /usr/lib/gcc/i686-linux-gnu/8/cc1
>> /usr/lib/firefox-esr/libxul.so
>> /usr/lib/firefox-esr/omni.ja
>> /usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so
>> /usr/lib/i386-linux-gnu/dri/nouveau_dri.so
>> /usr/lib/i386-linux-gnu/dri/r300_dri.so
>> /usr/lib/i386-linux-gnu/dri/r600_dri.so
>> /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so
>> /usr/lib/i386-linux-gnu/dri/swrast_dri.so
>> /usr/lib/i386-linux-gnu/dri/virtio_gpu_dri.so
>> /usr/lib/i386-linux-gnu/dri/vmwgfx_dri.so
>> /usr/share/doc/libgstreamer1.0-0/changelog.gz
>> /usr/lib/i386-linux-gnu/libgucharmap_2_90.so.7.0.0
>> /usr/lib/i386-linux-gnu/libicudata.so.63.1
>> /usr/lib/i386-linux-gnu/libLLVM-7.so.1
>> /usr/lib/i386-linux-gnu/libQt5WebKit.so.5.212.0
>> /usr/lib/i386-linux-gnu/libre2.so.5.0.0
>> /usr/share/libreoffice/share/config/images_helpimg.zip
>> /usr/lib/libreoffice/program/libmergedlo.so
>> /usr/lib/libreoffice/program/libpcrlo.so
>> /usr/lib/jvm/java-11-openjdk-i386/lib/modules
>> /usr/lib/jvm/java-11-openjdk-i386/lib/server/libjvm.so
>> /usr/share/thunderbird/omni.ja
>> [ ] EXT4-fs error (device sda-1): ext4_lookup:1591: inode #1222922: 
>> comm debsums: iget: checksum invalid
>> [ ] Aborting journal on device sda1-8.
>> [ ] EXT4-fs (sda1): Remounting filesystem read-only
>>
>>
>> I have then thought that it could be the hard drive, so I replaced it 
>> with a spare one: install failed again, but when configuring a 
>> different package.
>>
>> Is the motherboard or processor faulty, or is there any hope for a 
>> simple solution to save this computer?
>>
>> Regards,
>> Yvan
> 
> Was the memory in your computer installed by Acer?
I believe so.
> 
> 
> Have you removed or inserted any memory modules?
Not before the issue arose.
> 
> 
> Do you use static safe tools and work practices?
In this case I only used my hands, and touched grounded metal before.
> 
> 
> What is the model/ part number of your computer?
I can not tell now as I won't have access to the computer before two days.
> 
> 
> How many memory slots does the computer have?
1
> 
> 
> For each slot, what is the manufacturer name and and model/ part number 
> of the installed memory module?
Can not tell right now.
> 
> 
> Run Memtest86+ for 24+ hours with the computer in the same location and 
> under the same environmental conditions as the failed installations.  I 
> have seen  computers pass Memtest86+ for the first 12 hours, then give a 
> few failures in the next 12 hours.  Understand that temperature and 
> airflow can affect the reliability of electronics.
> 
> 
> Try installing from media only; do not use a mirror:
> 
> https://cdimage.debian.org/debian-cd/current/i386/iso-cd/debian-10.4.0-i386-xfce-CD-1.iso 
> 
> 
> 
> Checksum the ISO file after you download it.
> 
> 
> Checksum the installation media after you have burned it and before you 
> have booted it (installer images on USB flash drives can and do change 
> when booted).
> 
> 
> Document the choices you make while running the installer.
> 
> 
> David
> 

Thanks for your suggestions! I will first try to find another RAM stick 
that I know is good, and try install again: it seems faster than trying 
to diagnose a faulty RAM stick.

[toc] | [prev] | [next] | [standalone]

#222437

On 2020-05-12 08:04, Yvan Masson wrote:
> Le 12/05/2020 à 03:37, David Christensen a écrit :
>> On 2020-05-11 10:28, Yvan Masson wrote:

>> Was the memory in your computer installed by Acer?
> I believe so.

Okay.


>> Have you removed or inserted any memory modules?
> Not before the issue arose.

Okay.


>> Do you use static safe tools and work practices?
> In this case I only used my hands, and touched grounded metal before.
AIUI microelectronics are now so small that an electrostatic discharge 
too small for people to notice may still be large enough to damage the 
electronics.


>> What is the model/ part number of your computer?
> I can not tell now as I won't have access to the computer before two days.

Okay.  Please post the information when available.


>> How many memory slots does the computer have?
> 1

Okay.


>> For each slot, what is the manufacturer name and and model/ part 
>> number of the installed memory module?
> Can not tell right now.

Okay.  Please post the information when available.


>> Run Memtest86+ for 24+ hours with the computer in the same location 
>> and under the same environmental conditions as the failed 
>> installations.  I have seen  computers pass Memtest86+ for the first 
>> 12 hours, then give a few failures in the next 12 hours.  Understand 
>> that temperature and airflow can affect the reliability of electronics.

>> Try installing from media only; do not use a mirror:
>>
>> https://cdimage.debian.org/debian-cd/current/i386/iso-cd/debian-10.4.0-i386-xfce-CD-1.iso 

>> Checksum the ISO file after you download it.

>> Checksum the installation media after you have burned it and before 
>> you have booted it (installer images on USB flash drives can and do 
>> change when booted).

>> Document the choices you make while running the installer.

> Thanks for your suggestions! I will first try to find another RAM stick 
> that I know is good, and try install again: it seems faster than trying 
> to diagnose a faulty RAM stick.

I would run Memtest86+ for 24 hours first.  If it fails, replace the 
memory module with a known good module and run Memtest86+ for another 24 
hours.  If that fails, I would blame the motherboard.


If/ when your memory is good (and CPU by proxy), download the 
manufacturer diagnostic tool for your system drive and run that. 
Consider wiping the system drive.  I prefer bootable USB images.  For 
example:

https://www.seagate.com/support/downloads/seatools/


Once your CPU, memory, and system drive are known good, then do the install.


David

[toc] | [prev] | [next] | [standalone]

#222507

Le 13/05/2020 à 02:30, David Christensen a écrit :
> On 2020-05-12 08:04, Yvan Masson wrote:
>> Le 12/05/2020 à 03:37, David Christensen a écrit :
>>> On 2020-05-11 10:28, Yvan Masson wrote:
> 
>>> Was the memory in your computer installed by Acer?
>> I believe so.
> 
> Okay.
> 
> 
>>> Have you removed or inserted any memory modules?
>> Not before the issue arose.
> 
> Okay.
> 
> 
>>> Do you use static safe tools and work practices?
>> In this case I only used my hands, and touched grounded metal before.
> AIUI microelectronics are now so small that an electrostatic discharge 
> too small for people to notice may still be large enough to damage the 
> electronics.
> 
> 
>>> What is the model/ part number of your computer?
>> I can not tell now as I won't have access to the computer before two 
>> days.
> 
> Okay.  Please post the information when available.
It is an Acer AspireOne AO751h.
> 
> 
>>> How many memory slots does the computer have?
>> 1
> 
> Okay.
> 
> 
>>> For each slot, what is the manufacturer name and and model/ part 
>>> number of the installed memory module?
>> Can not tell right now.
> 
> Okay.  Please post the information when available.
It is a Hynix HYMP112S64CP6-Y5 AB-C (1GB 2Rx16 PC2-5300S-555-12)
> 
> 
>>> Run Memtest86+ for 24+ hours with the computer in the same location 
>>> and under the same environmental conditions as the failed 
>>> installations.  I have seen  computers pass Memtest86+ for the first 
>>> 12 hours, then give a few failures in the next 12 hours.  Understand 
>>> that temperature and airflow can affect the reliability of electronics.
> 
>>> Try installing from media only; do not use a mirror:
>>>
>>> https://cdimage.debian.org/debian-cd/current/i386/iso-cd/debian-10.4.0-i386-xfce-CD-1.iso 
> 
> 
>>> Checksum the ISO file after you download it.
> 
>>> Checksum the installation media after you have burned it and before 
>>> you have booted it (installer images on USB flash drives can and do 
>>> change when booted).
> 
>>> Document the choices you make while running the installer.
> 
>> Thanks for your suggestions! I will first try to find another RAM 
>> stick that I know is good, and try install again: it seems faster than 
>> trying to diagnose a faulty RAM stick.
> 
> I would run Memtest86+ for 24 hours first.  If it fails, replace the 
> memory module with a known good module and run Memtest86+ for another 24 
> hours.  If that fails, I would blame the motherboard.
> 
> 
> If/ when your memory is good (and CPU by proxy), download the 
> manufacturer diagnostic tool for your system drive and run that. 
> Consider wiping the system drive.  I prefer bootable USB images.  For 
> example:
> 
> https://www.seagate.com/support/downloads/seatools/

I might have forgot to tell that I already tried with another hard 
drive, and the installer failed exactly the same way.
> 
> 
> Once your CPU, memory, and system drive are known good, then do the 
> install.
> 
> 
> David
> 

Before seeing your last email, I replaced the RAM with a known-good, 2GB 
this time. Again, I had an issue while doing the install during packages 
configuration.

I then try an install without desktop environment (only SSH, print 
server and usual system utilities) successfully. After reboot, `apt 
install task-lxqt-desktop` failed (LZMA error when unziping 
libreoffice-core_1%3a6.1.5-3+deb10u6_i386.deb and 
libqt5webenginecore5_5.11.3+dfsg-2+deb10u1_i386.deb). Removed packages 
from cache, did `apt install -f`, and those packages installed properly.

I then installed many packages, still no issue.

I will run debsums to know the state of packages files, and then run 
memtest86+ during 24h.

Thanks again,
Yvan

[toc] | [prev] | [next] | [standalone]

#222508

Le 14/05/2020 à 21:22, Yvan Masson a écrit :
> Le 13/05/2020 à 02:30, David Christensen a écrit :
>> On 2020-05-12 08:04, Yvan Masson wrote:
>>> Le 12/05/2020 à 03:37, David Christensen a écrit :
>>>> On 2020-05-11 10:28, Yvan Masson wrote:
>>
>>>> Was the memory in your computer installed by Acer?
>>> I believe so.
>>
>> Okay.
>>
>>
>>>> Have you removed or inserted any memory modules?
>>> Not before the issue arose.
>>
>> Okay.
>>
>>
>>>> Do you use static safe tools and work practices?
>>> In this case I only used my hands, and touched grounded metal before.
>> AIUI microelectronics are now so small that an electrostatic discharge 
>> too small for people to notice may still be large enough to damage the 
>> electronics.
>>
>>
>>>> What is the model/ part number of your computer?
>>> I can not tell now as I won't have access to the computer before two 
>>> days.
>>
>> Okay.  Please post the information when available.
> It is an Acer AspireOne AO751h.
>>
>>
>>>> How many memory slots does the computer have?
>>> 1
>>
>> Okay.
>>
>>
>>>> For each slot, what is the manufacturer name and and model/ part 
>>>> number of the installed memory module?
>>> Can not tell right now.
>>
>> Okay.  Please post the information when available.
> It is a Hynix HYMP112S64CP6-Y5 AB-C (1GB 2Rx16 PC2-5300S-555-12)
>>
>>
>>>> Run Memtest86+ for 24+ hours with the computer in the same location 
>>>> and under the same environmental conditions as the failed 
>>>> installations.  I have seen  computers pass Memtest86+ for the first 
>>>> 12 hours, then give a few failures in the next 12 hours.  Understand 
>>>> that temperature and airflow can affect the reliability of electronics.
>>
>>>> Try installing from media only; do not use a mirror:
>>>>
>>>> https://cdimage.debian.org/debian-cd/current/i386/iso-cd/debian-10.4.0-i386-xfce-CD-1.iso 
>>
>>
>>
>>>> Checksum the ISO file after you download it.
>>
>>>> Checksum the installation media after you have burned it and before 
>>>> you have booted it (installer images on USB flash drives can and do 
>>>> change when booted).
>>
>>>> Document the choices you make while running the installer.
>>
>>> Thanks for your suggestions! I will first try to find another RAM 
>>> stick that I know is good, and try install again: it seems faster 
>>> than trying to diagnose a faulty RAM stick.
>>
>> I would run Memtest86+ for 24 hours first.  If it fails, replace the 
>> memory module with a known good module and run Memtest86+ for another 
>> 24 hours.  If that fails, I would blame the motherboard.
>>
>>
>> If/ when your memory is good (and CPU by proxy), download the 
>> manufacturer diagnostic tool for your system drive and run that. 
>> Consider wiping the system drive.  I prefer bootable USB images.  For 
>> example:
>>
>> https://www.seagate.com/support/downloads/seatools/
> 
> I might have forgot to tell that I already tried with another hard 
> drive, and the installer failed exactly the same way.
>>
>>
>> Once your CPU, memory, and system drive are known good, then do the 
>> install.
>>
>>
>> David
>>
> 
> Before seeing your last email, I replaced the RAM with a known-good, 2GB 
> this time. Again, I had an issue while doing the install during packages 
> configuration.
> 
> I then try an install without desktop environment (only SSH, print 
> server and usual system utilities) successfully. After reboot, `apt 
> install task-lxqt-desktop` failed (LZMA error when unziping 
> libreoffice-core_1%3a6.1.5-3+deb10u6_i386.deb and 
> libqt5webenginecore5_5.11.3+dfsg-2+deb10u1_i386.deb). Removed packages 
> from cache, did `apt install -f`, and those packages installed properly.
> 
> I then installed many packages, still no issue.
> 
> I will run debsums to know the state of packages files, and then run 
> memtest86+ during 24h.

Interesting! `debsums -ac` returns most of the same files than on the 
first install: a few more (normal because I installed other packages) 
and a few less (but present on my current install). Time for memtest86+…

[toc] | [prev] | [next] | [standalone]

#222512

On 2020-05-14 12:22, Yvan Masson wrote:
> Le 13/05/2020 à 02:30, David Christensen a écrit :
>> On 2020-05-12 08:04, Yvan Masson wrote:
>>> Le 12/05/2020 à 03:37, David Christensen a écrit :
>>>> On 2020-05-11 10:28, Yvan Masson wrote:

>>>> What is the model/ part number of your computer?

> It is an Acer AspireOne AO751h.

The model number seems to be valid, but I am unable to find a product 
support page, technical specifications, etc..  Do you have a URL?


>>>> ... what is the manufacturer name and and model/ part 
>>>> number of the installed memory module?

http://hynix.com/datasheet/eng/module/details/module_08_HYMP112S64CP6.jsp


> I might have forgot to tell that I already tried with another hard 
> drive, and the installer failed exactly the same way.

> Before seeing your last email, I replaced the RAM with a known-good, 2GB 
> this time. Again, I had an issue while doing the install during packages 
> configuration.
> 
> I then try an install without desktop environment (only SSH, print 
> server and usual system utilities) successfully. After reboot, `apt 
> install task-lxqt-desktop` failed (LZMA error when unziping 
> libreoffice-core_1%3a6.1.5-3+deb10u6_i386.deb and 
> libqt5webenginecore5_5.11.3+dfsg-2+deb10u1_i386.deb). Removed packages 
> from cache, did `apt install -f`, and those packages installed properly.
> 
> I then installed many packages, still no issue.
> 
> I will run debsums to know the state of packages files, and then run 
> memtest86+ during 24h.

That sounds like a bad installer image.  Did you checksum the ISO or 
image file after download?  Did you checksum your media after burning it?


> Thanks again,

YW.  :-)


I'm glad you got it working.


David

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web