Bonsoir,

Une amie mexicaine essaie (vainement pour l'instant) de mettre à
jour sa machine
de Ubuntu 16 à Ubuntu 20.04. Elle a fait pour cela un clef USB,
reconnue, d'où elle
peut « essayer » Ubuntu sans problème (connexion internet incluse, wifi OK). Mais
si elle essaie « d'installer » Ubuntu à ce moment-là, la machine
commence à mouliner et ne s'arrête pas... Plus exactement, rien ne se
passe apparemment sur le disque (ce au bout d'une demi-heure). Que faire ?

Infos techniques :
Procesor Intel (R) Core (TM) i5-6400 CPU @2.70GHz
Intel HD Graphics
RealTek ALC3861
RealTek ALC 3861
RealTek Wireless

Merci d'avance pour tout suggestion.
Serge.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 02/03/2022 22:46, serge bouc wrote:

  Une amie mexicaine essaie (vainement pour l'instant) de mettre à jour sa machine
de Ubuntu 16 à Ubuntu 20.04. Elle a fait pour cela un clef USB, reconnue, d'où elle
peut « essayer »  Ubuntu sans problème (connexion internet incluse, wifi OK). Mais
si elle essaie « d'installer » Ubuntu à ce moment-là, la machine commence à mouliner et ne s'arrête pas... Plus
exactement, rien ne se passe apparemment sur le disque (ce au bout d'une demi-heure). Que faire ?

from Google translate:

A Mexican friend is trying (unsuccessfully so far) to update her machine
from Ubuntu 16 to Ubuntu 20.04. She made a USB key for this, recognized, from where she
can "try" Ubuntu without problem (internet connection included, wifi OK). Corn if she tries to "install" Ubuntu at this time, the machine starts to grind and does not stop... More exactly, nothing
seems to happen on the disk (this after half an hour ). What to do ?

1) upgrade from 16 to 20 should pass through 18 LTS.
2) I would suggest doing a fresh install of 20.04, after saving her home directory on a separate partition.
3) what is the command she's using for "Install"
4) Google is your friend, see e.g. https://www.how2shout.com/linux/upgrade-ubuntu-16-04-lts-to-20-04-lts-using-command-terminal

--
Mike R.
Home: http://alpha.mike-r.com/
QOTD: http://alpha.mike-r.com/qotd.php
No Micro$oft products were used in the URLs above, or in preparing this message.
Recommended reading: http://www.catb.org/~esr/faqs/smart-questions.html#before
and: http://alpha.mike-r.com/jargon/T/top-post.html
Missile address: N31.7624/E34.9691

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Le 03/03/2022 à 05:47, Henry Crun a écrit :

On 02/03/2022 22:46, serge bouc wrote:

   Une amie mexicaine essaie (vainement pour l'instant) de mettre à
jour sa machine
de Ubuntu 16 à Ubuntu 20.04. Elle a fait pour cela un clef USB,
reconnue, d'où elle
peut « essayer »  Ubuntu sans problème (connexion internet incluse,
wifi OK). Mais
si elle essaie « d'installer » Ubuntu à ce moment-là, la machine
commence à mouliner et ne s'arrête pas... Plus exactement, rien ne se
passe apparemment sur le disque (ce au bout d'une demi-heure). Que
faire ?

from Google translate:

A Mexican friend is trying (unsuccessfully so far) to update her machine
from Ubuntu 16 to Ubuntu 20.04. She made a USB key for this, recognized,
from where she
can "try" Ubuntu without problem (internet connection included, wifi
OK). Corn
if she tries to "install" Ubuntu at this time, the machine starts to
grind and does not stop... More exactly, nothing seems to happen on the
disk (this after half an hour ). What to do ?

1) upgrade from 16 to 20 should pass through 18 LTS.
2) I would suggest doing a fresh install of 20.04, after saving her home directory on a separate partition.
3) what is the command she's using for "Install"
4) Google is your friend, see e.g. https://www.how2shout.com/linux/upgrade-ubuntu-16-04-lts-to-20-04-lts-using-command-terminal

Hi,

First of all, sorry for writing in french on this group... and
thanks for your quick reply!

