[qubes-users] HCL - ASUSTeK N501VW
l --- layout: 'hcl' type: 'notebook' hvm: 'yes' iommu: 'yes' slat: 'yes' tpm: 'unknown' remap: 'yes' brand: | ASUSTeK COMPUTER INC. model: | N501VW bios: | N501VW.307 cpu: | Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz cpu-short: | Skylake chipset: | Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:1910] (rev 07) chipset-short: | Sunrise gpu: | Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) gpu-short: | Intel HD530 network: | Intel Corporation Wireless 7265 (rev 59) memory: | 16183 scsi: | usb: | 1 versions: - works: 'yes' qubes: | R4.0 xen: | 4.8.5-18.fc25 kernel: | 5.6.16-1 remark: | Needs published EFI workaround to boot, Nvidia workaround not to OOPSing during install. I got the touchscreen working, once. USB-C does not work at all, but might be broken hardware. Touchpad palm suppression stinks, and the "Fn-f9" key to turn the touchpad off doesn't work; I had to bind a script to "WIN-f9" to turn it off before I could type without the cursor jumping around all the time. External-monitor config is not remembered from one connection to the next, and always prefers 60Hz/reduced-resolution over 30Hz/full-resolution. I had to configure enough RAM for two displays, in X, manually. Alcor Micro AU6621 MMC/SD slot did not work with 4.x kernels, but works under a 5.x kernel. Camera works. Intel 7265 wifi needs non-free "iwl" firmware. Have not tried Bluetooth. Suspend/resume works. "Fn" screen brightness, volume control keys work. Have not tried the Nvidia GM107/960M GPU. M.2 NVMe works. credit: | n...@cantrip.org link: | --- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/cbd7b1b7-7bf6-87a2-fb12-cc45748dfae1%40cantrip.org. Qubes-HCL-ASUSTeK_COMPUTER_INC_-N501VW-20200711-091022.cpio.gz Description: application/gzip
[qubes-users] Re: control boot line in installer?
On 3/8/18 1:19 AM, Nathan Myers wrote: I am trying to install on an ASUS ZenBook UV501 (Skylake, HD530, NV960M, NVME SSD). The installer kernel OOPSes because it loads the nouveau driver module, and gets confused by the bumblebee/optimus hardware arrangement. I have installed Debian 9.3 on this machine, and it works if I blacklist the nouveau module during boot. (I.e. the i915 module needs to load first.) But I don't see any way to control the boot line during installation. ("E" only shows me a chainloader command line.) Also, when choosing where to install, the installer seems to offer only the whole disk, but I have partitions already in place, currently formatted for swap and ext4, that I would like for the installer to overwrite. How do I tell the Qubes installer to use those? Might the 4.0 beta installer deal better with these details? With the 4.0rc5 installer, it never gets to the option to edit the chainloader command line. It just says X failed, press ENTER, and then nothing when i press ENTER. The log shows it looping trying to start things. But the kernel is not obviously OOPSing. What to try next? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/p7rlp0%24jdg%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] control boot line in installer?
I am trying to install on an ASUS ZenBook UV501 (Skylake, HD530, NV960M, NVME SSD). The installer kernel OOPSes because it loads the nouveau driver module, and gets confused by the bumblebee/optimus hardware arrangement. I have installed Debian 9.3 on this machine, and it works if I blacklist the nouveau module during boot. (I.e. the i915 module needs to load first.) But I don't see any way to control the boot line during installation. ("E" only shows me a chainloader command line.) Also, when choosing where to install, the installer seems to offer only the whole disk, but I have partitions already in place, currently formatted for swap and ext4, that I would like for the installer to overwrite. How do I tell the Qubes installer to use those? Might the 4.0 beta installer deal better with these details? Thanks, Nathan Myers -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/p7qkhm%24g4l%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.