About using ISO compiled from source codes

[Object Ho]

Hello all, 

My team just compiled Qubes with its source codes and met some issues. 

We got an ISO of 1.8GB when compiling on Fedora 17, and an ISO of 2.1 GB when compiling on Fedora 20, does this matter?

And then when we boot from those ISOs, we enter a command line interface rather than a GUI one. Is it possible to switch to GUI?

Thanks~

[Marek Marczykowski-Górecki]

On 04.01.2014 16:31, Object Ho wrote:
> Hello all,
>
> My team just compiled Qubes with its source codes and met some issues.
>
> We got an ISO of 1.8GB when compiling on Fedora 17, and an ISO of 2.1 GB
> when compiling on Fedora 20, does this matter?

Strange, I've compiled the sources on fc17, fc18 and fc19 and got the same in
all cases. Qubes builder uses chroot environment with build "sandbox" to have
always the same build environment, it the base system shouldn't matter...

In any case, 2.1GB seems more correct.

> And then when we boot from those ISOs, we enter a command line interface
> rather than a GUI one. Is it possible to switch to GUI?

Do you mean text-based installer? It is called as a fallback if GUI fails, so
check why the GUI installer failed (something about video drivers?).

--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

[Yu Chen]

hi,Marek:

  The machine is lenovo T420, which can run the default qubes B2R3.iso from sourceforge.

  I build the git repos from marmarek repo, not joanna or qubes-r2 repo.  I also modified builder.conf by adding NO_CHCEK=1 NO_SIGN=1 DEBUG=1  VERBOSE=2

  after build the ISO, burn it to usb disk, and run usb disk, I found I can not go into GUI installer interface. 

  I check the log info in /tmp, the root cause is X server. from /tmp/X.log

====================

....

X.Org X Server 1.13.3

.....

[22.703]     (WW) Failed to open protocol names file /usr/lib64/xorg/protocol.txt

Fatal server error:

[22.703]   xf86OpenConsole: VT_ACTIVE failed: Input/output error

[22.703]   

[22.703]   [EE]

I also check the EE information in X.log

=================

[EE] AIGLX error: dlopen of /usr/lib64/dri/i965_dri.so failed (....No such file or directory)

[EE] AIGLX : reverting to software rendering

[EE] AIGLX error: dlopen of /usr/lib64/dri/swrast_dri.so failed (....No such file or directory)

[EE] GLX : could not load  software renderer

....

I found there /usr/lib64/dri is empty in usb disk, but in qubes-builder/chroot-fc18/usr/lib64/dri/ contains i965_dri.so and swrast_dir.so

