Discussion:
VirtualBox version compatibility concern
Add Reply
Adam
2021-03-29 03:22:33 UTC
Reply
Permalink
FYI, old Ubuntu Win.vdi used virtualbox-4.3 (v4.3.26 r98988).

For new Ubuntu install, which VirtualBox version should I install for
Win.vdi ?

For compatibility, do I need to install virtualbox-4.3 ?


I encountered problems (beyond the typos in the article) using the
following PPA method...

How To Install VirtualBox From PPA In Ubuntu 16.04
https://www.ubuntubuzz.com/2016/04/how-to-install-virtualbox-from-ppa-in.html


***@ThinkPad-T430:~$ sudo apt-key add oracle_vbox.asc
[sudo] password for xerus:
OK
***@ThinkPad-T430:~$ sudo apt-get update
Get:1 http://download.virtualbox.org/virtualbox/debian xenial InRelease
[7,883 B]
Hit:2 http://ppa.launchpad.net/atareao/telegram/ubuntu xenial InRelease

Ign:1 http://download.virtualbox.org/virtualbox/debian xenial InRelease

Hit:3 http://archive.canonical.com/ubuntu xenial InRelease

Hit:4 http://archive.ubuntu.com/ubuntu xenial InRelease

Hit:5 http://ppa.launchpad.net/ubuntu-desktop/ubuntu-make/ubuntu xenial
InRelease
Get:6 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Hit:7 http://ppa.launchpad.net/webupd8team/y-ppa-manager/ubuntu xenial
InRelease
Get:8 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
Get:9 http://archive.ubuntu.com/ubuntu xenial-security InRelease [109 kB]
Fetched 333 kB in 2s (130 kB/s)
Reading package lists... Done
W: GPG error: http://download.virtualbox.org/virtualbox/debian xenial
InRelease: The following signatures couldn't be verified because the
public key is not available: NO_PUBKEY A2F683C52980AECF
W: The repository 'http://download.virtualbox.org/virtualbox/debian
xenial InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore
potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user
configuration details.
W: There is no public key available for the following key IDs:
A2F683C52980AECF
***@ThinkPad-T430:~$ sudo apt-get install virtualbox-4.3
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package virtualbox-4.3 is not available, but is referred to by another
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'virtualbox-4.3' has no installation candidate
***@ThinkPad-T430:~$ sudo apt-get install virtualbox-4.3 --fix-missing
[sudo] password for xerus:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package virtualbox-4.3 is not available, but is referred to by another
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'virtualbox-4.3' has no installation candidate
***@ThinkPad-T430:~$
Paul
2021-03-29 04:10:40 UTC
Reply
Permalink
Post by Adam
FYI, old Ubuntu Win.vdi used virtualbox-4.3 (v4.3.26 r98988).
For new Ubuntu install, which VirtualBox version should I install for
Win.vdi ?
For compatibility, do I need to install virtualbox-4.3 ?
I encountered problems (beyond the typos in the article) using the
following PPA method...
How To Install VirtualBox From PPA In Ubuntu 16.04
https://www.ubuntubuzz.com/2016/04/how-to-install-virtualbox-from-ppa-in.html
OK
Get:1 http://download.virtualbox.org/virtualbox/debian xenial InRelease
[7,883 B]
Hit:2 http://ppa.launchpad.net/atareao/telegram/ubuntu xenial InRelease
Ign:1 http://download.virtualbox.org/virtualbox/debian xenial InRelease
Hit:3 http://archive.canonical.com/ubuntu xenial InRelease
Hit:4 http://archive.ubuntu.com/ubuntu xenial InRelease
Hit:5 http://ppa.launchpad.net/ubuntu-desktop/ubuntu-make/ubuntu xenial
InRelease
Get:6 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Hit:7 http://ppa.launchpad.net/webupd8team/y-ppa-manager/ubuntu xenial
InRelease
Get:8 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
Get:9 http://archive.ubuntu.com/ubuntu xenial-security InRelease [109 kB]
Fetched 333 kB in 2s (130 kB/s)
Reading package lists... Done
W: GPG error: http://download.virtualbox.org/virtualbox/debian xenial
InRelease: The following signatures couldn't be verified because the
public key is not available: NO_PUBKEY A2F683C52980AECF
W: The repository 'http://download.virtualbox.org/virtualbox/debian
xenial InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore
potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user
configuration details.
A2F683C52980AECF
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package virtualbox-4.3 is not available, but is referred to by another
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'virtualbox-4.3' has no installation candidate
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package virtualbox-4.3 is not available, but is referred to by another
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'virtualbox-4.3' has no installation candidate
I won't comment on your installation attempt.

I'll comment on the notion of compatibility.

The .vbi is just a container. It has an image of something
inside. Well, that does not change from one release of VBox
to the next. A .vbi is just a .vbi. It's like a file system.
It's a means of transport and that is all.

However, there is a "settings file", which is XML based,
and it's critical. The settings control the
virtual hardware declarations.

You might have noticed for example, you can declare the virtual
hardware to have an Intel 440BX. That's my computer from the
year 2000. It would be a perfect chipset for an OS like Win98,
which is from that era. Or even Win2K or WinXP. Those would
likely have the vanilla IDE driver for that, as well as the
appropriate INT14 and INT15 behavior.

When you change from one version of VBox to another, some
of those items change. In particular, VirtualBox 6 made
some changes to the virtual graphics. It went from one
flavor to three flavors. If you download the VBox 6 PDF manual,
it will tell you what the purpose of those three is.

When VirtualBox 6 starts up, and sees the old XML files,
it should do its best to rewrite the XML files, using
the newer hardware items. It should be picking the
nearest equivalent graphic item to the old format.

I think I found in one case, that it had not done that
correctly, and I had to enter the Settings and select
another, and see if the Guest was "less pissed off at me".

Generally, if you deviate from the default selection,
it does not always end well for you. I think the first
time I tried that, the Guest black screened on me
(and you know how hard it is to debug something when
the symptoms are like that). While it might be fun
to change from 440BX for chipset, to ICH6 or ICH9 or
something, it doesn't always work out the way you
expected. That's the lesson I learned, was selecting
a "sexy" piece of hardware, was entirely unnecessary.
If it would accept the 440BX in the Guest OS, well,
that's just fine. Leave it.

But for the graphics, you pretty well have to fix it,
because sometimes if it makes the wrong choice, the
screen can't be resized.

All I'm pointing out here, is when the VBox 6 replaces
VBox 4, some of those virtual hardware items will
have changed. And occasionally, some work will be
required to get the Guest to boot. You want to keep
backup copies of the .vbi, so if the Guest OS records
that it's angry, you can remove the VBI file and restore
your backup to the folder. And try again. It won't
be the fault of the .vbi file, but if the OS decides
it's "Not Genuine" or the like, it may decide to
discard one tiny file, and that could make a difference
to later boot attempts.

You would hope Oracle does the migration properly,
each time the VBox version changes. But I've had at
least one case, where the transition wasn't perfect
and it took me a few tries to get it right.

Paul
Adam
2021-03-29 06:02:20 UTC
Reply
Permalink
Post by Paul
Post by Adam
FYI, old Ubuntu Win.vdi used virtualbox-4.3 (v4.3.26 r98988).
For new Ubuntu install, which VirtualBox version should I install for
Win.vdi ?
For compatibility, do I need to install virtualbox-4.3 ?
I encountered problems (beyond the typos in the article) using the
following PPA method...
How To Install VirtualBox From PPA In Ubuntu 16.04
https://www.ubuntubuzz.com/2016/04/how-to-install-virtualbox-from-ppa-in.html
OK
Get:1 http://download.virtualbox.org/virtualbox/debian xenial
InRelease [7,883 B]
Hit:2 http://ppa.launchpad.net/atareao/telegram/ubuntu xenial InRelease
Ign:1 http://download.virtualbox.org/virtualbox/debian xenial InRelease
Hit:3 http://archive.canonical.com/ubuntu xenial InRelease
Hit:4 http://archive.ubuntu.com/ubuntu xenial InRelease
Hit:5 http://ppa.launchpad.net/ubuntu-desktop/ubuntu-make/ubuntu
xenial InRelease
Get:6 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Hit:7 http://ppa.launchpad.net/webupd8team/y-ppa-manager/ubuntu xenial
InRelease
Get:8 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
Get:9 http://archive.ubuntu.com/ubuntu xenial-security InRelease [109 kB]
Fetched 333 kB in 2s (130 kB/s)
Reading package lists... Done
W: GPG error: http://download.virtualbox.org/virtualbox/debian xenial
InRelease: The following signatures couldn't be verified because the
public key is not available: NO_PUBKEY A2F683C52980AECF
W: The repository 'http://download.virtualbox.org/virtualbox/debian
xenial InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore
potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user
configuration details.
A2F683C52980AECF
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package virtualbox-4.3 is not available, but is referred to by another
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'virtualbox-4.3' has no installation candidate
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package virtualbox-4.3 is not available, but is referred to by another
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'virtualbox-4.3' has no installation candidate
I won't comment on your installation attempt.
I'll comment on the notion of compatibility.
The .vbi is just a container. It has an image of something
inside. Well, that does not change from one release of VBox
to the next. A .vbi is just a .vbi. It's like a file system.
It's a means of transport and that is all.
However, there is a "settings file", which is XML based,
and it's critical. The settings control the
virtual hardware declarations.
You might have noticed for example, you can declare the virtual
hardware to have an Intel 440BX. That's my computer from the
year 2000. It would be a perfect chipset for an OS like Win98,
which is from that era. Or even Win2K or WinXP. Those would
likely have the vanilla IDE driver for that, as well as the
appropriate INT14 and INT15 behavior.
When you change from one version of VBox to another, some
of those items change. In particular, VirtualBox 6 made
some changes to the virtual graphics. It went from one
flavor to three flavors. If you download the VBox 6 PDF manual,
it will tell you what the purpose of those three is.
When VirtualBox 6 starts up, and sees the old XML files,
it should do its best to rewrite the XML files, using
the newer hardware items. It should be picking the
nearest equivalent graphic item to the old format.
I think I found in one case, that it had not done that
correctly, and I had to enter the Settings and select
another, and see if the Guest was "less pissed off at me".
Generally, if you deviate from the default selection,
it does not always end well for you. I think the first
time I tried that, the Guest black screened on me
(and you know how hard it is to debug something when
the symptoms are like that). While it might be fun
to change from 440BX for chipset, to ICH6 or ICH9 or
something, it doesn't always work out the way you
expected. That's the lesson I learned, was selecting
a "sexy" piece of hardware, was entirely unnecessary.
If it would accept the 440BX in the Guest OS, well,
that's just fine. Leave it.
But for the graphics, you pretty well have to fix it,
because sometimes if it makes the wrong choice, the
screen can't be resized.
All I'm pointing out here, is when the VBox 6 replaces
VBox 4, some of those virtual hardware items will
have changed. And occasionally, some work will be
required to get the Guest to boot. You want to keep
backup copies of the .vbi, so if the Guest OS records
that it's angry, you can remove the VBI file and restore
your backup to the folder. And try again. It won't
be the fault of the .vbi file, but if the OS decides
it's "Not Genuine" or the like, it may decide to
discard one tiny file, and that could make a difference
to later boot attempts.
You would hope Oracle does the migration properly,
each time the VBox version changes. But I've had at
least one case, where the transition wasn't perfect
and it took me a few tries to get it right.
Paul
Thanks, Guru Paul !!

Almost forgot about the hidden .VirtualBox config files (XML) directory.
Thanks for the reminder.

Already tarballed and extracted the VMs directory.

Just did the same for the hidden .VirtualBox config files (XML) directory.

How about the Extension Pack, which is for VBox 4 ?


***@ThinkPad-T430:~$ find .VirtualBox/. -print
.VirtualBox/.
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.4.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.20.vbox-extpack
.VirtualBox/./compreg.dat
.VirtualBox/./VBoxSVC.log.6
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.8.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.20.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.12.vbox-extpack
.VirtualBox/./VBoxSVC.log.7
.VirtualBox/./xpti.dat
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.14.vbox-extpack
.VirtualBox/./VirtualBox.xml-prev
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.10.vbox-extpack
.VirtualBox/./VBoxSVC.log.1
.VirtualBox/./VBoxSVC.log.2
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.16.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.22.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.22.vbox-extpack
.VirtualBox/./selectorwindow.log
.VirtualBox/./VBoxSVC.log.9
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.14.vbox-extpack
.VirtualBox/./selectorwindow.log.1
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.26.vbox-extpack
.VirtualBox/./VBoxSVC.log.10
.VirtualBox/./vbox-ssl-cacertificate.crt
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.6.vbox-extpack
.VirtualBox/./VBoxSVC.log.8
.VirtualBox/./VBoxSVC.log.3
.VirtualBox/./VirtualBox.xml
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.12.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.10.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.14.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.8.vbox-extpack
.VirtualBox/./VBoxSVC.log.4
.VirtualBox/./VBoxSVC.log
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.16.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.18.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.18.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.20.vbox-extpack
.VirtualBox/./VBoxSVC.log.5
***@ThinkPad-T430:~$
***@ThinkPad-T430:~$ find VirtualBox\ VMs/. -print
VirtualBox VMs/.
VirtualBox VMs/./Win
VirtualBox VMs/./Win/Logs
VirtualBox VMs/./Win/Logs/VBox.log
VirtualBox VMs/./Win/Logs/VBox.log.2
VirtualBox VMs/./Win/Logs/VBox.log.3
VirtualBox VMs/./Win/Logs/VBox.log.1
VirtualBox VMs/./Win/Win.vbox
VirtualBox VMs/./Win/Win.vbox-prev
VirtualBox VMs/./Win/Win.vdi
***@ThinkPad-T430:~$
Paul
2021-03-29 10:16:52 UTC
Reply
Permalink
Post by Adam
Post by Paul
Post by Adam
FYI, old Ubuntu Win.vdi used virtualbox-4.3 (v4.3.26 r98988).
For new Ubuntu install, which VirtualBox version should I install for
Win.vdi ?
For compatibility, do I need to install virtualbox-4.3 ?
I encountered problems (beyond the typos in the article) using the
following PPA method...
How To Install VirtualBox From PPA In Ubuntu 16.04
https://www.ubuntubuzz.com/2016/04/how-to-install-virtualbox-from-ppa-in.html
OK
Get:1 http://download.virtualbox.org/virtualbox/debian xenial
InRelease [7,883 B]
Hit:2 http://ppa.launchpad.net/atareao/telegram/ubuntu xenial InRelease
Ign:1 http://download.virtualbox.org/virtualbox/debian xenial InRelease
Hit:3 http://archive.canonical.com/ubuntu xenial InRelease
Hit:4 http://archive.ubuntu.com/ubuntu xenial InRelease
Hit:5 http://ppa.launchpad.net/ubuntu-desktop/ubuntu-make/ubuntu
xenial InRelease
Get:6 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Hit:7 http://ppa.launchpad.net/webupd8team/y-ppa-manager/ubuntu xenial
InRelease
Get:8 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
Get:9 http://archive.ubuntu.com/ubuntu xenial-security InRelease [109 kB]
Fetched 333 kB in 2s (130 kB/s)
Reading package lists... Done
W: GPG error: http://download.virtualbox.org/virtualbox/debian xenial
InRelease: The following signatures couldn't be verified because the
public key is not available: NO_PUBKEY A2F683C52980AECF
W: The repository 'http://download.virtualbox.org/virtualbox/debian
xenial InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore
potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user
configuration details.
A2F683C52980AECF
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package virtualbox-4.3 is not available, but is referred to by another
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'virtualbox-4.3' has no installation candidate
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package virtualbox-4.3 is not available, but is referred to by another
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'virtualbox-4.3' has no installation candidate
I won't comment on your installation attempt.
I'll comment on the notion of compatibility.
The .vbi is just a container. It has an image of something
inside. Well, that does not change from one release of VBox
to the next. A .vbi is just a .vbi. It's like a file system.
It's a means of transport and that is all.
However, there is a "settings file", which is XML based,
and it's critical. The settings control the
virtual hardware declarations.
You might have noticed for example, you can declare the virtual
hardware to have an Intel 440BX. That's my computer from the
year 2000. It would be a perfect chipset for an OS like Win98,
which is from that era. Or even Win2K or WinXP. Those would
likely have the vanilla IDE driver for that, as well as the
appropriate INT14 and INT15 behavior.
When you change from one version of VBox to another, some
of those items change. In particular, VirtualBox 6 made
some changes to the virtual graphics. It went from one
flavor to three flavors. If you download the VBox 6 PDF manual,
it will tell you what the purpose of those three is.
When VirtualBox 6 starts up, and sees the old XML files,
it should do its best to rewrite the XML files, using
the newer hardware items. It should be picking the
nearest equivalent graphic item to the old format.
I think I found in one case, that it had not done that
correctly, and I had to enter the Settings and select
another, and see if the Guest was "less pissed off at me".
Generally, if you deviate from the default selection,
it does not always end well for you. I think the first
time I tried that, the Guest black screened on me
(and you know how hard it is to debug something when
the symptoms are like that). While it might be fun
to change from 440BX for chipset, to ICH6 or ICH9 or
something, it doesn't always work out the way you
expected. That's the lesson I learned, was selecting
a "sexy" piece of hardware, was entirely unnecessary.
If it would accept the 440BX in the Guest OS, well,
that's just fine. Leave it.
But for the graphics, you pretty well have to fix it,
because sometimes if it makes the wrong choice, the
screen can't be resized.
All I'm pointing out here, is when the VBox 6 replaces
VBox 4, some of those virtual hardware items will
have changed. And occasionally, some work will be
required to get the Guest to boot. You want to keep
backup copies of the .vbi, so if the Guest OS records
that it's angry, you can remove the VBI file and restore
your backup to the folder. And try again. It won't
be the fault of the .vbi file, but if the OS decides
it's "Not Genuine" or the like, it may decide to
discard one tiny file, and that could make a difference
to later boot attempts.
You would hope Oracle does the migration properly,
each time the VBox version changes. But I've had at
least one case, where the transition wasn't perfect
and it took me a few tries to get it right.
Paul
Thanks, Guru Paul !!
Almost forgot about the hidden .VirtualBox config files (XML) directory.
Thanks for the reminder.
Already tarballed and extracted the VMs directory.
Just did the same for the hidden .VirtualBox config files (XML) directory.
How about the Extension Pack, which is for VBox 4 ?
.VirtualBox/.
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.4.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.20.vbox-extpack
.VirtualBox/./compreg.dat
.VirtualBox/./VBoxSVC.log.6
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.8.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.20.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.12.vbox-extpack
.VirtualBox/./VBoxSVC.log.7
.VirtualBox/./xpti.dat
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.14.vbox-extpack
.VirtualBox/./VirtualBox.xml-prev
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.10.vbox-extpack
.VirtualBox/./VBoxSVC.log.1
.VirtualBox/./VBoxSVC.log.2
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.16.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.22.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.22.vbox-extpack
.VirtualBox/./selectorwindow.log
.VirtualBox/./VBoxSVC.log.9
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.14.vbox-extpack
.VirtualBox/./selectorwindow.log.1
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.26.vbox-extpack
.VirtualBox/./VBoxSVC.log.10
.VirtualBox/./vbox-ssl-cacertificate.crt
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.6.vbox-extpack
.VirtualBox/./VBoxSVC.log.8
.VirtualBox/./VBoxSVC.log.3
.VirtualBox/./VirtualBox.xml
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.12.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.10.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.14.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.8.vbox-extpack
.VirtualBox/./VBoxSVC.log.4
.VirtualBox/./VBoxSVC.log
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.16.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.18.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.18.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.20.vbox-extpack
.VirtualBox/./VBoxSVC.log.5
VirtualBox VMs/.
VirtualBox VMs/./Win
VirtualBox VMs/./Win/Logs
VirtualBox VMs/./Win/Logs/VBox.log
VirtualBox VMs/./Win/Logs/VBox.log.2
VirtualBox VMs/./Win/Logs/VBox.log.3
VirtualBox VMs/./Win/Logs/VBox.log.1
VirtualBox VMs/./Win/Win.vbox
VirtualBox VMs/./Win/Win.vbox-prev
VirtualBox VMs/./Win/Win.vdi
The extension pack, is for things like passthru USB.

You would think your Package Manager would include that.
It's no problem to go to the virtualbox site and download
a matching version manually. Then when you double-click the
file, it should open in VirtualBox and be unpacked.

The Guest Additions are another item. The VBox 4 .vbi will
have Guest Additions for VBox 4 in it. You can apply the
Guest Additions for VBox 6. That might involve some DKMS
work and take a bit of time.

I doubt every one of my Guest Additions in VMs here is
up-to-date, but the tool usually warns you about
versioning when it notices.

That's why you keep backups, until the smoke has cleared :-)
There'll always be some little detail that needs touchup.

But the settings file is the one that has some degree of
leverage, and sometimes you do have to look in there,
to see how fouled up things are.

Paul
Adam
2021-03-29 18:43:49 UTC
Reply
Permalink
Post by Paul
Post by Adam
Post by Paul
Post by Adam
FYI, old Ubuntu Win.vdi used virtualbox-4.3 (v4.3.26 r98988).
For new Ubuntu install, which VirtualBox version should I install for
Win.vdi ?
For compatibility, do I need to install virtualbox-4.3 ?
I encountered problems (beyond the typos in the article) using the
following PPA method...
How To Install VirtualBox From PPA In Ubuntu 16.04
https://www.ubuntubuzz.com/2016/04/how-to-install-virtualbox-from-ppa-in.html
I undid whatever was done based on article (above).
And, installed virtualbox-5.0. There's progress.

Now, I have network settings issues on VM startup...

Loading Image...

Loading Image...

Loading Image...

