"Pane is dead" error when attempting to install 4.0-rc4

[ArmeF97]

Hi. I can't install QubesOS.
Today I tried 4.0rc3 installer (tested also on rc4)

This is what I do to create an USB bootable. Oh, I forgot to mention my new lapton, " ASUS FX753VD-GC193T". (Details here 07.2605.pdf )
I tried UEFI installation and LEGACY, too. Secure boot disabled.
First, my BIOS asks me this (which one to boot)

There are 3 options: Legacy, Uefi, and Uefi "partition 1".
Let's start with UEFI without "Partion 1"

Here is the menu displayed. It's in the center of the screen, it's a little menu.
Whichever option I choose, it goes to anothere big menu (all screen this time)

Which has the same options, but it's larger in all the screen. But, which ever options I choose, nothing happens, it'll just re-do this menu.
And that's all for UEFI without "Partition 1".

Now, let's choose "Partition 1" from this beautiful good looking graphical boot menu

Let's see what happens.

Same little menu in the center, but now the options do something! :)
Let's choose "Install QubesOS"

And that's the result. :(
Same with choosing "Test"
Let's try "Troubleshooting"

And a nice black screen appears. :(
So, UEFI it's not possible.
There is still hope. Let's try Legacy!

Ok, let's try "Test"

Stucked here :(
Let's try "Install"

Stuck here. Let's take a picture of the text zoomed

With this at the bottom

"Pane is dead"... I don't know what that means. :(
Let's try "Troubleshooting"

This nice menu appears.
Let's try "Install"

Same error as before, but in low graphics

And that's it. I say that I have problem with the installation in any version (I tried 3.2 and 4.0rc2), because the problems where very similar to this one.
I hope you can help me :) thank you

[ArmeF97]

I should also say (because the title was edited not by me) that this "Pane error" didn't occur in 3.2 or 4.0rc2 (errors were different)

[ArmeF97]

I should also say (because the title was edited not by me) that this "Pane error" didn't occur in 3.2 or 4.0rc2 (errors were different)

[andrewdavidwong]

@ArmeF97:

I should also say (because the title was edited not by me) that

I edited your title to be more descriptive of the problem. "Can't install QUBESOS (any version)" was not very descriptive.

this "Pane error" didn't occur in 3.2 or 4.0rc2 (errors were different)

What errors did you receive in 3.2 and 4.0-rc2?

[andrewdavidwong]

@ArmeF97:

I should also say (because the title was edited not by me) that

I edited your title to be more descriptive of the problem. "Can't install QUBESOS (any version)" was not very descriptive.

this "Pane error" didn't occur in 3.2 or 4.0rc2 (errors were different)

What errors did you receive in 3.2 and 4.0-rc2?

[ArmeF97]

@andrewdavidwong
4.0rc2 stuck here

And 3.2 goes to text installation because my GPU isn't supported (I think) and text installation fails at partitioning (the bug is already known but of course it's 3.2 so it's not updated)

[ArmeF97]

@andrewdavidwong
4.0rc2 stuck here

And 3.2 goes to text installation because my GPU isn't supported (I think) and text installation fails at partitioning (the bug is already known but of course it's 3.2 so it's not updated)

[NinjaTurtle007]

I get the same window as your screenshot here https://user-images.githubusercontent.com/6240983/33285574-ff19ba94-d3b2-11e7-9251-ac9bbb3acf42.jpg
whatever i try. Legacy boot, rc2, rc3

What I observed though!
I reinstalled rc2 from scratch multiple times during one day, (im still new and managed to lose access to usb keyboard couple of times, then killed sys-net somehow)

while fighting this rc3 came out and I happily installed it hoping it would solve some of my problems.
It installed JUST FINE the first time. When I messed it up again and needed to do yet another clean reinstall i started getting the window above.

I tried different usb drives, redoing the iso of rc2, then rc3 again
disabled efi boot

always the same!

# So, in short, i was reinstaling rc2 number of times without any issues. As soon as I installed rc3 ONCE, then I was no longer to boot from USB!

[NinjaTurtle007]

I get the same window as your screenshot here https://user-images.githubusercontent.com/6240983/33285574-ff19ba94-d3b2-11e7-9251-ac9bbb3acf42.jpg
whatever i try. Legacy boot, rc2, rc3

What I observed though!
I reinstalled rc2 from scratch multiple times during one day, (im still new and managed to lose access to usb keyboard couple of times, then killed sys-net somehow)

while fighting this rc3 came out and I happily installed it hoping it would solve some of my problems.
It installed JUST FINE the first time. When I messed it up again and needed to do yet another clean reinstall i started getting the window above.

I tried different usb drives, redoing the iso of rc2, then rc3 again
disabled efi boot

always the same!

# So, in short, i was reinstaling rc2 number of times without any issues. As soon as I installed rc3 ONCE, then I was no longer to boot from USB!

[ArmeF97]

@NinjaTurtle007
I did try 4.0rc2, but, it gets stuck here https://user-images.githubusercontent.com/6240983/33363556-25cf8cac-d4e1-11e7-8479-cbceeb94e01e.jpg
Isn't it the same for you?

[ArmeF97]

@NinjaTurtle007
I did try 4.0rc2, but, it gets stuck here https://user-images.githubusercontent.com/6240983/33363556-25cf8cac-d4e1-11e7-8479-cbceeb94e01e.jpg
Isn't it the same for you?

[NinjaTurtle007]

ill make one of the usb drives back to rc2 today, try and let you know.

I really hope we can solve this asap, a lot of my work is on hold until I get that system back.
And i was just hoping to do a nice small upgrade, lol :)

