qubes-mgmt-salt-base-topd-4.0.0-1.fc25.noarch.rpm

[deusestverita...@gmail.com]

**Laptop still in this configuration [https://us.msi.com/pdf/nb/GL63%208RD-067.pdf] **

Installed Qubes 3.2 (UEFI and Legacy) all went great besides the display would not change from 800x600, and yes every terminal command was attempted to change it and also disable NVIDIA with no success.

Installing Qubes 4.0 (UEFI and Legacy) all goes well, (same as Qubes 3.2) get to GUI installer and start installation on the 1TB Hard Drive- gets to [qubes-mgmt-salt-base-topd-] [786/1018] (sometimes 781/1018 788/1018 794/1018 but always this title [qubes-mgmt-salt-base-topd]) and does not progress. Left it for hours, still no movement. You can hear the Hard Drive stop writing when it reaches that point.

Tried many different ISO editors to replace the [qubes-mgmt-salt-base-topd-4.0.0-1.fc25.noarch.rpm] with [qubes-mgmt-salt-base-topd-3.2.1-1.fc23.noarch.rpm] crazy? Oh Yeah. Thought that if the Qubes 3.2 [qubes-mgmt-salt-base-topd] worked then it would work with Qubes 4.0. Nope. Well actually haven't been able to write using Rufus 2.18 in Windows 8.1, it says "The current image doesn't match the boot option selected" even though it is still technically a ISO file, albeit a modified one. Yes, fedora 23/24 is the best for writing DD images, but since Qubes 3.2 worked and Qubes 4.0 works until the 786/1018 file, a different DD writer will not help. Right?

Have tried many different USB's high and low memory. Also multiple downloads of Qubes 4.0 and also tried Qubes 4.0 [rc1] [rc3] [rc5] first two never made it to the GUI installer screen [ACPI Error AE_NOT_FOUND] then [Installer cannot continue Press Enter to reboot]. Qubes 4.0-Rc5 made it to the same point as the final release of 4.0 then stopped.

**NOTE** Never was there an error or a explanation of the stopping at [qubes-mgmt-salt-base-topd] [786/1018] it just stopped.

Can do a complete HRL using Qubes 3.2 but only if absolutely necessary.

Questions:

What does [qubes-mgmt-salt-base-topd-4.0.0-1.fc25.noarch.rpm] draw from/correlate to? (Kernel, Graphics ect)?

Is it crazy think to try to replace [qubes-mgmt-salt-base-topd-4.0.0-1.fc25.noarch.rpm] with [qubes-mgmt-salt-base-topd-3.2.1-1.fc23.noarch.rpm]?

How to disable NVIDIA and would that help?

Is there a way to get past the ACPI Error? That would enable Qubes 4.0-rc1 to try and see if it also fails at [786/1018].
Already tried ACPI=off. This pretty well describes it.[https://groups.google.com/forum/#!searchin/qubes-users/qubes$20acpi%7Csort:date/qubes-users/ILXEZAD4TLA/cWqj76zAAQAJ]

No Computer Science degree, so Beginner/Intermediate Level.

Very resourceful. If you can Explain 13% of the questions asked that would be enough.


THANK YOU
BEST
ERIN D.

Ps. Stock Market. Will give you very valuable suggestions if what you say ends up working at all. Along with your message include [‡] at the end if you want to want this provided to you.

[awokd]

On Tue, May 15, 2018 9:12 pm, deusestverita...@gmail.com wrote:


> Installing Qubes 4.0 (UEFI and Legacy) all goes well, (same as Qubes 3.2)
> get to GUI installer and start installation on the 1TB Hard Drive- gets to
> [qubes-mgmt-salt-base-topd-] [786/1018] (sometimes 781/1018 788/1018
> 794/1018 but always this title [qubes-mgmt-salt-base-topd]) and does not
> progress. Left it for hours, still no movement. You can hear the Hard
> Drive stop writing when it reaches that point.

> Yes, fedora 23/24 is the best for writing DD
> images, but since Qubes 3.2 worked and Qubes 4.0 works until the 786/1018
> file, a different DD writer will not help. Right?

Not necessarily; maybe Rufus is doing something strange. Suggest booting a
live image and creating your R4.0 installer USB directly with DD.

> **NOTE** Never was there an error or a explanation of the stopping at
> [qubes-mgmt-salt-base-topd] [786/1018] it just stopped.
>
> Can do a complete HRL using Qubes 3.2 but only if absolutely necessary.
>
> Questions:
>
> What does [qubes-mgmt-salt-base-topd-4.0.0-1.fc25.noarch.rpm] draw
> from/correlate to? (Kernel, Graphics ect)?
>
> Is it crazy think to try to replace
> [qubes-mgmt-salt-base-topd-4.0.0-1.fc25.noarch.rpm] with
> [qubes-mgmt-salt-base-topd-3.2.1-1.fc23.noarch.rpm]?

Yes. :) I think that will break more things than it helps.

> How to disable NVIDIA and would that help?

It's something like nouveau.modeset=0, check the Nvidia troubleshooting
doc. Probably won't help if you're getting that far with the install.

[deusestverita...@gmail.com]

>Not necessarily; maybe Rufus is doing something strange. Suggest booting a
>live image and creating your R4.0 installer USB directly with DD.

If Live USB worked that isn't a really a solution to "using" Qubes 4.0, is it? Would that help to eventually achieving installing it?

> Yes. :) I think that will break more things than it helps.

Yeah, figured.

How to disable NVIDIA and would that help?

> It's something like nouveau.modeset=0, check the Nvidia troubleshooting
> doc. Probably won't help if you're getting that far with the install.

Tried that at the boot and also in Qubes 3.2 terminal with it rejecting it. Also Tried all the [Grub] and every linux command for changing display size to no end.

[awokd]

On Wed, May 16, 2018 3:49 am, deusestverita...@gmail.com wrote:
>>Not necessarily; maybe Rufus is doing something strange. Suggest booting
>> a
>>live image and creating your R4.0 installer USB directly with DD.
>
> If Live USB worked that isn't a really a solution to "using" Qubes 4.0, is
> it? Would that help to eventually achieving installing it?

I mean a Fedora or Debian live image, just to create the USB by using DD
directly instead of Rufus. Might fix your installation issue.

>> It's something like nouveau.modeset=0, check the Nvidia troubleshooting
>> doc. Probably won't help if you're getting that far with the install.
>
> Tried that at the boot and also in Qubes 3.2 terminal with it rejecting
> it. Also Tried all the [Grub] and every linux command for changing display
> size to no end.

If you're booting UEFI, you need to edit a different place. See the first
entry in https://www.qubes-os.org/doc/uefi-troubleshooting/. (But I don't
think this will help with the issue you're having.)

[deusestverita...@gmail.com]

> I mean a Fedora or Debian live image, just to create the USB by using DD
> directly instead of Rufus. Might fix your installation issue.

Ah, Yes.

> If you're booting UEFI, you need to edit a different place. See the first
> entry in https://www.qubes-os.org/doc/uefi-troubleshooting/. (But I don't
> think this will help with the issue you're having.)

Booted UEFI and Legacy with exact same conclusion. Installing Qubes 3.2 and the attempted installation of Qubes 4.0 have the same results when UEFI or Legacy is used.