How to fix ?
Post by Paul
Post by Adam
Post by Paul
I won't comment on your installation attempt.
I'll comment on the notion of compatibility.
The .vbi is just a container. It has an image of something
inside. Well, that does not change from one release of VBox
to the next. A .vbi is just a .vbi. It's like a file system.
It's a means of transport and that is all.
However, there is a "settings file", which is XML based,
and it's critical. The settings control the
virtual hardware declarations.
You might have noticed for example, you can declare the virtual
hardware to have an Intel 440BX. That's my computer from the
year 2000. It would be a perfect chipset for an OS like Win98,
which is from that era. Or even Win2K or WinXP. Those would
likely have the vanilla IDE driver for that, as well as the
appropriate INT14 and INT15 behavior.
When you change from one version of VBox to another, some
of those items change. In particular, VirtualBox 6 made
some changes to the virtual graphics. It went from one
flavor to three flavors. If you download the VBox 6 PDF manual,
it will tell you what the purpose of those three is.
When VirtualBox 6 starts up, and sees the old XML files,
it should do its best to rewrite the XML files, using
the newer hardware items. It should be picking the
nearest equivalent graphic item to the old format.
I think I found in one case, that it had not done that
correctly, and I had to enter the Settings and select
another, and see if the Guest was "less pissed off at me".
Generally, if you deviate from the default selection,
it does not always end well for you. I think the first
time I tried that, the Guest black screened on me
(and you know how hard it is to debug something when
the symptoms are like that). While it might be fun
to change from 440BX for chipset, to ICH6 or ICH9 or
something, it doesn't always work out the way you
expected. That's the lesson I learned, was selecting
a "sexy" piece of hardware, was entirely unnecessary.
If it would accept the 440BX in the Guest OS, well,
that's just fine. Leave it.
But for the graphics, you pretty well have to fix it,
because sometimes if it makes the wrong choice, the
screen can't be resized.
All I'm pointing out here, is when the VBox 6 replaces
VBox 4, some of those virtual hardware items will
have changed. And occasionally, some work will be
required to get the Guest to boot. You want to keep
backup copies of the .vbi, so if the Guest OS records
that it's angry, you can remove the VBI file and restore
your backup to the folder. And try again. It won't
be the fault of the .vbi file, but if the OS decides
it's "Not Genuine" or the like, it may decide to
discard one tiny file, and that could make a difference
to later boot attempts.
You would hope Oracle does the migration properly,
each time the VBox version changes. But I've had at
least one case, where the transition wasn't perfect
and it took me a few tries to get it right.
Paul
Thanks, Guru Paul !!
Almost forgot about the hidden .VirtualBox config files (XML)
directory. Thanks for the reminder.
Already tarballed and extracted the VMs directory.
Just did the same for the hidden .VirtualBox config files (XML) directory.
How about the Extension Pack, which is for VBox 4 ?
.VirtualBox/.
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.4.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.20.vbox-extpack
.VirtualBox/./compreg.dat
.VirtualBox/./VBoxSVC.log.6
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.8.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.20.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.12.vbox-extpack
.VirtualBox/./VBoxSVC.log.7
.VirtualBox/./xpti.dat
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.14.vbox-extpack
.VirtualBox/./VirtualBox.xml-prev
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.10.vbox-extpack
.VirtualBox/./VBoxSVC.log.1
.VirtualBox/./VBoxSVC.log.2
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.16.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.22.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.22.vbox-extpack
.VirtualBox/./selectorwindow.log
.VirtualBox/./VBoxSVC.log.9
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.14.vbox-extpack
.VirtualBox/./selectorwindow.log.1
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.26.vbox-extpack
.VirtualBox/./VBoxSVC.log.10
.VirtualBox/./vbox-ssl-cacertificate.crt
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.6.vbox-extpack
.VirtualBox/./VBoxSVC.log.8
.VirtualBox/./VBoxSVC.log.3
.VirtualBox/./VirtualBox.xml
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.12.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.10.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.14.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.8.vbox-extpack
.VirtualBox/./VBoxSVC.log.4
.VirtualBox/./VBoxSVC.log
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.16.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.18.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.18.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.20.vbox-extpack
.VirtualBox/./VBoxSVC.log.5
VirtualBox VMs/.
VirtualBox VMs/./Win
VirtualBox VMs/./Win/Logs
VirtualBox VMs/./Win/Logs/VBox.log
VirtualBox VMs/./Win/Logs/VBox.log.2
VirtualBox VMs/./Win/Logs/VBox.log.3
VirtualBox VMs/./Win/Logs/VBox.log.1
VirtualBox VMs/./Win/Win.vbox
VirtualBox VMs/./Win/Win.vbox-prev
VirtualBox VMs/./Win/Win.vdi
The extension pack, is for things like passthru USB.
You would think your Package Manager would include that.
It's no problem to go to the virtualbox site and download
a matching version manually. Then when you double-click the
file, it should open in VirtualBox and be unpacked.
Will deal with extras later.
Post by Paul
The Guest Additions are another item. The VBox 4 .vbi will
have Guest Additions for VBox 4 in it. You can apply the
Guest Additions for VBox 6. That might involve some DKMS
work and take a bit of time.
Okay, will do later.
Post by Paul
I doubt every one of my Guest Additions in VMs here is
up-to-date, but the tool usually warns you about
versioning when it notices.
That's why you keep backups, until the smoke has cleared :-)
There'll always be some little detail that needs touchup.
I have tarballs, source of tarballs and disk clones. :-)
Post by Paul
But the settings file is the one that has some degree of
leverage, and sometimes you do have to look in there,
to see how fouled up things are.
Paul
Paul
2021-03-29 23:47:07 UTC
Reply
Permalink
Post by Adam
Post by Adam
FYI, old Ubuntu Win.vdi used virtualbox-4.3 (v4.3.26 r98988).
For new Ubuntu install, which VirtualBox version should I install for
Win.vdi ?
For compatibility, do I need to install virtualbox-4.3 ?
I encountered problems (beyond the typos in the article) using the
following PPA method...
How To Install VirtualBox From PPA In Ubuntu 16.04
https://www.ubuntubuzz.com/2016/04/how-to-install-virtualbox-from-ppa-in.html
I undid whatever was done based on article (above).
And, installed virtualbox-5.0. There's progress.
Now, I have network settings issues on VM startup...
https://i.postimg.cc/qM2tYmYJ/Could-not-start-the-machine-because-physical-network-interfaces-were-not-found-eth0-adapter-1.png
https://i.postimg.cc/XN2SWFZT/VM-Network-Settings-Adapter-1.png
https://i.postimg.cc/VsZTp8pw/VBox-Error-NS-ERROR-FAILURE.png
How to fix ?
Well, this falls under the general topic of the Settings file
for each VM and what it says.

You know that "eth0" is a pre-SystemD way of naming the NIC.
And the convention used in the settings panel in one of
your pictures, shows the SystemD convention for naming the same
NIC.

Somehow, you have to convince VirtualBox, they're the same thing.

You could, for example change the settings using the VBox settings
panel. You can also visit the settings file, spot the "eth0" in
it and change it to the SystemD version.

I just want you to be aware, what VBox is doing sometimes, when
it complains. It's holding your settings file up and treating
it as "golden", then it notes that the situation on the ground,
is not the same as what the file says. VBox is full of consistency
checks. It will find the tinest defect, and ruin your day.

Using the settings panel, the GUI, that's the easy way to do edits.
But there will also be times, where you cannot decipher the error
message, and that's when you'll have the XML in the settings
file open for a look. I sometimes go in there and delete several
lines referring to volumes that no longer exist. As an example
of house-cleaning.

VBox 6 has become marginally worse, because there's a Media Manager,
and if you want to change a reference to point to a different .vdi
file, you have to remove the original file, remove it from the
Media Manager, add the new file to the Media Manager, then
enter the settings and add the file to the actual virtual machine.
Obviously, a design reviewed by career bureaucrats. I've had other
tools where it was "anything goes", you could delete a container,
throw in another... and the tool wouldn't even notice. Only doing
stuff that caused functional failures, would become wobbly. But
VBox does it's version of "Papers, please" any time you make the
slightest change. And your example, of the foaming at the mouth
because of the NIC name, that's classic behavior. Either fix from
the GUI, or fix with a text editor.

Paul
Adam
2021-03-30 00:26:33 UTC
Reply
Permalink
Post by Paul
Post by Adam
Post by Adam
FYI, old Ubuntu Win.vdi used virtualbox-4.3 (v4.3.26 r98988).
For new Ubuntu install, which VirtualBox version should I install for
Win.vdi ?
For compatibility, do I need to install virtualbox-4.3 ?
I encountered problems (beyond the typos in the article) using the
following PPA method...
How To Install VirtualBox From PPA In Ubuntu 16.04
https://www.ubuntubuzz.com/2016/04/how-to-install-virtualbox-from-ppa-in.html
I undid whatever was done based on article (above).
And, installed virtualbox-5.0. There's progress.
Now, I have network settings issues on VM startup...
https://i.postimg.cc/qM2tYmYJ/Could-not-start-the-machine-because-physical-network-interfaces-were-not-found-eth0-adapter-1.png
https://i.postimg.cc/XN2SWFZT/VM-Network-Settings-Adapter-1.png
https://i.postimg.cc/VsZTp8pw/VBox-Error-NS-ERROR-FAILURE.png
How to fix ?
Well, this falls under the general topic of the Settings file
for each VM and what it says.
You know that "eth0" is a pre-SystemD way of naming the NIC.
And the convention used in the settings panel in one of
your pictures, shows the SystemD convention for naming the same
NIC.
Somehow, you have to convince VirtualBox, they're the same thing.
You could, for example change the settings using the VBox settings
panel. You can also visit the settings file, spot the "eth0" in
it and change it to the SystemD version.
I just want you to be aware, what VBox is doing sometimes, when
it complains. It's holding your settings file up and treating
it as "golden", then it notes that the situation on the ground,
is not the same as what the file says. VBox is full of consistency
checks. It will find the tinest defect, and ruin your day.
Using the settings panel, the GUI, that's the easy way to do edits.
But there will also be times, where you cannot decipher the error
message, and that's when you'll have the XML in the settings
file open for a look. I sometimes go in there and delete several
lines referring to volumes that no longer exist. As an example
of house-cleaning.
VBox 6 has become marginally worse, because there's a Media Manager,
and if you want to change a reference to point to a different .vdi
file, you have to remove the original file, remove it from the
Media Manager, add the new file to the Media Manager, then
enter the settings and add the file to the actual virtual machine.
Obviously, a design reviewed by career bureaucrats. I've had other
tools where it was "anything goes", you could delete a container,
throw in another... and the tool wouldn't even notice. Only doing
stuff that caused functional failures, would become wobbly. But
VBox does it's version of "Papers, please" any time you make the
slightest change. And your example, of the foaming at the mouth
because of the NIC name, that's classic behavior. Either fix from
the GUI, or fix with a text editor.
Paul
Adding network printer now to warm up network usage.

I thought it might be due to lack of network usage because
/etc/network/interfaces file looks pretty bare...

***@ThinkPad-T430:~$ cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
***@ThinkPad-T430:~$
***@ThinkPad-T430:~$ ifconfig
enp0s25 Link encap:Ethernet HWaddr 28:d2:44:29:7d:ac
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:530 errors:0 dropped:0 overruns:0 frame:0
TX packets:2263 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:44906 (44.9 KB) TX bytes:677922 (677.9 KB)
Interrupt:20 Memory:f2500000-f2520000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:9773 errors:0 dropped:0 overruns:0 frame:0
TX packets:9773 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:812285 (812.2 KB) TX bytes:812285 (812.2 KB)

wlp3s0 Link encap:Ethernet HWaddr a4:4e:31:72:62:c8
inet addr:192.168.0.128 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: 2607:fb90:9c26:aec:a4c1:4d8c:86f7:c665/64
Scope:Global
inet6 addr: fe80::86b6:aed0:a090:2eb6/64 Scope:Link
inet6 addr: 2607:fb90:9c26:aec:9182:307b:70c9:e6bd/64
Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:139642 errors:0 dropped:0 overruns:0 frame:0
TX packets:101057 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:142727120 (142.7 MB) TX bytes:18919826 (18.9 MB)

***@ThinkPad-T430:~$
Adam
2021-03-30 05:00:50 UTC
Reply
Permalink
Post by Paul
Post by Adam
Post by Adam
FYI, old Ubuntu Win.vdi used virtualbox-4.3 (v4.3.26 r98988).
For new Ubuntu install, which VirtualBox version should I install for
Win.vdi ?
For compatibility, do I need to install virtualbox-4.3 ?
I encountered problems (beyond the typos in the article) using the
following PPA method...
How To Install VirtualBox From PPA In Ubuntu 16.04
https://www.ubuntubuzz.com/2016/04/how-to-install-virtualbox-from-ppa-in.html
I undid whatever was done based on article (above).
And, installed virtualbox-5.0. There's progress.
Now, I have network settings issues on VM startup...
https://i.postimg.cc/qM2tYmYJ/Could-not-start-the-machine-because-physical-network-interfaces-were-not-found-eth0-adapter-1.png
https://i.postimg.cc/XN2SWFZT/VM-Network-Settings-Adapter-1.png
https://i.postimg.cc/VsZTp8pw/VBox-Error-NS-ERROR-FAILURE.png
How to fix ?
Well, this falls under the general topic of the Settings file
for each VM and what it says.
You know that "eth0" is a pre-SystemD way of naming the NIC.
And the convention used in the settings panel in one of
your pictures, shows the SystemD convention for naming the same
NIC.
Somehow, you have to convince VirtualBox, they're the same thing.
You could, for example change the settings using the VBox settings
panel. You can also visit the settings file, spot the "eth0" in
it and change it to the SystemD version.
I just want you to be aware, what VBox is doing sometimes, when
it complains. It's holding your settings file up and treating
it as "golden", then it notes that the situation on the ground,
is not the same as what the file says. VBox is full of consistency
checks. It will find the tinest defect, and ruin your day.
Using the settings panel, the GUI, that's the easy way to do edits.
But there will also be times, where you cannot decipher the error
message, and that's when you'll have the XML in the settings
file open for a look. I sometimes go in there and delete several
lines referring to volumes that no longer exist. As an example
of house-cleaning.
After downloading and installing the corresponding VBox Extension Pack,
I was able to login to VM to see my data, which is still there. :-)

Then, things broke again after installing
virtualbox-guest-additions-iso, which replaced virtualbox-5.0 with
virtualbox-5.1.38...

Loading Image...

Loading Image...

Loading Image...

Loading Image...

Loading Image...

How to fix ?
Post by Paul
VBox 6 has become marginally worse, because there's a Media Manager,
and if you want to change a reference to point to a different .vdi
file, you have to remove the original file, remove it from the
Media Manager, add the new file to the Media Manager, then
enter the settings and add the file to the actual virtual machine.
Obviously, a design reviewed by career bureaucrats. I've had other
tools where it was "anything goes", you could delete a container,
throw in another... and the tool wouldn't even notice. Only doing
stuff that caused functional failures, would become wobbly. But
VBox does it's version of "Papers, please" any time you make the
slightest change. And your example, of the foaming at the mouth
because of the NIC name, that's classic behavior. Either fix from
the GUI, or fix with a text editor.
Paul
Adam
2021-03-30 07:16:42 UTC
Reply
Permalink
Post by Adam
Post by Paul
Post by Adam
Post by Adam
FYI, old Ubuntu Win.vdi used virtualbox-4.3 (v4.3.26 r98988).
For new Ubuntu install, which VirtualBox version should I install for
Win.vdi ?
For compatibility, do I need to install virtualbox-4.3 ?
I encountered problems (beyond the typos in the article) using the
following PPA method...
How To Install VirtualBox From PPA In Ubuntu 16.04
https://www.ubuntubuzz.com/2016/04/how-to-install-virtualbox-from-ppa-in.html
I undid whatever was done based on article (above).
And, installed virtualbox-5.0. There's progress.
Now, I have network settings issues on VM startup...
https://i.postimg.cc/qM2tYmYJ/Could-not-start-the-machine-because-physical-network-interfaces-were-not-found-eth0-adapter-1.png
https://i.postimg.cc/XN2SWFZT/VM-Network-Settings-Adapter-1.png
https://i.postimg.cc/VsZTp8pw/VBox-Error-NS-ERROR-FAILURE.png
How to fix ?
Well, this falls under the general topic of the Settings file
for each VM and what it says.
You know that "eth0" is a pre-SystemD way of naming the NIC.
And the convention used in the settings panel in one of
your pictures, shows the SystemD convention for naming the same
NIC.
Somehow, you have to convince VirtualBox, they're the same thing.
You could, for example change the settings using the VBox settings
panel. You can also visit the settings file, spot the "eth0" in
it and change it to the SystemD version.
I just want you to be aware, what VBox is doing sometimes, when
it complains. It's holding your settings file up and treating
it as "golden", then it notes that the situation on the ground,
is not the same as what the file says. VBox is full of consistency
checks. It will find the tinest defect, and ruin your day.
Using the settings panel, the GUI, that's the easy way to do edits.
But there will also be times, where you cannot decipher the error
message, and that's when you'll have the XML in the settings
file open for a look. I sometimes go in there and delete several
lines referring to volumes that no longer exist. As an example
of house-cleaning.
After downloading and installing the corresponding VBox Extension Pack,
I was able to login to VM to see my data, which is still there. :-)
Then, things broke again after installing
virtualbox-guest-additions-iso, which replaced virtualbox-5.0 with
virtualbox-5.1.38...
https://i.postimg.cc/zGkvYSQV/Virtual-Box-Error-VT-x-is-disabled-in-the-BIOS-for-all-CPU-modes-VERR-VMX-MSR-ALL-VMX-DISABLED.png
How to fix ?
Works again. Fixed by enabling both VT-x options in BIOS.


OT question about Display resolution. How to get higher resolution ?

Loading Image...
Post by Adam
Post by Paul
VBox 6 has become marginally worse, because there's a Media Manager,
and if you want to change a reference to point to a different .vdi
file, you have to remove the original file, remove it from the
Media Manager, add the new file to the Media Manager, then
enter the settings and add the file to the actual virtual machine.
Obviously, a design reviewed by career bureaucrats. I've had other
tools where it was "anything goes", you could delete a container,
throw in another... and the tool wouldn't even notice. Only doing
stuff that caused functional failures, would become wobbly. But
VBox does it's version of "Papers, please" any time you make the
slightest change. And your example, of the foaming at the mouth
because of the NIC name, that's classic behavior. Either fix from
the GUI, or fix with a text editor.
Paul
Paul
2021-03-30 11:50:02 UTC
Reply
Permalink
Post by Adam
Post by Adam
After downloading and installing the corresponding VBox Extension Pack,
I was able to login to VM to see my data, which is still there. :-)
Then, things broke again after installing
virtualbox-guest-additions-iso, which replaced virtualbox-5.0 with
virtualbox-5.1.38...
https://i.postimg.cc/zGkvYSQV/Virtual-Box-Error-VT-x-is-disabled-in-the-BIOS-for-all-CPU-modes-VERR-VMX-MSR-ALL-VMX-DISABLED.png
How to fix ?
Works again. Fixed by enabling both VT-x options in BIOS.
Yes, that's what the message was indicating, is that the BIOS
setting should be enabled.
Post by Adam
OT question about Display resolution. How to get higher resolution ?
https://i.postimg.cc/T2bpknFN/Display-Resolution.png
That depends on what the emulated hardware claims.

In the VBox settings, if you hold your mouse over the
warning at the bottom of the graphics settings screen in
Settings, it tells you what to do. I think I have
"VBoxVGA" selected for both VMs at present.

Win7 OS choice by user:

The virtual machine ... recommended one (VBoxSVGA)

Ubuntu OS choice by user:

The virtual machine ... recommended one (VMSVGA)

The recommendation is different, by family.

I presume the "recommended" choices give higher graphics
settings, just a guess. I don't really know what
properties these things are claiming - the
VBoxVGA vs VBoxSVGA is probably just size. But
why even bother offering three options, if two
options would cover all the cases ?

Paul
Adam
2021-03-30 14:35:16 UTC
Reply
Permalink
Post by Paul
Post by Adam
Post by Adam
After downloading and installing the corresponding VBox Extension Pack,
I was able to login to VM to see my data, which is still there. :-)
Then, things broke again after installing
virtualbox-guest-additions-iso, which replaced virtualbox-5.0 with
virtualbox-5.1.38...
https://i.postimg.cc/zGkvYSQV/Virtual-Box-Error-VT-x-is-disabled-in-the-BIOS-for-all-CPU-modes-VERR-VMX-MSR-ALL-VMX-DISABLED.png
How to fix ?
Works again. Fixed by enabling both VT-x options in BIOS.
Yes, that's what the message was indicating, is that the BIOS
setting should be enabled.
Post by Adam
OT question about Display resolution. How to get higher resolution ?
https://i.postimg.cc/T2bpknFN/Display-Resolution.png
Sorry for OT (Off Topic) question, I should have been more clear.
Guest Windows OS works fine so I asked an unrelated question.

Host Ubuntu OS (not VM) Display resolution is what needs higher
resolution options. Looks like I need to do something like this...

How to Set A Custom Screen Resolution in Ubuntu Desktop
https://ubuntuhandbook.org/index.php/2017/04/custom-screen-resolution-ubuntu-desktop/

Or, this...

Get Higher Screen Resolution in Virtual Box running Ubuntu
https://www.techquark.com/2009/09/get-higher-screen-resolution-in-virtual.html
Post by Paul
That depends on what the emulated hardware claims.
In the VBox settings, if you hold your mouse over the
warning at the bottom of the graphics settings screen in
Settings, it tells you what to do. I think I have
"VBoxVGA" selected for both VMs at present.
Guest Windows OS Display resolution seems fine.
There's no warning indicator for VM Settings for Display.
So, I left it alone. Besides, I don't see "...VGA" options.
Maybe because of different VirtualBox versions ?
Post by Paul
The virtual machine ... recommended one (VBoxSVGA)
The virtual machine ... recommended one (VMSVGA)
The recommendation is different, by family.
I presume the "recommended" choices give higher graphics
settings, just a guess. I don't really know what
properties these things are claiming - the
VBoxVGA vs VBoxSVGA is probably just size. But
why even bother offering three options, if two
options would cover all the cases ?
Paul
Adam
2021-03-30 15:07:54 UTC
Reply
Permalink
Post by Adam
Post by Paul
Post by Adam
Post by Adam
After downloading and installing the corresponding VBox Extension Pack,
I was able to login to VM to see my data, which is still there. :-)
Then, things broke again after installing
virtualbox-guest-additions-iso, which replaced virtualbox-5.0 with
virtualbox-5.1.38...
https://i.postimg.cc/zGkvYSQV/Virtual-Box-Error-VT-x-is-disabled-in-the-BIOS-for-all-CPU-modes-VERR-VMX-MSR-ALL-VMX-DISABLED.png
How to fix ?
Works again. Fixed by enabling both VT-x options in BIOS.
Yes, that's what the message was indicating, is that the BIOS
setting should be enabled.
Post by Adam
OT question about Display resolution. How to get higher resolution ?
https://i.postimg.cc/T2bpknFN/Display-Resolution.png
Sorry for OT (Off Topic) question, I should have been more clear.
Guest Windows OS works fine so I asked an unrelated question.
Host Ubuntu OS (not VM) Display resolution is what needs higher
resolution options. Looks like I need to do something like this...
How to Set A Custom Screen Resolution in Ubuntu Desktop
https://ubuntuhandbook.org/index.php/2017/04/custom-screen-resolution-ubuntu-desktop/
Uh-oh !! There's an error (below). How to fix ?