[NinjaTurtle007]

ill make one of the usb drives back to rc2 today, try and let you know.

I really hope we can solve this asap, a lot of my work is on hold until I get that system back.
And i was just hoping to do a nice small upgrade, lol :)

[ArmeF97]

I found this (referring to my problem with 4.0rc2)
https://www.reddit.com/r/Qubes/comments/5jyfjc/help_installation_stopped_at_790931/dbknopc/
Which says to leave the pc overnight... I don't know :( I'll git it a try

[ArmeF97]

I found this (referring to my problem with 4.0rc2)
https://www.reddit.com/r/Qubes/comments/5jyfjc/help_installation_stopped_at_790931/dbknopc/
Which says to leave the pc overnight... I don't know :( I'll git it a try

[NinjaTurtle007]

Wow, sounds funny, I mean that is not bread that needs to bulk up to leave it overnight.
I used to install it in under 15 mins, (i7, m.2 ssd, 16gb ram, usb 3.1)
And have left it for hours though.
However, will leave it overnight, just to have it tried but doubt it will help :(

[NinjaTurtle007]

Wow, sounds funny, I mean that is not bread that needs to bulk up to leave it overnight.
I used to install it in under 15 mins, (i7, m.2 ssd, 16gb ram, usb 3.1)
And have left it for hours though.
However, will leave it overnight, just to have it tried but doubt it will help :(

[ArmeF97]

The circle moved for me, so it was not completely stuck

[ArmeF97]

The circle moved for me, so it was not completely stuck

[NinjaTurtle007]

ah you meant to leave that install overnight?
well i dont go pass the efi windows with rc3

[NinjaTurtle007]

ah you meant to leave that install overnight?
well i dont go pass the efi windows with rc3

[ArmeF97]

rc3 doesn't work, but rc2 is slow, maybe i'll get rc2 tonight :)

[ArmeF97]

rc3 doesn't work, but rc2 is slow, maybe i'll get rc2 tonight :)

[NinjaTurtle007]

I tried with rc2, same as rc3
Actually I even tried to boot ubuntu 17.10 install and it's stuck at the ubuntu loading screen with the dots beneath the logo.

So to sum it up, after installing rc3 once, I can no longer boot ANYTHING from an USB drive.
How is this freakin possible?!

[NinjaTurtle007]

I tried with rc2, same as rc3
Actually I even tried to boot ubuntu 17.10 install and it's stuck at the ubuntu loading screen with the dots beneath the logo.

So to sum it up, after installing rc3 once, I can no longer boot ANYTHING from an USB drive.
How is this freakin possible?!

[ArmeF97]

They announced rc4.
I'll try qubes 4.0rc4 when it'll be out 👍

[ArmeF97]

They announced rc4.
I'll try qubes 4.0rc4 when it'll be out 👍

[mikekeehan]

The "cpu#N stuck for 22s! [Xorg:nnnn]" message is due to the nouveau video driver not being able to handle the new Nvidia chips. Same problem occurs in a Fedora installation. Workaround is to add the option "modprobe.blacklist=nouveau" to the kernel boot command. I believe that the Tab key gives access to the boot line at the menu. (This has been discussed a number of times on the User mailing list.)

[mikekeehan]

The "cpu#N stuck for 22s! [Xorg:nnnn]" message is due to the nouveau video driver not being able to handle the new Nvidia chips. Same problem occurs in a Fedora installation. Workaround is to add the option "modprobe.blacklist=nouveau" to the kernel boot command. I believe that the Tab key gives access to the boot line at the menu. (This has been discussed a number of times on the User mailing list.)

[ArmeF97]

I'm currently studing for my exams. When rc4 will be out, I'll try it and post it what happens. I'll also try what you said, @mikekeehan , so thank you

[ArmeF97]

I'm currently studing for my exams. When rc4 will be out, I'll try it and post it what happens. I'll also try what you said, @mikekeehan , so thank you

[ArmeF97]

Update: tested also on RC4
(same errors as the first post in this issue)

Then I tried @mikekeehan solution

uefi stucks here. I edited the file in /EFI/BOOT/ called "BOOTX64.cfg" and here it is
BOOTX64.zip
I didn't know where to add that line so I added it everywhere

Legacy stucks here

After doing this after pressing tab

[ArmeF97]

Update: tested also on RC4
(same errors as the first post in this issue)

Then I tried @mikekeehan solution

uefi stucks here. I edited the file in /EFI/BOOT/ called "BOOTX64.cfg" and here it is
BOOTX64.zip
I didn't know where to add that line so I added it everywhere

