HCL - Samsung Chronos series 7 - model 700ZA5 - R3.1 RC2

123 views
Skip to first unread message

jerome....@gmail.com

unread,
Jan 29, 2016, 3:54:25 AM1/29/16
to qubes-users
Hi,

Fresh install Qubes R3.1 RC2. I haven t tested everything yet but it looks good.
I attached my detailed HCL report.

I had the well know freeze at first boot while setting the network. So i choose to create the default vm myself. There is a checkbox for this.

I found this post from marek to create the defaults VM and everything worked :

The sys-net and sys-firewall vms where created with the fedora template. I m a debian guy but i assume that these too should be fedora based :/ Am i wrong?

I m still looking for the first boot script in order to verify that no other things are done in the recent version.

One other way around would be to let the system freeze while setting the network, reboot in rescue mode, chroot in /mnt/sysimage and detach the device from the netvm.
In my case the wireless card 02:00.0
-->  qvm-pci -d --offline-mode sys-net 02:00.0

I haven t tested this yet, but it should work. I have dettached my wireless card plenty of times while looking to make the wireless card work using the "rescue" method.

Finally got it to work thanks to the PCI permissive mode :

Thanks a lot to this users list and to marek for the help provided.
If someone could point me the first boot script, it would be greatly appreciated.

It seems that a lot of people have the freeze problem with BCM wireless card. If we can choose to not attach the card at first boot, that could really help to get things working and maybe point new users to the "permissive" workaround. Qubes seems to be installed primary on laptops.


cheers,
Samsung Chronos 7.cpio.gz
Samsung Chronos 7.yml

Marek Marczykowski-Górecki

unread,
Jan 31, 2016, 5:53:14 PM1/31/16
to jerome....@gmail.com, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Fri, Jan 29, 2016 at 12:54:25AM -0800, jerome....@gmail.com wrote:
> Hi,
>
> Fresh install Qubes R3.1 RC2. I haven t tested everything yet but it looks
> good.
> I attached my detailed HCL report.
>
> I had the well know freeze at first boot while setting the network. So i
> choose to create the default vm myself. There is a checkbox for this.
>
> I found this post from marek to create the defaults VM and everything
> worked :
> https://groups.google.com/d/msg/qubes-devel/aHEDUwsJ4IY/Ko7jqaRJxw0J
>
> The sys-net and sys-firewall vms where created with the fedora template. I
> m a debian guy but i assume that these too should be fedora based :/ Am i
> wrong?

Theoretically you can also use Debian template for that, but you'll need
to install linux-firmware package at least (as most wifi cards requires
firmware blobs, unfortunately).

> I m still looking for the first boot script in order to verify that no
> other things are done in the recent version.
>
> One other way around would be to let the system freeze while setting the
> network, reboot in rescue mode, chroot in /mnt/sysimage and detach the
> device from the netvm.
> In my case the wireless card 02:00.0
> --> qvm-pci -d --offline-mode sys-net 02:00.0
>
> I haven t tested this yet, but it should work. I have dettached my wireless
> card plenty of times while looking to make the wireless card work using the
> "rescue" method.
>
> Finally got it to work thanks to the PCI permissive mode :
> https://www.qubes-os.org/doc/assigning-devices/
>
> Thanks a lot to this users list and to marek for the help provided.
> If someone could point me the first boot script, it would be greatly
> appreciated.
>
> It seems that a lot of people have the freeze problem with BCM wireless
> card. If we can choose to not attach the card at first boot, that could
> really help to get things working and maybe point new users to the
> "permissive" workaround. Qubes seems to be installed primary on laptops.

Generally it is possible to simply not create any VMs there. Then create
them either manually, or using management stack (the same way as
firstboot does it). And adjust some settings then. Creating VMs using
management stack is quite easy (but I think not documented yet...):
1. Choose what you want to use and enable using `qubesctl top.enable`
tool. Available options:
- qvm.sys-net, qvm.sys-firewall - standard sys-net and sys-firewall
VMs, required for other VMs options
- qvm.sys-usb - USB VM
- qvm.work, qvm.personal, qvm.vault, qvm.untrusted - standard AppVMs
- qvm.sys-whonix, qvm.anon-whonix - Whonix gateway and workstation