***@ThinkPad-T430:~$ xrandr
Screen 0: minimum 8 x 8, current 1366 x 768, maximum 32767 x 32767
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x axis
y axis) 310mm x 174mm
1366x768 59.98*+
1360x768 59.80 59.96
1280x720 60.00
1024x768 60.00
1024x576 60.00
960x540 60.00
800x600 60.32 56.25
864x486 60.00
640x480 59.94
720x405 60.00
680x384 60.00
640x360 60.00
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
***@ThinkPad-T430:~$ cvt 1600 900
# 1600x900 59.95 Hz (CVT 1.44M9) hsync: 55.99 kHz; pclk: 118.25 MHz
Modeline "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934
-hsync +vsync
***@ThinkPad-T430:~$ sudo xrandr --newmode "1600x900_60.00" 118.25
1600 1696 1856 2112 900 903 908 934 -hsync +vsync
[sudo] password for xerus:
***@ThinkPad-T430:~$ sudo xrandr --addmode eDP-1 "1600x900_60.00"^C
***@ThinkPad-T430:~$ sudo xrandr --addmode LVDS1 "1600x900_60.00"
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 18 (RRAddOutputMode)
Serial number of failed request: 45
Current serial number in output stream: 46
***@ThinkPad-T430:~$ xrandr
Screen 0: minimum 8 x 8, current 1366 x 768, maximum 32767 x 32767
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x axis
y axis) 310mm x 174mm
1366x768 59.98*+
1360x768 59.80 59.96
1280x720 60.00
1024x768 60.00
1024x576 60.00
960x540 60.00
800x600 60.32 56.25
864x486 60.00
640x480 59.94
720x405 60.00
680x384 60.00
640x360 60.00
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
1600x900_60.00 (0x10f) 118.250MHz -HSync +VSync
h: width 1600 start 1696 end 1856 total 2112 skew 0 clock
55.99KHz
v: height 900 start 903 end 908 total 934 clock
59.95Hz
Post by Adam
Or, this...
Get Higher Screen Resolution in Virtual Box running Ubuntu
https://www.techquark.com/2009/09/get-higher-screen-resolution-in-virtual.html
Post by Paul
That depends on what the emulated hardware claims.
In the VBox settings, if you hold your mouse over the
warning at the bottom of the graphics settings screen in
Settings, it tells you what to do. I think I have
"VBoxVGA" selected for both VMs at present.
Guest Windows OS Display resolution seems fine.
There's no warning indicator for VM Settings for Display.
So, I left it alone. Besides, I don't see "...VGA" options.
Maybe because of different VirtualBox versions ?
Post by Paul
The virtual machine ... recommended one (VBoxSVGA)
The virtual machine ... recommended one (VMSVGA)
The recommendation is different, by family.
I presume the "recommended" choices give higher graphics
settings, just a guess. I don't really know what
properties these things are claiming - the
VBoxVGA vs VBoxSVGA is probably just size. But
why even bother offering three options, if two
options would cover all the cases ?
Paul
Paul
2021-03-31 10:23:04 UTC
Reply
Permalink
Post by Adam
Post by Adam
Post by Paul
Post by Adam
Post by Adam
After downloading and installing the corresponding VBox Extension Pack,
I was able to login to VM to see my data, which is still there. :-)
Then, things broke again after installing
virtualbox-guest-additions-iso, which replaced virtualbox-5.0 with
virtualbox-5.1.38...
https://i.postimg.cc/zGkvYSQV/Virtual-Box-Error-VT-x-is-disabled-in-the-BIOS-for-all-CPU-modes-VERR-VMX-MSR-ALL-VMX-DISABLED.png
How to fix ?
Works again. Fixed by enabling both VT-x options in BIOS.
Yes, that's what the message was indicating, is that the BIOS
setting should be enabled.
Post by Adam
OT question about Display resolution. How to get higher resolution ?
https://i.postimg.cc/T2bpknFN/Display-Resolution.png
Sorry for OT (Off Topic) question, I should have been more clear.
Guest Windows OS works fine so I asked an unrelated question.
Host Ubuntu OS (not VM) Display resolution is what needs higher
resolution options. Looks like I need to do something like this...
How to Set A Custom Screen Resolution in Ubuntu Desktop
https://ubuntuhandbook.org/index.php/2017/04/custom-screen-resolution-ubuntu-desktop/
Uh-oh !! There's an error (below). How to fix ?
Screen 0: minimum 8 x 8, current 1366 x 768, maximum 32767 x 32767
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x axis
y axis) 310mm x 174mm
1366x768 59.98*+
1360x768 59.80 59.96
1280x720 60.00
1024x768 60.00
1024x576 60.00
960x540 60.00
800x600 60.32 56.25
864x486 60.00
640x480 59.94
720x405 60.00
680x384 60.00
640x360 60.00
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
# 1600x900 59.95 Hz (CVT 1.44M9) hsync: 55.99 kHz; pclk: 118.25 MHz
Modeline "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934
-hsync +vsync
1600 1696 1856 2112 900 903 908 934 -hsync +vsync
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 18 (RRAddOutputMode)
Serial number of failed request: 45
Current serial number in output stream: 46
Screen 0: minimum 8 x 8, current 1366 x 768, maximum 32767 x 32767
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x axis
y axis) 310mm x 174mm
1366x768 59.98*+
1360x768 59.80 59.96
1280x720 60.00
1024x768 60.00
1024x576 60.00
960x540 60.00
800x600 60.32 56.25
864x486 60.00
640x480 59.94
720x405 60.00
680x384 60.00
640x360 60.00
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
1600x900_60.00 (0x10f) 118.250MHz -HSync +VSync
h: width 1600 start 1696 end 1856 total 2112 skew 0 clock
55.99KHz
v: height 900 start 903 end 908 total 934 clock
59.95Hz
Post by Adam
Or, this...
Get Higher Screen Resolution in Virtual Box running Ubuntu
https://www.techquark.com/2009/09/get-higher-screen-resolution-in-virtual.html
While it's fun crafting custom "mode lines", that should
not be necessary.

In the old days, "before automation", you could have a CRT with
just five coaxial cables for RGBHV. There was no electrical path,
nor an EEPROM, on the monitor. To operate such a CRT monitor,
you forced them to do stuff, like training a puppy.

Modern monitors have RGBHV (via one means or another), but
they also have SDA (data) and SCK (clock signal). The video card
can read the EEPROM on the monitor, via that bus.

Linux has various EDID utilities, like readedid.

By using the appropriate packages, you might even get the
native ("highest") resolution of the monitor. This is where
one pixel on the desktop, equals one pixel on the monitor,
and gives the sharpest picture.

Some monitors allow going past that. You go to Walmart and
get a TV set with an HDMI. It "accepts" 1920x1080 coming from
a set top DVD player. The scaler inside the TV, scales
that down to 1366x768. It was typical on a TV set, to use
"the next screen down" for ultimate cheapness. The 1366x768
panels were dirt-cheap. The bastards would call the TV "HD",
but the native resolution wasn't 1920, and the image would
look pretty bad if driven at 1920 (for text especially).

Now, I don't know where the geniuses got 1366 from, but that
number is not divisible by eight. Video cards don't like making that
exact resolution. My only point for mentioning that possibility,
is the EDID can sometimes claim the device supports 1920x1080,
when it really does not. Computer monitors (so called),
which are not TV sets, generally do not do that. If the
monitor panel was 1366x768, the EDID would just declare it
that way. It might offer 1366x768 (native) and 1024x768
(scaled badly to display on the panel).

When the system starts, something like /usr/bin/X runs as
the Xserver. It looks for xorg.conf. The xorg.conf used
to hold things like your custom mode line. Today, the xorg.conf
is crafted on-the-fly, using information collected from the
hardware. There are two aspects. Ping the video card, figure
out whether to use nouveau or the NVidia binary blob driver.
The hardware has a max resolution (defined by video card memory
for the frame buffer pixels), as well as clock rate limits
(165MHz DVI, 330MHz HDMI). In some cases, the clock rate is
only 60MHz max (the clock on the LUT or VGA look up table), and
this constrains the video card output.

At the other end of the link (the video cable), is the monitor
with EDID, declaring the available resolutions. A multi-sync
monitor uses a scaler chip inside, to give the appearance of
the same flexibility as a CRT.

So X chugs along for a bit, and "tests" all the valid combinations,
listing them in

/var/log/Xorg.0.log

The log is rolled over, so the old one is backed up, and a
new log is created during startup.

Since we no longer use a static configuration (i.e. be in
total 100% control), then the /var/log/Xorg.0.log is our *evidence*
of what happened during the run.

If there is a total failure (or if you're running Puppy perhaps),
a driver called "Vesa" could be used. It might support 1024x768
but no more. Making a custom modeline, I suppose it would be
respected. There would be a clock rate check, and just like
a real monitor has an OSD to check H and V for rate, the video
driver also checks for clock rate violations.

The Vesa driver would have xrandr show a max of 1024x768.

Eons ago, 1024x768 was considered to be the last, highest,
"constrained" value you could send to a fixed-sync monitor.
Some monitors, there was danger at 1152x8?? or so. You
could actually damage a monitor by using the wrong settings.
Or so the court case claimed :-) For liability reasons,
if a driver "doesn't know what it is doing", it uses
1024x768 as the top resolution. That's what it does,
if any of the sniffing routines doesn't find the Plug and Play
info needed.

You would seek to have the Xorg automation "sniff" the EDID
table and properly use what is provided. The EDID table
contains sufficient info, for the software to craft
custom modelines for every table entry, saving the user
the trouble of making up that menu of items.

Questions:

1) What is your monitor ?
2) What is its claimed native resolution ?
For example, my other machine, the monitor is 1440x900.
3) What does readedid show ?

Some of the info could be shown via

sudo apt install inxi

inxi -G

And that would give a summary of some of your particulars.

The readedid idea, is a way to debug whether the hardware
is working. On Windows, the third-party "moninfo.exe"
reads the EDID of the monitor and displays the particulars.
You'd look in the Linux package manager, for an EDID package
that does similar.

Based on the EDID info extracted, you ask yourself whether
the "menu of options" in the Display setup panel, matches
the EDID. That's a proof of the pudding, that the hardware
is not fabricating or is not artificially constrained
by some crusty component (an SIS video card perhaps).
Nobody seems to have that really crusty stuff any more,
and those people are running Puppy with the right materials
for older hardware (both hardware and software match on epoch).

But when a machine black-screens, and the monitor just
won't display at all, or, the OSD says "Out of Range",
that's when you look for

/var/log/Xorg.0.log

and look for "EE" in there. Even

grep EE /var/log/Xorg.0.log

would give a terse hint as to "what broke". But decoding
what is going on in there isn't particularly easy. I'm not
pointing you at that file because it is "pretty". I'm
pointing you at it as the "only" file you get for debug.

If you crafted a custom xorg.conf, then you'd be in control
for better or worse. It would be one more file, flapping
in the breeze. It's great to make one and be in control.
But then when it breaks, you're responsible for tipping
it upright again. If you want to put a custom modeline
in it, you can.

What are we doing ?

Asking ourselves first, what is the monitor capable of,
and then, why is Xorg.0.log not showing evidence of
having the ability to run at the native setting.

You can also run outside the native resolution. I've
run 4096x4096 on a 1440x900 monitor, and when the mouse
"bumps" against the side of the screen, the 1440x900
"viewport" moves sideways in the 4096x4096 space. It
is possible to pan and scan your way around a very large
surface. You can resize your Firefox window to 4096x4096,
then take a screenshot. The screenshot is then not
limited to 1440x900, but comes out as 4096x4096. Partially,
the limitation to size, is the video card memory, and
some modern video cards are up around 12GB, and the
max surface is constrained by address generators,
rather than anything else. The driver doesn't
particularly like me doing that stuff, and the
behavior is probably not regularly tested that way,
but it's still a way of operating.

When you run a 4096x4096 virtual screen, you use a
special background image, with screen coords printed
on it.

0,0 100,0 200,0 300,0
0,100 100,100 200,100 300,100
0,200 100,200 200,200 300,200

Then, when you're "lost" in the huge space, those numbers
are zoomed enough, you can tell your current position in
the virtual screen. You make your own GIF, using your
own resources, as none is provided for you. If you don't
have that background image, it's a lot harder to
practically use such a stupid setup :-)

Paul
Adam
2021-03-31 20:50:28 UTC
Reply
Permalink
Post by Paul
Post by Adam
Post by Adam
Post by Paul
Post by Adam
Post by Adam
After downloading and installing the corresponding VBox Extension Pack,
I was able to login to VM to see my data, which is still there. :-)
Then, things broke again after installing
virtualbox-guest-additions-iso, which replaced virtualbox-5.0 with
virtualbox-5.1.38...
https://i.postimg.cc/zGkvYSQV/Virtual-Box-Error-VT-x-is-disabled-in-the-BIOS-for-all-CPU-modes-VERR-VMX-MSR-ALL-VMX-DISABLED.png
How to fix ?
Works again. Fixed by enabling both VT-x options in BIOS.
Yes, that's what the message was indicating, is that the BIOS
setting should be enabled.
Post by Adam
OT question about Display resolution. How to get higher resolution ?
https://i.postimg.cc/T2bpknFN/Display-Resolution.png
Sorry for OT (Off Topic) question, I should have been more clear.
Guest Windows OS works fine so I asked an unrelated question.
Host Ubuntu OS (not VM) Display resolution is what needs higher
resolution options. Looks like I need to do something like this...
How to Set A Custom Screen Resolution in Ubuntu Desktop
https://ubuntuhandbook.org/index.php/2017/04/custom-screen-resolution-ubuntu-desktop/
Uh-oh !! There's an error (below). How to fix ?
Screen 0: minimum 8 x 8, current 1366 x 768, maximum 32767 x 32767
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x
axis y axis) 310mm x 174mm
1366x768 59.98*+
1360x768 59.80 59.96
1280x720 60.00
1024x768 60.00
1024x576 60.00
960x540 60.00
800x600 60.32 56.25
864x486 60.00
640x480 59.94
720x405 60.00
680x384 60.00
640x360 60.00
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
# 1600x900 59.95 Hz (CVT 1.44M9) hsync: 55.99 kHz; pclk: 118.25 MHz
Modeline "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908
934 -hsync +vsync
1600 1696 1856 2112 900 903 908 934 -hsync +vsync
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 18 (RRAddOutputMode)
Serial number of failed request: 45
Current serial number in output stream: 46
Screen 0: minimum 8 x 8, current 1366 x 768, maximum 32767 x 32767
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x
axis y axis) 310mm x 174mm
1366x768 59.98*+
1360x768 59.80 59.96
1280x720 60.00
1024x768 60.00
1024x576 60.00
960x540 60.00
800x600 60.32 56.25
864x486 60.00
640x480 59.94
720x405 60.00
680x384 60.00
640x360 60.00
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
1600x900_60.00 (0x10f) 118.250MHz -HSync +VSync
h: width 1600 start 1696 end 1856 total 2112 skew 0 clock
55.99KHz
v: height 900 start 903 end 908 total 934 clock
59.95Hz
Post by Adam
Or, this...
Get Higher Screen Resolution in Virtual Box running Ubuntu
https://www.techquark.com/2009/09/get-higher-screen-resolution-in-virtual.html
While it's fun crafting custom "mode lines", that should
not be necessary.
In the old days, "before automation", you could have a CRT with
just five coaxial cables for RGBHV. There was no electrical path,
nor an EEPROM, on the monitor. To operate such a CRT monitor,
you forced them to do stuff, like training a puppy.
Modern monitors have RGBHV (via one means or another), but
they also have SDA (data) and SCK (clock signal). The video card
can read the EEPROM on the monitor, via that bus.
Linux has various EDID utilities, like readedid.
By using the appropriate packages, you might even get the
native ("highest") resolution of the monitor. This is where
one pixel on the desktop, equals one pixel on the monitor,
and gives the sharpest picture.
My other laptop has higher resolution after having installed the fglrx
proprietary drivers, which were later removed. Was thinking of
installing the proprietary drivers just for the benefits of the
automated configuration files. :-)
Post by Paul
Some monitors allow going past that. You go to Walmart and
get a TV set with an HDMI. It "accepts" 1920x1080 coming from
a set top DVD player. The scaler inside the TV, scales
that down to 1366x768. It was typical on a TV set, to use
"the next screen down" for ultimate cheapness. The 1366x768
panels were dirt-cheap. The bastards would call the TV "HD",
but the native resolution wasn't 1920, and the image would
look pretty bad if driven at 1920 (for text especially).
Now, I don't know where the geniuses got 1366 from, but that
number is not divisible by eight. Video cards don't like making that
exact resolution. My only point for mentioning that possibility,
is the EDID can sometimes claim the device supports 1920x1080,
when it really does not. Computer monitors (so called),
which are not TV sets, generally do not do that. If the
monitor panel was 1366x768, the EDID would just declare it
that way. It might offer 1366x768 (native) and 1024x768
(scaled badly to display on the panel).
When the system starts, something like /usr/bin/X runs as
the Xserver. It looks for xorg.conf. The xorg.conf used
to hold things like your custom mode line. Today, the xorg.conf
is crafted on-the-fly, using information collected from the
hardware. There are two aspects. Ping the video card, figure
out whether to use nouveau or the NVidia binary blob driver.
The hardware has a max resolution (defined by video card memory
for the frame buffer pixels), as well as clock rate limits
(165MHz DVI, 330MHz HDMI). In some cases, the clock rate is
only 60MHz max (the clock on the LUT or VGA look up table), and
this constrains the video card output.
At the other end of the link (the video cable), is the monitor
with EDID, declaring the available resolutions. A multi-sync
monitor uses a scaler chip inside, to give the appearance of
the same flexibility as a CRT.
So X chugs along for a bit, and "tests" all the valid combinations,
listing them in
/var/log/Xorg.0.log
The log is rolled over, so the old one is backed up, and a
new log is created during startup.
Since we no longer use a static configuration (i.e. be in
total 100% control), then the /var/log/Xorg.0.log is our *evidence*
of what happened during the run.
It's a HUGE log file (/var/log/Xorg.0.log).
Post by Paul
If there is a total failure (or if you're running Puppy perhaps),
a driver called "Vesa" could be used. It might support 1024x768
but no more. Making a custom modeline, I suppose it would be
respected. There would be a clock rate check, and just like
a real monitor has an OSD to check H and V for rate, the video
driver also checks for clock rate violations.
The Vesa driver would have xrandr show a max of 1024x768.
Eons ago, 1024x768 was considered to be the last, highest,
"constrained" value you could send to a fixed-sync monitor.
Some monitors, there was danger at 1152x8?? or so. You
could actually damage a monitor by using the wrong settings.
Or so the court case claimed :-) For liability reasons,
if a driver "doesn't know what it is doing", it uses
1024x768 as the top resolution. That's what it does,
if any of the sniffing routines doesn't find the Plug and Play
info needed.
You would seek to have the Xorg automation "sniff" the EDID
table and properly use what is provided. The EDID table
contains sufficient info, for the software to craft
custom modelines for every table entry, saving the user
the trouble of making up that menu of items.
1) What is your monitor ?
https://www.cnet.com/products/lenovo-thinkpad-t430/
Post by Paul
2) What is its claimed native resolution ?
For example, my other machine, the monitor is 1440x900.
https://www.techpowerup.com/cpu-specs/core-i5-3320m.c1067
Post by Paul
3) What does readedid show ?
***@ThinkPad-T430:~$ sudo get-edid | parse-edid
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 3
No EDID on bus 4
No EDID on bus 5
No EDID on bus 6
No EDID on bus 7
No EDID on bus 8
1 potential busses found: 2
128-byte EDID successfully retrieved from i2c bus 2
Looks like i2c was successful. Have a good day.
Checksum Correct