My friend has indeed made a backup of her home directory, and then a
bootable USB key with Ubuntu 20.04. Then after boot, there are two options:

1) either try Ubuntu without installing it. This does work, everything
is ok, internet and wifi.

2) or install Ubuntu. This seems to start correctly, but at some point,
the process stops,
and nothing happens (no sign of disk activity whatsoever). My friend
waited for more than 30mn from there, without noticing any change.

She has tried several times, without success. At some point, she got a
message like this one (the exact numbers may be different, but not the
text):

DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x000000008d800000-0x000000008fffffff], contact BIOS vendor for fixes
DMAR: [Firmware Bug]: Your BIOS is broken; bad RMRR [0x000000008d800000-0x000000008

This is of course a bit frightening... :-( and I don't know how I could
help...

Serge.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

serge bouc wrote:

DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x000000008d800000-0x000000008fffffff], contact BIOS vendor for fixes
DMAR: [Firmware Bug]: Your BIOS is broken; bad RMRR [0x000000008d800000-0x000000008

Possible fix here:

<https://askubuntu.com/questions/1331090/dmar-firmware-bug-broken-bios>


--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Le 03/03/2022 à 15:17, Jonathan N. Little a écrit :

serge bouc wrote:

DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR
[0x000000008d800000-0x000000008fffffff], contact BIOS vendor for fixes
DMAR: [Firmware Bug]: Your BIOS is broken; bad RMRR
[0x000000008d800000-0x000000008

Possible fix here:

<https://askubuntu.com/questions/1331090/dmar-firmware-bug-broken-bios>

Thanks a lot for the link. We'll try that...

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 03/03/2022 16:00, serge bouc wrote:

Le 03/03/2022 à 05:47, Henry Crun a écrit :

On 02/03/2022 22:46, serge bouc wrote:

   Une amie mexicaine essaie (vainement pour l'instant) de mettre à jour sa machine
de Ubuntu 16 à Ubuntu 20.04. Elle a fait pour cela un clef USB, reconnue, d'où elle
peut « essayer »  Ubuntu sans problème (connexion internet incluse, wifi OK). Mais
si elle essaie « d'installer » Ubuntu à ce moment-là, la machine commence à mouliner et ne s'arrête pas... Plus
exactement, rien ne se passe apparemment sur le disque (ce au bout d'une demi-heure). Que faire ?

from Google translate:

A Mexican friend is trying (unsuccessfully so far) to update her machine
from Ubuntu 16 to Ubuntu 20.04. She made a USB key for this, recognized, from where she
can "try" Ubuntu without problem (internet connection included, wifi OK). Corn
if she tries to "install" Ubuntu at this time, the machine starts to grind and does not stop... More exactly, nothing
seems to happen on the disk (this after half an hour ). What to do ?

1) upgrade from 16 to 20 should pass through 18 LTS.
2) I would suggest doing a fresh install of 20.04, after saving her home directory on a separate partition.
3) what is the command she's using for "Install"
4) Google is your friend, see e.g.
https://www.how2shout.com/linux/upgrade-ubuntu-16-04-lts-to-20-04-lts-using-command-terminal

Hi,

   First of all, sorry for writing in french on this group... and thanks for your quick reply!

My friend has indeed made a backup of her home directory, and then a bootable USB key with Ubuntu 20.04. Then after
boot, there are two options:

1) either try Ubuntu without installing it. This does work, everything is ok, internet and wifi.

2) or install Ubuntu. This seems to start correctly, but at some point, the process stops,
and nothing happens (no sign of disk activity whatsoever). My friend waited for more than 30mn from there, without
noticing any change.

She has tried several times, without success. At some point, she got a message like this one (the exact numbers may be
different, but not the text):

DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x000000008d800000-0x000000008fffffff], contact
BIOS vendor for fixes
DMAR: [Firmware Bug]: Your BIOS is broken; bad RMRR [0x000000008d800000-0x000000008

This is of course a bit frightening... :-( and I don't know how I could help...

Serge.

did she try upgrading to 18.04 first?


--
Mike R.
Home: http://alpha.mike-r.com/
QOTD: http://alpha.mike-r.com/qotd.php
No Micro$oft products were used in the URLs above, or in preparing this message.
Recommended reading: http://www.catb.org/~esr/faqs/smart-questions.html#before
and: http://alpha.mike-r.com/jargon/T/top-post.html
Missile address: N31.7624/E34.9691

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Le 03/03/2022 à 15:36, Henry Crun a écrit :

Hi,

    First of all, sorry for writing in french on this group... and
thanks for your quick reply!

My friend has indeed made a backup of her home directory, and then a
bootable USB key with Ubuntu 20.04. Then after boot, there are two
options:

1) either try Ubuntu without installing it. This does work, everything
is ok, internet and wifi.

2) or install Ubuntu. This seems to start correctly, but at some
point, the process stops,
and nothing happens (no sign of disk activity whatsoever). My friend
waited for more than 30mn from there, without noticing any change.

She has tried several times, without success. At some point, she got a
message like this one (the exact numbers may be different, but not the
text):

DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR
[0x000000008d800000-0x000000008fffffff], contact BIOS vendor for fixes
DMAR: [Firmware Bug]: Your BIOS is broken; bad RMRR
[0x000000008d800000-0x000000008

This is of course a bit frightening... :-( and I don't know how I
could help...

Serge.

did she try upgrading to 18.04 first?

No. She made a backup, then a USB key with Ubuntu 20.04, and then tried to install from there, unsuccessfully. She even suspected the USB key, so
made a new one,
but the result was the same (actually even worse, the install process
froze earlier...).

Serge.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Le 03/03/2022 à 17:08, Henry Crun a écrit :

No. She made a backup, then a USB key with Ubuntu 20.04, and then
tried to
install from there, unsuccessfully. She even suspected the USB key, so
made a new one,
but the result was the same (actually even worse, the install process
froze earlier...).

Serge.

To reiterate:
The correct path would be to upgrade from 16.x (hopefully 16.04, NOT
16.10) to 18.04
The efficient path wuold be to upgrade online (probably using "sudo do-release-upgrade")
Please ask your friend why she is going about this in an unsupported and inefficient way.
And of course the simplest path would be to install 20.04 from scratch

Probably I was unclear in my explanations. So, to reiterate also:

1) She first made a backup of her home on a disk.

2) Then made a bootable USB key with an ISO image of Ubunto 20.04.

3) Tried several times to install from there, and each time the install
froze.

What else do you mean by "install 20.04 from scratch"?

Serge.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 03/03/2022 17:05, serge bouc wrote:

Le 03/03/2022 à 15:36, Henry Crun a écrit :

Hi,

    First of all, sorry for writing in french on this group... and thanks for your quick reply!

My friend has indeed made a backup of her home directory, and then a bootable USB key with Ubuntu 20.04. Then after
boot, there are two options:

1) either try Ubuntu without installing it. This does work, everything is ok, internet and wifi.

2) or install Ubuntu. This seems to start correctly, but at some point, the process stops,
and nothing happens (no sign of disk activity whatsoever). My friend waited for more than 30mn from there, without
noticing any change.

She has tried several times, without success. At some point, she got a message like this one (the exact numbers may
be different, but not the text):

DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x000000008d800000-0x000000008fffffff],
contact BIOS vendor for fixes
DMAR: [Firmware Bug]: Your BIOS is broken; bad RMRR [0x000000008d800000-0x000000008

This is of course a bit frightening... :-( and I don't know how I could help...

Serge.

did she try upgrading to 18.04 first?

No. She made a backup, then a USB key with Ubuntu 20.04, and then tried to install from there, unsuccessfully. She even suspected the USB key, so made a new one,
but the result was the same (actually even worse, the install process froze earlier...).

Serge.

To reiterate:
The correct path would be to upgrade from 16.x (hopefully 16.04, NOT 16.10) to 18.04
The efficient path wuold be to upgrade online (probably using "sudo do-release-upgrade")
Please ask your friend why she is going about this in an unsupported and inefficient way.
And of course the simplest path would be to install 20.04 from scratch

--
Mike R.
Home: http://alpha.mike-r.com/
QOTD: http://alpha.mike-r.com/qotd.php
No Micro$oft products were used in the URLs above, or in preparing this message.
Recommended reading: http://www.catb.org/~esr/faqs/smart-questions.html#before
and: http://alpha.mike-r.com/jargon/T/top-post.html
Missile address: N31.7624/E34.9691

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

serge bouc wrote:

Probably I was unclear in my explanations. So, to reiterate also:

1) She first made a backup of her home on a disk.

2) Then made a bootable USB key with an ISO image of Ubunto 20.04.

