[qubes-users] Re: Dell XPS 9560 4k resolution issues
On Friday, June 30, 2017 at 12:02:46 PM UTC+2, David Nogueira wrote: > On Friday, June 30, 2017 at 10:37:58 AM UTC+1, randy march wrote: > > I have the same notebook like you. > > I simply go to system tools - display and change resolution to 1920x1080. > > > > But I would like to have a 4k resolution with scaled everything... > > > > how can you do this? > > > > > > will qubes 4.0 solve this issue? > > Hi Randy, > > I only have one resolution showing, and that is what I am trying to change. > Does your brightness control work? > > What versions of Qubes do you have? and which kernel? Also which kernel > options? > > I believe I read somewhere HiDPI will be better supported in 4.0 > > Thanks! > > David my brightness control and everything else works. I installed the latest version of qubes with the standard configuration. the only think I changed was the wlan card cause the broadcom wlan card does not work with qubes. -- 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/9a5f6c0f-dbbf-4ba0-929c-4d7bd0e2de57%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Laptop Dual Win10 boot problem
On 07/01/2017 02:46 PM, Unman wrote:
On Sat, Jul 01, 2017 at 12:49:59PM -1000, yreb-qusw wrote:
On 07/01/2017 12:10 PM, Unman wrote:
Nothing will go wrong if you get the partition specification wrong -
Windows wont boot and you will see an error message.
From what you have said you have two options: msdos1 and msdos2.
In grub partitions are numbered starting from 1, so these can be
referenced as hd0,msdos1 and hd0,msdos2.
Just create two entries, one for each partition, and try to boot: if
the first fails, reboot and choose the second.
I'd be happy to if I had a clue what that means like what ?
menuentry "Windows" {
insmod part_msdos
insmod ntldr
insmod ntfs
ntldr (hd0,msdos1)/bootmgr
}
menuentry "Windows" {
insmod part_msdos
insmod ntldr
insmod ntfs
ntldr (hd1,1)/bootmgr
}
Again, lets say it might be hd0 it might be hd1 , it might be partition
msdos1 msdos2 or ? should it just be labeled 1 or 2
then I would put in 4 entries or reboot and just keep guessing on the format
No need to guess:
grub references disks numbering from 0
grub references partitions numbering from 1
So the first partition on the first disk would be hd0,msdos1. (also
hd0,1 - doesn't matter)
The third partition on a second disk would be hd1,msdos3
So now you can create two menu entries, one for each partition: Give them
different names - like this - menuentry "Windows msdos1"
PS: What is supposed to happen ? Where and When am I to make the choice to
boot the win10 vs Qubes .
When you start the machine you will see the grub menu - It should
contain a menu (obviously) with entries for Qubes, and the two entries
you have just created.
You can press up and down keys to move up and down the entries -
Pressing enter will try to boot with the highlighted entry.
(There are instructions under the menu)
And when one does :
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Should one be seeing something lie 'found windows .img" image or does
it matter ?
I'm seeing nothing when I run grub2-mkconfig and also nothing
with any of my entries at boot using both suggested versions of
the 'entry/stanza's' in /etc/grub.d/40_custom
I'm sort of doubting its supposed to be /etc/grub.d/40_custom, with
the comma at the end, and the docs have a typo ?
--
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/7f0e91e5-c082-0333-0c1b-2585faa7efe7%40riseup.net.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Help :: Disposable VMs start without a NetVM (can't use DVMs currently )
On Sun, Jul 02, 2017 at 01:08:44AM +0200, 'P R' via qubes-users wrote: > Hello, > > I have spend several hours to built new Template VMs from scratch (more > precise: the fedora-24-minimal templates). > > Now I have the problem, that my new disposable VMs all start without an > attaches Net-VM. > > sys-usb, sys-firewall, sys-net are now all based on the fedora-24-minimal > template, with some additional packages, as suggested in the documentation. > > I have also built a new dvm which is based on the fedora-24 template: > > My default fedora-24 template is named "my-fedora-24-apps" and is a Template > VM without a NetVM attached. > > I created a new dvm in dom0: > > [user@dom0 ~] qvm-create-default-dvm my-fedora-24-apps > > In preferences of the new dvm template which is named > "my-fedora-24-apps-dvm" I have attached the firewall Proxy VM as NetVM. > > But when I launch a program in the disposable VM there is no Net-VM > attached. > I have also set the "NetVM for DispVM" unter "Other" in the "Advanced" > Settings Tab of Qubes Manager for the dvm template to sys-firewall. > > Still all my disposable AppVM start with an empty NetVM. > If I edit a disposable App VM and add the sys-firewall as NetVM, everything > works fine. > > > QUESTION: > Where and how am I supposed to set the correct information which NetVM > should be used for my DVMs? > > - P R The "netVM for dispVM" entry sets the netVM for disposableVMs started from that qube. You haven't said HOW you are "launching a program". If you start it from the Qubes Menu then it will (should) honour the setting for the dvmTemplate, and so in your case start a disposableVM attached to the firewall. If you are starting a disposableVM from a qube (by e.g "open in disposable VM") then THAT disposableVM will be connected to whatever the entry for "NetVM for dispVM" says for that qube. I find it easier to check from dom0 terminal, using qvm-prefs , and to set the relevant values using 'qvm-prefs -s dispvm_netvm ' unman -- 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/20170702011901.gi4szxkgdes3tqex%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Best Laptop For Qubes
On Friday, June 30, 2017 at 2:19:53 AM UTC-4, tai...@gmx.com wrote: > On 06/28/2017 09:57 PM, cooloutac wrote: > > > On Wednesday, June 28, 2017 at 2:39:19 PM UTC-4, tai...@gmx.com wrote: > >> On 06/27/2017 10:20 PM, cooloutac wrote: > >> > >>> its common sense to me man. Server boards are designed for servers. I > >>> gave some tips on how to get something compatible which I think is > >>> priority. Another one is to research the board on linux forums and see > >>> if its used alot or not or if it has problems. > >> "Designed for servers" The IC's are identical to their desktop > >> counterparts, just with different features burned in. > >> > >> I want you to explain to me what makes a desktop board and CPU different > >> from a "server" board and CPU, real technical differences not marketing. > >>>Its like wanting to use centos as a gaming os. is it possible? > >>> probably, anything is possible, but is it practical? > >> CentOS and fedora are literally the same thing, what do you think makes > >> them different? > >>> But Jean brings up good points whats "best" is subjective. > >>> > >>>But I have to say talking someone out of buying Purism that supports > >>> Qubes and free hardware like you want, calling it overpriced, and then > >>> recommending expensive as hell server boards and 100 dollar keyboards as > >>> a little strange. I mean you balked first. > >>> > >> For the last time, purism is NOT free hardware. > >> Whats free about it? Why don't you explain that to me. > >> > >> I paid $500 total for my setup including the $300 motherboard and I have > >> actual free firmware, $80 more gets me a great keyboard that lasts 30 > >> years - compared to that a 2K quanta rebrand is simply overpriced. > > i only saw it for 475 just the motherboard alone, and I presum > > compatibility problems with it just cause its not a popular board. 100% > > libre is nice and all but so is being part of society lol. can you link > > me cheaper deals? lol 100 dollars for that keyboard. > The KCMA-D8 MSRP is $315, and the KGPE-D16 is $415 (available on newegg) > - I can't understand as to why you want to convince people to buy a 2K > laptop but $500 for a legitimately free system is considered too much money. > Boards don't have "compatibility issues", chipsets do.. The firmware > configures reference tables like SRAT/SLIT/IRVS etc but it shouldn't be > present or doing anything once you're in an OS. The chipset in that is > physically identical to the one in an AM3+ board you've probably had at > some point so it is quite popular. Irregardless I have tested it and it > works great. > > AMD has released a decent amount of documentation on their pre-2013 > systems, and it is enough to make firmware ports - they have also > donated time and resources to the coreboot project which makes them a > company worthy of respect - we can only hope they continue with that for > zen. > > The average keyboard costs $30 but it only lasts 3 years or less if like > to eat/drink at your desk, and $80 is actually a pretty good deal for > what it is - most mechanical keyboards are $200+. once you type on one > you can't go back. sure 500 dollars would be a great deal for a whole system, but you are just talking about the motherboard and keyboard for 500. seems expensive, especially since you complain about the price of purism. -- 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/988adbc5-5411-4561-8673-16cfcc25731f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Laptop Dual Win10 boot problem
On Friday, June 30, 2017 at 2:07:51 PM UTC-4, yreb-qusw wrote: > On 06/28/2017 04:03 PM, cooloutac wrote: > > so you would put hd0,X X= 1 2 or 3 etc... you said it was 200mb right so > > just look for something around that in kb's. probably the smallest > > partition it should say file type too no? ntfs. > > > > In general, what would happen if I guessed wrong with the 1, 2, 3 > etc > > > It should be file type NTFS not ext3 ?? windows is ntfs. -- 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/93788fa8-5e18-4149-bfb3-5655016ab4db%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Laptop Dual Win10 boot problem
On Sat, Jul 01, 2017 at 12:49:59PM -1000, yreb-qusw wrote:
> On 07/01/2017 12:10 PM, Unman wrote:
> > Nothing will go wrong if you get the partition specification wrong -
> > Windows wont boot and you will see an error message.
> > From what you have said you have two options: msdos1 and msdos2.
> > In grub partitions are numbered starting from 1, so these can be
> > referenced as hd0,msdos1 and hd0,msdos2.
> > Just create two entries, one for each partition, and try to boot: if
> > the first fails, reboot and choose the second.
>
>
>
> I'd be happy to if I had a clue what that means like what ?
>
>
>
> menuentry "Windows" {
> insmod part_msdos
> insmod ntldr
> insmod ntfs
> ntldr (hd0,msdos1)/bootmgr
> }
>
>
> menuentry "Windows" {
> insmod part_msdos
> insmod ntldr
> insmod ntfs
> ntldr (hd1,1)/bootmgr
> }
>
>
>
> Again, lets say it might be hd0 it might be hd1 , it might be partition
> msdos1 msdos2 or ? should it just be labeled 1 or 2
>
> then I would put in 4 entries or reboot and just keep guessing on the format
>
No need to guess:
grub references disks numbering from 0
grub references partitions numbering from 1
So the first partition on the first disk would be hd0,msdos1. (also
hd0,1 - doesn't matter)
The third partition on a second disk would be hd1,msdos3
So now you can create two menu entries, one for each partition: Give them
different names - like this - menuentry "Windows msdos1"
>
>
>
> PS: What is supposed to happen ? Where and When am I to make the choice to
> boot the win10 vs Qubes .
When you start the machine you will see the grub menu - It should
contain a menu (obviously) with entries for Qubes, and the two entries
you have just created.
You can press up and down keys to move up and down the entries -
Pressing enter will try to boot with the highlighted entry.
(There are instructions under the menu)
--
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/20170702004621.sajrnxj7cqht6o6z%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - Dell Inspiron 1546
No fiddling. USBs work; Sleep works. Intel wireless modem. It is just slow because it is 4GB, 2 cores. Only supports 2 user VMs plus the system ones. Limited by the lack of virtualization tech. -- 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/CAJrrhxtahgB_6msYHKQ-PU59Zi-_3rJHu0tnvg5cQQE6RvR1Lg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-Dell_Inc_-Inspiron_1545___-20170701-202426.cpio.gz Description: GNU Zip compressed data Qubes-HCL-Dell_Inc_-Inspiron_1545___-20170701-202426.yml Description: application/yaml
Re: [qubes-users] Re: Laptop Dual Win10 boot problem
On Sat, Jul 01, 2017 at 12:33:31PM -1000, yreb-qusw wrote: > On 07/01/2017 12:10 PM, Unman wrote: > > On Sat, Jul 01, 2017 at 10:05:36AM -1000, yreb-qusw wrote: > > > On 06/28/2017 04:03 PM, cooloutac wrote: > > > > so you would put hd0,X X= 1 2 or 3 etc... you said it was 200mb > > > > right so just look for something around that in kb's. probably the > > > > smallest partition it should say file type too no? ntfs. > > > > > > > > > > actualy this is from the qubes doc's not me > > > > > > > > > -- > > > Identify the Windows system partition that has /bootmgr > > > > > > In blkid output, the system partition is the one with LABEL=’SYSTEM > > > RESERVED’ or LABEL=’SYSTEM’ and is only about 100 to 200 MB in size > > > -- > > > > > > > > > ntldr (hd0,msdos2)/bootmgr ? > > > > > > or > > > > > > ntldr (hd0,2)/bootmgr ? > > > > > > > > > I would think it would be the 1st partitions when it comes to booting. > > > > > > > > > Is it possible my boot partition for win10 got overwritten when > > > installing Qubes somehow ? > > > > > > > > > > > > Maybe I should give up , as by the slow/no responses, it seems there > > > is > > > no way to get support for this > > > > > > > As far as I can see a number of people have tried to help you here > > You should read the guidelines at www.qubes-os.org/mailing-lists and > > be patient. > > Also, a two minute search on the net would bring you to guides that > > would enable you to learn something about grub and maybe solve the problem > > for > > yourself. > > > > On the specific points: > > I doubt that your Win10 boot partition got overwritten , unless you > > asked the installer to do so. > > It is possible to run Windows without a SYSTEM partition, particularly if > > installed in BIOS mode - it is, however, not standard. > > fdisk -l shows you which partition has been marked as bootable - this > > need not be the partition you want. It need not be the first partition. > > Nothing will go wrong if you get the partition specification wrong - > > Windows wont boot and you will see an error message. > > From what you have said you have two options: msdos1 and msdos2. > > In grub partitions are numbered starting from 1, so these can be > > referenced as hd0,msdos1 and hd0,msdos2. > > Just create two entries, one for each partition, and try to boot: if > > the first fails, reboot and choose the second. > > > > Incidentally, its relatively simple to enable legacy boot on InsydeH20 - > > again, a simple search would show you how. > > Unless someone did this for you it's most likely that you are in UEFI > > mode. You can check this in Linux by looking at the output from dmesg, > > and looking for "efi" entries - 'dmesg|grep efi' > > Also,look in /sys/firmware for efi directory. If it's there then you > > booted UEFI. > > The partition layout you have described doesn't seem to be standard for > > Windows under UEFI. > > > > It isn't clear if you read the documentation before installing Qubes, or > > if you have a back up or cloned disk. If you didn't I would do it now > > before trying anything else. You can attach the NTFS partitions to a qube > > and copy the data off, or clone the whole partition. > > > > Good luck. > > > I appreciate your replies, I'm not a sysadmin, enabled legacy boot , i > only vaguely understand that that is requird for Qubes, anyway, i've got > qubes installed, it's just acting different than on my desktop version > is, > > I don't expect any replies, just hoping for more than 1 or 2 , hence I > asked about the IRC, but I'm guessing that isn't well attended also > > forgive me , for asking , it really isn't "a two minute" search it is that > Grub and such are complicated for non sysadmin people > > > just for the record, I would think Qubes might like to have normal non > sysadmin people able to use the OS, so my questions to the list, my serve > those people, > > The format of post and wait days or never for a reply may not be ideal > for anything complicated IMHO > > anyway, thanks for listening > Actually, normal, non sysadmin people CAN use the OS for the most part - the installation process can be problematic and even seasoned users can find multiboot setups difficult. I would never recommend that - perhaps the "multiboot" page should carry that warning. -- 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/20170702002615.pkozu3vfrhmqfwlf%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Help :: Disposable VMs start without a NetVM (can't use DVMs currently )
Hello, I have spend several hours to built new Template VMs from scratch (more precise: the fedora-24-minimal templates). Now I have the problem, that my new disposable VMs all start without an attaches Net-VM. sys-usb, sys-firewall, sys-net are now all based on the fedora-24-minimal template, with some additional packages, as suggested in the documentation. I have also built a new dvm which is based on the fedora-24 template: My default fedora-24 template is named "my-fedora-24-apps" and is a Template VM without a NetVM attached. I created a new dvm in dom0: [user@dom0 ~] qvm-create-default-dvm my-fedora-24-apps In preferences of the new dvm template which is named "my-fedora-24-apps-dvm" I have attached the firewall Proxy VM as NetVM. But when I launch a program in the disposable VM there is no Net-VM attached. I have also set the "NetVM for DispVM" unter "Other" in the "Advanced" Settings Tab of Qubes Manager for the dvm template to sys-firewall. Still all my disposable AppVM start with an empty NetVM. If I edit a disposable App VM and add the sys-firewall as NetVM, everything works fine. QUESTION: Where and how am I supposed to set the correct information which NetVM should be used for my DVMs? - P R -- 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/ef49d62f-8b10-1947-e512-3c323b119054%40googlemail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Laptop Dual Win10 boot problem
On 07/01/2017 12:10 PM, Unman wrote:
Nothing will go wrong if you get the partition specification wrong -
Windows wont boot and you will see an error message.
From what you have said you have two options: msdos1 and msdos2.
In grub partitions are numbered starting from 1, so these can be
referenced as hd0,msdos1 and hd0,msdos2.
Just create two entries, one for each partition, and try to boot: if
the first fails, reboot and choose the second.
again fwiw this is what the
https://www.qubes-os.org/doc/multiboot/
says:
-
In blkid output, the system partition is the one with LABEL=’SYSTEM
RESERVED’ or LABEL=’SYSTEM’ and is only about 100 to 200 MB in size
Add this stanza to /etc/grub.d/40_custom,
menuentry "Windows" {
insmod part_msdos
insmod ntldr
insmod ntfs
ntldr (hd1,X)/bootmgr
}
(Change X to reflect the relevant system partition.)
Then update the grub config:
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
There is no need to reinstall grub itself.
If the above stanza does not work, you may try this one (at your own
risk!) instead:
menuentry "Windows" {
insmod part_msdos
insmod ntfs
set root='(hd0,msdosX)'
chainloader +1
}
(Change X to reflect the relevant system partition.)
--
see the part "at your own risk!" ..hence, I'm cautious
as for "making two entries"
I'd be happy to if I had a clue what that means like what ?
menuentry "Windows" {
insmod part_msdos
insmod ntldr
insmod ntfs
ntldr (hd0,msdos1)/bootmgr
}
menuentry "Windows" {
insmod part_msdos
insmod ntldr
insmod ntfs
ntldr (hd1,1)/bootmgr
}
Again, lets say it might be hd0 it might be hd1 , it might be
partition msdos1 msdos2 or ? should it just be labeled 1 or 2
then I would put in 4 entries or reboot and just keep guessing on the format
PS: What is supposed to happen ? Where and When am I to make the
choice to boot the win10 vs Qubes .
I have been waiting over a week, I don't 'expect' an answer I am
already trying different stanza entries so far no success
PPS: I've "cc'd the list"
--
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/586fdc5c-5a76-3dad-c8e8-2b15ac319da4%40riseup.net.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Laptop Dual Win10 boot problem
On 07/01/2017 12:10 PM, Unman wrote: and looking for "efi" entries - 'dmesg|grep efi' Also,look in /sys/firmware for efi directory. If it's there then you booted UEFI. fwiw, neither of these indicates EFI boot so, are you saying Legacy boot might fix something ? frankly, I am not even sure what behaviour to expect, if I did get grub2 with the right boot partition Would I see something when I boot in Grub that gives me a choice to boot win10 or Qubes, is there a choice that pops up in Grub or ? I'm sure this all makes sense to long term linux sysadmins... eg I also noticed with I do qvm-shutdown --all it seems to shutdown dom0 and freeze the computer -- 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/aa31eaa2-e611-05f5-d38d-c0b0aaf7eb0a%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Laptop Dual Win10 boot problem
On 07/01/2017 12:10 PM, Unman wrote: On Sat, Jul 01, 2017 at 10:05:36AM -1000, yreb-qusw wrote: On 06/28/2017 04:03 PM, cooloutac wrote: so you would put hd0,X X= 1 2 or 3 etc... you said it was 200mb right so just look for something around that in kb's. probably the smallest partition it should say file type too no? ntfs. actualy this is from the qubes doc's not me -- Identify the Windows system partition that has /bootmgr In blkid output, the system partition is the one with LABEL=’SYSTEM RESERVED’ or LABEL=’SYSTEM’ and is only about 100 to 200 MB in size -- ntldr (hd0,msdos2)/bootmgr ? or ntldr (hd0,2)/bootmgr ? I would think it would be the 1st partitions when it comes to booting. Is it possible my boot partition for win10 got overwritten when installing Qubes somehow ? Maybe I should give up , as by the slow/no responses, it seems there is no way to get support for this As far as I can see a number of people have tried to help you here You should read the guidelines at www.qubes-os.org/mailing-lists and be patient. Also, a two minute search on the net would bring you to guides that would enable you to learn something about grub and maybe solve the problem for yourself. On the specific points: I doubt that your Win10 boot partition got overwritten , unless you asked the installer to do so. It is possible to run Windows without a SYSTEM partition, particularly if installed in BIOS mode - it is, however, not standard. fdisk -l shows you which partition has been marked as bootable - this need not be the partition you want. It need not be the first partition. Nothing will go wrong if you get the partition specification wrong - Windows wont boot and you will see an error message. From what you have said you have two options: msdos1 and msdos2. In grub partitions are numbered starting from 1, so these can be referenced as hd0,msdos1 and hd0,msdos2. Just create two entries, one for each partition, and try to boot: if the first fails, reboot and choose the second. Incidentally, its relatively simple to enable legacy boot on InsydeH20 - again, a simple search would show you how. Unless someone did this for you it's most likely that you are in UEFI mode. You can check this in Linux by looking at the output from dmesg, and looking for "efi" entries - 'dmesg|grep efi' Also,look in /sys/firmware for efi directory. If it's there then you booted UEFI. The partition layout you have described doesn't seem to be standard for Windows under UEFI. It isn't clear if you read the documentation before installing Qubes, or if you have a back up or cloned disk. If you didn't I would do it now before trying anything else. You can attach the NTFS partitions to a qube and copy the data off, or clone the whole partition. Good luck. I appreciate your replies, I'm not a sysadmin, enabled legacy boot , i only vaguely understand that that is requird for Qubes, anyway, i've got qubes installed, it's just acting different than on my desktop version is, I don't expect any replies, just hoping for more than 1 or 2 , hence I asked about the IRC, but I'm guessing that isn't well attended also forgive me , for asking , it really isn't "a two minute" search it is that Grub and such are complicated for non sysadmin people just for the record, I would think Qubes might like to have normal non sysadmin people able to use the OS, so my questions to the list, my serve those people, The format of post and wait days or never for a reply may not be ideal for anything complicated IMHO anyway, thanks for listening -- 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/db6942e9-4094-dbd4-d955-ffa098e2ea28%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Laptop Dual Win10 boot problem
On Sat, Jul 01, 2017 at 10:05:36AM -1000, yreb-qusw wrote: > On 06/28/2017 04:03 PM, cooloutac wrote: > > so you would put hd0,X X= 1 2 or 3 etc... you said it was 200mb right so > > just look for something around that in kb's. probably the smallest > > partition it should say file type too no? ntfs. > > > > actualy this is from the qubes doc's not me > > > -- > Identify the Windows system partition that has /bootmgr > > In blkid output, the system partition is the one with LABEL=’SYSTEM > RESERVED’ or LABEL=’SYSTEM’ and is only about 100 to 200 MB in size > -- > > > ntldr (hd0,msdos2)/bootmgr ? > > or > > ntldr (hd0,2)/bootmgr ? > > > I would think it would be the 1st partitions when it comes to booting. > > > Is it possible my boot partition for win10 got overwritten when > installing Qubes somehow ? > > > > Maybe I should give up , as by the slow/no responses, it seems there is > no way to get support for this > As far as I can see a number of people have tried to help you here You should read the guidelines at www.qubes-os.org/mailing-lists and be patient. Also, a two minute search on the net would bring you to guides that would enable you to learn something about grub and maybe solve the problem for yourself. On the specific points: I doubt that your Win10 boot partition got overwritten , unless you asked the installer to do so. It is possible to run Windows without a SYSTEM partition, particularly if installed in BIOS mode - it is, however, not standard. fdisk -l shows you which partition has been marked as bootable - this need not be the partition you want. It need not be the first partition. Nothing will go wrong if you get the partition specification wrong - Windows wont boot and you will see an error message. >From what you have said you have two options: msdos1 and msdos2. In grub partitions are numbered starting from 1, so these can be referenced as hd0,msdos1 and hd0,msdos2. Just create two entries, one for each partition, and try to boot: if the first fails, reboot and choose the second. Incidentally, its relatively simple to enable legacy boot on InsydeH20 - again, a simple search would show you how. Unless someone did this for you it's most likely that you are in UEFI mode. You can check this in Linux by looking at the output from dmesg, and looking for "efi" entries - 'dmesg|grep efi' Also,look in /sys/firmware for efi directory. If it's there then you booted UEFI. The partition layout you have described doesn't seem to be standard for Windows under UEFI. It isn't clear if you read the documentation before installing Qubes, or if you have a back up or cloned disk. If you didn't I would do it now before trying anything else. You can attach the NTFS partitions to a qube and copy the data off, or clone the whole partition. Good luck. -- 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/20170701221027.axskrptkphp4iilv%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Laptop Dual Win10 boot problem
On 06/28/2017 04:03 PM, cooloutac wrote:
so you would put hd0,X X= 1 2 or 3 etc... you said it was 200mb right so
just look for something around that in kb's. probably the smallest partition
it should say file type too no? ntfs.
actually in the docs maybe instead they should recommmend
sudo fdisk -l
cause that Does show the boot partition /dev/sda2
however I'm left still not knowing how to write the 'stanza'
--
menuentry "Windows" {
insmod part_msdos
insmod ntldr
insmod ntfs
ntldr (hd1,X)/bootmgr
}
--
https://www.qubes-os.org/doc/multiboot/
eg in my case ?
ntldr (hd1,2)/bootmgr ? or
ntldr (hd0,2)/bootmgr
etc
sigh
--
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/1fa64476-f887-290c-6873-f4d67123c9b3%40riseup.net.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Laptop Dual Win10 boot problem
On 06/28/2017 04:03 PM, cooloutac wrote: so you would put hd0,X X= 1 2 or 3 etc... you said it was 200mb right so just look for something around that in kb's. probably the smallest partition it should say file type too no? ntfs. actualy this is from the qubes doc's not me -- Identify the Windows system partition that has /bootmgr In blkid output, the system partition is the one with LABEL=’SYSTEM RESERVED’ or LABEL=’SYSTEM’ and is only about 100 to 200 MB in size -- ntldr (hd0,msdos2)/bootmgr ? or ntldr (hd0,2)/bootmgr ? I would think it would be the 1st partitions when it comes to booting. Is it possible my boot partition for win10 got overwritten when installing Qubes somehow ? Maybe I should give up , as by the slow/no responses, it seems there is no way to get support for this -- 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/7fa47e67-87d4-7fb2-55e9-2642d53e97e1%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Terrible audio quality in one VM
On 07/01/2017 12:35 PM, Andrew Morgan wrote: I've had this problem for a while now, but so far haven't been able to pinpoint the cause. I have many VMs based on fedora-25 (this has been an issue since f23), but one of them always has very low-quality/scratchy bass in it. Unfortunately that happens to be the VM I do all my web-browsing in, making listening any music online a sub-par experience. I also have a VM specifically for watching media based on the same template, that has absolutely no problems with audio quality. There's no different between the different VMs in pavucontrol. Anyone have any idea on what may be causing this? Andrew Morgan I would guess its a pulse audio setting in your home folder. Easy way out may be to simply copy your data files over to a new appVM. -- Chris Laprise, tas...@openmailbox.org https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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/51e755f1-ee53-3083-5102-8621c87c3d59%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Rules for when "Update VM" is an active menu item
On 07/01/2017 01:33 PM, motech man wrote: On Saturday, July 1, 2017 at 5:37:53 AM UTC-5, Chris Laprise wrote: On 06/29/2017 01:13 PM, motech man wrote: I updated the fedora 23 template with changes to the hosts /etc/file, and I noticed that all other VMs that used that template had the update flag set. That makes perfect sense. So when I was done I shutdown the template VM and now the Update VM item is grayed out in the dom0 menu. Restarting the fedora 23 template or any of the VMs that use it in any order or combination does not allow me to update the VMs that use that template. I made sure all VMs that use that template were shutdown. In fact the only VM running is dom0. What is the correct procedure for updating the hosts file for all VMs dependent on fedora 23 (what is the rule for when the 'Update VM' menu is active)? You perform updates on templates themselves, not on the VMs which use them. The indicator you're referring to as "update flag" simply shows that the VM's template has been changed in some way. Shutting down the template and re-starting the derivative VM is how you make the update take effect in the VM. -- Chris Laprise, tasket@openmailbox dot org https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 I am aware of the template / AppVM relationship. However simply restarting the AppVM to obtain the updated hosts file does not work. I also mentioned an odd symptom associated with changing the hosts file in a subsequent post. Niether are explained by your reply, but thx for it anyway. "...now the Update VM item is grayed out in the dom0 menu." This reference to 'menu' gave me the impression you were trying to perform normal OS updates, but for the appVMs directly. Re: hosts file, here was some discussion: https://groups.google.com/forum/#!topic/qubes-users/xy2eYiZHvW4 FWIW, Fedora 23 is outdated and something may not be working quite right. I tried modifying hosts in a Debian 9 template and the change did propagate to the derivative VMs. -- Chris Laprise, tas...@openmailbox.org https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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/da8377b7-6bc8-2b8e-53ff-0bef5463df2d%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Rules for when "Update VM" is an active menu item
On Sat, Jul 01, 2017 at 10:33:01AM -0700, motech man wrote: > On Saturday, July 1, 2017 at 5:37:53 AM UTC-5, Chris Laprise wrote: > > On 06/29/2017 01:13 PM, motech man wrote: > > > I updated the fedora 23 template with changes to the hosts /etc/file, > > > and I noticed that all other VMs that used that template had the > > > update flag set. That makes perfect sense. > > > > > > So when I was done I shutdown the template VM and now the Update VM > > > item is grayed out in the dom0 menu. Restarting the fedora 23 > > > template or any of the VMs that use it in any order or combination > > > does not allow me to update the VMs that use that template. > > > > > > I made sure all VMs that use that template were shutdown. In fact the > > > only VM running is dom0. > > > > > > What is the correct procedure for updating the hosts file for all VMs > > > dependent on fedora 23 (what is the rule for when the 'Update VM' > > > menu is active)? > > > > > I am aware of the template / AppVM relationship. However simply restarting > the AppVM to obtain the updated hosts file does not work. I also mentioned an > odd symptom associated with changing the hosts file in a subsequent post. > Niether are explained by your reply, but thx for it anyway. > I don't have a fedora 23, but I have tested 24, and assorted Debian templates, and all of them work as expected. So I would say that the "correct procedure" is to do what you have done. This doesn't explain why it does not work for you or why you get the "censored" output - I'm assuming here that those are ACTUAL x characters. What package versions are you using? Are you using a default template with no other changes? -- 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/20170701183040.ku6uac6xvxsancph%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Rules for when "Update VM" is an active menu item
On Saturday, July 1, 2017 at 5:37:53 AM UTC-5, Chris Laprise wrote: > On 06/29/2017 01:13 PM, motech man wrote: > > I updated the fedora 23 template with changes to the hosts /etc/file, > > and I noticed that all other VMs that used that template had the > > update flag set. That makes perfect sense. > > > > So when I was done I shutdown the template VM and now the Update VM > > item is grayed out in the dom0 menu. Restarting the fedora 23 > > template or any of the VMs that use it in any order or combination > > does not allow me to update the VMs that use that template. > > > > I made sure all VMs that use that template were shutdown. In fact the > > only VM running is dom0. > > > > What is the correct procedure for updating the hosts file for all VMs > > dependent on fedora 23 (what is the rule for when the 'Update VM' > > menu is active)? > > > > You perform updates on templates themselves, not on the VMs which use them. > > The indicator you're referring to as "update flag" simply shows that the > VM's template has been changed in some way. Shutting down the template > and re-starting the derivative VM is how you make the update take effect > in the VM. > > -- > > Chris Laprise, tasket@openmailbox dot org > https://twitter.com/ttaskett > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 I am aware of the template / AppVM relationship. However simply restarting the AppVM to obtain the updated hosts file does not work. I also mentioned an odd symptom associated with changing the hosts file in a subsequent post. Niether are explained by your reply, but thx for it anyway. -- 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/af5173a3-622a-4c1c-a8e2-5a5d795c30b6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Terrible audio quality in one VM
I've had this problem for a while now, but so far haven't been able to pinpoint the cause. I have many VMs based on fedora-25 (this has been an issue since f23), but one of them always has very low-quality/scratchy bass in it. Unfortunately that happens to be the VM I do all my web-browsing in, making listening any music online a sub-par experience. I also have a VM specifically for watching media based on the same template, that has absolutely no problems with audio quality. There's no different between the different VMs in pavucontrol. Anyone have any idea on what may be causing this? Andrew Morgan -- 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/oj8ivv%2423n%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
[qubes-users] Re: How to enlarge the size of hvm?
Yes I got my windows hvm to full-size with the Windows tools. Now I'm trying to see if I change the one for Kali at all instead of such a small screen. -- 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/6d31e511-48f3-43d6-a429-5d7dbb745924%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: NO SOUND after debian 9 (stretch) upgrade + workaround
I have same problem. Thanks for you solution. -- 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/96137ff7-2b95-4fe0-b5b7-c6d5ce94de78%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Rules for when "Update VM" is an active menu item
On 06/29/2017 01:13 PM, motech man wrote: I updated the fedora 23 template with changes to the hosts /etc/file, and I noticed that all other VMs that used that template had the update flag set. That makes perfect sense. So when I was done I shutdown the template VM and now the Update VM item is grayed out in the dom0 menu. Restarting the fedora 23 template or any of the VMs that use it in any order or combination does not allow me to update the VMs that use that template. I made sure all VMs that use that template were shutdown. In fact the only VM running is dom0. What is the correct procedure for updating the hosts file for all VMs dependent on fedora 23 (what is the rule for when the 'Update VM' menu is active)? You perform updates on templates themselves, not on the VMs which use them. The indicator you're referring to as "update flag" simply shows that the VM's template has been changed in some way. Shutting down the template and re-starting the derivative VM is how you make the update take effect in the VM. -- Chris Laprise, tas...@openmailbox.org https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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/d2653010-e44b-92a4-c09c-14e2f1abe2e6%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: How to enlarge the size of hvm?
On Saturday, July 1, 2017 at 9:13:40 AM UTC+2, jaki...@gmail.com wrote: > Guess I didn't make myself clear. I meant the size of the display itself not > the size of storage. > > In Qubes manager I only see the disk storage, and memory CPU. I'm not seeing > any settings in relation to the display. > > Inside the vm in display settings my resolution is at max option of 1024x68. I see. No, that is something that just follows from the screen size for me (with seamless mode disabled). E.g. when I tell it to use the left side of the screen, the Qubes Video Driver changes the resolution on the fly. Did you install the Qubes Windows tools? -- 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/e2e0c0de-921d-4d2e-8605-fb50f40afa09%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: How to enlarge the size of hvm?
Guess I didn't make myself clear. I meant the size of the display itself not the size of storage. In Qubes manager I only see the disk storage, and memory CPU. I'm not seeing any settings in relation to the display. Inside the vm in display settings my resolution is at max option of 1024x68. -- 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/5198e49d-eda6-4f3b-b30b-e1ca8228e10a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
