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

[zarEclEC]

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

[zarEclEC]

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?

[zarEclEC]

@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!

[zarEclEC]

@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 :)

[zarEclEC]

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 :(

[zarEclEC]

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

[zarEclEC]

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?!

[zarEclEC]

They announced rc4. I'll try qubes 4.0rc4 when it'll be out :+1:

[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.)

[zarEclEC]

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

[zarEclEC]

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.

[zarEclEC]

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

[marmarek]

It's BOOTX64.cfg, sorry.

[zarEclEC]

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

[marmarek]

All is ok.

[zarEclEC]

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

[zarEclEC]

@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?

[zarEclEC]

I'll try it now

[zarEclEC]

Wow! Never made it so far! Let me try and I'll write soon enough if it works! Thanks for now

[zarEclEC]

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

[zarEclEC]

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.

[zarEclEC]

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

[zarEclEC]

Black screen @marmarek

[zarEclEC]

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 notifications@github.com 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.

[smak64]

Guys, is this bug of pane is dead fixed? Or we will have to edit stuff? I'm getting the same error in my new system

[andrewdavidwong]

@smak64: Please see above for information about how others resolved the problem. Please confirm whether the same does or does not work for you.

[MikeDotMpeg]

@andrewdavidwong I was experiencing the same issue as OP and can confirm that appending the following allowed the installation to proceed.

noexitboot=1 modprobe.blacklist=nouveau rd.driver.blacklist=nouveau --- intitrd.img

[Ce80]

Hello,

I have a very similar problem with the installation of Qubes-R4.0-x86_64.iso.

Booting with UEFI also gives me a full black screen.

Booting in legacy leads me to the install menu where I press tab and add "noexitboot=1 modprobe.blacklist=nouveau rd.driver.blacklist=nouveau --- intitrd.img" (since I am installing Qubes-R4.0-x86_64.iso I have i915.alpha_support=1 instead of i915.preliminary_hw_support=1)

which leads me again to the same page

From the above comments I know I should edit the BOOTX64.cfg file, but I am unable to open that file with writings rights, I can only mount the iso in read only. I have tried mounting the iso, copying the BOOTX64.cfg file and editing it but I could of course not add it back to the mounted iso file system.

So I tried opening the whole Qubes-R4.0-x86_64.iso with gVim. First, I only added "modprobe.blacklist=nouveau rd.driver.blacklist=nouveau" to the four "kernel=" lines, which gave me an error page with

Second, I followed the instructions found here https://www.engetsu-consulting.com/blog/installing-qubes-4-0-on-laptops-with-nvidia-gpus-that-do-not-support-the-nouveau-driver, so as to keep the same number of characters in the iso (I am trying to install on a Dell Inspiron, it does not have nvidia but has an integrated Intel GPU). This leads me to an error

I did not find the issue #4535 in the qubes-users mailing list

Since I am a beginner and still learning fundamentals (I am switching away from windows thanks to Qubes) I figured it might be faster to directly ask you how to edit the BOOTX64.cfg file.

In the BIOS, I have both Intel Virtualisation Technology and VT for Direct I/O enabled, and my SATA operations are on AHCI.

I hope you can help me, thanks in advance

[zarEclEC]

I'm sorry but I edited the file from another PC... you can't do that?

[andrewdavidwong]

I did not find the issue #4535 in the qubes-users mailing list

4535 is in qubes-issues (here). You can just click the link to go there.

[andrewdavidwong]

Reopening as a task to document the fix. Anyone here is welcome to submit a pull request:

https://www.qubes-os.org/doc/doc-guidelines/

[Ce80]

@ArmeF97 since Qubes did not install I still have Fedora installed on the computer (it is not yet overwritten), I have another computer but trust it less than the one with fedora, do I need another PC? is it not possible to make those changes on the same PC under fedora?

@andrewdavidwong sorry bad wording, I meant that I did check whether the issues raised in issue #4535 had also been raised in the qubes-users mailing list and found it had not

[Ce80]

@ArmeF97 Can I ask you for some more information? Based on the BOOTX64.zip file you sent I have eddited BOOTX64.cfg to

[global] default=qubes-verbose modprobe.blacklist=nouveau

[qubes-check] options=console=none kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-rc4-x86_64 i915.alpha_support=1 quiet rhgb rd.live.check modprobe.blacklist=nouveau ramdisk=initrd.img modprobe.blacklist=nouveau

[qubes] options=console=none kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-rc4-x86_64 i915.alpha_support=1 quiet rhgb modprobe.blacklist=nouveau ramdisk=initrd.img modprobe.blacklist=nouveau

[qubes-verbose] options=console=vga efi=attr=uc noexitboot=1 mapbs=1 kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-rc4-x86_64 i915.alpha_support=1 modprobe.blacklist=nouveau ramdisk=initrd.img modprobe.blacklist=nouveau

[qubes-rescue] options=loglvl=all kernel=vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0-rc4-x86_64 rescue modprobe.blacklist=nouveau ramdisk=initrd.img modprobe.blacklist=nouveau

But I cannot find the xen.cfg.zip file you sent, did you create and add it to the iso?

[zarEclEC]

But I cannot find the xen.cfg.zip file you sent, did you create and add it to the iso?

Well, I don't remember 😅 But I think you can find it using a file manager, in the ISO

[Ce80]

I couldn't find it, I only have a xen.gz. But you did edit both files?

[zarEclEC]

https://github.com/QubesOS/qubes-issues/issues/3340#issuecomment-366458557 It seems that that file was created after I successfully installed qubes, but I really don't remember. A year has passed. I'm sorry

[Ce80]

Hello, I have tried mounting the ISO, copying its content, making the changes, and creating a new ISO with genisoimage instead of inserting the changes back into the original ISO. It is still not successful, so I am hoping you could help me identify the mistake I am making in that process.

Here are the first steps of mounting and coping

After copying I made the following changes

I then created the new image with genisoimage (see first picture) and used dd to make a bootable USB

But I got this result

I believe that I am making a mistake in the process because the disk utility displays differently a bootable USB with the original iso, and a bootable USB with the modified iso (done with the above steps) which fills the whole USB and does not have an anaconda partition.

After I tried with the new release of Qubes 4.0.1, first with the original iso without modifying anything, same error as with Qubes 4.0, I get to the grub menu, try to install and get the same pane is dead error. I then tried modifying the ISO as above, except that I added 'sudo' after the error "cp: impossible to open 'mountedISO/EFI/BOOT/initrd.img' reading: Permission denied" (the 9th line in the picture).

I then made a bootable USB in two ways, first with the command

sudo dd if=Qubes_fixed.iso of=/dev/sda bs=1048576 && sync

and after by restoring an image via the disk utility on fedora. The changes I had made in BOOTX64.cfg were the same as those in the second image, and I again got the same result "no boot device found".

I hope you can help me identify what error I am making

Thanks in advance

[Ce80]

Half of my problem is solved, I needed to make a bootable USB with isohybrid not iso. This launches the installation, gets me to the grub menu where I press tab and add

Mapbs=1 noexitboot=1 modprobe.blacklist=nouveau rd.driver.blacklist=nouveau

like the solution described above. Unfortunately, this leads me to an error page with “warning: /dev/root does not exist”. The changes I made in the iso are the exact same as described in my previous post.

[smak64]

For my Gigabyte GA AX370 and Ryzen 3 2200G, Qubes 4.0.1 worked easily. In CPU core advanced settings, I enabled an option for virtualization and enabled IOMMU and everything was extremely smooth from there on. However, I'm facing problems with USB Tethering.

[n0nameNPC]

Half of my problem is solved, I needed to make a bootable USB with isohybrid not iso. This launches the installation, gets me to the grub menu where I press tab and add

Mapbs=1 noexitboot=1 modprobe.blacklist=nouveau rd.driver.blacklist=nouveau

like the solution described above. Unfortunately, this leads me to an error page with “warning: /dev/root does not exist”. The changes I made in the iso are the exact same as described in my previous post.

Hi, if your question still actual, - you need click "tab" on first menu, and replace from i965.*(?= ---) on "modprobe.blacklist=nouveau rd.driver.blacklist=nouveau"

you should get something like: "mboot.c32 xen.gz console=none ---vmlinuz inst.stage2=hd:LABEL=Qubes-R4.0.1-x86_64 modprobe.blacklist=nouveau rd.driver.blacklist=nouveau --- initrd.img"

and click enter and wait 5-15sec before next step.

still if the error repeats, you can try disable TPM module in BIOS.

[ThatAimDude]

I still have the problem here is a full video of what happens when i dont edit anything the grub menu. https://www.reddit.com/r/Qubes/comments/j2i5qn/pane_is_dead/

Im really confused and im not sure what to do