3) Tried several times to install from there, and each time the install froze.

What else do you mean by "install 20.04 from scratch"?

I think some confusion comes from your first message which says, or
rather translates to "update her machine from Ubuntu 16 to Ubuntu 20.04".

I believe the current process is one of trying to install 20.04 as a
fresh install, not an update procedure which could be possible from
updating 16.04 to 18.04 and then updating 18.04 to 20.04, but not as
advisable as a fresh install or 'from scratch'.

--
Mike Easter

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 03.03.2022 17:22, serge bouc wrote:

[...]
3) Tried several times to install from there, and each time the install froze.

This reminds me my try to upgrade from 18 to 20 that resulted in
a freeze during executing the snap-based installation sub-process.

(I have no idea whether that cause matches your case, since only
the few keywords of your post match. - Anyway, in consequence I
disabled/remove snap - with help and hints from a google search -
and reinstalled v18 from scratch, abstaining completely from v20.)

Janis

What else do you mean by "install 20.04 from scratch"?

Serge.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 03/03/2022 16:25, Dan Purgert wrote:

Serge - has your friend tried running the media self-test off the USB Bootloader and/or memtest to check the RAM? I think those are the last options (or "hidden" behind the "Advanced Startup" option); but it's
been a while since I've booted off install media.

==============
It seems she can run UB 20.3 in live mode off the (bootable)USB device
,so the bootable device is OK

But when installing on a machine with an existing distro did she specify
to install UB20.3 on the whole HD ? If not there might not be enough HD
space to install UB 20.3 alongside the existing distro .

Personally I would first erase the HD to its "unallocated" state with
Gparted before installing UB20.3

Frank in County Wicklow Ireland

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Le 03/03/2022 à 23:19, wicklowham a écrit :

On 03/03/2022 16:25, Dan Purgert wrote:

Serge - has your friend tried running the media self-test off the USB
Bootloader and/or memtest to check the RAM?   I think those are the last >> options (or "hidden" behind the "Advanced Startup" option); but it's
been a while since I've booted off install media.

==============
It seems she can run UB 20.3 in live mode off the (bootable)USB device
,so the bootable device is OK

But when installing on a machine with an existing distro did she specify
to install UB20.3 on the whole HD ? If not there might not be enough HD
space to install UB 20.3 alongside the existing distro .

Personally I would first erase the HD to its "unallocated" state with Gparted  before installing UB20.3

Frank in County Wicklow Ireland

Hi everybody,

and thanks for your answers. Several questions :

1) I can't see Dan Purgert's message (above) in my news reader (on thunderbird), and
I don't know why... Sorry about that.

2) I don't know how to run the "media self test" you mention. As
Wicklowham mentions,
the live version seems ok. Is that enough?

3) There is a log after (failed) install, on the USB key. It mentions
something related to Nvidia, but I don't understand it either... :-(
Might be unrelated to the problem, but just
in case, here it is:

log_file: /var/log/gpu-manager.log
last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
can't access /run/u-d-c-nvidia-was-loaded file
can't access /opt/amdgpu-pro/bin/amdgpu-pro-px
Looking for nvidia modules in /lib/modules/5.11.0-27-generic/kernel
Looking for nvidia modules in /lib/modules/5.11.0-27-generic/updates/dkms Looking for amdgpu modules in /lib/modules/5.11.0-27-generic/kernel
Looking for amdgpu modules in /lib/modules/5.11.0-27-generic/updates/dkms
Is nvidia loaded? no
Was nvidia unloaded? no
Is nvidia blacklisted? no
Is intel loaded? yes
Is radeon loaded? no
Is radeon blacklisted? no
Is amdgpu loaded? no
Is amdgpu blacklisted? no
Is amdgpu versioned? no
Is amdgpu pro stack? no
Is nouveau loaded? yes
Is nouveau blacklisted? no
Is nvidia kernel module available? no
Is amdgpu kernel module available? no
Vendor/Device Id: 8086:1912
BusID "PCI:0@0:2:0"
Is boot vga? yes
Vendor/Device Id: 10de:1287
BusID "PCI:1@0:0:0"
Is boot vga? no
can't access /etc/u-d-c-nvidia-runtimepm-override file
can't open /sys/module/nvidia/version
Warning: cannot check the NVIDIA driver major version
Support for runtimepm not detected.
You can override this check at your own risk by creating the /etc/u-d-c-nvidia-runtimepm-override file.
Is nvidia runtime pm supported for "0x1287"? no
Checking power status in /proc/driver/nvidia/gpus/0000:01:00.0/power
Error while opening /proc/driver/nvidia/gpus/0000:01:00.0/power
Is nvidia runtime pm enabled for "0x1287"? no
Skipping "/dev/dri/card1", driven by "nouveau"
Skipping "/dev/dri/card0", driven by "i915"
Skipping "/dev/dri/card1", driven by "nouveau"
Skipping "/dev/dri/card0", driven by "i915"
Found "/dev/dri/card1", driven by "nouveau"
output 0:
card1-VGA-1
Number of connected outputs for /dev/dri/card1: 1
Skipping "/dev/dri/card1", driven by "nouveau"
Found "/dev/dri/card0", driven by "i915"
output 0:
card0-DP-1
Number of connected outputs for /dev/dri/card0: 1
can't access /etc/prime-discrete
No prime-settings found. Assuming prime is not set to ON (ONDEMAND could
be on).
Does it require offloading? no
I couldn't open /var/lib/ubuntu-drivers-common/last_gfx_boot for reading. Create /var/lib/ubuntu-drivers-common/last_gfx_boot for the 1st time
last cards number = 1
Has amd? no
Has intel? yes
Has nvidia? yes
How many cards? 2
The number of cards has changed!
Has the system changed? Yes
System configuration has changed
Intel IGP detected
Desktop system detected

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Le 03/03/2022 à 23:19, wicklowham a écrit :

On 03/03/2022 16:25, Dan Purgert wrote:

Serge - has your friend tried running the media self-test off the USB
Bootloader and/or memtest to check the RAM?   I think those are the last >> options (or "hidden" behind the "Advanced Startup" option); but it's
been a while since I've booted off install media.

==============
It seems she can run UB 20.3 in live mode off the (bootable)USB device
,so the bootable device is OK

But when installing on a machine with an existing distro did she specify
to install UB20.3 on the whole HD ? If not there might not be enough HD
space to install UB 20.3 alongside the existing distro .

Personally I would first erase the HD to its "unallocated" state with Gparted  before installing UB20.3

Frank in County Wicklow Ireland

Hi everybody,

and thanks for your answers. Several questions :

1) I can't see Dan Purgert's message (above) in my news reader (on thunderbird), and
I don't know why... Sorry about that.

2) I don't know how to run the "media self test" you mention. As
Wicklowham mentions,
the live version seems ok. Is that enough?

3) There is a log after (failed) install, on the USB key. It mentions
something related to Nvidia, but I don't understand it either... Might
be unrelated to the problem.

I have tried to include the log to this message, but it doesn' show up
either on the newsgroup. Seems I'm missing something... :-(

Serge.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 3/3/22 15:49, serge bouc wrote:

Le 03/03/2022 à 23:19, wicklowham a écrit :

On 03/03/2022 16:25, Dan Purgert wrote:

Serge - has your friend tried running the media self-test off the USB
Bootloader and/or memtest to check the RAM?   I think those are the last >>> options (or "hidden" behind the "Advanced Startup" option); but it's
been a while since I've booted off install media.

==============
It seems she can run UB 20.3 in live mode off the (bootable)USB device
,so the bootable device is OK