I think maybe  we miss dri/* when building ISO

Any advice?

在 2014年1月5日星期日UTC+8上午2时49分01秒，Marek Marczykowski-Górecki写道：

[71951...@gmail.com]

Hello :
    I want to build qubes from sources on fedora 18 and refer to the''http://wiki.qubes-os.org/trac/wiki/QubesBuilder''.Now I have run the "make get-sources"successfly,but when "make qubes" I got the following:
   Iintializing RPM database...
   -> Installing core RPM packages...
   http://ftp6.sjtu.edu.cn/fedora/linux/releases/18/Everything/x86_64/os/Packages/m/MAKEDEV-3.24-11.fc18.x86_64.rpm: [Errno 14] curl#7 - "Failed to connect to              2001:da8:8000:6023::230: Network is unreachable"

  Trying other mirror
  awk: fatal: cannot open file `/etc/fstab' for reading (NO such file or directory)
  /usr/lib/dracut/modules.d/95rootfs-block/module-setup.sh: line 5: /etc/fstab: No such file or directory
  E: Directories consolefonts, consoletrans, keymaps, unimaps not found. Please inform us about the issue including your OS name and version.
  /usr/lib/dracut/modules.d/99base/dracut-lib.sh: line 80: /proc/cmdline: No such file or directory
  Failed to open /dev/urandom: No such file or directory
  groupadd：GID “0”exited
  make[1]: *** [/home/wsn/download/qubes-builder/chroot-fc18/home/user/.prepared_base] error 1
  make[1]:leave catalog “/home/wsn/download/qubes-builder”
  make: *** [vmm-xen-dom0] error 1
  I edited the file "builder.conf"and set "GIT_SUBDIR=joanna""NO_SIGN=1".
 Do I should use another fedora distro?


Grettings

Wsn

[Marek Marczykowski-Górecki]

Make should be called as normal user, which have unlimited sudo access. Did
you done that?

[Marek Marczykowski-Górecki]

On 03.05.2014 07:38, 王淑妮 wrote:
> Hello:
> When I did the "make desktop-linux-kde ,I got the followings:
> make[1]: Entering directory `/home/wsn/public/qubes-builder'
> -> Building desktop-linux-kde (kde-baseapps/kde-baseapps.spec) for fc18
> dom0 (logfile: build-logs/desktop-linux-kde-dom0-fc18.log)
> --> build failed!
> Getting requirements for kde-baseapps/kde-baseapps.spec
> --> Already installed : gcc-c++-4.7.2-8.fc18.x86_64
> --> desktop-file-utils-0.21-1.fc18.x86_64
> --> libtidy-devel-0.99.0-26.20091203.fc18.x86_64
> --> Already installed : 1:pkgconfig-0.27-1.fc18.x86_64
> --> Already installed : glib2-devel-2.34.2-2.fc18.x86_64
> --> strigi-devel-0.7.8-1.fc18.x86_64
> Error: No Package found for kdelibs4-devel >= 4.12.3

Current desktop-linux-kde master branch is designed for fc20 dom0. You can
change it in builder.conf (I'll update the defaults soon...).

> make[2]: *** [dist-build-dep] Error 1
> make[2]: Leaving directory `/home/wsn/public/qubes-builder'
> make[1]: *** [packages] Error 1
> make[1]: Leaving directory `/home/wsn/public/qubes-builder'
> make: *** [desktop-linux-kde-dom0] Error 1
> But I could "make desktop-linux-xfce4 " no errors!
>
> Others when"make linux-template-builder":
> Downloading Packages:
> http://linuxdownload.adobe.com/linux/x86_64/flash-plugin-11.2.202.356-release.x86_64.rpm:
> [Errno 12] Timeout on
> http://linuxdownload.adobe.com/linux/x86_64/flash-plugin-11.2.202.356-release.x86_64.rpm:
> (28, '')
> Trying other mirror.
>
> Error Downloading Packages:
> flash-plugin-11.2.202.356-release.x86_64: Downloaded package
> flash-plugin-11.2.202.356-release.x86_64, from adobe-linux-x86_64, but it
> was invalid.
> flash-plugin-11.2.202.356-release.x86_64: [Errno 256] No more mirrors to
> try.
> make[1]: *** [rpms] Error 1.
> while I could downloaded the package,if I could use "sudo chroot
> chroot-fc18 rpm -i flash-plugin-11.2.202.356-release.x86_64.rpm"to install
> it .

Have you checked the package checksum and signature? This can be what "but it
was invalid" message was about.

[Marek Marczykowski-Górecki]

On 03.05.2014 15:21, 王淑妮 wrote:
> Does it means that i should remove whole chroot-fc18 directory and build
> all components again after editing the "builder.conf"to set the Default
> DIST_DOM0 : fc20?(Now i have set GIT_SUBDIR=marmarek , NO-SIGH Default:1,
> BRANCH Default: master,it's ok? )

You do not need to remove chroot-fc18 (unless you want to save some disk), but
yes, you need to rebuild all components. You can use "qubes-dom0" meta target
to rebuild only dom0 ones.

[Marek Marczykowski-Górecki]

On 03.05.2014 16:06, 王淑妮 wrote:
>
>
> Greetings
> wsn
>
>
> 2014-05-03 21:23 GMT+08:00 Marek Marczykowski-Górecki <
> marm...@invisiblethingslab.com>:

>
>> On 03.05.2014 15:21, 王淑妮 wrote:
>>> Does it means that i should remove whole chroot-fc18 directory and build
>>> all components again after editing the "builder.conf"to set the
>> Default
>>> DIST_DOM0 : fc20?(Now i have set GIT_SUBDIR=marmarek , NO-SIGH Default:1,
>>> BRANCH Default: master,it's ok? )
>>
>> You do not need to remove chroot-fc18 (unless you want to save some disk),
>> but
>> yes, you need to rebuild all components. You can use "qubes-dom0" meta
>> target
>> to rebuild only dom0 ones.

> I have found that when i called "make qubes",the dom0 is still fc18
> after editing the "builder.conf "to set the DIST -DOMO Default : fc20!
> Should i edit the file "Makefile"and set DIST_DOM0 ?= fc20(I have edited it
> and set GIT_SUBDIR ?= marmarek )

If you set "DIST -DOM0", it isn't surprising... The correct setting is
"DIST_DOM0". You should set:
DIST_DOM0=fc20

PS Keep the reply on mailing list.
PPS Do not top-post.

[Marek Marczykowski-Górecki]

On 04.05.2014 12:57, 王淑妮 wrote:
> when build the linux-dom0-updates,linux-yum and
> vmm-xen-windows-pvdrivers,it seems do nothing! Right?

That's correct.

>
> got followings:
> [wsn@localhost qubes-builder]$ make linux-dom0-updates
> [wsn@localhost qubes-builder]$
> [wsn@localhost qubes-builder]$ make linux-yum
> [wsn@localhost qubes-builder]$
> [wsn@localhost qubes-builder]$ make vmm-xen-windows-pvdrivers

> make[1]: Entering directory `/home/wsn/public/qubes-builder'

> make[1]: Leaving directory `/home/wsn/public/qubes-builder'

> [wsn@localhost qubes-builder]$

[Marek Marczykowski-Górecki]

On 05.05.2014 15:37, 王淑妮 wrote:
> I finished the "make iso"and then got a 1.5G ISO.it could be install the
> xen virtual machine?

1. Please keep the conversation on the mailing list.
2. Read the http://wiki.qubes-os.org/trac/wiki/InstallationGuideR2rc1, there
is an answer for your question.