[qubes-users] Re: Failed to get initiator name from iscsi firmware

2019-12-05 Thread lorodion
It seems like this was a graphics error and not related to iSCSI. Adding the following boot arguments to [qubes] section in BOOTX64.cfg fixed the problem: *mapbs=1 noexitboot=1 modprobe.blacklist=nouveau rd.driver.blacklist=nouveau* As suggested here:

[qubes-users] Re: Failed to get initiator name from iscsi firmware

2019-12-02 Thread lorodion
Moving the disk to another computer and then installing Qubes works. However after moving the disk back it can no longer boot (not surprised)... Is it possible to edit boot options to get it booting or are hardware differences a problem? -- You received this message because you are subscribed

[qubes-users] Re: Failed to get initiator name from iscsi firmware

2019-12-02 Thread lorodion
Since iSCSI is used just for networking, can it be disabled? https://anaconda-installer.readthedocs.io/en/latest/iscsi.html -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an

[qubes-users] Re: Failed to get initiator name from iscsi firmware

2019-12-02 Thread lorodion
Is iSCSI used just for networking? If so, is it possible to disable it? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com.

[qubes-users] Re: Qubes R4.0.1 Installer - The name org.freedesktop.UDisk2 was not provided by any .service files

2019-12-02 Thread lorodion
I get the same error running the installer on my XMG P407 laptop which has an M.2 SATA disk. Did you figure out how to solve it? Also posted here: https://groups.google.com/d/topic/qubes-users/cxDUYf7k0Cg/discussion On Saturday, May 18, 2019 at 12:43:18 AM UTC, Adam Lewis wrote: > > Manually

[qubes-users] Re: Failed to get initiator name from iscsi firmware

2019-12-02 Thread lorodion
After more testing with different releases I can conclude that the following low level errors are throw*n:* - *Qubes 4.0.2-rc2*: blivet.errors.DependencyError: storaged iSCSI functionality not available - *Qubes 4.0.1* & *Qubes 4.0 RC4*: blivet.safe_dbus.DBusCallError: Failed to call

[qubes-users] Failed to get initiator name from iscsi firmware

2019-11-29 Thread lorodion
Hello, I'm trying to install Qubes 4 on an XMG P407 laptop. Unfortunately I get the error "failed to get initiator name from iscsi firmware", coming from here: https://github.com/fepitre/qubes-installer-qubes-os/commit/2ee1f1ad93d0e51cb264aefdb3d6147223136eb7 Reading Reddit it seems like P407

[qubes-users] Problem installing Qubes on two laptops

2019-11-29 Thread lorodion
Hello, I'm trying to install Qubes 4 on an XMG P407 laptop. Unfortunately I get the error "failed to get initiator name from iscsi firmware", coming from here: https://github.com/fepitre/qubes-installer-qubes-os/commit/2ee1f1ad93d0e51cb264aefdb3d6147223136eb7 Reading Reddit it seems like P407

Re: [qubes-users] UnicodeDecodeError during Qubes 4.0 installation

2018-11-05 Thread lorodion
Since it was a file system error, I formatted the disk prior to starting the Qubes installation. This solved the problem for me. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it,

Re: [qubes-users] UnicodeDecodeError during Qubes 4.0 installation

2018-11-04 Thread lorodion
I have a similar problem installing Qubes R4.0 - it fails when loading the graphical installer with an "unknown error". The error is similarily: "UnicodeDecodeError: 'utf-8' codec can not decode byte 0xc0 in position 3: invalid start byte". Looking through the stack trace reveals that the