Legacy stucks here

After doing this after pressing tab

[marmarek]

Legacy stucks here

Press "ESC" to see more messages. I guess will be the same as in UEFI.

As for blacklisting nouveau driver - documentation is very inconsistent what actual option is, but I'd try rd.driver.blacklist=nouveau. In xen.cfg the right place is at the end of kernel= line.

[marmarek]

Legacy stucks here

Press "ESC" to see more messages. I guess will be the same as in UEFI.

As for blacklisting nouveau driver - documentation is very inconsistent what actual option is, but I'd try rd.driver.blacklist=nouveau. In xen.cfg the right place is at the end of kernel= line.

[ArmeF97]

Where can I find the xen.cfg file? @marmarek

[ArmeF97]

Where can I find the xen.cfg file? @marmarek

[marmarek]

It's BOOTX64.cfg, sorry.

[marmarek]

It's BOOTX64.cfg, sorry.

[ArmeF97]

Ok, but there are 4 "kernel=..." lines, which one? All? @marmarek

[ArmeF97]

Ok, but there are 4 "kernel=..." lines, which one? All? @marmarek

[marmarek]

All is ok.

[marmarek]

All is ok.

[ArmeF97]

kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-rc4-x86_64 i915.preliminary_hw_support=1 quiet rhgb rd.live.check modprobe.blacklist=nouveau rd.driver.blacklist=nouveau

Ok I added it, leaving the previous. I'll try boot now

[ArmeF97]

kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-rc4-x86_64 i915.preliminary_hw_support=1 quiet rhgb rd.live.check modprobe.blacklist=nouveau rd.driver.blacklist=nouveau

Ok I added it, leaving the previous. I'll try boot now

[ArmeF97]

@marmarek here
https://user-images.githubusercontent.com/6240983/36342231-99d13c46-13fb-11e8-9ef7-0e54c23a473b.jpg
I pressed tab, and wrote
modprobe.blacklist=nouveau rd.driver.blacklist=nouveau
(and I also edited the file you mentioned)
but it's stuck. Pressing ESC does nothing. Legacy mode

[ArmeF97]

@marmarek here
https://user-images.githubusercontent.com/6240983/36342231-99d13c46-13fb-11e8-9ef7-0e54c23a473b.jpg
I pressed tab, and wrote
modprobe.blacklist=nouveau rd.driver.blacklist=nouveau
(and I also edited the file you mentioned)
but it's stuck. Pressing ESC does nothing. Legacy mode

[marmarek]

What about UEFI?

[marmarek]

What about UEFI?

[ArmeF97]

I'll try it now

[ArmeF97]

I'll try it now

[ArmeF97]

Wow! Never made it so far!

Let me try and I'll write soon enough if it works! Thanks for now

[ArmeF97]

Wow! Never made it so far!

Let me try and I'll write soon enough if it works! Thanks for now

[ArmeF97]

Installed on a 1TB drive, I tell my boot option to boot it, I see some familiar text for an instant, then black screen... :( @marmarek

[ArmeF97]

Installed on a 1TB drive, I tell my boot option to boot it, I see some familiar text for an instant, then black screen... :( @marmarek

[ArmeF97]

I checked using Ubuntu (from another drive) and the xen.cfg it's set with the custom rule we added

[ArmeF97]

I checked using Ubuntu (from another drive) and the xen.cfg it's set with the custom rule we added

[marmarek]

Remove "quiet" and "rhgb" from there to see more details. Also try adding "mapbs=1" and "noexitboot=1" (as you had in BOOTX64.cfg) - maybe this was needed for your hardware.

[marmarek]

Remove "quiet" and "rhgb" from there to see more details. Also try adding "mapbs=1" and "noexitboot=1" (as you had in BOOTX64.cfg) - maybe this was needed for your hardware.

[ArmeF97]

Ok, sorry I was out last night. Now the xen.cfg is this. I'll try now to boot
xen.cfg.zip

[ArmeF97]

Ok, sorry I was out last night. Now the xen.cfg is this. I'll try now to boot
xen.cfg.zip

[ArmeF97]

Black screen @marmarek

[ArmeF97]

Black screen @marmarek

[ArmeF97]

After this, legacy mode, installed correctly (black screen was because of uefi)

No words to describe my thanks!
Thanks @marmarek & @mikekeehan

[ArmeF97]

After this, legacy mode, installed correctly (black screen was because of uefi)

No words to describe my thanks!
Thanks @marmarek & @mikekeehan

[mikekeehan]

On Sun, 18 Feb 2018 07:11:17 -0800 Federico Armellini ***@***.***> wrote:  After this, legacy mode, installed correctly (black screen was because of uefi) No words to describe my thanks! Thanks @marmarek & @mikekeehan

Glad you got it working Federico! Mike.

[mikekeehan]

On Sun, 18 Feb 2018 07:11:17 -0800 Federico Armellini ***@***.***> wrote:  After this, legacy mode, installed correctly (black screen was because of uefi) No words to describe my thanks! Thanks @marmarek & @mikekeehan

Glad you got it working Federico! Mike.