She wants to be using Ubuntu 20.04.4 on that USB Flash Drive

But when installing on a machine with an existing distro did she
specify to install UB20.3 on the whole HD ? If not there might not be
enough HD space to install UB 20.3 alongside the existing distro .

First the old installation has to be removed. It is messing up the attempt to install. Can she open a Termial and type the simple
command "df" and read the result to see which particon contains the
"/" aka root partition, This is where the the established directories
are and they are giving the installer a problem.

Personally I would first erase the HD to its "unallocated" state with
Gparted  before installing UB20.3

Just format the partition of the installation to Ext4 if Ubuntu features a tool to do that. if not use a live recent resease of
GPartEd. The Graphical User interface makes such operations and
more complex operations simple.

We dow not know what Graphic Processing Unit is active.

Noveau is a FOSS substitute for the non-FOSS nvidia drivers.
It does not work With some NVidia cards but for some uses the Noveau
works well enough but the proper non-FOSS driver may provide better effects.
i915 is an Intel driver for the GPU integrated in the
intel chip set.

Frank in County Wicklow Ireland

Hi everybody,

   and thanks for your answers. Several questions :

1) I can't see Dan Purgert's message (above) in my news reader (on thunderbird), and
I don't know why... Sorry about that.

2) I don't know how to run the "media self test" you mention. As
Wicklowham mentions,
the live version seems ok. Is that enough?

3) There is a log after (failed) install, on the USB key. It mentions something related to Nvidia, but I don't understand it either... :-(
Might be unrelated to the problem, but just
in case, here it is:

log_file: /var/log/gpu-manager.log
last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
can't access /run/u-d-c-nvidia-was-loaded file
can't access /opt/amdgpu-pro/bin/amdgpu-pro-px
Looking for nvidia modules in /lib/modules/5.11.0-27-generic/kernel
Looking for nvidia modules in /lib/modules/5.11.0-27-generic/updates/dkms Looking for amdgpu modules in /lib/modules/5.11.0-27-generic/kernel
Looking for amdgpu modules in /lib/modules/5.11.0-27-generic/updates/dkms
Is nvidia loaded? no
Was nvidia unloaded? no
Is nvidia blacklisted? no
Is intel loaded? yes
Is radeon loaded? no
Is radeon blacklisted? no
Is amdgpu loaded? no
Is amdgpu blacklisted? no
Is amdgpu versioned? no
Is amdgpu pro stack? no
Is nouveau loaded? yes
Is nouveau blacklisted? no
Is nvidia kernel module available? no
Is amdgpu kernel module available? no
Vendor/Device Id: 8086:1912
BusID "PCI:0@0:2:0"
Is boot vga? yes
Vendor/Device Id: 10de:1287
BusID "PCI:1@0:0:0"
Is boot vga? no
can't access /etc/u-d-c-nvidia-runtimepm-override file
can't open /sys/module/nvidia/version
Warning: cannot check the NVIDIA driver major version
Support for runtimepm not detected.
You can override this check at your own risk by creating the /etc/u-d-c-nvidia-runtimepm-override file.
Is nvidia runtime pm supported for "0x1287"? no
Checking power status in /proc/driver/nvidia/gpus/0000:01:00.0/power
Error while opening /proc/driver/nvidia/gpus/0000:01:00.0/power
Is nvidia runtime pm enabled for "0x1287"? no
Skipping "/dev/dri/card1", driven by "nouveau"
Skipping "/dev/dri/card0", driven by "i915"
Skipping "/dev/dri/card1", driven by "nouveau"
Skipping "/dev/dri/card0", driven by "i915"
Found "/dev/dri/card1", driven by "nouveau"
output 0:
    card1-VGA-1
Number of connected outputs for /dev/dri/card1: 1
Skipping "/dev/dri/card1", driven by "nouveau"
Found "/dev/dri/card0", driven by "i915"
output 0:
    card0-DP-1