Section "Monitor"
Identifier ""
ModelName ""
VendorName "LGD"
# Monitor Manufactured week 0 of 2012
# EDID version 1.3
# Digital Display
DisplaySize 310 170
Gamma 2.20
Option "DPMS" "true"
Modeline "Mode 0" 69.30 1366 1398 1430 1470 768 771 776 786 -hsync -vsync
EndSection
Post by Paul
Some of the info could be shown via
sudo apt install inxi
inxi -G
And that would give a summary of some of your particulars.
***@ThinkPad-T430:~$ inxi -G
Graphics: Card: Intel 3rd Gen Core processor Graphics Controller
Display Server: X.Org 1.18.3 drivers: intel (unloaded:
fbdev,vesa)
Resolution: ***@59.98hz
GLX Renderer: Mesa DRI Intel Ivybridge Mobile
GLX Version: 3.0 Mesa 11.2.0
***@ThinkPad-T430:~$
***@ThinkPad-T430:~$ xrandr
Screen 0: minimum 8 x 8, current 1366 x 768, maximum 32767 x 32767
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x axis
y axis) 310mm x 174mm
1366x768 59.98*+
1360x768 59.80 59.96
1280x720 60.00
1024x768 60.00
1024x576 60.00
960x540 60.00
800x600 60.32 56.25
864x486 60.00
640x480 59.94
720x405 60.00
680x384 60.00
640x360 60.00
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
Post by Paul
The readedid idea, is a way to debug whether the hardware
is working. On Windows, the third-party "moninfo.exe"
reads the EDID of the monitor and displays the particulars.
You'd look in the Linux package manager, for an EDID package
that does similar.
Based on the EDID info extracted, you ask yourself whether
the "menu of options" in the Display setup panel, matches
the EDID. That's a proof of the pudding, that the hardware
is not fabricating or is not artificially constrained
by some crusty component (an SIS video card perhaps).
Nobody seems to have that really crusty stuff any more,
and those people are running Puppy with the right materials
for older hardware (both hardware and software match on epoch).
But when a machine black-screens, and the monitor just
won't display at all, or, the OSD says "Out of Range",
that's when you look for
/var/log/Xorg.0.log
and look for "EE" in there. Even
grep EE /var/log/Xorg.0.log
***@ThinkPad-T430:~$ grep EE /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
***@ThinkPad-T430:~$ grep WW /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 25.665] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not
exist.
[ 26.329] (WW) Falling back to old probe method for modesetting
[ 26.330] (WW) Falling back to old probe method for fbdev
[ 26.330] (WW) Falling back to old probe method for vesa
Post by Paul
would give a terse hint as to "what broke". But decoding
what is going on in there isn't particularly easy. I'm not
pointing you at that file because it is "pretty". I'm
pointing you at it as the "only" file you get for debug.
If you crafted a custom xorg.conf, then you'd be in control
for better or worse. It would be one more file, flapping
in the breeze. It's great to make one and be in control.
But then when it breaks, you're responsible for tipping
it upright again. If you want to put a custom modeline
in it, you can.
What are we doing ?
Asking ourselves first, what is the monitor capable of,
and then, why is Xorg.0.log not showing evidence of
having the ability to run at the native setting.
You can also run outside the native resolution. I've
run 4096x4096 on a 1440x900 monitor, and when the mouse
"bumps" against the side of the screen, the 1440x900
"viewport" moves sideways in the 4096x4096 space. It
is possible to pan and scan your way around a very large
surface. You can resize your Firefox window to 4096x4096,
then take a screenshot. The screenshot is then not
limited to 1440x900, but comes out as 4096x4096. Partially,
the limitation to size, is the video card memory, and
some modern video cards are up around 12GB, and the
max surface is constrained by address generators,
rather than anything else. The driver doesn't
particularly like me doing that stuff, and the
behavior is probably not regularly tested that way,
but it's still a way of operating.
When you run a 4096x4096 virtual screen, you use a
special background image, with screen coords printed
on it.
0,0 100,0 200,0 300,0
0,100 100,100 200,100 300,100
0,200 100,200 200,200 300,200
Then, when you're "lost" in the huge space, those numbers
are zoomed enough, you can tell your current position in
the virtual screen. You make your own GIF, using your
own resources, as none is provided for you. If you don't
have that background image, it's a lot harder to
practically use such a stupid setup :-)
Paul
Paul
2021-04-01 02:04:57 UTC
Reply
Permalink
Post by Adam
Post by Paul
Post by Adam
Post by Adam
Post by Paul
Post by Adam
Post by Adam
After downloading and installing the corresponding VBox Extension Pack,
I was able to login to VM to see my data, which is still there. :-)
Then, things broke again after installing
virtualbox-guest-additions-iso, which replaced virtualbox-5.0 with
virtualbox-5.1.38...
https://i.postimg.cc/zGkvYSQV/Virtual-Box-Error-VT-x-is-disabled-in-the-BIOS-for-all-CPU-modes-VERR-VMX-MSR-ALL-VMX-DISABLED.png
How to fix ?
Works again. Fixed by enabling both VT-x options in BIOS.
Yes, that's what the message was indicating, is that the BIOS
setting should be enabled.
Post by Adam
OT question about Display resolution. How to get higher resolution ?
https://i.postimg.cc/T2bpknFN/Display-Resolution.png
Sorry for OT (Off Topic) question, I should have been more clear.
Guest Windows OS works fine so I asked an unrelated question.
Host Ubuntu OS (not VM) Display resolution is what needs higher
resolution options. Looks like I need to do something like this...
How to Set A Custom Screen Resolution in Ubuntu Desktop
https://ubuntuhandbook.org/index.php/2017/04/custom-screen-resolution-ubuntu-desktop/
Uh-oh !! There's an error (below). How to fix ?
Screen 0: minimum 8 x 8, current 1366 x 768, maximum 32767 x 32767
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x
axis y axis) 310mm x 174mm
1366x768 59.98*+
1360x768 59.80 59.96
1280x720 60.00
1024x768 60.00
1024x576 60.00
960x540 60.00
800x600 60.32 56.25
864x486 60.00
640x480 59.94
720x405 60.00
680x384 60.00
640x360 60.00
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
# 1600x900 59.95 Hz (CVT 1.44M9) hsync: 55.99 kHz; pclk: 118.25 MHz
Modeline "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908
934 -hsync +vsync
1600 1696 1856 2112 900 903 908 934 -hsync +vsync
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 18 (RRAddOutputMode)
Serial number of failed request: 45
Current serial number in output stream: 46
Screen 0: minimum 8 x 8, current 1366 x 768, maximum 32767 x 32767
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x
axis y axis) 310mm x 174mm
1366x768 59.98*+
1360x768 59.80 59.96
1280x720 60.00
1024x768 60.00
1024x576 60.00
960x540 60.00
800x600 60.32 56.25
864x486 60.00
640x480 59.94
720x405 60.00
680x384 60.00
640x360 60.00
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
1600x900_60.00 (0x10f) 118.250MHz -HSync +VSync
h: width 1600 start 1696 end 1856 total 2112 skew 0 clock
55.99KHz
v: height 900 start 903 end 908 total 934 clock
59.95Hz
Post by Adam
Or, this...
Get Higher Screen Resolution in Virtual Box running Ubuntu
https://www.techquark.com/2009/09/get-higher-screen-resolution-in-virtual.html
While it's fun crafting custom "mode lines", that should
not be necessary.
In the old days, "before automation", you could have a CRT with
just five coaxial cables for RGBHV. There was no electrical path,
nor an EEPROM, on the monitor. To operate such a CRT monitor,
you forced them to do stuff, like training a puppy.
Modern monitors have RGBHV (via one means or another), but
they also have SDA (data) and SCK (clock signal). The video card
can read the EEPROM on the monitor, via that bus.
Linux has various EDID utilities, like readedid.
By using the appropriate packages, you might even get the
native ("highest") resolution of the monitor. This is where
one pixel on the desktop, equals one pixel on the monitor,
and gives the sharpest picture.
My other laptop has higher resolution after having installed the fglrx
proprietary drivers, which were later removed. Was thinking of
installing the proprietary drivers just for the benefits of the
automated configuration files. :-)
Post by Paul
Some monitors allow going past that. You go to Walmart and
get a TV set with an HDMI. It "accepts" 1920x1080 coming from
a set top DVD player. The scaler inside the TV, scales
that down to 1366x768. It was typical on a TV set, to use
"the next screen down" for ultimate cheapness. The 1366x768
panels were dirt-cheap. The bastards would call the TV "HD",
but the native resolution wasn't 1920, and the image would
look pretty bad if driven at 1920 (for text especially).
Now, I don't know where the geniuses got 1366 from, but that
number is not divisible by eight. Video cards don't like making that
exact resolution. My only point for mentioning that possibility,
is the EDID can sometimes claim the device supports 1920x1080,
when it really does not. Computer monitors (so called),
which are not TV sets, generally do not do that. If the
monitor panel was 1366x768, the EDID would just declare it
that way. It might offer 1366x768 (native) and 1024x768
(scaled badly to display on the panel).
When the system starts, something like /usr/bin/X runs as
the Xserver. It looks for xorg.conf. The xorg.conf used
to hold things like your custom mode line. Today, the xorg.conf
is crafted on-the-fly, using information collected from the
hardware. There are two aspects. Ping the video card, figure
out whether to use nouveau or the NVidia binary blob driver.
The hardware has a max resolution (defined by video card memory
for the frame buffer pixels), as well as clock rate limits
(165MHz DVI, 330MHz HDMI). In some cases, the clock rate is
only 60MHz max (the clock on the LUT or VGA look up table), and
this constrains the video card output.
At the other end of the link (the video cable), is the monitor
with EDID, declaring the available resolutions. A multi-sync
monitor uses a scaler chip inside, to give the appearance of
the same flexibility as a CRT.
So X chugs along for a bit, and "tests" all the valid combinations,
listing them in
/var/log/Xorg.0.log
The log is rolled over, so the old one is backed up, and a
new log is created during startup.
Since we no longer use a static configuration (i.e. be in
total 100% control), then the /var/log/Xorg.0.log is our *evidence*
of what happened during the run.
It's a HUGE log file (/var/log/Xorg.0.log).
Post by Paul
If there is a total failure (or if you're running Puppy perhaps),
a driver called "Vesa" could be used. It might support 1024x768
but no more. Making a custom modeline, I suppose it would be
respected. There would be a clock rate check, and just like
a real monitor has an OSD to check H and V for rate, the video
driver also checks for clock rate violations.
The Vesa driver would have xrandr show a max of 1024x768.
Eons ago, 1024x768 was considered to be the last, highest,
"constrained" value you could send to a fixed-sync monitor.
Some monitors, there was danger at 1152x8?? or so. You
could actually damage a monitor by using the wrong settings.
Or so the court case claimed :-) For liability reasons,
if a driver "doesn't know what it is doing", it uses
1024x768 as the top resolution. That's what it does,
if any of the sniffing routines doesn't find the Plug and Play
info needed.
You would seek to have the Xorg automation "sniff" the EDID
table and properly use what is provided. The EDID table
contains sufficient info, for the software to craft
custom modelines for every table entry, saving the user
the trouble of making up that menu of items.
1) What is your monitor ?
https://www.cnet.com/products/lenovo-thinkpad-t430/
Post by Paul
2) What is its claimed native resolution ?
For example, my other machine, the monitor is 1440x900.
https://www.techpowerup.com/cpu-specs/core-i5-3320m.c1067
Post by Paul
3) What does readedid show ?
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 3
No EDID on bus 4
No EDID on bus 5
No EDID on bus 6
No EDID on bus 7
No EDID on bus 8
1 potential busses found: 2
128-byte EDID successfully retrieved from i2c bus 2
Looks like i2c was successful. Have a good day.
Checksum Correct
Section "Monitor"
Identifier ""
ModelName ""
VendorName "LGD"
# Monitor Manufactured week 0 of 2012
# EDID version 1.3
# Digital Display
DisplaySize 310 170
Gamma 2.20
Option "DPMS" "true"
Modeline "Mode 0" 69.30 1366 1398 1430 1470 768 771 776 786
-hsync -vsync
EndSection
Post by Paul
Some of the info could be shown via
sudo apt install inxi
inxi -G
And that would give a summary of some of your particulars.
Graphics: Card: Intel 3rd Gen Core processor Graphics Controller
fbdev,vesa)
GLX Renderer: Mesa DRI Intel Ivybridge Mobile
GLX Version: 3.0 Mesa 11.2.0
Screen 0: minimum 8 x 8, current 1366 x 768, maximum 32767 x 32767
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x axis
y axis) 310mm x 174mm
1366x768 59.98*+
1360x768 59.80 59.96
1280x720 60.00
1024x768 60.00
1024x576 60.00
960x540 60.00
800x600 60.32 56.25
864x486 60.00
640x480 59.94
720x405 60.00
680x384 60.00
640x360 60.00
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
Post by Paul
The readedid idea, is a way to debug whether the hardware
is working. On Windows, the third-party "moninfo.exe"
reads the EDID of the monitor and displays the particulars.
You'd look in the Linux package manager, for an EDID package
that does similar.
Based on the EDID info extracted, you ask yourself whether
the "menu of options" in the Display setup panel, matches
the EDID. That's a proof of the pudding, that the hardware
is not fabricating or is not artificially constrained
by some crusty component (an SIS video card perhaps).
Nobody seems to have that really crusty stuff any more,
and those people are running Puppy with the right materials
for older hardware (both hardware and software match on epoch).
But when a machine black-screens, and the monitor just
won't display at all, or, the OSD says "Out of Range",
that's when you look for
/var/log/Xorg.0.log
and look for "EE" in there. Even
grep EE /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 25.665] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not
exist.
[ 26.329] (WW) Falling back to old probe method for modesetting
[ 26.330] (WW) Falling back to old probe method for fbdev
[ 26.330] (WW) Falling back to old probe method for vesa
Post by Paul
would give a terse hint as to "what broke". But decoding
what is going on in there isn't particularly easy. I'm not
pointing you at that file because it is "pretty". I'm
pointing you at it as the "only" file you get for debug.
If you crafted a custom xorg.conf, then you'd be in control
for better or worse. It would be one more file, flapping
in the breeze. It's great to make one and be in control.
But then when it breaks, you're responsible for tipping
it upright again. If you want to put a custom modeline
in it, you can.
What are we doing ?
Asking ourselves first, what is the monitor capable of,
and then, why is Xorg.0.log not showing evidence of
having the ability to run at the native setting.
You can also run outside the native resolution. I've
run 4096x4096 on a 1440x900 monitor, and when the mouse
"bumps" against the side of the screen, the 1440x900
"viewport" moves sideways in the 4096x4096 space. It
is possible to pan and scan your way around a very large
surface. You can resize your Firefox window to 4096x4096,
then take a screenshot. The screenshot is then not
limited to 1440x900, but comes out as 4096x4096. Partially,
the limitation to size, is the video card memory, and
some modern video cards are up around 12GB, and the
max surface is constrained by address generators,
rather than anything else. The driver doesn't
particularly like me doing that stuff, and the
behavior is probably not regularly tested that way,
but it's still a way of operating.
When you run a 4096x4096 virtual screen, you use a
special background image, with screen coords printed
on it.
0,0 100,0 200,0 300,0
0,100 100,100 200,100 300,100
0,200 100,200 200,200 300,200
Then, when you're "lost" in the huge space, those numbers
are zoomed enough, you can tell your current position in
the virtual screen. You make your own GIF, using your
own resources, as none is provided for you. If you don't
have that background image, it's a lot harder to
practically use such a stupid setup :-)
Paul
http://www.thinkwiki.org/wiki/Replacing_T430_screen_with_a_better_one

"Thinkpad T430 laptops (as well as T430s, T420 and T420s) are
equipped with awful screens. It doesn't matter if the screen is
HD (1366x768) or HD+ (1600x900), whether the screen manufacturer
is LG, Samsung or AUO: every screen has awful viewing angles,
poor colors and weak brightness."

Normally, there would be a procedure, for telling the machine
what size screen is installed. Because the interconnect is LVDS,
there's no plug and play for the screen native resolution.

The two sizes listed, would be if no user intervened in the hardware.
Some people mod the machine and use panels that are not meant
for the machine. But I *still* can't find mention of them using
a procedure so the correct EDID info is stored in the machine.

Paul
Adam
2021-04-01 02:40:46 UTC
Reply
Permalink
Post by Paul
Post by Paul
Post by Adam
Post by Adam
Post by Paul
Post by Adam
Post by Adam
After downloading and installing the corresponding VBox Extension Pack,
I was able to login to VM to see my data, which is still there. :-)
Then, things broke again after installing
virtualbox-guest-additions-iso, which replaced virtualbox-5.0 with
virtualbox-5.1.38...
https://i.postimg.cc/zGkvYSQV/Virtual-Box-Error-VT-x-is-disabled-in-the-BIOS-for-all-CPU-modes-VERR-VMX-MSR-ALL-VMX-DISABLED.png
How to fix ?
Works again. Fixed by enabling both VT-x options in BIOS.
Yes, that's what the message was indicating, is that the BIOS
setting should be enabled.
Post by Adam
OT question about Display resolution. How to get higher resolution ?
https://i.postimg.cc/T2bpknFN/Display-Resolution.png
Sorry for OT (Off Topic) question, I should have been more clear.
Guest Windows OS works fine so I asked an unrelated question.
Host Ubuntu OS (not VM) Display resolution is what needs higher
resolution options. Looks like I need to do something like this...
How to Set A Custom Screen Resolution in Ubuntu Desktop
https://ubuntuhandbook.org/index.php/2017/04/custom-screen-resolution-ubuntu-desktop/
Uh-oh !! There's an error (below). How to fix ?
Screen 0: minimum 8 x 8, current 1366 x 768, maximum 32767 x 32767
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x
axis y axis) 310mm x 174mm
1366x768 59.98*+
1360x768 59.80 59.96
1280x720 60.00
1024x768 60.00
1024x576 60.00
960x540 60.00
800x600 60.32 56.25
864x486 60.00
640x480 59.94
720x405 60.00
680x384 60.00
640x360 60.00
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
# 1600x900 59.95 Hz (CVT 1.44M9) hsync: 55.99 kHz; pclk: 118.25 MHz
Modeline "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908
934 -hsync +vsync
1600 1696 1856 2112 900 903 908 934 -hsync +vsync
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 18 (RRAddOutputMode)
Serial number of failed request: 45
Current serial number in output stream: 46
Screen 0: minimum 8 x 8, current 1366 x 768, maximum 32767 x 32767
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x
axis y axis) 310mm x 174mm
1366x768 59.98*+
1360x768 59.80 59.96
1280x720 60.00
1024x768 60.00
1024x576 60.00
960x540 60.00
800x600 60.32 56.25
864x486 60.00
640x480 59.94
720x405 60.00
680x384 60.00
640x360 60.00
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
1600x900_60.00 (0x10f) 118.250MHz -HSync +VSync
h: width 1600 start 1696 end 1856 total 2112 skew 0 clock
55.99KHz
v: height 900 start 903 end 908 total 934 clock
59.95Hz
Post by Adam
Or, this...
Get Higher Screen Resolution in Virtual Box running Ubuntu
https://www.techquark.com/2009/09/get-higher-screen-resolution-in-virtual.html
While it's fun crafting custom "mode lines", that should
not be necessary.
In the old days, "before automation", you could have a CRT with
just five coaxial cables for RGBHV. There was no electrical path,
nor an EEPROM, on the monitor. To operate such a CRT monitor,
you forced them to do stuff, like training a puppy.
Modern monitors have RGBHV (via one means or another), but
they also have SDA (data) and SCK (clock signal). The video card
can read the EEPROM on the monitor, via that bus.
Linux has various EDID utilities, like readedid.
By using the appropriate packages, you might even get the
native ("highest") resolution of the monitor. This is where
one pixel on the desktop, equals one pixel on the monitor,
and gives the sharpest picture.
My other laptop has higher resolution after having installed the fglrx proprietary drivers, which were later removed. Was thinking of installing the proprietary drivers just for the benefits of the automated configuration files. :-)
Post by Paul
Some monitors allow going past that. You go to Walmart and
get a TV set with an HDMI. It "accepts" 1920x1080 coming from
a set top DVD player. The scaler inside the TV, scales
that down to 1366x768. It was typical on a TV set, to use
"the next screen down" for ultimate cheapness. The 1366x768
panels were dirt-cheap. The bastards would call the TV "HD",
but the native resolution wasn't 1920, and the image would
look pretty bad if driven at 1920 (for text especially).
Now, I don't know where the geniuses got 1366 from, but that
number is not divisible by eight. Video cards don't like making that
exact resolution. My only point for mentioning that possibility,
is the EDID can sometimes claim the device supports 1920x1080,
when it really does not. Computer monitors (so called),
which are not TV sets, generally do not do that. If the
monitor panel was 1366x768, the EDID would just declare it
that way. It might offer 1366x768 (native) and 1024x768
(scaled badly to display on the panel).
When the system starts, something like /usr/bin/X runs as
the Xserver. It looks for xorg.conf. The xorg.conf used
to hold things like your custom mode line. Today, the xorg.conf
is crafted on-the-fly, using information collected from the
hardware. There are two aspects. Ping the video card, figure
out whether to use nouveau or the NVidia binary blob driver.
The hardware has a max resolution (defined by video card memory
for the frame buffer pixels), as well as clock rate limits
(165MHz DVI, 330MHz HDMI). In some cases, the clock rate is
only 60MHz max (the clock on the LUT or VGA look up table), and
this constrains the video card output.
At the other end of the link (the video cable), is the monitor
with EDID, declaring the available resolutions. A multi-sync
monitor uses a scaler chip inside, to give the appearance of
the same flexibility as a CRT.
So X chugs along for a bit, and "tests" all the valid combinations,
listing them in
/var/log/Xorg.0.log
The log is rolled over, so the old one is backed up, and a
new log is created during startup.
Since we no longer use a static configuration (i.e. be in
total 100% control), then the /var/log/Xorg.0.log is our *evidence*
of what happened during the run.
It's a HUGE log file (/var/log/Xorg.0.log).
Post by Paul
If there is a total failure (or if you're running Puppy perhaps),
a driver called "Vesa" could be used. It might support 1024x768
but no more. Making a custom modeline, I suppose it would be
respected. There would be a clock rate check, and just like
a real monitor has an OSD to check H and V for rate, the video
driver also checks for clock rate violations.
The Vesa driver would have xrandr show a max of 1024x768.
Eons ago, 1024x768 was considered to be the last, highest,
"constrained" value you could send to a fixed-sync monitor.
Some monitors, there was danger at 1152x8?? or so. You
could actually damage a monitor by using the wrong settings.
Or so the court case claimed :-) For liability reasons,
if a driver "doesn't know what it is doing", it uses
1024x768 as the top resolution. That's what it does,
if any of the sniffing routines doesn't find the Plug and Play
info needed.
You would seek to have the Xorg automation "sniff" the EDID
table and properly use what is provided. The EDID table
contains sufficient info, for the software to craft
custom modelines for every table entry, saving the user
the trouble of making up that menu of items.
1) What is your monitor ?
https://www.cnet.com/products/lenovo-thinkpad-t430/
Post by Paul
2) What is its claimed native resolution ?
For example, my other machine, the monitor is 1440x900.
https://www.techpowerup.com/cpu-specs/core-i5-3320m.c1067
Post by Paul
3) What does readedid show ?
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 3
No EDID on bus 4
No EDID on bus 5
No EDID on bus 6
No EDID on bus 7
No EDID on bus 8
1 potential busses found: 2
128-byte EDID successfully retrieved from i2c bus 2
Looks like i2c was successful. Have a good day.
Checksum Correct
Section "Monitor"
Identifier ""
ModelName ""
VendorName "LGD"
# Monitor Manufactured week 0 of 2012
# EDID version 1.3
# Digital Display
DisplaySize 310 170
Gamma 2.20
Option "DPMS" "true"
Modeline "Mode 0" 69.30 1366 1398 1430 1470 768 771 776 786 -hsync -vsync
EndSection
Post by Paul
Some of the info could be shown via
sudo apt install inxi
inxi -G
And that would give a summary of some of your particulars.
Graphics: Card: Intel 3rd Gen Core processor Graphics Controller
Display Server: X.Org 1.18.3 drivers: intel (unloaded: fbdev,vesa)
GLX Renderer: Mesa DRI Intel Ivybridge Mobile
GLX Version: 3.0 Mesa 11.2.0
Screen 0: minimum 8 x 8, current 1366 x 768, maximum 32767 x 32767
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 310mm x 174mm
1366x768 59.98*+
1360x768 59.80 59.96
1280x720 60.00
1024x768 60.00
1024x576 60.00
960x540 60.00
800x600 60.32 56.25
864x486 60.00
640x480 59.94
720x405 60.00
680x384 60.00
640x360 60.00
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
Post by Paul
The readedid idea, is a way to debug whether the hardware
is working. On Windows, the third-party "moninfo.exe"
reads the EDID of the monitor and displays the particulars.
You'd look in the Linux package manager, for an EDID package
that does similar.
Based on the EDID info extracted, you ask yourself whether
the "menu of options" in the Display setup panel, matches
the EDID. That's a proof of the pudding, that the hardware
is not fabricating or is not artificially constrained
by some crusty component (an SIS video card perhaps).
Nobody seems to have that really crusty stuff any more,
and those people are running Puppy with the right materials
for older hardware (both hardware and software match on epoch).
But when a machine black-screens, and the monitor just
won't display at all, or, the OSD says "Out of Range",
that's when you look for
/var/log/Xorg.0.log
and look for "EE" in there. Even
grep EE /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 25.665] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 26.329] (WW) Falling back to old probe method for modesetting
[ 26.330] (WW) Falling back to old probe method for fbdev
[ 26.330] (WW) Falling back to old probe method for vesa
Post by Paul
would give a terse hint as to "what broke". But decoding
what is going on in there isn't particularly easy. I'm not
pointing you at that file because it is "pretty". I'm
pointing you at it as the "only" file you get for debug.
If you crafted a custom xorg.conf, then you'd be in control
for better or worse. It would be one more file, flapping
in the breeze. It's great to make one and be in control.
But then when it breaks, you're responsible for tipping
it upright again. If you want to put a custom modeline
in it, you can.
What are we doing ?
Asking ourselves first, what is the monitor capable of,
and then, why is Xorg.0.log not showing evidence of
having the ability to run at the native setting.
You can also run outside the native resolution. I've
run 4096x4096 on a 1440x900 monitor, and when the mouse
"bumps" against the side of the screen, the 1440x900
"viewport" moves sideways in the 4096x4096 space. It
is possible to pan and scan your way around a very large
surface. You can resize your Firefox window to 4096x4096,
then take a screenshot. The screenshot is then not
limited to 1440x900, but comes out as 4096x4096. Partially,
the limitation to size, is the video card memory, and
some modern video cards are up around 12GB, and the
max surface is constrained by address generators,
rather than anything else. The driver doesn't
particularly like me doing that stuff, and the
behavior is probably not regularly tested that way,
but it's still a way of operating.
When you run a 4096x4096 virtual screen, you use a
special background image, with screen coords printed
on it.
0,0 100,0 200,0 300,0
0,100 100,100 200,100 300,100
0,200 100,200 200,200 300,200
Then, when you're "lost" in the huge space, those numbers
are zoomed enough, you can tell your current position in
the virtual screen. You make your own GIF, using your
own resources, as none is provided for you. If you don't
have that background image, it's a lot harder to
practically use such a stupid setup :-)
Paul
http://www.thinkwiki.org/wiki/Replacing_T430_screen_with_a_better_one
"Thinkpad T430 laptops (as well as T430s, T420 and T420s) are
equipped with awful screens. It doesn't matter if the screen is
HD (1366x768) or HD+ (1600x900), whether the screen manufacturer
is LG, Samsung or AUO: every screen has awful viewing angles,
poor colors and weak brightness."
Normally, there would be a procedure, for telling the machine
what size screen is installed. Because the interconnect is LVDS,
there's no plug and play for the screen native resolution.
The two sizes listed, would be if no user intervened in the hardware.
Some people mod the machine and use panels that are not meant
for the machine. But I *still* can't find mention of them using
a procedure so the correct EDID info is stored in the machine.
Paul
Thanks, Guru Paul !!

But, I'm not annoyed enough to replace the screen panel yet.
Too much surgery. If it ain't broke, don't fix it. :-)

