date:20171230

[qubes-users] Qubes R3.3

2017-12-30 Thread fepitre

A topic of the topic in the devel list
(https://groups.google.com/d/msg/qubes-devel/PhI0-9RfI7Y/GBs4f6VaDQAJ), for
those who want to try:

1: git clone -b master-fepitre https://github.com/fepitre/qubes-builder
2: use the builder-R3.3.conf joined to this message
3: make qubes template iso
4: burn the ISO and have fun :)

The master-fepitre branch is just the master one with my signing key added in
the trusted key when verifying the git tags (check it!)

Of course, you will not have any update from the officials repositories. You
can do your own repos or if there is really a need, I could do something about
it.

Please keep in mind this is an UNOFFICIAL release. This is not polish as it
should be and I have not had time to test everything (e.g. backup). Also, the
few problems with Debian 9 (X not starting etc, I have not took the time to
correct it as it will be done in the officials repositories very soon).

As I said in my initial post, only few backports was needed with respect to the
master branches. From my side, using a more recent version of core-libvirt lead
me to recover the use of dispvm! The use of dom0 FC25 allows me to finally use
more recent packages for some dom0 custom things.

Next step, wait for the great R4.0 :)

--
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/4a97bc88-cbd8-4b7b-9046-d4ef8d537db9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: [coreboot] G505s with Coreboot unable to run any version of Qubes

2017-12-30 Thread 'Emil Novik' via qubes-users

Thanks !

With the help of Awokd I managed to boot each version by using 
"xen-pciback.hide=(PCI address of the discrete GPU)" and the small grub fix for 
3.2.

I was planning on using 4rc3 but the VM setup on first boot always fails to 
create sys-net because of a libxenlight error. I can still start my session but 
no internet access, same error each time I try to start sys-net and no VM 
manager to be found.

So I decided to use 3.2 and it works like a charm, just needs some more ram and 
all will be perfect :)

---
Emil Novik

 Original Message 
On Dec 30, 2017, 21:44, Ivan Ivanov wrote:

> Hi Emil, thank you very much for your report.
> Regarding Qubes 3.2 : at the Qubes HCL list I wrote:
>
> "after Qubes R3.2 installation it cant boot - cant reach GRUB Boot Menu
> because MBR (or GRUB) is corrupted. Use grub2-install to fix it (read more)
> Everything else is OK "
>
> https://groups.google.com/forum/#!msg/qubes-users/TS1zfKZ7q8w/JQFkVF4xBgAJ
>
> If you fix your GRUB as described ^^^ you may be able to finally boot Qubes 
> 3.2
> Please test it and let me know the results
>
> Live 3.1 was buggy, full 3.1 would have worked. Haven't tested 4.0 -
> can't speak about it
>
> Best regards,
> Ivan
>
> 2017-12-28 1:19 GMT+03:00 Emil Novik via coreboot :
>> Hey, I'm having some heavy trouble getting my laptop to run Qubes and I
>> first thought I was having issues with the OS. But after digging into the
>> logs I managed to get(crashes too early during boot to get any persistent
>> logs, had to write most by hand) it feels more like an issue with my
>> Coreboot built.
>>
>> So there are the details :
>> - G505s with integrated HD 8650G + discrete R5 M230 graphics.
>> - Coreboot 4.6-2477-g6ab3edac3c-dirty with processor microcode patch
>> (change-ID: Ibbfee47ce1d5081640d6924e2b12f5213a7fcadb).
>> - Runs Debian Stretch fine.
>> - Fails to start Qubes 3.2 / 4.0 rc3 / Live 3.1.
>> - I added the vgabios.rom for the integrated card with menuconfig and the
>> one for the discrete card with cbfstool.
>> - Coreboot.rom, .config and full make output as attachment.
>>
>>
>> Some more error data I gathered from coreinfo's Bootlog :
>>
>> Failed to enable LTR for dev = PCI: 01:00.0
>> Failed to enable LTR for dev = PCI: 02:00.0
>> ...
>> I2C: 01:50 missing read_resources
>> I2C: 01:51 missing read_resources
>> PNP: 00ff.1 missing read_resources
>> ...
>> Warning: Can't write PCI_INTR 0xC00/0xC01 registers because
>> 'mainboard_picr_data' or 'mainboard_intr_data' tables are NULL
>> Warning: Can't write PCI IRQ assignments because 'mainboard_pirq_data'
>> structure does not exist
>> ...
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
>> ...
>> Manufacturer: ef
>> SF: Detected W25Q32 with sector size 0x1000, total 0x40
>> ASSERTION ERROR: file 'src/drivers/spi/spi_flash.c', line 425
>> ASSERTION ERROR: file 'src/drivers/spi/spi_flash.c', line 425
>> ASSERTION ERROR: file 'src/drivers/spi/spi_flash.c', line 425
>> ASSERTION ERROR: file 'src/drivers/spi/spi_flash.c', line 425
>> Manufacturer: ef
>> SF: Detected W25Q32 with sector size 0x1000, total 0x40
>> ASSERTION ERROR: file 'src/drivers/spi/spi_flash.c', line 425
>> ASSERTION ERROR: file 'src/drivers/spi/spi_flash.c', line 425
>>