Number of connected outputs for /dev/dri/card0: 1
can't access /etc/prime-discrete
No prime-settings found. Assuming prime is not set to ON (ONDEMAND could
be on).
Does it require offloading? no
I couldn't open /var/lib/ubuntu-drivers-common/last_gfx_boot for reading. Create /var/lib/ubuntu-drivers-common/last_gfx_boot for the 1st time
last cards number = 1
Has amd? no
Has intel? yes
Has nvidia? yes
How many cards? 2
The number of cards has changed!
Has the system changed? Yes
System configuration has changed
Intel IGP detected
Desktop system detected

Good luck.
bliss
--
bliss dash SF 4 ever at dslextreme dot com

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 3/3/2022 8:12 PM, Dan Purgert wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

serge bouc wrote:

1) I can't see Dan Purgert's message (above) in my news reader (on
thunderbird), and
I don't know why... Sorry about that.

No worries, maybe there's an errant killfile entry on me (or an
imposter).

USENET has been flaky for a couple months, and network partitions
are now a normal part of operations.

Paul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 3/3/2022 6:49 PM, serge bouc wrote:

Le 03/03/2022 à 23:19, wicklowham a écrit :

On 03/03/2022 16:25, Dan Purgert wrote:

Serge - has your friend tried running the media self-test off the USB
Bootloader and/or memtest to check the RAM?   I think those are the last >>> options (or "hidden" behind the "Advanced Startup" option); but it's
been a while since I've booted off install media.

==============
It seems she can run UB 20.3 in live mode off the (bootable)USB device ,so the bootable device is OK

But when installing on a machine with an existing distro did she specify to install UB20.3 on the whole HD ? If not there might not be enough HD space to install UB 20.3 alongside the existing distro .

Personally I would first erase the HD to its "unallocated" state with Gparted  before installing UB20.3

Frank in County Wicklow Ireland

Hi everybody,

   and thanks for your answers. Several questions :

1) I can't see Dan Purgert's message (above) in my news reader (on thunderbird), and
I don't know why... Sorry about that.

2) I don't know how to run the "media self test" you mention. As Wicklowham mentions,
the live version seems ok. Is that enough?

3) There is a log after (failed) install, on the USB key. It mentions something related to Nvidia, but I don't understand it either... :-( Might be unrelated to the problem, but just
in case, here it is:

log_file: /var/log/gpu-manager.log
last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
can't access /run/u-d-c-nvidia-was-loaded file
can't access /opt/amdgpu-pro/bin/amdgpu-pro-px
Looking for nvidia modules in /lib/modules/5.11.0-27-generic/kernel
Looking for nvidia modules in /lib/modules/5.11.0-27-generic/updates/dkms Looking for amdgpu modules in /lib/modules/5.11.0-27-generic/kernel
Looking for amdgpu modules in /lib/modules/5.11.0-27-generic/updates/dkms
Is nvidia loaded? no
Was nvidia unloaded? no
Is nvidia blacklisted? no
Is intel loaded? yes
Is radeon loaded? no
Is radeon blacklisted? no
Is amdgpu loaded? no
Is amdgpu blacklisted? no
Is amdgpu versioned? no
Is amdgpu pro stack? no
Is nouveau loaded? yes
Is nouveau blacklisted? no
Is nvidia kernel module available? no
Is amdgpu kernel module available? no
Vendor/Device Id: 8086:1912
BusID "PCI:0@0:2:0"
Is boot vga? yes
Vendor/Device Id: 10de:1287
BusID "PCI:1@0:0:0"
Is boot vga? no
can't access /etc/u-d-c-nvidia-runtimepm-override file
can't open /sys/module/nvidia/version
Warning: cannot check the NVIDIA driver major version
Support for runtimepm not detected.
You can override this check at your own risk by creating the /etc/u-d-c-nvidia-runtimepm-override file.
Is nvidia runtime pm supported for "0x1287"? no
Checking power status in /proc/driver/nvidia/gpus/0000:01:00.0/power
Error while opening /proc/driver/nvidia/gpus/0000:01:00.0/power
Is nvidia runtime pm enabled for "0x1287"? no
Skipping "/dev/dri/card1", driven by "nouveau"
Skipping "/dev/dri/card0", driven by "i915"
Skipping "/dev/dri/card1", driven by "nouveau"
Skipping "/dev/dri/card0", driven by "i915"
Found "/dev/dri/card1", driven by "nouveau"
output 0:
    card1-VGA-1