So long as I'm getting the highest possible resolution via
configuration, it's fine.
Adam
2021-04-06 19:01:43 UTC
Reply
Permalink
Post by Adam
Post by Adam
Post by Paul
Post by Adam
Post by Adam
FYI, old Ubuntu Win.vdi used virtualbox-4.3 (v4.3.26 r98988).
For new Ubuntu install, which VirtualBox version should I install for
Win.vdi ?
For compatibility, do I need to install virtualbox-4.3 ?
I encountered problems (beyond the typos in the article) using the
following PPA method...
How To Install VirtualBox From PPA In Ubuntu 16.04
https://www.ubuntubuzz.com/2016/04/how-to-install-virtualbox-from-ppa-in.html
I undid whatever was done based on article (above).
And, installed virtualbox-5.0. There's progress.
Now, I have network settings issues on VM startup...
https://i.postimg.cc/qM2tYmYJ/Could-not-start-the-machine-because-physical-network-interfaces-were-not-found-eth0-adapter-1.png
https://i.postimg.cc/XN2SWFZT/VM-Network-Settings-Adapter-1.png
https://i.postimg.cc/VsZTp8pw/VBox-Error-NS-ERROR-FAILURE.png
How to fix ?
Well, this falls under the general topic of the Settings file
for each VM and what it says.
You know that "eth0" is a pre-SystemD way of naming the NIC.
And the convention used in the settings panel in one of
your pictures, shows the SystemD convention for naming the same
NIC.
Somehow, you have to convince VirtualBox, they're the same thing.
You could, for example change the settings using the VBox settings
panel. You can also visit the settings file, spot the "eth0" in
it and change it to the SystemD version.
I just want you to be aware, what VBox is doing sometimes, when
it complains. It's holding your settings file up and treating
it as "golden", then it notes that the situation on the ground,
is not the same as what the file says. VBox is full of consistency
checks. It will find the tinest defect, and ruin your day.
Using the settings panel, the GUI, that's the easy way to do edits.
But there will also be times, where you cannot decipher the error
message, and that's when you'll have the XML in the settings
file open for a look. I sometimes go in there and delete several
lines referring to volumes that no longer exist. As an example
of house-cleaning.
After downloading and installing the corresponding VBox Extension Pack,
I was able to login to VM to see my data, which is still there. :-)
Then, things broke again after installing
virtualbox-guest-additions-iso, which replaced virtualbox-5.0 with
virtualbox-5.1.38...
https://i.postimg.cc/zGkvYSQV/Virtual-Box-Error-VT-x-is-disabled-in-the-BIOS-for-all-CPU-modes-VERR-VMX-MSR-ALL-VMX-DISABLED.png
How to fix ?
Works again. Fixed by enabling both VT-x options in BIOS.
USB problem...

***@ThinkPad-T430:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 19.5G 0 part
├─sda2 8:2 0 1K 0 part
├─sda3 8:3 0 19.5G 0 part /
├─sda4 8:4 0 19.5G 0 part
├─sda5 8:5 0 7.5G 0 part [SWAP]
└─sda6 8:6 0 351.6G 0 part /home
sdb 8:16 1 57.7G 0 disk
├─sdb1 8:17 1 15G 0 part /media/xerus/RALLY2
└─sdb2 8:18 1 15G 0 part /media/xerus/SPBLAZE64GB
sr0 11:0 1 1024M 0 rom
***@ThinkPad-T430:~$ VBoxManage list usbhost
Host USB Devices:

<none>

***@ThinkPad-T430:~$

How to fix ?
Post by Adam
OT question about Display resolution. How to get higher resolution ?
https://i.postimg.cc/T2bpknFN/Display-Resolution.png
Post by Adam
Post by Paul
VBox 6 has become marginally worse, because there's a Media Manager,
and if you want to change a reference to point to a different .vdi
file, you have to remove the original file, remove it from the
Media Manager, add the new file to the Media Manager, then
enter the settings and add the file to the actual virtual machine.
Obviously, a design reviewed by career bureaucrats. I've had other
tools where it was "anything goes", you could delete a container,
throw in another... and the tool wouldn't even notice. Only doing
stuff that caused functional failures, would become wobbly. But
VBox does it's version of "Papers, please" any time you make the
slightest change. And your example, of the foaming at the mouth
because of the NIC name, that's classic behavior. Either fix from
the GUI, or fix with a text editor.
Paul
Paul
2021-04-06 20:06:20 UTC
Reply
Permalink
Post by Adam
Post by Adam
Post by Adam
Post by Paul
Post by Adam
Post by Adam
FYI, old Ubuntu Win.vdi used virtualbox-4.3 (v4.3.26 r98988).
For new Ubuntu install, which VirtualBox version should I install for
Win.vdi ?
For compatibility, do I need to install virtualbox-4.3 ?
I encountered problems (beyond the typos in the article) using the
following PPA method...
How To Install VirtualBox From PPA In Ubuntu 16.04
https://www.ubuntubuzz.com/2016/04/how-to-install-virtualbox-from-ppa-in.html
I undid whatever was done based on article (above).
And, installed virtualbox-5.0. There's progress.
Now, I have network settings issues on VM startup...
https://i.postimg.cc/qM2tYmYJ/Could-not-start-the-machine-because-physical-network-interfaces-were-not-found-eth0-adapter-1.png
https://i.postimg.cc/XN2SWFZT/VM-Network-Settings-Adapter-1.png
https://i.postimg.cc/VsZTp8pw/VBox-Error-NS-ERROR-FAILURE.png
How to fix ?
Well, this falls under the general topic of the Settings file
for each VM and what it says.
You know that "eth0" is a pre-SystemD way of naming the NIC.
And the convention used in the settings panel in one of
your pictures, shows the SystemD convention for naming the same
NIC.
Somehow, you have to convince VirtualBox, they're the same thing.
You could, for example change the settings using the VBox settings
panel. You can also visit the settings file, spot the "eth0" in
it and change it to the SystemD version.
I just want you to be aware, what VBox is doing sometimes, when
it complains. It's holding your settings file up and treating
it as "golden", then it notes that the situation on the ground,
is not the same as what the file says. VBox is full of consistency
checks. It will find the tinest defect, and ruin your day.
Using the settings panel, the GUI, that's the easy way to do edits.
But there will also be times, where you cannot decipher the error
message, and that's when you'll have the XML in the settings
file open for a look. I sometimes go in there and delete several
lines referring to volumes that no longer exist. As an example
of house-cleaning.
After downloading and installing the corresponding VBox Extension Pack,
I was able to login to VM to see my data, which is still there. :-)
Then, things broke again after installing
virtualbox-guest-additions-iso, which replaced virtualbox-5.0 with
virtualbox-5.1.38...
https://i.postimg.cc/zGkvYSQV/Virtual-Box-Error-VT-x-is-disabled-in-the-BIOS-for-all-CPU-modes-VERR-VMX-MSR-ALL-VMX-DISABLED.png
How to fix ?
Works again. Fixed by enabling both VT-x options in BIOS.
USB problem...
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 19.5G 0 part
├─sda2 8:2 0 1K 0 part
├─sda3 8:3 0 19.5G 0 part /
├─sda4 8:4 0 19.5G 0 part
├─sda5 8:5 0 7.5G 0 part [SWAP]
└─sda6 8:6 0 351.6G 0 part /home
sdb 8:16 1 57.7G 0 disk
├─sdb1 8:17 1 15G 0 part /media/xerus/RALLY2
└─sdb2 8:18 1 15G 0 part /media/xerus/SPBLAZE64GB
sr0 11:0 1 1024M 0 rom
<none>
How to fix ?
Post by Adam
OT question about Display resolution. How to get higher resolution ?
https://i.postimg.cc/T2bpknFN/Display-Resolution.png
vboxusers cannot be the last item at the end of groups.

Loading Image...

You add your useraccount to vboxusers group, as part of
having permission to do stuff. But there's a tiny additional
detail.

I got the idea from user "gon1332" post at the bottom here.

https://superuser.com/questions/956622/no-usb-devices-available-in-virtualbox

I added a dummygroup after adding vboxusers to my account.
And then (this time), it started working and USB passthru
was present.

Paul
Adam
2021-04-06 23:56:59 UTC
Reply
Permalink
Post by Paul
Post by Adam
Post by Adam
Post by Adam
Post by Paul
Post by Adam
Post by Adam
FYI, old Ubuntu Win.vdi used virtualbox-4.3 (v4.3.26 r98988).
For new Ubuntu install, which VirtualBox version should I install for
Win.vdi ?
For compatibility, do I need to install virtualbox-4.3 ?
I encountered problems (beyond the typos in the article) using the
following PPA method...
How To Install VirtualBox From PPA In Ubuntu 16.04
https://www.ubuntubuzz.com/2016/04/how-to-install-virtualbox-from-ppa-in.html
I undid whatever was done based on article (above).
And, installed virtualbox-5.0. There's progress.
Now, I have network settings issues on VM startup...
https://i.postimg.cc/qM2tYmYJ/Could-not-start-the-machine-because-physical-network-interfaces-were-not-found-eth0-adapter-1.png
https://i.postimg.cc/XN2SWFZT/VM-Network-Settings-Adapter-1.png
https://i.postimg.cc/VsZTp8pw/VBox-Error-NS-ERROR-FAILURE.png
How to fix ?
Well, this falls under the general topic of the Settings file
for each VM and what it says.
You know that "eth0" is a pre-SystemD way of naming the NIC.
And the convention used in the settings panel in one of
your pictures, shows the SystemD convention for naming the same
NIC.
Somehow, you have to convince VirtualBox, they're the same thing.
You could, for example change the settings using the VBox settings
panel. You can also visit the settings file, spot the "eth0" in
it and change it to the SystemD version.
I just want you to be aware, what VBox is doing sometimes, when
it complains. It's holding your settings file up and treating
it as "golden", then it notes that the situation on the ground,
is not the same as what the file says. VBox is full of consistency
checks. It will find the tinest defect, and ruin your day.
Using the settings panel, the GUI, that's the easy way to do edits.
But there will also be times, where you cannot decipher the error
message, and that's when you'll have the XML in the settings
file open for a look. I sometimes go in there and delete several
lines referring to volumes that no longer exist. As an example
of house-cleaning.
After downloading and installing the corresponding VBox Extension Pack,
I was able to login to VM to see my data, which is still there. :-)
Then, things broke again after installing
virtualbox-guest-additions-iso, which replaced virtualbox-5.0 with
virtualbox-5.1.38...
https://i.postimg.cc/zGkvYSQV/Virtual-Box-Error-VT-x-is-disabled-in-the-BIOS-for-all-CPU-modes-VERR-VMX-MSR-ALL-VMX-DISABLED.png
How to fix ?
Works again. Fixed by enabling both VT-x options in BIOS.
USB problem...
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 19.5G 0 part
├─sda2 8:2 0 1K 0 part
├─sda3 8:3 0 19.5G 0 part /
├─sda4 8:4 0 19.5G 0 part
├─sda5 8:5 0 7.5G 0 part [SWAP]
└─sda6 8:6 0 351.6G 0 part /home
sdb 8:16 1 57.7G 0 disk
├─sdb1 8:17 1 15G 0 part /media/xerus/RALLY2
└─sdb2 8:18 1 15G 0 part /media/xerus/SPBLAZE64GB
sr0 11:0 1 1024M 0 rom
<none>
How to fix ?
Post by Adam
OT question about Display resolution. How to get higher resolution ?
https://i.postimg.cc/T2bpknFN/Display-Resolution.png
vboxusers cannot be the last item at the end of groups.
https://i.postimg.cc/q7N3gn9x/usb-stick-vbox-guest.jpg
In my case, "vboxusers" was not the last item at the end of groups...
==========================================================================
***@ThinkPad-T430:~$ cat /etc/group
root:x:0:
daemon:x:1:
bin:x:2:
sys:x:3:
adm:x:4:syslog,xerus
tty:x:5:
disk:x:6:
lp:x:7:
mail:x:8:
news:x:9:
uucp:x:10:
man:x:12:
proxy:x:13:
kmem:x:15:
dialout:x:20:xerus
fax:x:21:
voice:x:22:
cdrom:x:24:xerus
floppy:x:25:
tape:x:26:
sudo:x:27:xerus
audio:x:29:pulse
dip:x:30:xerus
www-data:x:33:
backup:x:34:
operator:x:37:
list:x:38:
irc:x:39:
src:x:40:
gnats:x:41:
shadow:x:42:
utmp:x:43:
video:x:44:
sasl:x:45:
plugdev:x:46:xerus
staff:x:50:
games:x:60:
users:x:100:
nogroup:x:65534:
systemd-journal:x:101:
systemd-timesync:x:102:
systemd-network:x:103:
systemd-resolve:x:104:
systemd-bus-proxy:x:105:
input:x:106:
crontab:x:107:
syslog:x:108:
netdev:x:109:
messagebus:x:110:
uuidd:x:111:
ssl-cert:x:112:
lpadmin:x:113:xerus
lightdm:x:114:
nopasswdlogin:x:115:
whoopsie:x:116:
mlocate:x:117:
ssh:x:118:
avahi-autoipd:x:119:
avahi:x:120:
bluetooth:x:121:
scanner:x:122:saned
colord:x:123:
pulse:x:124:
pulse-access:x:125:
rtkit:x:126:
saned:x:127:
xerus:x:1000:
sambashare:x:128:xerus
vboxusers:x:129:xerus
Post by Paul
You add your useraccount to vboxusers group, as part of
having permission to do stuff. But there's a tiny additional
detail.
***@ThinkPad-T430:~$ sudo adduser $USER vboxusers
[sudo] password for xerus:
***@ThinkPad-T430:~$

Guest OS USB works after logout/login.

Then, WinXP prompts for drivers for USB controller. USB 3.0 ?

Is it safe to let it search the internet for the drivers ?
Post by Paul
I got the idea from user "gon1332" post at the bottom here.
https://superuser.com/questions/956622/no-usb-devices-available-in-virtualbox
I added a dummygroup after adding vboxusers to my account.
And then (this time), it started working and USB passthru
was present.
Paul
Paul
2021-04-07 01:41:29 UTC
Reply
Permalink
Post by Adam
Guest OS USB works after logout/login.
Then, WinXP prompts for drivers for USB controller. USB 3.0 ?
Is it safe to let it search the internet for the drivers ?
In the Settings panel for the Guest

enable USB Controller
USB1.1 OHCI
USB2.0 EHCI
X USB3.0 xHCI

USB Device Filters
asmedia ASMT1051 [0100]
Sandisk Ultra [0100] this is a 0781:5581 USB stick

The Guest Additions and the PEUL Extension Pack,
they don't do everything. PEUL passes packets through
to the Guest. The Guest Additions provides a virtual
hardware device, "to be discovered".

For example, on Linux, perhaps discovery is "lsusb"
and "modprobe" and so on.

WinXP and Win7 have no native xHCI driver.
WinXP and Win7 have native EHCI driver.

This thread suggests "picking up an Intel driver for the Win Guest".

https://forums.virtualbox.org/viewtopic.php?f=2&t=79915

However, the bumpkins, neither of them mentions the file,
because "that would be telling".

I can use either WinXP or Win7 here, but the chipset emulation
might make a difference. The VM I'm in right now, is using
PIIX3, and such a chip from year 2000, doesn't have USB3 on it.
So it looks like the emulation is "mixed-epoch".

The device is 8086:1E31 . This seems to be what is installed
in my Win7 VM, but it's not really a numeric match and there
also don't seem to be PNP CC codes either in the INF files.

https://downloadmirror.intel.com/22904/eng/Intel_USB3.0-xHCI_v2.5.0.19_whql.zip

They seem to think WinXP is not going to work.

https://forums.virtualbox.org/viewtopic.php?t=68847

Now, I have an actual USB3 card in my physical WinXp setup, a
the NEC USB3 chip is superior to the Intel, in that it was
the first one delivered (the first expander cards used it).
The company name changed to Renesas around the same time.

One of the reasons NEC made the USB3 chip and tried to
be first, was because NEC also made the first USB2 chip
long ago.

The NEC USB3 chip had a WinXP driver, and the USBMON also
works properly in the tray (it will tell you "this device
can work faster in a USB3 port").

If VirtualBox had emulated the NEC chip (72xx series), then
the USB3 drivers would have worked back to WinXP at least.

*******

OK, using Pauls story-telling ability, we end up here.

https://forums.virtualbox.org/viewtopic.php?t=74575

"VBoxManage setextradata <vmname>
VBoxInternal/Devices/usb-xhci/0/Config/ChipType
uPD720201"

That means that VirtualBox can also emulate a NEC USB3,
but there's no GUI for the selector. All that the Settings
Panel has, is a USB1/USB2/USB3 selector, not an Intel/Renesas
selector.

The "uPD" is what NEC chip numbers start with. It *might*
stand for microprocessor division or device, something
like that. NEC also made various networking chips.

Anyway, in the thread there, you're also going to need
to find the NEC driver. And NEC doesn't offer drivers,
only the card makers do. The thread recommends this search,
once the extradata key is added to the VM XML file or so.
VBoxManage knows where to stuff it, because of <vmname>.
So once the extradata key is set, your hardware identifier
is no longer Intel for the USB3 interface. It will change
magically to NEC/Renesas.

https://www.google.com/search?q=renesas+usb+driver+3.0.23.0

Paul
Adam
2021-04-07 03:29:51 UTC
Reply
Permalink
Post by Paul
Post by Adam
Guest OS USB works after logout/login.
Then, WinXP prompts for drivers for USB controller. USB 3.0 ?
Is it safe to let it search the internet for the drivers ?
In the Settings panel for the Guest
enable USB Controller
USB1.1 OHCI
USB2.0 EHCI
X USB3.0 xHCI
USB Device Filters
asmedia ASMT1051 [0100]
Sandisk Ultra [0100] this is a 0781:5581 USB stick
The Guest Additions and the PEUL Extension Pack,
they don't do everything. PEUL passes packets through
to the Guest. The Guest Additions provides a virtual
hardware device, "to be discovered".
For example, on Linux, perhaps discovery is "lsusb"
and "modprobe" and so on.
WinXP and Win7 have no native xHCI driver.
WinXP and Win7 have native EHCI driver.
Thanks, Guru Paul !!

Loading Image...

Okay, I'll just use whatever WinXP has [native USB 2.0 (EHCI)
Controller]. I don't have to use USB 3.0 (xHCI) Controller.

Also, I removed...

- Ricoh Company Ltd. Integrated Camera [1011]
- Auth Biometric Coprocessor [0001]


WinXP is happier. However, WinXP only assigns a drive letter to
partition1 (RALLY2)...

***@ThinkPad-T430:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 19.5G 0 part
├─sda2 8:2 0 1K 0 part
├─sda3 8:3 0 19.5G 0 part /
├─sda4 8:4 0 19.5G 0 part
├─sda5 8:5 0 7.5G 0 part [SWAP]
└─sda6 8:6 0 351.6G 0 part /home
sdb 8:16 1 57.7G 0 disk
├─sdb1 8:17 1 15G 0 part /media/xerus/RALLY2
└─sdb2 8:18 1 15G 0 part /media/xerus/SPBLAZE64GB
sr0 11:0 1 1024M 0 rom
***@ThinkPad-T430:~$

There's no drive letter assigned to partition2 (SPBLAZE64GB).

How to access partition2 (SPBLAZE64GB) ? Or, do I have to merge the two
partitions into one ? RALLY2 partition has that corrupted (?) "Taxes -
Current" directory folder (which I no longer need and just want to get
rid of) that the system says...

Loading Image...


