matteopa wrote: ↑Sat Jan 19, 2019 12:33 pm
Nah, I don't usually check checksum for doing Virtual Machine installs. If I do installs on host /main machines I check the checksums. I did download it from one of the linked mirrors from MXLinux site though. Not from outside sources / other odd ball sites.
ALWAYS check.
We need to be sure that your checksum is good or we'll be helping to no avail after all. :)
I will from now on. And true, if it's crap ISO and causing issues, then never know if it's MX issue or crap ISO issue.
I've tried last two times to install it and got through Grub installation and through rest of installer without root password error etc. I might try later and download another ISO and check the checksum and try to install again then. But will be later tonight while I'm sleeping. Otherwise I can't do anything online for an hour or two while ISO downloads... on crappy 3mbps connection here. lol Or I can try and reinstall MX again later with the same ISO. Cause it happened with this ISO before once so...
Graphics:
Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.15.0.0 bus ID: 00:02.0
Display: x11 server: X.Org 1.19.2 driver: vmware
Also note PAE/NX is selected. Is that useful on a 64 bit system? Or even counterproductive?
None of these things might be relevant, but maybe...
I left the installer do the partitioning itself. So not sure if that's bug with MX installer or not... >_>
Um, for graphics controller the default selected was used: VMSVGA
not sure if that's VirtualBox graphic controller or not? There's also "VboxVGA" and "VboxSVGA" options there but never thought to change that?
I only did the PAE/NX cause got in habit watching a guy on youtube select it for installing some other distro. But did try a fresh installation without it and so forth. Didn't seem to make much difference cause the bugs are there anyway..lol
thank you for the info. the grub fault happened in the same place it looks like, but its likely that the problem is not in the grub installer itself but in the system installers connection to it. This may take a little while to sort out.
I'm glad it installed eventually, even if it was a little ugly.
If we are able to make a change to the installer, I'll be sure to notify here so that you can test again, since you have such a "good" system to test this with.
Um, for graphics controller the default selected was used: VMSVGA
not sure if that's VirtualBox graphic controller or not? There's also "VboxVGA" and "VboxSVGA" options there but never thought to change that?
I've never seen this option on the Linux Virtual Box, but I'm only running 5.2.24, so maybe it's something you see in version 6 or only on Windows hosts. On a Linux host, an MX guest reports:
dolphin_oracle wrote: ↑Sat Jan 19, 2019 7:20 pm
thank you for the info. the grub fault happened in the same place it looks like, but its likely that the problem is not in the grub installer itself but in the system installers connection to it. This may take a little while to sort out.
I'm glad it installed eventually, even if it was a little ugly.
If we are able to make a change to the installer, I'll be sure to notify here so that you can test again, since you have such a "good" system to test this with.
And thanks for sticking with it.
You're welcome and glad I can help you guys out. :) I'll keep trying installs here and there to see if the root password bug happens again and then post the details from terminal. I might also try and download another ISO later tonight before I go to bed and do checksum and see if it happens after grabbing another ISO.
Even with the old one (the one on the ISO) I tried and installed GRUB 20 times without a crash, but I did get 2 in a row first time I tried (same location) so hopefully this change fixed this issue. Too bad I cannot reliably reproduce the problem to know if I really fixed it.
Um, for graphics controller the default selected was used: VMSVGA
not sure if that's VirtualBox graphic controller or not? There's also "VboxVGA" and "VboxSVGA" options there but never thought to change that?
I've never seen this option on the Linux Virtual Box, but I'm only running 5.2.24, so maybe it's something you see in version 6 or only on Windows hosts. On a Linux host, an MX guest reports:
Not sure, but I had 5.x.x version of VirtualBox up until two nights ago and had those same controllers and not "vboxvideo". I'm on Windows 7 Home 64bit, so probably is for Windows host machines... hmm.
Even with the old one (the one on the ISO) I tried and installed GRUB 20 times without a crash, but I did get 2 in a row first time I tried (same location) so hopefully this change fixed this issue. Too bad I cannot reliably reproduce the problem to know if I really fixed it.
I had downloaded another MX-18_January_x64 ISO last night while I slept and checked the checksum and it matches, so the checksum passed. First time I installed I got grub error again and it crashed doing grub install, same error as before. I left VM open and ran the command sudo -E minstall again and got through grub installation and the rest of the installation as well. No root password error popup or whatever.
Will that DEB file of yours work on Windows VirtualBox instead of using an "ISO" mounted in it? Or is that DEB only for debian host machines with virtualbox on Linux machine?
matteopa wrote: ↑Sun Jan 20, 2019 1:33 pm
Will that DEB file of yours work on Windows VirtualBox instead of using an "ISO" mounted in it? Or is that DEB only for debian host machines with virtualbox on Linux machine?
It's a deb that you need to install in MX (VirtualBox has nothing to do with it, you can install on MX running in VirtualBox or running on metal), actually I asked Tim to update the installer so if it's not yet in the pool it should be soon then you won't need to download and install the deb you could run just a regular update before trying the installer -- but depending on what mirror you are connected to it might not come right now, so in a way is clearer if you download and install the deb and try again.