Oryx Pro laptop (BOOTX64.cfg for Qubes 4.0.1)

389 views
Skip to first unread message

Daniil Travnikov

unread,
Feb 26, 2019, 3:37:29 PM2/26/19
to qubes-users
Hi everyone and especially those who useing Oryx Pro with 4.0.1 Release :)

Tell me please what config variations I must try in BOOTX64.cfg (or maybe somewhere else) to successfuly install Qubes?


Now with .iso (dd via Rufus) without any changes I got this problem:
https://drive.google.com/open?id=1y38UJKq1ucuZIKtvlHLFyMKbMhYO3VBo


Also tried different options in BOOTX64.cfg.


Example 1:
[qubes-verbose]
options=console=vga efi=no-rs

(here I changed 'efi=attr=uc' on efi=no-rs') and got this:
https://drive.google.com/open?id=1ms_p53vRnSMy7OTjYFuSBlMH2ULvypLh


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

(here I added 'nouveau.modeset=0') and got this:
https://drive.google.com/file/d/1zGI53XZ6f-8BoX28XueuuAmDQmFVf4FT/view


Maybe I missing something or doing something wrong?

Will appriciate to any help.

Daniil Travnikov

unread,
Feb 27, 2019, 6:57:59 PM2/27/19
to qubes-users
Today I tried to change the xen configuration on a USB media. I tried to put in BOOTX64.cfg line 'modprobe.blacklist=nouveau' and change also some options but without any success because of .iso format file which has Write protection.

I got this information from here: https://www.engetsu-consulting.com/blog/installing-qubes-4-0-on-laptops-with-nvidia-gpus-that-do-not-support-the-nouveau-driver

And in my case VIM editor could not save any changes in .iso file.

Also I tried to change xen configuration directly in an .iso image from here: https://www.qubes-os.org/doc/uefi-troubleshooting/

My steps:

1. [user@dom0 Desktop]$ sudo parted Qubes-R4.0.1-x86_64.iso unit B print
Model: (file)
Disk /home/user/Desktop/Qubes-R4.0.1-x86_64.iso: 4693426176B
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
2 530432B 29591551B 29061120B primary fat16 esp

2. [user@dom0 Desktop]$ sudo losetup -o 524288 --sizelimit 30562304 /dev/loop13 Qubes-R4.0.1-x86_64.iso

3. [user@dom0 Desktop]$ sudo mount /dev/loop13 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/loop13,
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try
dmesg | tail or so.

[user@dom0 Desktop]$ sudo dmesg | tail
[ 1006.443849] audit: type=1106 audit(1551309604.284:192): pid=3760 uid=0 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
[ 1006.443913] audit: type=1104 audit(1551309604.284:193): pid=3760 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
[ 1046.908659] audit: type=1123 audit(1551309644.748:194): pid=3777 uid=1000 auid=1000 ses=2 msg='cwd="/home/user/Desktop" cmd=6D6F756E74202F6465762F6C6F6F703133202F6D6E74 terminal=pts/4 res=success'
[ 1046.908881] audit: type=1110 audit(1551309644.749:195): pid=3777 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
[ 1046.911708] audit: type=1105 audit(1551309644.751:196): pid=3777 uid=0 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
[ 1046.994127] audit: type=1106 audit(1551309644.834:197): pid=3777 uid=0 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
[ 1046.994244] audit: type=1104 audit(1551309644.834:198): pid=3777 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
[ 1051.322813] audit: type=1123 audit(1551309649.163:199): pid=3785 uid=1000 auid=1000 ses=2 msg='cwd="/home/user/Desktop" cmd="dmesg" terminal=pts/4 res=success'
[ 1051.322918] audit: type=1110 audit(1551309649.163:200): pid=3785 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'
[ 1051.324299] audit: type=1105 audit(1551309649.164:201): pid=3785 uid=0 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/4 res=success'


So I am stuck on the 3 step where I must mount the loop device. Actually i don't know do I need to do this, because I even don't know about success of this steps on the end. I just need to change some files in .iso image and I don't know how to do this. When I am just extracting and replace those files and packing back the .iso - it is new .iso which not works (I showed the screenshots in first message if this topic).


Could anybody help with this problem?

awokd

unread,
Feb 27, 2019, 10:19:09 PM2/27/19
to qubes...@googlegroups.com
Daniil Travnikov:
> Today I tried to change the xen configuration on a USB media. I tried to put in BOOTX64.cfg line 'modprobe.blacklist=nouveau' and change also some options but without any success because of .iso format file which has Write protection.
>
> I got this information from here: https://www.engetsu-consulting.com/blog/installing-qubes-4-0-on-laptops-with-nvidia-gpus-that-do-not-support-the-nouveau-driver
>
> And in my case VIM editor could not save any changes in .iso file.

Don't edit the ISO directly. dd or cp it to a USB drive (not partition),
then follow the steps and mount the second partition and edit files in
there.

Message has been deleted

Daniil Travnikov

unread,
Feb 28, 2019, 5:18:57 AM2/28/19
to qubes-users
On Wednesday, February 27, 2019 at 10:19:09 PM UTC-5, awokd wrote:
> Don't edit the ISO directly. dd or cp it to a USB drive (not partition),
> then follow the steps and mount the second partition and edit files in
> there.
Thank you very much for your answer and for your help!

Ok, that's what I am doing step by step:

1. I write .iso via Rufus in DD mode.

2. When I am trying to open file BOOTX64.cfg:
[user@dom0 BOOT]$ sudo nano BOOTX64.cfg

I can't save any edits in files and after open nano editor I see this below:
[ File 'BOOTX64.cfg' is unwritable ]

What am I doing wrong?

unman

unread,
Feb 28, 2019, 9:04:05 AM2/28/19
to qubes-users
You are trying to write to an iso file, which is a read only file
system. (It's an image of a CD/DVD)

As awokd has suggested, you need to copy the files to a USB drive, or
similar, and edit them there. Then create a new iso image and boot from
that.

Daniil Travnikov

unread,
Feb 28, 2019, 9:26:31 AM2/28/19
to qubes-users
On Thursday, February 28, 2019 at 9:04:05 AM UTC-5, unman wrote:
> You are trying to write to an iso file, which is a read only file
> system. (It's an image of a CD/DVD)
>
> As awokd has suggested, you need to copy the files to a USB drive, or
> similar, and edit them there. Then create a new iso image and boot from
> that.

In first step: "1. I write .iso via Rufus in DD mode." I already copied this files on USB. It means that when I open usb flash drive I see not .iso file, I see files and folders which I can't edit because it is not writable.

I don't know, maybe it is the problem of DD mode writing of .iso, but I tried
also usual .iso mode in Rufus and when I am changing anything then I got this:

https://drive.google.com/file/d/1zGI53XZ6f-8BoX28XueuuAmDQmFVf4FT/view - 8GB flash drive
https://drive.google.com/file/d/1ms_p53vRnSMy7OTjYFuSBlMH2ULvypLh/view - 1TB SSD drive


Or you mean another method of copy files to USB drive?

brenda...@gmail.com

unread,
Feb 28, 2019, 10:33:08 AM2/28/19
to qubes-users
On Thursday, February 28, 2019 at 9:26:31 AM UTC-5, Daniil Travnikov wrote:
> On Thursday, February 28, 2019 at 9:04:05 AM UTC-5, unman wrote:
> > You are trying to write to an iso file, which is a read only file
> > system. (It's an image of a CD/DVD)
> >
> > As awokd has suggested, you need to copy the files to a USB drive, or
> > similar, and edit them there. Then create a new iso image and boot from
> > that.
>
> In first step: "1. I write .iso via Rufus in DD mode." I already copied this files on USB. It means that when I open usb flash drive I see not .iso file, I see files and folders which I can't edit because it is not writable.

The file system on the USB stick is still ISO 9660 (not FAT or ext2 or NTFS). That file system does not support updates to files.

From wikipedia:
> ISO 9660 is by design a read-only, pre-mastered file system ... all the data has to be written in one go or "session" to the medium

In order to update files, you need to extract the tree to a file system that supports updating files, then remaster the image, then use that image to DD to the USB.

Brendan

awokd

unread,
Feb 28, 2019, 5:30:38 PM2/28/19
to qubes...@googlegroups.com
brenda...@gmail.com wrote on 2/28/19 3:33 PM:
Thought I was able to edit them directly on the USB drive in the past.
Has that changed, or am I confused?

brenda...@gmail.com

unread,
Feb 28, 2019, 8:41:22 PM2/28/19
to qubes-users
On Thursday, February 28, 2019 at 5:30:38 PM UTC-5, awokd wrote:
> br...r@gmail.com wrote on 2/28/19 3:33 PM:

> > From wikipedia:
> >> ISO 9660 is by design a read-only, pre-mastered file system ... all the data has to be written in one go or "session" to the medium
> >
> > In order to update files, you need to extract the tree to a file system that supports updating files, then remaster the image, then use that image to DD to the USB.
> >
> Thought I was able to edit them directly on the USB drive in the past.
> Has that changed, or am I confused?

If you:

a) use dd to image an iso onto a flash drive, you now have an iso 9660 file system. It's not meant to be written ad-hoc from mount in an OS.
If, instead, you:
b) extract the files from the ISO to an appropriate r/w file system partition on a flash drive (FAT, eFAT, ext3, NTFS) then you can add/modify/delete files to your heart's content.

However, with the latter approach, the mastered-for-ISO boot chain might only be expecting an ISO 9660 file system and therefore fail (in some cases) if it's not running off of one. Hence why there are often very detailed settings required to properly write some ISOs to flash drives and still end up with bootable media.

Brendan

Daniil Travnikov

unread,
Mar 4, 2019, 12:28:17 PM3/4/19
to qubes-users
Finally I did it! Thanks to those who responded and did not remain indifferent to my situation.

Especially,

'Shahin Azad' who gave me this url-instruction: https://www.engetsu-consulting.com/blog/installing-qubes-4-0-on-laptops-with-nvidia-gpus-that-do-not-support-the-nouveau-driver

and

'0brand' who told me how to use this instruction in right way.

This is my steps:

1. I copied .iso-file to linux system.
2. Opened terminal and start command 'sudo su -'
3. 'chmod u+w /path/to/file.iso'
4. 'nano vim /path/to/file.iso'
5. Edit those lines which described in url: https://www.engetsu-consulting.com/blog/installing-qubes-4-0-on-laptops-with-nvidia-gpus-that-do-not-support-the-nouveau-driver
6. Saved file and write on flash drive in DD-mode.


I know, maybe this is not that easiest way, but this worked for me in my case.

Mike Gifford

unread,
Oct 14, 2020, 10:08:09 AM10/14/20
to qubes-users
I can open the .iso with "nano vim" but ultimately that doesn't get me to the config file /EFI/BOOT/BOOTX64.cfg that is described but not named in the following post.  

I'm also rather concerned why there are two "Original Installer ISO" files described here. Why doesn't he just list the filenames?

I'm also having difficult saving files to the .iso

Mike

load...@gmail.com

unread,
Oct 15, 2020, 3:45:12 PM10/15/20
to qubes-users
Hi,

I can open the .iso with "nano vim" but ultimately that doesn't get me to the config file /EFI/BOOT/BOOTX64.cfg that is described but not named in the following post.  

If you trying to change .iso-file with via opening in 'vim' or any other editor, then you don't need to search bootx64.cfg. You can just find those lines which you need to edit via CTRL-F or other command for you editor to find the lines which you need to change.
 

I'm also rather concerned why there are two "Original Installer ISO" files described here. Why doesn't he just list the filenames?

Actually I don't remember if there any 2 .iso-files. You could printscreen this to clarify this moment.
 

I'm also having difficult saving files to the .iso
 
If you did the command:
'chmod u+w /path/to/file.iso'
and it didn't help you, then you can try to use any live-system of any Linux system like Fedora/Ubuntu/Debian where it is worked always correctly for me. For example at first time on Windows it did not worked for me, but about month ago I tried the same Notepad++ on Windows and it worked. I don't know what changed. I stopped looking for answers if something concerns the Windows OS :)
Reply all
Reply to author
Forward
0 new messages