***@ThinkPad-T430:~$ ls /media/xerus/RALLY2/Taxes\ -\ Current/
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/╤├≤╔┴'$'\034''╠'$'\016''.n░)': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes - Current/ƒ▓╚v₧±╡i.ß°█':
Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/ε«≥öao¢▀.'$'\a'';n': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes - Current/⌐¥98╖s÷─.ª╠█':
Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/∞±▄c°Φe'$'\034''.╝9\': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/'$'\004''^Å¥εr▌ÿ.o'$'\001'')': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes - Current/A╩ ▐°≈┼1.¢D╔':
Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/j.⌠ºs╖π'$'\f''.┬fö': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/»¥n'$'\035\027''Åïk.[^j': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/s'$'\036''<o≤jun.π∞┌': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes - Current/æ£gπD*+@.ä$û':
Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/è'$'\027''£'$'\033\027''╕▄'$'\027''.Γ─¼': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/╡'$'\027''┤│▒U÷M.ÿoå': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/1oh'$'\037\r''⌡⌐╖.σ▓▌': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/a■╓ü'$'\177''¼°α.╔Γ-': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/£ª'$'\025''t!æ'$'\033''φ.}√í': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/Lú'$'\r''R0Dé{.╞': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/╣2δ'$'\002''≈'$'\a''3╩.u,─': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes - Current/,╦┬╫÷dn▐.┌t╫':
Input/output error
ls: reading directory '/media/xerus/RALLY2/Taxes - Current/':
Input/output error
¼╒É₧╖σ}?.º╬╚ æ£gπD*+@.ä$û è?£??╕▄?.Γ─¼ mΩ{$oá¡^.å¢? ╡?┤│▒U÷M.ÿoå
)¼x╩t╛?e.äm¢ ]å?╛rbæ?."òG ≤⌡█éσ:ßæ.ôΩ⌡ ╤├≤╔┴?╠?.n░) ¡%,{╢⌐?u.nlp
1oh??⌡⌐╖.σ▓▌ £ª?t!æ?φ.}√í )╧╞?╞ê┤Φ.π1¬ »¥n??Åïk.[^j ƒ▓╚v₧±╡i.ß°█
╣2δ?≈?3╩.u,─ a■╓ü?¼°α.╔Γ- ?╧îbò¬+╩.?gé ?n?zj≤¢┌.▌C╟ XÅ?µ╨±╜║.5₧?
5═Γ;╟0é╬.⌠░▓ ?^Å¥εr▌ÿ.o?) Ib█»Θ╚g╜.6?å öIÅb?)^<.╔t│ xhdæ▄µïτ.55∞
}?ⁿ7~τú.?πc A╩ ▐°≈┼1.¢D╔ ┐╖ï=n┐╨j.c#o {ô }▐╧!╨.|á? Γ╞?2░fE?.gµµ
⌐¥98╖s÷─.ª╠█ ?cα??⌠ûy.3╜5 ╖ì╩╓u?ⁿ╪.??ì ⌐«pü╗▐zƒ.╦7> ε«≥öao¢▀.?;n
*?å╞])?7.T[ù ∞±▄c°Φe?.╝9\ j.⌠ºs╖π?.┬fö q╗═çσ█├_.û╓¼ └Θ⌠≤á?Ç╔.?─?
a°åöy?²".2µ═ ,╦┬╫÷dn▐.┌t╫ ?╕÷Kb~-S.═?? s?<o≤jun.π∞┌
¥╗∙.àcé ╗e??ú?am.∞ⁿì Lú?R0Dé{.╞ ▐£Uak¬]?.ⁿu_
***@ThinkPad-T430:~$

How to fix/get rid of corrupted (?) "Taxes - Current" directory folder ?


Okay, later, if I really-really need USB 3.0 (xHCI) Controller drivers,
I will backup/clone the drive first before trying the following...
Post by Paul
This thread suggests "picking up an Intel driver for the Win Guest".
https://forums.virtualbox.org/viewtopic.php?f=2&t=79915
However, the bumpkins, neither of them mentions the file,
because "that would be telling".
I can use either WinXP or Win7 here, but the chipset emulation
might make a difference. The VM I'm in right now, is using
PIIX3, and such a chip from year 2000, doesn't have USB3 on it.
So it looks like the emulation is "mixed-epoch".
The device is 8086:1E31 . This seems to be what is installed
in my Win7 VM, but it's not really a numeric match and there
also don't seem to be PNP CC codes either in the INF files.
https://downloadmirror.intel.com/22904/eng/Intel_USB3.0-xHCI_v2.5.0.19_whql.zip
They seem to think WinXP is not going to work.
https://forums.virtualbox.org/viewtopic.php?t=68847
Now, I have an actual USB3 card in my physical WinXp setup, a
the NEC USB3 chip is superior to the Intel, in that it was
the first one delivered (the first expander cards used it).
The company name changed to Renesas around the same time.
One of the reasons NEC made the USB3 chip and tried to
be first, was because NEC also made the first USB2 chip
long ago.
The NEC USB3 chip had a WinXP driver, and the USBMON also
works properly in the tray (it will tell you "this device
can work faster in a USB3 port").
If VirtualBox had emulated the NEC chip (72xx series), then
the USB3 drivers would have worked back to WinXP at least.
*******
OK, using Pauls story-telling ability, we end up here.
https://forums.virtualbox.org/viewtopic.php?t=74575
"VBoxManage setextradata <vmname>
VBoxInternal/Devices/usb-xhci/0/Config/ChipType
uPD720201"
That means that VirtualBox can also emulate a NEC USB3,
but there's no GUI for the selector. All that the Settings
Panel has, is a USB1/USB2/USB3 selector, not an Intel/Renesas
selector.
The "uPD" is what NEC chip numbers start with. It *might*
stand for microprocessor division or device, something
like that. NEC also made various networking chips.
Anyway, in the thread there, you're also going to need
to find the NEC driver. And NEC doesn't offer drivers,
only the card makers do. The thread recommends this search,
once the extradata key is added to the VM XML file or so.
VBoxManage knows where to stuff it, because of <vmname>.
So once the extradata key is set, your hardware identifier
is no longer Intel for the USB3 interface. It will change
magically to NEC/Renesas.
https://www.google.com/search?q=renesas+usb+driver+3.0.23.0
Paul
Adam
2021-04-07 04:49:13 UTC
Reply
Permalink
Post by Adam
Post by Paul
Post by Adam
Guest OS USB works after logout/login.
Then, WinXP prompts for drivers for USB controller. USB 3.0 ?
Is it safe to let it search the internet for the drivers ?
In the Settings panel for the Guest
enable USB Controller
USB1.1 OHCI
USB2.0 EHCI
X USB3.0 xHCI
USB Device Filters
asmedia ASMT1051 [0100]
Sandisk Ultra [0100] this is a 0781:5581 USB stick
The Guest Additions and the PEUL Extension Pack,
they don't do everything. PEUL passes packets through
to the Guest. The Guest Additions provides a virtual
hardware device, "to be discovered".
For example, on Linux, perhaps discovery is "lsusb"
and "modprobe" and so on.
WinXP and Win7 have no native xHCI driver.
WinXP and Win7 have native EHCI driver.
Thanks, Guru Paul !!
https://i.postimg.cc/RhWH08hD/Win-XP-VM-Settings.png
Okay, I'll just use whatever WinXP has [native USB 2.0 (EHCI)
Controller]. I don't have to use USB 3.0 (xHCI) Controller.
Also, I removed...
- Ricoh Company Ltd. Integrated Camera [1011]
- Auth Biometric Coprocessor [0001]
WinXP is happier. However, WinXP only assigns a drive letter to
partition1 (RALLY2)...
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 19.5G 0 part
├─sda2 8:2 0 1K 0 part
├─sda3 8:3 0 19.5G 0 part /
├─sda4 8:4 0 19.5G 0 part
├─sda5 8:5 0 7.5G 0 part [SWAP]
└─sda6 8:6 0 351.6G 0 part /home
sdb 8:16 1 57.7G 0 disk
├─sdb1 8:17 1 15G 0 part /media/xerus/RALLY2
└─sdb2 8:18 1 15G 0 part /media/xerus/SPBLAZE64GB
sr0 11:0 1 1024M 0 rom
There's no drive letter assigned to partition2 (SPBLAZE64GB).
How to access partition2 (SPBLAZE64GB) ? Or, do I have to merge the two
partitions into one ? RALLY2 partition has that corrupted (?) "Taxes -
Current" directory folder (which I no longer need and just want to get
rid of) that the system says...
https://i.postimg.cc/W4Qy1R5d/This-location-could-not-be-displayed.png
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/╤├≤╔┴'$'\034''╠'$'\016''.n░)': Input/output error
Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/ε«≥öao¢▀.'$'\a'';n': Input/output error
Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/∞±▄c°Φe'$'\034''.╝9\': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/'$'\004''^Å¥εr▌ÿ.o'$'\001'')': Input/output error
Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/j.⌠ºs╖π'$'\f''.┬fö': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/»¥n'$'\035\027''Åïk.[^j': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/s'$'\036''<o≤jun.π∞┌': Input/output error
Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/è'$'\027''£'$'\033\027''╕▄'$'\027''.Γ─¼': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/╡'$'\027''┤│▒U÷M.ÿoå': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/1oh'$'\037\r''⌡⌐╖.σ▓▌': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/a■╓ü'$'\177''¼°α.╔Γ-': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/£ª'$'\025''t!æ'$'\033''φ.}√í': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/Lú'$'\r''R0Dé{.╞': Input/output error
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/╣2δ'$'\002''≈'$'\a''3╩.u,─': Input/output error
Input/output error
Input/output error
)¼x╩t╛?e.äm¢ ]å?╛rbæ?."òG ≤⌡█éσ:ßæ.ôΩ⌡ ╤├≤╔┴?╠?.n░) ¡%,{╢⌐?u.nlp
1oh??⌡⌐╖.σ▓▌ £ª?t!æ?φ.}√í )╧╞?╞ê┤Φ.π1¬ »¥n??Åïk.[^j ƒ▓╚v₧±╡i.ß°█
╣2δ?≈?3╩.u,─ a■╓ü?¼°α.╔Γ- ?╧îbò¬+╩.?gé ?n?zj≤¢┌.▌C╟ XÅ?µ╨±╜║.5₧?
5═Γ;╟0é╬.⌠░▓ ?^Å¥εr▌ÿ.o?) Ib█»Θ╚g╜.6?å öIÅb?)^<.╔t│ xhdæ▄µïτ.55∞
}?ⁿ7~τú.?πc A╩ ▐°≈┼1.¢D╔ ┐╖ï=n┐╨j.c#o {ô }▐╧!╨.|á? Γ╞?2░fE?.gµµ
⌐¥98╖s÷─.ª╠█ ?cα??⌠ûy.3╜5 ╖ì╩╓u?ⁿ╪.??ì ⌐«pü╗▐zƒ.╦7> ε«≥öao¢▀.?;n
*?å╞])?7.T[ù ∞±▄c°Φe?.╝9\ j.⌠ºs╖π?.┬fö q╗═çσ█├_.û╓¼ └Θ⌠≤á?Ç╔.?─?
a°åöy?²".2µ═ ,╦┬╫÷dn▐.┌t╫ ?╕÷Kb~-S.═?? s?<o≤jun.π∞┌
¥╗∙.àcé ╗e??ú?am.∞ⁿì Lú?R0Dé{.╞ ▐£Uak¬]?.ⁿu_
How to fix/get rid of corrupted (?) "Taxes - Current" directory folder ?
https://www.wikihow.com/Run-a-Chkdsk-Function-on-Windows-XP

"Another way to run Chkdsk is to click the Start menu, select My
Computer, right-click the drive to check, and go to Properties > Tools >
Check Now..."

Checking RALLY2 now...
Post by Adam
Okay, later, if I really-really need USB 3.0 (xHCI) Controller drivers,
I will backup/clone the drive first before trying the following...
Post by Paul
This thread suggests "picking up an Intel driver for the Win Guest".
https://forums.virtualbox.org/viewtopic.php?f=2&t=79915
However, the bumpkins, neither of them mentions the file,
because "that would be telling".
I can use either WinXP or Win7 here, but the chipset emulation
might make a difference. The VM I'm in right now, is using
PIIX3, and such a chip from year 2000, doesn't have USB3 on it.
So it looks like the emulation is "mixed-epoch".
The device is 8086:1E31 . This seems to be what is installed
in my Win7 VM, but it's not really a numeric match and there
also don't seem to be PNP CC codes either in the INF files.
https://downloadmirror.intel.com/22904/eng/Intel_USB3.0-xHCI_v2.5.0.19_whql.zip
They seem to think WinXP is not going to work.
https://forums.virtualbox.org/viewtopic.php?t=68847
Now, I have an actual USB3 card in my physical WinXp setup, a
the NEC USB3 chip is superior to the Intel, in that it was
the first one delivered (the first expander cards used it).
The company name changed to Renesas around the same time.
One of the reasons NEC made the USB3 chip and tried to
be first, was because NEC also made the first USB2 chip
long ago.
The NEC USB3 chip had a WinXP driver, and the USBMON also
works properly in the tray (it will tell you "this device
can work faster in a USB3 port").
If VirtualBox had emulated the NEC chip (72xx series), then
the USB3 drivers would have worked back to WinXP at least.
*******
OK, using Pauls story-telling ability, we end up here.
https://forums.virtualbox.org/viewtopic.php?t=74575
"VBoxManage setextradata <vmname>
VBoxInternal/Devices/usb-xhci/0/Config/ChipType
uPD720201"
That means that VirtualBox can also emulate a NEC USB3,
but there's no GUI for the selector. All that the Settings
Panel has, is a USB1/USB2/USB3 selector, not an Intel/Renesas
selector.
The "uPD" is what NEC chip numbers start with. It *might*
stand for microprocessor division or device, something
like that. NEC also made various networking chips.
Anyway, in the thread there, you're also going to need
to find the NEC driver. And NEC doesn't offer drivers,
only the card makers do. The thread recommends this search,
once the extradata key is added to the VM XML file or so.
VBoxManage knows where to stuff it, because of <vmname>.
So once the extradata key is set, your hardware identifier
is no longer Intel for the USB3 interface. It will change
magically to NEC/Renesas.
https://www.google.com/search?q=renesas+usb+driver+3.0.23.0
Paul
Paul
2021-04-07 09:19:30 UTC
Reply
Permalink
Post by Adam
WinXP is happier. However, WinXP only assigns a drive letter to
partition1 (RALLY2)...
Windows only mounts the first of N partitions, on USB sticks.
This depends on how the device declares itself (as removable
media or as a fixed disk, via the RMB bit).

In years past, the sticks only came one way, and just the
first partition (like FAT32 or NTFS) would mount.

That would explain why SPBLAZE64GB can't be seen in WinXP.

Note that, Microsoft has *finally* fixed this or claims to
have. It's either 20H2 or the Insider Edition, that would
mount all four on a legacy MSDOS partitioned USB stick.

I haven't tested this, because I'll believe it when I
see it :-) It's just not work spending even five minutes
on it, to see which version has the feature.
Post by Adam
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 19.5G 0 part
├─sda2 8:2 0 1K 0 part
├─sda3 8:3 0 19.5G 0 part /
├─sda4 8:4 0 19.5G 0 part
├─sda5 8:5 0 7.5G 0 part [SWAP]
└─sda6 8:6 0 351.6G 0 part /home
sdb 8:16 1 57.7G 0 disk
├─sdb1 8:17 1 15G 0 part /media/xerus/RALLY2
└─sdb2 8:18 1 15G 0 part /media/xerus/SPBLAZE64GB
sr0 11:0 1 1024M 0 rom
There's no drive letter assigned to partition2 (SPBLAZE64GB).
How to access partition2 (SPBLAZE64GB) ? Or, do I have to merge the two
partitions into one ? RALLY2 partition has that corrupted (?) "Taxes -
Current" directory folder (which I no longer need and just want to get
rid of) that the system says...
https://i.postimg.cc/W4Qy1R5d/This-location-could-not-be-displayed.png
ls: cannot access '/media/xerus/RALLY2/Taxes -
Current/╤├≤╔┴'$'\034''╠'$'\016''.n░)': Input/output error
As for this one, this has the smell of "Windows 10 touched this stick".

That's my first suspicion. Note that the "Input/output error" message,
as been changed in current distros, to a message stating the driver
cannot display the contents. Which is closer to what happens with
things like Reparse Points in NTFS.

But your displayed corruption, I don't know what to make
of that. While it could be the virtual to physical translation
of addresses outside the USB stick, to flash blocks inside, is
loading the wrong block, is that really what happened ? Dunno.
Like structure damage caused by a flash block issue in the stick.

Make a backup with "dd" so you have an image of the stick first.
Don't run CHKDSK on it, until you have a good backup copy.

I would use the CHKDSK on Windows 7 for this. While the CHKDSK
on Windows 10 works, the logic in it is entirely too "loose"
for my liking. It does not repair things like it should. Whereas
Win7 is stricter about what it finds.

If CHKDSK is happy with it, then rm in Linux or del in Windows
should work.

Paul
Adam
2021-04-07 12:01:55 UTC
Reply
Permalink
Post by Paul
WinXP is happier. However, WinXP only assigns a drive letter to partition1 (RALLY2)...
Windows only mounts the first of N partitions, on USB sticks.
This depends on how the device declares itself (as removable
media or as a fixed disk, via the RMB bit).
In years past, the sticks only came one way, and just the
first partition (like FAT32 or NTFS) would mount.
That would explain why SPBLAZE64GB can't be seen in WinXP.
Okay, now that chkdsk has been run on RALLY2 to fix the corrupted (?) "Taxes - Current" directory folder, I'll just merge the partitions and stick with one partition per USB stick. Having multiple nautilus windows pop open after Windows releases the USB partitions is meh anyways.
Post by Paul
Note that, Microsoft has *finally* fixed this or claims to
have. It's either 20H2 or the Insider Edition, that would
mount all four on a legacy MSDOS partitioned USB stick.
I haven't tested this, because I'll believe it when I
see it :-) It's just not worth spending even five minutes
on it, to see which version has the feature.
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 19.5G 0 part
├─sda2 8:2 0 1K 0 part
├─sda3 8:3 0 19.5G 0 part /
├─sda4 8:4 0 19.5G 0 part
├─sda5 8:5 0 7.5G 0 part [SWAP]
└─sda6 8:6 0 351.6G 0 part /home
sdb 8:16 1 57.7G 0 disk
├─sdb1 8:17 1 15G 0 part /media/xerus/RALLY2
└─sdb2 8:18 1 15G 0 part /media/xerus/SPBLAZE64GB
sr0 11:0 1 1024M 0 rom
There's no drive letter assigned to partition2 (SPBLAZE64GB).
How to access partition2 (SPBLAZE64GB) ? Or, do I have to merge the two partitions into one ? RALLY2 partition has that corrupted (?) "Taxes - Current" directory folder (which I no longer need and just want to get rid of) that the system says...
https://i.postimg.cc/W4Qy1R5d/This-location-could-not-be-displayed.png
ls: cannot access '/media/xerus/RALLY2/Taxes - Current/╤├≤╔┴'$'\034''╠'$'\016''.n░)': Input/output error
As for this one, this has the smell of "Windows 10 touched this stick".
The "Taxes - Current" directory folder is the data I first copied out of Windows guest OS to Ubuntu host OS via a drive created with VirtualBox guest additions (?) long ago. Was trying to get the data out in case the system bellies up. Then, I made another copy from Ubuntu host OS to RALLY2.

Windows 10 did not touch the USB stick.
Post by Paul
That's my first suspicion. Note that the "Input/output error" message,
as been changed in current distros, to a message stating the driver
cannot display the contents. Which is closer to what happens with
things like Reparse Points in NTFS.
But your displayed corruption, I don't know what to make
of that. While it could be the virtual to physical translation
of addresses outside the USB stick, to flash blocks inside, is
loading the wrong block, is that really what happened ? Dunno.
Like structure damage caused by a flash block issue in the stick.
Make a backup with "dd" so you have an image of the stick first.
Don't run CHKDSK on it, until you have a good backup copy.
This new 64 GB USB stick IS the backup/clone. The 32 GB OCZ RALLY2 USB stick has been retired.
Less confusing working with different size USB sticks. :-)

Already ran chkdsk on RALLY2 partition, which fixed the corruption leaving a file named "Taxes - Current" and a directory folder named "FOUND.000".
Post by Paul
I would use the CHKDSK on Windows 7 for this. While the CHKDSK
on Windows 10 works, the logic in it is entirely too "loose"
for my liking. It does not repair things like it should. Whereas
Win7 is stricter about what it finds.
If CHKDSK is happy with it, then rm in Linux or del in Windows
should work.
Paul
Yes, at least the file/directory is accessible now after chkdsk.

I may install a Win7 guest OS later. I think I have the Win7 ISO around somewhere.


[OT] Are there good automotive motor repair newsgroups (where ABS Booster Pump Motor repair can be discussed) ?

ABS Booster Pump - Repair or Replace? Part Sources? Rebuild in DFW, TX (6 Viewers)
https://forum.ih8mud.com/threads/abs-booster-pump-repair-or-replace-part-sources-rebuild-in-dfw-tx.992375/

Looks like my ABS Booster Motor Pump needs new components (commutator, brushes and bearings).
Paul
2021-04-07 15:05:13 UTC
Reply
Permalink
Post by Adam
[OT] Are there good automotive motor repair newsgroups (where ABS
Booster Pump Motor repair can be discussed) ?
ABS Booster Pump - Repair or Replace? Part Sources? Rebuild in DFW, TX (6 Viewers)
https://forum.ih8mud.com/threads/abs-booster-pump-repair-or-replace-part-sources-rebuild-in-dfw-tx.992375/
Looks like my ABS Booster Motor Pump needs new components (commutator,
brushes and bearings).
Look in newsgroups under the brand of your car.

alt.autos.toyota.*

A small electric motor shop could look at it. They do
things like rewind burned coils. Ours had a coil winding
machine (which likely only services a few types of motors).
I used to go to the small motor shop, to buy enamel wire
from them.

For things like destroyed brush assemblies, they won't
have parts and won't be able to get parts. Part of
our throw-away society. Real motors have decent brush
assemblies and can be repaired. Real motors have thick
commutator plates, and can be turned down on a lathe.
But that's a motor about as big as your arm, in diameter.

There were some items, I would not repair on principle.
Black and Decker weed cutters, the line powered ones,
the brush assemblies were too easily damaged. And I
must have been given about five of those to fix, and
you look inside and "nope, too much plastic". Sometimes
the plastic was melted or deformed.

Brush assemblies today, are a lot better than they used to be.
I put a new brush in my Black and Decker electric lawn
mower, no problem at all. It was structurally sound enough,
I could probably replace it twice-more if needed. But their
early weed cutters were a disaster.

As for cars, I'm not in favor of rebuilds, because in
my opinion, with the multiple alternators that have
blown here, there just is not enough care during
the rebuild. It's like the bearings aren't getting
replaced.

Paul
Adam
2021-04-07 17:43:09 UTC
Reply
Permalink
Post by Paul
Post by Adam
[OT] Are there good automotive motor repair newsgroups (where ABS Booster Pump Motor repair can be discussed) ?
ABS Booster Pump - Repair or Replace? Part Sources? Rebuild in DFW, TX (6 Viewers)
https://forum.ih8mud.com/threads/abs-booster-pump-repair-or-replace-part-sources-rebuild-in-dfw-tx.992375/
Looks like my ABS Booster Motor Pump needs new components (commutator, brushes and bearings).
Look in newsgroups under the brand of your car.
alt.autos.toyota.*
A small electric motor shop could look at it. They do
things like rewind burned coils. Ours had a coil winding
machine (which likely only services a few types of motors).
I used to go to the small motor shop, to buy enamel wire
from them.
The shops that work on generators, starters and alternators ?
Post by Paul
For things like destroyed brush assemblies, they won't
have parts and won't be able to get parts. Part of
our throw-away society. Real motors have decent brush
assemblies and can be repaired. Real motors have thick
commutator plates, and can be turned down on a lathe.
But that's a motor about as big as your arm, in diameter.
The following YouTube video shows the HBB pump motor and accumulator...

HBB (Hydraulic Brake Booster) new motor install 4runner gx470 lx470 abs unit screeching screaming noise


1998-2005 Lexus GS300 GS400 OEM Anti-Lock Brake Pump Accumulator Motor (47960-30030)
Loading Image...

For this particular motor, most repairs have been on the brush assembly (not the coils).
Poor design or just old (1999) ? IDK

There are many photos in the following thread...

ABS Booster Pump - Repair or Replace? Part Sources? Rebuild in DFW, TX (6 Viewers)
https://forum.ih8mud.com/threads/abs-booster-pump-repair-or-replace-part-sources-rebuild-in-dfw-tx.992375/
Post by Paul
There were some items, I would not repair on principle.
Black and Decker weed cutters, the line powered ones,
the brush assemblies were too easily damaged. And I
must have been given about five of those to fix, and
you look inside and "nope, too much plastic". Sometimes
the plastic was melted or deformed.
Weed cutters are cheap enough where buying a whole new one is less painful.
Not the case with car motors. :-)
Post by Paul
Brush assemblies today, are a lot better than they used to be.
I put a new brush in my Black and Decker electric lawn
mower, no problem at all. It was structurally sound enough,
I could probably replace it twice-more if needed. But their
early weed cutters were a disaster.
As for cars, I'm not in favor of rebuilds, because in
my opinion, with the multiple alternators that have
blown here, there just is not enough care during
the rebuild. It's like the bearings aren't getting
replaced.
Paul
For alternators, seems like rebuilt is all that's available.
At least, for my old Lexus GS400.


Any idea why Thunderbird keeps getting this warning...

Loading Image...

Seems like the same line/location every time. Then, the window goes gray and the system gets sluggish for a minute or so.
Paul
2021-04-07 20:02:59 UTC
Reply
Permalink
Post by Adam
Post by Paul
Post by Adam
[OT] Are there good automotive motor repair newsgroups (where ABS
Booster Pump Motor repair can be discussed) ?
ABS Booster Pump - Repair or Replace? Part Sources? Rebuild in DFW, TX (6 Viewers)
https://forum.ih8mud.com/threads/abs-booster-pump-repair-or-replace-part-sources-rebuild-in-dfw-tx.992375/
Looks like my ABS Booster Motor Pump needs new components
(commutator, brushes and bearings).
Look in newsgroups under the brand of your car.
alt.autos.toyota.*
A small electric motor shop could look at it. They do
things like rewind burned coils. Ours had a coil winding
machine (which likely only services a few types of motors).
I used to go to the small motor shop, to buy enamel wire
from them.
The shops that work on generators, starters and alternators ?
The kind of shop I am referring to, is not automotive. They
would work on any motor, but from the electrical side of things.
They do brushes, commutators, fix bad windings. They're not
a rebuilder, because they wouldn't have the parts for just
anything. Like, if you needed a new shaft, they may not
stock blanks for just anything. There are various patterns
on the end, for the mechanical mating. There are standards
for some of it, making it easier to stock stuff. The distinction
is, they work on a lot of fractional horsepower motors. If you
had a 10,000 HP motor in your manufacturing plant, you'd
be calling somebody else. Big jobs need big tools. The coil
winder would be different, the wire as big as your finger.
Post by Adam
The following YouTube video shows the HBB pump motor and accumulator...
HBB (Hydraulic Brake Booster) new motor install 4runner gx470 lx470 abs
unit screeching screaming noise
http://youtu.be/E5NoyVjZAWo
That's a reasonably small motor, but it runs from +12V
so the current flow is likely to be relatively high
for the motive power it generates.
Post by Adam
1998-2005 Lexus GS300 GS400 OEM Anti-Lock Brake Pump Accumulator Motor (47960-30030)
https://i.postimg.cc/GtPvwM7r/47960-30030-ABS-Pump-for-1999-Lexus-GS400-s-l1600.jpg
For this particular motor, most repairs have been on the brush assembly (not the coils).
Poor design or just old (1999) ? IDK
There are many photos in the following thread...
ABS Booster Pump - Repair or Replace? Part Sources? Rebuild in DFW, TX (6 Viewers)
https://forum.ih8mud.com/threads/abs-booster-pump-repair-or-replace-part-sources-rebuild-in-dfw-tx.992375/
It could be a cascade failure. Bearing seizes first. Motor
current climbs, as motor struggles to keep turning. Burns
brushes. Or, pops fuse. Now, for safety, can a thing
like that even be fused ? Maybe at a very high value of
current flow. I'm surprised at reports of "pedal to floor",
which would be a safety issue. A modulator when failed,
should leave the brake action operational - failure should
not cause a complete loss of pressure.
Post by Adam
Weed cutters are cheap enough where buying a whole new one is less painful.
Not the case with car motors. :-)
You repair them, because they can be easy to fix. My lawn
mower only took me about ten minutes, taking my time, and
one reason is I asked for a crimp while I was there to
get the new brush. The crimp, pinches the brush wire to
the wire in the housing. So some brands, it wouldn't
be a problem to make them last 30 years. It's irritating
to see such poor designs, the plastic has melted. When it
doesn't have to be that way. It doesn't cost any more on
a BOM, to make a unit that doesn't fail that way. But
on stuff like that, the bearings aren't bad. Automotive,
everything is fucked bearings.
Post by Adam
For alternators, seems like rebuilt is all that's available.
At least, for my old Lexus GS400.
The discussion thread has a picture of the motor opened
up, so you can see the rotor and the windings. But the
commutator must be out of view, underneath. Brush assemblies
are usually spring loaded, and you can't use up the entire
carbon brush or it could flop around in the holder. If
they're worn, there's a sorta safe amount of wear, and
more than that, it won't stay in the holder properly.

