usysconf timeout on every retry

georgeonsolus

Hi,
today, I wanted to do a fresh reinstall of Solus. So I connected to the internet, set up disks, and started the install.
Everything went well for the first 15 minutes or so, but then came an error message. Something with usysconf took more than 300 seconds. I pressed yes to send the protocol. But funnily, after the error occured, nothing was working: WiFi, charger, not even disk recognition. I have tried multiple times, all with the same result.
Any help would be greatly appreciated.
Thanks,
George

Harvey

If the installer is open, close it and edit /usr/share/calamares/modules/shellprocess_postinstall.conf

Find this line

script:
    - command: "/usr/sbin/usysconf run"
      timeout: 300

Increase the timeout to at least double, save it and try again.

georgeonsolus

Harvey
This doesn't work.
I tried, but then I get errors about a python packing tool, usysconf produced no output and /etc/squash already exists.
Installing in a VM works.

Staudey

georgeonsolus I tried, but then I get errors about a python packing tool, usysconf produced no output and /etc/squash already exists.

If you could get the actual text of the error(s) that would be ideal

georgeonsolus

Staudey
The text is: "Befehl <i>/usr/sbin/usysconf</i> konnte nicht innerhalb von 300 Sekunden abgeschlossen werden. Soll das Installationsprotokoll an eine Internetadresse gesendet werden?" (Command <i>/usr/sbin/usysconf</i> could not be completed in 300 seconds, should the log be sent to an internet domain?)
And "Could not create directory /tmp/squash: already exists".

Staudey

You said you had an error "about a python packaging tool". What happened to that? The one you posted again sounds like it should be solved by Harvey's workaround (follow the steps he describes exactly; and make sure you edit the file as root and that it's actually saved before launching the installer again)

georgeonsolus

Staudey The python packaging tool error somehow resolved, and Harvey's workaround still causes the timeout. Only waits for a longer time.

Staudey

georgeonsolus Then why does your error above still talk about 300 seconds for usysconf? It seems like you didn't edit the file correctly. Again, make sure you edit it as root and save it BEFORE launching the installer.