[qubes-users] Re: [coreboot] G505s with Coreboot unable to run any version of Qubes

2017-12-30 Thread Ivan Ivanov

Hi Emil, thank you very much for your report.
Regarding Qubes 3.2 : at the Qubes HCL list I wrote:

"after Qubes R3.2 installation it cant boot - cant reach GRUB Boot Menu
because MBR (or GRUB) is corrupted. Use grub2-install to fix it (read more)
Everything else is OK "

https://groups.google.com/forum/#!msg/qubes-users/TS1zfKZ7q8w/JQFkVF4xBgAJ

If you fix your GRUB as described ^^^ you may be able to finally boot Qubes 3.2
Please test it and let me know the results

Live 3.1 was buggy, full 3.1 would have worked. Haven't tested 4.0 -
can't speak about it

Best regards,
Ivan

2017-12-28 1:19 GMT+03:00 Emil Novik via coreboot :
> Hey, I'm having some heavy trouble getting my laptop to run Qubes and I
> first thought I was having issues with the OS. But after digging into the
> logs I managed to get(crashes too early during boot to get any persistent
> logs, had to write most by hand) it feels more like an issue with my
> Coreboot built.
>
> So there are the details :
> - G505s with integrated HD 8650G + discrete R5 M230 graphics.
> - Coreboot 4.6-2477-g6ab3edac3c-dirty with processor microcode patch
> (change-ID: Ibbfee47ce1d5081640d6924e2b12f5213a7fcadb).
> - Runs Debian Stretch fine.
> - Fails to start Qubes 3.2 / 4.0 rc3 / Live 3.1.
> - I added the vgabios.rom for the integrated card with menuconfig and the
> one for the discrete card with cbfstool.
> - Coreboot.rom, .config and full make output as attachment.
>
>
> Some more error data I gathered from coreinfo's Bootlog :
>
> Failed to enable LTR for dev = PCI: 01:00.0
> Failed to enable LTR for dev = PCI: 02:00.0
> ...
> I2C: 01:50 missing read_resources
> I2C: 01:51 missing read_resources
> PNP: 00ff.1 missing read_resources
> ...
> Warning: Can't write PCI_INTR 0xC00/0xC01 registers because
> 'mainboard_picr_data' or 'mainboard_intr_data' tables are NULL
> Warning: Can't write PCI IRQ assignments because 'mainboard_pirq_data'
> structure does not exist
> ...
> ASSERTION ERROR: file
> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
> ASSERTION ERROR: file
> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
> ASSERTION ERROR: file
> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
> ASSERTION ERROR: file
> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
> ASSERTION ERROR: file
> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
> ASSERTION ERROR: file
> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
> ASSERTION ERROR: file
> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
> ASSERTION ERROR: file
> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
> ASSERTION ERROR: file
> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
> ASSERTION ERROR: file
> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
> ASSERTION ERROR: file
> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
> ASSERTION ERROR: file
> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
> ASSERTION ERROR: file
> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
> ASSERTION ERROR: file
> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
> ASSERTION ERROR: file
> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
> ASSERTION ERROR: file
> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
> ASSERTION ERROR: file
> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
> ASSERTION ERROR: file
> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
> ...
> Manufacturer: ef
> SF: Detected W25Q32 with sector size 0x1000, total 0x40
> ASSERTION ERROR: file 'src/drivers/spi/spi_flash.c', line 425
> ASSERTION ERROR: file 'src/drivers/spi/spi_flash.c', line 425
> ASSERTION ERROR: file 'src/drivers/spi/spi_flash.c', line 425
> ASSERTION ERROR: file 'src/drivers/spi/spi_flash.c', line 425
> Manufacturer: ef
> SF: Detected W25Q32 with sector size 0x1000, total 0x40
> ASSERTION ERROR: file 'src/drivers/spi/spi_flash.c', line 425
> ASSERTION ERROR: file 'src/drivers/spi/spi_flash.c', line 425
> ASSERTION ERROR: file 'src/drivers/spi/spi_flash.c', line 425
> ASSERTION ERROR: file 'src/drivers/spi/spi_flash.c', line 425
> ASSERTION ERROR: file 'src/drivers/amd/agesa/state_machine.c', line 309
> ...
> EEPROM not found
> EEPROM not found
> EEPROM not found
> EEPROM not found
> EEPROM not found
> EEPROM not found
> EEPROM not found
> ...
> I2C: 01:50 (unknown)
> I2C: 01:51 (unknown)
> ...
> APIC: 11 (unknown)
> APIC: 12 (unknown)
> APIC: 13 (unknown)
> PCI: 01:00.0 (unknown)
> PCI: 02:00.0 (unknown)
> PNP: 00ff.0 (unknown)
>
>
> "..." are parts I didn't write down as they didn't show any obvious
> errors(but I'm bad at seeing them) and it would take me a lng time to
> write down the full

Re: [qubes-users] qubes-mirage-firewall 0.4

2017-12-30 Thread Roy Bernat

On Saturday, 30 December 2017 15:51:14 UTC+2, ra...@ralphdouglass.com  wrote:
> Here's a script that should do the trick (run in dom0):
> 
> $ cat create-mirage-firewall-vm 
> #!/bin/bash
> 
> qvm-create \
>   --property kernel=mirage-firewall \
>   --property kernelopts=None \
>   --property memory=32 \
>   --property maxmem=32 \
>   --property netvm=sys-net \
>   --property provides_network=True \
>   --property vcpus=1 \
>   --property virt_mode=pv \
>   --label=red \
>   --class StandaloneVM \
>   mirage-firewall
> 
> On Saturday, December 30, 2017 at 6:46:25 AM UTC-5, ra...@ralphdouglass.com 
> wrote:
> > On Friday, December 29, 2017 at 3:51:47 AM UTC-5, Roy Bernat wrote:
> > > On Monday, 25 December 2017 09:20:02 UTC+2, Roy Bernat  wrote:
> > > > On Sunday, 24 December 2017 16:24:37 UTC+2, donoban  wrote:
> > > > > On 12/24/2017 12:57 PM, Roy Bernat wrote:
> > > > > > 
> > > > > > Hi 
> > > > > > 
> > > > > > Not seems to work for me . 
> > > > > > 
> > > > > > Ideas ? 
> > > > > > 
> > > > > > R
> > > > > > 
> > > > > 
> > > > > Could you paste your 'qvm-prefs mirage-firewall' output?
> > > > 
> > > > autostart D  False
> > > > backup_timestamp  D  
> > > > debug -  False
> > > > default_dispvmD  fedora-25-dvm
> > > > default_user  D  user
> > > > gateway   D  
> > > > gateway6  D  
> > > > include_in_backupsD  True
> > > > installed_by_rpm  D  False
> > > > ipD  10.137.0.33
> > > > ip6   D  
> > > > kernel-  mirage-firewall
> > > > kerneloptsD  nopat
> > > > klass D  AppVM
> > > > label -  green
> > > > mac   D  
> > > > maxmem-  320
> > > > memory-  32
> > > > name  -  mirage-firewall
> > > > netvm -  sys-net
> > > > provides_network  -  False
> > > > qid   -  33
> > > > qrexec_timeoutD  60
> > > > stubdom_mem   U
> > > > stubdom_xid   D  -1
> > > > template  -  fedora-26-minimal
> > > > template_for_dispvms  D  False
> > > > updateableD  False
> > > > uuid  -  378b816e-b7bf-4ec3-a22a-03218cc433bd
> > > > vcpus -  1
> > > > virt_mode -  pv
> > > > visible_gateway   D  10.137.0.5
> > > > visible_gateway6  D  
> > > > visible_ipD  10.137.0.33
> > > > visible_ip6   D  
> > > > visible_netmask   D  255.255.255.255
> > > > xid   D  -1
> > > 
> > > Someone ???
> > 
> > Try changing provides_network:
> > 
> > $ qvm-prefs mirage-firewall provides_network True

Great , it is working .  

Thanks to all 

-- 
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/4088b960-11b9-48ed-8408-75d77c131d7c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Detached LUKS header

2017-12-30 Thread spiegs

Hello!
One simple question: is it possible to setup Qubes OS with detached LUKS 
header and store it on bootable USB key?
Tried custom installation, but seems that the GUI thingie doesn't recognize 
LUKS partition without the header :(
With archlinux this was a breeze.

-- 
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/19134cb2-8f6e-4678-9b3c-eab88f7ba5f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Enable PCI_HOTPLUG

2017-12-30 Thread Fabrizio Romano Genovese

Hello everyone,

As in 
https://github.com/QubesOS/qubes-issues/issues/1673
It looks like PCI Hotplug is disabled by default in Qubes. I just bought a new 
laptop with thunderbolt port, and I really need PCI hotplug since I attach and 
detach it from my dockstation multiple times per day. 
I am aware of the risks of having PCI hotplug enabled, but I do not take my PC 
out of my house very often, so it is in general quite difficult for someone to 
have physical access to it. Moreover, I also use thunderbird port blockers 
(that are just some plastic caps that you stick into your port and can't take 
out without a particular key). Obviously this solution is still not 100% secure 
but, all things considered, it is enough for my use case.
So, how do I enable PCI hotplug? Do I have to manually compile the kernel? I'm 
a total noob when it comes to this sort of things so if someone could at least 
redirect me to a guide to do this I'd really appreciate it!

Cheers,
Fab

-- 
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/2e720f96-f8c2-420a-8968-6a47c10bfd9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: [3.2] HCL report for Inspiron 15-5578 (AKA 15z Touch)

2017-12-30 Thread Vít Šesták

Just another note: I have found that the laptop has accelerometers and they can 
be used for autorotation with a simple script: 
https://github.com/admiralakber/thinkpad-yoga-scripts/blob/master/rotate/thinkpad-rotate.py

I've tuned it a bit, so it does not configure touchpads. I use an external 
touchpad that is rotated, so its autoconfiguration by this script is not 
welcome.

Regards,
Vít Šesták 'v6ak'

-- 
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/09e9e11f-d92d-46f1-b52a-9acbc35e8091%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qubes-mirage-firewall 0.4

2017-12-30 Thread ralph

Here's a script that should do the trick (run in dom0):

$ cat create-mirage-firewall-vm 
#!/bin/bash

qvm-create \
  --property kernel=mirage-firewall \
  --property kernelopts=None \
  --property memory=32 \
  --property maxmem=32 \
  --property netvm=sys-net \
  --property provides_network=True \
  --property vcpus=1 \
  --property virt_mode=pv \
  --label=red \
  --class StandaloneVM \
  mirage-firewall

On Saturday, December 30, 2017 at 6:46:25 AM UTC-5, ra...@ralphdouglass.com 
wrote:
> On Friday, December 29, 2017 at 3:51:47 AM UTC-5, Roy Bernat wrote:
> > On Monday, 25 December 2017 09:20:02 UTC+2, Roy Bernat  wrote:
> > > On Sunday, 24 December 2017 16:24:37 UTC+2, donoban  wrote:
> > > > On 12/24/2017 12:57 PM, Roy Bernat wrote:
> > > > > 
> > > > > Hi 
> > > > > 
> > > > > Not seems to work for me . 
> > > > > 
> > > > > Ideas ? 
> > > > > 
> > > > > R
> > > > > 
> > > > 
> > > > Could you paste your 'qvm-prefs mirage-firewall' output?
> > > 
> > > autostart D  False
> > > backup_timestamp  D  
> > > debug -  False
> > > default_dispvmD  fedora-25-dvm
> > > default_user  D  user
> > > gateway   D  
> > > gateway6  D  
> > > include_in_backupsD  True
> > > installed_by_rpm  D  False
> > > ipD  10.137.0.33
> > > ip6   D  
> > > kernel-  mirage-firewall
> > > kerneloptsD  nopat
> > > klass D  AppVM
> > > label -  green
> > > mac   D  
> > > maxmem-  320
> > > memory-  32
> > > name  -  mirage-firewall
> > > netvm -  sys-net
> > > provides_network  -  False
> > > qid   -  33
> > > qrexec_timeoutD  60
> > > stubdom_mem   U
> > > stubdom_xid   D  -1
> > > template  -  fedora-26-minimal
> > > template_for_dispvms  D  False
> > > updateableD  False
> > > uuid  -  378b816e-b7bf-4ec3-a22a-03218cc433bd
> > > vcpus -  1
> > > virt_mode -  pv
> > > visible_gateway   D  10.137.0.5
> > > visible_gateway6  D  
> > > visible_ipD  10.137.0.33
> > > visible_ip6   D  
> > > visible_netmask   D  255.255.255.255
> > > xid   D  -1
> > 
> > Someone ???
> 
> Try changing provides_network:
> 
> $ qvm-prefs mirage-firewall provides_network True

-- 
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/5817f5c8-e224-4505-bb49-76f85303fca5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qubes-mirage-firewall 0.4

2017-12-30 Thread ralph

On Friday, December 29, 2017 at 3:51:47 AM UTC-5, Roy Bernat wrote:
> On Monday, 25 December 2017 09:20:02 UTC+2, Roy Bernat  wrote:
> > On Sunday, 24 December 2017 16:24:37 UTC+2, donoban  wrote:
> > > On 12/24/2017 12:57 PM, Roy Bernat wrote:
> > > > 
> > > > Hi 
> > > > 
> > > > Not seems to work for me . 
> > > > 
> > > > Ideas ? 
> > > > 
> > > > R
> > > > 
> > > 
> > > Could you paste your 'qvm-prefs mirage-firewall' output?
> > 
> > autostart D  False
> > backup_timestamp  D  
> > debug -  False
> > default_dispvmD  fedora-25-dvm
> > default_user  D  user
> > gateway   D  
> > gateway6  D  
> > include_in_backupsD  True
> > installed_by_rpm  D  False
> > ipD  10.137.0.33
> > ip6   D  
> > kernel-  mirage-firewall
> > kerneloptsD  nopat
> > klass D  AppVM
> > label -  green
> > mac   D  
> > maxmem-  320
> > memory-  32
> > name  -  mirage-firewall
> > netvm -  sys-net
> > provides_network  -  False
> > qid   -  33
> > qrexec_timeoutD  60
> > stubdom_mem   U
> > stubdom_xid   D  -1
> > template  -  fedora-26-minimal
> > template_for_dispvms  D  False
> > updateableD  False
> > uuid  -  378b816e-b7bf-4ec3-a22a-03218cc433bd
> > vcpus -  1
> > virt_mode -  pv
> > visible_gateway   D  10.137.0.5
> > visible_gateway6  D  
> > visible_ipD  10.137.0.33
> > visible_ip6   D  
> > visible_netmask   D  255.255.255.255
> > xid   D  -1
> 
> Someone ???

Try changing provides_network:

$ qvm-prefs mirage-firewall provides_network True

-- 
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/915d9fc1-b597-4d59-9964-e5f27fdd4ebd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Touchscreen not working on Qubes 3.2

2017-12-30 Thread Vít Šesták

While both mouse and touchscreen have some similarities (both are pointing 
devices), there are also some important differences:

First, mouse reports relative movements, while touchscreen reports absolute 
positions of touch.
Second, mouse reports two different types of events (movement and clicks*), 
while touchscreen reports just touches.
Third, touchscreen might report multiple pointers.

For those reasons, touchscreen needs a different proxy, which is not 
implemented yet.

Regards,
Vít Šesták 'v6ak'

*) Scrolling is AFAIK a specific type of button.

-- 
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/8677bc98-f7c1-490f-b28e-4cd6cb243f5e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Lenovo G505s with Coreboot and Qubes R4-rc3 fails to boot

2017-12-30 Thread Ivan Ivanov

Thank you very much! Luckily, when the people search, your posts and
posts like this are among the top results:
https://libreboot.org/faq.html#will-the-purism-laptops-be-supported
"There are severe privacy, security and freedom issues with these
laptops, due to the Intel chipsets that they use"
Hopefully the majority of their buyers realize that they are getting a
typical Intel laptop with coreboot preinstalled,
which is not the "Ultimate Freedom Machine" and actually not much
better than Sandy/Ivy Bridge thinkpads...

Meanwhile, let me to spam this again ;)
" Great idea is to stockpile the G505S and its spare replacement parts
/ IC components , so that - if your current one breaks - you had a
more than one replacement.
Lenovo tells that the average lifespan of G505S laptop is 4 years -
and, while it could survive longer in the caring hands - it would
really help if you have the replacement G505S / G505S motherboards /
major components of G505S motherboard like the spare KB9012QF A3
controllers and southbridge.
Especially the KB9012's - they are very cheap, and at the same time -
vulnerable to voltage spikes, so if you have unstable electricity at
house and your power adapter wouldn't block a spike - KB9012 could
easily die. AliExpress is your friend... :P "