Number of connected outputs for /dev/dri/card1: 1
Skipping "/dev/dri/card1", driven by "nouveau"
Found "/dev/dri/card0", driven by "i915"
output 0:
    card0-DP-1
Number of connected outputs for /dev/dri/card0: 1
can't access /etc/prime-discrete
No prime-settings found. Assuming prime is not set to ON (ONDEMAND could be on).
Does it require offloading? no
I couldn't open /var/lib/ubuntu-drivers-common/last_gfx_boot for reading. Create /var/lib/ubuntu-drivers-common/last_gfx_boot for the 1st time
last cards number = 1
Has amd? no
Has intel? yes
Has nvidia? yes
How many cards? 2
The number of cards has changed!
Has the system changed? Yes
System configuration has changed
Intel IGP detected
Desktop system detected

It's a Dell, because of the RealTek ALC3861 audio.

It has an HD530 GPU, because of the processor. The
processor is not that old, and it spans two generations
of RAM types.

The video card is NVIDIA GT 730, a card which is still shipping
today. It's one of the last cards you can buy today, with a VGA
connector on it, which hints at how old the chip is. VGA was "eliminated"
by the industry, and the only way to get it today, is to use HDMI to VGA
or DP to VGA active adapters (pretty cheap actually).

But that doesn't explain why your install is not working.

The install should have been mostly a "standard" one. Like,
Nouveau should have picked up the GT 730. It should have
detected it easily, because the card is old enough now, to be
out of mainstream support.

*******

Many years ago (2005 say), if you plugged in an AGP video card,
it disabled the chipset GPU. You could not get the benefit of
two GPUs back then.

But that changed later. The Dell, as far as Ubuntu is concerned,
has two video cards, and could run, say, four monitors. No matter
whether you plug into the VGA on the I/O plate, or the VGA
on the GT 730, you should have got a response. Maybe you would
not see the BIOS screen, but the OS screen should have showed up.

It's possible the install is failing due to a disk drive health
problem. The disk drive could be 6-7 years old or so. A Dell refurb
I got, it had a WD Blue in it, which promptly failed after I had
it for a year or so. The CRC errors hinted it had run low
on spare sectors.

Using the Ubuntu Live media, you should be able to use smartmontools

sudo apt install smartmontools

That will install the package temporarily in RAM, while you query
the hard drive. The Dell should have enough RAM, for lots of tests.
The command in the article, will give an overall health assessment
of the drive -- only if the drive is near death, does smartmontools
use bad language concerning the health. It would pass its own grandmother, given a chance (it will say "healthy", even when it is not healthy).
Still, it bears looking, if it can quickly tell
you how the drive is doing.

https://help.ubuntu.com/community/Smartmontools

If we had the Dell model number, we could toss that into a Google
and see if any other failures similar to yours have occurred. I
cannot determine the exact Dell model from the info so far, because
Dell produces bushels of this stuff.

I'm going with "hard drive", because you did mention "a lot of grinding"
while the snaps analysis was going on.

Paul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Thank you all for precise information and suggestions. We will make more
tests,
and I'll post the results, if any, or more questions, if none... ;-)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Le 04/03/2022 à 10:30, serge bouc a écrit :

Thank you all for precise information and suggestions. We will make more tests,
and I'll post the results, if any, or more questions, if none... ;-)

Finally, there seems to be a hard disk problem: when trying to format it,
it gets stuck at 14%, and then ... nada :-(
More on this soon, I hope. Thanks again to you all.
Serge.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 3/4/2022 4:24 PM, serge bouc wrote:

Le 04/03/2022 à 10:30, serge bouc a écrit :

Thank you all for precise information and suggestions. We will make more tests,
and I'll post the results, if any, or more questions, if none... ;-)

Finally, there seems to be a hard disk problem: when trying to format it,
it gets stuck at 14%, and then ... nada :-(
More on this soon, I hope. Thanks again to you all.
   Serge.

Aha! Now there will be forward progress...

A new disk drive, install will just work.

Paul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)