Asus U35JC - Qubes
Hardware info on main page.
Hints:
dom0 to clipboard trick:
$ xrandr > /var/run/qubes/qubes-clipboard.bin $ echo "dom0" > /var/run/qubes/qubes-clipboard.bin.source
ok.
Boot key: Esc,
Links
Qubes, acpi_call, acpi_call_GUI_systemd,
Qubes-related links: Qubes OS Cheat Sheet, qubes-wallpapers, Setting up Qubes, Screenshots in Qubes, qubes-app-linux-yubikey, Building Qubes OS 3.0 ISO,
Work log
2021-12-11: I re-created this page on my self-hosted web server.
2015-10-08: Qubes 3.0 - I see lots of lines like these in /var/log/messages:
Oct 7 23:37:15 dom0 kernel: [ 3.334260] psmouse serio4: elantech: Synaptics capabilities query result 0x7e, 0x13, 0x0d. Oct 7 23:37:15 dom0 kernel: [ 3.439101] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio4/input/input11 Oct 7 23:37:15 dom0 kernel: [ 4.034594] pciehp 0000:00:1c.5:pcie04: Card not present on Slot(5) Oct 7 23:37:15 dom0 kernel: [ 4.038625] pciehp 0000:00:1c.5:pcie04: Card present on Slot(5)
(ignore the first two lines, they are just for context)
Oct 7 23:37:15 dom0 kernel: [ 13.933536] pciehp 0000:00:1c.5:pcie04: Card present on Slot(5) Oct 7 23:37:15 dom0 kernel: [ 13.957595] pciehp 0000:00:1c.5:pcie04: Card not present on Slot(5) Oct 7 23:37:15 dom0 kernel: [ 13.960610] pciehp 0000:00:1c.5:pcie04: Failed to check link status Oct 7 23:37:15 dom0 kernel: [ 13.960663] pciehp 0000:00:1c.5:pcie04: No adapter on slot(5) Oct 8 21:17:38 dom0 kernel: [78042.673830] pciehp 0000:00:1c.5:pcie04: Card not present on Slot(5) Oct 8 21:17:38 dom0 kernel: [78042.677946] pciehp 0000:00:1c.5:pcie04: Card present on Slot(5) Oct 8 21:17:38 dom0 kernel: [78042.702035] pciehp 0000:00:1c.5:pcie04: Card not present on Slot(5) Oct 8 21:17:38 dom0 kernel: [78042.706129] pciehp 0000:00:1c.5:pcie04: Card present on Slot(5)
not sure what it is about. lspci says
[tingo@dom0 ~]$ sudo lspci -s 00:1c.5 -vnn 00:1c.5 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 [8086:3b4c] (rev 06) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 53 Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: 0000a000-0000afff Memory behind bridge: d3800000-d4bfffff Prefetchable memory behind bridge: 00000000d7700000-00000000d78fffff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device [1043:1017] Capabilities: [a0] Power Management version 2 Kernel driver in use: pcieport Kernel modules: shpchp
ok, something about acpi then.
[tingo@dom0 ~]$ apropos shpchp shpchp: nothing appropriate. [tingo@dom0 ~]$ lsmod | grep shpchp shpchp 37047 0
ok. Actually, shpchp is the "Standard Hot Plug PCI Controller driver".
2015-10-08: Qubes 3.0 - PCI devices
[tingo@dom0 ~]$ lspci 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 18) 00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 18) 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18) 00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06) 00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06) 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06) 00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06) 00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 06) 00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6) 00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 06) 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 06) 00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 06) 01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce 310M] (rev a2) 03:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01) ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 05) ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 05) ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 05) ff:02.1 Host bridge: Intel Corporation 1st Generation Core i3/5/7 Processor QPI Physical 0 (rev 05) ff:02.2 Host bridge: Intel Corporation 1st Generation Core i3/5/7 Processor Reserved (rev 05) ff:02.3 Host bridge: Intel Corporation 1st Generation Core i3/5/7 Processor Reserved (rev 05)
ok.
2015-10-08: Qubes 3.0 - disk setup. physical volumes:
[tingo@dom0 ~]$ sudo pvs PV VG Fmt Attr PSize PFree /dev/sdb2 qubes_dom0 lvm2 a-- 28.48g 0
volume groups:
[tingo@dom0 ~]$ sudo vgs VG #PV #LV #SN Attr VSize VFree qubes_dom0 1 2 0 wz--n- 28.48g 0
logical volumes:
[tingo@dom0 ~]$ sudo lvs LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert root qubes_dom0 -wi-ao---- 25.58g swap qubes_dom0 -wi-ao---- 2.90g
ok. dmsetup:
[tingo@dom0 ~]$ sudo dmsetup info Name: snapshot-fd00:1184685-fd00:1184121 State: ACTIVE Read Ahead: 256 Tables present: LIVE Open count: 3 Event number: 0 Major, minor: 253, 2 Number of targets: 1 Name: qubes_dom0-swap State: ACTIVE Read Ahead: 256 Tables present: LIVE Open count: 2 Event number: 0 Major, minor: 253, 1 Number of targets: 1 UUID: LVM-4WyB7cC33wxfyJh8kfo69fJYcQSdN6ZZCUuItJOqceveXS5sXr4V4zg6rUwsI9cm Name: qubes_dom0-root State: ACTIVE Read Ahead: 256 Tables present: LIVE Open count: 1 Event number: 0 Major, minor: 253, 0 Number of targets: 1 UUID: LVM-4WyB7cC33wxfyJh8kfo69fJYcQSdN6ZZrNcjbl9p8gdef32gKIurx0u7qeKOg4gJ
ok. swap and df output:
[tingo@dom0 ~]$ swapon -s Filename Type Size Used Priority /dev/dm-1 partition 3039228 1580 -1 [tingo@dom0 ~]$ df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 3.2G 0 3.2G 0% /dev tmpfs 3.2G 1.9M 3.2G 1% /dev/shm tmpfs 3.2G 8.9M 3.2G 1% /run tmpfs 3.2G 0 3.2G 0% /sys/fs/cgroup /dev/mapper/qubes_dom0-root 26G 12G 13G 48% / tmpfs 3.2G 36K 3.2G 1% /tmp xenstore 3.2G 128K 3.2G 1% /var/lib/xenstored /dev/sdb1 477M 132M 316M 30% /boot
ok.
2015-10-06: in Xubuntu I used the acpi_call module and this to disable the nVidia card:
sudo echo '\_SB.PCI0.PEG1.GFX0._OFF' > /proc/acpi/call
but I need to compile the acpi_call module first.
2015-10-06: Qubes 3.0 - try to disable the nouveau driver by changing a line in /etc/default/grub file. before change:
[tingo@dom0 ~]$ grep GRUB_CMDLINE_LINUX /etc/default/grub GRUB_CMDLINE_LINUX="rd.lvm.lv=qubes_dom0/root vconsole.font=latarcyrheb-sun16 rd.lvm.lv=qubes_dom0/swap $([ -x /usr/sbin/rhcrashkernel-param ] && /usr/sbin/rhcrashkernel-param || :) rhgb quiet"
after change:
[tingo@dom0 ~]$ grep GRUB_CMDLINE_LINUX /etc/default/grub GRUB_CMDLINE_LINUX="rd.lvm.lv=qubes_dom0/root vconsole.font=latarcyrheb-sun16 rd.lvm.lv=qubes_dom0/swap $([ -x /usr/sbin/rhcrashkernel-param ] && /usr/sbin/rhcrashkernel-param || :) rhgb quiet noveau.modeset=0 rd.driver.blacklist=noveau"
and then regenerate grub via
[tingo@dom0 ~]$ sudo grub2-mkconfig -o /boot/grub2/grub.cfg Generating grub.cfg ... Found theme: /boot/grub2/themes/system/theme.txt Found linux image: /boot/vmlinuz-3.19.8-100.fc20.x86_64 Found initrd image: /boot/initramfs-3.19.8-100.fc20.x86_64.img Found linux image: /boot/vmlinuz-3.18.17-6.pvops.qubes.x86_64 Found initrd image: /boot/initramfs-3.18.17-6.pvops.qubes.x86_64.img Found linux image: /boot/vmlinuz-3.12.40-2.pvops.qubes.x86_64 Found initrd image: /boot/initramfs-3.12.40-2.pvops.qubes.x86_64.img Found linux image: /boot/vmlinuz-3.11.10-301.fc20.x86_64 Found initrd image: /boot/initramfs-3.11.10-301.fc20.x86_64.img done
good. An alternative way would be to create the file /etc/modprobe.d/noveau-disable.conf with the line blacklist noveau in. Verify that the module is loaded before rebooting:
[tingo@dom0 ~]$ lsmod | grep nouveau nouveau 1376846 0 mxm_wmi 12865 1 nouveau ttm 88933 1 nouveau i2c_algo_bit 13257 2 i915,nouveau drm_kms_helper 107014 2 i915,nouveau drm 313718 6 ttm,i915,drm_kms_helper,nouveau wmi 18820 2 mxm_wmi,nouveau video 24067 2 i915,nouveau
oops, I spelled it incorrectly. after fixing it
[tingo@dom0 ~]$ grep GRUB_CMDLINE_LINUX /etc/default/grub GRUB_CMDLINE_LINUX="rd.lvm.lv=qubes_dom0/root vconsole.font=latarcyrheb-sun16 rd.lvm.lv=qubes_dom0/swap $([ -x /usr/sbin/rhcrashkernel-param ] && /usr/sbin/rhcrashkernel-param || :) rhgb quiet nouveau.modeset=0 rd.driver.blacklist=nouveau"
and regenerated grub. All that is needed now is a reboot to test it. Ok, after a reboot, the nouveau module is still loaded:
[tingo@dom0 ~]$ lsmod | grep nouveau nouveau 1376846 0 ttm 88933 1 nouveau mxm_wmi 12865 1 nouveau i2c_algo_bit 13257 2 i915,nouveau drm_kms_helper 107014 2 i915,nouveau drm 313718 6 ttm,i915,drm_kms_helper,nouveau wmi 18820 2 mxm_wmi,nouveau video 24067 2 i915,nouveau
not good. Now try the blacklist nouveau alternative:
[tingo@dom0 ~]$ more /etc/modprobe.d/nouveau-disable.conf blacklist nouveau
now try a reboot again. Yep, that worked:
[tingo@dom0 ~]$ lsmod | grep nouveau
not sure if it helps with heat / power usage yet.
2015-10-04: Qubes 3.0 - check that my netvm has connection to my real DNS server:
[user@sys-net ~]$ sudo iptables -t nat -nvL PR-QBS Chain PR-QBS (1 references) pkts bytes target prot opt in out source destination 10518 618K DNAT udp -- * * 0.0.0.0/0 10.137.1.1 udp dpt:53 to:10.1.10.1
it does.
2015-10-04: Qubes 3.0 - various dmesg output from dom0:
[ 2.302467] vgaarb: setting as boot device: PCI:0000:00:02.0 [ 2.302473] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none [ 2.302489] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=none,locks=none [ 2.302496] vgaarb: loaded [ 2.302500] vgaarb: bridge control possible 0000:01:00.0 [ 2.302502] vgaarb: no bridge control possible 0000:00:02.0 [ 6.338904] MXM: GUID detected in BIOS [ 6.338976] ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x000000003) is beyond end of object (length 0x0) (20141107/exoparg2-420) [ 6.338985] ACPI Error: Method parse/execution failed [\_SB_.PCI0.GFX0._DSM] (Node ffff8801f78c2528), AE_AML_PACKAGE_LIMIT (20141107/psparse-536) [ 6.339035] ACPI: \_SB_.PCI0.GFX0: failed to evaluate _DSM (0x300b) [ 6.339042] ACPI Warning: \_SB_.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95) [ 6.339210] ACPI Warning: \_SB_.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95) [ 6.339360] i915 0000:00:02.0: optimus capabilities: disabled, status dynamic power, [ 6.339410] ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x000000003) is beyond end of object (length 0x0) (20141107/exoparg2-420) [ 6.339417] ACPI Error: Method parse/execution failed [\_SB_.PCI0.GFX0._DSM] (Node ffff8801f78c2528), AE_AML_PACKAGE_LIMIT (20141107/psparse-536) [ 6.339425] ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEG1.GFX0._DSM] (Node ffff8801f78d8398), AE_AML_PACKAGE_LIMIT (20141107/psparse-536) [ 6.339434] ACPI: \_SB_.PCI0.PEG1.GFX0: failed to evaluate _DSM (0x300b) [ 6.339439] ACPI Warning: \_SB_.PCI0.PEG1.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95) [ 6.339572] ACPI Warning: \_SB_.PCI0.PEG1.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95) [ 6.339754] pci 0000:01:00.0: optimus capabilities: disabled, status dynamic power, [ 6.339762] VGA switcheroo: detected Optimus DSM method \_SB_.PCI0.PEG1.GFX0 handle [ 6.339851] nouveau 0000:01:00.0: enabling device (0004 -> 0007) [ 6.396005] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 6.396013] [drm] Driver supports precise vblank timestamp query. [ 6.396632] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=none:owns=io+mem [ 6.419237] ACPI: Video Device [GFX0] (multi-head: yes rom: yes post: no) [ 6.423105] acpi device:03: registered as cooling_device4 [ 6.423394] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/LNXVIDEO:00/input/input13 [ 6.425510] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 6.429355] acpi device:48: registered as cooling_device5 [ 6.429475] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:02/input/input14 [ 6.429816] [drm] Initialized i915 1.6.0 20141121 for 0000:00:02.0 on minor 0 [ 6.430661] nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x0a8800b1 [ 6.430665] nouveau [ DEVICE][0000:01:00.0] Chipset: GT218 (NVA8) [ 6.430667] nouveau [ DEVICE][0000:01:00.0] Family : NV50 [ 6.431034] fbcon: inteldrmfb (fb0) is primary device [ 6.439429] nouveau 0000:01:00.0: Invalid ROM contents [ 6.439763] nouveau ![ VBIOS][0000:01:00.0] unable to locate usable image [ 6.439768] nouveau E[ DEVICE][0000:01:00.0] failed to create 0x10000001, -22 [ 6.439772] nouveau E[ DRM] failed to create 0x00000080, -22 [ 6.447700] nouveau: probe of 0000:01:00.0 failed with error -22 [ 7.128892] Console: switching to colour frame buffer device 170x48 [ 7.136092] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [ 7.136095] i915 0000:00:02.0: registered panic notifier [ 12.750602] intel ips 0000:00:1f.6: CPU TDP doesn't match expected value (found 25, expected 29) [ 12.751270] intel ips 0000:00:1f.6: IPS driver initialized, MCP temp limit 90 [ 13.772801] asus_laptop: Asus Laptop Support version 0.42 [ 13.772997] asus_laptop: BSTS called, 0xbc00 returned [ 13.773028] asus_laptop: model detected [ 13.773841] asus_laptop: Backlight controlled by ACPI video driver [ 13.773980] input: Asus Laptop extra buttons as /devices/platform/asus_laptop/input/input18
ok.
2015-10-04: Qubes 3.0 - switching to Xfce was easy - log out from the session, select Xfce from the menu upper right (the "K") and login again.
2015-10-03: Qubes 3.0 - no DNS from personal appvm. I can ping ip adresses, but not dns names. Bothe the sys-net and sys-firewall VMs have full connectivity. I tried updating dom0 via Qubes VM Manager, but it said "no updates available". Ok, no DNS from the the other appVMs either. OK, there are updates for the fedora-21 template vm. It seems that it is for the openjpeg2 package. Ok, that didn't help. qvm-ls -n from dom0 seems to look normal to me. Ok, found this thread in the mailing list. From dom0:
$ qvm-prefs -s sys-firewall netvm sys-net
and that worked. See also issue 1067, which might be relevant.
2015-10-03: Qubes 3.0 - ok, installation without encryption worked. A boot, and the Setup Agent starts. create user, set date and time, create service VMs (default), and starting the netvm failed:
firstboot failure! Starting Qubes networking failed: ['/usr/sbin/service', 'qubes-netvm', 'start'] failed: Redirecting to /bin/systemctl start qubes-netvm.service job for qubes-netvm.service failed. See 'systemctl status qubes-netvm.service' and 'journalctl -xn' for details.
and at the bottom of the dialog box:
libvirt.libvirtError: internal error: Unable to reset PCI device 0000:04:00.0: internal error: Failed to restore PCI config space for 0000:04:00.0
that is probably the (wired) network card again. I fix that by removing the Ethernet controller from the netvm. Then I restart the machine. After a reboot, the sys-net and sys-firewall vm started automatically. And I can connect to a wireless network. No
2015-10-03: Qubes 3.0 - first boot. I boot from the SandDisk usb stick (via Esc and the bios boot menu). First the grub boot menu shows up, then a "Q" screen with the disk password and a progress gauge. As reported by another user, I had to wait until the progress bar is about 3/4 full before the disk password is accepted. Before that, Qubes just asks for the password again. Unfortunately, the boot failed and I was in the dracut rescue shell. Looking at various logs didn't help, so in the end I used 'reboot' from the dracut shell. Try 2 - I wait until the progress bar is almost full before I input the disk password. Nope it still doesn't work. Oh well - install again. Install Qubes 3.0 - second try, this time without encryption of the disk. Qubes install program runs on vt7, use ctrl-alt-f1 to switch to vt1. anaconda uses vt1 to vt5, use alt-F1 to alt-F5 to switch between them. Use alt-F7 to swtch back to the Qubes install program.
2015-10-03: try to install Qubes 3.0 release onto a memory stick. I insert both memory sticks (installer on a Kingston stick) into the machine, power it up and select the Kingston from the bios boot menu. First the image is checked, then the Qubes installer (anaconda) starts up. Install language: English. Next is Date and time, Europe/Oslo + correct the time, keyboard layout Norwegian, Language - I added Norsk bokmål (Norge), Software selection - unchanged, Qubes OS wih KDE and Xfce, instllation source - unchanged (local media), I select the SanDisk Ultra (sdc, it says 29.66 GB after deleting a vfat partition via reclaim space), partition scheme LVM, encrypt, save passphrase, Next is "Begin installation". It creates filesystems and so on, then starts to install 951 packages. Package installation continues with good speed, until qubes-template-fedora-21 (819) this takes a while. Maybe it is a large package. After a (long while) it continues with other packages, and after a lengthy process it reports "Qubes is now sucessfully installed on your system and ready for use! Go ahead and reboot to start using it!". So I press the "Reboot" button.
2015-10-03: run the HCL report (in dom0)
[liveuser@localhost ~]$ qubes-hcl-report -s personal Qubes release 3.0 (R3.0) Brand: ASUSTeK Computer Inc. Model: U35JC BIOS: U35JC.208 Xen: 4.4.2 Kernel: 3.18.17-5 RAM: 7979 Mb CPU: Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz Chipset: Intel Corporation Core Processor DRAM Controller [8086:0044] (rev 18) VGA: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) NVIDIA Corporation GT218M [GeForce 310M] [10de:0a70] (rev a2) (prog-if 00 [VGA controller]) Net: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01) Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) SCSI: WDC WD6400BEVT-8 Rev: 1A01 Cruzer Rev: 8.01 Cruzer Rev: 8.01 HVM: Active I/O MMU: Not active TPM: Device not found Qubes HCL Files are copied to: 'personal' Qubes-HCL-ASUSTeK_Computer_Inc.________-U35JC-20151003-145347.yml - HCL Info Qubes-HCL-ASUSTeK_Computer_Inc.________-U35JC-20151003-145347.cpio.gz - HCL Support Files
the files have sent to my workstation too. Contents of the cpio archive:
[user@personal ~]$ zcat Qubes-HCL-ASUSTeK_Computer_Inc.________-U35JC-20151003-145347.cpio.gz | cpio -itv drwx------ 2 user 1001 0 Oct 3 14:53 . -rw-rw-r-- 1 user 1001 16384 Oct 3 14:53 xl-dmesg -rw-rw-r-- 1 user 1001 1228 Oct 3 14:53 xl-info -rw-rw-r-- 1 user 1001 19415 Oct 3 14:53 dmidecode -rw-rw-r-- 1 user 1001 495 Oct 3 14:53 scsi -rw-rw-r-- 1 user 1001 8377 Oct 3 14:53 lspci -rw-rw-r-- 1 user 1001 2816 Oct 3 14:53 cpuinfo -rw-rw-r-- 1 user 1001 25 Oct 3 14:53 qubes-release 98 blocks
ok.
2015-10-03: VM info from dom0 from Xen
[liveuser@localhost ~]$ xl list Name ID Mem VCPUs State Time(s) dom0 0 3933 4 r----- 2148.9 sys-net 3 295 4 -b---- 121.0 sys-firewall 4 663 4 -b---- 56.3 personal 5 2933 4 -b---- 1850.6
from Qubes
[liveuser@localhost ~]$ qvm-ls ----------------+----+---------+-------+-------+-----------+---------------+--------+ name | on | state | updbl | type | template | netvm | label | ----------------+----+---------+-------+-------+-----------+---------------+--------+ {dom0} | * | Running | Yes | Admin | None | n/a | black | {sys-net} | * | Running | | Net | fedora-21 | n/a | red | {sys-firewall} | * | Running | | Proxy | fedora-21 | sys-net | green | =>[fedora-21] | | Halted | Yes | Tpl | n/a | *sys-firewall | black | work | | Halted | | | fedora-21 | *sys-firewall | green | banking | | Halted | | | fedora-21 | *sys-firewall | green | personal | * | Running | | | fedora-21 | *sys-firewall | yellow | untrusted | | Halted | | | fedora-21 | *sys-firewall | red | fedora-21-dvm | | Halted | | | fedora-21 | *sys-firewall | gray |
cool.
2015-10-03: info from dom0:
[liveuser@localhost ~]$ uname -a Linux localhost 3.18.17-5.pvops.qubes.x86_64 #1 SMP Sat Aug 8 20:56:31 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux [liveuser@localhost ~]$ ls -l /etc/*release* lrwxrwxrwx 1 root root 13 Aug 9 18:20 /etc/fedora-release -> qubes-release -rw-r--r-- 1 root root 137 Aug 9 18:17 /etc/os-release -rw-r--r-- 1 root root 25 Aug 9 18:17 /etc/qubes-release lrwxrwxrwx 1 root root 13 Aug 9 18:20 /etc/redhat-release -> qubes-release lrwxrwxrwx 1 root root 13 Aug 9 18:20 /etc/system-release -> qubes-release -rw-r--r-- 1 root root 21 Aug 9 18:17 /etc/system-release-cpe [liveuser@localhost ~]$ more /etc/qubes-release Qubes release 3.0 (R3.0) [liveuser@localhost ~]$ more /etc/os-release NAME=Qubes VERSION="3.0 (R3.0)" ID=qubes VERSION_ID=3.0 PRETTY_NAME="Qubes 3.0 (R3.0)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:ITL:qubes:3.0" [liveuser@localhost ~]$ more /etc/system-release-cpe cpe:/o:ITL:qubes:3.0
ok.
2015-10-03: info from VM personal
[user@personal ~]$ uname -a Linux personal 3.18.17-5.pvops.qubes.x86_64 #1 SMP Sat Aug 8 20:56:31 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux [user@personal ~]$ lsb_release -a bash: lsb_release: command not found... Install package 'redhat-lsb-core' to provide command 'lsb_release'? [N/y]
ok, we don't need it.
[user@personal ~]$ ls -l /etc/*release* -rw-r--r-- 1 root root 31 Nov 21 2014 /etc/fedora-release -rw-r--r-- 1 root root 377 Nov 21 2014 /etc/os-release lrwxrwxrwx 1 root root 14 Nov 21 2014 /etc/redhat-release -> fedora-release lrwxrwxrwx 1 root root 14 Nov 21 2014 /etc/system-release -> fedora-release -rw-r--r-- 1 root root 31 Nov 21 2014 /etc/system-release-cpe
look into it
[user@personal ~]$ cat /etc/fedora-release Fedora release 21 (Twenty One)
and os-release
[user@personal ~]$ cat /etc/os-release NAME=Fedora VERSION="21 (Twenty One)" ID=fedora VERSION_ID=21 PRETTY_NAME="Fedora 21 (Twenty One)" ANSI_COLOR="0;34" CPE_NAME="cpe:/o:fedoraproject:fedora:21" HOME_URL="https://fedoraproject.org/" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_BUGZILLA_PRODUCT="Fedora" REDHAT_BUGZILLA_PRODUCT_VERSION=21 REDHAT_SUPPORT_PRODUCT="Fedora" REDHAT_SUPPORT_PRODUCT_VERSION=21 and system-release-cpe [user@personal ~]$ cat /etc/system-release-cpe cpe:/o:fedoraproject:fedora:21
ok.
2015-10-03: graphics - this HCL report on the qubes-users mailing list details how to use the acpi_call module to turn off discrete nVidia graphics.
2015-10-03: graphics - Optimus, info from dmesg:
[ 6.780294] MXM: GUID detected in BIOS [ 6.780363] ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x000000003) is beyond end of object (length 0x0) (20140926/exoparg2-420) [ 6.780371] ACPI Error: Method parse/execution failed [\_SB_.PCI0.GFX0._DSM] (Node ffff8801ed44a528), AE_AML_PACKAGE_LIMIT (20140926/psparse-536) [ 6.780386] ACPI: \_SB_.PCI0.GFX0: failed to evaluate _DSM (0x300b) [ 6.780393] ACPI Warning: \_SB_.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95) [ 6.780507] ACPI Warning: \_SB_.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95) [ 6.780622] pci 0000:00:02.0: optimus capabilities: disabled, status dynamic power, [ 6.780663] ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x000000003) is beyond end of object (length 0x0) (20140926/exoparg2-420) [ 6.780670] ACPI Error: Method parse/execution failed [\_SB_.PCI0.GFX0._DSM] (Node ffff8801ed44a528), AE_AML_PACKAGE_LIMIT (20140926/psparse-536) [ 6.780677] ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEG1.GFX0._DSM] (Node ffff8801ed460398), AE_AML_PACKAGE_LIMIT (20140926/psparse-536) [ 6.780687] ACPI: \_SB_.PCI0.PEG1.GFX0: failed to evaluate _DSM (0x300b) [ 6.780692] ACPI Warning: \_SB_.PCI0.PEG1.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95) [ 6.780800] ACPI Warning: \_SB_.PCI0.PEG1.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95) [ 6.781779] pci 0000:01:00.0: optimus capabilities: disabled, status dynamic power, [ 6.781788] VGA switcheroo: detected Optimus DSM method \_SB_.PCI0.PEG1.GFX0 handle [ 6.782364] nouveau 0000:01:00.0: enabling device (0004 -> 0007)
interesting or not. Using vgaswitcheroo, I can see
[liveuser@localhost ~]$ sudo cat /sys/kernel/debug/vgaswitcheroo/switch 0:DIS: :DynPwr:0000:01:00.0 1:IGD:+:Pwr:0000:00:02.0
So, the Discrete card (0) has "DynPwr", and the Integrated Graphics Device (1) is powered on and active. Ufortunately, it doesn't seem like I can manipulate the card with vga switcheroo:
[liveuser@localhost ~]$ sudo su - Last login: Sat Oct 3 11:39:26 EDT 2015 on pts/1 [root@localhost ~]# cat /sys/kernel/debug/vgaswitcheroo/switch 0:DIS: :DynPwr:0000:01:00.0 1:IGD:+:Pwr:0000:00:02.0 [root@localhost ~]# echo OFF > /sys/kernel/debug/vgaswitcheroo/switch [root@localhost ~]# cat /sys/kernel/debug/vgaswitcheroo/switch 0:DIS: :DynPwr:0000:01:00.0 1:IGD:+:Pwr:0000:00:02.0
Oh well.
2015-10-03: temperature - the machine runs a bit hot, it would be better if I turned off the discrete graphics card. sensors output from dom0:
[liveuser@localhost ~]$ sensors acpitz-virtual-0 Adapter: Virtual device temp1: +72.0°C (crit = +108.0°C) nouveau-pci-0100 Adapter: PCI adapter temp1: +72.0°C (high = +95.0°C, hyst = +3.0°C) (crit = +105.0°C, hyst = +5.0°C) (emerg = +135.0°C, hyst = +5.0°C) coretemp-isa-0000 Adapter: ISA adapter Core 0: +67.0°C (high = +95.0°C, crit = +105.0°C) Core 2: +67.0°C (high = +95.0°C, crit = +105.0°C)
ok.
2015-10-03: Graphics - ok, Qubes thinks that both outputs LVDS1 and VGA-1-1 are connected (I have no display connected externally). Easily fixed - disable VGA-1-1 in System Settings, Display and Monitor. From VM personal it looks like this:
[user@personal ~]$ xrandr Screen 0: minimum 64 x 64, current 1368 x 768, maximum 32767 x 32767 DUMMY0 connected 1368x768+0+0 0mm x 0mm QB2392x768 64.44 + QB1366x768 59.88* DUMMY1 connected QB2392x768 64.44 + QB1024x768 59.92 DUMMY2 disconnected DUMMY3 disconnected
ok From dom0 it looks like this:
Screen 0: minimum 8 x 8, current 1366 x 768, maximum 32767 x 32767
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 293mm x 164mm
1366x768 60.02*+
1024x768 60.00
800x600 60.32 56.25
640x480 59.94
DP1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
VGA2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
VGA-1-1 connected (normal left inverted right x axis y axis)
1024x768 60.00
800x600 60.32 56.25
848x480 60.00
640x480 59.94
1024x768 (0x63) 65.000MHz
h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.36KHz
v: height 768 start 771 end 777 total 806 clock 60.00Hz
800x600 (0x64) 40.000MHz
h: width 800 start 840 end 968 total 1056 skew 0 clock 37.88KHz
v: height 600 start 601 end 605 total 628 clock 60.32Hz
800x600 (0x65) 36.000MHz
h: width 800 start 824 end 896 total 1024 skew 0 clock 35.16KHz
v: height 600 start 601 end 603 total 625 clock 56.25Hz
I don't know why. Perhaps because this is an Optimus laptop? This possible via the dom0 to clipboard trick:
$ xrandr > /var/run/qubes/qubes-clipboard.bin $ echo "dom0" > /var/run/qubes/qubes-clipboard.bin.source
ok.
2015-10-03: When I try to restart the netVM (sys-net) from Qubes VM Manager, I get an error message: "Error starting VM 'sys-net': internal error: unable to reset PCI device 0000:04:00.0: internal error: Failed to restore PCI config space for 0000:04:00.0". From Settings in the sys-net VM I see that 04:00.0 is the Ethernet controller (Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0)). I'm not using that (yet), let me see if removing it from the vm allows it to start. Yes - that works. Now, how do I connect to a wireless network in Qubes? Ok, I stopped sys-frewall and sys-net, and restarted sys-net (and dsys-firewall) again, and the I got the NetworkManager Applet in my systray, and could connect to a wireless network from it. Nice!
2015-10-03: I booted Qubes R3.1-alpha (Qubes-R3.1-alpha1.1-x86_64-LIVE.iso) from a usb stick. It started up ok, but only the dom0 vm started. It runs the display in the correct resolution (1366x768), so that is a positive thing. I use setxkbmap no in any terminal / console window to get a correct layout for my keyboard.