Mike is good at writing wiki pages like these:
http://dangerousprototypes.com/docs/Flashing_a_BIOS_chip_with_Bus_Pirate
http://dangerousprototypes.com/docs/Flashing_KB9012_with_Bus_Pirate
http://dangerousprototypes.com/docs/Compal_POST_diagnostic_card
http://dangerousprototypes.com/docs/Compal_POST_diagnostic_card_-_Additional
Maybe together we could create a new page for us all, describing the
G505S components and their part numbers.
I will ask him about it soon

Unlike the libreboot-supported laptops, which are good but have a slow
hardware ( Core 2 Duo / 4 GB RAM ),
G505S ia a quad core beast with 16 GB RAM possible -> and at the
same time not Intel ME / PSP !
Could take many years before we see another laptop with such a great
performance / freedom ratio,
so it makes a total sense to turn it into Long Term Support laptop for
you and your freedom caring friends.

And, if you accidentally get too many G505S - their value should only
rise in the future, could re-sell.
Just hope we wouldn't inflate the prices for each other at those auctions ;-)

Happy coming New Year :)
Ivan

2017-12-30 3:20 GMT+03:00 taii...@gmx.com :
> On 12/29/2017 06:39 PM, awokd wrote:
>
>> On Fri, December 29, 2017 11:32 pm, Ivan Ivanov wrote:
>>>
>>> 2017-12-30 1:57 GMT+03:00 taii...@gmx.com :
>>>
>>> Yes, I am also very disappointed in purism, and its still unclear for
>>> me why they went the Intel road, when - at 2013 - they could have created
>>> a
>>> more freedom-respecting equivalent of G505S, instead of
>>
>> This was hashed over in the Coreboot mailing list recently, see
>> https://mail-archive.com/coreboot@coreboot.org/msg50746.html. To be
>> honest, I'm kind of tired of hearing about Purism now. ;) I think people
>> have made their positions clear.
>
> :<
> I only make so much noise because no one else is doing so - they have
> strangely universal positive coverage in the mainstream tech media and the
> real facts and downsides are never mentioned or investigated - not to
> mention that the real libre products like TALOS 2 and Novena get little to
> no press for some reason.
>
> I respect your opinion, but there are still so many laymen who think that
> "LibreM" means "Libre" (the purism goons say it doesn't and that its not
> their fault people are confused) so I feel as though I must continue.

-- 
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/CAAaskFB0U6fSBs3i06-0_8byp5g%2BNRvVJJcqcv40jVPZ8OUFcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes R3.3

[qubes-users] Re: [coreboot] G505s with Coreboot unable to run any version of Qubes

[qubes-users] Re: [coreboot] G505s with Coreboot unable to run any version of Qubes

Re: [qubes-users] qubes-mirage-firewall 0.4

[qubes-users] Detached LUKS header

[qubes-users] Enable PCI_HOTPLUG

[qubes-users] Re: [3.2] HCL report for Inspiron 15-5578 (AKA 15z Touch)

Re: [qubes-users] qubes-mirage-firewall 0.4

Re: [qubes-users] qubes-mirage-firewall 0.4

[qubes-users] Re: Touchscreen not working on Qubes 3.2

Re: [qubes-users] Re: Lenovo G505s with Coreboot and Qubes R4-rc3 fails to boot

11 matches

Site Navigation

Mail list logo

Footer information