You can enable multiple of them in a single command call:
qubesctl top.enable qvm.sys-net qvm.sys-firewall qvm.work qvm.personal

2. Apply the configuration (create selected VMs):

qubesctl stat.highstate

@Axon, any idea where to put that in the documentation? User FAQ?
Separate page about boot/installation related troubleshooting? Somewhere
else? Could you put that info there?


Another thing is an option to simply not start the VMs in case of such
freeze problems.
https://github.com/QubesOS/qubes-issues/issues/1709

- --
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?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWrpBSAAoJENuP0xzK19csS78H/1T7GD7VCJKTdSjB2zlbMSRC
XB3Ivu6ABykTMCkPX8BKAsgn4Ukpy3i0ztm1s/ja/fan5J/gDG10pLHnXuYrR1xe
okGzOPbQRZ+64n8oxdZ0zXHMhlnzqArwfhZUf4oBPEe0wJBd5mIThxBwWct8zqwW
w5wCe3Rk/HXpDUMlS3peyOFxZ98st5PUUaNldluvmsAfKKsVTlFhd36YxhLVXL9E
O5B2hKXC0Tfo1CJPqLPyd/dL0usq1ZmufYordgvucQSzVxwoXAdUiN6WHJ2R9Vg/
bZnw26JzQ2iTOVS+XQ1LzbWl9ZpvSSuaYkB/8JVhR6HWxZHn4hxZ6TIdj8/6TAw=
=Bcsw
-----END PGP SIGNATURE-----

jerome....@gmail.com

unread,
Feb 1, 2016, 2:06:59 PM2/1/16
to qubes-users, jerome....@gmail.com


On Sunday, January 31, 2016 at 11:53:14 PM UTC+1, Marek Marczykowski-Górecki wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Fri, Jan 29, 2016 at 12:54:25AM -0800, jerome....@gmail.com wrote:
> Hi,
>
> Fresh install Qubes R3.1 RC2. I haven t tested everything yet but it looks
> good.
> I attached my detailed HCL report.
>
> I had the well know freeze at first boot while setting the network. So i
> choose to create the default vm myself. There is a checkbox for this.
>
> I found this post from marek to create the defaults VM and everything
> worked :
> https://groups.google.com/d/msg/qubes-devel/aHEDUwsJ4IY/Ko7jqaRJxw0J
>
> The sys-net and sys-firewall vms where created with the fedora template. I
> m a debian guy but i assume that these too should be fedora based :/ Am i
> wrong?

Theoretically you can also use Debian template for that, but you'll need
to install linux-firmware package at least (as most wifi cards requires
firmware blobs, unfortunately).


That what i thought first. I downloaded my firmware for the debian template. But then , it occurs to me that sys-net and sys-firewall are very specific vms for the system and that there could be some scripts to interract with dom0.(some examples are wireless settings and updating dom0 trough sys-firewall) So i got back to fedora. Is it safe to use debian template for both? No problem for setting wireless settings manually but i would like to be able to update dom0. Actually, i m not even sure that it currently works with the fedora template. I have some errors...
Thank you a lot for this.

Marek Marczykowski-Górecki

unread,
Feb 1, 2016, 2:08:55 PM2/1/16
to jerome....@gmail.com, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Yes, theoretically both sys-firewall and sys-net should work also using
Debian template.

- --
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?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWr61BAAoJENuP0xzK19csLuIH+wbPiaAAfGAuk6//MCPFpgZP
HmWmd1QPxL/YoedKdRn+CJZMrrXPVS78KvZJ0PBLX2OoqWXtA/z1tzgapdQBNiAh
6dDgkTRpICkOtYUdAuCRL13KrCYuqLIhkK9JH3CoIXMJJh0RCgc6lb3cHLhUTIWX
VtasVO7d3Mb36XKvrAqfwbZxbFdMxuKs8y90fLJF/uw4aT7WoJqT5D+hCIXyfboh
JL2CGlSvu5e/8uGAmNsogxGqoM208gVfy7MuRvZ7U9cnLievCJhFzHTrGuPMsHOd
cYK9reQydT03a6soQalKacx6YtQjd3dfD2CkL876ts9oraKZUcPTNjuYuvOzcfg=
=k8hG
-----END PGP SIGNATURE-----
Reply all
Reply to author
Forward
0 new messages