They also wear in, and follow the curve of the commutator
when installed. The contact area will be a bit smaller than
normal at first, but they wear to shape and then the
friction will be less.

If you see dirt in the commutator, between plates (the ones
with wires joined to the plates and leading off to the coils),
don't panic. If you attempt to clean out the gap there,
you could be setting yourself up for a fail. Resist the
urge to do that. The problem is, hobbyists don't
have any tools for cleaning, and any cleaning action
there leaves burrs on the brass (edge). The burrs will cause
abnormal friction and cutting action on the brush face, which
you don't want. Too much dirt in the gap, causes conductive
failure, but too much "attention to detail" is also bad.
These are the things that would normally be turned in
a lathe, and returned to proper shape. But on small motors,
the commutator segments are too thin to be turned.

You can only tell whether it can be saved, once it is
taken apart. Look for reports from others on that.
Whether every one of them is destroyed. The thing is,
you'd need to find the end bearing, to attempt a
rebuild yourself. The screeching could be the bearing.
And you hope that sound isn't coming from the brushes
(the metal on the brush holder could scrape against
the commutator). If the brush ejects and is floating
around the housing, the brush holder could need
replacement.
Post by Adam
Any idea why Thunderbird keeps getting this warning...
https://i.postimg.cc/G2g7yfLK/Thunderbird-Warning-Unresponsive-script.png
Seems like the same line/location every time. Then, the window goes
gray and the system gets sluggish for a minute or so.
Maybe something has attacked one of the .js files in the
profile folder ? If you view a lot of HTML content within
Thunderbird, It's possible there's an exploit that way.
I turn off HTML via one of the prefs in there (the
equivalent of about:config but via the settings panel
for it).

Thunderbird is Firefox in disguise. The three-pane view
is made via an XML file. The window is a browser window.
It really should not slow down, as the files they write
to do that, would be built for performance. It's only
when files or content that should not be in the files
gets there, it eats into CPU cycles. For the simplest pests,
maybe opening a prefs.js and looking near the end, would
present a few lines that don't belong. I'm not an expert on
stuff like that, and stumble around in there like
anyone else. I wouldn't know a .js from a .htm :-)

Paul
Adam
2021-04-07 23:41:59 UTC
Reply
Permalink
Post by Paul
Post by Adam
Post by Paul
Post by Adam
[OT] Are there good automotive motor repair newsgroups (where ABS Booster Pump Motor repair can be discussed) ?
ABS Booster Pump - Repair or Replace? Part Sources? Rebuild in DFW, TX (6 Viewers)
https://forum.ih8mud.com/threads/abs-booster-pump-repair-or-replace-part-sources-rebuild-in-dfw-tx.992375/
Looks like my ABS Booster Motor Pump needs new components (commutator, brushes and bearings).
Look in newsgroups under the brand of your car.
alt.autos.toyota.*
A small electric motor shop could look at it. They do
things like rewind burned coils. Ours had a coil winding
machine (which likely only services a few types of motors).
I used to go to the small motor shop, to buy enamel wire
from them.
The shops that work on generators, starters and alternators ?
The kind of shop I am referring to, is not automotive. They
would work on any motor, but from the electrical side of things.
They do brushes, commutators, fix bad windings. They're not
a rebuilder, because they wouldn't have the parts for just
anything. Like, if you needed a new shaft, they may not
stock blanks for just anything. There are various patterns
on the end, for the mechanical mating. There are standards
for some of it, making it easier to stock stuff. The distinction
is, they work on a lot of fractional horsepower motors. If you
had a 10,000 HP motor in your manufacturing plant, you'd
be calling somebody else. Big jobs need big tools. The coil
winder would be different, the wire as big as your finger.
Post by Adam
The following YouTube video shows the HBB pump motor and accumulator...
HBB (Hydraulic Brake Booster) new motor install 4runner gx470 lx470 abs unit screeching screaming noise
http://youtu.be/E5NoyVjZAWo
That's a reasonably small motor, but it runs from +12V
so the current flow is likely to be relatively high
for the motive power it generates.
Post by Adam
1998-2005 Lexus GS300 GS400 OEM Anti-Lock Brake Pump Accumulator Motor (47960-30030)
https://i.postimg.cc/GtPvwM7r/47960-30030-ABS-Pump-for-1999-Lexus-GS400-s-l1600.jpg
For this particular motor, most repairs have been on the brush assembly (not the coils).
Poor design or just old (1999) ? IDK
There are many photos in the following thread...
ABS Booster Pump - Repair or Replace? Part Sources? Rebuild in DFW, TX (6 Viewers)
https://forum.ih8mud.com/threads/abs-booster-pump-repair-or-replace-part-sources-rebuild-in-dfw-tx.992375/
It could be a cascade failure. Bearing seizes first. Motor
current climbs, as motor struggles to keep turning. Burns
brushes. Or, pops fuse. Now, for safety, can a thing
like that even be fused ? Maybe at a very high value of
current flow. I'm surprised at reports of "pedal to floor",
which would be a safety issue. A modulator when failed,
should leave the brake action operational - failure should
not cause a complete loss of pressure.
Yes, brake pedal has ZERO brake assist and feels very heavy with little to no brake effect.

LOUD buzzer + NO brake assist + DASH lights ON (BRAKE, VSC, ABS, VSC OFF) + DTC codes...
Loading Image...

The guy in the following video...

HBB (Hydraulic Brake Booster) new motor install 4runner gx470 lx470 abs unit screeching screaming noise
http://youtu.be/E5NoyVjZAWo

says that the LOUD buzzer is from reverse polarity ?
Post by Paul
Post by Adam
Weed cutters are cheap enough where buying a whole new one is less painful.
Not the case with car motors. :-)
You repair them, because they can be easy to fix. My lawn
mower only took me about ten minutes, taking my time, and
one reason is I asked for a crimp while I was there to
get the new brush. The crimp, pinches the brush wire to
the wire in the housing. So some brands, it wouldn't
be a problem to make them last 30 years. It's irritating
to see such poor designs, the plastic has melted. When it
doesn't have to be that way. It doesn't cost any more on
a BOM, to make a unit that doesn't fail that way. But
on stuff like that, the bearings aren't bad. Automotive,
everything is fucked bearings.
The guy in the following video...

2003-2004 TOYOTA 4 Runner ABS UNIT PROBLEMS GX470, C1223-C1251-C1256 (PART 2)


shows what components (commutator, brushes and bearings) are needed.

Where to buy quality small motor components ? What brands are good ?

I want to try DIY repair to prevent waste and for a quality repair.
Post by Paul
Post by Adam
For alternators, seems like rebuilt is all that's available.
At least, for my old Lexus GS400.
The discussion thread has a picture of the motor opened
up, so you can see the rotor and the windings. But the
commutator must be out of view, underneath. Brush assemblies
are usually spring loaded, and you can't use up the entire
carbon brush or it could flop around in the holder. If
they're worn, there's a sorta safe amount of wear, and
more than that, it won't stay in the holder properly.
They also wear in, and follow the curve of the commutator
when installed. The contact area will be a bit smaller than
normal at first, but they wear to shape and then the
friction will be less.
If you see dirt in the commutator, between plates (the ones
with wires joined to the plates and leading off to the coils),
don't panic. If you attempt to clean out the gap there,
you could be setting yourself up for a fail. Resist the
urge to do that. The problem is, hobbyists don't
have any tools for cleaning, and any cleaning action
there leaves burrs on the brass (edge). The burrs will cause
abnormal friction and cutting action on the brush face, which
you don't want. Too much dirt in the gap, causes conductive
failure, but too much "attention to detail" is also bad.
These are the things that would normally be turned in
a lathe, and returned to proper shape. But on small motors,
the commutator segments are too thin to be turned.
You can only tell whether it can be saved, once it is
taken apart. Look for reports from others on that.
Whether every one of them is destroyed. The thing is,
you'd need to find the end bearing, to attempt a
rebuild yourself. The screeching could be the bearing.
And you hope that sound isn't coming from the brushes
(the metal on the brush holder could scrape against
the commutator). If the brush ejects and is floating
around the housing, the brush holder could need
replacement.
Post by Adam
Any idea why Thunderbird keeps getting this warning...
https://i.postimg.cc/G2g7yfLK/Thunderbird-Warning-Unresponsive-script.png
Seems like the same line/location every time. Then, the window goes gray and the system gets sluggish for a minute or so.
Maybe something has attacked one of the .js files in the
profile folder ? If you view a lot of HTML content within
Thunderbird, It's possible there's an exploit that way.
I turn off HTML via one of the prefs in there (the
equivalent of about:config but via the settings panel
for it).
Okay, I changed it from "View > Message Body As > Original HTML" to "View > Message Body As > Plain Text".

Quickly Enable or Disable HTML Messages In Thunderbird
https://www.ghacks.net/2012/01/22/quickly-enable-or-disable-html-messages-in-thunderbird/
Post by Paul
Thunderbird is Firefox in disguise. The three-pane view
is made via an XML file. The window is a browser window.
It really should not slow down, as the files they write
to do that, would be built for performance. It's only
when files or content that should not be in the files
gets there, it eats into CPU cycles. For the simplest pests,
maybe opening a prefs.js and looking near the end, would
present a few lines that don't belong. I'm not an expert on
stuff like that, and stumble around in there like
anyone else. I wouldn't know a .js from a .htm :-)
Paul
Paul
2021-04-08 09:47:21 UTC
Reply
Permalink
Post by Adam
The guy in the following video...
2003-2004 TOYOTA 4 Runner ABS UNIT PROBLEMS GX470, C1223-C1251-C1256 (PART 2)
http://youtu.be/kJXl9O5BhsU
shows what components (commutator, brushes and bearings) are needed.
Where to buy quality small motor components ? What brands are good ?
I could see a replacement motor on Amazon, but it's out of stock,
which means the OEM has stopped making it.

I don't know the electric motor industry in that kind of detail,
as to where the parts come from. Or say, who makes commutators.

At this point, I'm still assuming this is a DC motor, based on the
two brushes being on either side of what looks like a commutator,
and it's not "slip rings". On slip rings, the contacts would
not be in the same plane. Each contact would line up with its
own circular ring. The guy in the video referred to "collector",
and I think that's a slip ring terminology.

In the video, the inside of the motor looks a bit dirty, suggesting
a lot of brush carbon or something. The brush assemblies might be
self-contained ones (brush+holder, instead of brush being separately
replaceable). I notice the brushes didn't shoot out when the
rotating part was pulled free.
Post by Adam
Post by Adam
Any idea why Thunderbird keeps getting this warning...
https://i.postimg.cc/G2g7yfLK/Thunderbird-Warning-Unresponsive-script.png
Okay, I changed it from "View > Message Body As > Original HTML" to
"View > Message Body As > Plain Text".
Quickly Enable or Disable HTML Messages In Thunderbird
https://www.ghacks.net/2012/01/22/quickly-enable-or-disable-html-messages-in-thunderbird/
Something in the setup of .js and such files, is calling for
the execution of something which is not normally there. Remember
that even if you disable HTML rendering, that applies to
content in emails (or in USENET news items). The three-pane view
is also a browser artifact, and that part never gets disabled,
because without that, you'd have no three-pane view in Thunderbird.

On Windows, something like adwcleaner could spot items that
did not belong. But that tool was bought from the developer,
and another company (Malwarebytes?) now maintains it.

About the only "easy" debug tool, is something like strace,
which can show which files the program is accessing. I would think
it would be extremely hard, to notice something out of the ordinary
by debugging that way. It could be referring to random files in
the cache, and that's not going to tell us anything. All you might
see, is excess CPU consumption in "top". Using gdb on it, is kinda
too low of a level to go. And then you're left with trying to
make sense of the content of the files in the profile folder.

The problem is, how do you (easily) clean out the profile, while
at the same time not losing any emails or useful settings. There
was something like mozbackup, but then, if someone injected something
into your profile, it might be designed to get backed up too.

Loading Image...

It's just really hard to find a free lunch here - something that
filters off crap, yet doesn't lose any custom settings.

I don't think I've *ever* seen Thunderbird do that here, but
then again, I don't use Thunderbird for "live email". I have a
Thunderbird in a VM, with an email server, for testing, and that's
about as close to email usage as I get.

*******

It could be a Lightning Calendar problem, which is an extension
added by default to modern releases of TBird. The last time I
did a TBird setup, I removed that extension. No idea what it's
doing - maybe it uses webdav to reach a server ?

https://support.mozilla.org/en-US/questions/1168837

Paul
Adam
2021-04-09 20:17:15 UTC
Reply
Permalink
Post by Paul
Post by Adam
The guy in the following video...
2003-2004 TOYOTA 4 Runner ABS UNIT PROBLEMS GX470, C1223-C1251-C1256 (PART 2)
http://youtu.be/kJXl9O5BhsU
shows what components (commutator, brushes and bearings) are needed.
Where to buy quality small motor components ? What brands are good ?
I could see a replacement motor on Amazon, but it's out of stock,
which means the OEM has stopped making it.
I don't know the electric motor industry in that kind of detail,
as to where the parts come from. Or say, who makes commutators.
At this point, I'm still assuming this is a DC motor, based on the
two brushes being on either side of what looks like a commutator,
and it's not "slip rings". On slip rings, the contacts would
not be in the same plane. Each contact would line up with its
own circular ring. The guy in the video referred to "collector",
and I think that's a slip ring terminology.
In the video, the inside of the motor looks a bit dirty, suggesting
a lot of brush carbon or something. The brush assemblies might be
self-contained ones (brush+holder, instead of brush being separately
replaceable). I notice the brushes didn't shoot out when the
rotating part was pulled free.
Post by Adam
Post by Adam
Any idea why Thunderbird keeps getting this warning...
https://i.postimg.cc/G2g7yfLK/Thunderbird-Warning-Unresponsive-script.png
Okay, I changed it from "View > Message Body As > Original HTML" to "View > Message Body As > Plain Text".
Quickly Enable or Disable HTML Messages In Thunderbird
https://www.ghacks.net/2012/01/22/quickly-enable-or-disable-html-messages-in-thunderbird/
Something in the setup of .js and such files, is calling for
the execution of something which is not normally there. Remember
that even if you disable HTML rendering, that applies to
content in emails (or in USENET news items). The three-pane view
is also a browser artifact, and that part never gets disabled,
because without that, you'd have no three-pane view in Thunderbird.
The warning keeps complaining about the Folder Pane so, today,
I removed ALL newsgroups from the other accounts that are not really used.
Maybe there was just too much clutter ? Keeping my fingers crossed.
Post by Paul
On Windows, something like adwcleaner could spot items that
did not belong. But that tool was bought from the developer,
and another company (Malwarebytes?) now maintains it.
About the only "easy" debug tool, is something like strace,
which can show which files the program is accessing. I would think
it would be extremely hard, to notice something out of the ordinary
by debugging that way. It could be referring to random files in
the cache, and that's not going to tell us anything. All you might
see, is excess CPU consumption in "top". Using gdb on it, is kinda
too low of a level to go. And then you're left with trying to
make sense of the content of the files in the profile folder.
The problem is, how do you (easily) clean out the profile, while
at the same time not losing any emails or useful settings. There
was something like mozbackup, but then, if someone injected something
into your profile, it might be designed to get backed up too.
http://mozbackup.jasnapaka.com/images/eng/04.png
It's just really hard to find a free lunch here - something that
filters off crap, yet doesn't lose any custom settings.
I don't think I've *ever* seen Thunderbird do that here, but
then again, I don't use Thunderbird for "live email". I have a
Thunderbird in a VM, with an email server, for testing, and that's
about as close to email usage as I get.
*******
It could be a Lightning Calendar problem, which is an extension
added by default to modern releases of TBird. The last time I
did a TBird setup, I removed that extension. No idea what it's
doing - maybe it uses webdav to reach a server ?
https://support.mozilla.org/en-US/questions/1168837
Paul
Paul
2021-04-07 20:27:04 UTC
Reply
Permalink
Post by Adam
[OT] Are there good automotive motor repair newsgroups (where ABS
Booster Pump Motor repair can be discussed) ?
ABS Booster Pump - Repair or Replace? Part Sources? Rebuild in DFW, TX (6 Viewers)
https://forum.ih8mud.com/threads/abs-booster-pump-repair-or-replace-part-sources-rebuild-in-dfw-tx.992375/
Looks like my ABS Booster Motor Pump needs new components
(commutator, brushes and bearings).
I took a closer look at this. It's a relatively high-res picture.

https://forum.ih8mud.com/attachments/20171003_184234-jpg.1556058/

The housing looks a bit failed, like it's not sealing properly on
the side facing the camera. That could allow water to eventually
get in there. You would want to inspect the rest of the
assembly that the motor joins to, because it could be
corroded and damaged the same way.

You can see the brush assembly. I spotted the braided copper
wire on the side, and the braided stuff is embedded in the
carbon brush. The spring visible in the picture is compressed,
and that tells me the brush isn't worn. If the spring was
relaxed, that would be a hint the brush was shot. The end of
the braided copper appears to be underneath a screw. The
ones I've fixed, had a crimp instead.

The brush has the wire on the side. Some are on the side, some
on the end, depending on holder design. The spring is usually
designed for a relatively long travel. The spring force
does not have to be too high - if it was, it would cause
excessive brush wear.

Be careful when attempting to pull the commutator and rotor,
out from between the brushes. You want to make sure no "tricks"
or special tools are needed to hold the brushes into their holders,
during reassembly. I've had motors before, where I pulled the
rotating part free, and couldn't figure out a way to get the
brushes depressed for reassembly. It's a matter of whether
you can get fingers or tools in there to keep them depressed.
You can't use any brutal techniques that mark up the brush
faces. It's tempting...

In this case, I also don't know how easy it is to get the
bearing out. Or where you could order the exact bearing.

Paul
Adam
2021-04-08 00:39:54 UTC
Reply
Permalink
Post by Paul
Post by Adam
[OT] Are there good automotive motor repair newsgroups (where ABS Booster Pump Motor repair can be discussed) ?
ABS Booster Pump - Repair or Replace? Part Sources? Rebuild in DFW, TX (6 Viewers)
https://forum.ih8mud.com/threads/abs-booster-pump-repair-or-replace-part-sources-rebuild-in-dfw-tx.992375/
Looks like my ABS Booster Motor Pump needs new components (commutator, brushes and bearings).
I took a closer look at this. It's a relatively high-res picture.
https://forum.ih8mud.com/attachments/20171003_184234-jpg.1556058/
The housing looks a bit failed, like it's not sealing properly on
the side facing the camera. That could allow water to eventually
get in there. You would want to inspect the rest of the
assembly that the motor joins to, because it could be
corroded and damaged the same way.
Those are pics for someone else's ABS pump motor. Same ABS pump motor as mine.
My faulty ABS pump motor is still on the vehicle.

This is the "used" ABS pump motor that I bought...

1998-2005 Lexus GS300 GS400 OEM Anti-Lock Brake Pump Accumulator Motor (47960-30030)
https://i.postimg.cc/GtPvwM7r/47960-30030-ABS-Pump-for-1999-Lexus-GS400-s-l1600.jpg

Not sure about the condition though.

Once, my faulty ABS pump motor comes off the vehicle, I plan to repair it (if feasible) in case the "used" one doesn't last very long. You never know when buying "used" auto parts.
Post by Paul
You can see the brush assembly. I spotted the braided copper
wire on the side, and the braided stuff is embedded in the
carbon brush. The spring visible in the picture is compressed,
and that tells me the brush isn't worn. If the spring was
relaxed, that would be a hint the brush was shot. The end of
the braided copper appears to be underneath a screw. The
ones I've fixed, had a crimp instead.
Not bad, Guru Paul !!

The brushes are at the bottom and the carbon part is hidden from view.
Post by Paul
The brush has the wire on the side. Some are on the side, some
on the end, depending on holder design. The spring is usually
designed for a relatively long travel. The spring force
does not have to be too high - if it was, it would cause
excessive brush wear.
Be careful when attempting to pull the commutator and rotor,
out from between the brushes. You want to make sure no "tricks"
or special tools are needed to hold the brushes into their holders,
during reassembly. I've had motors before, where I pulled the
rotating part free, and couldn't figure out a way to get the
brushes depressed for reassembly. It's a matter of whether
you can get fingers or tools in there to keep them depressed.
You can't use any brutal techniques that mark up the brush
faces. It's tempting...
Sounds gnarly.
Post by Paul
In this case, I also don't know how easy it is to get the
bearing out. Or where you could order the exact bearing.
Paul
Maybe that's why they don't sell ABS pump motor rebuilds ?


That dreaded Thunderbird warning...

https://i.postimg.cc/G2g7yfLK/Thunderbird-Warning-Unresponsive-script.png

is still there.
Adam
2021-04-09 06:02:59 UTC
Reply
Permalink
Post by Adam
Post by Paul
Post by Adam
[OT] Are there good automotive motor repair newsgroups (where ABS Booster Pump Motor repair can be discussed) ?
ABS Booster Pump - Repair or Replace? Part Sources? Rebuild in DFW, TX (6 Viewers)
https://forum.ih8mud.com/threads/abs-booster-pump-repair-or-replace-part-sources-rebuild-in-dfw-tx.992375/
Looks like my ABS Booster Motor Pump needs new components (commutator, brushes and bearings).
I took a closer look at this. It's a relatively high-res picture.
https://forum.ih8mud.com/attachments/20171003_184234-jpg.1556058/
The housing looks a bit failed, like it's not sealing properly on
the side facing the camera. That could allow water to eventually
get in there. You would want to inspect the rest of the
assembly that the motor joins to, because it could be
corroded and damaged the same way.
Those are pics for someone else's ABS pump motor. Same ABS pump motor as mine.
My faulty ABS pump motor is still on the vehicle.
This is the "used" ABS pump motor that I bought...
1998-2005 Lexus GS300 GS400 OEM Anti-Lock Brake Pump Accumulator Motor (47960-30030)
https://i.postimg.cc/GtPvwM7r/47960-30030-ABS-Pump-for-1999-Lexus-GS400-s-l1600.jpg
Not sure about the condition though.
Once, my faulty ABS pump motor comes off the vehicle, I plan to repair it (if feasible) in case the "used" one doesn't last very long. You never know when buying "used" auto parts.
Post by Paul
You can see the brush assembly. I spotted the braided copper
wire on the side, and the braided stuff is embedded in the
carbon brush. The spring visible in the picture is compressed,
and that tells me the brush isn't worn. If the spring was
relaxed, that would be a hint the brush was shot. The end of
the braided copper appears to be underneath a screw. The
ones I've fixed, had a crimp instead.
Not bad, Guru Paul !!
The brushes are at the bottom and the carbon part is hidden from view.
Got your point about rewinding, Guru Paul !! I learned something. :-)

Once the ABS pump motor has been taken apart, may as well replace ALL components (commutator, windings, brushes and bearing).

How does the following ABS pump motor look...

Mitsubishi Shogun no brakes! HBB fault, ABS and brake light on. Fault finding and repair.


Interesting...

Broken Electric Motor? HOW TO Test If A Motor Armature With Commutator Is Damaged #ElectricMotor​

Post by Adam
Post by Paul
The brush has the wire on the side. Some are on the side, some
on the end, depending on holder design. The spring is usually
designed for a relatively long travel. The spring force
does not have to be too high - if it was, it would cause
excessive brush wear.
Be careful when attempting to pull the commutator and rotor,
out from between the brushes. You want to make sure no "tricks"
or special tools are needed to hold the brushes into their holders,
during reassembly. I've had motors before, where I pulled the
rotating part free, and couldn't figure out a way to get the
brushes depressed for reassembly. It's a matter of whether
you can get fingers or tools in there to keep them depressed.
You can't use any brutal techniques that mark up the brush
faces. It's tempting...
Sounds gnarly.
Just a thought...

How about shipping tape folded so that the sticky side is stuck to each other ?
Replace the commutator before the brushes ? Use folded shipping tape to protect/pull the new brushes back into the holder ? Then, cut shipping tape near where commutator and brush meet to release ?

Remove brushes to get them out of the way. Then, install new brushes last.
Post by Adam
Post by Paul
In this case, I also don't know how easy it is to get the
bearing out. Or where you could order the exact bearing.
Paul
Maybe that's why they don't sell ABS pump motor rebuilds ?
That dreaded Thunderbird warning...
https://i.postimg.cc/G2g7yfLK/Thunderbird-Warning-Unresponsive-script.png
is still there.
I unsubscribed from a bunch of newsgroups. Wait a few days and see if that helps.
Paul
2021-04-09 17:45:23 UTC
Reply
Permalink
Post by Adam
Got your point about rewinding, Guru Paul !! I learned something. :-)
Once the ABS pump motor has been taken apart, may as well replace ALL
components (commutator, windings, brushes and bearing).
How does the following ABS pump motor look...
Mitsubishi Shogun no brakes! HBB fault, ABS and brake light on. Fault finding and repair.
http://youtu.be/vrsXN6hy-JM
Interesting...
<facepalm>

How awful.

He put solder on the braid. Don't do that!!!
It makes the braid brittle. The braid is flexible, to
allow flexure at the brush. The braid will wick solder
and a major portion of the braid will become very stuff.

Where the solder stops and the dry braid begins, is
the stress point.

They used spot weld for a reason.

The motor could get hot enough to melt
solder, under fault conditions. It's not likely
to have thermal protection, either.

But at least that video shows us what obstacles
have been placed in our way. I thought there was
a screw where the braid met the wiring. In the other
pictures, I couldn't see the join-method.

Solder is not considered a structural material. It's
not the same as "Gorilla Glue". It is intended for
making low resistance electrical connections. His
bodge of the brush holders ? Ugh.

The design does seem to have some sensing capability.
But exactly how the sensing works isn't clear. The motor
design is so simple, there's no "stuck rotor" output
from the motor itself. But the codes for the car have
a code for that anyway. It could be based on measuring an
abnormally high current going into the motor. Or based
on measuring a noise signal on the current (as a surrogate
for RPM of the motor). It would be normal to have a
pressure sensor on the accumulator.

We might assume the two controls are relays, but one
of the relays could have some other function.

And the damage pattern on the sample commutator is weird.

I don't think a shop doing "rebuilds", would be using
solder. Just as when my toaster oven broke, I opened it
and found spot welds everywhere, I just tossed it. The
previous toaster oven had regular connection methods
and was repairable. The newer one was junkyard material
(as I had no intention of investing in the appropriate
kind of cold spot welder). My response was, to not
buy another toaster oven. Its day is done.

Paul
Adam
2021-04-09 19:49:59 UTC
Reply
Permalink
Post by Paul
Post by Adam
Got your point about rewinding, Guru Paul !! I learned something. :-)
Once the ABS pump motor has been taken apart, may as well replace ALL components (commutator, windings, brushes and bearing).
How does the following ABS pump motor look...
Mitsubishi Shogun no brakes! HBB fault, ABS and brake light on. Fault finding and repair.
http://youtu.be/vrsXN6hy-JM
Interesting...
<facepalm>
How awful.
He put solder on the braid. Don't do that!!!
I don't solder anyways. Not sure why he chose to solder.
The hook design is meant for crimping. Just press and done. So easy.
But, not sure how many times that can be done before the hook breaks off. :-)
Post by Paul
It makes the braid brittle. The braid is flexible, to
allow flexure at the brush. The braid will wick solder
and a major portion of the braid will become very stuff.
Where the solder stops and the dry braid begins, is
the stress point.
They used spot weld for a reason.
The motor could get hot enough to melt
solder, under fault conditions. It's not likely
to have thermal protection, either.
But at least that video shows us what obstacles
have been placed in our way. I thought there was
a screw where the braid met the wiring. In the other
pictures, I couldn't see the join-method.
Solder is not considered a structural material. It's
not the same as "Gorilla Glue". It is intended for
making low resistance electrical connections. His
bodge of the brush holders ? Ugh.
The design does seem to have some sensing capability.
But exactly how the sensing works isn't clear. The motor
design is so simple, there's no "stuck rotor" output
from the motor itself. But the codes for the car have
a code for that anyway. It could be based on measuring an
abnormally high current going into the motor. Or based
on measuring a noise signal on the current (as a surrogate
for RPM of the motor). It would be normal to have a
pressure sensor on the accumulator.
Hydraulic Brake Booster Assembly has an oil pressure sensor.

No Sensor DTC generated though.
Post by Paul
We might assume the two controls are relays, but one
of the relays could have some other function.
Brake-related relays...

88263N - RELAY, ABS MOTOR <<< ABS Pump Motor Relay
88263M - RELAY, ABS SOLENOID <<< ABS Modulator Relay
89633A - RELAY, TRACTION CONTROL OR VSC <<< TRAC Motor Relay

Already replaced ABS pump motor relay.

Just ordered the other two relays.

How to test relays ?
Post by Paul
And the damage pattern on the sample commutator is weird.
I don't think a shop doing "rebuilds", would be using
solder. Just as when my toaster oven broke, I opened it
and found spot welds everywhere, I just tossed it. The
previous toaster oven had regular connection methods
and was repairable. The newer one was junkyard material
(as I had no intention of investing in the appropriate
kind of cold spot welder). My response was, to not
buy another toaster oven. Its day is done.
Paul
Paul
2021-04-09 21:14:14 UTC
Reply
Permalink
Post by Adam
Already replaced ABS pump motor relay.
Just ordered the other two relays.
How to test relays ?
Relays have coils.

Relays have contacts (SPDT, DPDT, single pole double throw, double pole double throw).

You try to get a spec for the relay trigger current.
And you have to know how the relay works.

Some relays are pulse operated, and this is
"moving something". The relay in this case,
is a kind of "mechanical memory".

__
_____/ \_______________ ON control

__
______________/ \______ OFF control

------- --------
|_______| Measured between NC and COM,
zero ohms when ON.

But most relays are simple amplifiers, and
when there is "coil current" of the right magnitude,
the arm closes and the contacts are pushed together.
Maybe 100mA of current, causes a 40A contact pair to close.

When building drivers for relays, a typical value is
to multiply the rated current by five. If the relay
coil needs 100mA, you hammer it with 500mA, to
"ensure it's closed". This might be provided by
a transistor drive circuit, where the Hfe is variable,
and it doesn't always deliver the 500mA you were expecting.
You might arrange it then, so that under optimistic
conditions it supplies 500mA, and some corner case involves
a lower current drive. They don't typically try to drive
exact currents into it.

Now, you might ask me "where do currents come from?".

Good question.

If I take a 12V battery and put a 1K ohm resistor
in series, the max current flow is 12 mA.

If I take a 12V battery and put a 100 ohm resistor
in series, the max current flow is 120mA.

Now, the relay coil has a specified resistance
value too. Let us say the relay coil is 100 ohms and
my external resistor is 100 ohms. 12V divided by 200 ohms,
gives 60mA through the circuit. Then I have to check
and see if that meets the trigger current flow value.

In some cases, the relay coil resistance is so high,
I can put 12V right across it (safety violation!).
Say for example, the relay coil is 1K ohms, the
trigger current is 6mA, my computed current is 12mA,
then it's going to work for me. But perhaps hard to drive
with "authority" by the 5X rule. When a company does that,
makes an automotive relay with an extremely high coil
resistance, it's a way of saying "nope, you're not going
to abuse ours" :-)

Anyway, a 12V battery and a resistor, provides a stimulus
for the coil, and an ohmmeter between COM and either NC
or NO, gives you a property to measure. You don't measure
from NC to NO - the measurements with be with respect
to the common (COM) terminal.

You put the meter on Ohms, to measure when the relay contacts
are closed. In cases where relays are required to carry
extreme currents, you actually ohm the contacts and
make sure they meet expected resistance. Say for example,
the contact is 50 milliohms, you could use some sort of
metering device to verify the value is less than that,
like say 37 milliohms. When a relay has low resistance
on the contacts, it gets "less warm" due to the
load. Running the headlights, might be 20 amps or 40 amps
or whatever.

For extreme currents, the name of the device changes
from "relay" to "contactor", if you need a Wikipedia
term. A central air uses a contactor, to handle the
compressor stall current flow.

Paul

Peter
2021-03-31 09:58:59 UTC
Reply
Permalink
Post by Adam
Post by Paul
Post by Adam
Post by Paul
Post by Adam
FYI, old Ubuntu Win.vdi used virtualbox-4.3 (v4.3.26 r98988).
For new Ubuntu install, which VirtualBox version should I install for
Win.vdi ?
For compatibility, do I need to install virtualbox-4.3 ?
I encountered problems (beyond the typos in the article) using the
following PPA method...
How To Install VirtualBox From PPA In Ubuntu 16.04
https://www.ubuntubuzz.com/2016/04/how-to-install-virtualbox-from-ppa-in.html
I undid whatever was done based on article (above).
And, installed virtualbox-5.0.  There's progress.
Now, I have network settings issues on VM startup...
https://i.postimg.cc/qM2tYmYJ/Could-not-start-the-machine-because-physical-network-interfaces-were-not-found-eth0-adapter-1.png
https://i.postimg.cc/XN2SWFZT/VM-Network-Settings-Adapter-1.png
https://i.postimg.cc/VsZTp8pw/VBox-Error-NS-ERROR-FAILURE.png
How to fix ?
Post by Paul
Post by Adam
Post by Paul
I won't comment on your installation attempt.
I'll comment on the notion of compatibility.
The .vbi is just a container. It has an image of something
inside. Well, that does not change from one release of VBox
to the next. A .vbi is just a .vbi. It's like a file system.
It's a means of transport and that is all.
However, there is a "settings file", which is XML based,
and it's critical. The settings control the
virtual hardware declarations.
You might have noticed for example, you can declare the virtual
hardware to have an Intel 440BX. That's my computer from the
year 2000. It would be a perfect chipset for an OS like Win98,
which is from that era. Or even Win2K or WinXP. Those would
likely have the vanilla IDE driver for that, as well as the
appropriate INT14 and INT15 behavior.
When you change from one version of VBox to another, some
of those items change. In particular, VirtualBox 6 made
some changes to the virtual graphics. It went from one
flavor to three flavors. If you download the VBox 6 PDF manual,
it will tell you what the purpose of those three is.
When VirtualBox 6 starts up, and sees the old XML files,
it should do its best to rewrite the XML files, using
the newer hardware items. It should be picking the
nearest equivalent graphic item to the old format.
I think I found in one case, that it had not done that
correctly, and I had to enter the Settings and select
another, and see if the Guest was "less pissed off at me".
Generally, if you deviate from the default selection,
it does not always end well for you. I think the first
time I tried that, the Guest black screened on me
(and you know how hard it is to debug something when
the symptoms are like that). While it might be fun
to change from 440BX for chipset, to ICH6 or ICH9 or
something, it doesn't always work out the way you
expected. That's the lesson I learned, was selecting
a "sexy" piece of hardware, was entirely unnecessary.
If it would accept the 440BX in the Guest OS, well,
that's just fine. Leave it.
But for the graphics, you pretty well have to fix it,
because sometimes if it makes the wrong choice, the
screen can't be resized.
All I'm pointing out here, is when the VBox 6 replaces
VBox 4, some of those virtual hardware items will
have changed. And occasionally, some work will be
required to get the Guest to boot. You want to keep
backup copies of the .vbi, so if the Guest OS records
that it's angry, you can remove the VBI file and restore
your backup to the folder. And try again. It won't
be the fault of the .vbi file, but if the OS decides
it's "Not Genuine" or the like, it may decide to
discard one tiny file, and that could make a difference
to later boot attempts.
You would hope Oracle does the migration properly,
each time the VBox version changes. But I've had at
least one case, where the transition wasn't perfect
and it took me a few tries to get it right.
    Paul
Thanks, Guru Paul !!
Almost forgot about the hidden .VirtualBox config files (XML)
directory.  Thanks for the reminder.
Already tarballed and extracted the VMs directory.
Just did the same for the hidden .VirtualBox config files (XML) directory.
How about the Extension Pack, which is for VBox 4 ?
.VirtualBox/.
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.4.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.20.vbox-extpack
.VirtualBox/./compreg.dat
.VirtualBox/./VBoxSVC.log.6
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.8.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.20.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.12.vbox-extpack
.VirtualBox/./VBoxSVC.log.7
.VirtualBox/./xpti.dat
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.14.vbox-extpack
.VirtualBox/./VirtualBox.xml-prev
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.10.vbox-extpack
.VirtualBox/./VBoxSVC.log.1
.VirtualBox/./VBoxSVC.log.2
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.16.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.22.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.22.vbox-extpack
.VirtualBox/./selectorwindow.log
.VirtualBox/./VBoxSVC.log.9
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.14.vbox-extpack
.VirtualBox/./selectorwindow.log.1
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.26.vbox-extpack
.VirtualBox/./VBoxSVC.log.10
.VirtualBox/./vbox-ssl-cacertificate.crt
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.6.vbox-extpack
.VirtualBox/./VBoxSVC.log.8
.VirtualBox/./VBoxSVC.log.3
.VirtualBox/./VirtualBox.xml
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.12.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.10.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.14.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.8.vbox-extpack
.VirtualBox/./VBoxSVC.log.4
.VirtualBox/./VBoxSVC.log
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.16.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.18.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.18.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.20.vbox-extpack
.VirtualBox/./VBoxSVC.log.5
VirtualBox VMs/.
VirtualBox VMs/./Win
VirtualBox VMs/./Win/Logs
VirtualBox VMs/./Win/Logs/VBox.log
VirtualBox VMs/./Win/Logs/VBox.log.2
VirtualBox VMs/./Win/Logs/VBox.log.3
VirtualBox VMs/./Win/Logs/VBox.log.1
VirtualBox VMs/./Win/Win.vbox
VirtualBox VMs/./Win/Win.vbox-prev
VirtualBox VMs/./Win/Win.vdi
The extension pack, is for things like passthru USB.
You would think your Package Manager would include that.
It's no problem to go to the virtualbox site and download
a matching version manually. Then when you double-click the
file, it should open in VirtualBox and be unpacked.
Will deal with extras later.
Post by Paul
The Guest Additions are another item. The VBox 4 .vbi will
have Guest Additions for VBox 4 in it. You can apply the
Guest Additions for VBox 6. That might involve some DKMS
work and take a bit of time.
Okay, will do later.
Post by Paul
I doubt every one of my Guest Additions in VMs here is
up-to-date, but the tool usually warns you about
versioning when it notices.
That's why you keep backups, until the smoke has cleared :-)
There'll always be some little detail that needs touchup.
I have tarballs, source of tarballs and disk clones.  :-)
Post by Paul
But the settings file is the one that has some degree of
leverage, and sometimes you do have to look in there,
to see how fouled up things are.
    Paul
If your .vdi is WinXP be aware that 3D acceleration is no longer
supported in newer versions of VirtualBox.

"VirtualBox does not provide 3D acceleration for XP guests. VirtualBox
6.0.x was the last version that did."

According to this thread :
https://forums.virtualbox.org/viewtopic.php?f=6&t=98450
Adam
2021-03-31 20:56:20 UTC
Reply
Permalink
Post by Peter
Post by Adam
Post by Paul
Post by Adam
Post by Paul
Post by Adam
FYI, old Ubuntu Win.vdi used virtualbox-4.3 (v4.3.26 r98988).
For new Ubuntu install, which VirtualBox version should I install for
Win.vdi ?
For compatibility, do I need to install virtualbox-4.3 ?
I encountered problems (beyond the typos in the article) using the
following PPA method...
How To Install VirtualBox From PPA In Ubuntu 16.04
https://www.ubuntubuzz.com/2016/04/how-to-install-virtualbox-from-ppa-in.html
I undid whatever was done based on article (above).
And, installed virtualbox-5.0. There's progress.
Now, I have network settings issues on VM startup...
https://i.postimg.cc/qM2tYmYJ/Could-not-start-the-machine-because-physical-network-interfaces-were-not-found-eth0-adapter-1.png
https://i.postimg.cc/XN2SWFZT/VM-Network-Settings-Adapter-1.png
https://i.postimg.cc/VsZTp8pw/VBox-Error-NS-ERROR-FAILURE.png
How to fix ?
Post by Paul
Post by Adam
Post by Paul
I won't comment on your installation attempt.
I'll comment on the notion of compatibility.
The .vbi is just a container. It has an image of something
inside. Well, that does not change from one release of VBox
to the next. A .vbi is just a .vbi. It's like a file system.
It's a means of transport and that is all.
However, there is a "settings file", which is XML based,
and it's critical. The settings control the
virtual hardware declarations.
You might have noticed for example, you can declare the virtual
hardware to have an Intel 440BX. That's my computer from the
year 2000. It would be a perfect chipset for an OS like Win98,
which is from that era. Or even Win2K or WinXP. Those would
likely have the vanilla IDE driver for that, as well as the
appropriate INT14 and INT15 behavior.
When you change from one version of VBox to another, some
of those items change. In particular, VirtualBox 6 made
some changes to the virtual graphics. It went from one
flavor to three flavors. If you download the VBox 6 PDF manual,
it will tell you what the purpose of those three is.
When VirtualBox 6 starts up, and sees the old XML files,
it should do its best to rewrite the XML files, using
the newer hardware items. It should be picking the
nearest equivalent graphic item to the old format.
I think I found in one case, that it had not done that
correctly, and I had to enter the Settings and select
another, and see if the Guest was "less pissed off at me".
Generally, if you deviate from the default selection,
it does not always end well for you. I think the first
time I tried that, the Guest black screened on me
(and you know how hard it is to debug something when
the symptoms are like that). While it might be fun
to change from 440BX for chipset, to ICH6 or ICH9 or
something, it doesn't always work out the way you
expected. That's the lesson I learned, was selecting
a "sexy" piece of hardware, was entirely unnecessary.
If it would accept the 440BX in the Guest OS, well,
that's just fine. Leave it.
But for the graphics, you pretty well have to fix it,
because sometimes if it makes the wrong choice, the
screen can't be resized.
All I'm pointing out here, is when the VBox 6 replaces
VBox 4, some of those virtual hardware items will
have changed. And occasionally, some work will be
required to get the Guest to boot. You want to keep
backup copies of the .vbi, so if the Guest OS records
that it's angry, you can remove the VBI file and restore
your backup to the folder. And try again. It won't
be the fault of the .vbi file, but if the OS decides
it's "Not Genuine" or the like, it may decide to
discard one tiny file, and that could make a difference
to later boot attempts.
You would hope Oracle does the migration properly,
each time the VBox version changes. But I've had at
least one case, where the transition wasn't perfect
and it took me a few tries to get it right.
Paul
Thanks, Guru Paul !!
Almost forgot about the hidden .VirtualBox config files (XML)
directory. Thanks for the reminder.
Already tarballed and extracted the VMs directory.
Just did the same for the hidden .VirtualBox config files (XML) directory.
How about the Extension Pack, which is for VBox 4 ?
.VirtualBox/.
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.4.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.20.vbox-extpack
.VirtualBox/./compreg.dat
.VirtualBox/./VBoxSVC.log.6
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.8.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.20.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.12.vbox-extpack
.VirtualBox/./VBoxSVC.log.7
.VirtualBox/./xpti.dat
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.14.vbox-extpack
.VirtualBox/./VirtualBox.xml-prev
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.10.vbox-extpack
.VirtualBox/./VBoxSVC.log.1
.VirtualBox/./VBoxSVC.log.2
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.16.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.22.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.22.vbox-extpack
.VirtualBox/./selectorwindow.log
.VirtualBox/./VBoxSVC.log.9
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.14.vbox-extpack
.VirtualBox/./selectorwindow.log.1
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.26.vbox-extpack
.VirtualBox/./VBoxSVC.log.10
.VirtualBox/./vbox-ssl-cacertificate.crt
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.6.vbox-extpack
.VirtualBox/./VBoxSVC.log.8
.VirtualBox/./VBoxSVC.log.3
.VirtualBox/./VirtualBox.xml
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.12.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.3.10.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.14.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.8.vbox-extpack
.VirtualBox/./VBoxSVC.log.4
.VirtualBox/./VBoxSVC.log
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.16.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.18.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.2.18.vbox-extpack
.VirtualBox/./Oracle_VM_VirtualBox_Extension_Pack-4.1.20.vbox-extpack
.VirtualBox/./VBoxSVC.log.5
VirtualBox VMs/.
VirtualBox VMs/./Win
VirtualBox VMs/./Win/Logs
VirtualBox VMs/./Win/Logs/VBox.log
VirtualBox VMs/./Win/Logs/VBox.log.2
VirtualBox VMs/./Win/Logs/VBox.log.3
VirtualBox VMs/./Win/Logs/VBox.log.1
VirtualBox VMs/./Win/Win.vbox
VirtualBox VMs/./Win/Win.vbox-prev
VirtualBox VMs/./Win/Win.vdi
The extension pack, is for things like passthru USB.
You would think your Package Manager would include that.
It's no problem to go to the virtualbox site and download
a matching version manually. Then when you double-click the
file, it should open in VirtualBox and be unpacked.
Will deal with extras later.
Post by Paul
The Guest Additions are another item. The VBox 4 .vbi will
have Guest Additions for VBox 4 in it. You can apply the
Guest Additions for VBox 6. That might involve some DKMS
work and take a bit of time.
Okay, will do later.
Post by Paul
I doubt every one of my Guest Additions in VMs here is
up-to-date, but the tool usually warns you about
versioning when it notices.
That's why you keep backups, until the smoke has cleared :-)
There'll always be some little detail that needs touchup.
I have tarballs, source of tarballs and disk clones. :-)
Post by Paul
But the settings file is the one that has some degree of
leverage, and sometimes you do have to look in there,
to see how fouled up things are.
Paul
If your .vdi is WinXP be aware that 3D acceleration is no longer
supported in newer versions of VirtualBox.
"VirtualBox does not provide 3D acceleration for XP guests. VirtualBox
6.0.x was the last version that did."
https://forums.virtualbox.org/viewtopic.php?f=6&t=98450
Thanks, I don't use any graphics acceleration.
Loading...